Sorry of my poor English but because, which is only a translation of google. But i can read and understand english.
Unfortunately I am in despair, because apparently I shot my note. So you are my last hope.
Do not worry, I do not expect that Rocket-ROM was the cause, but still my note do not want.
I had recently been used the very cool Rocket V8, and then install the game from Gameloft M99. At the first call about the game loads down 1100MB, or rather it wants. So did release my misery, because every time at 70 MB to 100 MB, the note went into the SoD, and could only be by a long press the power button to move to restart. After several attempts to download via Wi-Fi yet to get out, then the my note shows only in the boot animation and stayed there seemingly stuck in a loop (until min to 30. Wait). Several attempts later, I tried in recovery-mode to delet cache and Davlik, but also did not lead to success. I then tried a in the recovery a full wipe-making, where the note was then stuck too (also up to 30 min. Wait).
Since this has not brought anything, I wanted to flash with Odin 3 (1.85) a stock-ROM (N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5), but in Odin "<ID:0/003> NAND Write Start!" remains standing.
I have at thecond trie to flash a three part ROM, but the log-screen from odin shows following:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXKJ1_CL627135_REV02_user_low_ship.tar.m d5 is valid.
<OSM> MODEM_N7000XXKJ1_REV_05_CL1067428.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXAKJ1.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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
...... and ........ stands and stands and stands .......... ...........
I have also tried to flash just a kernel, with the same result. Even my attempt to redefine the partitions (with suitable PIT) and then flash the firmware ends similarly, that confirms (again for 30 minutes waiting and nothing is happening.)
<OSM> Check MD5 .. Thurs unplug not the cable ..
<OSM> Please wait ..
<OSM> N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5 is valid.
Checking MD5 <OSM> Successfully finished ..
Leave <OSM> CS ..
<ID:0/003> Odin v.3 engine (ID: 3) ..
File <ID:0/003> analysis ..
<ID:0/003> Setup connection ..
<ID:0/003> Initialzation ..
Set PIT <ID:0/003> file ..
DO NOT TURN OFF TARGET <ID:0/003>!
I hope someone of you has an idea, because I really could cry!
P.S. CWM now I'm no longer pure, normal boot will stand with the Samsung logo. Download mode goes. The DL-counter shows number 1.
if you can go to download mode again your note is not killed
try to do same ones more time
it has to go right
did you do like this ?
{
"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"
}
Note sure if I got it right but it sounds liek you can still boot into recovery. Have you made Backup which you can restore?
I've already tried countless times today over again, even with PIT for the repartitioning.
If I use a PIT in the Flash plug operation stucks after the PIT.
In the recovery-mode can't I'm no longer, and my backups I have on the external SD moved.
I guess you put the phone into ODIN-mode by holding Vol- + midle key + On/Off right?
I have not had this before.. so you could try to flash again via ODIN that way.. in case you have not tried already. Not sure if KIES will communicate with the Note in ODIN mode. But also this would be worth a try.
thommic said:
I guess you put the phone into ODIN-mode by holding Vol- + midle key + On/Off right?
I have not had this before.. so you could try to flash again via ODIN that way.. in case you have not tried already. Not sure if KIES will communicate with the Note in ODIN mode. But also this would be worth a try.
Click to expand...
Click to collapse
1. So i have it do anytime.
2. Kies will not communicate with my Note in Odin-Mode.
A normal boot without push of the key-comnbination, let the note show the screen with smartphone ... "exclamation mark" ... PC.
try to download this rom
http://hotfile.com/dl/135702954/9c9d385/N7000XXKKA_N7000OXXKK6_XEO.zip.html
then thick PDA in odin
then put your note in download mode(odin mode) vol down+home+off button
then push start in odin
I have try it, but the result is:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000OXXKK6_N7000XXKK5_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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
and here stop the flash.
I give the Note back to Amazon.
pctelco said:
I have try it, but the result is:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000OXXKK6_N7000XXKK5_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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
and here stop the flash.
I give the Note back to Amazon.
Click to expand...
Click to collapse
just do a factory reset/clean install:reinstall all the sofware maybe its damaged..format your sd...and install a stock rom
Nicht zurück geben !!!
Follow this instruction
http://jjpda.blogspot.com/2011/11/n7000-how-to-flash-n7000zskk1-236.html
nowy57 said:
try to download this rom
http://hotfile.com/dl/135702954/9c9d385/N7000XXKKA_N7000OXXKK6_XEO.zip.html
then thick PDA in odin
then put your note in download mode(odin mode) vol down+home+off button
then push start in odin
Click to expand...
Click to collapse
First of all make sure the Kies is installed on your computer correctly. If the USB Samsung Drivers are corrupted ODIN will not be able to access Note properly! I would try to uninstall and install Kies again. Good luck!!!!
Haddar said:
First of all make sure the Kies is installed on your computer correctly. If the USB Samsung Drivers are corrupted ODIN will not be able to access Note properly! I would try to uninstall and install Kies again. Good luck!!!!
Click to expand...
Click to collapse
exactly !!
if you are not shure reinstal kies once more time by the newest version of kies
gerardroid said:
just do a factory reset/clean install:reinstall all the sofware maybe its damaged..format your sd...and install a stock rom
Click to expand...
Click to collapse
I can't do that. I came only in the DL-Mode, but not in CWM!
I would like to do so, but i can't.
Maybe this can help:
http://www.ebay.com/itm/UnBrick-USB...937128?pt=PDA_Accessories&hash=item3a6dc827e8
gerardroid said:
just do a factory reset/clean install:reinstall all the sofware maybe its damaged..format your sd...and install a stock rom
Click to expand...
Click to collapse
budalica said:
Nicht zurück geben !!!
Follow this instruction
http://jjpda.blogspot.com/2011/11/n7000-how-to-flash-n7000zskk1-236.html
Click to expand...
Click to collapse
Sorry, but this ended by the same results, then all my other tries to rescue my note.
I have no other option than to send the note back to Amazon.
pctelco said:
Sorry, but this ended by the same results, then all my other tries to rescue my note.
I have no other option than to send the note back to Amazon.
Click to expand...
Click to collapse
The ebay dongle supposedly works...
I have no problem in the DL mode to come, which should help me the USB JIG then?
Unfortunately I can not flash ROM with Odin, because it is always aborted.
@ hotweiss
You're right, supposedly!!?
Would have been interesting but the use of USB-JIG @ SGN is still ****ty.
edit:
@ pctelco
I wrote it already in another forum.
An USB-JIG can unbrick you phone. Can!
The procedure might go like this:
http://www.pocketpc.ch/galaxy-note-...tfernen-flashcounter-reseten.html#post1250472
I know this might seem pointless but it helped me before. Very simple step is unplug phone and do a complete shutdown(not restart) of your computer.
Related
Restoring A Stuck Samsung Galaxy SI, SII and SIII
Is your phone stuck like this?
{
"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"
}
Then read on! If not, this may only be useful for those who want to go back to the original Samsung Firmware.
Introduction
Too many people are getting stuck on the Samsung logo so I decided to make a tutorial on how to
get yourself off it. It is a simple tutoiral and noob friendly, but it will take time and patience because
the stock firmware is not just 300mb but can go into 1GB and more. This should on Samsung
Galaxy SI, SII, SIII. They are all tested and working, you may experiment on other phones if you
wish and you have no other choice. Read on for the downloads and instructions.
Downloads
Odin v3.07 - Click Here
Your Firmware - Find Here
Instructions
1. Go here and select your phone and its correct version's official firmware here: http://samsung-updates.com/latest-firmware/
2. Download Odin v3.07
3. Turn phone off completely and put it into download mode (Down Volume, Home Button and Power Button together).
4. After downloading the official firmware extract it and open Odin.
5. Select Auto Boot and F. Reset and put that .md5 file in the PDA section. NOTE: There should be COM: (PORT NUMB) in the first box.
6. Click Start and wait. If it succeeded then it will say PASS in green.
NOTE: This has worked for me and other people have confirmed it working for them after testing.
But if something more happens to your phone, I am not responsible.
Good luck.
Will be attaching more tutorials soon.
Sent from my GT-I9300 using xda premium
This is just a stock firmware flash via Odin as per multiple guides on the forum .
Its not getting off a stuck logo its re flashing full firmware in many cases a factory reset should be the first step or a reflash through recovery of the custom rom .
Multiple exact same guides in my view only confuse noobs .
jje
JJEgan said:
This is just a stock firmware flash via Odin as per multiple guides on the forum .
Its not getting off a stuck logo its re flashing full firmware in many cases a factory reset should be the first step or a reflash through recovery of the custom rom .
Multiple exact same guides in my view only confuse noobs .
jje
Click to expand...
Click to collapse
Got me off stuck on a logo.
Sent from my GT-I9300 using xda premium
AndroidPlant said:
Got me off stuck on a logo.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
A wipe data often fixes that too, if you have custom recovery,a dalvik/cache wipe could potentially fix it.
A re-flash of the Rom could fix it
.....indeed many things "could" fix it........I know your intentions are good, but could you refrain from posting links to this thread every time a problem comes up, because often the solution is much easier
There doesn't seem to be any i9300 firmwares on that site.
Hi, im doing everything as it says but gives me this
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help me
Try different USB cables and USB ports. Try flashing the latest stock ROM from sammobile.com.
help plz
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOF1_I9300OXXGOF1_I9300XXUGNB1_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Cant pass this part.
audit13 said:
Try different USB cables and USB ports. Try flashing the latest stock ROM from sammobile.com.
Click to expand...
Click to collapse
Yes, i've already done that still nothing.
Could it be hardware related issue?
You confirmed the model # in download mode? It fails with the original Samsung usb cables too?
OK first off I going to express my deepest apologies for starting a thread with an issue that has probably been answered 100 times... My problem is that I have tried every possible phrase that I know for search term pertaining to my particular issue and I am still stuck. SO I will be as details as possible and I hope and pray that at LEAST if I get kicked for starting this and the thread being shutdown, that someone will have posted "heres the link numb nuts be more careful next time".
OK so on with my issue. I have a Rogers Samsung Galaxy S4 I337M on 4.3, I tried to use chainfire's latest cf-Autoroot to root my phone and it just failed. Here is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltecan-jfltevl-sghi337m.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!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
As you can see when odin could not find the PIT I downloaded one and retried.
Anyway now I'm stuck on this:
{
"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"
}
and the top left may be important so here is the clearest shot of that:
Now I have tried to flash stock firmware that I downloaded from sammobile AND samsung update and no matter how many times I try to flash its the same thing over and over again (log):
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I then thought about trying Kies. First problem, Emergency firmware did not list my device. Then I tried firmware upgrade and initialize and even though the start button wouldn't show unless I plugged the phone in as download mode, once the firmware was finished downloading and ready to flash it would give me an error saying it couldn't not detect my device.
I am not sure is this is EVERYTHING I could have tried but to MY knowledge it is. Please help
And my deepest gratitude to anyway and all who point me to the right direction. I hope I have been as detailed as I possibly can be.
djkaozz said:
And my deepest gratitude to anyway and all who point me to the right direction. I hope I have been as detailed as I possibly can be.
Click to expand...
Click to collapse
Point you to the right direction, huh? How about the Q&A, Help & Troubleshooting subforum? Posting questions like this in the development subforum is a no-no.
mattdm said:
Point you to the right direction, huh? How about the Q&A, Help & Troubleshooting subforum? Posting questions like this in the development subforum is a no-no.
Click to expand...
Click to collapse
This is a start, my apologies AND a big thank you!
i encountered this before. although i cannot remember how i fixed it. few things to try though.
option A: download a stock rom from sammobile it is pretty straight forward on the site to select the correct stock rom. be careful when selecting though. make sure you get the correct version to match the bootloader. ex download the 4.4.2 stock rom from rogers if you had 4.4.2. the rom from sammobile is odin flash only. so put it in the pda and make sure your phone is in download mode if you can get to it
option B: if you cant get to download mode then you will have to try the firmware emergency recovery option on the actual samsung keis program. I cannot remember the steps for this but a google search should give directions
if either of these work you will be brought back to square one where you can start the root process over again. this time try a different rooting method. just incase.
Buddyjohn said:
i encountered this before. although i cannot remember how i fixed it. few things to try though.
option A: download a stock rom from sammobile it is pretty straight forward on the site to select the correct stock rom. be careful when selecting though. make sure you get the correct version to match the bootloader. ex download the 4.4.2 stock rom from rogers if you had 4.4.2. the rom from sammobile is odin flash only. so put it in the pda and make sure your phone is in download mode if you can get to it
option B: if you cant get to download mode then you will have to try the firmware emergency recovery option on the actual samsung keis program. I cannot remember the steps for this but a google search should give directions
if either of these work you will be brought back to square one where you can start the root process over again. this time try a different rooting method. just incase.
Click to expand...
Click to collapse
the problem is i did this and no matter what i am getting the results that are posted in the log above.
any other suggestions out there?
i appreciate the responses so far. thank you
Did you try the option that doesn't involve Odin? Also try changing USB cables
Sent from my SGH-I337M using Tapatalk
Use a different computer?
Adizzzle said:
Use a different computer?
Click to expand...
Click to collapse
thats another option i have tried to no success. it seems that even with the pit file its failing but no reason as to why
FIXED!!
djkaozz said:
thats another option i have tried to no success. it seems that even with the pit file its failing but no reason as to why
Click to expand...
Click to collapse
wow.... i fixed it... the solution is SO STUPID that embarrassed to say it.
Help
djkaozz said:
wow.... i fixed it... the solution is SO STUPID that embarrassed to say it.
Click to expand...
Click to collapse
Do you remember what you did? Because i have the same problem
Winston.huang said:
Do you remember what you did? Because i have the same problem
Click to expand...
Click to collapse
i have the same problem. please do share!
Had the same problem. I was finally able to complete the update only after I inserted a SIM card and rebooted my computer.
djkaozz said:
wow.... i fixed it... the solution is SO STUPID that embarrassed to say it.
Click to expand...
Click to collapse
Are you for real? I have the same Canadian model as you, EXACT same problem and you find a solution and don't post it... Thanks bro, RIP Harambe
The problem was probably fixed by flashing a stock rom via Odin, factory wipe, and set up the rom.
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
So, one night, my Galaxy C9 Pro asks to update overnight. I placed it on charge and let it do its thing.
In the morning, it showed a black screen, with a single centred grey circle with a charging symbol inside it.
After unplugging, the Samsung splashscreen appeared, then started bootlooping indefinitely.
After flashing the stock rom:
AP_C9000ZHU1AQA1_CL10182499_QB12232143_REV00_user_low_ship_MULTI_CERT.tar
BL_C9000ZHU1AQA1_CL10182499_QB12232143_REV00_user_low_ship_MULTI_CERT.tar
CP_C9000ZHU1AQA1_CL10182499_QB12232143_REV00_user_low_ship_MULTI_CERT.tar
HOME_CSC_ZZH_C9000ZZH1AQA1_CL10182499_QB12232143_REV00_user_low_ship_MULTI_CERT.tar
with OdinV3.11, and with it saying "PASS", i unplug.
Phone shows the usual splashscreen, with an added "RECOVERY BOOTING..." at the top, and continues to bootloop again.
What now?
Just download the latest firmware from www.sammobile.com choose your C9 Pro variant/region which variant of your C9 pro use latest odin v3.12.7 don't tick reparation just tick f-reset and auto reboot and now this time don't put Home CSC to csc slot just put CSC then flash it
Shozaf.shah said:
Just download the latest firmware from www.sammobile.com choose your C9 Pro variant/region which variant of your C9 pro use latest odin v3.12.7 don't tick reparation just tick f-reset and auto reboot and now this time don't put Home CSC to csc slot just put CSC then flash it
Click to expand...
Click to collapse
OK, im already downloading now, 50% done. complete in another 4 hours.
Will post back afterwards.
Meanwhile, anyone have any other ideas?
welp, it didnt work.
KaixaR said:
welp, it didnt work.
Click to expand...
Click to collapse
I'd recommend trying to flash this firmware APL2 first. It should be the very first firmware the phone was released with.
As mentioned above use Odin v3.12.7 to flash all the files and use regular CSC file NOT HOME_CSC. That will wipe the internal sd so the phone will be back to it's OOTB condition.
I was having the same issue with my girlfriend's C9 Pro after she received the OTA for 7.1.1 (Guess I need to email Samsung about this )
Also if you can't boot into download mode due to the phone automatically trying to go into recovery at every boot cycle you should:
Fully discharge the phone
Press button combination Power+Home+Vol Down WHILE plugging the charger (have somebody give you a hand )
Leave the phone charging for an hour or so to make sure when you flash it there is no risk of the phone dying
Hope that helps you :good:
alonso_91 said:
I'd recommend trying to flash this firmware APL2 first. It should be the very first firmware the phone was released with.
As mentioned above use Odin v3.12.7 to flash all the files and use regular CSC file NOT HOME_CSC. That will wipe the internal sd so the phone will be back to it's OOTB condition.
I was having the same issue with my girlfriend's C9 Pro after she received the OTA for 7.1.1 (Guess I need to email Samsung about this )
Also if you can't boot into download mode due to the phone automatically trying to go into recovery at every boot cycle you should:
Fully discharge the phone
Press button combination Power+Home+Vol Down WHILE plugging the charger (have somebody give you a hand )
Leave the phone charging for an hour or so to make sure when you flash it there is no risk of the phone dying
Hope that helps you :good:
Click to expand...
Click to collapse
Flashed with odin as you stated, heres what it looks like
{
"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"
}
After flashing, it was still bootlooping. Even after 30 minutes.
Still cannot access recovery, only download mode.
If i flash AP only, it removes the "recovery booting" message and when i plug in USB, it will show a battery charging sign
Ive tried flashing the firmware you posted, the newest firmware, and a firmware in between with no luck.
Contacted samsung in my country who pretty much told me to piss off because i didnt buy it from them (in that country)
Im running out of ideas and patience here
heres the log btw
<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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> cmnlib.mbn
<ID:0/003> keymaster.mbn
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> sec.dat
<ID:0/003> lksecapp.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> adspso.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<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)
Now you have to choose repartition option at the time to flash firmware But if still the problem is not resolved so it will be the hardware problem ?
I faced same situation with my C9008 and finally rooted it and flashed the following custom rom and works better than stock rom.
https://forum.xda-developers.com/c9-pro/development/rom-stock-rooted-debloated-deodexed-t3702643
Shozaf.shah said:
Now you have to choose repartition option at the time to flash firmware But if still the problem is not resolved so it will be the hardware problem ?
Click to expand...
Click to collapse
But i dont have the PIT file
I heard its rather dangerous
Yup download twrp flash it by odin then flash C9 pro Nougat custom rom by twrp try it https://forum.xda-developers.com/c9-pro/development/rom-stock-rooted-debloated-deodexed-t3702643
But the thing is, if a custom recovery doesnt fix it, im left with a warranty voided paper weight...
KaixaR said:
But the thing is, if a custom recovery doesnt fix it, im left with a warranty voided paper weight...
Click to expand...
Click to collapse
If it could be put in download mode and recognized by odin then it will be ok with custom roms.
Sent from my SM-C9000 using Tapatalk
KaixaR said:
So, one night, my Galaxy C9 Pro asks to update overnight. I placed it on charge and let it do its thing.
In the morning, it showed a black screen, with a single centred grey circle with a charging symbol inside it.
After unplugging, the Samsung splashscreen appeared, then started bootlooping indefinitely.
After flashing the stock rom:
AP_C9000ZHU1AQA1_CL10182499_QB12232143_REV00_user_low_ship_MULTI_CERT.tar
BL_C9000ZHU1AQA1_CL10182499_QB12232143_REV00_user_low_ship_MULTI_CERT.tar
CP_C9000ZHU1AQA1_CL10182499_QB12232143_REV00_user_low_ship_MULTI_CERT.tar
HOME_CSC_ZZH_C9000ZZH1AQA1_CL10182499_QB12232143_REV00_user_low_ship_MULTI_CERT.tar
with OdinV3.11, and with it saying "PASS", i unplug.
Phone shows the usual splashscreen, with an added "RECOVERY BOOTING..." at the top, and continues to bootloop again.
What now?
Click to expand...
Click to collapse
Did you get this fixed ? If yes, how ?
Thank you
Same problem help me plz how i trun on my device
Help. Sir samsung c9 pro. Automatic reboot without charger not power on after i flasj all file but same issue.
Shozaf.shah said:
Yup download twrp flash it by odin then flash C9 pro Nougat custom rom by twrp try it https://forum.xda-developers.com/c9-pro/development/rom-stock-rooted-debloated-deodexed-t37
Click to expand...
Click to collapse
I have the same issue, it is stuck in bootloop or samsung logo screen, I flashed it with stock ROM and it passed, But after booting it was still stuck on sumsung logo but it is showing "recovery booting" in the upper left screen. I tried to flash twrp but it fails because FRP blocked it. I can't unblock it because eom is off when i shot down. PLS help..
I also tried doing this and it didn't work for me :
I've been having problems with my phone after the Oreo update. (freezing / bootloops / random restarts)
Already did a factory reset on my phone but the issue was not fixed so I've decided to flash my phone but I'm having problems.
Details
Phone - SM-G935FD - Non Rooted
Software: Odin3 v3.13.1 - Downloaded from https://dl.sammobile.com/Odin3-v3.13.1.zip
Only Auto Reboot and F. Reset Time are ticket - Pit tab not changed. Loaded BL AP CP and CSC/HOME_CSC from firmware below.
Firmware - GALAXY S7 edge / SM-G935FD - PDA G935FXXU2EREM - Downloaded from https://updato.com/firmware-archive-select-model?record=36A47F5A6E2711E89F15FA163EE8F90B
After several retries, ODIN still fails to flash my phone. It gets stuck at system.img
Code:
<ID:0/005> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> modem_debug.bin
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4200 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hope you guys can help me out. Thanks!
What is the Phone model on the back of ur phone
SM-935what
Is your phone rooted?
Possibilities are that the firmware and your phone are non compatible also send a screenshot of your odin.
You might have the wrong version selected.
Usually if your getting bootloops it's best to flash 1 checkbox at a time.
Make sure the port doesn't say com 3.
Com4 or com7 is OK.
The boxes don't really matter except the boxes u are flashing like the ap cp bl and csc
If your phone is 935fd then it is also compatible with 935f firmware which is more updated latest version is ERG2. Dual sim functuality is the same.
pingufanpoy said:
What is the Phone model on the back of ur phone
SM-935what
Is your phone rooted?
Possibilities are that the firmware and your phone are non compatible also send a screenshot of your odin.
You might have the wrong version selected.
Usually if your getting bootloops it's best to flash 1 checkbox at a time.
Make sure the port doesn't say com 3.
Com4 or com7 is OK.
The boxes don't really matter except the boxes u are flashing like the ap cp bl and csc
If your phone is 935fd then it is also compatible with 935f firmware which is more updated latest version is ERG2. Dual sim functuality is the same.
Click to expand...
Click to collapse
Thanks, my phone is a SM-935FD stock before I tried all of this.
I'm using Com4. In the screenshots I'm trying to flash to older 7.0 firmware.
By one checkbox at a time you mean I can uncheck BL after success right?
{
"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"
}
Would it be ok to flash to SM-G935F firmware even if my phone is carrier locked?
Thanks
dhysics said:
Thanks, my phone is a SM-935FD stock before I tried all of this.
I'm using Com4. In the screenshots I'm trying to flash to older 7.0 firmware.
By one checkbox at a time you mean I can uncheck BL after success right?
Would it be ok to flash to SM-G935F firmware even if my phone is carrier locked?
Thanks
Click to expand...
Click to collapse
You can flash oreo 935f firmware on a 935fd but your phone will still be locked to smart sim.
The only way to unlock your sim imei would be to pay the company around 150 usd on average usually most companies won't do it because of money and people terminating their contracts early.
You will still be able to call and text from your smart Sim.
Just flash the CSC named SMA after installing if you want the smart branding it's not necessary tho.
pingufanpoy said:
You can flash oreo 935f firmware on a 935fd but your phone will still be locked to smart sim.
The only way to unlock your sim imei would be to pay the company around 150 usd on average usually most companies won't do it because of money and people terminating their contracts early.
You will still be able to call and text from your smart Sim.
Just flash the CSC named SMA after installing if you want the smart branding it's not necessary tho.
Click to expand...
Click to collapse
Thanks, I'm downloading the 935f oreo version.
Specifically this one: https://updato.com/firmware-archive-select-model?record=489AC01E8C1E11E89F15FA163EE8F90B
Hopefully it works, will post back here later
Unfortunately it still failed. Anything else I can try?
https://forum.xda-developers.com/showpost.php?p=77167218&postcount=14
ajox said:
https://forum.xda-developers.com/showpost.php?p=77167218&postcount=14
Click to expand...
Click to collapse
Thanks! Tried it but mine fails at the AP part I think.
download lastOdin3_v3.13.1
Fixed this. It was a USB cable issue.
What did you have to do?
dhysics said:
Fixed this. It was a USB cable issue.
Click to expand...
Click to collapse
Hey
I have a similar issue. The process starts and then just freezes, always in the same spot. I haven't even gotten through the BL file yet. At this point I don't mind if I have to completely wipe the phone and start over, I just want it to boot again.
I've tried with 2 different cables, though neither is an "original" cable as that one broke ages ago. Any tips?
Code:
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 5 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> param.bin
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dhysics said:
Fixed this. It was a USB cable issue.
Click to expand...
Click to collapse
Hi there
Do you know what cable you used? I am using a mixture of original Samsung cables but not sure if they are for the galaxy s7, probably S5 days.