Database Users

[Requests] Odin stock Rom for AT&T SGS3

Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox

matrox00612 said:
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
Click to expand...
Click to collapse
In the absence of a stock flashable ROM, and if you can still get into CWM, you can do the following:
1. Mount system in recovery
2. Pull the build.prop via ADB (I believe it's adb pull /system/build.prop) on your computer
3. Revert/fix whatever tweaks you jacked up when messing with it earlier (on your PC)
4. ADB push it back
5. ADB reboot
If build.prop is all that was wrong, hopefully this may get you back in business.

pinoymutt said:
In the absence of a stock flashable ROM, and if you can still get into CWM, you can do the following:
1. Mount system in recovery
2. Pull the build.prop via ADB (I believe it's adb pull /system/build.prop) on your computer
3. Revert/fix whatever tweaks you jacked up when messing with it earlier (on your PC)
4. ADB push it back
5. ADB reboot
If build.prop is all that was wrong, hopefully this may get you back in business.
Click to expand...
Click to collapse
Under CWM mount system, adb show error device nor found, its look that my only hope is a stock odin rom.
Thanks

Ouch, sounds like bad news. Hopefully someone will post something you can use to revert soon.
Sent from my GT-P3113 using Tapatalk 2

matrox00612 said:
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
Click to expand...
Click to collapse
Go to the att android dev section there is a root method posted that also has a unbrick fixboot.tar file for Odin, that will put you back in business.
http://forum.xda-developers.com/sho...ick your phone from flashing a gsm boot image
Sent from my SAMSUNG-SGH-I747

stan.s said:
Go to the att android dev section there is a root method posted that also has a unbrick fixboot.tar file for Odin, that will put you back in business.
http://forum.xda-developers.com/sho...ick your phone from flashing a gsm boot image
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Thanks for the info, but thats the boot.img I need the system.img packed into an Odin tar.

matrox00612 said:
Thanks for the info, but thats the boot.img I need the system.img packed into an Odin tar.
Click to expand...
Click to collapse
There is no system.img released yet..Many of us are waiting for that system.img file. Its not leaked, released or created yet... But should be released, created soon. I am pretty sure the developers are working on it.
Till then we can just wait!!

masonjoe69 said:
There is no system.img released yet..Many of us are waiting for that system.img file. Its not leaked, released or created yet... But should be released, created soon. I am pretty sure the developers are working on it.
Till then we can just wait!!
Click to expand...
Click to collapse
Yes it is like that, we have to wait a little, but lets get the first dev to throw a working odin flashable file some motivation, i will donate 50 beers.

Help trying to get back into custom recovery

I did research for this for a couple of hours but didn't find anything too helpful besides flashing back to stock. I also saw I could install the TWRP img file by the command line but that makes me a little nervous for the brick warnings posted.
I have the Goldeneye rom on my phone and I had TWRP 2.5.0.2 and everything was working great. I also updated the Modem to the MF3 one. I flashed TWRP up to 2.6 and loki-doki and everything seemed to go OK until I rebooted the phone.
I rebooted the phone and got the error of System software not authorized by ATT has been found on your phone and the SECURE FAIL: KERNEL message at the top.
I am now unable to boot into recovery with the buttons or using the reboot menu from the Goldeneye rom. Every time I try to reboot it goes to the error message above.
Now I am able to have the phone boot up fully if I go into download mode and then press the volume down key to cancel/restart the phone and then it will boot up with out issue. Any time I reboot though with out going into download mode I get the secure kernel error.
Is there a way to recover the device without going through ODIN and reflashing it back to stock? Also, my baseband shows MF3 now since I flashed the modem, is that going to cause any issues?
Any advice would be appreciated. Thanks

Can you try reinstalling the twrp recovery through goomanager when you get it to boot.. Then retrying to get into recovery?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta

bump
Sent from my SAMSUNG-SGH-I337 using xda premium

rcklss1 said:
Can you try reinstalling the twrp recovery through goomanager when you get it to boot.. Then retrying to get into recovery?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I go to install OpenRecoveyScript in goomanager and it tells me that no recoveries were found for my device

lyrad12 said:
bump
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Why are you bumping this--
---------- Post added at 11:52 PM ---------- Previous post was at 11:47 PM ----------
dibe said:
I go to install OpenRecoveyScript in goomanager and it tells me that no recoveries were found for my device
Click to expand...
Click to collapse
Why not Odin
I haven't looked for awhile, but if you example of command to put recovery on phone by adb, try it. If you have the command line from a dev thread then just copy/paste the line. No chance of typing error. Still double check all. And any bu's you can do prior, do them and put copy on pc. Know you can't nandroid, but maybe MyBackUp Pro.

I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin

dibe said:
I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin
Click to expand...
Click to collapse
Good Luck--:good:

dibe said:
I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin
Click to expand...
Click to collapse
Lol, odin is much easier.
Sent from my HTC One X using xda premium

rugmankc said:
Good Luck--:good:
Click to expand...
Click to collapse
Thanks.
I installed the TWRP 2.5.0.2 img file using Android Terminal Emulator and the command line. Everything is working fine now with the phone and I didn't have to reflash or lose any data.
Thanks for everyone's help.

convict_moody said:
Lol, odin is much easier.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Odin is last resort for me since you lose everything--
---------- Post added at 02:47 AM ---------- Previous post was at 02:46 AM ----------
dibe said:
Thanks.
I installed the TWRP 2.5.0.2 img file using Android Terminal Emulator and the command line. Everything is working fine now with the phone and I didn't have to reflash or lose any data.
Thanks for everyone's help.
Click to expand...
Click to collapse
Glad you got it--:good:

rugmankc said:
Odin is last resort for me since you lose everything--
I would have to fully agree with you there. I am very glad installing the img worked.
Click to expand...
Click to collapse

[Q] Phone will enter recovery but not main bootloader screen

So I am trying to install CM11 on my G2 D802. Root done, Loki done, CWM or TWRP recovery done, CM11 image and GApps on sdcard partition. Now there is just one problem. I need to transfer the boot.img file from the CM11 zip file, however, I am unable to enter the main booloader screen, thus the Fastboot option. When I try to do so, the phone just reboots normally and launches the Android. I have the same problem with both CWM and TWRP. Anyone have an idea as to what is wrong?

Not really sure what you are talking about. If you have recovery all you need to do is wipe system, data, and cache. Then install the CM11 zip.
Sent from my LG-VS980 using xda app-developers app

**** Ripple said:
Not really sure what you are talking about. If you have recovery all you need to do is wipe system, data, and cache. Then install the CM11 zip.
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
I should start by mentioning, that the whole; Power and volume down button to enter bootloader never worked on the D802.
Basically what I need to do, is to transfer the boot.img file before flashing the .zip file, otherwise I will get bootloop (this is my second D802). That has always been the case for any Android device I have had.
So in order to flash the boot.img file, I must enter the Fastboot menu on my G2 before I can transfers the file via command prompt.

Stop what your doing read up before you try to do anything.
Sent from my LG-LS980 using xda premium

I've been flashing roms for years and nothing you are saying makes any sense. If you are having trouble entering recovery download terminal emulator. Open app and type su then press enter. You will be asked to grant root access assuming you have root. Then type reboot recovery, after that your phone will boot into recovery. Wipe, flash rom and gapps.
Sent from my LG-VS980 using xda app-developers app

shopperen said:
I should start by mentioning, that the whole; Power and volume down button to enter bootloader never worked on the D802.
Basically what I need to do, is to transfer the boot.img file before flashing the .zip file, otherwise I will get bootloop (this is my second D802). That has always been the case for any Android device I have had.
So in order to flash the boot.img file, I must enter the Fastboot menu on my G2 before I can transfers the file via command prompt.
Click to expand...
Click to collapse
If you downloaded CM11 for your device specifically then you do not need to flash a separate kernel (boot.img) it would be included in the ROM zip file.. As should be the case with any current ROM that is compatible with your model G2. If you were going to experiment by way of flashing some other G2 variant (ie. D800/1/3) which is not advisable btw on your D802 then I could see you flashing a kernel separately.
That said I agree with the person above me.. You should do a bit more reading so you understand these elements properly before ending up with a paper weight (or another one from the sounds of your post). Hope it helps good luck
Sent from my d800 using Tapatalk

th3g1z said:
If you downloaded CM11 for your device specifically then you do not need to flash a separate kernel (boot.img) it would be included in the ROM zip file.. As should be the case with any current ROM that is compatible with your model G2. If you were going to experiment by way of flashing some other G2 variant (ie. D800/1/3) which is not advisable btw on your D802 then I could see you flashing a kernel separately.
That said I agree with the person above me.. You should do a bit more reading so you understand these elements properly before ending up with a paper weight (or another one from the sounds of your post). Hope it helps good luck
Sent from my d800 using Tapatalk
Click to expand...
Click to collapse
Kernel files very depending on region. The distributor for LG phones in my country have altered the kernel in such a way, that the boot.img is required to be flashed.

[SOLVED] Coming Over From GS3 (d2att)

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

[Q&A] [ROOT][RECOVERY][100%] ROOT +TWRP RECOVERY for samsung Galaxy Tab 4 t231

Q&A for [ROOT][RECOVERY][100%] ROOT +TWRP RECOVERY for samsung Galaxy Tab 4 t231
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][RECOVERY][100%] ROOT +TWRP RECOVERY for samsung Galaxy Tab 4 t231. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Faiyaz5yaz said:
100%ROOT + TWRP RECOVERY ​
NOTE:This Was Tested By Me On TAB 4 t231 with Firmware Version T231XXU0ANG1_T231ODD0ANF3_INU ; It May Work With Latest Firmware Verions , But I Haven't Tested
REQUIREMENTS:
* PC
*TAB 4 T231
*DATA CABLE
*PROPER DRIVERS INSTALLED
*ODIN V3.09.zip HERE and Extract
*Download TWRP from HERE AND EXTRACT
* DOWNLOAD SuperSU from HERE
INSTRUCTIONS:
RECOVERY :
Put your tablet in download mode by Pressing the Home button + Power + Volume Down; Release buttons ,wen u see a warning ; then you should press the volume up (vol +) to continue to download mode.
* Run Odin v3.09 and connect tablet, The box in odin will turn to light blue box ID: COM;
* Check The AP box and locate the unzipped file TWRP file recovery.img.tar.md5;
*Finally click on the Star button and wait for few seconds until Odin process and show you the notice Pass in green and completely restart the tablet, click Exit to exit Odin.
RECOVERY WAS SUCCESSFULLY FLASHED
ROOT
*BOOT INTO RECOVERY BY PRESSING POWER+HOME+VOL UP
*NOW SELECT INSTALL ZIP FROM SD CARD
* CHOOSE THE sUPERSU.ZIP
*CONFIRM YES BY SWIPING
REBOOT CHECK WITH ROOT CHECKER
SUCESSFULLY ROOTED Tab 4 t231​
Click to expand...
Click to collapse
Wow thanks, now i can root my friend tab 4 7.0

Any word on whether this root and recovery works on the 237P? I've gotta get the stock bloat off my free tablet.

BjarturOS said:
Any word on whether this root and recovery works on the 237P? I've gotta get the stock bloat off my free tablet.
Click to expand...
Click to collapse
If you have the 237P, I believe you need this thread to root your tablet. Make sure to read carefully, especially the most recent posts, as some have had trouble from not following directions carefully. Should work fine. Idk where you guys are as far as a custom recovery, but I'm all but certain this recovery will NOT work for your tablet.
Edit: On the thread I linked to, Post #15 has how to root info and Page 6 has the info about people messing up and what to do to correct that.

Do not download odin from this link!!
I rooted my tablet through this thread. It went smoothly , but one problem I had with the Odin download. It installed so much adware and malware without my permission or giving me a chance to decline anything, that my computer is totally screwed. I have had too do a full reinstall of windows due to this version of Odin. It has cost me money because I use my computer to design graphics for people and companies. If you don't believe me, try it out. But you can't blame me for being a bit ticked off because of this file screwing with my lively hood .

SoCalGhstRydr said:
I rooted my tablet through this thread. It went smoothly , but one problem I had with the Odin download. It installed so much adware and malware without my permission or giving me a chance to decline anything, that my computer is totally screwed. I have had too do a full reinstall of windows due to this version of Odin. It has cost me money because I use my computer to design graphics for people and companies. If you don't believe me, try it out. But you can't blame me for being a bit ticked off because of this file screwing with my lively hood .
Click to expand...
Click to collapse
That's really crappy, I am truly sorry to hear that. You're right, that website is so shady I have a browser extension called WOT (Web of Trust check it out it's pretty handy) that wouldn't even let me go to the site. For your future reference, and anyone else reading this thread, I have attached Odin, both versions 3.07 and 3.09. They're attached to the bottom of this post, not hosted on any other site, I guarantee 100% both files are safe. They're both zip files, all you have to do is extract the folder inside to your desktop. Inside the folder will be two files. Double click the .exe to run Odin, it's that simple. Again, I'm so sorry you had to go through that mess, been there before, it's no fun.

Thanks for your quick response to my post. I just did not want others to go through what i went through. Luckily I had back ups of everything, but good news was, I rooted my tablet first try. lol. Thanks again.

hi
to where i should install all these the odin, superuser, in my android device or in pc? or should i install these in both android device and pc? im confuse. thanks!

Arkyarao said:
to where i should install all these the odin, superuser, in my android device or in pc? or should i install these in both android device and pc? im confuse. thanks!
Click to expand...
Click to collapse
Odin is installed on the PC. SuperSU (superuser) is an android app. You use Odin to flash the custom recovery (TWRP) onto your tablet.

thisisapoorusernamechoice said:
Odin is installed on the PC. SuperSU (superuser) is an android app. You use Odin to flash the custom recovery (TWRP) onto your tablet.
Click to expand...
Click to collapse
oh i see!. and what about the TWRP should it be installed also on the pc?..what is TWRP by the way. thank you. sorry for asking too many questions.

Arkyarao said:
oh i see!. and what about the TWRP should it be installed also on the pc?..what is TWRP by the way. thank you. sorry for asking too many questions.
Click to expand...
Click to collapse
TWRP is a custom recovery, you use it on your tablet to root (and possibly to install custom roms, if you wish). You download it as a .tar file to your PC, run Odin on your PC with your tablet connected via usb in download mode to your PC and flash the recovery file.

thisisapoorusernamechoice said:
TWRP is a custom recovery, you use it on your tablet to root (and possibly to install custom roms, if you wish). You download it as a .tar file to your PC, run Odin on your PC with your tablet connected via usb in download mode to your PC and flash the recovery file.
Click to expand...
Click to collapse
oh! how to install custom root?

Arkyarao said:
oh! how to install custom root?
Click to expand...
Click to collapse
This is the Q&A thread on how to root, so you can see that thread again on how to root.
Custom roms are something else. Root your tablet first and then we can talk about custom roms lol

Arkyarao said:
oh! how to install custom root?
Click to expand...
Click to collapse
hehehe. sorry! i didnt know. thank you...is there any other way so we can talk about this in a quick way. like facebook or what. i really need ur help. hehehe. thanks again.
---------- Post added at 05:16 AM ---------- Previous post was at 04:23 AM ----------
silentroom said:
Wow thanks, now i can root my friend tab 4 7.0
Click to expand...
Click to collapse
help me guys. i have downloaded TWRP through the link posted in the instruction. now i open the Odin and checked the AP box and locate the unzipped file TWRP (recovery.img.tar.md5) but the file is empty. what should i do? can someone give a link for TWRP so that i can continue the process. thanks!

Arkyarao said:
hehehe. sorry! i didnt know. thank you...is there any other way so we can talk about this in a quick way. like facebook or what. i really need ur help. hehehe. thanks again.
---------- Post added at 05:16 AM ---------- Previous post was at 04:23 AM ----------
help me guys. i have downloaded TWRP through the link posted in the instruction. now i open the Odin and checked the AP box and locate the unzipped file TWRP (recovery.img.tar.md5) but the file is empty. what should i do? can someone give a link for TWRP so that i can continue the process. thanks!
Click to expand...
Click to collapse
Just downloaded the file myself, everything is there (inside the tar - tar is an archive like zip or rar - there is a recovery.img, like there should be). It sounds like you're having trouble using Odin? Google hangouts if you want to chat with me, I had very good reasons to delete my facebook

thisisapoorusernamechoice said:
Just downloaded the file myself, everything is there (inside the tar - tar is an archive like zip or rar - there is a recovery.img, like there should be). It sounds like you're having trouble using Odin? Google hangouts if you want to chat with me, I had very good reasons to delete my facebook
Click to expand...
Click to collapse
yeah your right! i really having trouble with odin. haha. i thought it was ok. i only having problem with this... what is tar? and how can i locate the exact file. can u pleasssseee tell me how. i already did everything. haha. oh my God!..please bare with me this time.

Arkyarao said:
yeah your right! i really having trouble with odin. haha. i thought it was ok. i only having problem with this... what is tar? and how can i locate the exact file. can u pleasssseee tell me how. i already did everything. haha. oh my God!..please bare with me this time.
Click to expand...
Click to collapse
Download this file to your PC and extract it. Run Odin and point it to that extracted file
When you're flashing your tablet with Odin you have to have your tablet in download mode
To boot your tablet into download mode, first turn it off, then hold down home, vol -, and the power button simultaneously.

thisisapoorusernamechoice said:
Download this file to your PC and extract it. Run Odin and point it to that extracted file
When you're flashing your tablet with Odin you have to have your tablet in download mode
To boot your tablet into download mode, first turn it off, then hold down home, vol -, and the power button simultaneously.
Click to expand...
Click to collapse
yeah thats what i did. i followed all the instructions and procedures..ive already found the extracted file. i donwloaded zip manager. now the problem is "md5 is error! binary is invalid" what is this?...what will i do. i didnt know that i have to encounter this.