Good afternoon XDA Developers!! I'm new in this forum. It is so awesome!!
I have a terrible problem with my Note II. My phone runs, opens download mode and recovery (I have a custom) but gets stuck in the main logo. I tried downloading firmwares and flashing with Odin and always happens the same error.
Odin 3.10.7
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sometimes Odin gets stuck in "Setup Connection", I remove and put the battery again and runs, but with the same error described before.
I tried downloading stock firmwares from my country (Mexico), now I tried with one from Russia, and now I'm downloading a Repair Pack with BL, PDA, CSC and MODEM (I'm doubting that this will work).
I was checking the repairing manuals from Samsung, and I believe that the main problem is in the IC (U500) or probably R503, but if this will be the main reason, I need to change the motherboard. I don't hope so.
I disassembled the phone and the IC's and connections "appears to be OK".
Are there another alternatives to verify and repair the phone in the software or hardware? In this case, what can I do? Or what I'm doing wrong to correct the mistakes? I will be so grateful with your help.
Thank you so much. I hope your soon answer!
how it happened - just restarted and stuck on logo for no reason?
Try PIT, but be careful. It's very likely that you have famous SDS, that's why it can't mount partitions and flash anything.
You can also try different Odin versions and PCs/cables
I have downloaded the PIT file and my question is: How can I flash it? With the PDA, MODEM, etc. together or only the PIT alone? What checkboxs i need to check? I was reading about SDS and apparently the only solution is to change the eMMC and weld it. I sent the phone to the Carrier Company "Telcel" to unlock the Phone and after this the phone restarted and restarted and erased all the apps. This happens like 2 or 3 times. After this the phone get stuck in the logo.
Dear Sir,
I am Samsung Note 2 GT N7100 mobile.
My mobile anderoid ver.4.2.2
How to update in lolipop ver.
please support.
Related
stuck at boot logo
enter into recovery but internal memory not mounting shows only 0mb storage not evn wipe,restore,backup anything wd dt not possible
odin show me dis when m try to install new md5 file.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
plzzzzzzzzz help pllzzzz
thankz in advance
What recovery are you using? Try updating it. Factory resetting almost always solves boot hangups. For Odin, try flashing a different firmware. If you ever flashed 4.3 firmware, you can ONLY flash the same or newer from now on.
DocHoliday77 said:
What recovery are you using? Try updating it. Factory resetting almost always solves boot hangups. For Odin, try flashing a different firmware. If you ever flashed 4.3 firmware, you can ONLY flash the same or newer from now on.
Click to expand...
Click to collapse
SIr i have the same Problem but a little bit different .
i can recover my Phone without Odin problem but when the phone start up the is hangup with SAMSUNG logo and nothing appear then suddenly the phone is restarting without any action .. !!!!
please what should i do to fix my phone !?
Wallid92 said:
SIr i have the same Problem but a little bit different .
i can recover my Phone without Odin problem but when the phone start up the is hangup with SAMSUNG logo and nothing appear then suddenly the phone is restarting without any action .. !!!!
please what should i do to fix my phone !?
Click to expand...
Click to collapse
What steps have you taken to try to fix it?
Model: SGH-T999V (Wind Mobile)
Firmware Rom: Cyanogenmod 10.1.3 (IIRC, might have been 10.1.2)
So, last night I plugged my phone in to my computer to charge. I walked away to do some other things, and when I came back a few minutes later I found it rebooting, or at least trying to. It seemed to be stuck in a loop. It would vibrate and show the Samsung logo, and then show the model logo (in my case "Samsung Galaxy SIII" with the cyanogenmod logo on the bottom half of the screen). After this, it would vibrate twice with around a two second delay between each vibration. Then it would show the Samsung logo, the model logo, and vibrate twice again, repeating indefinitely. The only thing that stops the loop is pulling the battery.
At this point I'm thinking that there's a problem with the battery. I kept it plugged in to my computer for a little while while it tried to boot, hoping that it just needed to be charged. After this didn't work, I tried charging it with a portable battery pack I had and used a different cable. Still nothing. Then, I found a spare battery that I had and replaced the one I had been using. That didn't work either, the phone continued doing the same boot loop.
I don't believe that the problem is a faulty power button, since it doesn't start trying to boot until I either plug it in to charge or I press the power button myself. I can't seem to enter recovery mode. Whenever I try, it shows the initial Samsung logo screen with "Recovery Booting...." in small blue text in the top left corner of the screen, but then proceeds to reboot again.
I am, however, able to enter download mode. I decided to try and flash my stock firmware, hoping that would fix the problem. I put my phone in download mode, opened odin, and it seemed to recognize my phone. I loaded the .md5 file and hit start, but almost immediately it showed 'FAIL'. This is what it said in the message box:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
At this point I have no idea what else I can do. I hope it's not a hardware failure, but it's starting to look like that's the case. Is there anything else I can try, or is my phone just dead? And, if it is dead, does anyone know the exact cause?
CM is your rom, not your firmware. The firmware is what we generally refer to as everything but system, kernel and recovery. Do you know what your current firmware build is?
Are you certain you downloaded the Wind version of the firmware?
I could be wrong but from the Odin output it looks like you have pre 4.3 firmware. If so, try using any other build and see if it flashes.
Judging from the symptoms you described, it is possible you could be looking at a hardware failure. Possibly the SoC, but more likely the memory. If you cant get Odin to flash anything the possibility of this becomes greater.
Try other firmware with Odin. Try with and without re-partition checked. (This will wipe all your data)
Try flashing TWRP via Odin. If that makes recovery work you may then be able to factory reset and flash a rom again.
Try different usb cables and ports. Try another computer as well if nothing else is helping.
Beyond all of that, im not sure theres gonna be much you can do.
Argh, I always seem to get ROM and firmware mixed up. Anyway, If I'm understanding this correctly I'm pretty sure that my firmware was 4.2.2. I definitely downloaded the wind version of my stock firmware. I also found on my computer 4.0 firmware that I'd downloaded a couple years ago. I tried flashing that with odin and got the same result. Then I tried it with re-partition checked and it failed again with this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I guess that's that then. Luckily I had backed up all my photos last week on a whim.
Out of curiosity, did you use a PIT file when repartitioning, or did it use the one in the device? Whichever it is, try the other as well. I believe the pit files are in the General section.
I used the PIT file on my device when I first tried to repartition. I downloaded the PIT file that you were talking about and tried again:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you try flashing recovery only? And does odin see the devices COM port in the top left?
Did you try different ports and cables?
Odin does see the COM port. I just tried flashing TWRP and odin said that it passed, but I'm still not able to boot into recovery mode. I have tried using another port but I don't have another cable on me.
Well if it said it passed the recovery flash, the cable and port are probably ok.
Im not really sure there is much else you can do tbh. Its sounding more like a hardware problem at this point.
Sorry I dont have anything better to tell you, but if I think of anything else you could try ill let you know.
[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/
Q&A for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i did all this to my s4 but now when i boot it, says Kernel Is Not Seandroid Enforcing, Set Warranty Bit
also when i booted the phone the wifi does not work. could you help with this problem?
Samsung Galaxy S4
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?
Ayaz Gill said:
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?
Click to expand...
Click to collapse
Yes
UPDATE: I fixed the issue while posting this, the solution is included. I am hoping by posting this it may help someone having the same problem, because I spent hours and days trying to solve the issue. Sorry the post is so long.
This is my first post.. I am in desperate need of help!
I have searched everywhere, and cannot find any answers really.
I rooted my M919 at one point, and I could not receive OTA updates.
I do not know if it was rooted when I tried to update it with Odin though.
I was in a hurry (I know BIG mistake) and I never wiped my phone or anything before trying to flash the phone.
I think the phone may not be working because I may have not used triangle away before, but I am not sure if I ever used it. I did the root a long time ago.
I have tried changing USB cords, computers, drivers, md5 files, different Odin versions, flashing PIT file, you name it, I have probably tried it
When I boot the phone the currupt recovery screen shows up. Kies will not recognize the phone.
In the left corner it says:
ODIN MODE
...SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
I can still access "downloading" mode, and it says the same as above.
Odin gives me different errors depending on the file I am attempting to flash
The reason I tried flashing the PIT file is because it would sometimes say
I am not completely sure what update I was using before this all happened, but I think it may have been this one, unrooted?:
CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5
Error codes are as follows:
While flashing 4.4.4 (Odin 3.10)
M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
JFLTE_USA_TMO_16G.pit
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5 is valid.
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
One time I tried using this and it passed!!!
This ONLY works on 3.07 to my knowledge though. It fails on every other Odin
Recovery File I found (Odin 3.07)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The screen is now frozen on the "Samsung Galaxy S4" screen and just shuts off if trying to boot into recovery mode.
If plugged into USB while trying to boot into recovery it launches the recovery file I just flashed!
I went back into download mode, and plugged the phone back in.
I opened Odin 3.07 again, since I had success with the recovery file.
I tried flashing 4.4.4 again M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
and it failed while only having Auto Reboot checked. I tried launching it with Auto Reboot AND F Reset Time, and it worked!! Hope this helps someone!!
Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks
shaqto said:
Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks
Click to expand...
Click to collapse
Replied to your email. Not sure if I still have it but I may be able to find it if you say it's not there.
alright i did a no no... I tried flashing back to stock odin when my phone was encrypted .. now its softbricked.
everytime i try to flash the stock odin, it always fails at system.img ext4. Need some help guys, its been softbricked for a week. I flashed philz touch twrp on it so I do recovery on it. any ideas?
doesnt work
Bricked my s4/but i had twrp installed to fix it
I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> 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/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
asmth00 said:
I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> 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/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version Bootloader/Modems do you have now on the phone? If the version you have now has Knox, then you can't downgrade to MDL.
If you are not sure, you can use this free app: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
If the version is MK2 or newer, you can't downgrade to MDL.
You can find newer firmwares either on the SamMobile.com site, or on this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Rob
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
In odin, it says 0:[COM4] on the top left
You have 0:[COM3] in your screenshot
Is there a problem or something?Or is it fine?
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me
AziNoapte said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me
Click to expand...
Click to collapse
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: http://www.sammobile.com/firmwares/
Rob
rlichtefeld said:
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: ------------To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links--------------
Rob
Click to expand...
Click to collapse
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?
AziNoapte said:
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?
Click to expand...
Click to collapse
Since this forum is for the T-Mobile variant of the S4, and I'm not familiar with the GT-I9505, I would suggest you try the forum for that model:
http://forum.xda-developers.com/galaxy-s4
If you flashed a T-Mobile tar to your I9505, it is probably because of the radio/modem which was designed for the T-Mo model. There should be links in that forum about no WiFi, etc.
Rob
Hello gang. Got a new circuit board installed two weeks ago. Got the phone back, started setting it up, and after about an hour the touchscreen quit working. >8\
I emailed the shop and they said "could be because you're rooted."
Smelled like bull**** to me, but giving them the benefit of the doubt I figured I'd try to flash back to stock. (Which I WAS actually stock, I had the 4.4.4 OTA update, and then rooted and de-bloated.)
Anyway, I downloaded the "Stock firmware" (SGH-M919-UVUAMDB-k0nane.tar.md5) from post 1 in the title thread and flashed it with Odin.
SEEMS to be working, but oddly enough I have a M919UVUFNH7 baseband and bootloader, but Android 4.4.2, which based on my reading, should be impossible?
Also, like several other posters, I have no wifi.
In any event, I am currently downloading the NH7 firmware from sammobile. Says 2 hours to go.
Will try to flash that with Odin and we'll see what happens. Anyone have suggestions in the meantime?
OK - follow-up. I downloaded M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar and flashed it with Odin. Even though Odin said "Boot" and "Modem" in the flashing process, I still seem to have NH7 bootloaders and baseband.
Help?
Well, never mind. I don't care anymore. Tried to replace my glass and cracked the digitizer. Dunno if I'm down to drop another $120 on this thing now.
$300 purchase price
$100 circuit board replacement
$12 glass
Now $120 for a display? I might just call knock it off with this thing.
Hey,
I have some old samsung ace 2 that I was experimenting around with, wanted to try and get some 5.1.1 ROM on it. But first I figured I needed to get some kernel on it, though I did something which now means that during bootup it is stuck on the samsung galaxy ace 2 logo. I can access ODIN mode, though cant access recovery mode. The battery mode also seems to be broke too as it just displays a loading symbol. So far I have flashed the EK kernel on it with what seems to be a success according to ODIN mode. Also note that Samsung KIES tries to connect to my device in ODIN mode but it never connects and troubleshooting doesnt do anything.
I tried to flash stock firmware to it through the odin software whilst my phone was in odin mode, though it displays a bunch of stuff in the odin pc software then attempts to reboot my phone though it just gets stuck on the boot logo again without odin really doing much here are the logs:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8160XXLD8_ready_to_root_ANT.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> kernel.bin.md5
<ID:0/003> NAND Write Start!!
<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)
Reckon my device is still salvagable from this hole I have dug myself in?
i am also having the same problem. tried to flash stock firmware with and without pit, still can't work :crying:
and i don't have jtag and don't know how to use it even if i have jtag :crying:
My SM-T110 is stuck in bootloop. I can use download mode and not recovery.
I have tried so far:
1) Start in recovery mode by pressing vol up, home and power buttons at once.. i get a dead android logo and "NO COMMAND"
2) Flash new firmware by downloading stock software and using ODIN for flashing. It fails.
3) Install TWRP and CWM - again both fail with ODIN.
I tried 3 different cables with odin but get same result.
I googled for days and had no luck so i hope you can help me.
ccsrichman said:
My SM-T110 is stuck in bootloop. I can use download mode and not recovery.
I have tried so far:
1) Start in recovery mode by pressing vol up, home and power buttons at once.. i get a dead android logo and "NO COMMAND"
2) Flash new firmware by downloading stock software and using ODIN for flashing. It fails.
3) Install TWRP and CWM - again both fail with ODIN.
I tried 3 different cables with odin but get same result.
I googled for days and had no luck so i hope you can help me.
Click to expand...
Click to collapse
what version of Odin are you using?
Give THIS version a try.
If it fails, post a screenshot of Odin.
I tried 3.09, 1.something and now yours 3.07.. still no luck. I cant upload a screenshot because im a new user. but thats what it says with 3.07
I have auto reboot and f reset time on. nothing else and i chose PDA which is for my region and for sm-t100
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T110XXUANI9_T110SEBANH2_T110XXUANI9_HOME.tar.md5 is valid.
<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> timh.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> obm.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
ccsrichman said:
I tried 3.09, 1.something and now yours 3.07.. still no luck. I cant upload a screenshot because im a new user. but thats what it says with 3.07
I have auto reboot and f reset time on. nothing else and i chose PDA which is for my region and for sm-t100
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T110XXUANI9_T110SEBANH2_T110XXUANI9_HOME.tar.md5 is valid.
<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> timh.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> obm.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've seen other people have success by trying different cables or sometimes even other computers. Other than that, I have no other ideas.
Anybody else has any ideas ?
gr8nole said:
I've seen other people have success by trying different cables or sometimes even other computers. Other than that, I have no other ideas.
Click to expand...
Click to collapse
BTW Odin is written in white in download mode not red as others have.. and when i try to use odin the upper left corner goes paritially black.. like theres a black box covering half of the text there
ccsrichman said:
BTW Odin is written in white in download mode not red as others have.. and when i try to use odin the upper left corner goes paritially black.. like theres a black box covering half of the text there
Click to expand...
Click to collapse
And the text there is:
ODIN MODE
PRODUCT NAME: SM-T110
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
nothing else
Also a newbie with the Tab TM-110
Hi there
Since we are not many here with our device i thought i should send you a message.
Unfortunately i do not have a solution for your problem but maybe it helps if you take a look at what i experienced so far.
I hope you can find my Thread by my profile.
Have you tried to use a different PC yet for flashing with Odin? Would be interesting to know if it helped.
So. Don`t give up. There will be a solution. :good:
Naturestone
I'm having the same issue, anyone can help?
same error GT-I8200 2ND partition error