Hi People
I Have a Problem, and the first thing I must say is: If you do not really know how do you can help me, please say nothing. Because, All that stuff you guys would tell me I ALREADY TRIED! So I need a Developer or someone who really knows what I am talking about.
Ok, as first: I am from austria, so I guess, I have the "EURO Tab"
My Problem Description:
I had a custom rom on my tab, it worked well.
then I saw a thread with the newest Official Firmware from samsung in this Thread:
http://forum.xda-developers.com/showthread.php?t=1004816
- I downloaded the file and extracted it..
- I took ODIN 1.7 and put the PDA, PHONE, CSC in their right places
(And here is the Clue!! >.<)
- I checked:
- Repartition- Auto Reboot- F.Reset Time- PHONE EFS CLEAR!!!- PHONE UPLOADER UPDATE!!!
- Then I clicked on START and it successfully finished....
BUT THEN
The TAB was rebooted, so far so good.. but it STUCKS at the FIRST "GalaxyTab" Logo.
I can reach the Download Mode again.
I CAN NOT!! reach the Recovery (Volume Up + Power Button)
Since then, I tried many different Kernels, Firmwares etc... but it is still the same!!
Maybe it happened, because i checked the Bootloader and EFS boxes...??
PLEASE, tell me what to do.
I have been trying for three Days to repair it, but I did not experienced any progress.
If you can help me, and you would need morde details, ask me, I am going to answere your questions.
Hi, I have the same problem
Unfortunately, I have a stock rom and not rooted EuroTab
the tab boots to logo samsung and remains stuck in a loop is the ton. Download Mod and Recovery I'm coming in only a hard reset I get not go.
Please help us.
have you guys try this http://forum.xda-developers.com/showpost.php?p=12315206&postcount=2 ? if you guys can go in Download mode, or the phone is showing : phone - ? - computer , it should work, so you will go back to the stock JMI firmware!
If you haven't yet, get ADB set up on your PC. It will save you a lot of effort. There are plenty of guides on XDA that can help.
Once you do that, you should be able to copy files to your sdcard over ADB and use the ADB logcat command to see what the problem actually is. Then you'll know what exactly you need help with.
spacemoose1 said:
If you haven't yet, get ADB set up on your PC. It will save you a lot of effort. There are plenty of guides on XDA that can help.
Once you do that, you should be able to copy files to your sdcard over ADB and use the ADB logcat command to see what the problem actually is. Then you'll know what exactly you need help with.
Click to expand...
Click to collapse
Yeah. I have ADB Shell on my PC.
I can reach my device only whenn I press "Volume Up + Power"... I can't see recovery on my tab but "adb devices" says:
List of devices attached
1000d300aab6 recovery
Click to expand...
Click to collapse
Logcat doesnt work.
Adb pull works
Adb push doesn't.
Hope you can give me more support.
thank you
you try any of these firmwares to bring it back yet?
http://www.thegalaxytabforum.com/index.php?/topic/112-samsung-galaxy-tab-firmware-list/
or go to this thread as well
http://forum.xda-developers.com/showthread.php?t=1002059
you can also try this att firmware
http://forum.xda-developers.com/archive/index.php/t-847609.html
Dont know much about other variants of tablets, but you can also try hemdall and this is the walkthrough for the Verizon Version, but DO NOT USE FILES ON THIS LINK!! I've restored my verizon tab 5 times using custom roms this way using hemdall.
http://forum.xda-developers.com/showthread.php?t=967175
vzt said:
you try any of these firmwares to bring it back yet?
http://www.thegalaxytabforum.com/index.php?/topic/112-samsung-galaxy-tab-firmware-list/
or go to this thread as well
http://forum.xda-developers.com/showthread.php?t=1002059
you can also try this att firmware
http://forum.xda-developers.com/archive/index.php/t-847609.html
Dont know much about other variants of tablets, but you can also try hemdall and this is the walkthrough for the Verizon Version, but DO NOT USE FILES ON THIS LINK!! I've restored my verizon tab 5 times using custom roms this way using hemdall.
http://forum.xda-developers.com/showthread.php?t=967175
Click to expand...
Click to collapse
Ok man... thank you very much for your suggestions.... but... why don't you just read what I said above?
I already tried to fix it, I did everything I was able to do.
I need some REAL HELP... someone who is going to tell me: "Oh! I know what your problem is, do this and this and you are going to fix your tab"!!
david_kurtovic said:
Ok man... thank you very much for your suggestions.... but... why don't you just read what I said above?
I already tried to fix it, I did everything I was able to do.
I need some REAL HELP... someone who is going to tell me: "Oh! I know what your problem is, do this and this and you are going to fix your tab"!!
Click to expand...
Click to collapse
Ok, we get it... You've stuffed your tab. It sucks to be you. My advice is if you want to fix it to take note of what people are actually saying to you.
Your description of the issue is pretty lame considering you Quote: 'did everything', so maybe your issue is beyond help!?
Anyhoo, here's my wild stab at what the issue is:
- your using an incorrect pit file, or possibly no pit file when flashing
- the rom your using is corrupt. Check the file size against the release notes.
Good luck.
Sent from my GT-P1000 using Tapatalk
krispyjim said:
Ok, we get it... You've stuffed your tab. It sucks to be you. My advice is if you want to fix it to take note of what people are actually saying to you.
Your description of the issue is pretty lame considering you Quote: 'did everything', so maybe your issue is beyond help!?
Anyhoo, here's my wild stab at what the issue is:
- your using an incorrect pit file, or possibly no pit file when flashing
- the rom your using is corrupt. Check the file size against the release notes.
Good luck.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
oh! yes I am actually listening what the people say
and whenn I say everything, I mean everything I could do...
I tried lots of different Stock and Custom roms.
I tried 4 different .PIT files ...
So look... you said something, but I already tried THIS TOO!
so again people...
IF YOU DON'T KNOW WHAT MY PROBLEM IS... DONT TELL ANYTHING...
the only one who said something good, was the guy with the logcat idea... but it doesn't work ;(
Cheers
You have a wrong pit file, you have screwed your own tab. I was listening and have provided you with possible information that can help. If you really tried everything, then don't be a douche, and don't bother posting. I would ask the moderators to close the thread.
Sent from my SCH-I500 using XDA App
david_kurtovic said:
IF YOU DON'T KNOW WHAT MY PROBLEM IS... DONT TELL ANYTHING...
the only one who said something good, was the guy with the logcat idea... but it doesn't work ;(
Cheers
Click to expand...
Click to collapse
i think you judge the people whom tried to help you. everybody from this forum faced with this problem, I guess... just because you made a mistake, is not our fault. I agree with what @vzt said.....
sorry, i am just confused... :S
Hmm.. wrong .PIT file... nope. because I tried to flash with all available .PIT files.
thank you
It has nothing to do with the .pit files you tried, did you use the right one with the right rom.
And 2, most people flashing the tab also use Hemdall. I you would actually read peoples posts, and take suggestions before knee-jerking and criticizing someone when they are pointing something out.
Nothing in your posts says that you use the specific .pit with the specific stock rom.
Also which version of odin are you using? 1.3 or 1.7? That makes a difference with specific euro firmwares as well......
but i guess if you wouldn't pull your head out of you know where and just listen to someone who is trying to help you, it wouldn't start a flame war on a site that is dedicated to helping people with device issues.
A) If it boots at all then it's NOT "bricked".
B) If you can't boot to DOWNLOAD mode (Power On+Down) then you've got problems, otherwise you can recover it.
- F.Reset Time
- PHONE EFS CLEAR!!!
- PHONE UPLOADER UPDATE!!!
Click to expand...
Click to collapse
You rarely need to use these options, don't unless told to.
If use use the "Add Hidden" PIT and Rotohammers complete JMI kernel, then you may be ok.
IF however you have flashed the version with the locked bootloader (ignoring the comment saying not to do so in that forum post), then you've got bigger problems. Did you check if this was the case first? If so then there's no point trying to repair it with non-official firmwares, you'll need to use an official one as base, then unlock the bootloader as per the howto elsewhere on this forum.
I already tried to fix it, I did everything I was able to do.
I need some REAL HELP... someone who is going to tell me: "Oh! I know what your problem is, do this and this and you are going to fix your tab"!!
Click to expand...
Click to collapse
If you're so confident that you've done "everything" - then don't be a **** when people try to help you, as if you had done so then one of the permutations would've been a solution, obviously that's not the case.
Thank you people for helping me.
Hmm... If I say that I have already tried to recover the Tab with many different Official ROMs ... and mostly with the p1 hidden. Pit ... did I do something wrong?
And yes, i think i was dumb enough do flash a locked bootloader :$ ^^
Thank you
Sent from my X10i using XDA App
david_kurtovic said:
Hi People
I Have a Problem, and the first thing I must say is: If you do not really know how do you can help me, please say nothing. Because, All that stuff you guys would tell me I ALREADY TRIED! So I need a Developer or someone who really knows what I am talking about.
Ok, as first: I am from austria, so I guess, I have the "EURO Tab"
My Problem Description:
I had a custom rom on my tab, it worked well.
then I saw a thread with the newest Official Firmware from samsung in this Thread:
http://forum.xda-developers.com/showthread.php?t=1004816
- I downloaded the file and extracted it..
- I took ODIN 1.7 and put the PDA, PHONE, CSC in their right places
(And here is the Clue!! >.<)
- I checked:
- Repartition- Auto Reboot- F.Reset Time- PHONE EFS CLEAR!!!- PHONE UPLOADER UPDATE!!!
- Then I clicked on START and it successfully finished....
BUT THEN
The TAB was rebooted, so far so good.. but it STUCKS at the FIRST "GalaxyTab" Logo.
I can reach the Download Mode again.
I CAN NOT!! reach the Recovery (Volume Up + Power Button)
Since then, I tried many different Kernels, Firmwares etc... but it is still the same!!
Maybe it happened, because i checked the Bootloader and EFS boxes...??
PLEASE, tell me what to do.
I have been trying for three Days to repair it, but I did not experienced any progress.
If you can help me, and you would need morde details, ask me, I am going to answere your questions.
Click to expand...
Click to collapse
You've flashed an "official" ROM over a custom ROM? Including the locked bootloaders? Seems like quite a bold thing to do (though I've done it myself)... Also ticking those buttons on Odin - clear EFS etc. Was that done for any particular reason?
As you've now got locked bootloaders you won't be able to flash any custom ROM, and you won't be able to unlock the bootloader until you've got a functioning tab again. So your only current option would seem to be to flash JMK or any other official ROM again. Either try again using Odin when device is in download mode, or unpack the files and use Heimdall.
I've actually installed this JMK rom/kernel over a custom ROM myself as I was curious to know what was in it, and the bootloader unlocker apk worked fine afterwards. One thing you don't have is a bricked Tab, so recovery is entirely possible, but you'll need to be more explicit in the steps you're taking, and also realise that (before you type another frustrated response) most people here would be happy to help you ....
@david_kurtovic
I come again to you and advice one more time to do EXACTELY what you see in my screeshoot, but first:
- make sure your TAB is in download mode (even it shows phone - ? - computer )
- have your TAB ChARGED
- and dont add anything except PIT, PDA, MODEM, and CSC
good luck!!! hope it help
(i have done by my self today just to make sure it will work....from custom rom - to stock, and reverse....)
Hi.. I'm a new member here, and have bricked my Samsung tab yesterday...
I get only screen having mobile connected to a PC "Mobile...!.... PC"
I have tried everything with Odin 1.7
All what I get is the as per the follows:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJJ4-REV03-ALL-CL639474.tar.md5 is valid.
<OSM> MODEM_P1000XXJID.tar.md5 is valid.
<OSM> GT-P1000-CSC-SERJJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Could anyone explain what is the real status of my tab?
Related
Hi there,
Today i decided to install android Froyo 2.2 to my galaxy s(dutch). I did this using samsung KIES, everything worked fine and i was told my phone would restart. It turned itself down but after the samsunglogo (the blinking one) the screen turned black while the bottom 2 buttens are lighted, it doesn't go passed this stage.. Also it vibrates ones in a while, sometimes 1 time, sometimes 3 short bursts of vibration. I still have the phone connected to my computer, what should i do? Jank battery out and pray for startup? Or are there any other suggestions?
Regards,
I had this problem.
If I remember correctly, I removed the battery and powered it on into Download Mode and reflashed it. But I didn't use Kies so it may be different.
Thnx, ill google around to see how to flash without keys, iam gonna jank it out
tried this guide:
http://forum.xda-developers.com/showthread.php?t=853950
But it sticks on SetupConnection and then sais he can't open the serial comport
ideas?
regards,
This is the Dev section, please move to Q and A.
tried again, went to firmware update start.. param.lfs then complete (write) operation failed... Iam getting a bit scared now!!
tokyogtr said:
This is the Dev section, please move to Q and A.
Click to expand...
Click to collapse
how do i do that?
wilfred0107 said:
how do i do that?
Click to expand...
Click to collapse
afaik this is for the mods
you could have done it the following way (as a reference for the future):
*) save the content of your post - delete the post
*) open a new post in the other section of the forum
use the search function and google
I'm sure there's at least one solution for you to get your phone running again
Hello, I'm Luis Henrique. I'm brazilian, so I bought the national version of Galaxy S, the GT I9000B. Yesterday (03/06/2011) I was testing some new Roms for my phone. I was using the Odin3 v1.7. I was going to put a 2.2 original Rom, but I accidentally left the box called "re-partition" checked and pressed start. All other boxes was correct. In the middle of the process i saw it, but I didn't stopped it because I got afraid that something worst could happen. I guess that option half-bricked my phone. I already wiped all data, wiped cache partition and tried to format the internal sd-card. I tried a thousand different ways of fixing it, but it all was useless. I'm not that smart with all this rom, flash, kernell, version stuff. But if you guys help me, I'm sure will try my best to fix the phone, because it's such a great phone...
I'm sorry for this new thread, but all the others didn't helped me at all.
Thanks in advance.
Luis Henrique
Darn... I've another rom and nothing happened...
I"m using odin3 1.83 now...
my story. I fixed it.
good luck
http://forum.xda-developers.com/showthread.php?t=982729
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) odin w/repartition.
should work let me know.
Thanks for the answer...
Is this hard to recover my phone?
http://forum.xda-developers.com/showthread.php?t=983785
check this out i just fixed it
Lyon huntington said:
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) odin w/repartition.
should work let me know.
Click to expand...
Click to collapse
I'm sure trying to find one, but it's hard as hell...
I've been looking at samfirmware and I didn't find nothing there...
danni_ind said:
http://forum.xda-developers.com/showthread.php?t=983785
check this out i just fixed it
Click to expand...
Click to collapse
Yeah, I'm trying HARD to find a 3 .tar stock rom to flash my phone again...
Thanks for the help!!
u need to download and flash dbdata.rfs.tar in odin by itself
here is the file
Chillax !!! ok dude listen to me here is the 3 tar file
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
Info Samsung Stock Rom :I9000XXJPC
Use 512.pit and 3-tar files from here and Re-partion in Odin and you're done
Believe me...
danni_ind said:
Chillax !!! ok dude listen to me here is the 3 tar file
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
Info Samsung Stock Rom :I9000XXJPC
Use 512.pit and 3-tar files from here and Re-partion in Odin and you're done
Believe me...
Click to expand...
Click to collapse
So, Danni_ind, I won't have problem since my phone is a GT-I9000B? I don't know if this Rom was made for him...
I9000B !...really sorry i dont know, but it works on my international model
XX = Europe (I am from india)
danni_ind: hey, I'm having the same problem and your solution didn't seem to work either. I tried both ways using the 512 pit file with odin 1.3 and the also the package you threw into the zip, 803 pit with odin 1.0.
had all 3 files with repartition clicked and still didn't work...
i guess there may be some compatibility issues with the phone if you use the european version of firmware , but the main problem will be solved(partition)... then after that you can use the 1 tar file to change it to I9000B version which you have ? give it a try....
are you sure you selected the right PDA MODEM AND CSC files in the right dialoug boxes ? because once i didn't select the files properly and it was showing the same...check it
danni_ind said:
i guess there may be some compatibility issues with the phone if you use the european version of firmware , but the main problem will be solved(partition)... then after that you can use the 1 tar file to change it to I9000B version which you have ? give it a try....
Click to expand...
Click to collapse
I'm sure will try, but now I'm downloading it...
2 mb internet from Brazil sucks...
Thanks, man.. Like we say here, you're bein a hand in the well...
uhuhraushrashsauh...
Really usefull tips...!!
actually i am mind fcked i am having problem with a vodoo kernel(supercurio)...it changes the filesystem during first boot and gets stuck at the home screen, god knows whats wrong
formatted my phone 11 times since i posted the 1st reply to you
god help me....arggg
Yeah, I'm sure. This didn't work at all for me.
jt_kyle said:
Yeah, I'm sure. This didn't work at all for me.
Click to expand...
Click to collapse
I'll have to try, this is my second day trying to solve this damn problem...
danni_ind said:
actually i am mind fcked i am having problem with a vodoo kernel(supercurio)...it changes the filesystem during first boot and gets stuck at the home screen, god knows whats wrong
formatted my phone 11 times since i posted the 1st reply to you
god help me....arggg
Click to expand...
Click to collapse
I'm not that smart or anything, but.. Why don't you try another kernell...?
There are other that can give you the same result, don't?
Hi All
Today I thought I would try to install Jellybean on My tab, I am a total nube at this but thought I could follow the tutorial. First I rooted my tab, then tried to backup the tab but it didn't work and then I thought what the hell I'll just try it.
Now it just shows the black and white Samsung Screen and won't turn off.
When I go in to the Android System recovery a message shows - /cant access to ‘system/csc/XEF/system/
I've tried using Odin and all seems good but I can't get ClockWorkMod to appear on my tab.
I bought my tab in the UK but it got shipped from France so has default language setup in French If that has anything to do with it.
Please help, I've tried following some threads on here but some of it seems to be out of my depth. Could someone explain in simple terms how I can get my tab back to normal?? It would be very much appreciated. I'm so annoyed at myself :crying:
Thanks in advance
Mike
Seems like you dont have root for some reason... there is a all in 1 guide in general section, u might wanna check that out... then install CWM and after that a new rom after installion clear dalvik and data.
JU57FL1P said:
Seems like you dont have root for some reason... there is a all in 1 guide in general section, u might wanna check that out... then install CWM and after that a new rom after installion clear dalvik and data.
Click to expand...
Click to collapse
Thanks for your reply, I've been looking at the All in 1 guide but it does confuse me a little, could you explain how I install these as I've been trying to fix this all day and haven't gotten anywhere.
Thanks
Help its getting worse!
I read that all for one help guide and decided to flash the pit file since nothing else was working, now my tab is stuck on the android downloading screen and wont go off it, I can't even get it to go in to recovery mode! Help!!!!!!!!!!!!! :crying:
Ummn u need to use odin to fully restore ur tab, wait for someone to provide u with the files... i dont have enough experience with odin...
JU57FL1P said:
Ummn u need to use odin to fully restore ur tab, wait for someone to provide u with the files... i dont have enough experience with odin...
Click to expand...
Click to collapse
Thanks, can someone please help me with these files please I'm desperate. :fingers-crossed:
Right, I've been looking at this for 2 days now.
I've noticed that their is a CSC file option on Odin, I'm also in the middle of downloading the stock rom P7310XWLA2 which is the French version of the ROM.
So when it has downloaded should I try to find a CSC file as well as the PDA file to send to my tab?
Please Help :fingers-crossed:
MikeMcGrathXmen said:
Right, I've been looking at this for 2 days now.
I've noticed that their is a CSC file option on Odin, I'm also in the middle of downloading the stock rom P7310XWLA2 which is the French version of the ROM.
So when it has downloaded should I try to find a CSC file as well as the PDA file to send to my tab?
Please Help :fingers-crossed:
Click to expand...
Click to collapse
ok I've loaded the stock rom P7310XWLA2 from odin there was no seperate csc file
But the tab started to load up 3 things came up with failing to mount data and cant mount your storage is not prepared yet on updating application, applting Multi CSC and installing multi CSC
The tab then rebooted and all looked well until the tab asked 'Entrer mot passe' which I think is enter you password i entered 'samfirmware.com' but it says desole - sorry
Any ideas please???
MikeMcGrathXmen said:
ok I've loaded the stock rom P7310XWLA2 from odin there was no seperate csc file
But the tab started to load up 3 things came up with failing to mount data and cant mount your storage is not prepared yet on updating application, applting Multi CSC and installing multi CSC
The tab then rebooted and all looked well until the tab asked 'Entrer mot passe' which I think is enter you password i entered 'samfirmware.com' but it says desole - sorry
Any ideas please???
Click to expand...
Click to collapse
Or should I just install the uk stock rom?
Im really going round in circles here and could really use some helpful advice, please :fingers-crossed:
Oh my god I've fixed it!
Finally got there in the end thanks to this tutorial phew :good:
MikeMcGrathXmen said:
Or should I just install the uk stock rom?
Im really going round in circles here and could really use some helpful advice, please :fingers-crossed:
Click to expand...
Click to collapse
Luckily I've never had to use ODIN with my Tab, however back in the days on my SGS I used it a lot.
So just a few things: you don't have a CSC file, because your tab is a Wifi only model, so don't worry about that.
Also, be sure to tick the re-partition box on the left if you are using a pit file (which at this state you should), this should repartition your internal SD and thus have a clean install.
Good luck
Thanks, but i've got it working and I'm not gonna mess round with it again.
Can't believe i finally got it working!
After trying to rooting my Note3 with kingo app i trying to used chain fire<s unregion lock so i can use any sim and it just wouldnt work. later on i tried to unroot using kingo app and that would not work either. I then downloaded all the rooting software and data to manually root it using N900AUCUBMI9_OneClickBin, it would keep giving me <ID:0/024> 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/024> Odin v.3 engine (ID:24)..
<ID:0/024> One Click Downloader Mode
<ID:0/024> File analysis..
<ID:0/024> SetupConnection..
<ID:0/024> Initialzation..
<ID:0/024> Set PIT file..
<ID:0/024> DO NOT TURN OFF TARGET!!
<ID:0/024> Get PIT for mapping..
<ID:0/024> Firmware update start..
<ID:0/024> SingleDownload.
<ID:0/024> sbl1.mbn
<ID:0/024> NAND Write Start!!
<ID:0/024>
<ID:0/024>
<ID:0/024>
<OSM> All threads completed. (succeed 0 / failed 1)
and the phone would say SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1
then i tried odin3 thinking that would fix the problem and it Softbricked my Note3
i tried to use N900AUCUBMI9_OneClickBin to fix it but it keeps giving me the same Error What can i do? Pls Help
Abduizzle said:
After trying to rooting my Note3 with kingo app i trying to used chain fire<s unregion lock so i can use any sim and it just wouldnt work. later on i tried to unroot using kingo app and that would not work either. I then downloaded all the rooting software and data to manually root it using N900AUCUBMI9_OneClickBin, it would keep giving me <ID:0/024> 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/024> Odin v.3 engine (ID:24)..
<ID:0/024> One Click Downloader Mode
<ID:0/024> File analysis..
<ID:0/024> SetupConnection..
<ID:0/024> Initialzation..
<ID:0/024> Set PIT file..
<ID:0/024> DO NOT TURN OFF TARGET!!
<ID:0/024> Get PIT for mapping..
<ID:0/024> Firmware update start..
<ID:0/024> SingleDownload.
<ID:0/024> sbl1.mbn
<ID:0/024> NAND Write Start!!
<ID:0/024>
<ID:0/024>
<ID:0/024>
<OSM> All threads completed. (succeed 0 / failed 1)
and the phone would say SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1
then i tried odin3 thinking that would fix the problem and it Softbricked my Note3
i tried to use N900AUCUBMI9_OneClickBin to fix it but it keeps giving me the same Error What can i do? Pls Help
Click to expand...
Click to collapse
Simply Put.......FOR NOW YOU ARE SCEWED!!!
this kind of thing happened to me, you are getting the Pen Detect has stopped error right. once you start using Odin to go back to stock from MJ5 you get a loop, then if you flash the right files you can get it to boot, but always give that error every 10 sec. i have not seen a solution to this yet. i had to get my exchanged at best buy ( it was a very painful process on my end ) they had a lot of questions.
but yea, i dont think you will be using your phone anytime soon bruh. sucks but thats what alot of users are going through with the note 3 on ATT.
the2rrell said:
.........but yea, i dont think you will be using your phone anytime soon bruh. sucks but thats what alot of users are going through with the note 3 on ATT.
Click to expand...
Click to collapse
That's because alot of users are rooting without reading the instructions or threads first. It has been written very clearly all over the att N3 forum that you cannot go backwards from MJ5. Those that choose to do it their way without researching first are now the proud owners of $800 bricks. PERIOD.
I'm sorry for your loss. kraz
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
krazman325 said:
That's because alot of users are rooting without reading the instructions or threads first. It has been written very clearly all over the att N3 forum that you cannot go backwards from MJ5. Those that choose to do it their way without researching first are now the proud owners of $800 bricks. PERIOD.
I'm sorry for your loss. kraz
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its not always about lack of reading, i read it all and just simply fudged my phone up on my own accord by trying to swap a system file. This is what bricked my phone. and others as well, but yes most are the ones that were trying to downgrade from mj5 to m19 for whatever reason and they get the brick as well.
so weather its Not Reading or Just a F up there is still no coming back from it yet.
Agreed +1
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Does downgrading void your Sammy/AT&T warranty? I know that rooting will void warranty, but downgrading technically has nothing to do with being rooted (until you actually perform the root). So if you bricked your phone b/c of downgrading, shouldn't you still be able to make a claim (hypothetically)?
BlackZenith said:
Does downgrading void your Sammy/AT&T warranty? I know that rooting will void warranty, but downgrading technically has nothing to do with being rooted (until you actually perform the root). So if you bricked your phone b/c of downgrading, shouldn't you still be able to make a claim (hypothetically)?
Click to expand...
Click to collapse
Yes but downgrading does not really down grade your phone, you will have a MJ5 M19 mash up IF it boots. which if they happen to look at will mean you were flashing things to your phone because there are no ODIN packages soooo HOW did you do that, know what i mean. i took the advice of another member, i downgraded to get rid of the CUSTOM Lock (Root) boot. then odind back to M19 again and pulled the update at 40 percent leaving my phone in the Firmware encountered a problem and needs to plugged up to recovery screen. so they could not look at anything on the phone. But if your going through att mail in replacement all of that may not even matter. I had to do that because i was walking into a best buy and knew they would check whatever they could to prove i rooted and messed it up. They could not prove it so i got a new phone.
the2rrell said:
Yes but downgrading does not really down grade your phone, you will have a MJ5 M19 mash up IF it boots. which if they happen to look at will mean you were flashing things to your phone because there are no ODIN packages soooo HOW did you do that, know what i mean. i took the advice of another member, i downgraded to get rid of the CUSTOM Lock (Root) boot. then odind back to M19 again and pulled the update at 40 percent leaving my phone in the Firmware encountered a problem and needs to plugged up to recovery screen. so they could not look at anything on the phone. But if your going through att mail in replacement all of that may not even matter. I had to do that because i was walking into a best buy and knew they would check whatever they could to prove i rooted and messed it up. They could not prove it so i got a new phone.
Click to expand...
Click to collapse
Had same problem. Half m19 half mj5. .. just told At&t that "something happened during the OTA ..." and played dumb. Got a warranty exchange.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I have been looking around and i found this do you think this will work?
http://forum.xda-developers.com/showthread.php?t=2476353
Abduizzle said:
I have been looking around and i found this do you think this will work?
http://forum.xda-developers.com/showthread.php?t=2476353
Click to expand...
Click to collapse
You I saw that too, it looks like it may work. But as I am not brocked any more due to me exchanging it before I tried it out. If your bricked what do you have to lose. .....I would try it if your not looking to get it replaced.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Abduizzle said:
I have been looking around and i found this do you think this will work?
http://forum.xda-developers.com/showthread.php?t=2476353
Click to expand...
Click to collapse
Step 14 is problematic for us right now b/c a complete Odin package for MJ5 does not exist.
that is exactly where i am having problems
this is what happens
first i boot up my phone and it says
firmware upgrade encountered issue. please select recovery mode in kies & try agian. I tryed kies and it didnt work.
then i got N900AUCUBMI9_OneClickBin and tryed to run it but it would fail and my phone would give me the message Fused 2 > Binary 1
i still dont understand why other people with ATT note3 could do it and i couldnt....... and is the a fix coming?
the2rrell said:
Yes but downgrading does not really down grade your phone, you will have a MJ5 M19 mash up IF it boots. which if they happen to look at will mean you were flashing things to your phone because there are no ODIN packages soooo HOW did you do that, know what i mean. i took the advice of another member, i downgraded to get rid of the CUSTOM Lock (Root) boot. then odind back to M19 again and pulled the update at 40 percent leaving my phone in the Firmware encountered a problem and needs to plugged up to recovery screen. so they could not look at anything on the phone. But if your going through att mail in replacement all of that may not even matter. I had to do that because i was walking into a best buy and knew they would check whatever they could to prove i rooted and messed it up. They could not prove it so i got a new phone.
Click to expand...
Click to collapse
I'm in same boat after rooting for YEARS...UGH
NOW, My Current Binary and Sammy Warranty are both still at "official" and KNOX Kernal Lock is 0X0 as well as Knox Warranty Void (Both at 0X0)
Also, when Note 3N900A Boots normally before it locks up or (doesn't continue) there is no "unlock or lock icon at all, Just Galaxy Note 3 where right after the AT&T would appear so I'm thinking I'm fine to play dumb "Failed OTA update" and simply go in and exchange it...
Is there another way AT&T could tell its been tampered with if those both say official? If not I'm taking in for warranty and claiming OTA update.
please advise
Thx
Fas
---------- Post added at 12:46 AM ---------- Previous post was at 12:42 AM ----------
Abduizzle said:
first i boot up my phone and it says
firmware upgrade encountered issue. please select recovery mode in kies & try agian. I tryed kies and it didnt work.
then i got N900AUCUBMI9_OneClickBin and tryed to run it but it would fail and my phone would give me the message Fused 2 > Binary 1
i still dont understand why other people with ATT note3 could do it and i couldnt....... and is the a fix coming?
Click to expand...
Click to collapse
I'm in same boat after rooting for YEARS...UGH
NOW, My Current Binary and Sammy Warranty are both still at "official" and KNOX Kernal Lock is 0X0 as well as Knox Warranty Void (Both at 0X0)
Also, when Note 3N900A Boots normally before it locks up or (doesn't continue) there is no "unlock or lock icon at all, Just Galaxy Note 3 where right after the AT&T would appear so I'm thinking I'm fine to play dumb "Failed OTA update" and simply go in and exchange it...
Is there another way AT&T could tell its been tampered with if those both say official? If not I'm taking in for warranty and claiming OTA update.
please advise
Thx
Fas
---------- Post added at 12:46 AM ---------- Previous post was at 12:46 AM ----------
BlackZenith said:
Step 14 is problematic for us right now b/c a complete Odin package for MJ5 does not exist.
Click to expand...
Click to collapse
I'm in same boat after rooting for YEARS...UGH
NOW, My Current Binary and Sammy Warranty are both still at "official" and KNOX Kernal Lock is 0X0 as well as Knox Warranty Void (Both at 0X0)
Also, when Note 3N900A Boots normally before it locks up or (doesn't continue) there is no "unlock or lock icon at all, Just Galaxy Note 3 where right after the AT&T would appear so I'm thinking I'm fine to play dumb "Failed OTA update" and simply go in and exchange it...
Is there another way AT&T could tell its been tampered with if those both say official? If not I'm taking in for warranty and claiming OTA update.
please advise
Thx
Fas
the2rrell said:
Simply Put.......FOR NOW YOU ARE SCEWED!!!
this kind of thing happened to me, you are getting the Pen Detect has stopped error right. once you start using Odin to go back to stock from MJ5 you get a loop, then if you flash the right files you can get it to boot, but always give that error every 10 sec. i have not seen a solution to this yet. i had to get my exchanged at best buy ( it was a very painful process on my end ) they had a lot of questions.
but yea, i dont think you will be using your phone anytime soon bruh. sucks but thats what alot of users are going through with the note 3 on ATT.
Click to expand...
Click to collapse
This is exactly the problem I am having and I've tried everything.
Seriously, no solution?
Patience my friend multifentre will soon !
mgdes said:
Patience my friend multifentre will soon !
Click to expand...
Click to collapse
What does multifentre mean?
Odin fail
I'm in the same boat. My issue is that my internet was messed up and corrupted files that I downloaded. So when I went to root the phone it failed and got me stuck on the firmware screen instead of booting up. Found the files to flash using odin and heimdall. Got the phone to boot up just fine but then kept getting a message that "unfortunately SNS has stopped". I just forced it to stop running and things are fine but now I cannot get back to stock (odin keeps failing) and I can also download the patch of 4.3 (47mb) but when the phone boots into recovery to install it fails on the installation. Has anyone heard of this going on and is there a way to fix it at all or do we have to wait and does this sound like a mash/mix of MI9 and MJ5?
Direct pen input has stopped working
I hate this error message i really dont want to send it in to samsung because i will not have a phone for a while. Anybody have any luck with fixing it?
setfly95 said:
I hate this error message i really dont want to send it in to samsung because i will not have a phone for a while. Anybody have any luck with fixing it?
Click to expand...
Click to collapse
There is thread in the GENERAL section called MJ5 Restore that will get your phone back to stock MJ5 rooted or not its up to you. but it works i have used it twice and it gets everything back to mj5 no mash up no errors just a normal out of the box phone again.
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try aga
My watch is stuck on a screen saying
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can't get it to connect to Odin, adb, anything...
Can't get it into recovery or download mode.
If I hold the power button, it just flashes off quickly, then straight back into that screen.
Any ideas??
I understand you're in a panic because your device is having issues. But please read the forum rules and search for your issue before posting the same question in multiple threads like you just did. By you posting the same question over and over searching becomes difficult and people are less likely to help. Please try searching again. If you can't find a resolution post exactly what you did, and what files you were trying to load.
I haven't had any further progress.
When I try to flash with Odin, it gets stuck at SetupConnection..
lokidokie said:
I haven't had any further progress.
When I try to flash with Odin, it gets stuck at SetupConnection..
Click to expand...
Click to collapse
Did you find out how to go on download or recovery mode?
americo85 said:
Did you find out how to go on download or recovery mode?
Click to expand...
Click to collapse
No, but the device does "show up" in Odin. But again, doesn't get past Setup Connection when I try to flash something.
Ok... Fixed my issue.
Just had to flash the MK7 firmware. That was the ONLY one that works.
Thanks all!
lokidokie said:
Ok... Fixed my issue.
Just had to flash the MK7 firmware. That was the ONLY one that works.
Thanks all!
Click to expand...
Click to collapse
Could you please tell us how you fixed your issue?
americo85 said:
Could you please tell us how you fixed your issue?
Click to expand...
Click to collapse
If you would please read. The answer is in the post above yours!!!!!!!!!!!
You even quoted the answer!!!
americo85 said:
Could you please tell us how you fixed your issue?
Click to expand...
Click to collapse
Yeah mate,
You just have to download a stock MK7 firmware from sammobile. I don't think it matters which region, I used Australia (because that's where I am).
Then connect up the watch, right click on Odin 3.09 to "open as administrator", make sure the watch shows up in a "COM" port, load the MD5 into AP, then start.
Not sure how much more detail I can give.
Good luck guy!
lokidokie said:
Yeah mate,
You just have to download a stock MK7 firmware from sammobile. I don't think it matters which region, I used Australia (because that's where I am).
Then connect up the watch, right click on Odin 3.09 to "open as administrator", make sure the watch shows up in a "COM" port, load the MD5 into AP, then start.
Not sure how much more detail I can give.
Good luck guy!
Click to expand...
Click to collapse
That's exactly what I did but for some reason mine is not working
I got the same issue. When i do it, im still stock at "SetupConnection.."
By the way, im from Denmark, so which region do i have to choose? Cause, denmark is not on the list.
And, what were you flashing at first when you bricked your Gear ?
A friend of mine went through the same problems 2 days ago, he tried to flash directly Tizen 2.2.1.1 over Null_rom (Android), and it went bad like your Gear.
I found out he needed to first flash Tizen 2.2.0, the very first Tizen version that came out.
This version weights 200MB+ than the latest.
I guess it's all the Android -> Tizen conversion software and tools that are embedded, and if flashing a newer Tizen version directly, it fails because of this 200MB+ stuff lacking in the rom.
Is it what you did too ?
I don't know if this is documented somewhere down here, didn't searched before reply.
edit: user nunyabiziz too had sorted it out : http://forum.xda-developers.com/showpost.php?p=53872341&postcount=3
chleb said:
And, what were you flashing at first when you bricked your Gear ?
A friend of mine went through the same problems 2 days ago, he tried to flash directly Tizen 2.2.1.1 over Null_rom (Android), and it went bad like your Gear.
I found out he needed to first flash Tizen 2.2.0, the very first Tizen version that came out.
This version weights 200MB+ than the latest.
I guess it's all the Android -> Tizen conversion software and tools that are embedded, and if flashing a newer Tizen version directly, it fails because of this 200MB+ stuff lacking in the rom.
Is it what you did too ?
I don't know if this is documented somewhere down here, didn't searched before reply.
edit: user nunyabiziz too had sorted it out : http://forum.xda-developers.com/showpost.php?p=53872341&postcount=3
Click to expand...
Click to collapse
That is exactly what i did
But i've tried with Tizen 2.2.0 too. Does the same thing.
I had this prob went from android to tizen by mistake. Had to find firmware an install it again. Back running though
Sent from my Nexus 5 using Tapatalk