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?
Related
I haven't been able to update this post in quite awhile due to travels abroad. And since its is still being used as a reference, I want to make sure the information is valid. I've removed links to the T959UVJE8 firmware, as it was causing issues for people. Included is a more recent firmware package T959UVJFD.
Please take note: I am not responsible for any damage caused to your device.
Using Oden, you'll first need to put your device into Download Mode. From a device still on Vibrant firmware, you'll need to hold down the "volume down" button while booting. If you've been playing with I9000 firmware's like I was, your volume has been reversed and the reverse applies to you, "up volume". If you still can't enter download mode, you may want to try holding down the volume key + the power button. Plugging in your USB cable may also aid your efforts to enter download mode.
Once in download mode, use the attached files below to flash your device. I'll give you a quick run through of Odin, but for detailed information I'd suggest this YouTube video. Keep in mind that in this video the poster is actually flashing an I9000. But the process is similar in all respects with the only difference being the key combination used to enter Download Mode.
A system wipe beforehand is recommended. If your having Market issues after flashing, this is more than likely the culprit.
1. Extract Oden, and run as Administrator.
2. Extract the .pit file, click the PIT button in Oden, and load the file you just extracted.
3. Updated... Download the T959UVJFD.tar firmware image to the same directory as your PIT file. This will be selected as your "PDA" file.
4. Under Options, be sure the following three boxes are checked. Re-Partition, Auto Reboot, and F. Reset Time. Update... also check "Phone EFS Clear" and "Phone Bootloader Update".
5. Put your device in download mode and plug it in. Specific COM ports are unimportant at this point, if you see the "ID:COM" field turn yellow, your in business. If you receive a message that says driver failed to install, or couldn't be found, extract and install the attached drivers file, and direct "Windows Hardware Manager" to search for the driver in the extracted drivers folder. I've seen better results using this manual approach, versus the installer.
6. Now press start, sit back, and be patient. In my case, the install only took around a minute.
After installation has finished your sent to recovery, just hit the power button, and have patience. Remember that your first boot can take a few minutes, so no pushing buttons, unplugging, or battery removals.
FYI; I stopped and rebooted my phone at every sequence during this flash process, and I never bricked. Not necessarily intentionally, but I am very rough on my toys. Even after freezing or stalling partway through cache setup, factoryfs, you name it, no paper weight. This phone is stout!
Required Tools:
Odin3 v1.81...
Odin Firmware Flashing Tool, Odin3 Version 1.81
Megaupload, Odin Firmware Flashing Tool, Odin3 Version 1.81
Multiupload Mirrors, Odin Firmware Flashing Tool, Odin3 Version 1.81
Pit file, as mentioned in other threads, the 512 seems to work best...
512 PIT File
Multiupload Mirrors, 512 PIT File
x86 & x64 drivers directly from Samsung:
Windows x86 & x64 Drivers Directly From Samsung
Windows x86 & x64 Drivers Directly From Samsung, Local Attachment
Windows x86 & x64 Drivers Directly From Samsung, Multiupload Mirror
Windows x86 & x64 Drivers Directly From Samsung, Megaupload Mirror
Samsung Installable Drivers, located on Softpedia. I'd recommend manually installing your drivers. My results using the installer weren't great...
Windows x64 Drivers on Softpedia
Windows x86 Drivers on Softpedia
(Update)T959UVJFD Firmwares, ODIN Flashable:
Megaupload, T959UVJFD Stock Vibrant, Odin Flashable... (PDA)
Depositfiles Mirror, T959UVJFD Stock Vibrant, Odin Flashable... (PDA)
(Update) Kies Mini Installer Method:
An alternate method is to use Samsungs Kies Mini Installer. Using this method you'll actually be updating your device to the latest Froyo 2.3 Firmware directly from Samsung. An internet connection is required, but driver installation, as well as firmware download and flashing, are all performed automatically. This method of Original restoration should be absolutely noob proof.
Samsungs Kies Mini Installer, Direct Download
Samsungs Kies Mini Installer, Multiupload Mirrors
Thanks for this. But this link is not working.
These are the drivers I used with all the alien firmwares I've installed. There's an installer included, but I didn't use it. I'm just leaving everything I've been using intact...
Megaupload
EDIT: my bad working now.
The links are all valid as of this reply. If you've never downloaded from Megaupload, I'm guessing your not waiting for the timer and hitting another link. Type the captcha, click the button, pages reloads, look down a tad and you'll see a count down.
Yep.
I got it. It was a browser issue.
But, good post. for those who want to revert.
Which firmware seems best for the vibrant atm? i know the other galaxy's have diff buttons thats why i dont want to flash
Stupid newbie question: What's the difference between this firmware, and the dump by wesgarner (T959UVJFD)?
I really haven't dug into this thing deep enough to tell you all the differences. I used this version because it was all I could find in terms of a flash-able firmware. Something I have noticed is seems to be a good deal less bloatware.
I'll say this, after wiping and re flashing with this version, I'm really quite happy with the results. Its faster and smoother than when I first got it, and I've got my navigation button back. As far as I can tell, everything works, and well at that.
Does this firmware included the lag fix in this thread http://forum.xda-developers.com/showthread.php?t=727279
I restore back some backup apks from my G1 (no data, only the app) and the phone is lagging terrible in some applications and normal in others. I am applying your firmware as I write but wanted to know if I need to apply the fix in that thread after getting root again.
thanks in advance
No I haven't incorporated anything that would, or could, be considered a hack. I really am trying to keep this thing stock. The intent is to have a factory image to flash to if we ever need warranty work.
@ ellopr More likely than not, your phone is simply in need of a system wipe. The fix your using is dangerous, and probably not even needed in your case.
both my wife and I have vibrants.mine is rooted, hers is not. Is there anything I could do to get the base firmware off it minus her user data (privacy issue) without factory resetting her phone? (Since she now has hers set up the way she likes it, and I don't want to catch hell for making her start over)
I got it working now, thanks.
firmware info
Is this firmware flashable on samsung captivate? Since i will be using the phone on tmobile after unlocking it.
This process worked for me after I had destroyed the bootloader and recovery image.
Phone would boot to the phone--<!>--PC screen (even with volumeDn+home+power and volumeUp+home+power). Holding down volumeUp+volumeDn then power did put me into download mode.
I had to rerun odin3 a couple times to get it to work though. Patience is key (which is pretty hard for me)
I couldn't tell you what else this firmware would work on. All I've got is my trusty G1 and this Stout Beast of a phone. If you'd really like to know, there's probably one sure way of doing it. Emulators are for.. umm.... Girls, yeah that it.
So over all, my phones been running great. No dropped calls, no missed texts, the call quality is amazing, speaker and headset. Now if it looked just a tad less like an IPhone, but then no ones perfect.
As it stands, I've been running this firmware for a few days now. And since then I've been striping the old girl down one service at a time. Tmobile Sync was the biggest nuisance by far. Its not just an annoyance on this firmware, it seems to be a nuisance on every phone its installed on. I use my phone for work, and I've got well over 450 contacts. That stupid app never stopped running. Not only that, but it monitors and synchronizes contacts between, your SIM, internal phone storage, Gmail, and tmobile. Needless to say, that was only the first of many Tmobile apps to hit the chopping block.
So here are the numbers... Starting apps 246, more than the dump from T959UVJFD, at 239. I got that down to 207, but I like the active desktop, and I've got to have a calendar. So currently 213 apps. My memory available stands at just about 130mb + 65MB available in 24 services, before I started ShootMe that is. Such weird numbers. The way the internal and external memory interacts is definitely going to be a major headache down the road.
My current memory usage...
{
"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"
}
Lock Screen....
I use a lightly Modified LauncherPro, so smooth...
What few apps I have left...
The rest of the apps, yeah I pretty much got rid of everything...
Backup ups don't seem to like this phone very much. "System app Backupper" has always been a favorite, but now instead of a folder with all the apps in it, all I get is an empty folder. Titanium did a partial job as well. Two extremely useful tools for this type of modding are Root Explorer, and Root Manager. And if your wondering about clockworks, I did try flashing a few "generic" so to speak recovery's. To no avail, and during the week I'm to busy to hack, probe, and tinker. But its a very useful program when it comes to one click permissions fixes. I'd much rather see someone port Amon Ra to this thing.
I'm really looking forward to a newer release. This phones got some great potential. I hope you enjoyed picture time.
Woo..
this is good for reference..i deleted some system apps trying to reinstall..this thing saved me...good work!!
Can someone post a /system dump of this. Its slightly different than the t-mo shipped rom.
Anyone also have the issue of T-Mobile being in account settings with no way to remove it?
Is there any way of having the phone reflashed to the actual factory image?
Can anyone that flashed this also provide a df -h printout?
I click start and it says:
<OSM> All threads completed. (succeed 0 / failed 0)
and thats it.... any suggestions?
drivers..
junkdruggler said:
I click start and it says:
<OSM> All threads completed. (succeed 0 / failed 0)
and thats it.... any suggestions?
Click to expand...
Click to collapse
Make sure u have the samsung drivers installed..if u do...just unplug and replug the phone in with odin open..u should see a com port open up with a number..ie 12 was mine..hope this helps
Ive uninstalled and reinstalled the drivers... but still says usb device not recognized when I plug it in...
adb and all that work fine... am i missing a different driver somewhere just for DL mode?
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
I have done hours of researching and this isn't my first time i bricked a phone so I kind off have some experince fixing the phone but this seems harder than before.
I first tired to flash a kernel through odin on my captivate because i wanted to try out cyanogen mod but somehow the kernel had failed on me. When i tried to restart my phone, I got the phone---!---pc logo.
So i did some research on how to get the phone out of the soft brick. First thing I did was trying to get into recovery mode with the 3 buttons, but didnt work out. After that I tried to get into download mode and it worked. My first thought was too use odin and reflash, and that is what i did. Now the problem is, I had put the correct pit file and stock rom, because I had reflashed using these two same files before, but the thing is, it gets stuck on "set partition". So I did everything from, trying on different computers to changing usb cables to using different versions of odin and finally to taking out the sim card and sd card and taking out and placing the phones battery back in. And i had everything checked too so that wasn't the problem. The following were checked: Auto Reboot, Check Re-Partition and F.Reset Time.
If anyone knows the solution can you please help me out, thank you in advance!
When you check repartition, you need to load a pit file in the pit slot/tab for Odin. You have two options.
1) Flash froyo stock(kb2), if you don't want/need Gingerbread Bootloaders. The Heimdall package from Adam Outler is an easy 1 click solution.
2) Flash KF1 if you need GB bootloaders. This will also fix ant previous 3 button combo problem you may have. Use the package with a pit file and bootloaders.
It also sounds like you may need ajig to get into download mode, but if you follow the Captivate sig link below, you should be able to find everything you need to get going.
Thank you !
Thanks a lot mrhaley30705 ! I have gone through of some guides and done more research about these two, and I was thinking of flashing kb2 on to my phone but I'm really worried if it might brick my phone, because the captivate I have is the rogers one not the ATT&T one.
I just had a few questions like, before I do the Heimdall One-Click, is it required to install the Zadig file ? because it had came up before I opened up the Heimdall One Click program. I think i had used the Heimdall One-Click before (the video that is posted on youtube) by outleradam, but the thing was, it wasn't recognizing my phone. So I'm guessing it has something to do with Zadig file, because I made sure I ran it as Administrator also so I'm kinda lost.
My other question was, the consequences, if this program would not work for me, would it hard brick my phone? I really want to make sure I go ahead with it.
And my last question is, if I were to go ahead with this, it said on the forum I would have to reset my APN settings, so would that be applying another software to the phone or can i configure that manual ?
And Thanks again for all your help !
If you want the Canadian firmware, search for TRusselo's stock threads. He has a full set of Canadian firmware.
Anytime you flash bootloaders there is a chance of hard bricking your phone, either from an interruption in communication between your phone and computer (think power outage or bad cable) or accidentally mismatching bootloaders (think the old 3 button fix on top of GB bootloaders). Just follow all of the precautions you can when flashing bootloaders.
APN editing is done manually.
Oh alright I got how put the APN information, thank you.
And oh okay, that makes more senses.
And for the Canadian firmwares, that's what I pretty much did with Odin, I took his stock firmware and tried to flash it with Odin but wasn't passing the "set partition" part like I mentioned before. I followed his instructions too. So, that's why I'm a bit confused now, because I'm guessing if Odin doesn't work then I would have to use the Kb2 link that is posted on your Sig. Do you have any suggestions maybe ?
The canadian version of the captivate will flash the US verson, it just changes your boot screen and kernel splash to an att one. I would flash the KB2, then if you absolutley had to have the canadian version, flash it.
Thank you !
Thanks a lot once again ! and I will give it a try and let you know how it goes !
Maybe try NOT checking re-partition. This sometimes can cause a problem, in fact most tutorials i have seen always say DO NOT check re-partition. It's worth a try
i was installing the ics repack zclp1 with pc odin but it stuck on data.img
what should i do?
can i remove the cable?
please help ...
you can restart but dont reboot phone any you turn it once the bootloader is flashed you will be safe you can also check the link in my sig
antiguangenius said:
you can restart but dont reboot phone any you turn it once the bootloader is flashed you will be safe you can also check the link in my sig
Click to expand...
Click to collapse
Please stop offering your 'bootloader' advice to guys having problems after flashing Angelom's ICS kernel.
Bootloader is not going to help because their problem is corrupted data partition. Nothing to do with the bootloader whatsoever.
Ok
chasmodo said:
Please stop offering your 'bootloader' advice to guys having problems after flashing Angelom's ICS kernel.
Bootloader is not going to help because their problem is corrupted data partition. Nothing to do with the bootloader whatsoever.
Click to expand...
Click to collapse
ummm read properly before you respond
I SAID HE CAN RESTART THE FLASH BECAUSE THE BOOTLOADER IS FLASHED FIRST SO HE IS SAFE.
i never told him to flash his bootloader obvoiusly he is try to root or install ics so a smart guy will click on the rooted or rom link for help....
PS
look before you leap.....
Let me guess re-partition was on in odin?
If yes u need to call samsung.
avetny said:
Let me guess re-partition was on in odin?
If yes u need to call samsung.
Click to expand...
Click to collapse
you dont need to call samsung.... i have use the repartition few times..... sounds like he has a bad flash chip....
antiguangenius said:
you dont need to call samsung.... i have use the repartition few times..... sounds like he has a bad flash chip....
Click to expand...
Click to collapse
so whats the solution mate? we have tried everything. pit, odin, cwm, kernel flash, it gets stuck either at boot n700 logo or at factoryfs or data.im on odin
antiguangenius said:
ummm read properly before you respond
I SAID HE CAN RESTART THE FLASH BECAUSE THE BOOTLOADER IS FLASHED FIRST SO HE IS SAFE.
i never told him to flash his bootloader obvoiusly he is try to root or install ics so a smart guy will click on the rooted or rom link for help....
PS
look before you leap.....
Click to expand...
Click to collapse
No, you read properly before you respond, and even more properly before dishing out any more useless advice to people with a very specific problem, i.e. bricked phones after flashing Angelom ICS kernel v1.2.
Read this, for instance:
http://forum.xda-developers.com/showpost.php?p=23256341&postcount=405
and this:
http://forum.xda-developers.com/showpost.php?p=23256829&postcount=406
I'll say no more about it.
androidindian said:
so whats the solution mate? we have tried everything. pit, odin, cwm, kernel flash, it gets stuck either at boot n700 logo or at factoryfs or data.im on odin
Click to expand...
Click to collapse
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
I have put some thought into in.... i could be wrong or sound like an idiot to say this but it seem like the boot block for the main flash chip it been corrupted with the wrong header....
for eg. most note is 16gb, lets say with a A14BC ok check sum.... the rom seem to be interfering with that checksum or flash header... so when the odin which has only a specific command to modify that flash chip look for the checksum to proceed.. its not getting it so it waits and waits and waits... which is what its officially programmed to do.. i'm guessing that these it a specific switch odin needs to start with to over ride its normal procedure and reset flash to its original state or there's a higher level program to do this.... these flash chips was programmed in the phone not out so there has to be a way to revive them... its electronics...... it remind me of the boot legged usb flash cards, you will buy one at 32gb months later it wont work properly or at all.
but nevertheless most people getting the N7000 bootlogo and nothing after its just like a pc with a bad harddrive the phone is looking for the Unified Extensible Firmware Interface (UEFI) which is a specification that defines a software interface between an operating system and platform firmware.. its not that because odin can't load it... odin cant load if for many reason which can be the flash chip has been corrupted so the full size cant be read or the checksum mismatched... only fix i believe it there is if odin has a special switch which ignore checksums or it had a grandfather program we don't have access to....
bottom line is the flash chip aka hard drive from the note is not formatted and/or partitioned so its not accepting the firmware aka the os.......
we need the chinese that made these thing to say whats missing.... or a samsung tech so leak something...
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
antiguangenius said:
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
Click to expand...
Click to collapse
Those are some really interesting thoughts.
And this chap here http://forum.xda-developers.com/showpost.php?p=23305688&postcount=1
Did something similar and succeeded, though the root cause was different it seems to be matching with your analysis!!
antiguangenius said:
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
I have put some thought into in.... i could be wrong or sound like an idiot to say this but it seem like the boot block for the main flash chip it been corrupted with the wrong header....
for eg. most note is 16gb, lets say with a A14BC ok check sum.... the rom seem to be interfering with that checksum or flash header... so when the odin which has only a specific command to modify that flash chip look for the checksum to proceed.. its not getting it so it waits and waits and waits... which is what its officially programmed to do.. i'm guessing that these it a specific switch odin needs to start with to over ride its normal procedure and reset flash to its original state or there's a higher level program to do this.... these flash chips was programmed in the phone not out so there has to be a way to revive them... its electronics...... it remind me of the boot legged usb flash cards, you will buy one at 32gb months later it wont work properly or at all.
but nevertheless most people getting the N7000 bootlogo and nothing after its just like a pc with a bad harddrive the phone is looking for the Unified Extensible Firmware Interface (UEFI) which is a specification that defines a software interface between an operating system and platform firmware.. its not that because odin can't load it... odin cant load if for many reason which can be the flash chip has been corrupted so the full size cant be read or the checksum mismatched... only fix i believe it there is if odin has a special switch which ignore checksums or it had a grandfather program we don't have access to....
bottom line is the flash chip aka hard drive from the note is not formatted and/or partitioned so its not accepting the firmware aka the os.......
we need the chinese that made these thing to say whats missing.... or a samsung tech so leak something...
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
Click to expand...
Click to collapse
makes a lot of sense.
so do you think its an issue in the chinese i9220 kernel itself? or was it an issue created with angeloms kernel of i9220?
androidindian said:
makes a lot of sense.
so do you think its an issue in the chinese i9220 kernel itself? or was it an issue created with angeloms kernel of i9220?
Click to expand...
Click to collapse
I'm actually running chriskelo rom, i did flash the chinese ics first then the chriskelo... my phone works fine.. before the chriskelo i did flash team ics but was getting massive FC so i tried to flash back the GB but it would just stuck at modem which naturally comes after bootloader.... so what i did was download a GB Modem for recovery then flash it then reflash rocket rom v22 all in recovery and my phone was back up and running in a matter of 20 mins
as response to the i9220 and N7000 differences there must be some internal differences which only samsung knows cant just be language and region thats controlled by the csc...
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC.
china have many different mobile rules that the rest of the world so its more than just the firmware.....
I just made a thought.... can someone try to download a firmware that has all the pieces some can be found in my guide in my sig and flash the phone in the reverse order... that is flash only the CSC file then the phone file then the PDA then lastly the bootloader.... can someone please try them individually... and report back...
antiguangenius said:
I'm actually running chriskelo rom, i did flash the chinese ics first then the chriskelo... my phone works fine.. before the chriskelo i did flash team ics but was getting massive FC so i tried to flash back the GB but it would just stuck at modem which naturally comes after bootloader.... so what i did was download a GB Modem for recovery then flash it then reflash rocket rom v22 all in recovery and my phone was back up and running in a matter of 20 mins
as response to the i9220 and N7000 differences there must be some internal differences which only samsung knows cant just be language and region thats controlled by the csc...
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC.
china have many different mobile rules that the rest of the world so its more than just the firmware.....
I just made a thought.... can someone try to download a firmware that has all the pieces some can be found in my guide in my sig and flash the phone in the reverse order... that is flash only the CSC file then the phone file then the PDA then lastly the bootloader.... can someone please try them individually... and report back...
Click to expand...
Click to collapse
yes, before sending my phone to samsung yesterday, I did try that with KL8 firmware. starting from the kernel, bootloader, csc, ums, and at the end code/pda, but again stuck at factoryfs.img
http://forum.xda-developers.com/showthread.php?t=1532830 >> just saw this thread, makes me wonder.. if the chinese leak has something to do with this.
but when i was on cf repack, i could easily flash another kernel like angelom or another rom, only after angelom issues started.
were you able to flash via odin a stock rom being on cf kernel ics?
androidindian said:
yes, before sending my phone to samsung yesterday, I did try that with KL8 firmware. starting from the kernel, bootloader, csc, ums, and at the end code/pda, but again stuck at factoryfs.img
http://forum.xda-developers.com/showthread.php?t=1532830 >> just saw this thread, makes me wonder.. if the chinese leak has something to do with this.
but when i was on cf repack, i could easily flash another kernel like angelom or another rom, only after angelom issues started.
were you able to flash via odin a stock rom being on cf kernel ics?
Click to expand...
Click to collapse
I didnt still on ICS but I did went back to GB once no issue,,, but all this ICS issues is hurting my head.... I'm going back to GB NOW... I'll report in a few mins....
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.