Related
Ok here goes... This is my first thread post here but I am in serious need of help.
I have searched and searched the forums for a hopeful answer but I have found it difficult to find the answer I seek.
So here is the story:
Bought a GT second hand from Akihabara in Japan which was locked to NTT DoCoMo. I was using it as a WIFI only Tab and all was wonderful till my IT brain decided it could be better and I began to tinker.
I had been looking around for a way to make my Australian Virgin Mobile SIM to work on the tab and found a lot of good answers but nothing that would make it work.
I then had the brilliant idea to change the firmware with a European firmware so I could get all the features enabled from a fresh start. Which is where it all went wrong.
I first tried to flash the tab using Odin 1.7 with the P1000XXJK5 euro firmware from samfirmware.com
This failed and left my tab with the picture of a phone and a pc with a dotted line and in between them an exclamation point in a triangle.
After a lot of fiddling (I dont remember what I did but I managed to get rid of that screen had something to do with retrying the flash and it was very late last night at this point) I managed to try again but Odin just kept failing on running the updated firmware.
I then decided that it would be a good idea to run the Rotohammer firmware by following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=895827&highlight=sc-01c
This is where I once again received errors from Odin and now my tab is somewhat bricked.
I tried reflashing but same errors every time. (I currently dont have the errors from Odin but I will update my post when I get home)
I can still get to the downloading screen (Yellow triangle with the Android digging) so I am hopeful all is not lost.
So now you have heard my sob story I will ask two questions....
1. Has anyone actually successfully flashed a Japanese model Tab?
2. My only thought/hope at the moment can anyone direct me to an original NTT DoCoMo firmware so I can at least go back to having WIFI only Tab?
Thanks in advance if you can help
Alex
Yes , i suggest you to wait until you get a right firmware for it !
That would probably work if the partitions are a match !
What is this model called btw ?
"NTT DoCoMo Japanese Tab" or there is any model ? such as M180 for korean , P1000 , P100 Sprint , I800 Verizon , etc..
Br
Oz
I am searching the an original NTT DoCoMo firmware.
Electroboy said:
Yes , i suggest you to wait until you get a right firmware for it !
That would probably work if the partitions are a match !
What is this model called btw ?
"NTT DoCoMo Japanese Tab" or there is any model ? such as M180 for korean , P1000 , P100 Sprint , I800 Verizon , etc..
Br
Oz
Click to expand...
Click to collapse
Oz the model is SC-01C it has a build date of 2010/12
I was thinking considering I can get into the build/download screen maybe trying an emergency firmware recovery using Kies.
Hi,
I'm a fellow SC01 owner. You can get a backup of the stock firmware here: http://www.megaupload.com/?d=OJAK2UZF
Firmware code is SC01COMJK2
I believe there are newer firmwares (which I haven't installed as some of them contain a new bootloader that only allows for signed firmwares, same as the international units) that I have seen mentioned on various Japanese blogs. Let me know if you want me to try to hunt any down for you.
As for my SC01, I installed the custom kernel by koxudaxi and it's working great. Mind you, I've only changed to this kernel and apart from that am running the stock OS. I got his kernel here which can overclock to 1.4GHz: http://koxudaxi.sakura.ne.jp/
The kernel I installed via Heindall is zImage_ntt_2. It looks like he's built a newer version though, I might check that out. I think what you might want to do, is in download mode try to restore the above backup to your unit. Look up the Roto Backup thread to see how to do this. Hopefully since you can get download mode, all is not lost. I personally think it's quite crummy that there are different hardware versions like this which aren't interchangeable though >_<
I'm going to give the original firmware a go today at lunch time and I will let you know how I go. Thanks anyways for the link if all goes well I'll look at possibly trying the the koxudaxi kernel.
UPDATE: Well I'm not having luck getting the firmware to flash to my tab I keep getting "Failed to retrieve config Descriptor" when trying to flash. I will keep plugging away.
UPDATE: Still getting the same problems using heimdall to flash the tab. Any suggestions as to what I could do next?
Recovering a Docomo Tab
I'm currently running Overcome v1.1.3 ROM and richardtrip's V15 kernel on my SC-01C.
acont said:
UPDATE: Well I'm not having luck getting the firmware to flash to my tab I keep getting "Failed to retrieve config Descriptor" when trying to flash. I will keep plugging away.
Click to expand...
Click to collapse
You're getting this error from Heimdall, right? Have you tried Odin 1.7?
Here's how I recovered my Tab using Odin:
1. Following the instructions in http://forum.xda-developers.com/showthread.php?t=895827, specify the P1_add_hidden.pit in the PIT button and select Re-Partition.
2. Specify the stock Docomo ROM when pressing the PDA button.
3. Ignore the Phone and CSC buttons, as the stock ROM already contain these items.
You should be able to restore your Tab to stock settings using this procedure.
If this doesn't work, you might want to check if the USB connection to your PC is ok, and if everything necessary to run Odin is installed on your PC.
Bugger!
Well thanks for your help all of you but I think I have just made matters worse.
Last night I had success in flashing the original docomo firmware provided to me by zetsurin but I think I shouldn't have included the boot images.
Unfortunately I think it is completely bricked now it now wont turn on and when plugged into power (thinking that the battery had died) it just comes up with a white screen.
I can't boot into download mode and I can hold down the power button till I turn blue in the face... So as Bones would say "It's dead Jim"
Unless any of you have anything else I could try as a last ditch shot I might just have to ship it back to Japan and get them to fix it or maybe try Samsung here in Oz.
Serves me right
Thanks again.
acont said:
Last night I had success in flashing the original docomo firmware provided to me by zetsurin but I think I shouldn't have included the boot images.
Click to expand...
Click to collapse
What exactly happened?
The SC01COMJK2 firmware does not contain protected bootloaders, by the way.
acont said:
Unfortunately I think it is completely bricked now it now wont turn on and when plugged into power (thinking that the battery had died) it just comes up with a white screen.
Click to expand...
Click to collapse
I've heard about this happening when the battery runs out. Try connecting the Tab to your PC (not your AC adapter) and let it trickle-charge for an hour or so. If successful, you should see the download screen.
fury1sog unfortunately that didnt work
spoke to the samsung repairers here in Aus and they said they can take a look at it for me hopefully bring life back into my unit and then I will never touch it again
Any thoughts?
Hopefully this post is still being looked at but has anyone got any ideas as to what I could do before I fork out $374 to my tab repaired by Samsung Australia?
According to the repair guys its a faulty board (not an idiot that tried to flash it) and needs to be replaced. Not sure if this is worth my trouble considering I could buy a brand new tab for $599.
There is a positive out of this, the MB will be an Australian MB and I will have a working "Australian" tab instead of the Japanese version.
Considering the unfortunate tragedy in Japan I am not sure I should try and get my friend in Japan to fix it for me.
Thoughts anyone?
I know someone who can unlock it, I have mine unlocked by them.
I was afraid of flashing it myself so I paid to have it unlocked, cost was $20.
I think you better go for the MB replacement, it's cheaper.
For what it's worth, I went to reset my tab to factory using a rotohammer backup I made when I first bought it, and got stuck in a boot loop. So I then used ODIN. Still got a boot loop. Then I tried ODIN repartition... it hung for hours. Knowing the thing was likely bricked I pulled the plug and now I am in the situation as you: I have a crappy icon of a phone + an exclamation + computer image. Dead.
I think the best thing I can do for this junk is to toss it unceremoniously in the bin. Fortunately I also have an iPad which has resumed full-time service.
EDIT: Some signs of hope in here: http://forum.xda-developers.com/showthread.php?t=903257
Try "heimdall close-pc-screen" to see if your tab can get kicked back into the boot loop at least. Mine has failed a repartition, but I can still get it into the boot loop, which is a start. Will experiment over the weekend.
EDIT 2: Well my tab is back up and runing. I reflashed my original roto backup using ODIN with repartition on, then I went into recovery and did a factory restore. Back up like stock now. I think I'm going to sell it though, since it's been badly dis-owned by Samsung.
zetsurin said:
Hi,
I'm a fellow SC01 owner. You can get a backup of the stock firmware here: http://www.megaupload.com/?d=OJAK2UZF
Firmware code is SC01COMJK2
I believe there are newer firmwares (which I haven't installed as some of them contain a new bootloader that only allows for signed firmwares, same as the international units) that I have seen mentioned on various Japanese blogs. Let me know if you want me to try to hunt any down for you.
As for my SC01, I installed the custom kernel by koxudaxi and it's working great. Mind you, I've only changed to this kernel and apart from that am running the stock OS. I got his kernel here which can overclock to 1.4GHz: http://koxudaxi.sakura.ne.jp/
The kernel I installed via Heindall is zImage_ntt_2. It looks like he's built a newer version though, I might check that out. I think what you might want to do, is in download mode try to restore the above backup to your unit. Look up the Roto Backup thread to see how to do this. Hopefully since you can get download mode, all is not lost. I personally think it's quite crummy that there are different hardware versions like this which aren't interchangeable though >_<
Click to expand...
Click to collapse
hi zetsurin!
thanks for teaching me how to unlock the tab.
problem now is, im not able to successfully flash any rom. keeps saying write fail, using odin.
stuck at docomo logo when rebooted.
need help.
also used heimdall. starts downloading. but stuck almost at the end of the tab's progress bar.
argh...
me too ! samsung galaxy tab m180 Korean .... huhu
What ROM is best for a SC-01C?
Hi Guys
I picked up a 2nd hand SC-01C from Yahoo Auction, and am wondering what the best ROM to use with it is...
Looks like this guy has got an Overcome ROM on it OK, (http://chaki-ramone.blogspot.com/2011/06/galaxytabsc-01cgingerbreadromovercome.html), so I wonder if the latest version (http://forum.xda-developers.com/showthread.php?t=1205990) will work OK - anyone tried? (is the SC-01C a GSM-based model??)
I'm not going to use a SIM with it, so I'm not bothered about unlocking - but just want it rooted & want a good balance between speed & battery life. If you were going from scratch with an SC-01C, what would you do? Any suggestions greatfully received!
Thanks in advance?
PS - I'm an iPhone / iPad / Ideos 8150 / Notion Ink Adam owner, all jailbroken / rooted. So I'm not scared about rooting per-se, just worried about trying something that will not work because of anything docomo has done to the Tab!
Acont you could be coma bricked try pluginging it into THE MAINS for at least 4 hours if nothing come up your hard bricked.
Sent from my GT-P1000 using XDA Premium App
zetsurin said:
For what it's worth, I went to reset my tab to factory using a rotohammer backup I made when I first bought it, and got stuck in a boot loop. So I then used ODIN. Still got a boot loop. Then I tried ODIN repartition... it hung for hours. Knowing the thing was likely bricked I pulled the plug and now I am in the situation as you: I have a crappy icon of a phone + an exclamation + computer image. Dead.
I think the best thing I can do for this junk is to toss it unceremoniously in the bin. Fortunately I also have an iPad which has resumed full-time service.
EDIT: Some signs of hope in here: http://forum.xda-developers.com/showthread.php?t=903257
Try "heimdall close-pc-screen" to see if your tab can get kicked back into the boot loop at least. Mine has failed a repartition, but I can still get it into the boot loop, which is a start. Will experiment over the weekend.
EDIT 2: Well my tab is back up and runing. I reflashed my original roto backup using ODIN with repartition on, then I went into recovery and did a factory restore. Back up like stock now. I think I'm going to sell it though, since it's been badly dis-owned by Samsung.
Click to expand...
Click to collapse
Can anyone pls help,, my galaxy tab 7inch gt-p1000r is stuck on phone+pc logo, can't go to download mode, can't go to recovery mode,, can't do anything,, pls someone help me,, I am desperate..
huylang280285 said:
me too ! samsung galaxy tab m180 Korean .... huhu
Click to expand...
Click to collapse
unbricking M180 is done long time ago
Here is a video for you
http://www.ort-jtag.com/blog/?e=15
udhtari said:
Can anyone pls help,, my galaxy tab 7inch gt-p1000r is stuck on phone+pc logo, can't go to download mode, can't go to recovery mode,, can't do anything,, pls someone help me,, I am desperate..
Click to expand...
Click to collapse
What about this P1000R , what is special or different ?
I know P1000L was for south american edition !
lemmy_0 said:
hi zetsurin!
thanks for teaching me how to unlock the tab.
problem now is, im not able to successfully flash any rom. keeps saying write fail, using odin.
stuck at docomo logo when rebooted.
need help.
Click to expand...
Click to collapse
Docomo solution is very soon !
That TAB need JTAGging thats the only way ..
I have the good and dead device in hand , we will release for ORT-JTAG probably this week ..
Best Regards
Oz.
I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
everett1911 said:
I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
Click to expand...
Click to collapse
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
prbassplayer said:
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
Click to expand...
Click to collapse
last time I had bothered to update cyanogen, it was a week ago. I don't remember the exact nightly build. The other roms I tried were miui, apex and something else that wouldn't boot and which I deleted quickly (apex wouldn't boot either but I spent a couple hours trying to make it work). I wiped everything prior to flashing.
as for the stock rom, it's a stock rom for the SGH-I896 (I896UXJI2), my phone model. before, the stock rom worked fine. I just can't figure out why it's suddenly not working now.
anyone? I really want to put the stock rom back into my phone.
Are you using a PIT file when flashing? If not try using this one with that package then report back.
I've already did that with odin.
and just out of curiousity, what are pit files for?
everett1911 said:
I've already did that with odin.
and just out of curiousity, what are pit files for?
Click to expand...
Click to collapse
I dont know what it exacly does BUT I know if you want to repartition your phone and you are on a AOSP like CM7 or MIUI you need a pit.
P.i.t.
Partitioning
Information
Table
Lol makes sense now
Sent from my SAMSUNG-SGH-I897 using xda premium
studacris said:
P.i.t.
Partitioning
Information
Table
Click to expand...
Click to collapse
*windows user* so it's a bit like a batch fdisk?
if so, is the internal sd card itself supposed to be wiped clean? because it didn't happen when I used mine.
Ok so using the PIT file didn't work for you. I've seen several Samsung devices suffer from a problematic internal OneNAND in the past but never one a Captivate. It's always been a TAB, i9000 or Vibrant. Can you try flashing the base files used in the Serendipity ROM? It's the stock Gingerbread installed before flashing the Serendipity ROM itself. You can find them in that thread. It will help distinguish whether you have an actual issue or whether you just need some in depth CSC scripts to help clean it up. In general that ROM has a very nicely built CSC cleanup script that is able to correct what I call "partition bricking" on the Captivate, i9000 and Vibrant. Give it a shot and report back...
Also, if that won't work, I have been able to correct this via JTAG. PM me if it comes to that. If JTAG won't correct it, then it is indeed a case of a partially dead OneNAND. It's rare but does happen.
I'll give that CSC script thing a try. What's JTAG, by the way?
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
anyone, please?
everett1911 said:
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
Click to expand...
Click to collapse
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
For2ndtwin said:
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
Click to expand...
Click to collapse
thanks but I think it's too late. while trying to flash serendipity two days ago, I used the odin flasher that site linked to, and it flashed my phone with at&t's firmware, which somehow completely ruined my phone. now, the phone won't boot, and I can't enter download mode at all. I'm not sure even a usb jig would help, and right now I don't have money for that, so I'll have to wait till I do.
And if this doesn't work, then what? All the phone does is show a spinning little circle, immobile for 3 seconds, and the phone turns off. when I insert the battery (after pulling it out), the phone automatically starts with the same screen, same result. if I plug in the usb cable, it shows the charging battery indicator, freezes, and reboots. This repeats over and over, with no end at all, and since I can't enter download mode in any way so far, I can't do anything about that. It's so bad that not even windows detect my phone, and I've plugged it into two separate computers, so I know it's not just my pc pulling a trick on me.
The worst part is that since I was using wifi tether on my phone (hello, pdanet), now I'm without any internet (right now I'm typing this on my little sister's laptop, from my dad's place.)
So... yeah.
By the way, the heimdall link is for i897 phones, even in the post for i896 phones. Is there any risks my phone will react as badly as it did with the at&t firmware?
^ I've read good things about Heimdall. Btw, if ur phone has any signs of life, then a Jig should get u back into download mode.
The fact that it was at&t firmware has nothing to do with it. Running I897 firmware on an I896 is fine. **** you can run I9000 firmware...
so many days after, I still can't get it into download mode at all. all it shows is a spinning circle, a spinning circle and then the charging battery image for a second when the usb cable is plugged in, and the AT&T world logo when the battery is low.
I could go for a solderless usb jig but even then I don't have cash for that right now (next week.), so until then I'm screwed.
I tried everything minus the usb jig, looked for many threads on the topic, and nothing works. nothing.
no matter how many times I do the battery trick or the three finger salute or the odin stuff, and it still doesn't work.
so... yeah. that usb jig better damn work.
I'll call it magic
First, I'd like to thank 4-2ndtwin for providing a complete stock rogers rom.
Second: how does a usb jig work, really? my thing's computers, software and hardware in general but not to the point of knowing how capacitors, resistors and all that stuff works, so for me the usb jig bringing back my phone from firmware limbo... that's magic. seriously.
Ok I have a stock KB2 Cappy. I used Odin to flash back to 2.1 KB1 JF6
Then I used Odin 3 to flash a kernel so I can put on CM7. I am now stuck in the Boot screen.
I have no 3 button, I cannot get into download mode (my jig is homemade should i order one?)
I tried to change usb and remove the sim card to try odin again to get back into stock.
Nothing seems to work the only thing is my jig is not good either for DL Mode. I want to get back to stock so any suggestions. I tried heimandall did not work either.
I am really stuck on this galaxy s I897 screen.
Is the jig soldered? If its not make sure you are connecting the correct pins and use some black tape or something to isolate your fingers from the resistors (might screw up the actual ohms making it to boot up normally and not in to dl mode.
The bootloop was expected, you are supposed to check that you have a working button combo both before you flash the kernel (because it will bootloop and you boot into recovery and flash whatever) and before you ever flash cm7 because that is the only way to get into download mode besides a jig on aosp roms.
so, fiddle around with your jig some more and if you get it in download mode just flash the captivate gingerbread bootloaders, that will fix your button combo and allow you to proceed flashing cm7.
Hi Guys,
I have a similar problem. I am a total noob-I've had my I896 cappy (Canadian Rogers based) for about a year now; i fiddled with it on Saturday and also got the bootloop. I freaked out, and managed to further flash (out of frustration and confusion) the cappy with another wrong ROM, the I900. I managed to get it back into DL mode and tried flashing stock eclair or 2.2 froyo via ODIN. For some reason, whenever I start the flash (press start on Odin with the froyo 2.2 file on PDA), the progress fails at the factory section. I don't know much about jigs yet, but any tips would be greatly appreciated.
thanks
Chord in the back of the PC directly attached to the motherboard NO EXTERNAL HUBS, right click on Odin run as admin.
Once you have it working READ AND UNDERSTAND WHAT YOU'RE DOING, BEFORE DOING ANYTHING ELSE TO YOUR PHONE
This is probably the easiest guide on how to make one. Layman Jig First one I did I butchered a pare car charger to make it. You can just grab one from MobileTechVideos.com for about $8.
AlphaJ1 said:
Hi Guys,
I have a similar problem. I am a total noob-I've had my I896 cappy (Canadian Rogers based) for about a year now; i fiddled with it on Saturday and also got the bootloop. I freaked out, and managed to further flash (out of frustration and confusion) the cappy with another wrong ROM, the I900. I managed to get it back into DL mode and tried flashing stock eclair or 2.2 froyo via ODIN. For some reason, whenever I start the flash (press start on Odin with the froyo 2.2 file on PDA), the progress fails at the factory section. I don't know much about jigs yet, but any tips would be greatly appreciated.
thanks
Click to expand...
Click to collapse
Hi guys,
Thanks for the link.
From what I understand, a jig is an improvised connection that allows your phone to go into DL mode. What if my phone is still capable of going into DL mode? My apologies, as I am at work.
Im not sure what you mean with your question. What the jig does is give the signal for it to go to download mode as was intended by samsung. Same theory on how your phone knows its connected to your computer, or the wall or the car charger. Its by manipulating the current between 2 pins. Keep in mind your phone should always be capable of going in to download mode assuming the hardware is working and your bootloaders are in working order.
I believe I read it on a different website that as long as your phone can go into download mode, then it is only "soft-bricked," meaning it can still be recovered using ODIN. I don't know If I was misinformed or not. I guess my question is, since my phone is still able to go into download mode, but the flash is still failing, did I DL the wrong ROM, or was the copy of Froyo 2.2 I DL'd corrupt? If so, is there a reliable source/site where I can download Froyo or Eclair?
I hope that makes more sense.
Read my post after yours...
studacris said:
Chord in the back of the PC directly attached to the motherboard NO EXTERNAL HUBS, right click on Odin run as admin.
Once you have it working READ AND UNDERSTAND WHAT YOU'RE DOING, BEFORE DOING ANYTHING ELSE TO YOUR PHONE
Click to expand...
Click to collapse
^What he said. If that fails could be a faulty cable.
AlphaJ1 said:
I believe I read it on a different website that as long as your phone can go into download mode, then it is only "soft-bricked," meaning it can still be recovered using ODIN. I don't know If I was misinformed or not. I guess my question is, since my phone is still able to go into download mode, but the flash is still failing, did I DL the wrong ROM, or was the copy of Froyo 2.2 I DL'd corrupt? If so, is there a reliable source/site where I can download Froyo or Eclair?
I hope that makes more sense.
Click to expand...
Click to collapse
You are correct, if you can get into download mode you are not bricked. Make sure you are using the usb cord that came with your phone, plugged directly into the back of your computer. Make sure your SIM card is out, you're logged in as an administrator, and that you start odin before you plug your phone in.
If it still doesn't work, try another computer and/or another cord.
Why do people say take sim out? Ive never taken it out and had no issues. Just curious.
That is a practice from way back in the winmo days, sometimes the flash would corrupt the Sim itself. Not the case anymore for the most part. I'm with you never take mine out either.
Thanks guys, I will try this at home; hopefully it works.
prbassplayer said:
Why do people say take sim out? Ive never taken it out and had no issues. Just curious.
Click to expand...
Click to collapse
I say it because, while I've never had it screw up the SIM itself, I had a situation where I forgot to remove it and then couldn't get odin to complete a flash on several attempts, resulting in a soft brick that I couldn't flash out of. As soon as I removed the sim, Odin flashed without an issue.
Coincidence? Maybe, although I didn't change anything else. If it possibly keeps me from repeating this terrifying event, though, I'll just keep doing it
apbthe3 said:
I say it because, while I've never had it screw up the SIM itself, I had a situation where I forgot to remove it and then couldn't get odin to complete a flash on several attempts, resulting in a soft brick that I couldn't flash out of. As soon as I removed the sim, Odin flashed without an issue.
Coincidence? Maybe, although I didn't change anything else. If it possibly keeps me from repeating this terrifying event, though, I'll just keep doing it
Click to expand...
Click to collapse
Did you get a red "FAIL" message on ODIN? Because thats what I got several times. My buddy also tried and he got the same thing. The green progress bar completes up till about 80 percent and gives up on me. I'll try taking out the SD and SIM cards when I get home, hopefully it works.
Hi guys, little update:
I found this on the forums and used it:
http://forum.xda-developers.com/showthread.php?t=731989
Anyways, this worked after my second try. Interestingly enough, it worked once i removed the Sim card, which is what apbthe3 suggested..great! I'm just glad my phone is no longer bricked. Minor issue though, my phone is now an AT&T phone, but unfortunately, I am a Canadian Samsung user. New problem now. My phone is no longer rooted (never was actually, but was bricked in the process), I'm happy it works, but i need to know if there are any Canadians out there that know how to revert my device back to Rogers.
Any help would be great. Anyways, the link I provided works great, so its a great resource for our American friends.
Why don't you look at Cognition 4.x.x? Froyo stock ish looking rom tweaked out the ass very fast. Good rom.
Look in development. There are a couple of threads there just for Rogers users.
Hi,
I installed a Cyanogenmod ICS 4.0.3. build 17 firmware on my Samsung Galaxy S I9000 almost 5 months ago from a tutorial. The update itself has been a fantastic experience from the start and I'm not sure if my current problem is even related to that firmware update. Apparently new users like me can't post URLs so I can't provide it now. If you need it let me know.
I have to admit that lately the phone has been rebooting every couple of days, or Android's been freezing and I had to remove the battery, but I didn't think too much of it. It wasn't too bad of a problem really, but this morning all of a sudden the device has become totally unusable. Help! :-/
The issue that's started since today is that my phone won't boot anymore. It seems to reboot somewhere during the boot process. There's only two screens that will be shown, before it reboots. When I remove the battery, put it back in and attach the charger, I will only see two charging screens. While charging, the device will also*reboot after a while.*
I can get into download-mode (volume-down + ok-button + power-key) but can't get into recovery mode (volume-up + ok-button + power-key).
Any ideas would be appreciated, thanks!
Greetings,
Adriaan
ps -> I have pictures of the booting screens and the charging screens but wasn't allowed to post them here. Again, if you need to see them please PM.
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
I'll try that, thanks.
switch_42 said:
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
Click to expand...
Click to collapse
just to be sure...
Just to be sure, could you please check that my logic is correct?
First off: the tutorial I had followed had me follow a few procedures:
first I updated Galaxy S with XXJVU Firmware
then rooted Galaxy S on XXJVU Firmware
after that I flashed CM 9, ICS 4.0.3. build 17 to the device
To which of these steps were you referring? My guess would be to take the last one, but perhaps it's wiser to restart the tutorial from the beginning. I'd appreciate any additional support you can give me, you can understand that I don't want to brick my device due to my misunderstandings..
Seems like a high overclock or high underclock
Sent from my GT-I9000
Helloworld294 said:
Seems like a high overclock or high underclock
Click to expand...
Click to collapse
Not sure what you mean there. In any event I've never taken any steps to overclock or underclock my device. Maybe it's going senile and I get to buy a galaxy s III soon
*phew* well my problem's been solved. Since I was able to get into download mode I flashed a baseline rom with Odin and found my way back to ICS. One surprise along the way was that from the same tutorial I had followed (and had happy results from) a few months ago, the step of using Odin to root the device wasn't working, it kept getting stuck at 'zImage' during the process! What's more, after that I was getting the BSOD image (the phone, exclamation mark and computer), which I found could be helped by using a 'One-Click Unbrick for Samsung devices'.
That was a XXJVU firmware. After some snooping around I found a different firmware than the one I had previously used and had switched from a XXJVU firmware to a XXJW4 firmware through a page on XDA-Developers. Did that. It worked. And now I'm back to ICS again, yay!
Thanks for the help along the way!
Hi All.
I am looking for help and advice with regards to getting my wife's Samsung Galaxy S3 Mini GT-I8190N working again.
My wife has been having issues with this phone restarting it's self at random on and off for the last few months, but as the phone is always in use/needed, I have been unable to have a look for the cause of the problem.
A few weeks ago the phone powered down, and would not switch back or, it would also not charge.
After removing the battery and having a closer look it seems that the battery has swollen and is no longer flat so a new replacement battery was ordered.
The new replacement battery was fitted and the phone was put on charge, the phone displayed that is was now charging, I thought all was good and just left the phone to charge.
Some time later on I tried to power on the phone, but am just greeted by "Samsung Galaxy S3 Mini GT-I8190N" logo and then the phone just restarts again, and keeps on doing this.
The phone is 100% stock, it has not been unlocked or re-flashed.
The phone is on contract from Tesco Mobile, but my wife has been told by Tesco that the warranty has expired.
From searching on the forum it seems that it is quite common for Samsung phones to get stuck in this kind of boot loop.
So far it seems that there are two possible ways to fix the current issue.
1 - Power off the phone and go into boot-loader and do a factory reset.
or
2 - Re-flash the stock rom.
So I thought I would 1st try the factory reset.
So I removed and replaced the battery, Held down "Volume Up, Home, Power", I am then greeted by "Samsung Galaxy S3 Mini GT-I8190N" logo and the phone just sits there.
So it now looks like the only other option is to re-flash the phone with the stock rom.
But how do I find out what stock rom that I need for this phone, as I am unable to get into the bootloader to run any ADB or FastBoot commands.
Any help would be much appreciated.
Thanks for your time.
Best Regards.
MadProfessor2002 said:
Hi All.
I am looking for help and advice with regards to getting my wife's Samsung Galaxy S3 Mini GT-I8190N working again.
My wife has been having issues with this phone restarting it's self at random on and off for the last few months, but as the phone is always in use/needed, I have been unable to have a look for the cause of the problem.
A few weeks ago the phone powered down, and would not switch back or, it would also not charge.
After removing the battery and having a closer look it seems that the battery has swollen and is no longer flat so a new replacement battery was ordered.
The new replacement battery was fitted and the phone was put on charge, the phone displayed that is was now charging, I thought all was good and just left the phone to charge.
Some time later on I tried to power on the phone, but am just greeted by "Samsung Galaxy S3 Mini GT-I8190N" logo and then the phone just restarts again, and keeps on doing this.
The phone is 100% stock, it has not been unlocked or re-flashed.
The phone is on contract from Tesco Mobile, but my wife has been told by Tesco that the warranty has expired.
From searching on the forum it seems that it is quite common for Samsung phones to get stuck in this kind of boot loop.
So far it seems that there are two possible ways to fix the current issue.
1 - Power off the phone and go into boot-loader and do a factory reset.
or
2 - Re-flash the stock rom.
So I thought I would 1st try the factory reset.
So I removed and replaced the battery, Held down "Volume Up, Home, Power", I am then greeted by "Samsung Galaxy S3 Mini GT-I8190N" logo and the phone just sits there.
So it now looks like the only other option is to re-flash the phone with the stock rom.
But how do I find out what stock rom that I need for this phone, as I am unable to get into the bootloader to run any ADB or FastBoot commands.
Any help would be much appreciated.
Thanks for your time.
Best Regards.
Click to expand...
Click to collapse
Download the stock firmware you prefer from here: http://www.tsar3000.com/Joomla/inde...iii-mini-firmwares&catid=55:samsung&Itemid=82
Then follow this guide to install it: http://forum.xda-developers.com/showthread.php?t=2429169
Riky720: Thank you for your reply, and the links.
I have already been reading the following guides
[GUIDE] Stock Rom - All S3 Mini
and
[GUIDE] Unroot / Unbrick, Flash official stock firmware on Galaxy SIII Mini GT-I8190
Can you please advice how I can find out what is the correct firmware / stock rom to download, as the phone will not boot, and I am unable to use ADB or Fastboot to pull any information from the phone.
As said before my wife got the phone from Tesco Mobile on contract, and from my understanding is that Tesco Mobile uses the O2 Network.
Looking at the list of firmware's I can't not see any listed as Tesco Mobile.
Thanks again for your time.
Best Regards.
I am still having issues with this phone, and I have been unable to progress forward.
I did start this post: Samsung Galaxy S3 Mini GT-I8190N - Re-flashing stock rom, to try and locate the stock firmware (rom) so that I could re-flash it.
From my other post I have been able to locate the following firmware (roms) for the phone.
I8190NXXAMJ2_I8190NBTUAMJ1_BTU.zip
I8190NXXAMG1_I8190NOXXAMG1_BTU.zip
I8190NXXALL6_I8190NOXXALL3_BTU.zip
I have tried flashing all of the above firmwares (roms) one by one, but I am still having the same issue.
Can anyone please advice me on anything else that I can try.
Thanks for your time.
Best Regards.
I am still having issues with this phone, and would really like some help and advice.
I found this post with a similar issue: S3 Mini stuck in boot loop after flashing cm 10.2 try odin am i missing a step?
The above post pointed me here: Official ROOTED firmwares for the SIII mini - OXX csc
I have once again tried all the I8190N firmware (roms) listed, and I am still having the same issue as before.
Just to recap the issue that I am having.
The phone will switch on, get as far as displaying "Samsung Galaxy S3 Mini GT-I8190N" then the phone restarts, this will on happening.
If you try to start the phone in bootloader / recovery mode the phone will just display "Samsung Galaxy S3 Mini GT-I8190N" and sit there.
Powering up the phone in Odin mode seems to work fine.
Thanks again for your time.
Best Regards.
MadProfessor2002 said:
I am still having issues with this phone, and would really like some help and advice.
I found this post with a similar issue: S3 Mini stuck in boot loop after flashing cm 10.2 try odin am i missing a step?
The above post pointed me here: Official ROOTED firmwares for the SIII mini - OXX csc
I have once again tried all the I8190N firmware (roms) listed, and I am still having the same issue as before.
Just to recap the issue that I am having.
The phone will switch on, get as far as displaying "Samsung Galaxy S3 Mini GT-I8190N" then the phone restarts, this will on happening.
If you try to start the phone in bootloader / recovery mode the phone will just display "Samsung Galaxy S3 Mini GT-I8190N" and sit there.
Powering up the phone in Odin mode seems to work fine.
Thanks again for your time.
Best Regards.
Click to expand...
Click to collapse
Let me understand.
Download mode is working fine and ODIN recognizes phone ?
You tried to flash stock ROM via Odin ?
But It still stucked in bootloop ?
That is correct.
Are you sure about did you find the stock ROM ?
Behind the battery there is a paper. With S/N you may understand which baseband do you have
I am not sure about the stock firmware (rom), that is why I have been asking for help and advice.
The sticker under the battery has the following details:
MODEL: GT-I8190N
FCC ID: A3LGTI8190N
SSN: -I8190NGSMH
IMEI: ******/**/******/*
S/N: R21D7D7BEJE
Click to expand...
Click to collapse
The sticker on the NAND Flash chip has the following details:
073110
H49C BTU
HS033741
C-HVT1
I8190NXXA
Click to expand...
Click to collapse
Are you above to advice me what is the correct firmware (rom) I need with the above details?
Best Regards.
You should try kies. It will find the correct ROM but I didnt use it and its diffrent from ODIN
Kies does not work, when you have kies loaded and then plug the usb cable into the phone kies just shows connecting but fails to connect or do anything else.
You need to unistall ODIN. Did you entered your phone S/N and did kies download the files ?
simbilli said:
You should try kies. It will find the correct ROM but I didnt use it and its diffrent from ODIN
Click to expand...
Click to collapse
Here are some question about Kies.
Does Kies detect a rooted device and deny its USB connection?
Or limit any feature on it?
I`m facing a problem using Odin and USB connection while
trying to flash TWRP update on my Samsung Galaxy S3 Mini (GT-I8190N).
i have no issue using Kies to make a backup before, so i`m guesting that`s the reason.
my solution was to uninstall Kies temporarily(keeping the backup files).
Its no major problem, just trying to communicate and share opinions in this forum.
Anyone having/had this kind of problem?
Naimlaaa said:
Here are some question about Kies.
Does Kies detect a rooted device and deny its USB connection?
Or limit any feature on it?
I`m facing a problem using Odin and USB connection while
trying to flash TWRP update on my Samsung Galaxy S3 Mini (GT-I8190N).
i have no issue using Kies to make a backup before, so i`m guesting that`s the reason.
my solution was to uninstall Kies temporarily(keeping the backup files).
Its no major problem, just trying to communicate and share opinions in this forum.
Anyone having/had this kind of problem?
Click to expand...
Click to collapse
Did you installed USB drivers ?
simbilli said:
Did you installed USB drivers ?
Click to expand...
Click to collapse
I did. Probably after done the backup via Kies, I think (not sure the exact time).
I was looking forward on flashing custom ROMs.
Naimlaaa said:
I did. Probably after done the backup via Kies, I think (not sure the exact time).
I was looking forward on flashing custom ROMs.
Click to expand...
Click to collapse
Ok now If you installed USB drivers flash twrp via ODIN. Donf forget to unistall kies.
simbilli said:
Ok now If you installed USB drivers flash twrp via ODIN. Donf forget to unistall kies.
Click to expand...
Click to collapse
Thank you simbili Bro. Will flash -f2fs 2.8.1.0 version. i just got an update of CM11 Rom, maybe will use it on my Mini`s. Thanks again simbili.
:highfive:
Your welcome
I will be happy If you use thanks button :good:
simbilli said:
Your welcome
I will be happy If you use thanks button :good:
Click to expand...
Click to collapse
Done. :good:
What does the "thanks" button main effect anyway?
Naimlaaa said:
Done. :good:
What does the "thanks" button main effect anyway?
Click to expand...
Click to collapse
It just effects thanks meter not a big thing