Hi, everyone I'm at a lost my S4 has been down for over a month now.
I've tried all the steps in the s4 bricked forums with no luck. I can't do the Kies recovery because it asks for a recovery code I don't have. (I bought the phone 2nd hand)
At this point I'm not even sure which stock rom I need to set the phone back to stock. I believe its a I337MVLUAMG1. I'm trying to run the phone on Aio.
When flashing from odin I usually get a failure. Seems like the Canadian S4 is prone to soft bricking searching the forums.
Currently I have Philz Advanced recovery installed. I'm stuck at Samsung Galaxy S4 logo
with
Kernel is not seandroid enforcing
Set Warranty bit: kernel
Any help of suggestions are gratefully appreciated.
Hey dude. No expert here, but it sounds like u have the new bootloader i.e. Knox. If ur going to do an odin flash to restore it, it's going to have to be at least MK6 firmware (I'm guessing this is the firmware u were on as NC1 just dropped and u said u'd been bricked for a month). Knox won't let u downgrade so if u've been flashing a 4.2 firmware then that's prolly why ur stuck at the boot screen. Good luck chief.
Oh, also, if u can boot into recovery, doing a factory reset and wiping /system couldn't hurt.
blankingblank said:
Hey dude. No expert here, but it sounds like u have the new bootloader i.e. Knox. If ur going to do an odin flash to restore it, it's going to have to be at least MK6 firmware (I'm guessing this is the firmware u were on as NC1 just dropped and u said u'd been bricked for a month). Knox won't let u downgrade so if u've been flashing a 4.2 firmware then that's prolly why ur stuck at the boot screen. Good luck chief.
Oh, also, if u can boot into recovery, doing a factory reset and wiping /system couldn't hurt.
Click to expand...
Click to collapse
Alright thank you thats a step in the right direction. I downloaded: I337MVLUFNC1_880525_REV06_user_low_ship_MULTI and tried flashing it. I'm getting odin failures. I can successful flash a recovery or modem. But flashing an entire ROM from odin fails every time. I'm not sure what stock ROMs will work with my phone. Its a Canadian i337m last time I was able to boot I was on MG1 i believe. I don't know if it matters. But I bricked my phone trying to undo the tmobile AWS work around (I swtiched to Aio).
crayak said:
Alright thank you thats a step in the right direction. I downloaded: I337MVLUFNC1_880525_REV06_user_low_ship_MULTI and tried flashing it. I'm getting odin failures. I can successful flash a recovery or modem. But flashing an entire ROM from odin fails every time. I'm not sure what stock ROMs will work with my phone. Its a Canadian i337m last time I was able to boot I was on MG1 i believe. I don't know if it matters. But I bricked my phone trying to undo the tmobile AWS work around (I swtiched to Aio).
Click to expand...
Click to collapse
U said u had the Knox msg come up when booting right? That means ur bootloader is 4.3 or higher regardless of what baseband ur on (modem). U can find a carrier specific version of the latest firmware at samsung-updates. Extract the tar.md5 and flash under AP in Odin 3.09 after unticking auto reboot and force reboot. If that fails u can try formatting all ur device partitions in recovery. Doubt that last part would help the odin flash stick but it's worth a shot. I use philz and u can format everything from /boot to /firmware_mdm. Like I said, dunno if that'll help but u could try it. Also, using kies on ur PC, u should make sure u have the latest drivers installed. Hope some of that helps
blankingblank said:
U said u had the Knox msg come up when booting right? That means ur bootloader is 4.3 or higher regardless of what baseband ur on (modem). U can find a carrier specific version of the latest firmware at samsung-updates. Extract the tar.md5 and flash under AP in Odin 3.09 after unticking auto reboot and force reboot. If that fails u can try formatting all ur device partitions in recovery. Doubt that last part would help the odin flash stick but it's worth a shot. I use philz and u can format everything from /boot to /firmware_mdm. Like I said, dunno if that'll help but u could try it. Also, using kies on ur PC, u should make sure u have the latest drivers installed. Hope some of that helps
Click to expand...
Click to collapse
Holly Vag thank you! I can now fully boot the phone. I installed Philz recovery and installed Vision X G4. WiFi is not working, and I haven't put my sim card in to see if it'll work with At&t/Aio yet.
Okay next step this is a Canadian Rogers i337m I think. Not sure how to confirm it. But assuming it is. What do I need to do to get wifi running. I see forums saying to install certain kernel and modems for the Canadian version. I'm not sure how to proceed considering I'm trying to use the phone on Aio/At&t, and suggestions?
Thank you, thank you. This is the farthest I've gotten I've been using a SGH-I437Z=Crapola.
crayak said:
Holly Vag thank you! I can now fully boot the phone. I installed Philz recovery and installed Vision X G4. WiFi is not working, and I haven't put my sim card in to see if it'll work with At&t/Aio yet.
Okay next step this is a Canadian Rogers i337m I think. Not sure how to confirm it. But assuming it is. What do I need to do to get wifi running. I see forums saying to install certain kernel and modems for the Canadian version. I'm not sure how to proceed considering I'm trying to use the phone on Aio/At&t, and suggestions?
Thank you, thank you. This is the farthest I've gotten I've been using a SGH-I437Z=Crapola.
Click to expand...
Click to collapse
Lol not sure anything I said helped. I think u must've wiped /firmware or /firmware_MDM right? I only meant to do that if u were going to flash a stock fw as it would replace those parts automatically. I think u lost ur non.hlos.bin file... Flashing a stock fw will bring it back. U can wipe everything again from philz if u want and try an Odin flash again using my instructions from the last post. Also, u want to flash a stock fw that uses the same base as the rom ur planning to flash, i.e. if u restore using a stock KitKat ROM (NC1), then ur gonna wanna make sure u flash a KitKat rom afterwards as the Knox BL won't let u downgrade.
As for which carrier fw to choose, the hardware is the same in all the Canadian variants, so any will work, although I think u were on a bell fw originally cuz of the MG1 suffix.
blankingblank said:
Lol not sure anything I said helped. I think u must've wiped /firmware or /firmware_MDM right? I only meant to do that if u were going to flash a stock fw as it would replace those parts automatically. I think u lost ur non.hlos.bin file... Flashing a stock fw will bring it back. U can wipe everything again from philz if u want and try an Odin flash again using my instructions from the last post. Also, u want to flash a stock fw that uses the same base as the rom ur planning to flash, i.e. if u restore using a stock KitKat ROM (NC1), then ur gonna wanna make sure u flash a KitKat rom afterwards as the Knox BL won't let u downgrade.
As for which carrier fw to choose, the hardware is the same in all the Canadian variants, so any will work, although I think u were on a bell fw originally cuz of the MG1 suffix.
Click to expand...
Click to collapse
You helped me quite a bit. Thank you. I reflashed Philz recovery with odin, then installed Vision X. I'm not sure what MDM or non.hlos.bin fiels are for. I don't want to use Odin with this phone. Searching the forums seems like this phone and odin don't get along when flashing a full ROM. I'd prefer to do all flashing using recovery. Now I just need to find the right stock zip.
crayak said:
You helped me quite a bit. Thank you. I reflashed Philz recovery with odin, then installed Vision X. I'm not sure what MDM or non.hlos.bin fiels are for. I don't want to use Odin with this phone. Searching the forums seems like this phone and odin don't get along when flashing a full ROM. I'd prefer to do all flashing using recovery. Now I just need to find the right stock zip.
Click to expand...
Click to collapse
No problem. Ya I guess the recovery zips could work just as well as the Odin tar.md5's would. I've just never used a recovery to flash a stock rom before.
Fwiw I have the same phone as u and have used Odin plenty, with positive results, although I've heard that peoples experiences with it vary a great deal. Having the right USB drivers installed on ur PC is key tho if u do use it.
Rom or Firmware?
crayak said:
Hi, everyone I'm at a lost my S4 has been down for over a month now.
I've tried all the steps in the s4 bricked forums with no luck. I can't do the Kies recovery because it asks for a recovery code I don't have. (I bought the phone 2nd hand)
At this point I'm not even sure which stock rom I need to set the phone back to stock. I believe its a I337MVLUAMG1. I'm trying to run the phone on Aio.
When flashing from odin I usually get a failure. Seems like the Canadian S4 is prone to soft bricking searching the forums.
Currently I have Philz Advanced recovery installed. I'm stuck at Samsung Galaxy S4 logo
with
Kernel is not seandroid enforcing
Set Warranty bit: kernel
Any help of suggestions are gratefully appreciated.
Click to expand...
Click to collapse
that have tried to install rom or firmware?
Pika71 said:
that have tried to install rom or firmware?
Click to expand...
Click to collapse
I have it booting into Maple Leaf now. Still trying to figure out if my performance issues are kernel, modem, or maybe its just KitKat?
My next phone is going to be a developer edition.
oh...
crayak said:
I have it booting into Maple Leaf now. Still trying to figure out if my performance issues are kernel, modem, or maybe its just KitKat?
My next phone is going to be a developer edition.
Click to expand...
Click to collapse
is the kit kat is very little battery
Related
Hi all,
I think I have soft bricked my S4 i337m rogers Canadian variant.
I had rooted / unlocked the bootloader with motochopper successfully.
- I am using CWM
First thing I tried to do was backup the phone onto the external SD which would not work so I just went onto the next step.
I tried flashing a ROM onto the phone after doing phone restore and clearing cache. All installed correctly (apparently) and now when I boot up the phone the Samsung logo will appear for about 5 seconds then the phone will go black and try to boot up again.
The good:
- i have access the recovery mode still
The bad:
- no recovery made for the phone
- seems to be boot looping
As a side not I have tried installing a couple other ROMs which all result in the same issue.
Is there anything that can possibly be done?
I would happily put the stock ROM back on the phone.
All help would be greatly appreciated!
Rob.
9 times out of 10 a factory reset will get you out of a boot loop. Do that in recovery and reboot.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Robby29 said:
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Click to expand...
Click to collapse
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
kiru said:
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
Click to expand...
Click to collapse
Okay great I will try these. Does the kernel have to be specific to the ROM?
Robby29 said:
Okay great I will try these. Does the kernel have to be specific to the ROM?
Click to expand...
Click to collapse
The kernel is specific to your device. so you would use the i337M kernel.
So the procedure would be flash the rom of your choice, then before you boot flash YOUR i337M kernel, it will boot.
Good luck.
And make sure you do not flash a rom for the i9500 as you will hard brick
Also,
Make sure you choose the right i337m kernel. ie. a TouchWiz kernel for TW Roms and an AOSP kernel for CM10.1/AOSP Roms.
You should be able to:
remove your sdcard,
format it to fat32,
download the correct rom and kernel for you i337m to your freshly formatted sdcard,
put the card back into your phone,
boot into recovery,
install ROM zip from ext-sdcard,
install Kernel zip from ext-sdcard,
reboot.
phew....sounds like a lot of steps but not really I guess.
we good up in here....
Soft Brick S4
TheAxman said:
we good up in here....
Click to expand...
Click to collapse
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
car154 said:
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
Click to expand...
Click to collapse
Thanks for posting this. I hope many people read it. Anyone who flashes needs to know how to return to stock before they start flashing roms. You will need it someday!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi there ... yes I've done something wrong and would like to try to fix it without going to Vodafail to get them to berate me.
I was trying to install PhilZ Touch recovery but was having trouble with Odin (1.85, and 3.07 I was trying) and finally gave up and just wanted to make a normal boot but the dreaded firmware message has come up.
I've had a quick search & read and it seems that I need to flash (with Odin) a new stock ROM.
It's getting late here so I'm not going to try anything more without a lot of advice and reading.
So any suggestions please?
I'm in Australia with Vodafone, phone is about two or three months old. i9505.
Cam you get into download mode? Turn it off then press home, power and volume down at the same time, if you can download a stock firmware for your device this can be found at Sam mobile. Then flash it with Odin. Always use the latest version.
Sent from my GT-I9500 using Tapatalk 4 Beta
BillzillaAus said:
Hi there ... yes I've done something wrong and would like to try to fix it without going to Vodafail to get them to berate me.
I was trying to install PhilZ Touch recovery but was having trouble with Odin (1.85, and 3.07 I was trying) and finally gave up and just wanted to make a normal boot but the dreaded firmware message has come up.
I've had a quick search & read and it seems that I need to flash (with Odin) a new stock ROM.
It's getting late here so I'm not going to try anything more without a lot of advice and reading.
So any suggestions please?
I'm in Australia with Vodafone, phone is about two or three months old.
Click to expand...
Click to collapse
Hi,
Stock firmwares are HERE
Try ODIN 3.04 as well
Thanks guys, I'm downloading http://www.hotfile.com/dl/227186782/ebf4c32/I9505XXUBMEA_I9505XSABME4_XSA.zip.html now and will try it when it's finished.
And yes the phone will go into download mode okay.
I also had a think about it last night and I'm not against putting a different ROM into it, any suggestions?
Okay trying to flash that rom with Odin failed.
Where do I go from here please? Like I mentioned, I'm more than happy to try a custom rom.
Hmmmm just tried flashing CWM recovery ..... that failed as well.
Help!!
Know its probably a stupid question but did you root the phone before trying to install Phillz recovery?
If not, try CF-Autoroot, then try Phillz recovery. If you can't get these flashed you may have corrupted your partition table. Here's a link to the PIT file you need - http://forum.xda-developers.com/showthread.php?t=2265477 (Make sure you get the right one or you can say bye bye to your toy- I believe you should have an I9505)
Read this, then go and try again....
Cheers.... :good:
ultramag69 said:
Know its probably a stupid question but did you root the phone before trying to install Phillz recovery?
If not, try CF-Autoroot, then try Phillz recovery. If you can't get these flashed you may have corrupted your partition table. Here's a link to the PIT file you need - http://forum.xda-developers.com/showthread.php?t=2265477 (Make sure you get the right one or you can say bye bye to your toy- I believe you should have an I9505)
Read this, then go and try again....
Cheers.... :good:
Click to expand...
Click to collapse
Yep I flashed CF-Autoroot a couple of months ago without too many problems, I'll try it again.
Which version of Odin should be best to use?
Ah! Flashing the pit file thingy did it, THANKS!!!
BillzillaAus said:
Ah! Flashing the pit file thingy did it, THANKS!!!
Click to expand...
Click to collapse
No problem, just remember though that flashing the pit file is no small thing... If that stuffs up or you have a corrupt pit file you can actually hard brick your device... It really is the final step before giving it back to Samsung to fix...
Glad it all worked out and cheers....:good:
Yes I'll try to not need to do that again!
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
tr10 said:
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
Click to expand...
Click to collapse
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
xBeerdroiDx said:
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
Click to expand...
Click to collapse
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
tr10 said:
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
Click to expand...
Click to collapse
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the advice, I have done that countless times. I'm hoping that it changes one of these times though.
I took your advice regarding re-flashing the image and ticking the bootloader update option, odin stated it was successful and auto-rebooted. I pulled the battery and tried to enter recovery, no cigar.
Perhaps try the Heimdall route: http://forum.xda-developers.com/showthread.php?t=2374441
When attempting to flash TWRP recovery, my phone says in the top right hand corner:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enabled
START [224, 1440]
SECURE CHECK FAIL: recovery
Don't know what that means.
I haven't tried the heimdall method yet, not sure if I wanna give it a shot because it seems a lot more complex only to accomplish the same thing odin would. I can imagine something is stopping odin from putting a bootloader, or kernel. That same thing would stop heimdall. But, I have no idea what I'm talking about. Waiting to hear more advice before I make the hole I dug deeper.
Thank you for your time guys.
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Febby said:
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
xBeerdroiDx said:
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Click to expand...
Click to collapse
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
tr10 said:
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
Click to expand...
Click to collapse
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Febby said:
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Aou said:
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Click to expand...
Click to collapse
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Febby said:
I actually considered switching to a ONE today.
Click to expand...
Click to collapse
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
Either way. Also, if one fails, try the other of course.
Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
I converted the .img to a .tar and I sadly had the same results =( Thank you for the idea though, definitely helped.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
Thank you, I attempted to reflash the stock kernel included in the MDL package. No avail. Same problem. Good advice though!
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
I just reflashed the stock kernel, no cigar =( It is very strange to me that I can't get the phone to respond to anything other than download mode. Especially considering that I odin'd to stock. I'm starting to think I made it worse by going back to stock after flashing slimbean's weekly update.
Thank you for your time guys, keep the ideas coming, I'm definitely trying to come up with my own ideas.
I have so far done the following:
Odin'd MDL, MDB, Stock Kernel, Stock Recovery (All through download mode, as I don't have access to recovery.)
I've also tried to odin TWRP but I fail in Odin since download mode blocks the illegal recovery.
Thank you again for your time.
tr10 said:
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Click to expand...
Click to collapse
Im not so sure how everyone just over looked this but the rom in that link is for the att S3. So you flashed an S3 rom to your S4.
D2att is the s3 for att.
Jflteatt is the att variant.
http://www.slimroms.net/index.php/downloads/all/viewcategory/620-jflteatt
Thats the correct link to weekly roms for slim rom for our device. your partitions might just be corrupted in case maybe having a jtag or using the pit file for MDL would fix? :/ im not an expert haha just observations.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 06:01 PM ---------- Previous post was at 05:57 PM ----------
xBeerdroiDx said:
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Click to expand...
Click to collapse
You sure? On the att one majority of devs dont post on the att htc one section but eather "HtC one" section since all roms work vice versa on that phone international roms > works on all models of the one.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
hi all. need help
i've been playing with different roms for couple of years now on different phones and did not have any problems.
till now that is ....
i have installed Omega 21.1, but from time to time phone would lose gsm data connection so i decided to flash something else.
installed [ROM]KOT49H【4.4.2】AOSP official Google Edition and it was good.
for some, God knows what reason, wanted to try Omega19 (4.3). installed fine but sound was broken. when ever phone used any kind of sound it would start flashing or would freeze or something. Flasing any other rom did not help. and for some reason it does not let me change modem with odin.
Last modem i have installed is XXUEMJ5.
tried to do restore using [GUIDE] Unroot/Unbrick, Flash official stock firmware on Galaxy S4 GT-I9500 & I9505 but Odin would fail with Auth error
tried with Odin 3.47, and 3.07
now i still can install rom but stops in logo loop. tried both Omega and google edition.
pls help
gec said:
hi all. need help
i've been playing with different roms for couple of years now on different phones and did not have any problems.
till now that is ....
i have installed Omega 21.1, but from time to time phone would lose gsm data connection so i decided to flash something else.
installed [ROM]KOT49H【4.4.2】AOSP official Google Edition and it was good.
for some, God knows what reason, wanted to try Omega19 (4.3). installed fine but sound was broken. when ever phone used any kind of sound it would start flashing or would freeze or something. Flasing any other rom did not help. and for some reason it does not let me change modem with odin.
Last modem i have installed is XXUEMJ5.
tried to do restore using [GUIDE] Unroot/Unbrick, Flash official stock firmware on Galaxy S4 GT-I9500 & I9505 but Odin would fail with Auth error
tried with Odin 3.47, and 3.07
now i still can install rom but stops in logo loop. tried both Omega and google edition.
pls help
Click to expand...
Click to collapse
Hi,
Once you have installed a TW 4.4.2 ROM , it installs the latest knox bootloader.
At that point , you cannot downgrade your firmware.
You said you installed [ROM]KOT49H【4.4.2】AOSP official Google Edition and it was good.
Your best bet is to re-install that.
As for the modem , there is a technique which you have to try:
Look HERE
That should help.
BTW , I edited your title
thx. will try that and report back.
nope, still stuck @ logo loop
not sure what more combination to test
tried Omega 21.1 with
Bootloader -> BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 and
Modems -> CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5
but now it does not get to the logo. shows samsung logo and than screen goes blank.
gec said:
tried Omega 21.1 with
Bootloader -> BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 and
Modems -> CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5
but now it does not get to the logo. shows samsung logo and than screen goes blank.
Click to expand...
Click to collapse
Hi,
Did you try the GE ROM?
gec said:
tried Omega 21.1 with
Bootloader -> BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 and
Modems -> CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5
but now it does not get to the logo. shows samsung logo and than screen goes blank.
Click to expand...
Click to collapse
Try to reFlash those Files with Odin then Boot into TWRP mode and Do a full wipe and Install Omega (Inside Omega file there's Fullwipe , Click that and Setup the apps you need) then reboot .Make sure that You have a TWRP recovery^
malybru said:
Hi,
Did you try the GE ROM?
Click to expand...
Click to collapse
nope. cant find anything with that name. could you link it please?
Repulsa said:
Try to reFlash those Files with Odin then Boot into TWRP mode and Do a full wipe and Install Omega (Inside Omega file there's Fullwipe , Click that and Setup the apps you need) then reboot .Make sure that You have a TWRP recovery^
Click to expand...
Click to collapse
thx.
tried it. no success after samsung logo just goes black.
gec said:
nope. cant find anything with that name. could you link it please?
Click to expand...
Click to collapse
Hi,
You said you tried the [ROM]KOT49H【4.4.2】AOSP official Google Edition ,and it worked .
So I figured to try and re-install that one.
The other thing you must do between flashing different ROMS is a full wipe (Cache and data)
yes. that was first thing i tested. at best i get the logo loop.
and yes, i do full data wipe before and after reinstallation of the new rom.
cache wipe only whe requested but in this case done that to.
is there a way to see a boot log or something to see where and why booting stops?
gec said:
yes. that was first thing i tested. at best i get the logo loop.
and yes, i do full data wipe before and after reinstallation of the new rom.
cache wipe only whe requested but in this case done that to.
is there a way to see a boot log or something to see where and why booting stops?
Click to expand...
Click to collapse
The best thing you can do is flash the entire 4.4.2 stock rom via odin.And start from scratch(Recovery/Custom rom) Since you already flashed the newestbootloader (from OMEGA file) .This mean your knox is now triggered and your warranty is now void 0x01.
gec said:
yes. that was first thing i tested. at best i get the logo loop.
and yes, i do full data wipe before and after reinstallation of the new rom.
cache wipe only whe requested but in this case done that to.
is there a way to see a boot log or something to see where and why booting stops?
Click to expand...
Click to collapse
Hi,
Perhaps you should try to find the latest test stock 4.4.2 firmware ( I9505XXUFNA1) and flash it in odin.
Wipe data and cache before and after flashing.
And then wait for the official update.
At least you should have a phone you can use.
following http://forum.xda-developers.com/showthread.php?t=2265477
i've found that there is 4.3 stock image I9505XXUEMKF. downloaded it and tried to install but that did not work.
now this is a noob question but is there a speciffic bootloader, modem or something else i need to flash before flashing this image?
or should i search for 4.4.2 version?
thx
flashing stock 4.3 on current bootloader/modem combination gives me Fail from Odin and Sw. Rev. Check Fail error on the phone.
gec said:
flashing stock 4.3 on current bootloader/modem combination gives me Fail from Odin and Sw. Rev. Check Fail error on the phone.
Click to expand...
Click to collapse
I believe malybru already answer that for you .Thread and Stop experimenting with your Phone because there's a chance that you might bricked your Device or end up with no IMEI.. and Your asking for help/Solution mate so follow their instruction . If not feel free to send your Phone to customer Service for repair.( and Be aware that your warranty is already voided unless your Country is part of EU so Rooting and Flashing don't void your warranty)
Repulsa said:
I believe malybru already answer that for you .Thread and Stop experimenting with your Phone because there's a chance that you might bricked your Device or end up with no IMEI.. and Your asking for help/Solution mate so follow their instruction . If not feel free to send your Phone to customer Service for repair.( and Be aware that your warranty is already voided unless your Country is part of EU so Rooting and Flashing don't void your warranty)
Click to expand...
Click to collapse
So what you mean that if you leave in a country that is part of EU, It doesn't matter if KNOX is triggered? (I life in Holland btw)
KingOfDope said:
So what you mean that if you leave in a country that is part of EU, It doesn't matter if KNOX is triggered? (I life in Holland btw)
Click to expand...
Click to collapse
Click the link on EU mate . And start reading even my provider said that if the knox is already triggered, My phone still have warranty for 2 years as long its a hardware/system problem. But if i break the glass on my phone and such then i dont have any warranty for that..and must pay them for a repair.
Sent from Hell ��
Repulsa said:
I believe malybru already answer that for you .Thread and Stop experimenting with your Phone because there's a chance that you might bricked your Device or end up with no IMEI.. and Your asking for help/Solution mate so follow their instruction . If not feel free to send your Phone to customer Service for repair.( and Be aware that your warranty is already voided unless your Country is part of EU so Rooting and Flashing don't void your warranty)
Click to expand...
Click to collapse
ah, my bad. for some reason i was reading 4.4.2 as 4.2.2
i did follow all other instructions, and i thank you all for them, but still not sure where to go from here.
i know i should stick to 4.4.2 firmware but need to check somehow if bootloader/modem combination that i've install is actually installed.
gec said:
ah, my bad. for some reason i was reading 4.4.2 as 4.2.2
i did follow all other instructions, and i thank you all for them, but still not sure where to go from here.
i know i should stick to 4.4.2 firmware but need to check somehow if bootloader/modem combination that i've install is actually installed.
Click to expand...
Click to collapse
If you already flash the Bootloader from Omega then you can no longer downgrade to 4.3 stock , that's why your Getting Fail (Auth) in Odin Flash the 4.4.2 stock Leak rom for now then if you consider flashing a Custom Rom then ,flash the philz recovery 6.09.2 or TWRP (Dont forget to Nandroid backup EFS and such and then DO A CLEAN WIPE by Wiping cache, dalvik cache data and system) and From recovery flash any Custom rom you like. (no need to root your phone, Your phone will be rooted after flashing any custom rom . So goodluck
So, first,
Thanks all in advance.. You are amazing.. I, and so many others have learnt so much from you and your support.
Now,
I have a Canadian n900w8
http://www.mrcrab.net/viewstockrom/10688-sm-n900w8.html
I was so happy at that ROM,and was playing around.. Learning.. And ran into problems..
I made a stupid mistake, really.. Now I don't know how to get out..
I installed a 4.4.4 boot loader.. And flashed with Phil's, back to my 4.4.2 fine, was testing.. So ten I tried a 4.4.4 ROM, and the boot loader.. Worked.. And then some how I lost my recovery, now no matter what I do I can't get a recovery to load.. I have the ROM working, except the modem does work.. Its rooted.. And I can flash a little with flashify, or Odin.. But there are only att2 recoveries.. For 4.4.4 and any TLS recoveries are for 4.4.2..
Any help would be appreciated.. Thanks all in advance..
I already know I'm a noon, no sence reminding me, that's why I'm here..
as far as i know i can still odin back to my normal firmware,
is that correct?
it's been 3 days, i've been trying to download the right one, but most of the mirrors are brokens..
I'm currently Downloading at 35k from one.. so if it's just that simple,
I'll post back so people know..
There seems to be allot of confusion about bootloaders...
as far as i understand though, the one i flashed witih wasn't locked, so..
I think I can still odin to stock..
GhostCyber said:
as far as i know i can still odin back to my normal firmware,
is that correct?
it's been 3 days, i've been trying to download the right one, but most of the mirrors are brokens..
I'm currently Downloading at 35k from one.. so if it's just that simple,
I'll post back so people know..
There seems to be allot of confusion about bootloaders...
as far as i understand though, the one i flashed witih wasn't locked, so..
I think I can still odin to stock..
Click to expand...
Click to collapse
1. Download and unzip the latest firmware for your device: HERE.
2. Remember untick autoreboot in ODIN. Wait till the flash finish. Reboot your device in Recovery Mode and Wipe data/Factory reset your device. Reboot now normally.
3. Install this APPhttps://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and take a look the part that tells "BOOTLOADER" for clarify things then.
Thanks.
Joku1981 said:
1. Download and unzip the latest firmware for your device: HERE.
2. Remember untick autoreboot in ODIN. Wait till the flash finish. Reboot your device in Recovery Mode and Wipe data/Factory reset your device. Reboot now normally.
3. Install this APPhttps://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and take a look the part that tells "BOOTLOADER" for clarify things then.
Click to expand...
Click to collapse
Thanks,
Like I said I have been trying to do that, but i apreciate you conferming it will work..
unfortunately, samMobile has just broken links to the rom...
I'm on my forth attempt, downloading froma source with 45k...
Why sammobiles got broken dl's I don't know, but it really has made this experience draw out.
Thanks Again,
Peace.
thanks man. everything worked out, thanks for the reassurances, bricked stuff is scary...
for everyone else with a telus note...
i spent 3 days trackingn the stock firmware, so i'm uploading it to a site, and will post it here sometime soon..