Hello all!
So I bought a SGH M919 s4 off craigslist for 150 knowing that it wouldn't boot past the Samsung galaxy s4 boot screen, Thinking it would be an easy fix by flashing the stock firmware through odin. Well that's not the case, I've tried just about everything I am capable of...
1.Both odin 3.0 7 and odin 3.0 9 both flash and the device passes but on the boot screen it says booting recovery and just sticks there, It stuck on that over night so I am being patient.
2. I've tried flashing 4.3 which fails right away leading me to believe the phone was updated to 4.4.2 at some point in time.
3. It wont let me boot into stock recovery or I've even tried flashing TWRP, CWM and it pass's but still will not let me boot into those recovery's either.
4. Tried rooting the phone a couple times and that passes in odin but does nothing after that.
5. I ve tried different phone cables, I haven't tried a different computer yet.
6. The only thing I can get into on the phone is download mode and it says this on the screen
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTYVOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: enable
eMMC BURST MODE enable
I don't remember seeing those last two things on the list normally if I can recall. Any help will be greatly appreciated and possibly a donation if we can get this thing fixed. Thanks.
Repartition it with the pit file while youre installing the firmware.
Last 2 strings are normal.
Sent from my SGH-M919 using XDA Premium 4 mobile app
ShinySide said:
Repartition it with the pit file while youre installing the firmware.
Last 2 strings are normal.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, Do you know where the pit file can be found or what do I write in the pit file box?
Ok so I pulled the pit file from another T-Mobile s4 I have and flashed that with the stock firmware and that didn't work. The phone I pulled the pit file from is on 4.3 still so I'm assuming that's why it didn't work???
Quickvic30 said:
Ok so I pulled the pit file from another T-Mobile s4 I have and flashed that with the stock firmware and that didn't work. The phone I pulled the pit file from is on 4.3 still so I'm assuming that's why it didn't work???
Click to expand...
Click to collapse
Na that wouldnt matter. Your pit file is for your partition layouts. Which dont ever change.
I really cant think of anything else of why you can't get into recovery or boot the phone with everything you've tried. You might just need to Jtag the device
Sent from my SGH-M919 using XDA Premium 4 mobile app
ShinySide said:
Na that wouldnt matter. Your pit file is for your partition layouts. Which dont ever change.
I really cant think of anything else of why you can't get into recovery or boot the phone with everything you've tried. You might just need to Jtag the device
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help, I might jtag it or just try to find a used motherboard :laugh:
Quickvic30 said:
Thanks for the help, I might jtag it or just try to find a used motherboard :laugh:
Click to expand...
Click to collapse
The OP mentions that you tried flashing 4.3 and you speculated if it had been updated to 4.4.2. Just out of curiosity, have you tried flashing the stock 4.4.2 firmware?
lordcheeto03 said:
The OP mentions that you tried flashing 4.3 and you speculated if it had been updated to 4.4.2. Just out of curiosity, have you tried flashing the stock 4.4.2 firmware?
Click to expand...
Click to collapse
Yes I've been to flashing 4.4.2 and it passes Odin. I think maybe you meant have I tried flashing 4.2.2? I have not tried flashing 4.2.2 firmware yet, I might try that but 4.2.2 didn't have the Knox counter did it?
Sent from my SM-G900A using XDA Free mobile app
Quickvic30 said:
Yes I've been to flashing 4.4.2 and it passes Odin. I think maybe you meant have I tried flashing 4.2.2? I have not tried flashing 4.2.2 firmware yet, I might try that but 4.2.2 didn't have the Knox counter did it?
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
No, I meant 4.4.2. It was a dumb question, but sometimes it's the simple things you overlook. Like I said, the OP only said you tried flashing MK2. You won't be able to flash anything pre-KNOX so there's no need in wasting the time downloading the MDL firmware.
An idea would be to power the phone off, boot straight to download mode, flash NB4, pull the battery when it's complete, boot straight back to download mode and re-flash NB4. I know that you have to do that sometimes for the modem to stick, perhaps you could try that with the firmware itself. Hey, worth a shot. Good luck.
lordcheeto03 said:
No, I meant 4.4.2. It was a dumb question, but sometimes it's the simple things you overlook. Like I said, the OP only said you tried flashing MK2. You won't be able to flash anything pre-KNOX so there's no need in wasting the time downloading the MDL firmware.
An idea would be to power the phone off, boot straight to download mode, flash NB4, pull the battery when it's complete, boot straight back to download mode and re-flash NB4. I know that you have to do that sometimes for the modem to stick, perhaps you could try that with the firmware itself. Hey, worth a shot. Good luck.
Click to expand...
Click to collapse
I think I might have tried flashing twice in a row but I'll try it again since I haven't tried that since I've flashed the pit file. Thanks for the tip and I'll report back after the double flash.
Sent from my SM-G900A using XDA Free mobile app
So I flashed it, pulled the battery and flashed it again and still the same thing......:sigh: lol Time to look for another wrecked phone for spare parts
Bought a phone off cl with a cracked screen and swapped the motherboard into the phone and it works like a champ now! :thumbup:
Sent from my SM-G900A using XDA Free mobile app
Related
I wanted to try an AKOP ROM or two on my completely stock, never rooted Note 2 running the OTA UCALK7 update. I followed the guide here (flash the SU injected stock UCALJ2 image) to root and now my note gets stuck at the Samsung logo. I have tried the following:
Downloaded the completely stock UCALJ2 unrooted image and flashed via ODIN.
Tried flashing both stock and rooted ROMs on another computer using the stock USB cable.
Flashed CWM touch via ODIN after flashing rooted UCALJ2 image, it can boot to CWM but fails miserably most likely to the lack of root.
My guess is it's bricked because sammy closed the root hole in the UCALK7 update and flashing back to rooted UCALJ2 isn't enough to bypass the patched exploit. Is there an ODIN flashable complete UCALK7 image that I can try (I've looked to no end, all I can find are rooted zips flashable via CWM) or am I really up the creek?
Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.
shakabra said:
Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.
Click to expand...
Click to collapse
Thanks but I can get into Odin and flash the stock ROM just fine. It then reboots and gets stuck at the Samsung logo.
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
The three finger salute lol:thumbup:
Sent from my GT-N7105 using Tapatalk 2
twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks - I actually figured that part out since my second post. The phone boots after the factory reset however I don't get phone/data service. I've since tried flashing the two AT&T modems I could find, atti317ucalj2modemfixed.zip and ATT K7 Modem - Baseband.zip. Neither resolve the issue.
Cheack ur apn
Sent from my SGH-I317 using xda premium
twanskys204 said:
Cheack ur apn
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks but I can't even enter the network configuration settings - it tells me to insert a SIM. My SIM is in the phone.
I'm having other problems too which I think are partition related. Apps are acting funny, saying there isn't space on the phone (dropbox can't download anything, etc). I'm trying to get TriangleAway installed so I can just RMA it but I can't even download it to my phone. Also a CWM fix permissions fails even though I grant it root access.
It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium
twanskys204 said:
It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
I know what you're saying, I'm definitely using the right file and process. I'm a pretty seasoned veteran when it comes to rooting/odin/RSD/fastboot, etc. I've run custom ROMs on dozens of phones since the G1. What's happening to me is apparently not a common failure with the note 2 or GS3. Is there a PIT file available for the AT&T Note 2? I see one for the Verizon Note 2 but I wouldn't dare try to flash that.
There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium
twanskys204 said:
There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Yeah, it's a tar file I'm flashing through Odin, got it from SamsungUpdates: Samsung-Updates.com-SGH-I317_ATT_1_20121005095854_bpaaavv07o.
I also tried flashing the stock ROM in deodex'd zip form after I got a custom recovery on there, still no dice. The non-functioning modem and lack of proper root/storage affects both Sammy and CM/AKOP based ROMs. I don't know about the modem part but I've seen weird things like this when the NAND starts going bad and things written to it don't "stick." I don't think that's the case here since it's only on its 4th or 5th flash. More than likely the latter problem is a file system issue. I have no idea about the radio.
I'm going to try and exchange it tomorrow. At least I got the flash count cleared and I'm back on a stock ROM (with the same problems).
We assume no responsibility or accountability for any damage that may occur from flashing these modems. As with all device modifications the user assumes all risk involved.
Thanks to the following people who have helped contribute along the way: @DirtyOldMan @celtichazard
Please reach out to Myself and @AlEjAnDrO812 with any request and we will continue to do our best for the community.
HAPPY FLASHING!
Click Here For all Canadian/Us Carriers Modems
Omg...work on M919 Tmobile US?
Sent from my SGH-M919 using Tapatalk 2
epsix said:
Omg...work on M919 Tmobile US?
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
No reason why it shouldn't! AWS is enabled and unlocked on most that are posted
Sent from my SGH-I337M using Tapatalk 2
What does aws do for us on T-Mobile?
Sent from my GT-I9505G using xda app-developers app
roblxskye said:
What does aws do for us on T-Mobile?
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
I strongly recommend reading the main thread but basically Advanced Wireless Services generally refers to the 1700/2100MHz frequency band pairing in the U.S. that will be used for T-Mobile USA's 3G UMTS network
Sent from my SGH-I337M using Tapatalk 2
Anybody who had luck with MG1 modem?
I tried to flash the MG1 modem from the tread using mobile odin (untar the MG1.tar, flash modem.bin using modem2 option). When I rebooted the baseband under settings/about was unknown and I couldn't get any reception. What am I doing wrong?
Im kinda confused, sorry but as far as I know there no updates for t mobiles modem/radio the only one I know from tmobile id currently is M919UVUAMDL? Many said if you flash others carrier modem/radio your phone gonna be bricked.
Please tell me that I can flash all these radio/modems it would make mr love my tmobile S4 even more. :thumbup:
Sent from my SGH-M919 using Tapatalk 2
onurd said:
I tried to flash the MG1 modem from the tread using mobile odin (untar the MG1.tar, flash modem.bin using modem2 option). When I rebooted the baseband under settings/about was unknown and I couldn't get any reception. What am I doing wrong?
Click to expand...
Click to collapse
Try re flashing your kernel of choice... If that doesn't work you'll have to stay on the modem specific to your carrier 1337m don't have any issues flashing international modems so I don't see why it wouldn't work.
Sent from my SGH-I337M using Tapatalk 2
2Tone5 said:
Try re flashing your kernel of choice... If that doesn't work you'll have to stay on the modem specific to your carrier 1337m don't have any issues flashing international modems so I don't see why it wouldn't work.
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
I tried to re-flash using ODIN 3.07, and I get an error saying that the C++ runtime crashed. I wonder whether the file is corrupt (I have re-downloaded MG1.tar, still same problem).... Very odd..
Somewhat, mobile odin broke my CWM recovery as well during this process. When I try to reboot into recovery to flash the kernel, the phone simply reboot after showing th small blue rebooting recovery text. So, I had to reflash the recovery through desktop odin again... Anyhow, long story short, I have reflashed google play edition 4.2.2 kernel that I was using, and still cannot get any reception (modem section still unknown) with the MG1 modem file...
onurd said:
I tried to re-flash using ODIN 3.07, and I get an error saying that the C++ runtime crashed. I wonder whether the file is corrupt (I have re-downloaded MG1.tar, still same problem).... Very odd..
Somewhat, mobile odin broke my CWM recovery as well during this process. When I try to reboot into recovery to flash the kernel, the phone simply reboot after showing th small blue rebooting recovery text. So, I had to reflash the recovery through desktop odin again... Anyhow, long story short, I have reflashed google play edition 4.2.2 kernel that I was using, and still cannot get any reception (modem section still unknown) with the MG1 modem file...
Click to expand...
Click to collapse
That's a first for me.... never heard of these issues... . try downloading the MDL unlocked zip extracting it and using odin to flash the bin file
Sent from my SGH-I337M using Tapatalk 2
Make sure you're following the instructions in the op exactly... it's hard for me to help if you start experimenting
Sent from my SGH-I337M using Tapatalk 2
2Tone5 said:
Make sure you're following the instructions in the op exactly... it's hard for me to help if you start experimenting
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
I did follow the Mobile Odin instructions.
Anyhow, now even after flashing the original standalone MDL modem through desktop odin, I have no baseband.... Kind of sucks I will try to go back to fully stock with the original ODIN package and retry later on. Hope this will fix my modem...
onurd said:
I did follow the Mobile Odin instructions.
Anyhow, now even after flashing the original standalone MDL modem through desktop odin, I have no baseband.... Kind of sucks I will try to go back to fully stock with the original ODIN package and retry later on. Hope this will fix my modem...
Click to expand...
Click to collapse
Sorry I thought you had said you went into recovery to flash the modem at first my bad
Going back to original firmware through odin always fixes problems that you can count on... I've bricked so many Samsung devices in my day ... flashing stock firmware works
Sent from my SGH-I337M using Tapatalk 2
2Tone5 said:
Sorry I thought you had said you went into recovery to flash the modem at first my bad
Going back to original firmware through odin always fixes problems that you can count on... I've bricked so many Samsung devices in my day ... flashing stock firmware works
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
That's odd.. I though the flash the original firmware would fix the baseband problem but I still have "unknown" baseband. I might've screwed this one up royally... Any ideas how to fix this?
onurd said:
That's odd.. I though the flash the original firmware would fix the baseband problem but I still have "unknown" baseband. I might've screwed this one up royally... Any ideas how to fix this?
Click to expand...
Click to collapse
Yup.... download triangle away...Flash stock firmware. .. boot into stock recovery and factory reset and wipe cache reboot.. should be good to go
Sent from my SGH-I337M using Tapatalk 2
I'm also adding the modem for tmobile to the op incase you wanna try flashing that since that would have been the original modem you had before
Sent from my SGH-I337M using Tapatalk 2
Haven't looked at international version yet.. but about using Odin, aren't the partitions different?
Sent from my SGH-M919 using Tapatalk 2
2Tone5 said:
I'm also adding the modem for tmobile to the op incase you wanna try flashing that since that would have been the original modem you had before
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
Ok, back to square 1. Fixed the unknown baseband and I am at the original MDL.
Now, I decided to go the DESKTOP ODIN route. Extracted modem.bin, fired up ODIN 3.07, clicked phone, selected modem.bin, unchecked auto reboot, hit start and got fail!. The phone screen shows "secure check fail : mdm". Is this MG1 modem maybe not compatible with M919?
I don't this is a good idea. Flashing other carrier's modem??
onurd said:
Ok, back to square 1. Fixed the unknown baseband and I am at the original MDL.
Now, I decided to go the DESKTOP ODIN route. Extracted modem.bin, fired up ODIN 3.07, clicked phone, selected modem.bin, unchecked auto reboot, hit start and got fail!. The phone screen shows "secure check fail : mdm". Is this MG1 modem maybe not compatible with M919?
Click to expand...
Click to collapse
as I recall s3 and s4 are sensitive to the kind of usb cable your using as I hax problems before. I would check that your using original.
hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!
messerchmidt said:
hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!
Click to expand...
Click to collapse
Only thing u can do without pit. Cause it seems pit wont work since update to 4.3 I tried many different things. Only thing you can do is odin a 4.3 stock rogers. Or the rooted 4.1.2 firmware.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
jester12345 said:
Only thing u can do without pit. Cause it seems pit wont work since update to 4.3 I tried many different things. Only thing you can do is odin a 4.3 stock rogers. Or the rooted 4.1.2 firmware.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can someone post a pit file for me?
Look in the general section.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2609871
messerchmidt said:
hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!
Click to expand...
Click to collapse
Before you attempt an Odin + pit recovery have you tried the following:
1 - boot into recovery and do a factory reset
2 - flash the stock image via Odin by itself (please copy and post the results from the status screen) - then repeat step #1
If that doesn't resolve your issue....
It's very rare that a repartition is needed, as I'm not aware of any roms that muck with the partition sizing/data on the i317/i317m .... but depending on what the status screen says it may be worth an attempt. If you visited the link above, you'll see that I've temporarily pulled the files. I have a new files ready and am planning on testing the one for the i317 this weekend. I don't have a i317m so... if you want to test the file (which was pulled correctly from an i317m and is now sized correctly) - send me a PM.
Zen Arcade said:
Before you attempt an Odin + pit recovery have you tried the following:
1 - boot into recovery and do a factory reset
2 - flash the stock image via Odin by itself (please copy and post the results from the status screen) - then repeat step #1
If that doesn't resolve your issue....
It's very rare that a repartition is needed, as I'm not aware of any roms that muck with the partition sizing/data on the i317/i317m .... but depending on what the status screen says it may be worth an attempt. If you visited the link above, you'll see that I've temporarily pulled the files. I have a new files ready and am planning on testing the one for the i317 this weekend. I don't have a i317m so... if you want to test the file (which was pulled correctly from an i317m and is now sized correctly) - send me a PM.
Click to expand...
Click to collapse
I reloaded the stock image (rogers 4.3) via odin and did a factory reset in twrp, but i still cannot get a non-stock rom to work. very annoyed, and was going to try to PIT it.
messerchmidt said:
I reloaded the stock image (rogers 4.3) via odin and did a factory reset in twrp, but i still cannot get a non-stock rom to work. very annoyed, and was going to try to PIT it.
Click to expand...
Click to collapse
Did the stock rom work?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
yes using the stock rom atm. as soon as i try to flash a non-stock rom, i it hangs at the boot screen after it retsrats. some older threads suggested re-flashing the phone with a pit file to repartition. I dont know what else to do
Which non-stock rom? After flashing it are you able to get into recovery mode? Does this rom by any chance flash a modem.bin?
If a stock rom loads ok, chances are your pit mapping is OK.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
messerchmidt said:
yes using the stock rom atm. as soon as i try to flash a non-stock rom, i it hangs at the boot screen after it retsrats. some older threads suggested re-flashing the phone with a pit file to repartition. I dont know what else to do
Click to expand...
Click to collapse
Sounds to me like ur definitely not giving the roms enough time on the boot. Some could take 5-7 minutes for initial boot. The fact that stock works and EVERY OTHER ROM here doesn't... leads me to believe this. Patience is virtue
Sent from my SAMSUNG-SGH-I317 using Xparent Skyblue Tapatalk 2
also, someone at your skill level should not be messing with partitions; you are just asking for a brick..
Not to mention the likely requirement of fully wiping the internal storage of the device...
Arbitrarily changing frameworks back and forth without wiping the file structure first will give you problems on boot...(boot loops)...
Additionally....once the rom is flashed...it may help to immediately go to recovery and wipe the device caches and data again...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
listen to greg; he is an authority on re-partitioning and bricking! :victory:
wase4711 said:
listen to greg; he is an authority on re-partitioning and bricking! :victory:
Click to expand...
Click to collapse
ok i will try again and keep you posted
got it working after several tires, running the 4.3 jedi x2
:good:
I am at the point where my AT&T Note 2 SGH-i317 either displays the Samsung Note II screen or I can go into the Odin screen. It will not open recovery.
If I try to install CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin, I get the message from the title.
Odin appears to load the factory 4.1 rom but I end up with the same message at the end.
I had successfully restored 4.1 using Odin and then the phone auto updated to 4.3. After that, I followed the instructions for installing Jedi Master but the phone won't restart. I tried to use the same files I got 4.1 back with (this has worked twice before from 4.3) but they will no longer work. Is there anything I can do to get the phone working again?
mid_life_crisis said:
I am at the point where my AT&T Note 2 SGH-i317 either displays the Samsung Note II screen or I can go into the Odin screen. It will not open recovery.
If I try to install CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin, I get the message from the title.
Odin appears to load the factory 4.1 rom but I end up with the same message at the end.
I had successfully restored 4.1 using Odin and then the phone auto updated to 4.3. After that, I followed the instructions for installing Jedi Master but the phone won't restart. I tried to use the same files I got 4.1 back with (this has worked twice before from 4.3) but they will no longer work. Is there anything I can do to get the phone working again?
Click to expand...
Click to collapse
Which version of odin are you using?
Can you enter stock recovery or only download mode?
If you can get into stock recovery if it says anything about knox then you have the new bootloader, which you should if you updated to 4.3 via an ota update or an odin file. If you have this we can skip a few steps. If you don't, we will basically be starting from the beginning.
Assuming you have the newer bootloader, this is what I need you to do.
Go to teamw.in and download the latest twrp and make sure it's the recovery.img.tar.md5 flash that through odin.
In the mean time start a fresh download of jedi masterx2. When that download finishes make sure you verify the md5 sum. This is key. One digit off and the entire download is bad and you'll end up bootlooping again.
Once you have twrp and a good download of jmx2 boot into twrp. Do a system wipe and then flash the rom.
Let me know how it works. Just be patient and we can get this fixed for you. As long as you can power on you can recover your phone and make it work.
Sent from my SM-N900T using XDA Premium 4 mobile app
I use an app called hash droid to verify md5
Sent from my Jedi MasterX Note 2
kushXmaster said:
Which version of odin are you using?
Can you enter stock recovery or only download mode?
If you can get into stock recovery if it says anything about knox then you have the new bootloader, which you should if you updated to 4.3 via an ota update or an odin file. If you have this we can skip a few steps. If you don't, we will basically be starting from the beginning.
Assuming you have the newer bootloader, this is what I need you to do.
Go to teamw.in and download the latest twrp and make sure it's the recovery.img.tar.md5 flash that through odin.
In the mean time start a fresh download of jedi masterx2. When that download finishes make sure you verify the md5 sum. This is key. One digit off and the entire download is bad and you'll end up bootlooping again.
Once you have twrp and a good download of jmx2 boot into twrp. Do a system wipe and then flash the rom.
Let me know how it works. Just be patient and we can get this fixed for you. As long as you can power on you can recover your phone and make it work.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odin shows the Knox flag, so I assume I am on 4.3.
I cannot find this file, "recovery.img.tar.md5".
The most likely looking file I found was this, but it isn't an md5, "openrecovery-twrp-2.6.3.1-t0lteatt.img.tar".
In fact I find no files with an "md5" extension on that site.
mid_life_crisis said:
Odin shows the Knox flag, so I assume I am on 4.3.
I cannot find this file, "recovery.img.tar.md5".
The most likely looking file I found was this, but it isn't an md5, "openrecovery-twrp-2.6.3.1-t0lteatt.img.tar".
In fact I find no files with an "md5" extension on that site.
Click to expand...
Click to collapse
I apologize. For the recovery.img it needs to be the tar extension.
Once you push that to the device you're back in business.
Sent from my SM-N900T using XDA Premium 4 mobile app
kushXmaster said:
I apologize. For the recovery.img it needs to be the tar extension.
Once you push that to the device you're back in business.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I gave you a thanks because I truly appreciate the attempt to help me, but that wouldn't load either.
Fortunately the guy at the Samsung counter was able to use a Samsung loader to force 4.3 and the phone is working again.
Just curious - is your knox warranty counter back to zero in download mode?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
mid_life_crisis said:
I gave you a thanks because I truly appreciate the attempt to help me, but that wouldn't load either.
Fortunately the guy at the Samsung counter was able to use a Samsung loader to force 4.3 and the phone is working again.
Click to expand...
Click to collapse
Hmm that us interesting. I wonder why it wouldn't load...
What version of odin do you use? I've been using 3.07 for a long time with no issues.
I'm curious about the knox counter as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
Zen Arcade said:
Just curious - is your knox warranty counter back to zero in download mode?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Neither counter reset. It still displays the count for custom roms and a "1" for the Knox toggle.
kushXmaster said:
Hmm that us interesting. I wonder why it wouldn't load...
What version of odin do you use? I've been using 3.07 for a long time with no issues.
I'm curious about the knox counter as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's 3.7
That's good and weird at the same time.
Its good because its what we expected AND that the Samsung person fixed your phone even though you tripped the KNOX bit.
Its weird because the Samsung person fixed your phone even though you tripped the KNOX bit.
Hello! Let me start by saying that i have researched a ton and there is a lot of great information on here. The info I've read however doesn't seem to work for me.
My situation is I spilled a little bit of water on my phone (really not much), but it got inside my phone a little, which was already rooted using auto root. My power button thinks its constantly being pushed (i think). It doesn't bootloop, but as soon as i pop the battery in it turns on, and my phone was unresponsive to me clicking the power button. The rest of the phone was fully functional and i checked with Tmobile and it is still under warrenty (didn't mention the water). They told me to backup the phone which i was able to do in kies with no problem. Then they said do a factory reset, which again I did with no problem. It didn't solve my issue which i kinda knew it wouldn't, so the next step for me was to unroot my phone so i can return it. I popped it in odin, selected the original firmware and it started , then it disconnected by itself. Now the firmware upgrade screen pops up, but i am still able to get it into download mode (for me since the power button is suspect) i just have to hold the home and volume down, pop in the battery and it goes to download mode. The problem is that every time i try to hit start in Odin it gets to the part about the PIT partition and disconnects and says there is no PIT partition. Everywhere i've read says to either use a PIT partition (can't find one for the M919) or that the partition is in the m5 file, which as far as i can tell it is not (at least not it's own file). I've tried downloading the stock firmware from a multitude of different places even Sammobile with no luck and I've also tried different computers, different cables, and all the USB ports available to me.
Can anyone please tell me where to go from here please? I need to get this replaced asap!
(sorry i also posted this in the general section on accident)
I really think I just need the PIT partition, but I can't seem to find one for the m919 model
I have also tried different version of Odin (1.85, 3.07, and 3.09) all with the same result
What stock firmware are you trying to flash?
4.4.2?
Sent from my SGH-M919 using XDA Premium 4 mobile app
i think so. the name of the file is M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
Ace$$ said:
i think so. the name of the file is M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
Click to expand...
Click to collapse
When you're in download mode do you see anything that mentions KNOX in the upper-left hand corner? I only ask because MDL (4.2.2) firmware is the pre-KNOX firmware and will have no mention of KNOX in the text in download mode; it also will not flash if your bootloader has been updated to MK2 (4.3) or NB4 (4.4.2).
You're trying to flash mdl to a phone that won't take it. (ie it's already been updated to mk2 or nb4).
I'd flash the mk2 or nb4 tar file.
Sent from my SGH-M919 using XDA Premium 4 mobile app
---------- Post added at 12:56 AM ---------- Previous post was at 12:55 AM ----------
You can get them here: http://forum.xda-developers.com/showthread.php?t=2816508
Sent from my SGH-M919 using XDA Premium 4 mobile app
no nothing about knox.
Fu** yeah!! :fingers-crossed: that looks like it might be the problem. i'll download and post how it goes
Ace$$ said:
no nothing about knox.
Fu** yeah!! :fingers-crossed: that looks like it might be the problem. i'll download and post how it goes
Click to expand...
Click to collapse
If the string "KNOX WARRANTY VOID:" doesn't appear in download mode, then your phone has not been updated to 4.3 or 4.4.2 as android_monsters stated. MDL should have flashed as there was nothing related to the bootloader or KNOX keeping you from a successful flash.
One thing I did encounter myself while trying to re-flash my pre-KNOX device; did you ever update your modem/baseband to MK2 or NB4? If you did, I would recommend finding the individual MDL modem/baseband files and manually reverting them before flashing the stock MDL firmware again. Odin never failed for me at the device .pit file, but I did encounter the firmware upgrade screen while trying to revert to stock with an updated modem. Doesn't make sense to me as the stock firmware has the modem and all in it, but that fixed it for me.
That did the trick all right! :victory: :victory:
Thanks!
SAVED :angel:
I had the same problem but when i tried to flash the lastest firmware its stock on samsung logo... anyone can help me?
Ace$$ said:
That did the trick all right! :victory: :victory:
Thanks!
Click to expand...
Click to collapse
Reverting the modem before flashing the stock firmware fixed your problem? Awesome! :highfive:
Hold the power button and the volume up button and try booting into recovery,
Wipe cache
3 times
Wipe dalvik
3 times
Wipe system
3 times
Reflash rom
1 time
Wipe cache
At least 1 time
Reboot or
Flash gapps
(Only if needed)
If that doesn't help, then maybe try a different rom?
Sent from my GT-I9505G using XDA Free mobile app
Infamous_CA said:
I had the same problem but when i tried to flash the lastest firmware its stock on samsung logo... anyone can help me?
Click to expand...
Click to collapse
I'm assuming you're flashing the stock firmware via Odin... if that's the case, simply factory reset via stock recovery and you should be good to go.
lordcheeto03 said:
I'm assuming you're flashing the stock firmware via Odin... if that's the case, simply factory reset via stock recovery and you should be good to go.
Click to expand...
Click to collapse
I tried but it dosnt show recovery.. I flash a recovery but it dossnt boot on recovery. It show samsung galaxy but the screen turn in black.. I think that maybe it a board problem.
Sent from my HTC One X using XDA Premium 4 mobile app
Infamous_CA said:
I tried but it dosnt show recovery.. I flash a recovery but it dossnt boot on recovery. It show samsung galaxy but the screen turn in black.. I think that maybe it a board problem.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try re-flashing the stock firmware in Odin. Don't flash a custom recovery at this point, just the stock firmware. Once it passes in Odin, power it off. Hold Power + Volume Up while powering up. It should show the Galaxy S4 screen with "Booting Recovery" in the upper-left.
Yes it say that on blue letters but dosnt show the recovery menu
Sent from my HTC One X using XDA Premium 4 mobile app
Infamous_CA said:
Yes it say that on blue letters but dosnt show the recovery menu
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ah. Well I don't know what to say; perhaps someone else may know? Sorry and good luck.
lordcheeto03 said:
Ah. Well I don't know what to say; perhaps someone else may know? Sorry and good luck.
Click to expand...
Click to collapse
Thanks for ur help man.
Sent from my HTC One X using XDA Premium 4 mobile app