Develop Bugs

[Q] [Brrrricked] GN wont past Google logo, electrical or software disease..

hey gays,
so I drop my my phone last night when Plugging it in.
Now my phone wont boot on battery and only shows Google logo for a few seconds before showing battery icon again when plugged in.
I went to a store to test my battery. They told me that my GN was demanding for like 5/6 Ah to work . Weren't aware if the issue was hard or software.
My GN is rooted and worked fine until the fall. Download mode works where the recovery mode doesn't.
Would appreciate any help preventing for spending many euros to fix it.
Thx !

What do you mean recovery doesn't work?
If you boot to fastboot scroll to recovery and accept, what do you see?

Been able to launch recovery. Wipe and then install.... Crash at the beginning of installation. Battery icon shows off again. Now cant' access to recovery mode (phone shows battery icon before reaching the recovery)
i'll let the phone charge a bit then try again but I think I'm doomed
:crying:

What's the error that you see when installation of the ROM is aborted?
a maguro wrote this.

Guillauminho said:
Been able to launch recovery. Wipe and then install.... Crash at the beginning of installation. Battery icon shows off again. Now cant' access to recovery mode (phone shows battery icon before reaching the recovery)
i'll let the phone charge a bit then try again but I think I'm doomed
:crying:
Click to expand...
Click to collapse
OK so no recovery mode. You said download mode (<Volume Down>+<Power>) works, is it still so? If it does, you may be able to easily rescue it with ODIN. If you have problem finding the ODIN images tell us your exact model (like I9250) and we will help.

Guillauminho said:
hey gays,
so I drop my my phone last night when...
Click to expand...
Click to collapse
Ummm hey what lol ^^^^
“Power-lust is a weed that grows only in the vacant lots of an abandoned mind. ”
― Ayn Rand >^.^<

DowntownJeffBrown said:
Ummm hey what lol ^^^^
“Power-lust is a weed that grows only in the vacant lots of an abandoned mind. ”
― Ayn Rand >^.^<
Click to expand...
Click to collapse
I lol'ed hahaha..

gay?
sent from my sexy Nexy

paarthdesai said:
gay?
sent from my sexy Nexy
Click to expand...
Click to collapse
Ahahaha
xD

Guillauminho said:
hey gays,
so I drop my my phone last night when Plugging it in.
Click to expand...
Click to collapse
I'm a dude and I find this offensive
Sent from my Nexus 7 using xda premium

RohinZaraki said:
I'm a dude and I find this offensive
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
You are not the only one
Sent from my Sensational Sensation using Tapatalk 2

You people had fun wothout me,
Btw did you reflash the firmware?
Also i'm 101% machismo man.
This post is in compliance with the national potato safety regulation.
[Galaxy S 4 LTE]

Guillauminho said:
hey gays,
Click to expand...
Click to collapse
The rest of us don't get a greeting?

veeman said:
The rest of us don't get a greeting?
Click to expand...
Click to collapse
I know right I feel discriminated against. I wanted to help this guy but I guess cause I'm straight my knowledge is not wanted
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power.” ― David Brin >^.^<

Aha I meant gUys. I'll try to fix it with odin. My device is a 9250 Maguro, so if you had a tutorial or something like that sould be great I dont want to brick it more if possible.

1) Read here: http://forum.xda-developers.com/showthread.php?t=2065470
2) Follow instructions.
3) ????
4) Profit!!!

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.4.2.2.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> 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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> bootloader.img
<ID:0/005> radio.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> __Xmit Write fail
<ID:0/005> XmitData Fail..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
dammit

Guillauminho said:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.4.2.2.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> 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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> bootloader.img
<ID:0/005> radio.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> __Xmit Write fail
<ID:0/005> XmitData Fail..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
dammit
Click to expand...
Click to collapse
A bit of Googling "__Xmit Write fail" turned some tips:
Try to connect to other USB port (and without USB hub). Try another computer. Try uninstalling the drivers and installing again (search "Universal Naked Drivers"). My tip: try another USB cable.
If nothing helps, could be a really bricked device (broken hardware)

Hey guys,
got pretty busy and didn't have the time to take care of my phone.
But still nothing is working, I have a Phone-Yellow Triangle-Computer issue and I can't get my phone back to stock
So desperate, if anybody has a solution...

FYI when I plug my device in, a message appears with "OMAP4440" to install.. I have valide drivers but still

[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/

[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.

[Q] Stock Rom ODIN Fail

So here's the Story.
My M919 has been running CM11 for awhile now and I want to go back to stock. So I grabbed the firmware from samsung-updates (would post link but not allowed to), loaded it up on Odin3 v3.09, and hit Start. Well, ODIN is now showing a red "FAIL!" and both the progress bars on my phone and Odin stopped moving. I've never gotten a Fail in Odin before, so I'm not sure how to proceed.
Odin Message Log:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNB4_M919TMBFNB4_M919UVUFNB4_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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
An Image of Odin can be found here:
i imgur com / mvTrRyj png

BWatson236 said:
So here's the Story.
My M919 has been running CM11 for awhile now and I want to go back to stock. So I grabbed the firmware from samsung-updates (would post link but not allowed to), loaded it up on Odin3 v3.09, and hit Start. Well, ODIN is now showing a red "FAIL!" and both the progress bars on my phone and Odin stopped moving. I've never gotten a Fail in Odin before, so I'm not sure how to proceed.
Click to expand...
Click to collapse
What is your current bootloader and baseband version? If, at some point in the past, you have updated your modem/baseband but left your bootloader a previous version, you will likely encounter problems with using Odin. If that's the case, your best bet would be to manually revert only your modem/baseband to match your bootloader version and try the full stock firmware flash again.

I have never done anything regarding my baseband (to my knowledge), and as far as bootloader, I've only ever toggled its locked state. I wouldn't know how to check the versions without turning off my device, but everywhere I've read the notice of not turning off your phone while its in download mode is a helpful one. Odin is still just like that screenshot and my phone is still frozen at that progress bar. I have no clue about how to stop it or whatnot because I've never ran into issues before.

Do a battery pull, restart phone. If you can access the play store d/l Samsung info app, run it and find out all of the info you need.
Pp.

Pulled the battery and reboot. Got the "Firmware updated an Issue" error. Noticed it had said ODIN at the top so I tried the flash again and it worked. Thanks for the help guys.

That's the reason a lot of devs tell you to uncheck reboot on Odin and do a battery pull and flash again.
Pp.

Bricked Ace 2 - Can access Odin but not Recovery

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 Samsung Galaxy Note II get's stuck in the logo(N7100)

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.