Develop Bugs

Help!

So I was dumb. I tried flashing a kernel (the one found on the main xda sprint galaxy s3 page) on my rooted, stock rom, kitkat s3. When it didn't seem to take, I tried flashing my nandroid recovery. When the phone booted, gapps weren't working, everything was crashing, and the phone had no service. I freaked out and (this entire time I'm trying to find helpful forums) tried flashing a stock 4.3 rom (the only one I could find). Gapps are working again and I'm still rooted with 4.3, but I still have no service. There doesn't appear to be a baseband version installed. At this point, I'd love to just get service back (I can't seem to find a relevant or helpful thread), and eventually update to 4.4 again. Help?!

gobluefanjp said:
So I was dumb. I tried flashing a kernel (the one found on the main xda sprint galaxy s3 page) on my rooted, stock rom, kitkat s3. When it didn't seem to take, I tried flashing my nandroid recovery. When the phone booted, gapps weren't working, everything was crashing, and the phone had no service. I freaked out and (this entire time I'm trying to find helpful forums) tried flashing a stock 4.3 rom (the only one I could find). Gapps are working again and I'm still rooted with 4.3, but I still have no service. There doesn't appear to be a baseband version installed. At this point, I'd love to just get service back (I can't seem to find a relevant or helpful thread), and eventually update to 4.4 again. Help?!
Click to expand...
Click to collapse
Have you tried flashing the MK3 modem? You can find it here: http://forum.xda-developers.com/showthread.php?t=2538978
Good luck!

MrWBucket said:
Have you tried flashing the MK3 modem? You can find it here: http://forum.xda-developers.com/showthread.php?t=2538978
Good luck!
Click to expand...
Click to collapse
Sorry, I'm pretty new at this. I forgot to mention that my usb cable for my phone to pc doesn't work well, so using the pc isn't a great option. Is the modem flashable through mobile odin? Thanks!

gobluefanjp said:
Sorry, I'm pretty new at this. I forgot to mention that my usb cable for my phone to pc doesn't work well, so using the pc isn't a great option. Is the modem flashable through mobile odin? Thanks!
Click to expand...
Click to collapse
Woops, found you need to flash it in recovery. However, when I tried doing that, it said signature verification failed?

gobluefanjp said:
Woops, found you need to flash it in recovery. However, when I tried doing that, it said signature verification failed?
Click to expand...
Click to collapse
Okay, I was able to flash that modem, but still no signal.

gobluefanjp said:
Okay, I was able to flash that modem, but still no signal.
Click to expand...
Click to collapse
If you were ever on Stock KitKat, you need to use the ND8 Modem. The only way of getting that is by re-Odining the stock ND8 tar.
You'll need a new cable. Do NOT use Mobile Odin with the stock tar, you'll hard brick your phone.
After you do that and Odin the latest Philz Recovery, make a nandroid of your ND8 modem in case this happens again.
What recovery and version were you on? This has been known to happen on CWM. I haven't tested restoring with TWRP v2.7.0.0 yet, but Philz is known to be 100% working with KitKat.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.

roirraW "edor" ehT said:
If you were ever on Stock KitKat, you need to use the ND8 Modem. The only way of getting that is by re-Odining the stock ND8 tar.
You'll need a new cable. Do NOT use Mobile Odin with the stock tar, you'll hard brick your phone.
After you do that and Odin the latest Philz Recovery, make a nandroid of your ND8 modem in case this happens again.
What recovery and version were you on? This has been known to happen on CWM. I haven't tested restoring with TWRP v2.7.0.0 yet, but Philz is known to be 100% working with KitKat.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.
Click to expand...
Click to collapse
Awesome, thanks for the help! I have a new cable on the way, so I can use that instead of mobile odin. The ND8 tar file is this one, right?
Once I odin the ND8 tar, that will break root, correct?
I'm pretty new at this, but I think I was using Clockworkmod recovery? I originally followed the instructions in this video: https://www.youtube.com/watch?v=_afP4BI1RFY.
I suppose after that I will be on unrooted stock kitkat?
Thanks for all your help and patience with what are probably silly questions!

gobluefanjp said:
Awesome, thanks for the help! I have a new cable on the way, so I can use that instead of mobile odin. The ND8 tar file is this one, right?
Once I odin the ND8 tar, that will break root, correct?
I'm pretty new at this, but I think I was using Clockworkmod recovery? I originally followed the instructions in this video: https://www.youtube.com/watch?v=_afP4BI1RFY.
I suppose after that I will be on unrooted stock kitkat?
Thanks for all your help and patience with what are probably silly questions!
Click to expand...
Click to collapse
You're welcome!
No, this one http://forum.xda-developers.com/showthread.php?t=2738533.
Just after ODINing that, ODIN the tar of the latest version of Philz Recovery, put the latest version of SuperSU.zip on your SD card, flash that in recovery and you'll be good.
The Nandroids from regular CWM don't seem to restore right and they do in Philz. I haven't tested restores in TWRP v2.7.0.0 yet.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.

roirraW "edor" ehT said:
You're welcome!
No, this one http://forum.xda-developers.com/showthread.php?t=2738533.
Just after ODINing that, ODIN the tar of the latest version of Philz Recovery, put the latest version of SuperSU.zip on your SD card, flash that in recovery and you'll be good.
The Nandroids from regular CWM don't seem to restore right and they do in Philz. I haven't tested restores in TWRP v2.7.0.0 yet.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.
Click to expand...
Click to collapse
Okay, so when I go to flash that, this keeps happening in Odin:
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried researching this in other threads, but nothing has worked. I just used odin successfully a couple weeks ago, so I'm not sure what's different now. Any ideas?
Also, I can't figure out what the latest version of PhilZ is for the sprint s3, which one would that be?
Again, thank you for all your help.

gobluefanjp said:
Okay, so when I go to flash that, this keeps happening in Odin:
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried researching this in other threads, but nothing has worked. I just used odin successfully a couple weeks ago, so I'm not sure what's different now. Any ideas?
Also, I can't figure out what the latest version of PhilZ is for the sprint s3, which one would that be?
Again, thank you for all your help.
Click to expand...
Click to collapse
Try a different USB port. Try rebooting Windows. Try a different cable if you have one.
Have you already been to the Philz Recovery thread in the Development section? Once you follow the link in it's OP to the downloads, and select Spr or LTE, I forget which they're using now for our builds, then the latest is at the bottom of the list. They have the file dates beside them. You want the one that ends in .tar.md5.
Not the .zip, and not the plain .md5 file listed after the zip, although it doesn't hurt to have those too, but for beginning purposes you want the .tar.md5.
You're welcome!
Sent from my 2767BK1 using Tapatalk

So I realized that even with a new catble, I wasn't going to get anywhere with odin because the microUSB port on my phone was shot. So I took it to the Sprint store and told them about the port and that I had lost service when trying to upgrade to KitKat. So, not only did they just completely re-flash the phone restoring service, they also just replaced the port. All for free and not with Sprint warranty. So, obviously, I'm now unrooted, but the phone is back to stock with service!
Anyway, thanks for all of your help! I think I'll root it after upgrading to KitKat from 4.3 again, and then use the PhilZ recovery you suggested. From now on, I'll just be doing things I know exactly how to do. Again, thanks for all the help!

gobluefanjp said:
Anyway, thanks for all of your help! I think I'll root it after upgrading to KitKat from 4.3 again, and then use the PhilZ recovery you suggested. From now on, I'll just be doing things I know exactly how to do. Again, thanks for all the help!
Click to expand...
Click to collapse
You're welcome! That's awesome. I'm glad you had such great luck at the Sprint store.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.

[Q] Flashed the stock rom but it is still showing cm 11 splash screen. . .

So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.

Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?

audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.

Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486

audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?

Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809

sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.

Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.

audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.

audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.

sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.

[Q] NB4 to NF4 without losing root or messing up Knox

So, I have a NB4 SM N900T. I rooted with cfautoroot, then installed Phillz Touch CWM, then made a full backup. After I rooted and installed a custom recovery, I was getting that recovery not SEANDROID enforcing/Kernel Warranty error on Boot. I then flashed Hyperdrive and used it for a few weeks. Today I wiped everything, and restored that nandroid backup to bring it back to stock NB4 because I cannot seem to get LTE to work to save my life.
Anyhow, now I see that NF4 is out.
With stock NB4, I'm no longer getting that error. It's still rooted, etc after the backup was restored.
What I would like to know is what would be the best way for me to get the NF4 update without messing up my root/Knox?
I can use ODIN, but if someone could just be a little more specific that would be great.
I downloaded N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5
and Cfautoroot from another thread...
I think I'm going to stay with the stock ROM until I figure out this LTE issue... I am on Straight Talk AT&T (Using Hyperdrive ROM) and get plain 4G and someone with the same phone- stock NB4 and ATT go service standing 2 feet away gets 4Glte. 15mbs+ speeds, while I'm under 5mbs.
Sorry, kinda all over the place here...
Anyhow, thanks for any help everyone.

re: Knox
Ed Murray said:
So, I have a NB4 SM N900T. I rooted with cfautoroot, then installed Phillz Touch CWM, then made a full backup. After I rooted and installed a custom recovery, I was getting that recovery not SEANDROID enforcing/Kernel Warranty error on Boot. I then flashed Hyperdrive and used it for a few weeks. Today I wiped everything, and restored that nandroid backup to bring it back to stock NB4 because I cannot seem to get LTE to work to save my life.
Anyhow, now I see that NF4 is out.
With stock NB4, I'm no longer getting that error. It's still rooted, etc after the backup was restored.
What I would like to know is what would be the best way for me to get the NF4 update without messing up my root/Knox?
I can use ODIN, but if someone could just be a little more specific that would be great.
I downloaded N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5
and Cfautoroot from another thread...
I think I'm going to stay with the stock ROM until I figure out this LTE issue... I am on Straight Talk AT&T (Using Hyperdrive ROM) and get plain 4G and someone with the same phone- stock NB4 and ATT go service standing 2 feet away gets 4Glte. 15mbs+ speeds, while I'm under 5mbs.
Sorry, kinda all over the place here...
Anyhow, thanks for any help everyone.
Click to expand...
Click to collapse
If you have installed any custom recovery like cwm/twrp you have
already tripped knox and there is no way to fix it so you may as well
simply flash whatever firmware and or custom rom you like.
Flashing/installing any custom recovery trips knox.
Good luck!

Fixed LTE issues. Threw away Straight Talk, Picked up AT&T.
Ok, so I'm considering staying on Stock ROM but my NB4 (RAC Build) N900T has no OTA update from Samsung...
So, am I able to just flash straight from NB4 to NF4? Will I lose root?

re: root
Ed Murray said:
Fixed LTE issues. Threw away Straight Talk, Picked up AT&T.
Ok, so I'm considering staying on Stock ROM but my NB4 (RAC Build) N900T has no OTA update from Samsung...
So, am I able to just flash straight from NB4 to NF4? Will I lose root?
Click to expand...
Click to collapse
Yes you will loose root however if you simply flash cf-autoroot after
flashing the official N900T NF4 firmware you will have root again.
Here is the direct download link for the official N900T NF4 firmware:
http://www.mediafire.com/download/f...VUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5
Here is the direct download link for the Odin flashable cf-autoroot:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
Good luck!

Misterjunky said:
Yes you will loose root however if you simply flash cf-autoroot after
flashing the official N900T NF4 firmware you will have root again.
Here is the direct download link for the official N900T NF4 firmware:
http://www.mediafire.com/download/f...VUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5
Here is the direct download link for the Odin flashable cf-autoroot:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
Good luck!
Click to expand...
Click to collapse
You're welcome for the firmware link.
I asked you nicely in pm to link to my thread instead of stealing my links, but since you ignored that, be prepared to have me comment on your posts where you try to pass them off as your own, or at least fail to attribute.
I appreciate that you want to help others, but please attribute links and/our abide by the posters requests when they ask you.
Thanks
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T

Thanks, both of you, for the info and links.
Can I use Mobile Odin to do this?

Ed Murray said:
Thanks, both of you, for the info and links.
Can I use Mobile Odin to do this?
Click to expand...
Click to collapse
You can, but just be aware that Mobile Odin cannot flash bootloaders, so if you're just looking to go straight up, you can either follow the directions in post #2 of this link: http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398 or use desktop odin.
If you want to do it all in one shot, desktop odin is your best bet. Just power your device down for about 15-30 seconds (or power off using power menu and battery pull for a bout 10 seconds), then boot straight into download mode (this helps ensure the modem and bootloader stick), and flash the full package in the AP (or PDA) slot of desktop odin.

toastido said:
You can, but just be aware that Mobile Odin cannot flash bootloaders, so if you're just looking to go straight up, you can either follow the directions in post #2 of this link: http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398 or use desktop odin.
If you want to do it all in one shot, desktop odin is your best bet. Just power your device down for about 15-30 seconds (or power off using power menu and battery pull for a bout 10 seconds), then boot straight into download mode (this helps ensure the modem and bootloader stick), and flash the full package in the AP (or PDA) slot of desktop odin.
Click to expand...
Click to collapse
Alright, thanks for the help. I'm out of "thanks" for the day, but will click the crap outta it tomorrow. Much appreciated.

[Q&A] [Stock/Base] 4.4.4 NK2 Rooted-Deodexed-Knoxless-CIQless

Q&A for [Stock/Base] 4.4.4 NK2 Rooted-Deodexed-Knoxless-CIQless
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 [Stock/Base] 4.4.4 NK2 Rooted-Deodexed-Knoxless-CIQless. 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!

mine says enforcing. So how do I get the permissive? I downloaded it but you say not to install it until after the modem and rom. So... ?
---------- Post added at 03:27 AM ---------- Previous post was at 03:19 AM ----------
mine says enforcing. So how do I get the permissive? I downloaded it but you say not to install it until after the modem and rom. So... ?

pmular said:
mine says enforcing. So how do I get the permissive? I downloaded it but you say not to install it until after the modem and rom. So... ?
---------- Post added at 03:27 AM ---------- Previous post was at 03:19 AM ----------
mine says enforcing. So how do I get the permissive? I downloaded it but you say not to install it until after the modem and rom. So... ?
Click to expand...
Click to collapse
Still says enforcing after flashing permissive kernel?

So I was on nh7 prior. Flashed the modem file in Odin.
Went into twrp 2.8.3.. wiped. Installed rom, then kernel, then booted into system. Wifi didn't work.
Any suggestions? Do I need to wipe dalvik after the kernel install?
Thanks...
Sent from my SGH-M919 using Tapatalk 2

Try reflash rom, sometimes it does not take the first time.
Pp.

No Wifi for me either. Barely even flinches when I click it.
SGH-M919 on 4.2.2 stock rooted -> Update via latest CWM = soft brick (stuck on Samsung boot screen)
-> 4.2.2 stock via Odin -> installed TWRP recovery -> installed your posted 4.4.4 NK2 ROM = no wifi
-> installed posted NK2 Modem -> installed posted kernel = still no wifi
-> Reverted back to 4.2.2 via backup + NK2 modem= regained wifi
Hopefully the datapoint will help. Thanks though

corpse101 said:
No Wifi for me either. Barely even flinches when I click it.
SGH-M919 on 4.2.2 stock rooted -> Update via latest CWM = soft brick (stuck on Samsung boot screen)
-> 4.2.2 stock via Odin -> installed TWRP recovery -> installed your posted 4.4.4 NK2 ROM = no wifi
-> installed posted NK2 Modem -> installed posted kernel = still no wifi
-> Reverted back to 4.2.2 via backup + NK2 modem= regained wifi
Hopefully the datapoint will help. Thanks though
Click to expand...
Click to collapse
It's the kernel causing it. Don't know why. Keep the stock kernel or flash a different one. No one has provided a log cat with errors

ShinySide said:
It's the kernel causing it. Don't know why. Keep the stock kernel or flash a different one. No one has provided a log cat with errors
Click to expand...
Click to collapse
Pardon my noobishness, but I always follow the guides and normally install w/e I am told. How can I revert to the stock kernel? I originally tested after flashing your custom ROM, and before the new kernel and it still didn't work.

Received a replacement S4 from SquareTrade today (last one broke), and it shipped with stock 4.4.4/NK2. Can I just flash this ROM/firmware in Odin? Or did I have to be rooted already?

You suppose to flash twrp recovery in Odin. Then flash this rom in twrp.
Sent from my SGH-M919 using Tapatalk 2

UJ95x said:
Received a replacement S4 from SquareTrade today (last one broke), and it shipped with stock 4.4.4/NK2. Can I just flash this ROM/firmware in Odin? Or did I have to be rooted already?
Click to expand...
Click to collapse
You need to root with cf-autoroot in Odin first. Then Odin whichever recovery you prefer.
Sent from my SGH-M919 using Tapatalk

mrbmg said:
You need to root with cf-autoroot in Odin first. Then Odin whichever recovery you prefer.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
The one on Chainfire's site only says it's for NH7. I'm on NK2, is that one still fine?
I should know this...it's just been a while lmao. Thanks

UJ95x said:
The one on Chainfire's site only says it's for NH7. I'm on NK2, is that one still fine?
I should know this...it's just been a while lmao. Thanks
Click to expand...
Click to collapse
Be fine. Or just skip cf auto and flash a recovery, flash supersu package, or flash recovery and flash a rom. Cf auto root is a waste of time if you're just gonna flash a recovery

ShinySide said:
Be fine. Or just skip cf auto and flash a recovery, flash supersu package, or flash recovery and flash a rom. Cf auto root is a waste of time if you're just gonna flash a recovery
Click to expand...
Click to collapse
Awesome. Thought I needed to root before flashing a custom recovery. So the only difference is my Knox counter will be tripped right? Oh, and the SGH-M919's boot loader is unlocked by default as well, correct?

UJ95x said:
Awesome. Thought I needed to root before flashing a custom recovery. So the only difference is my Knox counter will be tripped right? Oh, and the SGH-M919's boot loader is unlocked by default as well, correct?
Click to expand...
Click to collapse
Yes,custom recoveries and kernels trip knox. And yes it's unlocked

ShinySide said:
Yes,custom recoveries and kernels trip knox. And yes it's unlocked
Click to expand...
Click to collapse
Cool. Thanks again, man.

Is there a unrestricted hotspot hack I can flash with this rom?

I'd like an answer to this too if anyone knows.
I'm on an MDL bootloader with NK2 baseband.

Hey all. I'm not sure this is the right thread but I do believe it's related. I've posted similar questions in other threads so bear with me if you've read some of this before. I'm just having trouble getting responses...lol. So, I'm trying to help a friend who bought an s4 and hooked it up with metro pcs. After he got it connected, he brought it to me. I used odin to flash oudhs recovery and then I flashed the sickness rom (the guy I'm helping ONLY wants unrestricted tethering, btw). The rom would not boot--stuck at boot screen. I then tried wiping everything in recovery and restoring the stock (which I had backed up, of course). That will not boot either (ugh). So, I now plan to use Odin to flash the stock .tar. I found one here in the forums BUT then I found another stock .tar in the Metro PCS thread. I'm not sure which I should flash--I'm leaning towards the Metro one since the guy IS on metro (if someone knows better, please let me know).
Question now is, after I flash the stock .tar, what is the SIMPLEST way to unrestrict the guy's tethering (if possible)? I'd REALLY appreciate a little help. Even if it's just pointing me to a thread that might help. Also, if anyone can explain why the Sickness wouldn't boot, that might help as well.
Thanks in advance!

pathtologos said:
Hey all. I'm not sure this is the right thread but I do believe it's related. I've posted similar questions in other threads so bear with me if you've read some of this before. I'm just having trouble getting responses...lol. So, I'm trying to help a friend who bought an s4 and hooked it up with metro pcs. After he got it connected, he brought it to me. I used odin to flash oudhs recovery and then I flashed the sickness rom (the guy I'm helping ONLY wants unrestricted tethering, btw). The rom would not boot--stuck at boot screen. I then tried wiping everything in recovery and restoring the stock (which I had backed up, of course). That will not boot either (ugh). So, I now plan to use Odin to flash the stock .tar. I found one here in the forums BUT then I found another stock .tar in the Metro PCS thread. I'm not sure which I should flash--I'm leaning towards the Metro one since the guy IS on metro (if someone knows better, please let me know).
Question now is, after I flash the stock .tar, what is the SIMPLEST way to unrestrict the guy's tethering (if possible)? I'd REALLY appreciate a little help. Even if it's just pointing me to a thread that might help. Also, if anyone can explain why the Sickness wouldn't boot, that might help as well.
Thanks in advance!
Click to expand...
Click to collapse
Shabby's cwr is so extremely out of date. You need to use newer recoveries. I prefer twrp.
If you look in my nh7 stock base thread or my afh account you'll find a tethering mod for tmos nh7 which should work on metros nk2

[Q] Help with going back to stock (from CM11)

Hey, sup?
I need your help, I'm trying to go back to stock firmware on my i747, currently I'm running CM11 latest snapshot.
Background: Some time ago, I accidently erased my imei. Took the phone to a guy who restored it but the phone doesn't work with 3G now, only 2G. So I wanted to try going back to stock firmware to see if that fixes the issue.
I tried downloading the CUEMJB file from here, but it doesn't work (keeps looping the same page) http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/
Can you help me? Also, it is safe what I'm trying to do?
Thank you!

Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you. Yes the IMEI matches.
I was able to download the file.
Unfortunately, the thing didn't went ok. After flashing my phone is unresponsive, black screen, no more boot
If I connect it to the computer at this point, it tries to search for a QHSUSB_DLOAD driver. Not sure what is that, I think I bricked my phone.
I've seen some guides for unbricking by placing a sd card in the phone at boot but so far it haven't worked

Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.

dawgdoc said:
Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.
Click to expand...
Click to collapse
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back

Alright! I just tried the SD card method w/ one of the files in the threads linked. Phone boots!
So it seems my bootloader is bad right?

japi2000 said:
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back
Click to expand...
Click to collapse
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.

dawgdoc said:
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.
Click to expand...
Click to collapse
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?

japi2000 said:
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?
Click to expand...
Click to collapse
That is the stock recovery. If you were successfully running one of the latest CM11 snapshots, you were probably on one of the three 4.4.2 bootloaders ( and modems ), they are NE4, NJ1, and NJ2. This would explain why the MJB (4.3) image you downloaded and flashed would soft brick your phone. It looks like that flash may be responsible for you being back on stock recovery, at best guess. Before anything else, do a factory reset from the stock recovery. This is frequently necessary to boot when going from a CM/AOSP LP rom back to stock.
Since you can get to download mode, I think the best bet would be to install a custom recovery. TWRP for the i747 is here, the top image is flashable with Odin while in download mode. Remember not to reboot from Odin. Instead remove the cable, pull the battery, then boot straight to recovery. Once you have TWRP loaded, boot into recovery and use the terminal emulator in it to determine bootloader and modem with these commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Once you know the version of bootloader and modem you had been on, reflash that version from TWRP you will probably need the file on an external sdcard to do so. After this you can flash your rom of choice from TWRP, stock or otherwise. Since you were having imei issues go with one of enewman's stock roms, as @DocHoliday77 suggested. He can then help you with the imei issues if still necessary. Any other ideas Doc?

Ok, so
Bootloader = I747UCUEMJB
I don't get anything when running getprop | grep version.baseband in the recovery.
This is what I've done so far.
Booted w/ the sdcard trick (bootloader in the sdcard).
Installed twrp
Installed the following files:
AT&T_I747UCUEMJB.zip
d2att_I747UCUEMJB_bootloader.zip
d2att_I747UCUEMJB_modem.zip
d2att_Kernel_Stock_init.d_4_3_MJB_v1.0.zip
That brought the phone to life again (w/ stock 4.3). Then I flashed CM12 from the recovery. All went ok.
Problem is, I still don't have 3G connectivity, only edge.
What would you recommend try next?
Thank you

Alright, I was able to upgrade to UCUFNJ1 for both the bootloader and baseband. Still no 3G. Ideas?

Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Alright thank you

Alright, I'm happy to say that with the help of our fellow DocHoliday77 I was able to solve the issue !
Thanks everyone!

Glad you have it working.
Way to go Doc.

Damn japi2000. You did that quick good job.

Thank you!
I can't believe I went from a almost dead phone to a fully working one in only a few days, even with the 3G/4G working again !
This forum and people are amazing! Thank you!