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.
Hi, I just rooted my phone and installed Darky's ROM etc. Everything went perfectly but I just did a factory reset on my phone through the settings > privacy menu. Then i turned my phone off, now it's stuck on the boot screen (the one that says:
Galaxy S
GT-I9000
Samsung
)
Anyone know what I can do to resolve this?
PS, I've tried booting into recovery and download mode,- only download mode works
Flash ressurrection with Odin, or just try reflash a kernel.
Post in right section next time !
And don't say "dead" "brick" if you have download mode, nothing is more "noob" !
Sent from my GT-I9000 using XDA App
Flash another ROM in Odin with re-partition. You need CSC, Modem, and ROM. The next time, factory reset/wipe, clear cache, and clear Dalvik cache before flashing to a custom ROM, not after.
Also, this is the wrong section for this.
If download mode still works, its unlikely that its ' dead'.
Probably just a corrupted filesystem or some missing file that it needs.
If youve tried everything else, the thing left to do is flash a complete firmware via either Odin or Heimdall, in download mode. That should give you a working phone again.
First, wrong section... post in the right section next tome.
Get darky resurection edition and flash with odin, then reflash darky nornal rom from cwm
Sent from my GT-I9000
WiwiPouPou said:
Flash ressurrection with Odin.
Post in right section next time !
And don't say "dead" "brick" if you have download mode, nothing is more "noob" !
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Apologies for being a noob, couple of questions though:
never mind
EDIT: Thanks for your responses, and don't answer the above question
thanks for your help everyone
Which is the correct section for this type of thread though?
And Mods- please move this thread to correct location, cheers!
WRAITH07 said:
Apologies for being a noob, couple of questions though:
never mind
EDIT: Thanks for your responses, and don't answer the above question
thanks for your help everyone
Which is the correct section for this type of thread though?
And Mods- please move this thread to correct location, cheers!
Click to expand...
Click to collapse
follow this guide for flashing stock rom --> http://darky.ficeto.com/community/i...-stock-rom-over-darkys-rom-gt-i9000-only.486/
AND: if you can access DL mode then Recov Mode is working too. You are just doing something wrong then ... for Recov Mode you need to release all buttons when Galaxy S logo appears.
WRAITH07 said:
Apologies for being a noob, couple of questions though:
never mind
EDIT: Thanks for your responses, and don't answer the above question
thanks for your help everyone
Which is the correct section for this type of thread though?
And Mods- please move this thread to correct location, cheers!
Click to expand...
Click to collapse
For questions maybe the questions and answers section
Anyway, with download mode our phone is pretty much unbrick/killable unless you flash another bootloader which is a) rare and b) not really a threat either
I think my phone is dead.... can anyone help me verify that? I've been reading all over and tried all ways to get a response, but there's none.
I pulled the battery and let it sit for several hours before inserting. - No response.
Put in my spare batte, have it plugged to charger. Also no response.
Plug to PC, PC doesn't even see the phone.
Cannot go into recover, download or boot or show any signs of life.
It was charging fine one moment (last saw about 80%) then about 10 min later, went to unplug to use.... but found the phone dead and rather warm. (not sure if that is usual since the batt was being charged)
Anyway, I flashed my phone only 1 week ago using "Insane" kernel and doing Overclock to 1200 with about -75 undervolt across the frequencies. Did I kill the phone by doing this ???
What are my chancs of getting warranty on it if the service centre manages to find out it had been flashed??
What are my options now? Any other areas to chek and try to recover?
Thanks
Well, if you can't get into download mode, there is still one more step to try before giving up. Go to ebay and search for I9000 usb jig. That might be able to force your phone into download mode. (They are cheap. Very cheap.)
If that doesn't work, there's nothing else you can do but to bring it back to a service centre.
Check out the info for the rig you mentioned. Apparently, it doesn't wotk for phones that are totally dead. i.e. no signs of life at when buttons are pressed, no lights etc.
I brought the set down the to service centre and luckily, the lady there did not ask me anything much. She just swapped out the batt to verify, plugged into USB charger to verify... then started to fill in the form for the phone to be sent in for repairs. Though she's not the repair person.... she did mentioned that all data would be lost and most likely a new board would be put in.
I'm keeping my fingers crossed that'll be the case... just gimme a new PCBA w/o trying to repair the current one. Hope they don't have any diagnostic tool/fixture where they can boot from a "debug" chip (such as processor, etc) to do board level repair.... then it might just show up that I'm running a modified kernel & ROM.
They cant check, if you were runnig custom ROM. Stop worrying, mostly they do not have a choice but to replace PCB. This is my personal exp. with samsung.
Sent from my GT-I5700 using Tapatalk
Recently, I flashed my SGS I9000 with DarkyROM v11.0 Black Edition and all went smoothly. I did this while I was in Pakistan for the holidays. When I came back to the UK, I found that my phone wasn't getting any service, not from my old sim or my new sim. My new sim had been activated on the day I got back and it just showed the crossed-out triangle. My old sim was supposed to be working but it wasn't working on the phone for some reason. After a fair amount of hours spent on researching on the problem, I figured that my efs was corrupted. A symptom of this was that my imei had changed and I'm not sure how to get it back.
Samsung Services decided to shut the door in my face and I haven't any solutions as of yet.
What's your take on this? Do you have any solutions to this problem?
All help is greatly appreciated, thank you.
Any one have any solutions to this problem?
Why you did not backup of efs folder before flashing? ...sometimes flashing official gingerbread rom helps in getting imei back, so try that :/
This should help (replace Froyo by a Gingerbread release)
http://forum.xda-developers.com/showthread.php?t=1647890
Did it today with my dad's Galaxy S that lost service after installing CM9.
juvenile582 said:
What's your take on this? Do you have any solutions to this problem?
.
Click to expand...
Click to collapse
check out My Android Solutions, link below for the various options to solve efs & IMEI problems
juvenile582 said:
Recently, I flashed my SGS I9000 with DarkyROM v11.0 Black Edition and all went smoothly. I did this while I was in Pakistan for the holidays. When I came back to the UK, I found that my phone wasn't getting any service, not from my old sim or my new sim. My new sim had been activated on the day I got back and it just showed the crossed-out triangle. My old sim was supposed to be working but it wasn't working on the phone for some reason. After a fair amount of hours spent on researching on the problem, I figured that my efs was corrupted. A symptom of this was that my imei had changed and I'm not sure how to get it back.
Samsung Services decided to shut the door in my face and I haven't any solutions as of yet.
What's your take on this? Do you have any solutions to this problem?
All help is greatly appreciated, thank you.
Click to expand...
Click to collapse
i slove my IMEI problem buy using this step:
1) flash to stock rom and Check IMEI (*#06#) you will get the right IMEI number
2) connect you phone to the PC and copy the EFS file to the PC
3) Root the Phone and Flash to custom ROM you like (Check IMEI if is Wrong end with (0000)
4) Connect your phone to the PC and delete EFS folder on your PHONE
5) Copy the EFS file from your PC (Step2) and paste to your PHONE and restart the PHONE.
Hope this will help.
Samtan4326 said:
i slove my IMEI problem buy using this step:
1) flash to stock rom and Check IMEI (*#06#) you will get the right IMEI number
2) connect you phone to the PC and copy the EFS file to the PC
3) Root the Phone and Flash to custom ROM you like (Check IMEI if is Wrong end with (0000)
4) Connect your phone to the PC and delete EFS folder on your PHONE
5) Copy the EFS file from your PC (Step2) and paste to your PHONE and restart the PHONE.
Hope this will help.
Click to expand...
Click to collapse
Actually when I enter that code in, it gives me the IMEI i'm trying to get rid of.
Thanks for the suggestion!
When I lost my imei I just reflashed to stock couple times and my imei got restored automatically
Sent from my SGH-T959 using xda app-developers app
Mantis64 said:
This should help (replace Froyo by a Gingerbread release)
http://forum.xda-developers.com/showthread.php?t=1647890
Did it today with my dad's Galaxy S that lost service after installing CM9.
Click to expand...
Click to collapse
gun said:
When I lost my imei I just reflashed to stock couple times and my imei got restored automatically
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
I tried both of your ideas but it just wouldn't restore my imei for some reason. How many times did you flash yours?
I flashed different custom roms I think 4 and kept replacing them with stock rom
Sent from my SGH-T959 using xda app-developers app
Okay, I've hit a new low. You can blame my stupidity for this.
I was looking at xsenman's suggestions and I asked about one of his methods, he told me to use the M110S Repair kit which I downloaded. I opened it up and it shows a bunch files that I had to flash to my phone. While flashing my phone and eventually bricking it, I realised that the M110S is the Korean version and I just tried to flash that firmware onto mine, resulting in a brick. Basically, I hold the power button and it shows the Samsung Anycall logo and that's about the extent of the boot and my capabilities. I cannot go into download mode or recovery mode (via 3 buttons) it just tries to boot up the phone.
I have realized my complete idiocy at this point but I could use anything just to get my phone back up so that I can atleast continue trying to sort out the IMEI.
Today, 07:39 AM
juvenile582 said:
Hang on, this is for a different model...I've got the Samsung Galaxy S I9000 not the M110S.
Click to expand...
Click to collapse
Today, 07:46 AM
xsenman said:
hmmm, than you are on the wrong forum, anyway than you should try the solutions available for i9000 do you have any EFS backup? If not try downgrade to Froyo to see if it will work for you
Click to expand...
Click to collapse
Today, 05:58 PM
juvenile582 said:
Okay, I've hit a new low. You can blame my stupidity for this.
I was looking at xsenman's suggestions and I asked about one of his methods, he told me to use the M110S Repair kit which I downloaded. I opened it up and it shows a bunch files that I had to flash to my phone. While flashing my phone and eventually bricking it, I realised that the M110S is the Korean version and I just tried to flash that firmware onto mine, resulting in a brick. Basically, I hold the power button and it shows the Samsung Anycall logo and that's about the extent of the boot and my capabilities. I cannot go into download mode or recovery mode (via 3 buttons) it just tries to boot up the phone.
I have realized my complete idiocy at this point but I could use anything just to get my phone back up so that I can at east continue trying to sort out the IMEI.
Click to expand...
Click to collapse
Ok, this is rather strange and sad to hear , as you made a post in the Korean M110S Forum, my suggestions were for you to use the Korean repair kit at Today, 06:13 AM in response to a post made at Today, 03:07 AM.
But by Today, 07:39 AM, you responded I am referring to the wrong model and by Today, 07:46 AM, I advised you to use the i9000 froyo ROM instead .
So it sad to hear you still used the M110S repair kit knowingly , even after I advised you not to use it, at 07:46 AM today?
Anyway, what you should do is first power down, remove battery, remove SIM Card and Ext SD card, , press power button for a few min, than reinsert battery only and try for download mode or use Methods mention on MY Android Solutions, link below to achieve download mode .
Forget about recovery mode, get download mode and use PIT and full i9000 ROM package, use JVZ or JVU with boot loaders
I, Personally had tested i9000 ROMS on the M110S and spend a few hours flashing M110S repair kit over and over again to recover, so as long as your phone can get into download mode or with a help of a JIG, its not bricked.
xsenman said:
Today, 07:39 AM
Today, 07:46 AM
Today, 05:58 PM
Ok, this is rather strange and sad to hear , as you made a post in the Korean M110S Forum, my suggestions were for you to use the Korean repair kit at Today, 06:13 AM in response to a post made at Today, 03:07 AM.
But by Today, 07:39 AM, you responded I am referring to the wrong model and by Today, 07:46 AM, I advised you to use the i9000 froyo ROM instead .
So it sad to hear you still used the M110S repair kit knowingly , even after I advised you not to use it, at 07:46 AM today?
Anyway, what you should do is first power down, remove battery, remove SIM Card and Ext SD card, , press power button for a few min, than reinsert battery only and try for download mode or use Methods mention on MY Android Solutions, link below to achieve download mode .
Forget about recovery mode, get download mode and use PIT and full i9000 ROM package, use JVZ or JVU with boot loaders
I, Personally had tested i9000 ROMS on the M110S and spend a few hours flashing M110S repair kit over and over again to recover, so as long as your phone can get into download mode or with a help of a JIG, its not bricked.
Click to expand...
Click to collapse
At 7:39am, I had already flashed. At 7:30, I discovered that it was a different model. I spent some time trying to fix it before I sent that message.
Also, I'm going to try that jig method, see if it works.
juvenile582 said:
At 7:39am, I had already flashed. At 7:30, I discovered that it was a different model. I spent some time trying to fix it before I sent that message.
Also, I'm going to try that jig method, see if it works.
Click to expand...
Click to collapse
download combo keys may change when OTHER firmware are used on a phone, so you should try different combinations for download mode . For M110S , download mode is home key +power key...give it a try or
1) To enter download mode [volumedown+home+power] or home +power
2) While in this position, insert the battery
I once lost mine, and to get it back, I flashed back the last known good configuration.
Unfortunately sometimes these things happen.
Right, the phone is back onto Gingerbread 2.3.6 after a cheap jig that I ordered forced it into download mode. I then flashed froyo then gingerbread and now I'm back to where I started, no service and a missing imei.
I've had a development!
Okay, so after playing around with the phone, rooting and stuff. I managed to get my 3g working somehow but still no imei, texting or calling. Really strange how I can use internet but not be able to text or call anyone
juvenile582 said:
I've had a development!
Okay, so after playing around with the phone, rooting and stuff. I managed to get my 3g working somehow but still no imei, texting or calling. Really strange how I can use internet but not be able to text or call anyone
Click to expand...
Click to collapse
is it still in warranty?
TotallydubbedHD said:
is it still in warranty?
Click to expand...
Click to collapse
From what I know of rooting, my warranty's void by now. (It's like the tenth time I've rooted it)
juvenile582 said:
From what I know of rooting, my warranty's void by now. (It's like the tenth time I've rooted it)
Click to expand...
Click to collapse
if you get back on stock rom, wipe everything - samsung won't know
So my question remains
I would try figuring it out via google searches etc - but if you can't you could always send it into samsung.
So the other day i was on my captivate and i had just factory reset it to original eclair. so i tried updating it with kies but it kept failing. So i then tried using Odin and accidently checked bootloader and now my phone turned off and wont show any signs of life. PLEASE IM ASKING YOU PLEASE HELP! What do I do?
Can u get into Download mode with button combo or jig ?
If ur phone shows zero signs of life, even when plugged in to a wall charger, then it is probably hard bricked and so u will need jtag service in order to bring ur phone back to life. Check out mobiletechvideos.com, they can fix ur phone.
4-2ndtwin said:
Can u get into Download mode with button combo or jig ?
If ur phone shows zero signs of life, even when plugged in to a wall charger, then it is probably hard bricked and so u will need jtag service in order to bring ur phone back to life. Check out mobiletechvideos.com, they can fix ur phone.
Click to expand...
Click to collapse
But i dont get it. I was flashing with odin and it magically formatted the bootloader. Is there a way for me to fix it by myself like restoring the bootloader. I got my phone only 2 month ago. I dont have 40 dollars to invest on jtag service. Like how would they fix it. Could I please get instructions? Thanks and most help is appreciated
Theboss14 said:
But i dont get it. I was flashing with odin and it magically formatted the bootloader. Is there a way for me to fix it by myself like restoring the bootloader. I got my phone only 2 month ago. I dont have 40 dollars to invest on jtag service. Like how would they fix it. Could I please get instructions? Thanks and most help is appreciated
Click to expand...
Click to collapse
It doesn't format the bootloaders per say, it you flash a stock ROM with Odin that has bootloaders and if it gets interrupted while it's replacing them, your phone will be bricked as it doesn't have a way to boot (hence the name bootloaders).
The JTAG service basically pushes the bootloaders into the phone. It's something we can't do on our own unless we have the right equipment (riftbox).
Like 4-2ndtwin mentioned, try to get some response from your phone, anything that would show life. That means you can recover on your phone. From there, you'd have to be able to get in download mode and flash Odin KK4 without ANY interruption.
My phone wont turn on and when i put it in charge it wont even show the battery charging. What else can i do to fix my phone?
Theboss14 said:
My phone wont turn on and when i put it in charge it wont even show the battery charging. What else can i do to fix my phone?
Click to expand...
Click to collapse
Try the button combo to get in download mode (could even try a jig). If that fails too, you'll have to get jtag service.
Sent from my SGH-I747 using xda app-developers app
:cyclops:Fine If i Have to send my captivate for a jtag then i guess i will if thats my only options. But I find the one on mobiletechvideos really expensive does anyone know an alternative. Thanks. I apreciate it if you tell me.
Theboss14 said:
:cyclops:Fine If i Have to send my captivate for a jtag then i guess i will if thats my only options. But I find the one on mobiletechvideos really expensive does anyone know an alternative. Thanks. I apreciate it if you tell me.
Click to expand...
Click to collapse
The only alternative I can suggest you is to find that service around your place, hopefully for cheaper.
Yo. I think this service is legit. Is it?
On ebay.com
/itm/Samsung-Galaxy-Riff-Box-JTAG-Boot-Restore-Unbrick-Service-/271281826547?pt=US_Cell_Phone_Replacement_Parts_Tools&hash=item3f29a82af3
Theboss14 said:
Yo. I think this service is legit. Is it?
On ebay.com
/itm/Samsung-Galaxy-Riff-Box-JTAG-Boot-Restore-Unbrick-Service-/271281826547?pt=US_Cell_Phone_Replacement_Parts_Tools&hash=item3f29a82af3
Click to expand...
Click to collapse
Kinda hard to know. look at the seller's rep Imo.
Samsung Captivate is dead, unable to go in download mode....
Hi,
I also have similar kind of issue which is still not resolved.Long time back postem my problem regarding my samsung captivate phone, I tried all the solution provided my members of this community to fix my issue. But it is still not resolve.
Could you please look in to my thread, and advise me what could be the problem and how can I repair my phone ?
Below is link to my thread where I have mentioned the issue in detail -
http://forum.xda-developers.com/showthread.php?t=2194325
Jtag. The only possible way out.
Sent from my GT-S5282 using xda premium
vishu_10d said:
Hi,
I also have similar kind of issue which is still not resolved.Long time back postem my problem regarding my samsung captivate phone, I tried all the solution provided my members of this community to fix my issue. But it is still not resolve.
Could you please look in to my thread, and advise me what could be the problem and how can I repair my phone ?
Below is link to my thread where I have mentioned the issue in detail -
http://forum.xda-developers.com/showthread.php?t=2194325
Click to expand...
Click to collapse
From what I've read in your thread, you had the i9000 image working, correct? If so, why not just roll with it?
All Captivate/i9000 rom works with the i9000 bootloader. Captivate GB Rom will need to get the 2.3.5 i9000 Music Player APK, but aside from that, it all works. AOSP roms like Cyanogenmod and Slimbean will work out of the box if you get the captivate version. To install them, you'll need a slight workaround though:
Flash a kernel with CWM.
From there, flash the Captivate Glitch Kernel V13. It only comes in .ZIP format, which is why you need a CWM kernel before hand
Flash CM7 to convert the partition table(IMPORTANT. Rom will not boot if you skip this step.)
Flash anything from here on. If it throw a status 7 about device not being SGH-i896/SGH-i897, etc..., flash the Glitch Kernel before attempting to flash the ROM. You do not need to flash CM7 again.
(I know other ROM should have converted the partition table, but in reality it doesn't. Since you're flashing from Glitch, a CM7/MIUI kernel, they assumes you already have the MTD partition layout, and only resize it instead of doing a full conversion. CM7 check the partition table regardless of which kernel you're flashing it from.)
As a plus, Deep Idle works only with the i9000 bootloader. You'll get sleep of death otherwise. If you want your ATT World Phone image back, you can flash the custom param.lfs and change it manually. This can only be done from Touchwiz ROM though.
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
emsoh said:
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
Click to expand...
Click to collapse
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
arneldna said:
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
Click to expand...
Click to collapse
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
emsoh said:
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
Click to expand...
Click to collapse
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
th3cr0w said:
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
Click to expand...
Click to collapse
Ok, it makes me a bit more calm and Im starting to believe a bit, theres a way back for the phone to rise again. So you mean it might not be the failure of missed debugging, instead the critical main thing can be re-partiton?! It sounds very possible based on what you said.
The thing now is, ofcourse I would be satisfied if my first plan come true. But right now I really dont care what version it´ll be running, rooted or not. I only want it to act like a smartphone again n matter what´s installed. So I will go with your advise and test it one by one.
Thanx so far! To be continued..
SOLVED Forgot USB-debugging downgrading
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
emsoh said:
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
Click to expand...
Click to collapse
Glad to know you fixed it.. Appreciate your patience and efforts... :thumbup:
You don't care where I sent it from....!