Related
Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
vivelafrance said:
Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
Click to expand...
Click to collapse
where odin failed exactly?
did you try changing usb port? kies totally disabled? original usb cable?
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
vivelafrance said:
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
Click to expand...
Click to collapse
one more thing, remove battery for a couple of minutes, then try with odin 1.85
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
vivelafrance said:
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
Click to expand...
Click to collapse
i dont know if flashing pit file along with the firmware will work
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
vivelafrance said:
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
Click to expand...
Click to collapse
pit file is flashed with the firmware. choose the right pit for your device! re-partition will be checked automatically when you select the pit file.
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
vivelafrance said:
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
Click to expand...
Click to collapse
did you flash firmware with the pit file at same time and didnt work?
almost you did everything.
try to change computer if available.
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
vivelafrance said:
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
Click to expand...
Click to collapse
If you haw acess t dawnload mod you are nhot bricked pleas go and try other pc
Sent from my GT-I9505 using xda premium
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
this is surely NOT a mobile issue if you can enter into download mode.
i had the exact issue a month ago when i had note2.
if you can't try it on another pc, try :
1) uninstall skies completely
2) unisnstall usb drivers
3) reboot the pc
4) connect your s4 in download mode to your pc.
5) let your pc install freah usb drivers
6) start odin and flash
7) if still you get the same error download a different verison of the official rom and try flashing.
i followed the above procedure couple of times and was finally able to install the rom. the issue is either with the drivers or the rom.
Sent from my GT-I9500 using xda app-developers app
bricked for sure
vivelafrance said:
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
Click to expand...
Click to collapse
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Bluetoth10 said:
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Click to expand...
Click to collapse
thnx. yeah, flashing the PIT actually always worked but it was the only thing that worked! lol
DenmarkRootN00b said:
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
vivelafrance said:
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
Click to expand...
Click to collapse
good luck at least i just thought it would work by doing it in recovery but yeah... warranty is better.. if not.. then keep trying if they wont replace it
ok I FINALLY could access the stock recovery, did a full wipe and everything is back in order now, works perfectly.
THANKS to all!
Hello everyone! Its been a while since my rooting days(HTC ONE) and I'm a bit if not very rusty . I recently bought a Galaxy Tab 4 7.0. I attempted a root process through Odin and of course...it failed. Now I am stuck in the download mode and no matter what combination of buttons I use it returns there. I tried to see if I can get the original firmware through samfirmware.com for t230NU but to no avail. Any suggestions? I'd really appreciate it as I need the tablet. :fingers-crossed:
[email protected] said:
Hello everyone! Its been a while since my rooting days(HTC ONE) and I'm a bit if not very rusty . I recently bought a Galaxy Tab 4 7.0. I attempted a root process through Odin and of course...it failed. Now I am stuck in the download mode and no matter what combination of buttons I use it returns there. I tried to see if I can get the original firmware through samfirmware.com for t230NU but to no avail. Any suggestions? I'd really appreciate it as I need the tablet. :fingers-crossed:
Click to expand...
Click to collapse
stock firmware
http://forum.xda-developers.com/showthread.php?t=2778374
root
http://forum.xda-developers.com/showpost.php?p=53020637&postcount=87
Android Terminal Emulator cant find mrw
ShinySide said:
stock firmware
http://forum.xda-developers.com/showthread.php?t=2778374
root
http://forum.xda-developers.com/showpost.php?p=53020637&postcount=87
Click to expand...
Click to collapse
Thank you ShinySide for all your help! I was able to root successfully however when I try to replace vroot with Superuser with the terminal its unable to find the mrw file. I did extract and place the folder to the internal storage. I tried putting the file on the sdcard and that did not work either. What i ended up doing was downloading Superuser from the playstore. Will this have the same effect and will it update the binary correctly? My last question is-My Tab4 is says its a model T230NU but when i registered it n Samsung it shows SM-T230NZWAXAR...will the stock firmware conflict since the build is T230NUUEUOANE2?
Sorry for all the newb questions. I'm so glad I was able to unbrick my device and root though...Thank you so much!
[email protected] said:
Thank you ShinySide for all your help! I was able to root successfully however when I try to replace vroot with Superuser with the terminal its unable to find the mrw file. I did extract and place the folder to the internal storage. I tried putting the file on the sdcard and that did not work either. What i ended up doing was downloading Superuser from the playstore. Will this have the same effect and will it update the binary correctly? My last question is-My Tab4 is says its a model T230NU but when i registered it n Samsung it shows SM-T230NZWAXAR...will the stock firmware conflict since the build is T230NUUEUOANE2?
Sorry for all the newb questions. I'm so glad I was able to unbrick my device and root though...Thank you so much!
Click to expand...
Click to collapse
Post the exact terminal output. You shouldnt have any issue
Theres 2 model numbers. One for the white one for the black. Your tab 4 is SM-T230NZWAXAR which is the white one. SM-T230NYKAXAR is the blacks model number. It doesnt matter which you have its the same firmware. Samsung is just reading your full model number,
hi, iam the same problem, just 3 days ago my tab 4 7" (white) was stuck in a blacl screen with a yellow triangle, said: firmware upgrade encountered an issue, please select recovery mode in kies & try again.
The problem here is i cant enter in DOWNLOAD mode, in other tutorials said, for cellphones, that i need to put over the battery, but, in a tablet, how can i do this? i download a firmware from sammobile, my model number said SM-T230NU , i cant find the american version (i purchase this in radioshack USA) but i downlod the mexican version of Telcel, but nothing, OdIn always find an error, watch:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
THIS IS ANOTHER try:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0ANE6_T230OXX0ANE2_T230XXU0ANE6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> timh.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
please i need help.
and about the post of ShinySide (http://forum.xda-developers.com/showthread.php?t=2778374 ) what is the diference about NE2 firmware and ND9 firm?
nismo87 said:
hi, iam the same problem, just 3 days ago my tab 4 7" (white) was stuck in a blacl screen with a yellow triangle, said: firmware upgrade encountered an issue, please select recovery mode in kies & try again.
The problem here is i cant enter in DOWNLOAD mode, in other tutorials said, for cellphones, that i need to put over the battery, but, in a tablet, how can i do this? i download a firmware from sammobile, my model number said SM-T230NU , i cant find the american version (i purchase this in radioshack USA) but i downlod the mexican version of Telcel, but nothing, OdIn always find an error, watch:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
THIS IS ANOTHER try:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0ANE6_T230OXX0ANE2_T230XXU0ANE6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> timh.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
please i need help.
and about the post of ShinySide (http://forum.xda-developers.com/showthread.php?t=2778374 ) what is the diference about NE2 firmware and ND9 firm?
Click to expand...
Click to collapse
Your problem is you are trying to flash the wrong firmware. Youre trying to flash a firmware meant for data/service enabled tabs. Check my first post in this thread. Flash one of those.
Just bug/kernel fixes.
btw if youre seeing that message, you are in download mode.
Cant find mrw file
ShinySide said:
Post the exact terminal output. You shouldnt have any issue
Theres 2 model numbers. One for the white one for the black. Your tab 4 is SM-T230NZWAXAR which is the white one. SM-T230NYKAXAR is the blacks model number. It doesnt matter which you have its the same firmware. Samsung is just reading your full model number,
Click to expand...
Click to collapse
i have tried several times and still the same result. I get this message and then the tablet reboots. The Superuser app I downloaded from the Playstore did update the binary and all. However i would like to know what I did wrong for future reference with the mrw file. Thanks!
ShinySide said:
Your problem is you are trying to flash the wrong firmware. Youre trying to flash a firmware meant for data/service enabled tabs. Check my first post in this thread. Flash one of those.
Just bug/kernel fixes.
btw if youre seeing that message, you are in download mode.
Click to expand...
Click to collapse
thanks for the answer, but, excuse about my question, in u`r post about the firmwares, i just download this: Latest Firmware Version Download NE2, (the first link posted) but said me the same message in odin, (FAIL) i dont know if the options in ODIN are bad, i choose auto rebot and F.Reset Time.
or, need i erase the termination md5 with only .tar?
[email protected] said:
i have tried several times and still the same result. I get this message and then the tablet reboots. The Superuser app I downloaded from the Playstore did update the binary and all. However i would like to know what I did wrong for future reference with the mrw file. Thanks!
Click to expand...
Click to collapse
Do a search for each of those file names and give me the exact file names and locations. Someone else mentioned on another thread they had to ediit the script because they were a little different for some reason for them.
nismo87 said:
thanks for the answer, but, excuse about my question, in u`r post about the firmwares, i just download this: Latest Firmware Version Download NE2, (the first link posted) but said me the same message in odin, (FAIL) i dont know if the options in ODIN are bad, i choose auto rebot and F.Reset Time.
or, need i erase the termination md5 with only .tar?
Click to expand...
Click to collapse
Na those options wouldnt matter. That first time you flashed, loke_1st.bin flashed successfully then loke_2nd.bin failed. You might need to find a pit file for the tab 4 7inch and re-partition the device. Only one tho.... to get the pitfile you need hiemdall and hiemdall isnt compatible with the tab 4. least not yet. I saw a post a while ago for creating a pitfile on a device. Let me see if I can find it and see if itll work on my tab and create one and Ill post it if I can find it and create one
Okay this is all i can find. Just one issue...I have straight linux and no windows on my pc so I cant use or try to use it to get the pit, so 2 options if you want to try repartitioning it, try using this tool in download mode or find someone with windows willing to try to get the pitfile from their device
http://forum.xda-developers.com/galaxy-s2/orig-development/tool-updated-09-06-14-efs-professional-t1308546
ShinySide said:
Na those options wouldnt matter. That first time you flashed, loke_1st.bin flashed successfully then loke_2nd.bin failed. You might need to find a pit file for the tab 4 7inch and re-partition the device. Only one tho.... to get the pitfile you need hiemdall and hiemdall isnt compatible with the tab 4. least not yet. I saw a post a while ago for creating a pitfile on a device. Let me see if I can find it and see if itll work on my tab and create one and Ill post it if I can find it and create one
Click to expand...
Click to collapse
OK, thanks for the support, i will considering make a donation for this $$
so, in conclusion, iam really ina hole with this issue, no? i dont know how i can get brick in this form my tablet, only 3 weeks with it and is stuck...
i dont know much about this and samsung devices, but, need i another file apart of the firmware? the Pit file?
nismo87 said:
OK, thanks for the support, i will considering make a donation for this $$
so, in conclusion, iam really ina hole with this issue, no? i dont know how i can get brick in this form my tablet, only 3 weeks with it and is stuck...
i dont know much about this and samsung devices, but, need i another file apart of the firmware? the Pit file?
Click to expand...
Click to collapse
Check my previous post. I had just edited while you were responding Haha I have the donation link up because some people asked if I had one when I was compiling Carbon for s4's. I never accept them tho so its just there for "show" Ahaha
Its just one file. Contains all the partition block sizes, names, etc etc and willl delete everything and repartition the devices partitions, etc etc
Im guessing the loke bins are the bootloader. And since one flashed for you, it might be failing at a check point.
ShinySide said:
Check my previous post. I had just edited while you were responding Haha I have the donation link up because some people asked if I had one when I was compiling Carbon for s4's. I never accept them tho so its just there for "show" Ahaha
Its just one file. Contains all the partition block sizes, names, etc etc and willl delete everything and repartition the devices partitions, etc etc
Im guessing the loke bins are the bootloader. And since one flashed for you, it might be failing at a check point.
Click to expand...
Click to collapse
Hi again Shinyside,
today was a great day for my tablet jeje, its ALIVE again¡¡¡¡¡¡
what i made?
Just desinstall KIES, and reboot the Pc, install again the drivers for samsung, after, download again the Original firmware from your Link ( chrome://mega/content/secure.html#!I49V3YZB!LkqiYAvZF0dyL0YMbVMGlGWIhn7BQbFi84z4CIFQhKw
i downoad again because, sometimes in large files, the download is corrupted for X reason, unzip this in desktop (i dont know if this is good or not).
the next step was plug to charge for 1 hrs the tab 4, with the black screen turn on, Open Odin 3.07 , wait 2 minutes and upload the ND5 file previous downloaded, plug the TAB 4 in the Pc with (this is important) the OEM cable, i was plugin with other micro usb in the past attempted, so, just when Odin finish to charge 100% the firmware, just press START and wait a couple of minutes, the tablet autoreboot and now is alive.
but... i dont know but when my tab turn on again, all apps, pictures,etc was there so, i dont know if my tablet only was bricked temporarily or not completely bricked..... i dont know, only know that i have a tab again and thanks Shinyside for all support.
So, your link about donation is working or not? i want to invite u a beer, minimum :silly:
i want leave the Odin record about this, if anybody have the same problem:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> param.lfs
<ID:0/003> DTim.Primary
<ID:0/003> DTim.Recovery
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> NVM.img
<ID:0/003> cache.img
nismo87 said:
Hi again Shinyside,
today was a great day for my tablet jeje, its ALIVE again¡¡¡¡¡¡
what i made?
Just desinstall KIES, and reboot the Pc, install again the drivers for samsung, after, download again the Original firmware from your Link ( chrome://mega/content/secure.html#!I49V3YZB!LkqiYAvZF0dyL0YMbVMGlGWIhn7BQbFi84z4CIFQhKw
i downoad again because, sometimes in large files, the download is corrupted for X reason, unzip this in desktop (i dont know if this is good or not).
the next step was plug to charge for 1 hrs the tab 4, with the black screen turn on, Open Odin 3.07 , wait 2 minutes and upload the ND5 file previous downloaded, plug the TAB 4 in the Pc with (this is important) the OEM cable, i was plugin with other micro usb in the past attempted, so, just when Odin finish to charge 100% the firmware, just press START and wait a couple of minutes, the tablet autoreboot and now is alive.
but... i dont know but when my tab turn on again, all apps, pictures,etc was there so, i dont know if my tablet only was bricked temporarily or not completely bricked..... i dont know, only know that i have a tab again and thanks Shinyside for all support.
So, your link about donation is working or not? i want to invite u a beer, minimum :silly:
i want leave the Odin record about this, if anybody have the same problem:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> param.lfs
<ID:0/003> DTim.Primary
<ID:0/003> DTim.Recovery
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> NVM.img
<ID:0/003> cache.img
Click to expand...
Click to collapse
Sweet good deal man. Glad you got iit back up and running. I didn't even think about the cable. We an issue with using some different usb cables on the s4 too. But glad you got it back up and running. And yeah it works
the next step is, how to root my tab 4......
nismo87 said:
the next step is, how to root my tab 4......
Click to expand...
Click to collapse
Check post 2
ShinySide said:
Check post 2
Click to expand...
Click to collapse
Hope this is ok area to post this in. I am having a problem with Tab 4 T230NU wifi only. I am trying to get to download mode to flash with Odin, but I can not? It flashes on with screen. "Firmware Upgrade encountered an error an issue. Please select recovery mode in Kies & try again. " It just flashes then turns back on... I tried holding home and volume up. Home and volume down. home and volume up and down in the middle. I tried volume up, volume down. I have charged this for quite a while also, few hours. I also have a Jig that works with the s3 to go to download mode, that did not work.
I think if I can get to download mode I can get working again, but have not been able to get to that. Any help please? Thank you in advance.
jaredlappa said:
Hope this is ok area to post this in. I am having a problem with Tab 4 T230NU wifi only. I am trying to get to download mode to flash with Odin, but I can not? It flashes on with screen. "Firmware Upgrade encountered an error an issue. Please select recovery mode in Kies & try again. " It just flashes then turns back on... I tried holding home and volume up. Home and volume down. home and volume up and down in the middle. I tried volume up, volume down. I have charged this for quite a while also, few hours. I also have a Jig that works with the s3 to go to download mode, that did not work.
I think if I can get to download mode I can get working again, but have not been able to get to that. Any help please? Thank you in advance.
Click to expand...
Click to collapse
You are in download mode
Help!
Okay so I've been trying to root my Galaxy Tab 4 and everything I attempt fails, its stuck on ODIN mode and I cant seem to root it, recover it or anything. I need help
Devon S said:
Okay so I've been trying to root my Galaxy Tab 4 and everything I attempt fails, its stuck on ODIN mode and I cant seem to root it, recover it or anything. I need help
Click to expand...
Click to collapse
D,
while in odin reflash your custom recovery for your device with auto/restart checked.
odin will remain stuck in that mode until it restarts after successfully flashing an image.
m
This worked for me I was in soft brick I don't know if this will for you
1.download Odin v3
2.download twrp (sm-t230)
3.connect your tab to your PC and turn it on (make sure you have drivers installed)
4.you should see ADDED! ON ODIN (if you don't see it you probably didn't install the drivers correctly) click PDA and select the twrp rar file 5.wait for it to flash it (your tab may or may not reboot wait for Odin to say done or succeeded)
6.download a stock ROM for your tab
7.move the stock ROM onto a SD card
8.put SD card into tablet and mount it
9.tap install and look for the stock ROM
10.you may need to clear dalvik cache and/or data
I hope it helped. Pm me if you need help were to get the drivers and the stock ROM I'll be glad to help!
Sent from my SM-T230 using XDA Free mobile app
I have Samsung Galaxy Grand Prime SM-G531F and I installed a pre rooted firmware and everything worked nicely. Then I was messing around with applications and put xmodgames to be a system app via Lucky Patcher. The phone shut down because the battery was empty and I put it to charge. The next day I tried to turn it on it was stuck on booting logo forever, the particles around Samsung logo were still swinging tho. I tried to flash original firmware with Odin, but I got write operation failed error. Same thing happens when I try to flash recovery. If anyone can help that will be great. I dont wanna spend money on a technician to fix it if it's possible to be fixed by myself.
Edit : I tried wiping cache with volume up + home + power menu and wipe to factory settings but it still didn't help.
Send me the Odin log or ss as to fix it you need to flashthe stock firmware of your device model. Since you used pre rooted firmware to root the device I assume you do not have twrp or any other custom recovery. BTW using a pre rooted firmware is the last option to root, you should try to root with alternative methods first like using twrp
This appears when I try to flash stock firmware. I made sure that the stock firmware fits my region.
<ID:0/003> 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/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> Sboot.bin
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Same thing happens when I try to flash TWRP :
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any solution?
Sasser1 said:
Any solution?
Click to expand...
Click to collapse
Sorry for late reply but are you using the original Samsung USB cable as this problem is common with non Samsung cable , thin cables which are supposed to use only with charging and not intended for data transfer give this error (that's what I guess) but the line __XmitDataWrite_ is the error when using non Samsung cable which is not able to transfer data properly
I'm using a Tesla cable which is thin because my original cable was damaged and very hard for use. I will try dig around if I can find any thick Samsung cables or eventually buy one and I will be back with the reply.
The problem is, the Tesla cable is the only cable that can connect phone with the computer which Odin can recognize. I had no luck getting Odin to recognize my phone with other cables that I got in my house.
I got my original samsung cable and it's all working but one thing. It says that FRP Lock blocks the custom binary from installing. How can I disable that if I dont have access to my phone?
I managed to make it work. I installed the stock firmware and everything works nicely now. Thank you so much. One more question : How do I disable the FRP Lock so I can install TWRP and other mods that I need?
Sasser1 said:
I managed to make it work. I installed the stock firmware and everything works nicely now. Thank you so much. One more question : How do I disable the FRP Lock so I can install TWRP and other mods that I need?
Click to expand...
Click to collapse
Can you send me the screen shot of the developers option section I forgot something and don't have access to my grand prime as of now
My G935F shows "Could not do normal boot invalid kernel length" when attempting to boot into TWRP or turn on the device normally. The only thing I can access is ODIN. This happened after attempting to update TWRP and LineageOS. From looking online, I believe I can get a kernel and select the AP option in ODIN and flash a kernel as long as it is in .tar format. I was previously using PRIME kernel https://forum.xda-developers.com/s7-edge/development/kernel-prime-kernel-v1-4-0-t3678159 so I looked in the latest download from there but there are no .tar files, only a bootimg.tar.xz and a ramdisks.tar.xz. I tried extracting bootimg.tar.xz to a bootimg.tar and flashing that, but ODIN says it failed:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1210)..
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> g930eur-aosp-Image-r12p0
<ID:0/003> Unassigned file
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't know what I'm doing and I'm afraid to mess up my phone beyond repair with ODIN. Can someone please help me?
I tried flashing the zip from https://autoroot.chainfire.eu/#odin but ODIN gave me:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I ran ODIN as administrator and was able to flash Chainfire. I was then able to boot in normally, and after that flash TWRP again. Still not sure which step caused that issue but it is resoled now.
facing same problem.. please guide about chainfire..
invalid kernel length s7 edge
Hi .. looking for some help I recently rooted my s7 edge and a tried to put on a custom recovery (twrp) everything went well downloaded latest version for my device .. my phone still works fine just that when I turn phone off and try to go into custom recovery I get ... Could not do normal boot invalid kernel length.. and device turns off .. any help would be appreciated... thanks in advance ...
navnkd said:
facing same problem.. please guide about chainfire..
Click to expand...
Click to collapse
Put your phone into Download mode
Run Odin as administrator
Click AP and select CF-Auto-Root
Hit Start and you're done
If you did the flash before it crashed properly, you should have a stock recovery.
Good luck
---------- Post added at 07:59 PM ---------- Previous post was at 07:53 PM ----------
Gulmur6 said:
Hi .. looking for some help I recently rooted my s7 edge and a tried to put on a custom recovery (twrp) everything went well downloaded latest version for my device .. my phone still works fine just that when I turn phone off and try to go into custom recovery I get ... Could not do normal boot invalid kernel length.. and device turns off .. any help would be appreciated... thanks in advance ...
Click to expand...
Click to collapse
Is your device Rooted? If so. Download the TWRP app. And within the app you can download the newest version of TWRP for your device.
When the download is finished. Copy that file from your device to pc.
And then flash it again through odin. (use the TWRP you downloaded with your device..)
Trying to get working magiskhide action i flashed stock Boot.img now I have Could not do normal boot invalid kernel length
and the phone just refuse booting into recovery
same for me except i have S8 (G950F) and im on linux ;-;.
Hi!
!Total Newbie Alert!
I have a Galaxy S5 Active, SM-G870W. It was with Bell, but I unlocked and have been using another provider for some time now. I recently needed to install an app that needs root access, and figured I would be able to do the same.
In the distant past I had rooted some ancient android devices, so I read a bunch of pages, and feeling far too confident I pulled the trigger and tried to root my phone using the CF-Auto-Root tool from the firmware dot mobi website.
I entered SM-G870W, selected the only device option, hit Submit, Selected Android 6.0.1 (Build MMB29M.G870WVLU1CPF6), and continued to download a file:
cfar_samsung_sm-g870w_kltevlactive_mmb29m.g870wvlu1cpf6_t0.zip
I Extracted then launched the root.bat batch file, Odin Launched (Ver 3.12), I pick the AP as specified, and I get the following:
<ID:0/003> 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/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> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone stays at "Downloading... Do not turn off target!!"
I pulled the battery and rebooted into download mode again (Vol Down/Home/Power) and retried with the same file, and the same results.
I also tried powering up in recovery (Vol Up/Home/Power), but I get a message
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
Click to expand...
Click to collapse
At this point I am trying to get my device at least usable, I can restart in download mode no issue, but even after regenerating and redownloading, I am not able to get past this error.
I spent the last 6 or so hours going over posts here and elsewhere, with no luck, I tried Kies (Version 3.2.16084_2) and it says "The connected device is not supported by Kies 3" and the link to view supported devices on Samsungs site does not lead to any information. I also read somewhere that you can't root Android 6 images, but that post was 2014, and I found contradicting information elsewhere.
I would appreciate help on where to go from here, my priority is getting the phone working, rooted or not.
Thanks in advance!