Strange problems on MDL - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I just bought this s4 its running MDL stock but i just rooted with motochopper then i installed supersu from CF and it told me something about knox so i unistalled all the knox apks on system bit how is that i knew that there was no knox til 4.3 so what the ***k. Another thing i flash in odin philz recovery and always fails to write and using rom manager its sucesful but i cant enter it shows a yellow triangle and in red letter on top saying something about the kernel. And that at&t detect unoficial stuff. So im wondering if this was running 4.3 and downgraded to MDL or was MF3 what can i do??? Or a recovery you guys recomend. And if that fails try to flash stock MDL or MF3?? THANKS
Enviado desde mi SAMSUNG-SGH-I337 mediante Tapatalk

Well I dont think it was downgraded bc mf3 and mk2 which had knox didnt allow you to odin backwards. But I could be wrong. To have knox it would've had to of been upgraded. But knox isn't really a big deal it just voids your warranty with Samsung. As far as the yellow triangle you need to flash the loki doki zip in recovery and it will boot. Loki is a kernel patch for att s4. Some kernels and roms are lokid by the dev but if they're not you have to flash loki after flashing to avoid the unauthorized kernel error

Ok thanks but i cant flash a recovery. Everytime i try in odin it fails. Then i did root and used rom manager to install recovery and was sucesful but i boot in recovery and the yellow triangle appears but the s4 boots fine then. Can you help me install a working recovery in odin or other way. I was about to flash mf3 cause i thought it was running that firmware before i got it.
Enviado desde mi SAMSUNG-SGH-I337 mediante Tapatalk

I wouldn't install mf3, you'd be stuck with safestrap
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 09:25 PM ---------- Previous post was at 09:24 PM ----------
I'd flash MDL back and start over, make sure to take out your sim card and do not use Wi-Fi.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Smae here. Id suggest doing a odin stock image to amdl. And then use the motochopper 1 click that roots u and installs twrp
What ever u do dont ota mf3. You will kick yourself aleast a year if you do

bighleo114312 said:
Ok thanks but i cant flash a recovery. Everytime i try in odin it fails. Then i did root and used rom manager to install recovery and was sucesful but i boot in recovery and the yellow triangle appears but the s4 boots fine then. Can you help me install a working recovery in odin or other way. I was about to flash mf3 cause i thought it was running that firmware before i got it.
Enviado desde mi SAMSUNG-SGH-I337 mediante Tapatalk
Click to expand...
Click to collapse
Check this thread out .... as Easy as 123.... http://forum.xda-developers.com/showthread.php?t=2297033
.....u don't get any easier than this if u update to MF3 or even MK2......
SWYPED_FROM_S4_MF3_REDVENOM

Related

[Q] Bell Galaxy S4 Stock ROM

I have a bell i337m galaxy s4. I installed a google edition rom. Now I need to sell my S4 so i need to go back to stock touchwiz. I can't find anything. I need the touchwiz rom. Please reply as soon as possible!
Grab the firmware for bell here http://forum.xda-developers.com/showthread.php?t=2269304 and flash with Odin. You may find yourself in a boot loop after. To fix boot into recovery and factory reset
As you are rooted running custom recovery you most likely triggered the flash counter. To solve install triangle away and reset the counter before you boot into download mode and use Odin
Sent from my SGH-I337M
mymusicathome said:
Grab the firmware for bell here http://forum.xda-developers.com/showthread.php?t=2269304 and flash with Odin. You may find yourself in a boot loop after. To fix boot into recovery and factory reset
As you are rooted running custom recovery you most likely triggered the flash counter. To solve install triangle away and reset the counter before you boot into download mode and use Odin
Sent from my SGH-I337M
Click to expand...
Click to collapse
I don't know what is wrong with my root either. Superuser is on here. When I go to an that needs root. It says I'm not rooted. Then superuser pops up a notification saying i need to update binary. When I press install I get an error
I rooted like 7 times today. Sti I get the same error
Sent from my GT-I9505G using xda app-developers app
Makbrar3215 said:
I rooted like 7 times today. Sti I get the same error
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
I have superuser but it says I'm not rooted. Should I use the i337m root or GT-I9505G root. Because when I boot it shows i337m. But model number shows up as GT-I9505G. I am so confused!

Restoring sprint gs4 Bloatware help

So, long story short I rooted my sprint gs4 mja and killed some bloatware. Later my phone started overheating and having connection issues. I looked online and people said the remedy to the heat issue was to factory reset so i did. To my horror the problem still existed so I did some research and found out certain bloatware shouldn't be removed because it can cause these symptoms.
So anyway to get those apps back or re-install mja and mf9?
Also I have another small concern I would like an answer for which I cant find.
when I rooted and factory rested my gs4 I tried to install Cyanogenmod on it by using apply update from external storage in stock recovery all I got was errors and it booted me back into recovery. I then booted and stock rom came up.
After this I noticed I had some glitches in stock rom, could these glitchs have come from me trying to install CM from recovery?
Maybe odin back to stock mf9, take mja ota and reroot?
---------- Post added at 02:33 AM ---------- Previous post was at 02:28 AM ----------
You don't install custom roms or recoveries with the stock recovery, for ghat you have to be rooted first, then install custom recovery, search for twrp 2.5.0.2. Tar file and flash with odin, then you will be able to flash things.
matraca said:
Maybe odin back to stock mf9, take mja ota and reroot?
---------- Post added at 02:33 AM ---------- Previous post was at 02:28 AM ----------
You don't install custom roms or recoveries with the stock recovery, for ghat you have to be rooted first, then install custom recovery, search for twrp 2.5.0.2. Tar file and flash with odin, then you will be able to flash things.
Click to expand...
Click to collapse
If you noticed, he said he is in mja meaning knox bootloader, meaning he cant downgrade no more.
But op you can try this
http://forum.xda-developers.com/showthread.php?t=2506562
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
If you noticed, he said he is in mja meaning knox bootloader, meaning he cant downgrade no more.
But op you can try this
http://forum.xda-developers.com/showthread.php?t=2506562
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
That is exactly why I always wait a little before upgrading, until everything gets sorted out. Reminds me of the days qhen I had my e4gt and the whole ICS emmc brick bug
So is it possible for me to flash custom recovery with Odin on mja?
Sent from my SPH-L720 using xda app-developers app
JayMix said:
So is it possible for me to flash custom recovery with Odin on mja?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Yes you can, first root the phone with cf autoroot and then install a custom recovery. Make sure you know what you are doing because MJA is an all new animal. If you mess up you can't just odin MJA back to the phone since we don't have a full tar file of MJA. This means even a soft brick of your phones is a real hassle to recover from. Also, people have reported bootloops and other problems trying to restore backups with the new MJA. Once you have applied the MJA update, the bootloader will prevent you from downgrading the firmware so you can't odin MF9 or older firmware and you can't reapply the update since the update will stop once it sees the MJA bootloader is already installed. Tread carefully, until we have a full tar of MJA that you can use to return to stock after a screw up or brick.

Philz Touch problem! Please help!

I updated my GS4 to rooted (without knox) 4.3 and now i want to flash Sacs Custom rom but i can't i've tried every recovery I could find none work for me even Philz, everyone is saying use that one and I did but when I flash it through odin nothing happens when I try to boot it to recovery the phone simply skips through and reboots( yes it does try to get into recover, the blue text) but if i keep trying it, it'll boot to stock recovery after 2-3 tries (assuming that's a fail safe?) I don't know what i'm doing wrong can anyone help?
Yes i have the drivers (Odin can do anything but get a recovery to stick)
bounddyy said:
I updated my GS4 to rooted (without knox) 4.3 and now i want to flash Sacs Custom rom but i can't i've tried every recovery I could find none work for me even Philz, everyone is saying use that one and I did but when I flash it through odin nothing happens when I try to boot it to recovery the phone simply skips through and reboots( yes it does try to get into recover, the blue text) but if i keep trying it, it'll boot to stock recovery after 2-3 tries (assuming that's a fail safe?) I don't know what i'm doing wrong can anyone help?
Yes i have the drivers (Odin can do anything but get a recovery to stick)
Click to expand...
Click to collapse
Run Odin 'as administrator' and make sure you're flashing the right .tar - philz_touch_5.18.2-jfltespr.tar.md5
leaderbuilder said:
Run Odin 'as administrator' and make sure you're flashing the right .tar - philz_touch_5.18.2-jfltespr.tar.md5
Click to expand...
Click to collapse
Yes i did those and is it possible to downgrade to mf9 and directly flash sacs custom v4 4.3?
bounddyy said:
Yes i did those and is it possible to downgrade to mf9 and directly flash sacs custom v4 4.3?
Click to expand...
Click to collapse
If you can get into recovery now (philz). You can certainly flash Sac's 4.3. If you want the mf9 modem that is in the dev section too. Check out Unknownforce's post
But I suspect you've taken the mja "firmware" and tripped that Knox counter, and if that's the case I dint believe you can Odin back to mf9.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Well my rom was pre rooted and wasn't supposed to have Knox I'll try it and see but is it okay to flash to 4.3 v4 from mf9?
Sent from my SPH-L720 using xda app-developers app
bounddyy said:
Well my rom was pre rooted and wasn't supposed to have Knox I'll try it and see but is it okay to flash to 4.3 v4 from mf9?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
well that didn't workout so i figured out that i shouldnt let my phone reboot after flashing Philz recovery and instead directly force into recovery and it worked but now i need to just flash it thourgh there lol

[Q] Flashed new TWRP now no recovery.

I installed the KOT49H GE ROM on my AT&T SGH-I337 and it runs great. I then decided to see if there was an update to TWRP and I found an updated one and flashed it via goo.im. I later read that this is not the way to do it. Anyway, when I boot into recovery a big yella triangle appears and at&t scolds me for running in authorized firmware. I can boot into download, cancel it and the ROM boots and runs fine.
Under the "about device" page on settings it says the baseband is MK2 (because I flashed that modem). If I look at the boot loader version via android terminal emulator it shows I'm still on MDL.
Any ideas how to get recovery working again?
I am trying to understand the reason why you flashed a recovery.
From your post, it looks like you are using safestrap and deadly venom tool to run GE.
You can flash the MLD files from the tool to get the recovery back.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
insaneretard said:
I found an updated version of TWRP and thought it would be a good idea to update it. I think the problem might be that I didn't use Loki doki before I installed the twrp update. It can't get to the recovery now. Will I mess anything up if I use motochopper? I don't want safestrap because I like the Google Edition ROM and I'm still on the MDL boot loader.
I'm pretty much a newb with this S4. I had my S2 rooted with task650's ROM and understood that better because no locked bootloader
Click to expand...
Click to collapse
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
jmjoyas said:
My bad! I read that you had "MLD" bootloader instead of "MDL" and hence my comment. MLD is a leaked 4.4 firmware.
Motochopper is used to root and I am guessing you still have root. All you need to do is flash a recovery.
http://www.theandroidsoul.com/latest-twrp-recovery-for-att-galaxy-s4-android-4-4-compatible/
This link provides an Odin flashable TWRP.
Click to expand...
Click to collapse
Thanks for helping me out. I tried this yesterday and today with the link you provided. When I try to flash it via odin, it comes up as failed. On my phone, it says "SECURE CHECK FAIL: recovery" in red letters on the download page. Any other ideas?
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You could try grabbing the mdl package, an extracting the recovery from it and flash in Odin or Heimdall. Worst case you flash to mdl and then motochopper it again.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Do i need root to do this? I don't think I even have root any more. I'm running a custom ROM without root access. I tried to use CASUAL to root and install the recovery but it couldn't root it.
You will only need to root again if you go all the way back to stock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Changed recoveries, unauthorized software..

Hey all,
Tried to update the twrp that was on a device that I just got.
Update went fine, reboot into new recovery.. Unauthorized software message..
Does this mean Odin back to MDL stock, re-root and such?
Thanks in advance.
Sent from my GT-I9505G using Tapatalk
You need to flash Loki. . . if you flash a stock (rooted) ROM, you will boot to ROM, then use triangle away app to get rid of the padlock on boot screen. Just remember to flash the Loki zip if you're flashing a ROM that isn't specifically for the jflteatt
---------- Post added at 11:37 AM ---------- Previous post was at 11:00 AM ----------
If you can't get it to bottom after flashing Loki, you'll need to Odin back to stock, reroot and whatnot.
Mystique said:
Hey all,
Tried to update the twrp that was on a device that I just got.
Update went fine, reboot into new recovery.. Unauthorized software message..
Does this mean Odin back to MDL stock, re-root and such?
Thanks in advance.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
The guy above is right. It's loki that you have to flash in recovery. But that issue is because of the the kernel. Loki is a att kernel patch.
So anytime you flash a new rom or kernel by itself just flash the loki doki zip and reboot and all will be well
~Sent From My Insane S4~
So,
I found out that trying to flash philz via Odin would fail, almost immediately; but then the rom would boot..
I was able to loki_run recovery recovery.img from my still working rom.. Then get into the flashed recovery..
Cycle, rinse, repeat a dozen times or so while I was figuring it out.. Before I figured out what was getting me back in..
Sent from my GT-I9505G using Tapatalk

Categories

Resources