Hi,
I just bought a Samsung Galaxy S i9000 white, and started to work on getting CyanogenMod on it.
Then I noticed that someone in the shop (I guess) had already messed with it. It came with Lidroid ROM installed, but no ClockworkMod recovery.
Anyway, I started having strange issues trying to flash first the ClockworkMod recovery with Heimdall.
Then I decided to try going back to a stock rom, and take it from there.
After a lot of messing around, here is the status:
I have used Heimdall to flash a stock ROM, using first the 512 .pit, and then the 803 .pit.
Then I used the hardcore-speedmod.tar zImage with Heimdall, and finally got ClockworkMod recovery going.
I flashed CyanogenMod 7.2, which "works", but has some strange problems. See below.
I am becoming suspicious that this is not a 100% real Galaxy S (not sure if that's possible, though).
Problems:
Front buttons (Settings, Home, Back) don't work.
Screen rotation is messed up: it's like the sensor is 90 degrees rotated.
No GSM network, fortunately WiFi works. With some effort, I have made it to the Settings menu on CM9.1, and I have lost my IMEI I'll have to research into getting it back.
Can anyone give me some hints? Here are my questions:
There is a sticker with IMEI and model under the battery, it says i9000gsmh. How can I check 100% sure which model of Samsung Galaxy S i9000 I have?
Lidroid is a Chinese ROM, is that a clue? I can't find any useful information on it in English. Maybe I need to flash that and stay with it? (if I can find it)
Thanks for your help!!
kbloodstone said:
I just bought a Samsung Galaxy S i9000 white, and starte
Can anyone give me some hints? Here are my questions:
There is a sticker with IMEI and model under the battery, it says i9000gsmh. How can I check 100% sure which model of Samsung Galaxy S i9000 I have?
Lidroid is a Chinese ROM, is that a clue? I can't find any useful information on it in English. Maybe I need to flash that and stay with it? (if I can find it)
Thanks for your help!!
Click to expand...
Click to collapse
read this thread http://forum.xda-developers.com/showthread.php?t=1844821&page=2 and also this http://forum.xda-developers.com/showthread.php?t=1880689 and a few others, I have forgotten about
This units i9000gsmh seem to have an Anycall boot loader , which by right be used only on a M110S, but seems to be used by Lidroid ( Chinese developer) ..keeps me wondering if its a clone..problem here, they seem to get stuck and not being able to be changed by flashing a i9000 boot loader .
leads me to think that this units could be switched with motherboard or chips meant for Anycall M110S ...anyway solutions for IMEI issues are mentioned on My Android Solutions, link below
I'm going to try that M110S repair kit. See if I can get back to something that can be used as a phone, first priority.
I saw the Anycall logo on my screen, but back then I didn't know that I wasn't supposed to see that on a real i9000.
I think someone in South-East Asia has obtained a bunch of M110S, and has realized that swapping the case makes them worth more money...
xsenman said:
read this thread http://forum.xda-developers.com/showthread.php?t=1844821&page=2 and also this http://forum.xda-developers.com/showthread.php?t=1880689 and a few others, I have forgotten about
This units i9000gsmh seem to have an Anycall boot loader , which by right be used only on a M110S, but seems to be used by Lidroid ( Chinese developer) ..keeps me wondering if its a clone..problem here, they seem to get stuck and not being able to be changed by flashing a i9000 boot loader .
leads me to think that this units could be switched with motherboard or chips meant for Anycall M110S ...anyway solutions for IMEI issues are mentioned on My Android Solutions, link below
Click to expand...
Click to collapse
Ok, some progress..
EDIT: It works!!!!!!
I realized I had forgotten to flash the modem.bin file with Heimdall from the repair kit. I did that now, and I am connected to the GSM network!!!
Still running Eclair 2.1, stock M110S firmware.
I think it's quite clear that this is actually the M110S, and that they took Lidroid, hacked it to make it say i9000, and are now selling these phones as if they were the international version.
Now I need to make up my mind if I go back to the shop to try to get my money back, or swapped for a real i9000... if they have one. Life with the M110S doesn't seem so nice...
Thanks again, xsenman!!!!
=============================================================
Ok, I have flashed the files and .pit from the rescue kit using Heimdall. Now I have the Eclair 2.1 version for the M110S running. I couldn't flash the movinand file, though.
In any case, the front buttons work now, as well as the correct screen orientation. Model says M110S, but baseband unknown, and still no GSM network.
Now I can't get the phone into Download mode anymore. Does the M110S use a different 3-key combo? I can't find anything about that.
EDIT: Nevermind, now it's just holding the Home button.
I was able to recover the /sdcard/backup/efs/ folder, so I have that now, hopefully with my IMEI in there...
Any suggestions to get the phone into Download mode? Or how to root it so I can try to restore IMEI? It looks like the instructions for rooting are for a later firmware than 2.1.
kbloodstone said:
I'm going to try that M110S repair kit. See if I can get back to something that can be used as a phone, first priority.
I saw the Anycall logo on my screen, but back then I didn't know that I wasn't supposed to see that on a real i9000.
I think someone in South-East Asia has obtained a bunch of M110S, and has realized that swapping the case makes them worth more money...
Click to expand...
Click to collapse
Awesome! (sort of)
Ok, now that I have become so fluent in Heimdall usage, I just flashed the latest Korean .pit I have, from the repair kit, combined with the latest GFAN ROM WF07 SP8 XDA edition. So I'm on GB 2.3.6, GSM works, WiFi works. Now that I at least have a phone again, time to consider my options about going to the shop and sticking it to the guy where the sun don't shine...
It seems I have my IMEI working, too.
Once again: xsenman, thank you!!!
kbloodstone said:
EDIT: It works!!!!!!
I realized I had forgotten to flash the modem.bin file with Heimdall from the repair kit. I did that now, and I am connected to the GSM network!!!
Still running Eclair 2.1, stock M110S firmware.
I think it's quite clear that this is actually the M110S, and that they took Lidroid, hacked it to make it say i9000, and are now selling these phones as if they were the international version.
Now I need to make up my mind if I go back to the shop to try to get my money back, or swapped for a real i9000... if they have one. Life with the M110S doesn't seem so nice...
Thanks again, xsenman!!!!
=============================================================
Ok, I have flashed the files and .pit from the rescue kit using Heimdall. Now I have the Eclair 2.1 version for the M110S running. I couldn't flash the movinand file, though.
In any case, the front buttons work now, as well as the correct screen orientation. Model says M110S, but baseband unknown, and still no GSM network.
Now I can't get the phone into Download mode anymore. Does the M110S use a different 3-key combo? I can't find anything about that.
EDIT: Nevermind, now it's just holding the Home button.
I was able to recover the /sdcard/backup/efs/ folder, so I have that now, hopefully with my IMEI in there...
Any suggestions to get the phone into Download mode? Or how to root it so I can try to restore IMEI? It looks like the instructions for rooting are for a later firmware than 2.1.
Click to expand...
Click to collapse
kbloodstone said:
Ok, now that I have become so fluent in Heimdall usage, I just flashed the latest Korean .pit I have, from the repair kit, combined with the latest GFAN ROM WF07 SP8 XDA edition. So I'm on GB 2.3.6, GSM works, WiFi works. Now that I at least have a phone again, time to consider my options about going to the shop and sticking it to the guy where the sun don't shine...
It seems I have my IMEI working, too.
Once again: xsenman, thank you!!!
Click to expand...
Click to collapse
thanks , so most likely they removed the antenna and used a i9000 back cover to make it look like the i9000...anyway everything with regards to the M110S can be found at PIT STOP .
well at least this would resolve the problems faced by many i9000gsmh units
Sharing my fix...
Hi,
xsenman: I have compressed all the files that I used for converting my i9000gsmh into a "proper" SHM-M110S, for stock Eclair 2.1, and for GFAN's ROM, including a small script (just one line) that flashes them with Heimdall, including working .pit files and repartitioning the phone just in case.
I want to share them, to help out whoever is stuck with one of these phones. How do you recommend that I do that?
Do you want to look at them first and then share them yourself?
On a side note: it looks like the guy that sold it to me has absolutely no clue about Android, so he is as scammed as I was. So I guess I am the proud owner of a SHM-M110S, and not a i9000 like I hoped...
Hopefully someone will get a ICS or JB kernel going for this someday...
kbloodstone said:
I want to share them, to help out whoever is stuck with one of these phones. How do you recommend that I do that?
Do you want to look at them first and then share them yourself?
Click to expand...
Click to collapse
just put the links here as I have already linked this page here
Just wondering did the M110S repair kit fail in solving this problem?
---------- Post added at 12:17 PM ---------- Previous post was at 12:06 PM ----------
the model is SHW M110S, kindly edit your Header
Oops, I'll fix the header as soon as I can.
The Repair kit helped. It had the right files in but two things made life a bit more difficult for me:
I use Linux, so I can't use Odin. I had to do the flashing with Heimdall.
At least using Heimdall, it wouldn't finish flashing the movinand file. I had to ignore that one. Luckily it all still worked.
Besides that, I had to look at the Word file included, and from the screenshots figure out what was happening. I combined all three steps in one go, flashing directly the latest files. I put all the files of step 1 in a folder. Then I overwrote those files with the files from step 2, and then with the files from step 3. I made sure to use the .pit file that was used last (although it seems only in the first step the Repair kit was repartitioning the phone).
Does it make sense?
xsenman said:
just put the links here as I have already linked this page here
Just wondering did the M110S repair kit fail in solving this problem?
---------- Post added at 12:17 PM ---------- Previous post was at 12:06 PM ----------
the model is SHW M110S, kindly edit your Header
Click to expand...
Click to collapse
kbloodstone said:
Does it make sense?
Click to expand...
Click to collapse
No problem, a heimdall kit would of great help too , just upload to wherever you like and I will link it to PIT STOP too.
The actual guide for using the M110S kit is available as How to Flash guide
You can prepare something like this for using heimdall an include into your upload, would surely be helpful .
Repair your "i9000gsmh"
Ok, so I have uploaded the files that I used for fixing my phone, and getting it to 2.3.6.
There are some minimal instructions in both files, and they require Heimdall installed.
http://www.4shared.com/folder/WB8Bbk3z/SHW-M110S.html
And I forgot to mention, but I also went to check my IMEI in one of those websites, and it is the IMEI of a SHW-M110S.
So... yes, what we thought: now I have a DVB receiver that I'll never use, and a phone that can't run Jelly Bean
kbloodstone said:
Ok, so I have uploaded the files that I used for fixing my phone, and getting it to 2.3.6.
There are some minimal instructions in both files, and they require Heimdall installed.
http://www.4shared.com/folder/WB8Bbk3z/SHW-M110S.html
Click to expand...
Click to collapse
kbloodstone said:
Ok, so I have uploaded the files that I used for fixing my phone, and getting it to 2.3.6.
There are some minimal instructions in both files, and they require Heimdall installed.
Click to expand...
Click to collapse
How did you get into download mode?
jamesdubit said:
How did you get into download mode?
Click to expand...
Click to collapse
press home + Power, but this model will be in download mode if you see "UPGRADE" screen, so just connect to odin3, if it connects, just flash
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
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 guys, I've a galaxy tab TIM branded (Italian)... I flashed JMK rom and now my tab freeze at boot screen... rom JMx from samfirmware flash completes successfully but tab remain on boot screen.. roto roms too... i can only switch tab to download mode.... Someone can help me???
Thanks
I suspect the original rom had a protected bootloader.
I triet to flash sam's on Vodafone tab, unfortunatelly it had locked bootloader - which I realized only after I wa stuck at bootscreen.
I ended up with a new mainboard, under warranty though
Good luck!
Sent from my GT-P1000 using XDA App
Hi
I have similar prob. Tab stuck on boot logo and my tab is still under warranty. I have a question: When you send the tab to samsung, do you tell them how it happened or just lie and say something else?
Is there any way that they can know that the tab has been rooted and flashed to another ROM?
Thx in advance
Sent from my GT-I9000 using XDA Premium App
I went to the authorized service centre myself and told them that the system was acting strange (hangs, apps closing) and that it was connected to Kies before I turned it off for the night to charge.
When the morning came it was stuck on boot logo.
I asked for quick firmware re-flash and I made clear that I have no time and I am willing to pay for it. They took it into service and told me to wait an hour. Within 35mins they reported that the re-flash did not help.
It was repaired in 3 days, with new mainboard.
I suspect that if you just send it in they migh run some diagnostics or something to determine what´s wrong and I am quite sure they will easily see your activity
I believe you might be better off with a story similar to mine.
Best of Luck!
daavt said:
I went to the authorized service centre myself and told them that the system was acting strange (hangs, apps closing) and that it was connected to Kies before I turned it off for the night to charge.
When the morning came it was stuck on boot logo.
I asked for quick firmware re-flash and I made clear that I have no time and I am willing to pay for it. They took it into service and told me to wait an hour. Within 35mins they reported that the re-flash did not help.
It was repaired in 3 days, with new mainboard.
I suspect that if you just send it in they migh run some diagnostics or something to determine what´s wrong and I am quite sure they will easily see your activity
I believe you might be better off with a story similar to mine.
Best of Luck!
Click to expand...
Click to collapse
Thank you Daavt,
I'll bring it back to Bestbuy in Calgary as soon as I go back to Canada in.......July . It means no tab for almost 2 months !!!!. I have time to come up with a big lie heheheh.
Cheers.
Isn't there a Service Centre in Morocco?
I am affraid I have to go to a Service Centre too. I also have a boot logo and no recovery
rwa66 said:
Isn't there a Service Centre in Morocco?
I am affraid I have to go to a Service Centre too. I also have a boot logo and no recovery
Click to expand...
Click to collapse
Must be. But I left the bill in Canada. So I'll wait Sorry about your tab too !!
Do you think you need a bill? Samsung gives 2 years waranty on mobile phones (in Holland at least) The Tab is only about 6(?) months on the market. If I were you I would make a call to your nearest service center and explain them your problem of your Canadian device. It wouldn't hurt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guess what! Today Gingerbread was released for the tab.
I thought that one more try couldn't hurt and i have at least a bit more life in my tab!
I can't get the system to get to work completely, but I have a recovery mode back
Problem is that after the dbdata.tar flash, recovery comes up and installs Gingerbread I guess and then it serves me the following error:
Code:
E:error in cache/recovery/sec_csc.zip
(status 7)
Installation aborted.
It is not much, but at least I have recovery mode back
I will Google for this error, maybe the solution to our problem is not far away.
Ok guys, i have made it. My Tab is running again and with the brand spanking new Gingerbread. I am soooo happy!
Ok, let me tell you what i did.
I found out that i got a lot of errors wiping cache about the system can't find volume paths. So i thought it had something to do pit partitioning.
I searched the XDA-forum about partitioning and missing volume paths and i found a thread with an answer of Rotohammer about going back to a full firmware which contained a CSC file like: P1000XWJJ4.
So I went to samfirmware.com and downloaded the right JJ4, flashed and after reboot it looked like my Tab was realy bricked, it didnt even go into download mode anymore.
At that moment i hoped it was an empty battery and I put the Tab on the charger for an hour and i could get into download mode.
I flashed Gingerbread, et voila! A smooth working Tab again.
I really hope this method will work for you too guys!
Let me know the outcome.
rwa66 said:
Guess what! Today Gingerbread was released for the tab.
I thought that one more try couldn't hurt and i have at least a bit more life in my tab!
I can't get the system to get to work completely, but I have a recovery mode back
Problem is that after the dbdata.tar flash, recovery comes up and installs Gingerbread I guess and then it serves me the following error:
Code:
E:error in cache/recovery/sec_csc.zip
(status 7)
Installation aborted.
It is not much, but at least I have recovery mode back
I will Google for this error, maybe the solution to our problem is not far away.
Click to expand...
Click to collapse
I have the exact same prob. But as you said, at least the recovery mode is back. If you find any solution please do share
tupo05 said:
If you find any solution please do share
Click to expand...
Click to collapse
I did, 1 post above you:
Flash JJ4 firmware (this firmware has still all files, including CSC, instead of the firmwares with the hidden partitions)
Then install Gingerbread (or maybe any other newer firmware will work)
My Tab is alive and kicking again
rwa66 said:
I did, 1 post above you:
Flash JJ4 firmware (this firmware has still all files, including CSC, instead of the firmwares with the hidden partitions)
Then install Gingerbread (or maybe any other newer firmware will work)
My Tab is alive and kicking again
Click to expand...
Click to collapse
Hi man,
I followed the steps above and when I flash JJ4, the tab gets stuck on boot and no recovery is available. Than when I flash Gingerbread, same error occurs
(E: Error in /cache/recovery/sec_csc.zip (status 7)
Installation aborted
Any idea ?
Thanks in advance
Did you also flash the CSC file from P1000XWJJ4 (samfirmware.com)?
That should make a brand new CSC on your tab and should not give you an error anymore.
You could try flashing just the CSC again, without partition.
rwa66 said:
Did you also flash the CSC file from P1000XWJJ4 (samfirmware.com)?
That should make a brand new CSC on your tab and should not give you an error anymore.
You could try flashing just the CSC again, without partition.
Click to expand...
Click to collapse
Flashing the CSC file only without partition give me an error:
E:signature verification failed
Installation aborted
I'll try to flash another CSC to see hehehe
rwa66 said:
Did you also flash the CSC file from P1000XWJJ4 (samfirmware.com)?
That should make a brand new CSC on your tab and should not give you an error anymore.
You could try flashing just the CSC again, without partition.
Click to expand...
Click to collapse
rwa66, you're DA MAN. I was using the wrong JJ4. And my first thank you in this forum goes to YOU.
Thanks again for helping me.
Very good to hear my friend. I am glad you're back in business
And thanks for the thanks, which is also my first
I think JJ4 is a complete firmware whilst all firmwares we used are just updates.
So the Tab never received a good CSC. I think i will keep this JJ4 in a safe place
my first error:
"E: failed to mount /efs (invalid argument)
Cache wipe failed.
..
..
your storage not prepared yet... please use UI meno for format...
copy application failed...
"
And try topic 11.
I got the same error, but when did the process in topic 11,
99% when it was not completed and no error showed.
stopped in MOVENAND item.
My tab is a verizon cdma sch-i800.
Can someone help me?
sorry for my english. google translator.
rwa66 said:
Ok guys, i have made it. My Tab is running again and with the brand spanking new Gingerbread. I am soooo happy!
Ok, let me tell you what i did.
I found out that i got a lot of errors wiping cache about the system can't find volume paths. So i thought it had something to do pit partitioning.
I searched the XDA-forum about partitioning and missing volume paths and i found a thread with an answer of Rotohammer about going back to a full firmware which contained a CSC file like: P1000XWJJ4.
So I went to samfirmware.com and downloaded the right JJ4, flashed and after reboot it looked like my Tab was realy bricked, it didnt even go into download mode anymore.
At that moment i hoped it was an empty battery and I put the Tab on the charger for an hour and i could get into download mode.
I flashed Gingerbread, et voila! A smooth working Tab again.
I really hope this method will work for you too guys!
Let me know the outcome.
Click to expand...
Click to collapse
Thanks man you saved my day ,
btw , with this PIT P1_20100909.pit phone will work normally and no need to flash any other firmware ,,
BR
During Overcome gold installation after I pressed 'start' button of odin1.7, on the 'message' dialog box showed 'factoryfs.rfs' about 10 minutes. I closed the odin and reopen it. But it cannot flashed the SGT again .. I shut down SGT. Now, I have a SGT w Blackcsreen. It does not boot up or charge..
Any help?
http://forum.xda-developers.com/showthread.php?t=1133590
take a look at this thread , if nothing helped you , then my advice is to sent it to samsung service , i think its hard brick , sorry about your lose
what is your tab model ? and what you flashed overcome over ?
MyTab model number is P1000. It callled Euro Tab, I think..
Before overcome I did not flash anything. Stock froyo (2.2.1) flashed on tab, because I just bought yesterday
I think I'll sent it to samsung service...
dec_chaos said:
MyTab model number is P1000. It callled Euro Tab, I think..
Before overcome I did not flash anything. Stock froyo (2.2.1) flashed on tab, because I just bought yesterday
I think I'll sent it to samsung service...
Click to expand...
Click to collapse
did you patch , the "bootloader" before you flashed overcome stock safe ? because their stock safe contain their kernel , and easily you can't flash any non official rom\kernel on froyo until you patch the bootloader
that is why odin failed and your tab got hard bricked
Edit : did you check the thread i gave you in my previous post ?
check the only solution for hard brick , if it didn't work for you , my advice is to send it to the nearest samsung service and tell them i woke up found it like this
the best thing you can every say
1st lesson with ODIN, once you press start you DON'T stop it.
Before you flash with ODIN you check to see if your bootloaders are locked with app from here - http://forum.xda-developers.com/showthread.php?t=888071
I believe you may have had locked bootloaders causing you to get a brick...
Wouldn't mention ODIN when you take back though, just say updating the firmware and let them fill in the gaps...
ultramag69 said:
just say updating the firmware and let them fill in the gaps...
Click to expand...
Click to collapse
+1
that was Professional Saying
Thanks for all replies.
@ultramag69 You are probably right. I install the SGT-bootloaderpatch.apk But I don't remember whether I pathed bootloaders.
I have handed in The SGT to SAMSUNG service centre.
And now I'm praying...
If they don't take care of it for you please keep me in mind as I can correct this for you... PM sent.
Hello everybody
Due to some demand and request, I've decided to adapt my guide to the I9100G. It deserves some love too!
This is a guide dedicated to noobs, so if you're not one, I would advise to stop reading now! (altough feedback would be great! )
Yes, there have been quite a few threads about fixing a soft brick. But what I'm writting now is another solution to a different kind of problem : unflashable GSII (which also works with a soft brick of course ), which is a soft brick and a corrupted NAND rw (read/write) function.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, regarding NAND rw (NAND's read and write function being the corruption) it means that it is an issue deeper than a soft brick.
It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
BUT UNFORTUNATELY, this guide will not be able to fix a NAND r/w corruption, due to tyhe fact that I do not have either the .PIT, the bootloader or the kernel, I only have a stock ROM, which will only fix a soft brick.
As soon as I get my laptop back from RMA (this Pentium Dual core I'm using right now isn't trustworthy), I'll extract the zImage and sbl.bin from each ROM, zip it, upload it, and add the rest of the guide.
UPDATE 02/05/2012
GOOD NEWS EVERYONE!Thanks to maui75, I have the .PIT and the gingerbread bootloader! When my laptop arrives from RMA, I'll download and unzip all the packages in this thread, add the .PIT, zip, upload again, and add the rest of the guide! __________________________________________________
VERY IMPORTANT ANNOUNCEMENT
I would like to first apologize for my absence. My past months have been super busy, and they don't seem to be ending anytime soon. And "anytime soon" meaning in a couple of years. And I'm actually glad that this is happening, since I've been working pretty hard to achieve the state I'm in.
This thread has evolved into something I've never imagined. Only because of YOU guys, we managed to turn a normal thread into a pretty popular and well used Guide, and it made me so happy and joyous of being apart of the XDA community. I feel proud in being a XDA nut. This whole success is just because of YOU guys.
As painful as it is to say this... I believe that I will be dropping support on this thread after the New Year, because a) I lost my Galaxy S2 in Paris in a taxi with no hope of getting it back when I went there 3 weeks ago and b) I'm probably getting a Galaxy Note 2 in the New Year, so this thread will be most likely ported and maintained over at the Note 2 forums.
I'm extremely sorry it has come this way, and I hope you guys will understand. In the following days I'll be updating the files to their latest versions, and will try to find new bootloaders and kernels, but without sources, I'm unable to do so. I'll update whatever I'll be able to
Regards and thanks to all of you that have supported me,
Rafael K.
Click to expand...
Click to collapse
________________________________________________
IMPORTANT ANNOUNCEMENT #2
Please welcome neerajganga, your new thread maintainer (along with me)! He has been of great help, so I think he deserves this kind of announcement!________________________________________________
IF YOU ONLY HAVE A BOOTLOOP
Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE
__________________________________________________
Let's start with the basic files, downloads and requirements
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary ROM (they are Gingerbread 2.3.6) : Africa (Iraq), Asia (Malaysia), Europe (Open Austria), Middle East (Saudi Arabia). (password is samfirmware.com)
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
And that is it! Let's get down to business
__________________________________________________
If your GSII has the folowing symptoms :
Bootloop
Stuck on GSII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Enters Download mode but does NOT enter recovery mode (usually means a NAND rw corruption)
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
__________________________________________________
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch
But where are the files going, you say?
.tar -> PDA
__________________________________________________
Recovering a soft bricked phone
1) Grab the Recovery Package, and put the file in its place.
2) Turn off your phone. Enter Download mode by presing Vol. Up + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9, or other numbers)
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!
You deserve some cake afterwards, and some rest
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to Intratech and Sammobile, for his amazing gallery of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.
Very good and useful guide. Keep up the good work!
Much simpler
Yesterday i faced a similar problem , i just flashed a kernel and got rid of this problem...
Simple and easy.
I even fixed my Galaxy S2 which was stuck in "Phone-Exclamation-Computer" icon mode. Couldnt even get into Recovery or Download mode.
My phone showed up on Odin so i just flashed it with the stock firmware.
Thanks for the guide!!
When I tried to do a small update via OTA, it got stuck on the Bootlogo.. Did a factory reset, tried to flash via ODIN, but never worked.. Odin just says Checking CS and then closes. It doesn't flash the OS.. Help guys.
WolVish said:
When I tried to do a small update via OTA, it got stuck on the Bootlogo.. Did a factory reset, tried to flash via ODIN, but never worked.. Odin just says Checking CS and then closes. It doesn't flash the OS.. Help guys.
Click to expand...
Click to collapse
What version of ODIN are you using? What fw are you flashing? Have you tried changing cables/use ports?
madbutnotstupid said:
I even fixed my Galaxy S2 which was stuck in "Phone-Exclamation-Computer" icon mode. Couldnt even get into Recovery or Download mode.
My phone showed up on Odin so i just flashed it with the stock firmware.
Thanks for the guide!!
Click to expand...
Click to collapse
No problem!
ashwinsrihari said:
Yesterday i faced a similar problem , i just flashed a kernel and got rid of this problem...
Click to expand...
Click to collapse
Then you just had a corrupt kernel
What version of ODIN are you using? What fw are you flashing? Have you tried changing cables/use ports?
Click to expand...
Click to collapse
The ones found in this very thread only.. Asian firmware. I tried with USB 3.0 USB 2.0 ports, but forgot to try a new USB cable.. It didn't recognise the device i think.
Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9, or other numbers)
Click to expand...
Click to collapse
It didn't happen with my I9100G. Maybe the cable is the culprit.
WolVish said:
The ones found in this very thread only.. Asian firmware. I tried with USB 3.0 USB 2.0 ports, but forgot to try a new USB cable.. It didn't recognise the device i think.
It didn't happen with my I9100G. Maybe the cable is the culprit.
Click to expand...
Click to collapse
Either is the cable, or the USB drivers
TBH i prefer using Toxic Rom to get out of a pickle.
triobot said:
TBH i prefer using Toxic Rom to get out of a pickle.
Click to expand...
Click to collapse
this is for i9100G..not i9100..hihi
triobot said:
TBH i prefer using Toxic Rom to get out of a pickle.
Click to expand...
Click to collapse
ODIN or not, when recovering from a soft brick, it's always better to go stock. It's safer and that can prevent discrepancies between ROMs.
Plus, that's a I9100 ROM, this is the I9100G guide
Odin 1.85 will recognize the phone if it is soft bricked too.
To be updated and have available the original firmware that i want, I verify with "checkfusdownloader". Furthermore, it is faster and easyer than Kies.
It will download the whole files to write with ODIN...
maui75 said:
Odin 1.85 will recognize the phone if it is soft bricked too.
To be updated and have available the original firmware that i want, I verify with "checkfusdownloader". Furthermore, it is faster and easyer than Kies.
It will download the whole files to write with ODIN...
Click to expand...
Click to collapse
Interesting... But does it include a 3-file package, or is it only a 1-file package?
Phistachio said:
Interesting... But does it include a 3-file package, or is it only a 1-file package?
Click to expand...
Click to collapse
...In my case it is only one file .tar.md5
maui75 said:
...In my case it is only one file .tar.md5
Click to expand...
Click to collapse
There we go It's better to flash a 3 part, since sometimes in a soft brick, a single files doesn't pass, but a 3 file pack will.
Phistachio said:
There we go It's better to flash a 3 part, since sometimes in a soft brick, a single files doesn't pass, but a 3 file pack will.
Click to expand...
Click to collapse
I agree with you and in special way for soft brick due to the wrong firmware.
I wish to add the link for all the file ( PIT, PDA, MODEM, CSC, BOOTLOADER, APBOOT) of i9100G CHN KH4, it is a little old but good to repair the chn version.
ht * tp:/ /115.com/file/dnecfzp4
To download the file push the green button... in the begin I had some problem to find all the file for the chn version.... hope will be helpfull
maui75 said:
I agree with you and in special way for soft brick due to the wrong firmware.
I wish to add the link for all the file ( PIT, PDA, MODEM, CSC, BOOTLOADER, APBOOT) of i9100G CHN KH4, it is a little old but good to repair the chn version.
ht * tp:/ /115.com/file/dnecfzp4
To download the file push the green button... in the begin I had some problem to find all the file for the chn version.... hope will be helpfull
Click to expand...
Click to collapse
Oh wow, thanks a LOT! I was looking for the .PIT and the bootloader since always! I'll download the file and upload it to mediafire to facilitate (but that'll only be up when I get home, I'm at school at the moment )
Also, when my laptop arrives, I'll download each package, and add the .PIT so people can have a full recovery (the bootloader will be in a separate download)
Phistachio said:
Oh wow, thanks a LOT! I was looking for the .PIT and the bootloader since always! I'll download the file and upload it to mediafire to facilitate (but that'll only be up when I get home, I'm at school at the moment )
Also, when my laptop arrives, I'll download each package, and add the .PIT so people can have a full recovery (the bootloader will be in a separate download)
Click to expand...
Click to collapse
Great idea...I can not do it, here mediafire does not work
In the begin I did not know the difference from the 9100G and the 9100 so I flashed the wrong rom to root I drived crazy to find the link
Now will be better
maui75 said:
Great idea...I can not do it, here mediafire does not work
In the begin I did not know the difference from the 9100G and the 9100 so I flashed the wrong rom to root I drived crazy to find the link
Now will be better
Click to expand...
Click to collapse
No problem! You already helped me like so much! Thanks a lot again!
It will be better indeed
i9100G ROMS seem to all have different pit files
I ran across a problem while trying to flash the latest ROM from India on a phone bought in China, it always failed at "MSO" and was never recoverable until I flashed back the Chinese ROM, it seems the Indian ROM pack had some different files the Chinese ROM did not have. In short the partitioning appears to be different between some of the ROMS. So is it possible to find the pit files that are connected to each ROM?
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.