I need some assistance please. My phone is stuck on the Samsung Logo. When booting into recovery it just shows the Teamwin logo then reboots.
I didn't seem to modify anything. The phone just crashed one day.
I believe the android version it's on is 4.1.2, rooted, teamwin, flash counter (can't kies)
It hadn't been updated in a long time because my USB flex cable was faulty. I repaired this after the phone bricked and it seems to be functioning properly to charge and send data via odin.
I tried several fixes by flashing alleged stock roms with Odin. This didn't fix the issue or I did something wrong. I searched around a bit on the forums but it is difficult because there is so much information and many broken links. If anyone can help I would really appreciate it.
The ironic part is that my contract just ran out 2 days after it bricked. Sprint's trying to covertly get me to renew
(p.s. I'm currently on a Samsung Epic 4G, gingerbread!! It's quite a downgrade!!)
Also, ideally if the phone can be fixed I would like to have a rooted KitKat, so if the solution involves that no worries. I just want the phone to work really.
ChrisMcIntosh said:
I need some assistance please. My phone is stuck on the Samsung Logo. When booting into recovery it just shows the Teamwin logo then reboots.
I didn't seem to modify anything. The phone just crashed one day.
I believe the android version it's on is 4.1.2, rooted, teamwin, flash counter (can't kies)
It hadn't been updated in a long time because my USB flex cable was faulty. I repaired this after the phone bricked and it seems to be functioning properly to charge and send data via odin.
I tried several fixes by flashing alleged stock roms with Odin. This didn't fix the issue or I did something wrong. I searched around a bit on the forums but it is difficult because there is so much information and many broken links. If anyone can help I would really appreciate it.
The ironic part is that my contract just ran out 2 days after it bricked. Sprint's trying to covertly get me to renew
(p.s. I'm currently on a Samsung Epic 4G, gingerbread!! It's quite a downgrade!!)
Also, ideally if the phone can be fixed I would like to have a rooted KitKat, so if the solution involves that no worries. I just want the phone to work really.
Click to expand...
Click to collapse
Sounds like a corrupt recovery. Use odin to flash another recovery (suggest philz 6.07.9).
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Sounds like a corrupt recovery. Use odin to flash another recovery (suggest philz 6.07.9).
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Booting to recovery after flashing still gets me to the Teamwin logo then a reboot. Did I do something wrong?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-l900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Try cwm then. I have had this issue before once with philz and once with twrp.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Try cwm then. I have had this issue before once with philz and once with twrp.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/003> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
I tried cwm and same result of Teamwin logo and will not boot.
I had to convert the original cwm .img with a tool found in these forums to .md5.tar
Is it important to note that I currently dont have the SD card in the phone?
Also Odin is v3.04, Auto-reset and f. reset time are checked
Just for kicks I tried flashing the various recoveries with the reboot off. Tried various versions of Odin.
Still all result in a failure.
Please help.
You *might* try this
http://forum.xda-developers.com/showthread.php?t=2780984
Stock 4.4.2. It would install stock recovery (I believe). If it works, you could then flash custom recovery and root.
I currently use odin v3.07 (I believe)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
You *might* try this
http://forum.xda-developers.com/showthread.php?t=2780984
Stock 4.4.2. It would install stock recovery (I believe). If it works, you could then flash custom recovery and root.
I currently use odin v3.07 (I believe)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Unfortunately this did not fix the problem.
Odin (I used 1.85 this particular time)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> param.bin
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> tombstones.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
The only thing that i could think of would be to pull the battery for about 10 minutes. Sounds dumb, but it got me out of a boot loop once...
Just used the same file to update my wife's phone (but she wasn't soft-bricked either.
When i come up with something more I'll be back....
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Here's another thread that might help
http://forum.xda-developers.com/showthread.php?t=2781785
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
Here's another thread that might help
http://forum.xda-developers.com/showthread.php?t=2781785
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
The link for the fix is either not present or it is in the other thread and the link doesn't work. I will try that when it's available.
As for the battery pull, I leave it out of the phone between trials of getting this device to work, however the status of the brick(?) has since changed since flashing your last suggestion and leaving the battery out overnight.
Now it hangs at the Galaxy Note II logo on normal power on. (This is the change, all else is the same)
If I boot by going in to download mode then hitting cancel it will loop on the Samsung Logo
Recovery will display Teamwin logo then boot loop on Samsung Logo
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
---------- Post added at 05:53 PM ---------- Previous post was at 05:45 PM ----------
Chris this might be it?
http://forum.xda-developers.com/showthread.php?t=2653671
Page #29/post 289
Let me know if thats what you're looking for. And be sure to thank jlmancuso if this helps...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
---------- Post added at 05:53 PM ---------- Previous post was at 05:45 PM ----------
Chris this might be it?
http://forum.xda-developers.com/showthread.php?t=2653671
Page #29/post 289
Let me know if thats what you're looking for. And be sure to thank jlmancuso if this helps...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
This also did not work unfortunately. Any other suggestions?
ChrisMcIntosh said:
This also did not work unfortunately. Any other suggestions?
Click to expand...
Click to collapse
I believe this is what you're looking for .. not my work it's still jlmancuso's work I just have it saved and backed up as it was the only thing that saved my phone.
michael85tx said:
I believe this is what you're looking for .. not my work it's still jlmancuso's work I just have it saved and backed up as it was the only thing that saved my phone.
Click to expand...
Click to collapse
Sorry my sentence wasn't clear enough. I tried jlmancuso's fix.tar using the instructions given in the thread linked up there. It failed to get me any new results.
ChrisMcIntosh said:
Sorry my sentence wasn't clear enough. I tried jlmancuso's fix.tar using the instructions given in the thread linked up there. It failed to get me any new results.
Click to expand...
Click to collapse
Dude, at a loss. Only a couple of things that i could think (and you have probably tried)
I would:
Grab the ne2 tar
http://forum.xda-developers.com/showthread.php?t=2780984
Check the md5 after you dl the file.
Install odin v3.09
Make sure that ur running as admin. And make sure that your samsung drivers are installed (maybe even reinstall them?). Flash ne2 from AP.
I only ever use a usb port on the back of my pc/laptop (off the mb), and i only use the original samsung charging cable. Maybe just superstition but I've always had great luck...
I would only focus on getting a stock tar on right now. Wouldn't worry about custom recovery. Stock tar should over-write it anyway...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
Dude, at a loss. Only a couple of things that i could think (and you have probably tried)
I would:
Grab the ne2 tar
http://forum.xda-developers.com/showthread.php?t=2780984
Check the md5 after you dl the file.
Install odin v3.09
Make sure that ur running as admin. And make sure that your samsung drivers are installed (maybe even reinstall them?). Flash ne2 from AP.
I only ever use a usb port on the back of my pc/laptop (off the mb), and i only use the original samsung charging cable. Maybe just superstition but I've always had great luck...
I would only focus on getting a stock tar on right now. Wouldn't worry about custom recovery. Stock tar should over-write it anyway...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
It still failed but I have 2 questions.
Do you have the md5? Also should auto reboot be on (I had it on)
Also while it is booting up (but stuck at samsung screen)
One of the drivers it tries to install 'MTP USB Device' fails to install
I reinstalled drivers. The Odin operation appeared to be successful as always, I did use 3.09 (in admin) this time, its a samsung cable on mobo, but not the original from the note 2 as it is destroyed. The USB flex cable is new because the old was was broken, I think i installed it correctly.
After all this flashing it still kills me that the stupid Teamwin logo is still there. Did this become read only? (I'm such a novice)
Here is Odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> param.bin
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> tombstones.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
ChrisMcIntosh said:
... One of the drivers it tries to install 'MTP USB Device' fails to install
Click to expand...
Click to collapse
Until you get your Samsung drivers correctly installed, it's pointless to do anything else.
Plug in your phone, open device manager and find it under your bus controllers(I think?). It will probably be listed as unknown device (with a yellow exclamation). Right-click and Uninstall. Unplug your phone, plug it back in and it should attempt to reinstall the drivers.
Don't go any further unless all drivers install. Once you get them installed you can then flash the tar.
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
---------- Post added at 12:59 PM ---------- Previous post was at 12:36 PM ----------
Or, don't plug ur phone in. On ur pc (assuming Windows 7?) go to control panel/programs and features, and Uninstall your Samsung drivers from there. Then download drivers
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Then, hook up ur phone...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
---------- Post added at 01:22 PM ---------- Previous post was at 12:59 PM ----------
Here's the md5 for note2 ne2 tar
7300440488f7713e8269539d93b97f3c
I use winmd5 on my pc. Since I do all my dls over wireless, it's saved me from flashing a few bad downloads. It's become habit for me to check the md5 of everything I flash...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
Until you get your Samsung drivers correctly installed, it's pointless to do anything else.
Plug in your phone, open device manager and find it under your bus controllers(I think?). It will probably be listed as unknown device (with a yellow exclamation). Right-click and Uninstall. Unplug your phone, plug it back in and it should attempt to reinstall the drivers.
Don't go any further unless all drivers install. Once you get them installed you can then flash the tar.
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
---------- Post added at 12:59 PM ---------- Previous post was at 12:36 PM ----------
Or, don't plug ur phone in. On ur pc (assuming Windows 7?) go to control panel/programs and features, and Uninstall your Samsung drivers from there. Then download drivers
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Then, hook up ur phone...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
---------- Post added at 01:22 PM ---------- Previous post was at 12:59 PM ----------
Here's the md5 for note2 ne2 tar
7300440488f7713e8269539d93b97f3c
I use winmd5 on my pc. Since I do all my dls over wireless, it's saved me from flashing a few bad downloads. It's become habit for me to check the md5 of everything I flash...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Unfortunately I'm now at the MTP Failed to install roadblock with a million and one solutions. Apparently this is some common Samsung problem. Oh boy. Well I'll try to see if I can find a solution within the next few days. I've already installed/unistalled a bunch of times. Fun
ChrisMcIntosh said:
Unfortunately I'm now at the MTP Failed to install roadblock with a million and one solutions. Apparently this is some common Samsung problem. Oh boy. Well I'll try to see if I can find a solution within the next few days. I've already installed/unistalled a bunch of times. Fun
Click to expand...
Click to collapse
Just remember what doesn't kill us makes us stronger
There are a ton of possible solutions. Start with the easiest. Also, if you have kies installed on your pc uninstall/disable it. I don't use it so don't know, but I have heard that it can cause problems...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Related
I reinstalled the drivers, reinstalled odin, re-downloaded the LJ1 MD5, used different cables, but everytime I getting this in the Odin screen
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> param.bin
<ID:0/011> recovery.img
<ID:0/011> sboot.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Removed!!
Anyone have any other method I can try to get back to complete stock. Any ideas would be appreciated.
Go to Android development and look for billiard412's thread he had a back to stock setup that works very well.
http://forum.xda-developers.com/showthread.php?t=2086769
THAT
Sent from my SPH-L900 using xda app-developers app
Tw1sted247 said:
Go to Android development and look for billiard412's thread he had a back to stock setup that works very well.
Click to expand...
Click to collapse
00mred00 said:
http://forum.xda-developers.com/showthread.php?t=2086769
THAT
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks for help and suggestions.
All systems are go on my phone now, I downloaded the stock file from Samsungupdates.com, then installed it thru Odin and it worked like a charm.
Where did you find the stock file from samsungupdates.com? I can't find it anyway. I've been stuck on this for nearly a day now. I've learned quite a bit of new stuff... more than I care to know lol. I know there is a solution to this, I just need some guidance please.
QuantumPSI said:
Where did you find the stock file from samsungupdates.com? I can't find it anyway. I've been stuck on this for nearly a day now. I've learned quite a bit of new stuff... more than I care to know lol. I know there is a solution to this, I just need some guidance please.
Click to expand...
Click to collapse
here the link to the page
http:// samsung-updates.com/device/?id=SPH-L900 (remove the spaces)
download the middle link, it should take about 2 hours, run this file thru Odin as if it were any other TAR
After you download, this is what the file should be: KIES_HOME_L900VPALJ1_L900SPTALJ1_265523_REV04_user_low_ship.tar.md5
lexvdub1 said:
here the link to the page
download the middle link, it should take about 2 hours, run this file thru Odin as if it were any other TAR
After you download, this is what the file should be: KIES_HOME_L900VPALJ1_L900SPTALJ1_265523_REV04_user_low_ship.tar.md5
Click to expand...
Click to collapse
I REALLY NEED THIS FILE CAN YOU SEND IT TO ME PLZ! THE SITE IS DOWN..I used cdma ws 3.8.0 wont read my note 2 sph-l900 even connected to the correct com and in diag mode with pda and then dm+modem+adb...never had this problem before, I even flashed lj1 and ljc stock roms and still say's FAILED..PHONE DOES NOT ANSWER! I've flashed many phones and usually all I'd have to do is change the usb cable or the com port but even then it's not working.
Doesn't get any easier than this right here:
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using xda app-developers app
Well I was on the 4/10 nightly for CM 10.1, and I wanted to switch back to a stock TW ROM, so I downloaded and flashed PlainJane. Upon reboot my phone demanded that I reset my data because encryption had failed, and I never had my device encrypted, but the only thing I could do was press reset. So I did, and the phone booted into TWRP and flashed a quick message and rebooted to the same screen. I thought oh well no biggie I can restore my backup...NOPE. Looks like my SD card decided to corrupt. Well hey theres Odin right? WRONG AGAIN. I tried the method at
http://www.sxtpdevelopers.com/showthread.php?t=74 and Odin tells me
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> param.bin
<ID:0/006> recovery.img
<ID:0/006> sboot.bin
<ID:0/006>
<ID:0/006>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I cannot boot into recovery because it tells me a firmware update has failed. Please someone help...
When you use ljc it will always fail at sbin it's not going to install the old boot loader use the new tar from This thread
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Epix4G said:
When you use ljc it will always fail at sbin it's not going to install the old boot loader use the new tar from This thread
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
THANK YOU SO MUCH! I got TWRP up and running and I'm flashing the stock reset now .
hi my phone interputerd while updating and i get firware upgrade encountered an issue.kies cant see my phone i downloaded stock room and flash it through odin as below
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ3_N7100OJVALJ2_N7100XXALJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
odin passed
phone went back to firware upgrade encountered an issue please select recovery mode in kies
please help
Maybe use the correct image. That says n7100 unless that's what you have. If that's the case post in the right forum
Sent from my SGH-T889 using xda app-developers app
Like kin said ....... as for it stopping try a different usb cable/port... btw that screen you see.. it's still.download mode..
Sent from my SGH-T889 using Tapatalk 2
Should just use the toolkit in the original development, it literally babysit you step by step, almost fool proof
Sent from my SGH-T889 using xda premium
OmmNomNom said:
Should just use the toolkit in the original development, it literally babysit you step by step, almost fool proof
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
This is true, but I personally hate toolkits.i think people should understand what they are doing to their phone instead of just selecting option 1.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
This is true, but I personally hate toolkits.i think people should understand what they are doing to their phone instead of just selecting option 1.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
it's good for starters, you still have to select the correct files provided by that specific toolkit, but yes, at lease get the right file for the phone
thanks all i didnt manage to fix it so i took it to samsung they will fix it
following these directions:
techbeasts . com /2013/10/12/how-to-unroot-samsung-galaxy-s4-all-versions/
My wife's phone was on 4.3, I swapped it to whatever the latest CM was on Monday and she doesn't like it
She wants it reverted back to 4.2.2
I have the md5 file (M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5)
and when I try to load it via Odin I get:
Code:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> sbl2.mbn
<ID:0/011> NAND Write Start!!
<ID:0/011> sbl3.mbn
<ID:0/011> rpm.mbn
<ID:0/011> aboot.mbn
<ID:0/011> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says
Code:
Start [224, 1440]
SW Rev. Check Fail : fused : 4, Binary : 1
Do I need to use the 4.3 ROM (TMB-M919UVUEMK2-20131126142733.zip)?
Now when I try to turn it on I get
Firmware upgrade encountered an issue. Please select recover mode in Kies & try again.
HELP! I have no idea what to do now and her phone isn't working
chapel976 said:
following these directions:
techbeasts . com /2013/10/12/how-to-unroot-samsung-galaxy-s4-all-versions/
My wife's phone was on 4.3, I swapped it to whatever the latest CM was on Monday and she doesn't like it
She wants it reverted back to 4.2.2
I have the md5 file (M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5)
and when I try to load it via Odin I get:
Code:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> sbl2.mbn
<ID:0/011> NAND Write Start!!
<ID:0/011> sbl3.mbn
<ID:0/011> rpm.mbn
<ID:0/011> aboot.mbn
<ID:0/011> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says
Code:
Start [224, 1440]
SW Rev. Check Fail : fused : 4, Binary : 1
Do I need to use the 4.3 ROM (TMB-M919UVUEMK2-20131126142733.zip)?
Now when I try to turn it on I get
Firmware upgrade encountered an issue. Please select recover mode in Kies & try again.
HELP! I have no idea what to do now and her phone isn't working
Click to expand...
Click to collapse
Yes, find and flash the MK2 odin .tar file. That should solve the problem. The reason the 4.2 MDL tar file is failing is because once you were on 4.3 MK2 your qfuse counter was ticked up and you can no longer can flash down to MDL.
is there any better place to get this ROM? All I'm finding are these ridiculous sites that want me to pay like $15 to do a 'fast download'
all the other ones are like 8 hours to download and my computer keeps timing out
neither the terafile or rapidgator site works for me and I don't feel comfortable paying an out of country site like this.
are there any other options? My wife is leaving for a trip tomorrow and her phone is useless.
I downloaded some other ones (MODIFIED_STOCK_MK2_DEODEX_V1.4.zip) but there's no MD5 file included to do it with... just a ZIP
any way to package that as an MD5 tar?
chapel976 said:
is there any better place to get this ROM? All I'm finding are these ridiculous sites that want me to pay like $15 to do a 'fast download'
all the other ones are like 8 hours to download and my computer keeps timing out
neither the terafile or rapidgator site works for me and I don't feel comfortable paying an out of country site like this.
are there any other options? My wife is leaving for a trip tomorrow and her phone is useless.
I downloaded some other ones (MODIFIED_STOCK_MK2_DEODEX_V1.4.zip) but there's no MD5 file included to do it with... just a ZIP
any way to package that as an MD5 tar?
Click to expand...
Click to collapse
Have you tried downloading from Samsung?
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 01:40 AM ---------- Previous post was at 01:36 AM ----------
mrzhadow said:
Have you tried downloading from Samsung?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Try this http://samsung-updates.com/device/?id=SGH-M919&details=Galaxy_S_4_T-MOBILE its the official mk2
Sent from my SGH-M919 using xda app-developers app
I didn't know I could get it right from samsung. I'll try that link when I get to my desk. Thanks
chapel976 said:
I didn't know I could get it right from samsung. I'll try that link when I get to my desk. Thanks
Click to expand...
Click to collapse
Well you said your wife's phone was 4.3 so in order to go back to stock you must flash the official mk2. MDL will not work. You can't downgrade from 4.3. If you were flash official mdl over mk2 it will soft brick the phone. You can Google how to unbrick. It is doable. Good luck!
Sent from my SGH-M919 using xda app-developers app
I am fine with getting 4.3
is there a direct link for Samsung?
that link you provided me with was for those two sites that don't work for me
I'm getting it from SamMobile. They're not 15 hours slow.
Odin successfully loaded the ROM but now it's showing a gray battery icon.
I'm going to let it charge for a bit.
It was showing the T-mobile 4G LTE logo for a bit until I disconnected it from the PC after Odin reported success.
wish me luck.
so, it has taken a charge, but it just sits at the pulsing white T-mobile 4G LTE screen on boot. it makes the T-mobile noise... but that's it.
Were you able to fully boot the phone? Try doing a factory reset after you Odin the package. Sometimes you get issues after you Odin but a factory reset fixes most problems. Be sure to wipe dalvik and cache.
Sent from my SGH-M919 using xda app-developers app
I cleared the cache and did a factory reset and now it's starting up.
chapel976 said:
I cleared the cache and did a factory reset and now it's starting up.
Click to expand...
Click to collapse
Good deal. Great job man!!
Sent from my SGH-M919 using xda app-developers app
Thank you for your help. It looks like it's fully working now.
chapel976 said:
Thank you for your help. It looks like it's fully working now.
Click to expand...
Click to collapse
Good! You're welcome!
Sent from my SGH-M919 using xda app-developers app
Hi guys, bit of a noob here...I messed up my kids tablet.
It was running NoleKat 2.X, previous to that was running stock 4.4.2.
In an effort to get tablet back to stock to clear up some bootloop issues - used odin to flash stock 4.1.2 it worked no problem except Samsung update to 4.4.2 would no longer work...
so I break out odin again and grab what I think is the right stock 4.4.2 Rom from sammobile....try to flash it, it fails and now tablet only boots straight into recovery <3e>.
I tried wipes from recovery they all fail due to some make_extf4fs failed on dev block.
adb sideload will crash when ROM transfer gets to about 70%.
tablet will not take any other ADB commands
Smart switch and Kies will not reconize tablet say its unsupported - works fine on another tablet.
I can get it into odin mode but odin will fail no matter what I try and flash...works fine to flash second tablet I have.
Any suggestions or do I need a new tablet.
Plaz
I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat
plazomat said:
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat
Click to expand...
Click to collapse
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
So when I flash twrp 2.8.0 it , the progress bar goes all the way green then fails after a few seconds here is the oding log...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help RealWelder...
Plaz
And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz
plazomat said:
And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz
Click to expand...
Click to collapse
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ
plazomat said:
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ
Click to expand...
Click to collapse
Hi i have the same problem can u help me pls?
Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to samsung ( I think) recovery....
Plaz
plazomat said:
Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to recovery....
Plaz
Click to expand...
Click to collapse
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz
plazomat said:
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz
Click to expand...
Click to collapse
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Thanks RealWelder you are awesome to still be supporting these old beaters - gonna try this in the morning when I get some time....
Plaz
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz
plazomat said:
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz
Click to expand...
Click to collapse
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.
gr8nole said:
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.
Click to expand...
Click to collapse
Thanks gr8nole - tried flashing the 3.0.0 TWRP still no joy - keeps booting into stock (ithink) recovery. I pulled it from your file repo on Android file host.
I say I think cause the font is so big and the display is in landscape mode.
Plaz
RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Gave it a go with your ROM...still recovery boot loop as suggested by gr8nole.
Here is log..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> system.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Thanks again
Plaz
Hi Gents, still messing with this when I have time and no joy...
Can't get a custom recovery to stick, odin flashes file but when device reboots just goes back to stock recovery...
Any clues.
Plaz