I rooted my Note3 when an exploit first became available using RootDeLaVega. I haven't touched it since as I was waiting for the custom ROMs to roll out. I'm ready for Beans, but I want to be sure I'm going from rooted stock(no OTA's taken)...to upgraded Baseband(currently on M19)...to safestrap...to Beans.
Correct me if I'm wrong, but from what I've read I must do the following:
1. Use method 2 here: http://forum.xda-developers.com/showthread.php?t=2528707
2. Use Kingo to get root again.
3. Install safestrap: http://forum.xda-developers.com/showthread.php?t=2528707
Use Beta or Stable here?
4. Download and flash Beans to an open slot after making a backup.
I miss anything? Thanks.
cooch said:
I rooted my Note3 when an exploit first became available using RootDeLaVega. I haven't touched it since as I was waiting for the custom ROMs to roll out. I'm ready for Beans, but I want to be sure I'm going from rooted stock(no OTA's taken)...to upgraded Baseband(currently on M19)...to safestrap...to Beans.
Correct me if I'm wrong, but from what I've read I must do the following:
1. Use method 2 here: http://forum.xda-developers.com/showthread.php?t=2528707
2. Use Kingo to get root again.
3. Install safestrap: http://forum.xda-developers.com/showthread.php?t=2528707
Use Beta or Stable here?
4. Download and flash Beans to an open slot after making a backup.
I miss anything? Thanks.
Click to expand...
Click to collapse
1. Use method 2 only,download ODIN 3.09 and MJE Firmware Full Stock ROM 1.3 GB, Boot into Stock Recovery using Vol Up+Home+Power Button, Wipe Factory Reset/Data & Wipe Cache Partition, Reboot the device, as soon as screen goes black press Vol Down+Home Button to enter Download mode and connect the device to PC...then flash the MJE firmware...
2. After flashing boot again into Stock Recovery using Vol Up+Home+Power Button, Wipe Factory Reset/Data & Wipe Cache Partition
3. Use Kingo to root the device and make sure that Screen Display time is set to 10 Minutes..because u have to accept some confirmation while Kingo is rooting the device.
4. Install Safestrap 3.65 no problems till now...
5. Go into safestrap and go into Wipe then do Factory Data reset then advance wipe ( System, data, Internal Storage, cache , dalvik cache) then flash Beans ROM
6. Done.
Thank you for the detailed steps. I'll try it tonight.
cooch said:
Thank you for the detailed steps. I'll try it tonight.
Click to expand...
Click to collapse
Did you have any problems? I'm in the exact same situation.
I'm also curious about why we have to flash the odin image first. Is that for new radios? I'm already rooted, why not install SS and go from there?
cooch said:
I rooted my Note3 when an exploit first became available using RootDeLaVega. I haven't touched it since as I was waiting for the custom ROMs to roll out. I'm ready for Beans, but I want to be sure I'm going from rooted stock(no OTA's taken)...to upgraded Baseband(currently on M19)...to safestrap...to Beans.
Correct me if I'm wrong, but from what I've read I must do the following:
1. Use method 2 here: http://forum.xda-developers.com/showthread.php?t=2528707
2. Use Kingo to get root again.
3. Install safestrap: http://forum.xda-developers.com/showthread.php?t=2528707
Use Beta or Stable here?
4. Download and flash Beans to an open slot after making a backup.
I miss anything? Thanks.
Click to expand...
Click to collapse
I have a full on step by step, very detailed instruction for all the processes you need to take on your N3, check the link in my sig.
---------- Post added at 12:24 PM ---------- Previous post was at 12:19 PM ----------
dclutter1 said:
Did you have any problems? I'm in the exact same situation.
I'm also curious about why we have to flash the odin image first. Is that for new radios? I'm already rooted, why not install SS and go from there?
Click to expand...
Click to collapse
You only need to flash in Odin if you are on previous software (MI9, MJ7) in stead of current MJE. Flashing MJE in Odin installs latest modem, kernel and OS software updates. YOu'sd have issues running a MJE based Rom on a device with MJ7 or MI9 firmware...
If you're on MJE and rooted, start with the installation of Safestrap (custom recovery work around) on link in my sig. Everything is right there...
Yeah I read your thread, it looks great. Thanks for putting that together. And, thanks for the clarification.
Sent from my SM-N900V using Tapatalk
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
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
Instruction for installing a custom rom using safestrap
1. Choose a Lollipop Rom from the Verizon Galaxy S 5 Android Development. OnlyLollipop 5.0 TW based roms will work
2. If you already got safestrap working skip to step 10. Otherwise install the apk's in this zip View attachment Safestrap_Apps.zip
3. Once all are installed Click On Busybox Grant Super User Access and click on install
4. Now open Lollipop Safestrap and click on Install SafeStrap Grant Super User Access
5. Click On Install Recovery Once Installed It will Say State: Installed
6. Click the Back Button to take you to Lollipop Safestrap Recovery Main Screen
7. Click On Recovery Reboot. Grant Super User Access.
8. On the next screen click FLASH then when dialog comes up asking CLICK HERE TO REBOOT TO SAFESTRAP click on that and your phone will reboot to safestrap. May take a few seconds for the Recovery Screen to come up
9 In Safestrap Under Boot Options LEAVE THIS ALONE Install everything to STOCK ROM SLOT
10. Now If you have not I would make a backup of your current Rom so if something happens you can get back to where you are at now.
11.. Click on Wipe You will see 3 options Advance Wipe, Format Data And Swipe To Factory Reset. If you dont see these and you see a dialog asking something about entering Yes just hit the back button
12 To Install a new rom click on Advance Wipe And Check Dalvick Cache,Data,Cache,System Then click Swipe To wipe.
13. Now Click The Home Button
14 Now Choose Install. Underneath the header on the next screen You will see a black box it will either say Storage: Micro SDcard or Storage: Internal Storage. You can switch between the 2 by clicking that black box
15 Locate the zip you want to install and click on it
16. In next screen Click Swipe To Confirm Flash and your install will begin
17. When Finished Do Not Click Reboot Now Or Reboot System. Click The Home Button. All Older Roms should run fine on latest BOK3 Firmware so if your on BOK3 firmware simply flash BOK3 kernel.
18. Once That is installed you can reboot to system
19. If you get some kind of warning about unauthorized software all you need to do is delete SecurityLogAgent folder from the system/app
20 Now If you want to select a different Firmware Zip you only need to do this once. It will remain that Firmware untill another Firmware Zip is flashed. If you flash A Firmware Zip There is no need to flash a Kernel Zip during the same installation.
21. Most Deodexed Lollipop Roms will Take Up to 10 Min to boot. If it seems longer than that simple pull the battery and restart phone.
22. If something goes wrong! If the rom fails to boot or bootloops you are not screwed if you flashed with safestrap.
23. To get back to safestrap from a bootloop. Pull the battery. Boot to download mode Power+Volume Down+Home
24. Plug into your computer.
24. Open Odin make sure phone is connect blue box saying comport whatever will be lit up. In the AP section locate the NI2_stock_kernel.tar.md5 and flash kernel.
25. When phone reboots watch screen and click on the Recovery Button when the SafeStrap Screen comes up. If you miss it pull the battery and try again.
26. Once in Safestrap you can restore a back up or what ever you need to do
Just a note. You can also use flashfire to flash rom. Flashfire is a great tool. Just know that if you flash a rom with flashfire and have safestrap installed you will loose your safestrap installation. So after you flash a rom with flashfire if you want to use safestrap you will have to reinstall it. If something goes wrong during the the install when flashing with flash fire you will not be able to get back to safestrap and your only method if your bootlooped is using odin and flashing full factory tar image and going through the root process again!
Install Kit Kat Roms On All Bootloaders
Edit: I updated the method and added new firmware zips ran into some hardware issues these fixed the problem
This method should work for All Bootloaders Without having to wipe data on Internal storage
Download This one NK2_Firmware_No_Bootloaders_V3.zip should work for all Kit Kat Roms. This is a 4.4.4 Version I tested it on 4.42 Version and it worked fine . If you want to use a differen versions, all Version listed below
Reboot To Safestrap Wipe cache, system, data, dalvik cache then flash above zip
Go back and Wipe cache, system, data
Install Kit Kat Rom
Reboot to system and go through setup.
Remember when using Kit Kat Roms there is no reason to flash kernel in safestrap as you are all ready running kit kat kernel. Also do not use Lollipop Safestrap on kit kat roms you can reach safestrap by simply rebooting rom and choosing safestrap recovery when dialog comes up
All Firmwares
NCG_Firmware_No_Bootloaders_V3.zip
NE9_Firmware_No_Bootloaders_V3.zip
NHA_Firmware_No_Bootloaders_V3.zip
NI2_Firmware_No_Bootloaders_V3.zip
NK2_Firmware_No_Bootloaders_V3.zip
can i use the Optimal Rom if i have BOK3?
coopmaster said:
can i use the Optimal Rom if i have BOK3?
Click to expand...
Click to collapse
Yes. I just added some instructions in OP that may be helpful
jrkruse said:
Yes. I just added some instructions in OP that may be helpful
Click to expand...
Click to collapse
Just a question so if i have BOK3 when i go to flash the firmware do i need to wait till that rom has a BOK3 firmware or can i flash any of them?
coopmaster said:
Just a question so if i have BOK3 when i go to flash the firmware do i need to wait till that rom has a BOK3 firmware or can i flash any of them?
Click to expand...
Click to collapse
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.
jrkruse said:
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.
Click to expand...
Click to collapse
sweet thank you.
Might be stupid question but I was wondering if Extreme Syndicate and Cyanogemod are compatible.
jrkruse said:
. The BOK3 Firmware should be fine even on older roms. Just flash the rom and stay on the latest firmware. You may get a waring about unauthorized actions dialog warning just delete the SecurityLogAgent folder from the system/app folder, but all older roms should run fine on BOK3 firmware.
Click to expand...
Click to collapse
Am I understanding you correctly that newer firmwares are backwards-compatible? Are you referring to only Lollipop ROMs, or does this also apply to older KitKat ROMs?
If I were to update past BOD, that does slam the door on downgrading to a KitKat bootloader as we have already discussed. I understood this to mean I wouldn't be able to use any KitKat ROMs.
painiac said:
Am I understanding you correctly that newer firmwares are backwards-compatible? Are you referring to only Lollipop ROMs, or does this also apply to older KitKat ROMs?
If I were to update past BOD, that does slam the door on downgrading to a KitKat bootloader as we have already discussed. I understood this to mean I wouldn't be able to use any KitKat ROMs.
Click to expand...
Click to collapse
You can get kitkat roms to boot just by flashing the rom the kernel and the NON_HLOS.bin but I dont know if your bootloaders will let the NON-HLOS.bin flash or not. You have to wipe data and internal storage also
Plasma ROM steer clear of, doesn't wanna play nice. However Optimal ROM works perfectly but hopefully the developer updates it to BOK3. Is anyone working on a debloat.bat for this firmware? or can someone?
DimitrieRetezatu said:
Might be stupid question but I was wondering if Extreme Syndicate and Cyanogemod are compatible.
Click to expand...
Click to collapse
Not sure about Extreme Syndicate. ROMs must be touchwiz based. No AOSP based ROMs, so Cyanogenmod is not compatible. You have to look for ROMs in the Verizon Galaxy S5 Android Development forum. Cannot flash anything in the Original Android Development forum. Also probably not any or possibly just a couple from the Unified Development forum.
landshark68 said:
Not sure about Extreme Syndicate. ROMs must be touchwiz based. No AOSP based ROMs, so Cyanogenmod is not compatible. You have to look for ROMs in the Verizon Galaxy S5 Android Development forum. Cannot flash anything in the Original Android Development forum. Also probably not any or possibly just a couple from the Unified Development forum.
Click to expand...
Click to collapse
Thanks for the response. Makes more sense when you put it like that. Hopefully people will see that the new root is available and update some ROMs!
secandRRe said:
Plasma ROM steer clear of, doesn't wanna play nice. However Optimal ROM works perfectly but hopefully the developer updates it to BOK3. Is anyone working on a debloat.bat for this firmware? or can someone?
Click to expand...
Click to collapse
There are several debloater zips I have made just check the OP on my rom threads
If you like a very debloated rom that is super fast and great on battery I recommend my BS Free Roms. @CVertigo1 made a new BOK3 version of my BS Free roms its only 800 mb in size thats half the size of normal roms. Check out his thread
Sticking to OptimalROM seems to be everything I need.
jrkruse said:
There are several debloater zips I have made just check the OP on my rom threads
Click to expand...
Click to collapse
I gave your zips a try on BOK3 with no luck?
secandRRe said:
I gave your zips a try on BOK3 with no luck?
Click to expand...
Click to collapse
You need to use the debloat script on a clean install of rom flash rom the flash debloat script. This way you haven't updated a bunch of apps
I'm tempted to try your ROMs I just like the S6 Keyboard on OptimalROM it's probably one of the best keyboards I have used.
My BOG5 BS Free Rom and BS Free Google Rom both have s6 keyboards