Related
Anything new with getting around this MF3 nonsense? I'm constantly running out of storage space and am about to just sell this phone and be done with it.
whitesox311 said:
Anything new with getting around this MF3 nonsense? I'm constantly running out of storage space and am about to just sell this phone and be done with it.
Click to expand...
Click to collapse
I'm new to the s4 party, so I am not sure how recent it is, but fairly recently the stock images leaked and are flashable via odin, so you can go ahead and wipe and install whatever compatible you want right to the stock slot. This lets you use the full space instead of small slots and still be able to go back to stock later.
failedjedi said:
I'm new to the s4 party, so I am not sure how recent it is, but fairly recently the stock images leaked and are flashable via odin, so you can go ahead and wipe and install whatever compatible you want right to the stock slot. This lets you use the full space instead of small slots and still be able to go back to stock later.
Click to expand...
Click to collapse
Really? Nice! Still not nearly as cool as running AOSP roms, but better than what I'm working with now. Thanks for the head's up!
failedjedi said:
I'm new to the s4 party, so I am not sure how recent it is, but fairly recently the stock images leaked and are flashable via odin, so you can go ahead and wipe and install whatever compatible you want right to the stock slot. This lets you use the full space instead of small slots and still be able to go back to stock later.
Click to expand...
Click to collapse
NOPE NOT TRUE.. IF you wipe stock slot..and install custom rom it does not boot. PERIOD!!!!!.. Someone needs ta come up with unlocking the bootloader Like 3 months ago...GHOST!!!!
Sent from my SAMSUNG-SGH-I337 using Tapatalk
r1tesh said:
NOPE NOT TRUE.. IF you wipe stock slot..and install custom rom it does not boot. PERIOD!!!!!.. Someone needs ta come up with unlocking the bootloader Like 3 months ago...GHOST!!!!
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I have the 4.2.2 google play edition on stock slot. No other slots. Boots and is completely bug free.
Wow wamna tell us how its done..i am kn firmware mf3 then upgraded ta 4.3..so i am screwed..but others would like ur wisdom on this topic..
Sent from my SAMSUNG-SGH-I337 using Tapatalk
r1tesh said:
Wow wamna tell us how its done..i am kn firmware mf3 then upgraded ta 4.3..so i am screwed..but others would like ur wisdom on this topic..
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Well if you updated to MK2 via the OTA update your currently stuck with stock 4.3 right now. Hashcode (the creator of Safestrap) is working on a 4.3 version but it's unknown when / if it will released.
As for flashing to the stock slot in Safestrap it's this easy...
Use the MF3 Odin files to restore your phone to 100% stock via Odin. - Downloads --> MEGA - Mediafire
Root using jortex's MF3 root method.
Reboot
Install the latest version of Safestrap, and install the recovery.
Download a ROM confirmed to work in the stock slot and add the zip files to your SD card.
Download the MF3 Modules for Safestrap from here... and add them to your SD card.
Reboot into Safestrap
Inside Safestrap go to Wipe --> Advance Wipe --> Select Dalvik Cache, Data, Cache, and System. Do NOT select Micro SDcard.
Use the back arrow to return to the main Safestrap menu. IMPORTANT - Do NOT turn of your phone at this point or you will brick.
Select Install and navigate to your custom ROM's zip file. Proceed to flash it...
After the ROM is flashed do NOT reboot yet, instead go back to Install on the menu and install the MF3 modules.
Reboot, and hope for the best.
Basically any rom I try, will boot up to the Home screen and then before I can count to 7 reboot, and this will loop forever unless I shutdown and load the stock rooted rom. As long as I leave my phone off for a period of time the stock rom will work stably and be fine, if I try to go directly into the stock rom after trying any other apps will randomly crash and even the stock rom will be unstable. Often it will reboot randomly, although I will get more time with it before it does. Yes i am clearing Caches in between roms, no that does not make a difference. I'm not sure what i did wrong.
Here's how what I have done so far:
1. Odin flashed from MI9 to MJ7, now running N900VVRUBMJE
2. Rooted phone with Kingo (Installed Root Checker app made sure of rooted status)
3. installed safestrap
4. installed super SU on stock rom (and I install the super SU .zip along with any rom I have flashed)
5. set up safestrap so that the stock rom is on one of the backup slots and custom rom boots from the stock location (this is done so I can have the full amount of available memory on the custom rom.)
I have backups of everything.
Please help me I have been trying to get the Beanstown 106 rom to work on my phone but ANY rom I use (except stock) has the same issue get to home screen and reboot 5-7 seconds later. What did I miss?
MAsterOSkillio said:
Basically any rom I try, will boot up to the Home screen and then before I can count to 7 reboot, and this will loop forever unless I shutdown and load the stock rooted rom. As long as I leave my phone off for a period of time the stock rom will work stably and be fine, if I try to go directly into the stock rom after trying any other apps will randomly crash and even the stock rom will be unstable. Often it will reboot randomly, although I will get more time with it before it does. Yes i am clearing Caches in between roms, no that does not make a difference. I'm not sure what i did wrong.
Here's how what I have done so far:
1. Odin flashed from MI9 to MJ7, now running N900VVRUBMJE
2. Rooted phone with Kingo (Installed Root Checker app made sure of rooted status)
3. installed safestrap
4. installed super SU on stock rom (and I install the super SU .zip along with any rom I have flashed)
5. set up safestrap so that the stock rom is on one of the backup slots and custom rom boots from the stock location (this is done so I can have the full amount of available memory on the custom rom.)
I have backups of everything.
Please help me I have been trying to get the Beanstown 106 rom to work on my phone but ANY rom I use (except stock) has the same issue get to home screen and reboot 5-7 seconds later. What did I miss?
Click to expand...
Click to collapse
make sure you're running SS version 3.65 I think. If you're using 3.7x there are known problems. Too, try to re download Beans rom, you may have a bad download.
---------- Post added at 11:55 AM ---------- Previous post was at 11:53 AM ----------
drag&fly said:
make sure you're running SS version 3.65 I think. If you're using 3.7x there are known problems. Too, try to re download Beans rom, you may have a bad download.
Click to expand...
Click to collapse
You can also make a backup of your stock rom and then run beans in your stock slot. I keep my backup on my external SD.
drag&fly said:
make sure you're running SS version 3.65 I think. If you're using 3.7x there are known problems. Too, try to re download Beans rom, you may have a bad download.
---------- Post added at 11:55 AM ---------- Previous post was at 11:53 AM ----------
You can also make a backup of your stock rom and then run beans in your stock slot. I keep my backup on my external SD.
Click to expand...
Click to collapse
Thanks for the quick reply! ! Definatly 3.65 and I have tried deleting the rom and downloading again, from different computers even. I have been trying to run beans from the stock slot.
MAsterOSkillio said:
Thanks for the quick reply! ! Definatly 3.65 and I have tried deleting the rom and downloading again, from different computers even. I have been trying to run beans from the stock slot.
Click to expand...
Click to collapse
I'm sure someone with more knowledge will chime in soon. Patience Grasshoppa!
Tried a wipe from safestrap and it softbricked the phone, recovering with kies as we speak. I MUST have missed a step somewhere, because a wipe with safestrap should not cause bricking.
MAsterOSkillio said:
Tried a wipe from safestrap and it softbricked the phone, recovering with kies as we speak. I MUST have missed a step somewhere, because a wipe with safestrap should not cause bricking.
Click to expand...
Click to collapse
What kind of wipe? If you wipe everything from the stock slot, do not reboot recovery.
♢NoteIII♢
After the back to stock reflash with kies everything seems stable, I'm most of the way through the setup without a reboot yet!
MAsterOSkillio said:
After the back to stock reflash with kies everything seems stable, I'm most of the way through the setup without a reboot yet!
Click to expand...
Click to collapse
I would encourage you to leave the stock ROM in the stock slot and put dev ROMs in the other slots.
I'm not sure why that would matter unless Safestrap has an unintended dependency on the contents of /system beyond it's own interception toolkit. As it stands, the Safestrap "recovery" (not really a recovery at all - it is an application running on top of the stock kernel and stock ramdisk) needs to inject it's own interception toolkit onto whatever is in the "stock slot" - be that an actual stock ROM or a dev ROM.
I suppose that means that Safestrap needs to re-install itself after a flash to the stock slot occurs; perhaps there is a bug in there someplace.
good luck
Upgrading from Jelly Bean to KitKat is easy!
Disclaimer
As always, this carries a certain amount of risk so by using the guide below you agree not to hold me liable if your device turns into a very expensive paperweight (not at all likely but you have been warned! )
Prerequisites
Windows computer
You must be on a 4.3.X Jelly Bean (rooted stock or custom ROM)
You must have Safestrap installed
UrDroid Stock Rooted KitKat ROM.zip (Odexed or Deodexed) by @carl1961 (everyone go hit his Thanks button!)
ODIN.zip (download in second post)
First Steps
Download ODIN.zip & extract the .zip to your desktop.
Download UrDroid Stock Rooted KitKat ROM.zip to your internal SD Card by following the download links in the ROM’s original thread (found here).
Once downloaded, boot into Safestrap.
*IMPORTANT* Make sure you have deleted any extra ROM Slots you have created and that you have your STOCK slot activated!
In Safestrap main menu, click on the WIPE button and go ahead and “factory reset” your device (wipe data + cache) like you always do before flashing a ROM.
Once you have wiped data, navigate back to the INSTALL button in SafeStrap.
Navigate to the UrDroid ROM.zip that you saved to your SD Card and proceed to flash the ROM to your stock slot.
Once the ROM has successfully flashed - navigate back to Safestrap menu & choose REBOOT & then DOWNLOAD.
Your phone will reboot into Download Mode.
Now, open the file located inside of ODIN.zip labeled “Odin & needed files are here” on your desktop.
Click on and run Odin3 v3.09.exe.
On the right hand side of Odin you will see different buttons labeled PIT, BL, AP, CP.
Click on the PIT button and select HLTE_USA_ATT_32G.pit. Now select BL and choose BL_N900AUCECMGL.tar. Now continue to match AP with the AP file and CP with the CP file.
Once all 4 files have been inputted into Odin plug in your phone and click START.
Let Odin finish its magic then reboot your device.
Welcome to KitKat!!!
Next Steps
Now that you are on KK you need to sideload Safestrap v3.72.apk and install it to your device.
Once you’ve installed it go ahead and open it up and INSTALL Safestrap.
Once you have Safestrap installed it is important to note that you cannot mix Jelly Bean & KitKat ROMs with Safestrap….you must stick to KitKat based ROMs (it is possible this will change in the future...if it does I will update this post!)
Now that you are running rooted stock KitKat w/Safestrap feel free to flash whatever Custom ROM you'd like to try out!
Credits
@carl1961 - thank you for everything you do for the community!
Downloads
Download UrDroid Stock Rooted KitKat.zip
http://forum.xda-developers.com/showthread.php?t=2584994
Download ODIN.zip (includes all needed files + instructions)
http://goo.gl/GdJonL
*If you download please consider hitting the thanks button!
Thank you for your guide.
The following steps are not necessary:
[*]Once the ROM has successfully flashed, pull the battery out of the phone & put it back in (do not reboot).
[*]Once your battery is reinserted press and hold VOL Down & Power to boot into Download Mode.
Safestrap directly provides: Reboot --> Download.
SunnyOK said:
Thank you for your guide.
The following steps are not necessary:
[*]Once the ROM has successfully flashed, pull the battery out of the phone & put it back in (do not reboot).
[*]Once your battery is reinserted press and hold VOL Down & Power to boot into Download Mode.
Safestrap directly provides: Reboot --> Download.
Click to expand...
Click to collapse
OP updated to reflect this!!! Thanks for your help!
Sorry for the ignorance, but will this method keep my user data and root?
zewone said:
Sorry for the ignorance, but will this method keep my user data and root?
Click to expand...
Click to collapse
No problem! This is why this post is here. This method does not wipe your internal SD card but it does wipe user data!
Any feedback on this method?
Sent from my SAMSUNG-SM-N900A using Tapatalk
rawb123456 said:
Any feedback on this method?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
This is the same method as it always been just better explained. Feel free to sub any other KK ROM.zip you want!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Is still necessary to delete the JB safestrap (3.71), in order to use 3.72 safestrap effectively?
Sent from my Nexus 7 using XDA Premium 4 mobile app
dadymon53 said:
Is still necessary to delete the JB safestrap (3.71), in order to use 3.72 safestrap effectively?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you do a clean wipe in SafeStrap when you reboot into KK Safestrap will not be installed. You will need to sideload and install it.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Sorry for the basic question. But will this method trip knox?
Thanks
ast11 said:
Sorry for the basic question. But will this method trip knox?
Thanks
Click to expand...
Click to collapse
No sir it does not trip Knox.
Thanks for your method
I have a question...
I rooted my Note 3 using the de la Vega method,
Then I changed carrier from AT&T to Aio
Will any of my Aio phone settings affect your root method?
Thanks
Thanks, this procedure worked great!
Quick question though. After I install a rom into a SS slot. The activated rom doesn't see the existing internal sd card files. Instead the "sd card" folder appears to be from a brand new unused installation. However the stock rom and SS recovery still has access to all the old files.
Is this expected behavior or did I mess up somehow?
ast11 said:
Thanks, this procedure worked great!
Quick question though. After I install a rom into a SS slot. The activated rom doesn't see the existing internal sd card files. Instead the "sd card" folder appears to be from a brand new unused installation. However the stock rom and SS recovery still has access to all the old files.
Is this expected behavior or did I mess up somehow?
Click to expand...
Click to collapse
I am sorry but I do not understand. Could you clarify? When you say "After I install a rom into a SS slot"....does this mean you have already flashed to KK? If you have ROM Slots are not working correctly in Safestrap while on KK.
It's possible that has nothing to do with what you asked...let me know if I am off the mark.
T-mobile unlock
Will this work if I have an unlocked at&t phone on T-mobile's network?
Thanks
tropazr said:
I am sorry but I do not understand. Could you clarify? When you say "After I install a rom into a SS slot"....does this mean you have already flashed to KK? If you have ROM Slots are not working correctly in Safestrap while on KK.
It's possible that has nothing to do with what you asked...let me know if I am off the mark.
Click to expand...
Click to collapse
Yes I followed your guide and ended up with KK stock with safestrap.
And I didn't realize I have to install a custom rom onto the stock slot. I was able to create a new slot and install the rom and boot into it. but lot of things didn't work.
But I installed Dynamic Kat over stock now and it's working well and knox is still 0x0. Thanks again
I've had my Note 3 for about 2 weeks now, I rooted and installed SS on day one but haven't flashed anything yet. I wanna try this out but do I have to have a custom ROM downloaded besides UrDroid? I'm just asking because thats what the guy above me sounded like he had to do. Thanks!
KuRuPtIoN said:
I've had my Note 3 for about 2 weeks now, I rooted and installed SS on day one but haven't flashed anything yet. I wanna try this out but do I have to have a custom ROM downloaded besides UrDroid? I'm just asking because thats what the guy above me sounded like he had to do. Thanks!
Click to expand...
Click to collapse
Thanks for asking and I am glad you did. Since UrDroid is basically a stock KK ROM I feel like it is the best ROM to use this method with. This method WILL work with any other 4.4 based ROM....but I like the idea of flashing something that is based off stock to start with and then flashing anything else from there since stock is most likely to give us the fewest errors.
tropazr said:
Thanks for asking and I am glad you did. Since UrDroid is basically a stock KK ROM I feel like it is the best ROM to use this method with. This method WILL work with any other 4.4 based ROM....but I like the idea of flashing something that is based off stock to start with and then flashing anything else from there since stock is most likely to give us the fewest errors.
Click to expand...
Click to collapse
I flashed it successfully, I followed it step by step, word for word. Good write up, been running it now for a couple hours and haven't had any problems. Thanks!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
tomorrow i will be receiving my Galaxy S4 in the mail, and basically i just want to make sure i will be rooting this phone with the most recent and preferred method.
i found this guide from 2 different sticky threads "[HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2" and "Frequently Asked Questions"
http://forum.xda-developers.com/showthread.php?t=2297900
but i started to see thing different than what i'm used to on the GS3:
(1) "This will not work on Build Number I337UCUAMF3"
is this comparable to the bootloader on the GS3? kinda like how there's a different guide to root a GS3 on the MJB bootloader.
(1b) what version will come out of the box?
should i root it before even putting my SIM card in it so it doesn't have a chance to auto-update?
(2) CASUAL
it sounds like this is an all-in-one, do-it-all Windows application? so i won't need the use of Odin to flash any files?
(3) what's the preferred custom recovery?
i've been using CWM for so many years now, it's just my go-to custom recovery.
SOLVED, see my last post.
mrhomiec said:
tomorrow i will be receiving my Galaxy S4 in the mail, and basically i just want to make sure i will be rooting this phone with the most recent and preferred method.
i found this guide from 2 different sticky threads "[HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2" and "Frequently Asked Questions"
http://forum.xda-developers.com/showthread.php?t=2297900
but i started to see thing different than what i'm used to on the GS3:
(1) "This will not work on Build Number I337UCUAMF3"
is this comparable to the bootloader on the GS3? kinda like how there's a different guide to root a GS3 on the MJB bootloader.
(1b) what version will come out of the box?
should i root it before even putting my SIM card in it so it doesn't have a chance to auto-update?
(2) CASUAL
it sounds like this is an all-in-one, do-it-all Windows application? so i won't need the use of Odin to flash any files?
(3) what's the preferred custom recovery?
i've been using CWM for so many years now, it's just my go-to custom recovery.
Click to expand...
Click to collapse
Chances are you'll get an S4 with a newer firmware. This means you won't be able to use TWRP or CWM, and you can't run AOSP ROMs. You can still root and flash other Touchwiz ROMs.
1) Yes, that's exactly what it is in fact. Bootloaders MF3 and above do not support the only exploit we have to install AOSP ROMs.
1b) Like i said, probably a newer one. Check on the outside of the box and it will have a label somewhere about the software version. If it's not MDB or MDL then you can't use the exploit to get an AOSP ROM.
2) Yes, it is an AIO Windows app, but it won't work unless you get one on MDL or MDB again.
3) If you get the newer firmware, Safestrap is the only recovery, and Touchwiz ROMs are all that's compatible
If you want a better explanation of anything, PM me and I'll be glad to respond as soon as I finish the essay i should be typing at the moment.
so in short, MDB/MDL = awesome.
i really hope i get one of these then. i always flash CM on whatever phone i use.
if i do receive a phone that's MDB/MDL, i should NOT insert my SIM card, and NOT connect to wifi then? that way i can root first?
mrhomiec said:
so in short, MDB/MDL = awesome.
i really hope i get one of these then. i always flash CM on whatever phone i use.
if i do receive a phone that's MDB/MDL, i should NOT insert my SIM card, and NOT connect to wifi then? that way i can root first?
Click to expand...
Click to collapse
Exactly, do not let it connect. Just use CASUAL and then either use your root to disable the OTA updater or go straight to a ROM. Then just remember that if you ever have issues and need to flash stock firmware only flash the same and never a newer one.
aw man. just got the phone in, and it's already been updated.
came in on 4.4.2, I337UCUFNB1
found these threads:
http://forum.xda-developers.com/showthread.php?p=52167774
http://forum.xda-developers.com/showthread.php?t=2663545 (edit, upon more searching, this method seems the most mentioned/preferred)
and i'm wondering if i should even "root" this phone anymore. i feel like if/when a real root method comes out, i can root it then?
i guess the benefit of rooting now, would be to freeze/uninstall Samsung apps. also, would it be any easier to real root after sorta rooting?
edit, some more searching around, rooting right now (and with Safestrap Recovery installed) has a whole bunch of scenarios to be aware of. this is kinda overwhelming coming from the GS3 and Nexus phones/tablets.
edit, what are ROM slots? this sounds like dual-boots to me.
and also, since my phone came with NB1, what is the proper terminology for this situation? because i'm reading references like "NB1 users who took the OTA" and "NB1 users who started out there".
another edit! so i think i'm going to just root, and stop there, is that possible? or do i have to go one step further and install Safestrap Recovery?
i tried to follow the guide above (2nd link), and in Odin i got a FAIL message when i loaded the *.pit file to the PIT slot, and the *.md5 file to the AP slot.
mrhomiec said:
aw man. just got the phone in, and it's already been updated.
came in on 4.4.2, I337UCUFNB1
found these threads:
http://forum.xda-developers.com/showthread.php?p=52167774
http://forum.xda-developers.com/showthread.php?t=2663545 (edit, upon more searching, this method seems the most mentioned/preferred)
and i'm wondering if i should even "root" this phone anymore. i feel like if/when a real root method comes out, i can root it then?
i guess the benefit of rooting now, would be to freeze/uninstall Samsung apps. also, would it be any easier to real root after sorta rooting?
edit, some more searching around, rooting right now (and with Safestrap Recovery installed) has a whole bunch of scenarios to be aware of. this is kinda overwhelming coming from the GS3 and Nexus phones/tablets.
edit, what are ROM slots? this sounds like dual-boots to me.
and also, since my phone came with NB1, what is the proper terminology for this situation? because i'm reading references like "NB1 users who took the OTA" and "NB1 users who started out there".
another edit! so i think i'm going to just root, and stop there, is that possible? or do i have to go one step further and install Safestrap Recovery?
i tried to follow the guide above (2nd link), and in Odin i got a FAIL message when i loaded the *.pit file to the PIT slot, and the *.md5 file to the AP slot.
Click to expand...
Click to collapse
To root, you'll need to downgrade to mk2 with Odin. See the second post in this
http://forum.xda-developers.com/showthread.php?p=50667360
Then root using saferoot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
To root, you'll need to downgrade to mk2 with Odin. See the second post in this
http://forum.xda-developers.com/showthread.php?p=50667360
Then root using saferoot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.
mrhomiec said:
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.
Click to expand...
Click to collapse
Sorry man,I have you the wrong link. Use the all in one tar file from here http://forum.xda-developers.com/showthread.php?p=49687770
Sent from my Nexus 5 using XDA Free mobile app
mrhomiec said:
i tried following that guide, and i mentioned i got a FAIL message. i'm trying the other guide i linked to see if that method works.
Click to expand...
Click to collapse
The way most people follow on that thread is
1. Flash full NB1 post #2
2. Downgrade to MK2 post # 1
3. Root with safe root
4. Fix wife
5. Install safe strap
6 flash Tw rom of your preference.
7. Flash kernel if needed
8. Flash deadly venom magic tool.
9. Flash super su update.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
netomel said:
6 flash Tw rom of your preference.
7. Flash kernel if needed
8. Flash deadly venom magic tool.
9. Flash super su update.
Click to expand...
Click to collapse
flashing DVMT is optional. any modifications to the kernel will void his warranty (Knox 0x1). i'd advise looking into PurifieD or any 'stock' variant rom that does not require a custom kernel to be flashed, at least until your year of warranty goes by. Any post saying 'flashing period will void your warranty' is incorrect. On PurifieD with knox 0x0.
Rhymey said:
flashing DVMT is optional. any modifications to the kernel will void his warranty (Knox 0x1). i'd advise looking into PurifieD or any 'stock' variant rom that does not require a custom kernel to be flashed, at least until your year of warranty goes by. Any post saying 'flashing period will void your warranty' is incorrect. On PurifieD with knox 0x0.
Click to expand...
Click to collapse
We can't flash custom kernels on kit kat stock anyway.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
netomel said:
We can't flash custom kernels on kit kat stock anyway. I flashed deadly venom and knox still intouched.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
i am totally lost right now. i finally got this guide to work:
http://forum.xda-developers.com/showthread.php?t=2663545
(i was being dumb, and i forgot to put the phone into Download Mode for Odin)
now, i'm having a problem with the last step...
1. Download all three files above
2. Open ODIN3v3.09
3. Load both Pit and AP together to corerct slot ( Pit >>PIT SLOT.....AP>>PDA SLOT ) and hit start.....
5. When is done....reboot to stock recovery and choose Full Wipe/Factory Reset.
6. Re-Root using Saferoot Method
7. Re-install Safestrap-v3.71
8. Try restoring your back up from safestrap recovery....CONFIRMED WORK...
9. Special Thanks to @Michael3214 @rebel1699 @Maribou @dolph8886 @Surge1223 @jeboo for his bypasslkm exploit and others that help to get WiFi Fixed....
Click to expand...
Click to collapse
Flash in Safe Strap then reboot open universal init.d toggle on then press nb1wififix then press the play icon on the top right grant su. After that you'll have wifi on boot.
https://mega.co.nz/#!dct3ALRT!e81l_V...LaYu_yKvCYeHhg
Click to expand...
Click to collapse
Code:
adb push bypasslkm /data/local/tmp
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm
i cannot get wifi to work on the phone, and also, LTE/data is nowhere to be seen as well, and i'm hoping if i get the wifi fixed, it'll fix the data part too. i tried to flash the bypasslkm.zip via Safestrap Recovery, and it said it was successfully flashed, but still no wifi.
OR, i'm not sure if i did this all backwards. i received the phone today, and instead of putting my SIM card in right away, i booted up the phone, didn't connect to wifi, and attempted this whole rooting process.
then, i can't apply the update.zip for some reason with these instructions...
1. U need Samsung USB driver install to your PC ......Install SAMSUNG KIES and plug your phone, it will install latest driver for your phone....
2. Make sure u unable USB debugging mode on ur phone.....go to menu>settings>more> it should be on top of about device
( Developer options ) but if u dont have it go to about device and click build number 5 time....so that will unable developer options and CHECK USB DEBUGGING.
3. Make sure u have latest ADB ( Android Debugging Bridge ) version 1.0.31.... ANDROID SDK
4. IF you like to update to NB1 coming from MK2 ....Reboot to recovery>>>Apply Update From ADB....( MAKE SURE U DOWNLOAD update.zip AND PLACE IT INSIDE YOUR SD CARD)
5. Go to your PC >>> ADB folder >>> Shift+Right Click >>> Open Command Window Here
Click to expand...
Click to collapse
Code:
adb devices
adb sideload update.zip
i get this error...
* cannot read 'update.zip' *
mrhomiec said:
i am totally lost right now. i finally got this guide to work:
http://forum.xda-developers.com/showthread.php?t=2663545
(i was being dumb, and i forgot to put the phone into Download Mode for Odin)
Click to expand...
Click to collapse
Hi there! If you have safestrap installed and you still have root on whatever you're currently on, please update to 3.72 (if you haven't already) found here (click), and flash the stock rooted NC1 100% rom via Safestrap over your stock slot found here. This [should] fix your issues 100%. If not, scroll down to where it has the NC1 modem and flash that too.
Rhymey said:
Hi there! If you have safestrap installed and you still have root on whatever you're currently on, please update to 3.72 (if you haven't already) found here (click), and flash the stock rooted NC1 100% rom via Safestrap over your stock slot found here. This [should] fix your issues 100%. If not, scroll down to where it has the NC1 modem and flash that too.
Click to expand...
Click to collapse
i am on Safestrap Recovery 3.72, and i'm downloading that 100% ROM right now.
so i don't need to worry about the "update.zip" or the "bypasslkm.zip" files anymore?
just flash this ROM via Safestrap Recovery and i'm good to go?
back to my original post then, so i'm used to using CWM as a custom recovery, do i follow the usual steps with Safestrap?
* wipe data/factory reset
* wipe cache
* wipe dalvik cache
* flash ROM
* reboot
mrhomiec said:
i am on Safestrap Recovery 3.72, and i'm downloading that 100% ROM right now.
so i don't need to worry about the "update.zip" or the "bypasslkm.zip" files anymore?
just flash this ROM via Safestrap Recovery and i'm good to go?
back to my original post then, so i'm used to using CWM as a custom recovery, do i follow the usual steps with Safestrap?
* wipe data/factory reset
* wipe cache
* wipe dalvik cache
* flash ROM
* reboot
Click to expand...
Click to collapse
Yup, you got it. Go into advanced wipe on Safestrap and tick all of those. I never bothered with either of those zips. The only thing you might need to do is reflash SuperSU, but I never had an issue using the stock rom, just custom ones. SuperSU DL here.
Rhymey said:
Yup, you got it. Go into advanced wipe on Safestrap and tick all of those. I never bothered with either of those zips. The only thing you might need to do is reflash SuperSU, but I never had an issue using the stock rom, just custom ones. SuperSU DL here.
Click to expand...
Click to collapse
i found a link somewhere (and i forgot where no with how many tabs i had open originally), for a version of "UPDATE-SuperSU-v1.93.zip", but i downloaded the v1.89 from your link anyways (just in case).
the 100% ROM is still downloading, and i noticed something, you said to flash the NC1 modem if i continued to have problems, but i didn't see a mention of that in the link you provided. there's a kernel link if that's what you meant.
mrhomiec said:
i found a link somewhere (and i forgot where no with how many tabs i had open originally), for a version of "UPDATE-SuperSU-v1.93.zip", but i downloaded the v1.89 from your link anyways (just in case).
the 100% ROM is still downloading, and i noticed something, you said to flash the NC1 modem if i continued to have problems, but i didn't see a mention of that in the link you provided. there's a kernel link if that's what you meant.
Click to expand...
Click to collapse
Oh, guh. You're gonna need that kernel too. It's samsung signed so no voiding there. Modem here, just in case.
wipe everything except ext sd > flash rom > download mode, flash kernel in AP slot > boot, see if wifi works. If not, go flash the modem.
Rhymey said:
Oh, guh. You're gonna need that kernel too. It's samsung signed so no voiding there. Modem here, just in case.
wipe everything except ext sd > flash rom > download mode, flash kernel in AP slot > boot, see if wifi works. If not, go flash the modem.
Click to expand...
Click to collapse
looks like i'm good to go! thank you! :highfive:
i am on 4.4.2, baseband NC1, build NC1, LTE works, wifi works.
only took me 6 hours. :victory:
mrhomiec said:
looks like i'm good to go! thank you! :highfive:
i am on 4.4.2, baseband NC1, build NC1, LTE works, wifi works.
only took me 6 hours. :victory:
Click to expand...
Click to collapse
good to hear! if you have any issues with root just reflash SuperSU in safestrap. you can also jump around on TouchWiz roms now if you want to, but don't let any of them touch your kernel. And if you do, you'll need to flash an AT&T wifi module found here to get wifi working, and a build.prop to get LTE working found here. Have fun!
i think i'ma stay on this 100% ROM. i don't want to screw anything up. everything about rooting this phone is wayyyy out of my comfort zone. all the years of rooting i've done up until now was pretty much the same steps on different devices.
with that, i figure my last post should summarize this adventure.
basically, if you're in the same situation as me, getting a brand new Galaxy S4, automatically updated to 4.4.2 (NB1), here is what i went through. please see the original threads for all the download links.
NB1►DOWNGRADE★UPDATE◄MK2 ★ NB1 FULL ODIN ★ Apr.24.2014 said:
http://forum.xda-developers.com/showthread.php?t=2663545
1. Download all three files above
2. Open ODIN3v3.09
2b. put phone into Download Mode (from a shut down state, hold the Volume Down + Home Button + Power Button to start up)
3. Load both Pit and AP together to corerct slot ( Pit >>PIT SLOT.....AP>>PDA SLOT ) and hit start.....
4. (i don't know where step 4 is)
5. When is done....reboot to stock recovery and choose Full Wipe/Factory Reset.
5b. phone may freeze at the ATT screen, i left it alone for a good few minutes. then i took the chance to power down via holding Power Button, then putting the phone into stock recovery (hold the Volume Up + Home Button + Power Button).
6. Re-Root using Saferoot Method (not really re-rooting since this is a new phone, see below)
7. Re-install Safestrap-v3.71 (and not really re-installing either, also see below)
8. Try restoring your back up from safestrap recovery....CONFIRMED WORK...
8b. i skipped step 8.
9. Special Thanks to @Michael3214 @rebel1699 @Maribou @dolph8886 @Surge1223 @jeboo for his bypasslkm exploit and others that help to get WiFi Fixed....
9b. i skipped step 9 too.
10. download custom ROM, a kernel, and follow directions here:
http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
10b. and if needed, download modem here:
http://forum.xda-developers.com/showpost.php?p=52167761&postcount=2
11. and DONE, you should be on 4.4.2 again, but this time on NC1.
Click to expand...
Click to collapse
ROOT Saferoot: Root for VRUEMJ7 said:
http://forum.xda-developers.com/showthread.php?t=2565758
Step 1 - setting up the USB drivers
Before you try using this rooting program, you'll need to have the USB drivers installed for your phone.
The easiest way to do this is to install Samsung Kies (Kies 3, fyi). If Kies sees your phone, you're OK for the drivers.
If you don't have the drivers working, the root installer will hang at "waiting for device..."
Step 2 - Enable USB Debugging
The second thing you must do is to enable USB debugging on your phone. Go to "Settings", "More...", then "Developer Options".
If "Developer Options" doesn't appear, then you'll need to enable it - go to "Settings", "More", "About Phone". Scroll down so the "Build Number" is visible, then tap on that several times until developer mode is enabled.
In Developer Options, make sure "USB Debugging" is checkmarked.
Step 3 - Enable USB ADB Access
Make sure that your computer is allowed to use USB debugging on your phone. To do this, unplug your phone (from the phone end, not the computer end) and unlock it. Then, plug in the USB cable back into the phone.
If you see an "Alllow USB debugging?" window pop up, tap on the "Always allow from this computer" to check it, then tap OK.
If you don't see that popup, it's OK, you should be OK to proceed.
That's it for the phone.
Step 4 - Unzip the saferoot.zip
Then you need to unpack the attached ZIP file somewhere onto your PC.
You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
Step 5 - Root your phone
Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
The first thing that the install script will ask you is whether or not to install Busybox. Busybox is a program that provides a fairly extensive set of Linux shell utilities that a Unix user would expect to see. If you're not going to be using the shell (terminal emulator or adb shell) then you may not want to install Busybox. You may, however, find that some root-required utilities assume that Busybox is installed.
If SuperSU asks you to update the su binary, choose the "Normal" method.
If SuperSU asks you about disabling Knox, allow it.
This exploit will NOT set the Knox Warranty Void flag. It will set the "Custom" flag, but that's nothing to worry about.
While you're running this, you'll need to keep the phone awake and watch both the computer running the rooting script and your phone.
You shouldn't unplug the phone unless you're prompted by the rooting script. Leave it connected until it's done.
Click to expand...
Click to collapse
RECOVERY LOCKED Safestrap Recovery v3.71/v3.72 2014-04-02 KK Beta said:
http://forum.xda-developers.com/showthread.php?t=2448925
1. Requirement: Root
2. Requirement: Allow APK install from Unknown Sources
3. Download the Safestrap APK
4. Find the APK using a Filemanager tool and open it on your device, then click "Install".
5. (If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this
message.)
6. Once installed, open up the Safestrap application as you would any other app.
7. Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
8. Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
9. From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap
10. Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
(this part was pretty straight forward)
Click to expand...
Click to collapse
Ok, after my last attempt to follow the instructions and spending over a full day with a bricked phone, I don't trust myself to do it again.
But I refuse to let the bloatware have its way...
So if someone can work me through the process to installing an easy, basic ROM I would highly appreciate it.
My phone is a Samsung Galaxy s4. i337. AT&T service, and it's on stock right now. 4.4.2. That's all I can tell you, I think it's Mk2 but I'd like to be able to find a way to MAKE SURE, before I screw anything up.
I have Odin, and I'm about to root my phone. If anyone will help me I'd greatly appreciate it!
i don't think you need odin anymore since towel root. i'm fairly certain it is just root, install safestrap, flash rom, flash root and carrier modules enjoy. goldeneye is a really nice rom for these phones with all the bloat removed and a few nice tweaks and addons.
exactly what i did last time, i flashed the new goldeneye with safestrap and it was brick city for 24 hours...
everything went fine and then it went into a bootloop when it tried to restart
First thing I'd do is read through this more than once http://forum.xda-developers.com/showthread.php?p=53758227
Then I'd update to nc1 firmware, root with towelroot, then install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
First thing I'd do is read through this more than once http://forum.xda-developers.com/showthread.php?p=53758227
Then I'd update to nc1 firmware, root with towelroot, then install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
alright thanks
is there no way to just upgrade from where I am now? really would take an inferior rom over having to upgrade firmware before I...upgrade firmware.....
also how do I tell for sure what I'm on now?
Damani311 said:
alright thanks
is there no way to just upgrade from where I am now? really would take an inferior rom over having to upgrade firmware before I...upgrade firmware.....
also how do I tell for sure what I'm on now?
Click to expand...
Click to collapse
Go into settings, about phone. Look at your build number, what are the last three characters?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Go into settings, about phone. Look at your build number, what are the last three characters?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nb1
sweet
recommendations?
Damani311 said:
nb1
sweet
recommendations?
Click to expand...
Click to collapse
I'd ota to nc1. Then you can use towel root to root
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'd ota to nc1. Then you can use towel root to root
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Damani311-
You're on NB1 stock ROM, but I bet your baseband is actually NC1, based on the description here and in our PMs about your current status.
Like JD said, you can go into the phone's settings, and see if it takes the OTA update to NC1. That's the easiest way to get there. Alternatively, you can download the NC1 update zip file (from here) and flash it in the stock recovery. You get into stock recovery by starting with power off, and doing a power/home/upvolume start up. In there, there are options to install update from SD card. See the All things ATT & related links for the details. It's handy to have that NC1 updater zip. It's just an update that needs to be applied on top of NB1... it's not a replacement for starting with NB1.
Then, root with towel root. Install SuperSU from play store and let it disable knox. (may need to reboot phone after installing SuperSU if it hangs). Install SELinux Mode Changer from play store and set to permissive. Install SafeSTrap (from here). Note, there seems to be a zip file with lots of these goodies pre-included as a variant of the NC1 zip, at the same location quoted above. I haven't used that version, but it's probably fine.
Boot to safestrap. Very important: THOROUGHLY WIPE THE SYSTEM BEFORE FLASHING THE ROM. This means go into advanced wipe and wipe everything but the external SD card. Some folks say do it three times... seems to me there's a problem if doing it once doesn't work...
Then while still in safestrap recovery flash the GoldenEye ROM to the stock slot (our version of Safestrap only supports the stock slot). When it flashes, it brings up the Aroma installer. Choose the ATT / Safestrap options. When it finishes DO NOT DO NOT!! reboot. Exit the installer without letting it reboot and go back to safestrap. Some people recommend wiping the cache/dalvik caches again after flashing the rom (but of course you wouldn't wipe system at this point!).
While still in SafeStrap recovery:
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip (from here) . You could also manually enter the APN info (from the All Things ATT 1st post) but it is unclear to me whether GoldenEye properly identifies the phone build.prop entries with everything needed to be able to download all the I337 apps. I used the zip file and everything worked out great.
That's the overview. Detailed instructions are in the various threads. It sounds awfully complex but once you've done it a few times it all makes sense and is easy. But forgetting to do the wipes, or omitting SuperSu or any of the little details can cause a failure.
Takes ~5-10 mins for first boot, as I recall. I was nervous when it took so long. I left it, started cooking dinner, came back in a bit, it was done.
Good luck. Let us know how it turns out.
Frankenscript said:
Damani311-
You're on NB1 stock ROM, but I bet your baseband is actually NC1, based on the description here and in our PMs about your current status.
Like JD said, you can go into the phone's settings, and see if it takes the OTA update to NC1. That's the easiest way to get there. Alternatively, you can download the NC1 update zip file (from here) and flash it in the stock recovery. You get into stock recovery by starting with power off, and doing a power/home/upvolume start up. In there, there are options to install update from SD card. See the All things ATT & related links for the details. It's handy to have that NC1 updater zip. It's just an update that needs to be applied on top of NB1... it's not a replacement for starting with NB1.
Then, root with towel root. Install SuperSU from play store and let it disable knox. (may need to reboot phone after installing SuperSU if it hangs). Install SELinux Mode Changer from play store and set to permissive. Install SafeSTrap (from here). Note, there seems to be a zip file with lots of these goodies pre-included as a variant of the NC1 zip, at the same location quoted above. I haven't used that version, but it's probably fine.
Boot to safestrap. Very important: THOROUGHLY WIPE THE SYSTEM BEFORE FLASHING THE ROM. This means go into advanced wipe and wipe everything but the external SD card. Some folks say do it three times... seems to me there's a problem if doing it once doesn't work...
Then while still in safestrap recovery flash the GoldenEye ROM. When it flashes, it brings up the Aroma installer. Choose the ATT / Safestrap options. When it finishes DO NOT DO NOT!! reboot. Exit the installer without letting it reboot and go back to safestrap. Some people recommend wiping the cache/dalvik caches again after flashing the rom (but of course you wouldn't wipe system at this point!).
While still in SafeStrap recovery:
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip (from here) . You could also manually enter the APN info (from the All Things ATT 1st post) but it is unclear to me whether GoldenEye properly identifies the phone build.prop entries with everything needed to be able to download all the I337 apps. I used the zip file and everything worked out great.
That's the overview. Detailed instructions are in the various threads. It sounds awfully complex but once you've done it a few times it all makes sense and is easy. But forgetting to do the wipes, or omitting SuperSu or any of the little details can cause a failure.
Takes ~5-10 mins for first boot, as I recall. I was nervous when it took so long. I left it, started cooking dinner, came back in a bit, it was done.
Good luck. Let us know how it turns out.
Click to expand...
Click to collapse
wow awesome dude thanks a ton!
got to the part after installing safestrap, where it's time for goldeneye
which version of the rom should i use? the newest one got me in big trouble last time?
and so I'm going to need 4 zip files on my phone before i flash ROM?
Flash Goldeneye
-Flash SuperSU.zip file. (from here)
-Then flash the NC1 modem zip file (from here).
-Finally flash the I337 build.prop/APN zip
?
If so i'll proceed.....thanks again
I'm using Golden Eye v36. However, I've seen folks saying v38 (current) is good too... not sure where the problem cropped up with your last attempt so I can't speculate what the problem was.
And you're right, there should be 4 zip files on your SD card. The ROM, SuperSU, NC1 module, and the ATT APN/BuildProp file, which may not be necessary but worked fine for me.
alright looks like I'm up and running! wifi doesnt work, I think that's the only issue I can detect so far.........
WiFi fail usually fixed by flashing module matching your baseband. If nc1 module doesn't fix it, try nb1.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Frankenscript said:
WiFi fail usually fixed by flashing module matching your baseband. If nc1 module doesn't fix it, try nb1.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
i was hoping that was it, but it didn't get it....shoot
thanks for helping me out here
i flashed the jfleatt nb1 modules, btw
I'm out of ideas, sorry! Maybe start a thread about module not restoring WiFi after flash. My one relevant data point is that once, instead of Odin NB1 then flash NC1 update, I odined the rootable NB1. After that I did safestrap and flashed a ROM plus modules. I was never able to get WiFi no matter what I flashed. Odined back to regular NB1 then did NC1 update. Flashed ROM and modules again... Success. I assume kernel (locked on nc1 for me) has to interact with ROM and module. Improper match causes fail. Are you certain of what baseband you have?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Did you do the Selinux thingy--:good:
rugmankc said:
Did you do the Selinux thingy--:good:
Click to expand...
Click to collapse
Damani311,
Were you able to sort out the WiFi? Poking around the internet it does seem like permission issues are often at root of it, and the Selinux Mode Changer mentioned above (set to permissive) might be the solution.
Good luck! :good:
I think he is sorted based on posts on other threads. Maybe he will let us know--:good:
In just a couple of words, here's a basic overview of the ROM-flashing process:
- Root using Towelroot
- Install SuperSU
- Install Safestrap
- Download ROM
- Download modules
- Flash both
- Reboot
- Enjoy
Just make sure that whatever firmware you're on matches the ROM and modules (ex. NB1 users flash NB1 ROMs or MK2 ROMs and NB1 modules)
Best of luck! :good::good::good:
Appreciate your reply, but think OP is sorted and never came back--