Related
Greetings!
So, I just recently got my Note 3 after having to suffer for 2 years using an apple product ( which I hated ) , I had previous experience with rooting / loading ROMS on a Moto Droid X.
So I used Root De La Vega initially and rooted my phone with no problems.
Then I got the stupid software update notification that would pop up every 5 minutes on my phone and would only let me install now or schedule a time if I hit cancel. So I bit the bullet and installed the update, then used Kingo to re-root.
Everything worked, Knox still set to 0x0
I started looking into Safe Strap, I installed it , downloaded Jelly Bean ROM , and thought I had picked the first slot and went to install it, only to find out that I just installed it into the Stock Partition. By then it was to late, I was afraid to pull the battery so I just decided to see what happened.
Jelly Bean Rom installed , I kept all my apps and settings. But now every time I reboot my phone I get a screen that says Safe Strap is disabled , and to enter recovery or continue. Both work, if I select Recovery, I go into the Safe Strap menu, if I click on Continue the Jelly Bean Rom loads.
But I am wondering if this is for lack of a better term, a "clean" set up? I have the stock firmware downloaded, so I was wondering if I should ( or could ) Odin back to stock , then re-root , Safe Strap and then load roms correctly ( as in , not over stock ) and if that would be the correct way to do it?
Any advice would be appreciated. Thanks!
yes odin back to stockJ7 and start over. Brandonz has nice tutorial in the general section on setting up SafeStrap correctly.
droidstyle said:
yes odin back to stockJ7 and start over. Brandonz has nice tutorial in the general section on setting up SafeStrap correctly.
Click to expand...
Click to collapse
Thanks, I kind of thought starting over was the best thing to do. XDA has so much content it can be hard to filter through all of the noise to get solid answers.
Should Odin just be a plug in and reflash type of deal, or am I going to have to go into the phone, disable root , uninstall SS , then Odin? If I uninstall SS will I still be able to boot back into the stock partition?
Also the Firmware I got was posted earlier this week, it is ALL_N900VVRUBMI9_1671014_REV03 , do I need a different one?
That firmware is MI9. I think that You are currently on MJ7 because you took the update and had to root with Kingo. If you flash the MI9 fw, you will soft brick.
You need the MJ7 firmware found here:
http://forum.xda-developers.com/showthread.php?t=2483380
I've generally managed to root and/or customize most of my devices with the help from these forums, but this one has me stumped. I picked up an AT&T Galaxy S4 recently, and unfortunately it was already on a locked bootloader. I was able to root and install Safestrap 3.71 with little trouble. After some tweaking of the stock ROM, I decided to have a go with some custom ones.
Until recently, I'd been able to flash just about any SS-compatible ROM to any slot with little to no issue. Some required flashing of GApps, or Kernels, but aside from a few FC's or signal issues, the actual flashing portions always went smoothly. I ended up flashing DarthStalker vX1 to my stock slot with the MK2 kernels and have had zero issues with the ROM functionality. Being curious about recent developments with other ROM's, I decided to try flashing a few. The problem I'm having is that 90% of the ones I try to flash are going into a boot loop. Even those that worked previously (Hyperdrive, SHOstock) are boot looping.
I have tried deleting and recreating various ROM slots and at one point I managed to get SHOstock (SS) 3.0 to boot, but all of the GApps were crashing to the point where it was unusable, regardless of GApps I flashed over it for testing purposes.
I guess I'm wondering if there may be some sort of issue with having a custom ROM in the stock slot? Perhaps some sort of file or data corruption that is stopping these ROM's from working, even though they all worked previously? It just doesn't seem to be making sense because I don't believe I've changed anything since the last time I was able to flash to any SS slot. I've tried searching, but pretty much all of the boot loop issues I've come across were related to something that I've either already ruled out, or simply didn't apply to my configuration. Any hints or tips would be great. Please let me know if anyone needs more information about the config, or steps I've taken so far. Thanks all!
@remedee
I believe for HyperDrive u also need to install Att compatible pack and u also need flash ATT mk2 kernel modules .... check this thread about MK2 INDEX and ROM LISTS by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 anything u should know about all the compatible roms and instruction. ....u might get better help on that thread since alot of Rom flashaholic there. ...check with @ddubz he is flashaholic Master..... :thumbup::thumbup:.... Goodluck.....
Swyped From MK2 Dark Venom SS Edition
Once you flash a bad ROM on Stock slot and you boot loop, you are cooked. Only way to fix it is to Odin back to stock. Then you can restart the process.
If you flash a bad ROM on a ROM slot, you can just delete the ROM slot, recreate it, and you will be good to go for another try.
That's been my experience, anyways.
ted77usa said:
@remedee
I believe for HyperDrive u also need to install Att compatible pack and u also need flash ATT mk2 kernel modules .... check this thread about MK2 INDEX and ROM LISTS by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 anything u should know about all the compatible roms and instruction. ....u might get better help on that thread since alot of Rom flashaholic there. ...check with @ddubz he is flashaholic Master..... :thumbup::thumbup:.... Goodluck.....
Swyped From MK2 Dark Venom SS Edition
Click to expand...
Click to collapse
Thanks for the reply. I've read through quite a few of the threads for the individual ROMs, but unfortunately the issue isn't related to any one specific ROM. I do have the compatibility pack and modules for HyperDrive and I was able to successfully get that installed previously. I was using that as an example of a ROM that worked before with this same configuration, which is why it's bugging me. I'll wipe out the existing slot 1 and give it another go, making sure I flash those as well. Unfortunately that doesn't explain why SHOstock (which I tested extensively before), and others go into a boot loop as well.
The only thing I can think of is perhaps I'm not wiping properly. So far, whenever I attempt to install a new ROM, I create a new slot with the default size values, do a factory reset, install ROM and any module/kernel recommended with it, wipe cache, reboot. Not sure what else I could be doing wrong.
guut13 said:
Once you flash a bad ROM on Stock slot and you boot loop, you are cooked. Only way to fix it is to Odin back to stock. Then you can restart the process.
If you flash a bad ROM on a ROM slot, you can just delete the ROM slot, recreate it, and you will be good to go for another try.
That's been my experience, anyways.
Click to expand...
Click to collapse
Thankfully I don't think I've had any truly bad flashes that resulted in a brick, or even a partial brick. My stock slot is running a custom (Darthstalker) ROM that is still fully functional through all of this other testing. I do have backups of my original stock config, as well as a recent backup of the DS ROM in the stock slot, so I'm not sure it's related to a bad ROM in that slot. It's just really strange that ROMs that were working just fine before in any slot are now causing loops. I haven't had to Odin back to stock or anything, but I'm considering doing that just to get back to a clean base. It just seems unnecessary since my stock slot is still 100% functional. No signal drops, all wifi and bluetooth connections work flawlessly, etc.
I'm usually the guy that scours these forums until I find a solution, but this problem is just plain weird. As you can see from my post count, this is the first time I've thrown up my hands and asked for help. I'm not even sure there is anything really broken. It could very easily be something stupid I have or haven't done. It's just frustrating when I flash a ROM that I've verified the MD5 on, and I know for a fact has worked previously. I'll keep plugging away at it and post back if I figure out what's going on. Thanks again!
@remedee If I were u..... Follow my thread to go back to stock MK2 http://forum.xda-developers.com/showthread.php?t=2621279 check post #2 for guide on how to. After u got fresh MK2 firmware ..... root it.... install safestrap v3.71 and then create rom slot 1 first to see if the rom stable enough ....If it does then make your rom slot 1 back up .....then wipe your stock slot..... restore your rom slot 1 back up to stock slot or follow @guut13 instruction noted on every compatible rom lists from his thread. ..... Goodluck....:good:
Swyped From MK2 Dark Venom SS Edition
remedee said:
Thankfully I don't think I've had any truly bad flashes that resulted in a brick, or even a partial brick. My stock slot is running a custom (Darthstalker) ROM that is still fully functional through all of this other testing. I do have backups of my original stock config, as well as a recent backup of the DS ROM in the stock slot, so I'm not sure it's related to a bad ROM in that slot. It's just really strange that ROMs that were working just fine before in any slot are now causing loops. I haven't had to Odin back to stock or anything, but I'm considering doing that just to get back to a clean base. It just seems unnecessary since my stock slot is still 100% functional. No signal drops, all wifi and bluetooth connections work flawlessly, etc.
I'm usually the guy that scours these forums until I find a solution, but this problem is just plain weird. As you can see from my post count, this is the first time I've thrown up my hands and asked for help. I'm not even sure there is anything really broken. It could very easily be something stupid I have or haven't done. It's just frustrating when I flash a ROM that I've verified the MD5 on, and I know for a fact has worked previously. I'll keep plugging away at it and post back if I figure out what's going on. Thanks again!
Click to expand...
Click to collapse
Just to be clear, I didn't necessarily mean bricked when I said cooked, but kind of. I tested a bunch of ROMs for my threads. If i flashed one that didn't work, my phone would usually boot loop...
samsung logo, safestrap menu, black screen, reboot, samsung logo, safestrap menu, black screen, reboot, and so on...
If I stopped the boot loop by going back into safestrap, no matter how many times I wiped or which ever ROM I flashed next (even known working ones), I always went back into a boot loop after rebooting. Only thing that worked was odin back to stock. (Can't remember if I tried restoring, though.)
ROM slot was different. Deleting it and recreating was all it took. That's why I learned my lesson and just test new roms on ROM slot first.
remedee said:
Thanks for the reply. I've read through quite a few of the threads for the individual ROMs, but unfortunately the issue isn't related to any one specific ROM. I do have the compatibility pack and modules for HyperDrive and I was able to successfully get that installed previously. I was using that as an example of a ROM that worked before with this same configuration, which is why it's bugging me. I'll wipe out the existing slot 1 and give it another go, making sure I flash those as well. Unfortunately that doesn't explain why SHOstock (which I tested extensively before), and others go into a boot loop as well.
The only thing I can think of is perhaps I'm not wiping properly. So far, whenever I attempt to install a new ROM, I create a new slot with the default size values, do a factory reset, install ROM and any module/kernel recommended with it, wipe cache, reboot. Not sure what else I could be doing wrong.
Click to expand...
Click to collapse
next time you try to flash one and it fails try making the data partition smaller. Had a guy pm me and couldn't get rom to boot and i had him do this and bam it booted right up. Worth a shot. Also i have switched phones i went to the nexus 5 and i am not as fresh with the s4 stuff as i was a few weeks ago. PM if you need any help
I still plan to Odin back to stock but I didn't have time tonight. I did however grab a ROM from the link provided by ted77usa (thanks man, I can't seem to figure out how to mention at the moment). The Wicked v10 ROM installed to a clean Slot 1. I know that DarthStalker installed using Aroma, and Wicked is one of the few that I've tested that also uses Aroma. I don't know if it makes a difference, but this is the first ROM to install without a boot loop since I started having trouble.
I'm also wondering if the fact that this ROM had never been installed before has anything to do with it. I'm going to back it up since it's functional, then wipe and try to reinstall just to see if I get a boot loop. Thanks again to everyone for all of the input.
Sorry for the delay in getting back on this. My toddler finds new and interesting ways of keeping me from my hobbies Just wanted to say thanks to @ted77usa @guut13 and @ddubz. I tried resizing the partition and that didn't seem to help. I ended up starting from scratch and everything seems to be running properly. I've got DarthStalker back in the stock slot, Wicked in slot 1 and Hyperdrive in slot 2. I'm quite certain it's overkill, but just knowing I can switch between them and tinker makes me happy. Thanks again for all the input. XDA is definitely an awesome community.
Hello all, I posted a similar topic a few days back, and cannot seem to find it. I fear it was deleted, but could be wrong. I only looked back a few pages in the history.
My problems have multiplied since that posting. I have nc4, when I bought my phone it was on there. Used towelroot and was able to root, download safestrap 3.75 and was able to add/delete slots, attempted to use hyperdrive, experienced a lot of weird things like my SMS would randomly not send, battery life was not spectacular,and just other misc things. IT seemed like I might have used a rom that could not be used properly for nc4. I then tried bajarom, which completely does not work for my phone, probably because it's nc2 and I didn't realize that?? Tried jellybeanz or whatever the exact name was, my phone won't even boot, says it successfully installed but sticks on the black screen.
Somehow over the past few days I managed to wipe my stock so I do not have the stock, thus I cannot go back.
I am sure I can find or maybe be directed to the stock firmware and reflash it.
I am not sure if it's possible but I'd really love to be able to get nc2, or if someone more knowledgable than myself could point out a solution for me, I would like to have a custom rom if theres one that would work properly on my phone.
Another confusion I have, with the nc4, am I able to use odin to flash a different radio, should I even bother? I would sincerely appreciate someone who would help clear some of this up for me, I'm pretty novice as you can see. Thanks in advance.
update
I guess my question is unclear. I really can use some help if anyone would be so obliged.
I am trying to use ADB to push the file over, it says access denied, I was previously rooted and verified as much. My issue is I need a way to send the roms over to my SD or my regular phone internal mem so I can at least load a rom. Currently my phone is bricked and I am just getting very upset, I really could use someone to give me a bit of guidance.
I opened the cmd with admin and it's still saying access denied. IS there a way to force the phone to open as a media device via cmd? That way I can edit sd card info and push on there what needs to go?
I am currently trying to find a way to get hyperdrive, or another rom over.
I have beanstowns rom on there, it appears as .zip yet when I try to install from safestrap I end up exploring the directory, as opposed to just being an option I can choose.
Baja is the same way, both are still on my sd, yet for whatever reason I cannot select them to install them.
Hope is not lost.
I think your initial problem was that you tried using rom slots. It specifies in the Safestrap OP that rom slots are only supported on NC2 bootloader. Since you are on the NC4 bootloader you cannot go backwards, however you can flash the NC2 kernel if you want to run a custom rom, you simply need to use the stock slot alone.
Since I know very little about ADB & Terminal CMD, I will try to give you directions to get up and running the way I know how.
First you'll need to reflash the stock NC4 tar via odin and reroot. Files can be found here.
Since you've flashed a couple different roms that have probably messed with the system settings I would do a factory reset before rerooting.
After you are up, running and rooted, follow the instructions here to get on the NC2 kernel.
Once you've completed these steps you will be on the NC4 bootloader with the NC2 kernel and be able to flash a custom rom in the stock rom slot. Only a NC2+ rom will function so make sure it is based on NC2/NC4 (i.e. jelly 'beans' will not run on NC2+ firmware as it is based on MJE).
kinstre11 said:
Hope is not lost.
I think your initial problem was that you tried using rom slots. It specifies in the Safestrap OP that rom slots are only supported on NC2 bootloader. Since you are on the NC4 bootloader you cannot go backwards, however you can flash the NC2 kernel if you want to run a custom rom, you simply need to use the stock slot alone.
Since I know very little about ADB & Terminal CMD, I will try to give you directions to get up and running the way I know how.
First you'll need to reflash the stock NC4 tar via odin and reroot. Files can be found here.
Since you've flashed a couple different roms that have probably messed with the system settings I would do a factory reset before rerooting.
After you are up, running and rooted, follow the instructions here to get on the NC2 kernel.
Once you've completed these steps you will be on the NC4 bootloader with the NC2 kernel and be able to flash a custom rom in the stock rom slot. Only a NC2+ rom will function so make sure it is based on NC2/NC4 (i.e. jelly 'beans' will not run on NC2+ firmware as it is based on MJE).
Click to expand...
Click to collapse
firstly, thank you so much for the reply.
I did flash nc2 kernal, but was confused when I still saw nc4 in the about section. I flashed with odin NC2_modem_kk.tar and nc2kernel.tar.
The issue I was having is with hyperdrive, and baja I had some serious issues, so I assumed it was because I was using them incorrectly, ie didn't install one of the above files correctly, or did something else wrong in the process. Just for example, with hyperdrive, my sms would just stop sending/receiving/ double sending. My sim card was not being recognized. And a whole lot of other issues.. So I kept messing around and now im at a point where nothing boots up, I cannot reflash, and I'm just stuck.
I will follow your link and attempt to do as you said, will wipe, and then will try again.
deindichter said:
firstly, thank you so much for the reply.
I did flash nc2 kernal, but was confused when I still saw nc4 in the about section. I flashed with odin NC2_modem_kk.tar and nc2kernel.tar.
The issue I was having is with hyperdrive, and baja I had some serious issues, so I assumed it was because I was using them incorrectly, ie didn't install one of the above files correctly, or did something else wrong in the process. Just for example, with hyperdrive, my sms would just stop sending/receiving/ double sending. My sim card was not being recognized. And a whole lot of other issues.. So I kept messing around and now im at a point where nothing boots up, I cannot reflash, and I'm just stuck.
I will follow your link and attempt to do as you said, will wipe, and then will try again.
Click to expand...
Click to collapse
Alright, I applied to nc4 and did a factory reset, made sure all my slots were deleted (had 2). Then factory reset and rebooted, saw safestrap, pressed continue, and i'm looking at a blank screen now as though there is nothing to boot to. I was under the impression factory reset would undo all and it has not.
Did I do something wrong, or am I missing something?
deindichter said:
Alright, I applied to nc4 and did a factory reset, made sure all my slots were deleted (had 2). Then factory reset and rebooted, saw safestrap, pressed continue, and i'm looking at a blank screen now as though there is nothing to boot to. I was under the impression factory reset would undo all and it has not.
Did I do something wrong, or am I missing something?
Click to expand...
Click to collapse
Did you already boot into download mode and flash the correct files through Odin? If so that should set your phone back to stock. Then you would have to re root.
fsolares said:
Did you already boot into download mode and flash the correct files through Odin? If so that should set your phone back to stock. Then you would have to re root.
Click to expand...
Click to collapse
I did and it did not boot me back into stock. I then found http://forum.xda-developers.com/showthread.php?t=1922461which led me to download the files directly from samsung.
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
deindichter said:
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
Click to expand...
Click to collapse
can u post the link from where u got the official partition table/modem/kernel on verizon website...
deindichter said:
After downloading the official partition table/ modem/ kernal from the verizon website I finally have this back to stock. LOL. wow. Thank you very much for helping, and working with me on this.
Click to expand...
Click to collapse
So are you good to go now?
moin786 said:
can u post the link from where u got the official partition table/modem/kernel on verizon website...
Click to expand...
Click to collapse
could you post where you found all this since im trying to get my phone back to stock.
Paulrybicki83 said:
could you post where you found all this since im trying to get my phone back to stock.
Click to expand...
Click to collapse
Seriously, just Google for the Samsung official firmware. It's on their site. Not Verizon.
Alright, so i soft bricked my phone is what the internet is telling me. the phone turns on but stops at the opening samsung screen with the unlock symbol on it. i can get into odin mode, and recovery, but i have a locked recovery. I went to flash a rom to my stock slot which is what the forum said to do so i did it. looking back it was pretty stupid, and now when i tried to recover my back up it came back with an error and then said there was no os system in my stock slot. i tried doing a recovery in rom slot 1 which it recovered but when i restarted my phone everytime it went into a boot loop. so now i have a very expensive paperweight. so my questions are one is there anyway that i could salvage my phone. two is there a way i could get it back to where i was with any of my recoveries that i have. i herd the odin method works but will it work for my phone? i tried the odin before but never could get it to work. also kies is out of the question because neither programs will recognize my phone.
oh yeah my phone. so the last thing i had running on it was the 4.4.2 update I337 NC1 would i have to flash the NC1 os or could i flash an earlier one because all i could find were the 4.2.2's and the NB1 flash.
tshaulis said:
Alright, so i soft bricked my phone is what the internet is telling me. the phone turns on but stops at the opening samsung screen with the unlock symbol on it. i can get into odin mode, and recovery, but i have a locked recovery. I went to flash a rom to my stock slot which is what the forum said to do so i did it. looking back it was pretty stupid, and now when i tried to recover my back up it came back with an error and then said there was no os system in my stock slot. i tried doing a recovery in rom slot 1 which it recovered but when i restarted my phone everytime it went into a boot loop. so now i have a very expensive paperweight. so my questions are one is there anyway that i could salvage my phone. two is there a way i could get it back to where i was with any of my recoveries that i have. i herd the odin method works but will it work for my phone? i tried the odin before but never could get it to work. also kies is out of the question because neither programs will recognize my phone.
oh yeah my phone. so the last thing i had running on it was the 4.4.2 update I337 NC1 would i have to flash the NC1 os or could i flash an earlier one because all i could find were the 4.2.2's and the NB1 flash.
Click to expand...
Click to collapse
1. As long as you can get into Odin mode, you're ok.
2. if you are on NB1 or NC1 base running safestrap 3.72, stock slot is the ONLY slot you can use. ROM slots do not work.
3. it's not really clear what you did to cause the boot loop, but lets get you back to stock...
Check out post 5 in my thread. If you follow these steps, you should be back to stock (and rooted with recovery, if you want) in no time.
http://forum.xda-developers.com/showthread.php?t=2616221
BTW - Post 2 has a list of ROMs that are safe to flash for safetrap users. Read the install notes first then follow the install instructions to install one of the ROMS.
guut13 said:
1. As long as you can get into Odin mode, you're ok.
2. if you are on NB1 or NC1 base running safestrap 3.72, stock slot is the ONLY slot you can use. ROM slots do not work.
3. it's not really clear what you did to cause the boot loop, but lets get you back to stock...
Check out post 5 in my thread. If you follow these steps, you should be back to stock (and rooted with recovery, if you want) in no time.
http://forum.xda-developers.com/showthread.php?t=2616221
BTW - Post 2 has a list of ROMs that are safe to flash for safetrap users. Read the install notes first then follow the install instructions to install one of the ROMS.
Click to expand...
Click to collapse
sir i will tell you that your a genius. its pretty cool to see the creator of the link you posted (which is you) being used on other sites. goes to show you really know what you are doing. for me well i thought i did, and wish i did. it might be awhile before i change roms again or at least until i get more knowledge.
ok so from my understanding safestrap is having difficulties being you and only flash in the stock slot. ok well what i did was flashed the hyperdrive rom (from your link) to the stock slot because in the hyperdrive forum it said only can flash on stock. so i did a full wipe on stock then flashed the hyperdrive and gapps. well my guess is when i did the full wipe it wiped the os. also i didn't grab the supporting modules for the rom so i didnt have wifi or service which made me try to restore from my nandroid and couldnt because it said error loading /system. then tried other things i thought would work and softbricked it so to that.
i think for newbies like myself its a lot of reading and well we could miss some things and screw things up. and plus samsung had to make different freakin models like the i337 or i9505 or the i9000 or something and everything has to be the exact same and perfect. but oh well. i am happy to tell you that my phone is fully restored and working from the day before all this happened. thanks again and sorry for the long message.
My Prior thread: https://forum.xda-developers.com/galaxy-s4-att/help/n00b-sgh-i337-running-original-kernel-4-t3850783
I obtained a stock MDL i337 S4 running 4.2.2 and following the instructions in the prior thread I rooted with TowelRoot and updated to Lollipop 5.0.1/ GoldenEye and I've had nothing but problems ever since, so much so that the phone has almost gotten me lost in Oakland and has made me late for work twice!
The phone freezes, sometimes randomly reboots, shuts down applications without reason or warning (LIKE MY ALARM CLOCK!!!), apps can freeze while in use (like Google Maps at a critical time!), it eats power like me at a Chinese buffet and runs hot sometimes, apps are slow to load or won't load (sucks when a call comes in. By the time I am able to answer it, the caller has hung up!), app updates hang, and more. I suspect that part of the issue is that the instructions I got for rooting it and installing a custom ROM were a bit different than those of the GoldenEYe dev (who abandoned his project years ago and no longer answers questions) but I'm not sure.
The first time I did the upgrade, it froze at the Samsung screen for almost 30 min and I had to start over. Then when it was complete the phone was almost unusable. I read that there were issues with SuperSU so I started uninstalling some of the dev apps (I really don't know what the hell I'm doing but was desperate) and when I disabled SuperSU and did clean up to switch to another superuser app" then thought I uninstalled it and all the problems seemed to go away. A few days later while doing something else in the play store, I find that SuperSU is running even though it no longer shows in my apps! So thinking something nefarious was going on, I uninstalled it via the play store and my phone was back to being hosed again. Ok, yes I'm an idiot and deserved that.
I go back to the beginning and started all over AGAIN, reinstall/upgrade but with a different kernel (thinking maybe that?, I tried leaving my apps and settings but that didn't take. Any clue how many times I've now configured my email and office tools? lol) and ended up with what I have now, ie the issues above. I thought about trying to just somehow go back to stock 4.2.2 then just finding the stock ATT Lollipop firmware and saying to hell with root but those instructions are not clear and most post links to the firmware are now dead (I REALLY don't want to brick my phone. I have no money for another and I need my phone for my job). I'd really like to go above Lollipop if at all possible but would be happy just to have GoldenEye work!
Does anyone have any idea what the heck is going on with my phone and how I fix it? This is a serious problem for me.
SGi337
Android 5.0.1
Baseband I337UCUAMDL
Kernel Ver: 3.4.0-S4-AELKerel-v4.3-LP [email protected] #36 Wed Apr 8 19:56:06 EEST 2015
Build number LRX22C.I9505XXUHOD7
Rom Ver: GOLDENEYE 53 XXUHOD7
Dev iB4STid
SuperSU PseudoPro (had Pro, didn't reinstall it the last time) is installed but disabled
ES Task Manager and ES File Manager
Titanium Backup Pro
And so we meet again! Okay so forget golden eye. What you should do is get ODIN for your PC. Then get the MDL firmware and flash it with ODIN by connect your phone to your PC. You might also need Samsung Kies for your PC for this as it has the drivers for your phone.
Once you're back on Android jelly bean, use towel root to root, install Loki, install clockwork mod or TWRP recovery (for TWRP go here https://forum.xda-developers.com/showthread.php?t=2262996 and for clockwork mod just use my guide again).
Then flash this:
https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
This will give you the latest stock Rom for your phone. It's from AT&T but has been modified to work with the MDL bootloader so it doesn't patch the Loki exploit.
Also remember that you need superSU installed or else you won't have any root management for your root apps.
Hi! lol
Any idea why this is happening? I'd really like to go to something like Marshmallow or the like but if stock is it, that will have to do.
I tried finding the MDL firmware but so far all the links are old dead ones. Have you seen anything more current?
StoneyJSG said:
And so we meet again! Okay so forget golden eye. What you should do is get ODIN for your PC. Then get the MDL firmware and flash it with ODIN by connect your phone to your PC. You might also need Samsung Kies for your PC for this as it has the drivers for your phone.
Once you're back on Android jelly bean, use towel root to root, install Loki, install clockwork mod or TWRP recovery (for TWRP go here https://forum.xda-developers.com/showthread.php?t=2262996 and for clockwork mod just use my guide again).
Then flash this:
https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
This will give you the latest stock Rom for your phone. It's from AT&T but has been modified to work with the MDL bootloader so it doesn't patch the Loki exploit.
Also remember that you need superSU installed or else you won't have any root management for your root apps.
Click to expand...
Click to collapse
I have no idea why golden eye is giving you issues. It works fine for me and you followed my guide just like I did. Anyway, you can goto marshmallow but it'll be AOSP based rather than touchwiz based so the look and feel will be way different than that of golden eye or any other stock Samsung ROM.
You can also just try going into clockwork mod and do a wipe (I forgot the sequence, it's wipe system, data, cache I THINK but it's in my guide on the order of how to do it) for a clean install of a ROM from there. This will eliminate the need for ODIN. You should however, keep ODIN on standby in case anything goes south you can go back to how the phone was when you first got it. I have the ODIN MDL firmware on a USB drive, let me find it over the weekend and upload it to my Google drive and will link you to it.
SilkRoadDog said:
I tried finding the MDL firmware but so far all the links are old dead ones. Have you seen anything more current?
Click to expand...
Click to collapse
Hey dude, here's the link to the MDL firmware for ODIN off my Google drive: https://drive.google.com/file/d/1ZXv9FAcDbfkbFZzh078SSMZ85jbMVPSx/view?usp=drivesdk
StoneyJSG said:
Hey dude, here's the link to the MDL firmware for ODIN off my Google drive: https://drive.google.com/file/d/1ZXv9FAcDbfkbFZzh078SSMZ85jbMVPSx/view?usp=drivesdk
Click to expand...
Click to collapse
Well after putting up with the phone issues for 2 months, I reset everything following your instructions to the best of my abilities (except couldn't get towelroot to load so went with another). Let's see how this works! lol
Your instructions say "SuperSU will kill the evil KNOX for you." What is that and how do I do this?
SilkRoadDog said:
Your instructions say "SuperSU will kill the evil KNOX for you." What is that and how do I do this?
Click to expand...
Click to collapse
Once rooted, goto the Google play store and download the SuperSU app, open it and it will ask you some stuff then do the rest. Towel root needs internet access to work. I was starting to have issues with golden eye rom off and on until I flashed the OC3 modem, you may wanna try that after you get back to golden eye.
There's also another ROM on here called i337_OC3_stock_rooted_rom(MDL) , you may want to try it out as it's 100% stock and hasn't been modified like golden eye rom has. I am not sure it works with clock work mod recovery so you might need TWRP recovery for it.