I have a SIM free SM-T815C (Hong Kong) running stock Lollipop, and I want upgrade to MM. But the Hong Kong region still doesn't have an updated firmware. However, there are several Europeans SIM Free stock MM firmwares already available for the SM-T815.
Does anyone know the difference between my SM-T815C and a SM-T815? Maybe LTE bands and other regional nomenclature, but the hardware is certainly exactly the same. So I would think a SIM FREE (non-carrier specific) SM-T815C ROM should work fine on my SM-T815. I just worry Ill fry my new S2 Tab instantly..
In the past on my original Galaxy Tab 7 (sigh.. the best Tab ever..), I remember getting a stock German ROM with Gingerbread update that installed perfectly.. and that's how I used the Tab for almost 2 years. Still have it, still works.. just the battery lasts about 10 minutes now, haha
VeEuzUKY said:
I have a SIM free SM-T815C (Hong Kong) running stock Lollipop, and I want upgrade to MM. But the Hong Kong region still doesn't have an updated firmware. However, there are several Europeans SIM Free stock MM firmwares already available for the SM-T815.
Does anyone know the difference between my SM-T815C and a SM-T815? Maybe LTE bands and other regional nomenclature, but the hardware is certainly exactly the same. So I would think a SIM FREE (non-carrier specific) SM-T815C ROM should work fine on my SM-T815. I just worry Ill fry my new S2 Tab instantly..
In the past on my original Galaxy Tab 7 (sigh.. the best Tab ever..), I remember getting a stock German ROM with Gingerbread update that installed perfectly.. and that's how I used the Tab for almost 2 years. Still have it, still works.. just the battery lasts about 10 minutes now, haha
Click to expand...
Click to collapse
I'm in the same situation. Any helpful advice would be greatly appreciated.
Sent from my Nexus 6P using XDA-Developers mobile app
Wondering this too! I have the SM T815C with the SIM card slot. Can I flash MM with other ones saying SMT815 without the C?
DantheDan said:
Wondering this too! I have the SM T815C with the SIM card slot. Can I flash MM with other ones saying SMT815 without the C?
Click to expand...
Click to collapse
Seems lots of people wondering about this same question. I have not found a conclusive reply yet and am still researching. Of course on true and simple leap a faith would be to simply try to flash the update directly and see what happens. Given that the hardware is between the "C" and "non-C" is basically exactly the same, I think the risk of bricking the tab is minimal. But of course it can happen. However, I doubt it. Most likely what will happen if there's a mismatch, is that the flash will be stopped automatically before it even search. The only way to check this, is to try it. I am considering to give it a try is no proper answer comes forth on this.
I can't believe I'm about to say this, but let me be the one who tries it. My Tab is already in a bad way (the screen is separated from the aluminum a bit) and I actually don't like the tablet much, so if someone needs to be the guinea pig, I'm willing. However, some help in not screwing up the test would be most appreciated. I'm not the most fluent when it comes to flashing, and especially when it comes to using Odin.
So what is the deadline for a "proper answer" coming forth? Tomorrow? The end of the weekend? A week from now? What do you two think?
Michael833 said:
I can't believe I'm about to say this, but let me be the one who tries it. My Tab is already in a bad way (the screen is separated from the aluminum a bit) and I actually don't like the tablet much, so if someone needs to be the guinea pig, I'm willing. However, some help in not screwing up the test would be most appreciated. I'm not the most fluent when it comes to flashing, and especially when it comes to using Odin.
So what is the deadline for a "proper answer" coming forth? Tomorrow? The end of the weekend? A week from now? What do you two think?
Click to expand...
Click to collapse
HI Michael833! How your screen got separated from he rest of the body? Did you drop the tab? Bummer..
Anytime you want try the flashing, we will wait your feedback. There is no pressure here, you do it on your leisure time whenever you feel like it.
As far as the flashing itself, is very straight forward. Backup the tab if you haven't done it yet and do all wipes and a fresh install. If there is any major incompatibility, probably the flashing process will be prevented automatically by itself. But I'm almost sure will go fine. Any questions, let me know
By the way, unless you warped the main frame of the tab, getting the screen back into its place should be a simple job at any Samsung service center or independent repair guy that knows what he is doing. I don't know where you are located, but here in Hong Kong there are mini repair shops everywhere that could fix that is a couple minutes
Sadly it shipped to me this way. At first, it only separated once in a while, and I could just press it back together and it would stay solidly in place for a few days or more. But, as time has gone on, the separation seems to come more frequently. I sent it to the Samsung repair center here in The Netherlands, but since it was purchased in HK, they wouldn't even touch it. I sent it back to the company I bought it from, but then they kept the tablet and wouldn't send it back to me for several months. (The company is called ValueBasket and they totally efing suck. NEVER do business with them.) I finally just got it back yesterday and I put it into a case which keeps the opening at least covered a bit. Out of sight, out of mind. Maybe I'll try to bring it to someone around here to look at.
Anyway, I tired to flash it and it didn't work, but it also didn't harm anything. I used instructions from here and below is a screenshot of what happened. After the fail, I just rebooted and all my data and apps were still there.
https://storagemadeeasy.com/files/1a6ba54367215e8ad34081e1aa61b0f3.png
Any other suggestions, or did I do something wrong?
Michael833 said:
Sadly it shipped to me this way. At first, it only separated once in a while, and I could just press it back together and it would stay solidly in place for a few days or more. But, as time has gone on, the separation seems to come more frequently. I sent it to the Samsung repair center here in The Netherlands, but since it was purchased in HK, they wouldn't even touch it. I sent it back to the company I bought it from, but then they kept the tablet and wouldn't send it back to me for several months. (The company is called ValueBasket and they totally efing suck. NEVER do business with them.) I finally just got it back yesterday and I put it into a case which keeps the opening at least covered a bit. Out of sight, out of mind. Maybe I'll try to bring it to someone around here to look at.
Anyway, I tired to flash it and it didn't work, but it also didn't harm anything. I used instructions from here and below is a screenshot of what happened. After the fail, I just rebooted and all my data and apps were still there.
https://storagemadeeasy.com/files/1a6ba54367215e8ad34081e1aa61b0f3.png
Any other suggestions, or did I do something wrong?
Click to expand...
Click to collapse
Thanks for sharing this info and for giving this a try.
Maybe the flashing halted itself because the firmware is not compatible or maybe other reason.. I am not quite sure. What Firmware exactly did you download and use for the Flashing? Needs to be a SIM free (not carrier specific) firmware.
Let me do some additional researching about this and get back to you..
VeEuzUKY said:
Thanks for sharing this info and for giving this a try.
Maybe the flashing halted itself because the firmware is not compatible or maybe other reason.. I am not quite sure. What Firmware exactly did you download and use for the Flashing? Needs to be a SIM free (not carrier specific) firmware.
Let me do some additional researching about this and get back to you..
Click to expand...
Click to collapse
I'm tried using the firmware linked in that post, but now I'm going to SamMobile and downloading the Netherlands version of the software (PDA = T815XXU2BPE4).
Michael833 said:
I'm tried using the firmware linked in that post, but now I'm going to SamMobile and downloading the Netherlands version of the software (PDA = T815XXU2BPE4).
Click to expand...
Click to collapse
I hear Netherlands, UK and Germany firmwares (SIM free, not carried bounded) and all similar and most compatible
VeEuzUKY said:
I hear Netherlands, UK and Germany firmwares (SIM free, not carried bounded) and all similar and most compatible
Click to expand...
Click to collapse
Netherlands failed too. I'm not thinking this is going to work . . .
Remember to keep a backup in your sim in case it gets hard bricked but I think that is unlikely to happen
---------- Post added at 10:21 AM ---------- Previous post was at 10:20 AM ----------
Michael833 said:
Netherlands failed too. I'm not thinking this is going to work . . .
Click to expand...
Click to collapse
Netherlands failed too? Unlikely it is going to work then.
Very disappointed that this 815C model is stuck for good in the 5.0.2 territory
jcrewjcrew said:
Very disappointed that this 815C model is stuck for good in the 5.0.2 territory
Click to expand...
Click to collapse
Yes! I can't believe the situation. It's still the current model, being sold at every retail shop, yet, seems completely abandoned by Samsung. Even the first generation Tab S is already getting MM updates, I just can't believe this. This is a completely inadmissible situation
I'm thinking the rom official at 815C model is SM-T815N Korea currently has marshmallow but not the short time available to me I could not do it,
Joesnake said:
I'm thinking the ROM official at 815C model is SM-T815N Korea currently has marshmallow but not the short time available to me I could not do it,
Click to expand...
Click to collapse
The problem is the 815C and 815N are different models. I dont think it will work to cross flash them. I am thinking "maybe" one idea would be to do the flash without bootloader and modem.. I wonder if someone ever tried that and it could work.. I'm thinking maybe it might..
VeEuzUKY said:
The problem is the 815C and 815N are different models. I dont think it will work to cross flash them. I am thinking "maybe" one idea would be to do the flash without bootloader and modem.. I wonder if someone ever tried that and it could work.. I'm thinking maybe it might..
Click to expand...
Click to collapse
The only thing that changes from version 815 c 815n is the networks lte supported later by the specifications are the same
Joesnake said:
The only thing that changes from version 815 c 815n is the networks lte supported later by the specifications are the same
Click to expand...
Click to collapse
Then the flashing the 815N into the 815C without bootloader and modem maybe can work..
VeEuzUKY said:
Then the flashing the 815N into the 815C without bootloader and modem maybe can work..
Click to expand...
Click to collapse
Extract all the images from the stock firmware with 7zip.
Using 7-zip repack the boot and system images using the create archive option from the menu. Use Store and Tar as the only options.
Flash with ODIN.
ENSURE YOU HAVE A FULL TWRP BACKUP *BEFORE * DOING THIS PROCEDURE
Your mileage may vary, but it should at least flash.
ashyx said:
Extract all the images from the stock firmware with 7zip.
Using 7-zip repack the boot and system images using the create archive option from the menu. Use Store and Tar as the only options.
Flash with ODIN.
ENSURE YOU HAVE A FULL TWRP BACKUP *BEFORE * DOING THIS PROCEDURE
Your mileage may vary, but it should at least flash.
Click to expand...
Click to collapse
Thanks for the info, but I have a question. If am not adding or deleting any files to the original flashable firmware, what is the point to unpack it and repack it again as it was?
Related
I've had my phone for about a week now.
I had I9000XXJP2- version on it. i aslo had super user and one click lag fix. Everything was working fine untill this morning. The phone froze and attempted to restart. as it did it was stuck on the Galaxy S GT-I9000 screen and would not boot past that. I am able to get into recovery mode. and a mode that says upload by pressing with the android man next to it.
The phone also will not shut off unless the battery is taken out.
Can anyone help me get back into my phone.
I think some how it deleted its OS.
Thanks in advance.
Also: when in Odin and trying to put in the firmware I9000XXJP2-REV03-PDA-CL464213.tar says that file analysis failed.
As well as when i go to reformat internal sd-card the following comes up
Formatting SDCARD
ensure_root_path_unmounted++
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:copy_dbdate_media:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
Do you have a Bell I9000M Galaxy S Vibrant by chance?
Either way, You have the infamous internal SD failure issue. Your best bet at this point is to flash back to stock and send the phone in for repair/replacement.
If it is indeed the Bell phone. Check out this thread.
Yes I do have that model :|
Can you please guide me to how I can get my hands on the stock firmware and the steps in order to flash back.
So this way I can send it in for repair or hopefully a replacement.
eddy_ed11 said:
Yes I do have that model :|
Can you please guide me to how I can get my hands on the stock firmware and the steps in order to flash back.
So this way I can send it in for repair or hopefully a replacement.
Click to expand...
Click to collapse
You can get UGJH2 from http://samfirmware.com. You can then flash it with odin and a 512 pit file. Which is also located at the mentioned site.
Electroz said:
You can get UGJH2 from . You can then flash it with odin and a 512 pit file. Which is also located at the mentioned site.
Click to expand...
Click to collapse
I appericate your help. Thanks for taking the time to help.
Just to make sure, I just use odin and put it in all three sections
[] PDA
[] PHONE
[] CSC
and I already have the 512 pit file.
PDA = CODE
Phone = Modem
CSC = CSC
Rawat said:
PDA = CODE
Phone = Modem
CSC = CSC
Click to expand...
Click to collapse
Understood that part.
but the files that i got from there only come with one zip package.
Not each one individually.
I still appreciate the love from this forum.
eddy_ed11 said:
Understood that part.
but the files that i got from there only come with one zip package.
Not each one individually.
I still appreciate the love from this forum.
Click to expand...
Click to collapse
Some of them have all three in one tar file. If you open up the tar file you should see all of them in there. I believe the UGJH2 has all three in one file. Just load it in the PDA section and leave the CSC and modem blank and flash.
dawgpound6985 said:
Some of them have all three in one tar file. If you open up the tar file you should see all of them in there. I believe the UGJH2 has all three in one file. Just load it in the PDA section and leave the CSC and modem blank and flash.
Click to expand...
Click to collapse
thank you very much as this makes more sense to me. I was used to having all three.
So i wanted to update who ever has been watching this thread. I went back to that rom and now i can get past that galaxy screen and i got the animated S but now its just a black screen.
So all i can do now is send it in for repairs and or hopefully a replacement
eddy_ed11 said:
thank you very much as this makes more sense to me. I was used to having all three.
So i wanted to update who ever has been watching this thread. I went back to that rom and now i can get past that galaxy screen and i got the animated S but now its just a black screen.
So all i can do now is send it in for repairs and or hopefully a replacement
Click to expand...
Click to collapse
What Bell did for me was just give me a new phone. I returned it within the 30 days. I had to wait two weeks for new stock to come in but they just gave me the new phone.
hatdrawn said:
What Bell did for me was just give me a new phone. I returned it within the 30 days. I had to wait two weeks for new stock to come in but they just gave me the new phone.
Click to expand...
Click to collapse
Seriously ? They didnt say that you were playing with the firmware or anything.
Im scared they might say that and then voids me getting it replaced or repaired.
But its good news to know that you got a new one.
And in the mean time did you get a loner phone from bell as you waited for yours to come in ?
Thanks for all the support and help.
eddy_ed11 said:
Seriously ? They didnt say that you were playing with the firmware or anything.
Im scared they might say that and then voids me getting it replaced or repaired.
But its good news to know that you got a new one.
And in the mean time did you get a loner phone from bell as you waited for yours to come in ?
Thanks for all the support and help.
Click to expand...
Click to collapse
I had my old Galaxy i5700 to use, but they will give you a loner phone. Do you have the SPC or whatever they call it? The insurance basically.
I just made up some BS about downloading a large movie to my phone and then it crashed. At they rate all the I9000M users are going with bricking their phones, Bell probably assumes it's a phone problem anyway haha.
The process was actually very simple for me, hope it is for you too. Good luck.
I went in today, told me i needed to talk to tech support.
Talked to tech support
and now i have with me a brand new galaxy s
This time i will not be playing around with it as, i do not want to go through that hassle once again.
I appericate all the help from this forum. and I will look back in here once again in the near future.
I will hold off on updating till froyo is officially released.
Thanks again. This community has been one of a kind.
Hello
I hope i have posted in the right section and someone can explain too me if this is right or wrong.
I just downloaded the 2.0 version of samsung kies software,when i plugged my phone in it said i could do a firmware upgrade for my phone.
So of course i did so,i first done the backup which was an option in the process.Then pressed ok and it started doing its thing.
Well i left it and came back too see a green android guy on the phone and a message on laptop saying the update had failed and i need too recover the fail by going into emergency firmware recovery mode.
I did this(pressed yes) and it started doing its thing again and rebooted the phone,after it had done it said too disconnect and reconnect my usb cable which i did and the phone was back running again.
The question i have is what basically just happened?
I presume it was a fail on the firmware update since thats what it told me but on checking my stats it had done what it said it was going too and thats upgrade from CSC: JP5 to CSC: JP6.
So it said it failed but on the samsung kies software it now says the csc JP6 and i cant update any firther.
Im sorry i should maybe of checked the code better too be honest i didnt check the full version upgrade, i just thought ok firmware upgrade yup ill do that and flicked through the yes options til the upgrade started.
Thanks for any replies.I have a untouched samsung galaxy S by the way,i not done anything too it except installed apps and games.So no roms,no lag fix,no hacks at all.
Its been a coupleof days now since my post so hope its ok too comment in it again so maybe i can get some help.
Im not sure if my first post explained itself enough so if anyone has any questions i will be happy too answer them.I dont know if my phone will be affected long term but the fail or not.
Csc..what is this why had the software felt it needed too be changed from 5 to 6 ?
the fact it said it failed yet on checking i cannot update again and it has in fact changed from 5 to 6 as it said it would.All my added shortcuts on home screens went but the files stayed.
csc....has anyone also got the changed firmware like i have and gone through the failure too get it.
Im trying too add my own questions in the hope someone has some answers since i see many questions get answered in this section within no time,but mine seems too of stumped some.
thanks for replies guys it will settle my mind and i will of course try too find my own answers and if all else fails i will contact samsung and ask them what went wrong.
Hi,
I installed Kies today and connected my girlfriends cellphone, a Samsung Champ Duos (don't know if it's a phone only for the Philippino market)... Same here, started up first time and Kies prompted me to update the phone's firmware. I followed the steps, something went wrong and I was told to perform an emergency recovery.
I tried, but after 63% an error message appear telling me that something went wrong and "if the problem persists please contact support centre".
I've tried the recovery process maybe 20 times now and same every time. I have already sent an email to the support, but hoping someone here knows how to fix this in the meantime.
Thanks in advance!
Not sure Kies can be unreliable...
Have you tried another computer?
Try the recovery again but hold the usb cable in place, it may have a loose connection
Either way support should answer you shortly and they will sort it out, as it should be under warranty and kies messed it up. They will probably tell you to find your nearest service centre...
@Caz2k11 if you ever read this again and still haven't got your answer, it shouldn't have affected you that there was a problem installing in the first place.
CSC - there is a sticky on the the general section that describes most of this stuff but in brief i think its either country specific code or country service code, something like that. Really its only important if you have problems downloading things from the market, or reception/data related issues. Usually carrier related... Its worth checking you have the correct one when you update as it saves you from changing it later which results in a factory reset.
Ahh damn it...
Got a reply from their support this morning. They apologized and told me I have to send the phone to my nearest service centre. Great for me living in the province and I'll bet the closest service centre is located in Manila....
Does anyone know if the *original rom* is available somewhere on the internet?
Most of us do not use kies to update
You can fiind the latest original ROMs at samfirmware.com
jc
3d_jc said:
Most of us do not use kies to update
You can fiind the latest ROM ar samfirmware.com
jc
Click to expand...
Click to collapse
Hehe no ****
I'm running Andriod on my HTC Leo as well, but this is my girlsfriends phone, still warranty so I'll be a bit careful at the moment.
Have registered on the site mentioned above, not sure which file I'm going to use or anything, since I cannot start the phone to see the current firmware etc. The model no. is GT-E2652W and "SSN" is "E2652WGSMH", does that mean it's a E-series phone?
It means a few things ...
First of all, you are totaly at the wrong place since this forum section is for Samsung Galaxy S, and you Champ Duo , well, isn't a Galaxy S !
Second thing is that this forum, as well as samfirmware, deal mostly with Android phones, which your isn't, I believe. It does somehow look like, but isn't.
Sorry I can't help more
jc
3d_jc said:
It means a few things ...
First of all, you are totaly at the wrong place since this forum section is for Samsung Galaxy S, and you Champ Duo , well, isn't a Galaxy S !
Second thing is that this forum, as well as samfirmware, deal mostly with Android phones, which your isn't, I believe. It does somehow look like, but isn't.
Sorry I can't help more
jc
Click to expand...
Click to collapse
Yes, I'm awared of that. Found this thread when I Google-searched "samsung emergency recovery".
Sure, no arm done, it's just that non android phone have a different way to recover. I did a couple of googling too, but must admit I did not find a great deal of information either,
Sorry and best of luck for bringing your device back to happiness.
jc
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.
After upgrading the firmware successfully according to odin our P1010 wifi-only galaxy tabs are stuck in an infinite reboot sequence that happens so quickly that we cannot use our galaxy tabs for anything. Right before it reboots we are all getting:
"Process android.process.media stopped unexpectedly. Try again"
This occurs immediately after the upgrade when you are doing the initial setup of the device. It is rebooting about every 15-30 seconds.
Please help us. We can still download using odin but we do not have the stock firmware. Someone out there help please. We are all going absolutely bonkers insane. Thx.
Try this : http://forum.xda-developers.com/showthread.php?t=961732
bongski55 said:
Try this : http://forum.xda-developers.com/showthread.php?t=961732
Click to expand...
Click to collapse
Dont mean to be rude but i just read that whole thread and it has absolutely nothing to do with the problem we are having. not once in that thread is mentioned any problems after upgrading firmware. in fact the thread seems to be about the P1000 with only a small bit about the P1010 which is unrelated to our problem.
Does anyone else have a solution or anything helpful?
frootloops said:
Dont mean to be rude but i just read that whole thread and it has absolutely nothing to do with the problem we are having. not once in that thread is mentioned any problems after upgrading firmware. in fact the thread seems to be about the P1000 with only a small bit about the P1010 which is unrelated to our problem.
Does anyone else have a solution or anything helpful?
Click to expand...
Click to collapse
sorry for not explaining. I thought you might want to use/flash the particular p1010 firmware discussed in that thread instead of what you have right now so as to eliminate/erase your error/problem.
I don't have a p1010 so I cannot verify. Next time I will not respond anymore to avoid misunderstanding.
frootloops said:
Does anyone else have a solution or anything helpful?
Click to expand...
Click to collapse
Did you solve your problem?
andrewin said:
Did you solve your problem?
Click to expand...
Click to collapse
no, i just gave up. my tab has been sitting on my desk for like 3 months unused. i guess i'll try recharging it if i can find it buried under the pile of papers and giving it another attempt at finding a solution.
not going to hold my breath tho... since it appears to be impossible to find the official united states p1010 firmware or whatever u guys call it.
bongski55 said:
sorry for not explaining. I thought you might want to use/flash the particular p1010 firmware discussed in that thread instead of what you have right now so as to eliminate/erase your error/problem.
I don't have a p1010 so I cannot verify. Next time I will not respond anymore to avoid misunderstanding.
Click to expand...
Click to collapse
sorry, didn't mean to offend you. i am just so utterly miserable about this device. i was so excited to get it, then i read about updating to fix some speed issues and increase battery life so i followed the guide and so i have only been able to use my device a total of about 1 day in about 5 months. very frustrating.
also, i am deathly afraid of "just trying" to flash anything as i dont want to make my device even worse than it already is.
i'll tell u one thing, i will never ever ever ever buy another samsung product again. they so very clearly dont give a rat's a** about the suffering of their customers. it doesn't matter if we did this to ourselves, they should still help. it is a stupid software fix that costs them nothing. do they think if they dont help us we will break down and buy a second one? i dont f'ing think so.
I had the same problem once.
Maybe the files are not matching like .PIT with Modem or bootloader thats why it keeps on restarting.
You should reinstall .PIT file then install accurate PDA , CSC and MODEM files for your own region.
omr911 said:
You should reinstall .PIT file then install accurate PDA , CSC and MODEM files for your own region.
Click to expand...
Click to collapse
Yea, this is the problem. Cant get United States region files. That is the whole issue.
SOLVED !!!
if you are having the infinite reboot problem on your US galaxy tab gt-p1010 do this:
1. download this rom (it is the hong kong rom)
http://www.multiupload.com/KJO2KALU2O
password: nomoreuncheckedfirmwares
2. put your tab in download mode by holding down the volume down button first then press and hold the power button.
3. start odin3 version 1.7, plug your tab into your pc.
4. verify you have the yellow in the ID:COM area in odin then select the pit file, the csc file and the pda file (the only file remaining) and hit start.
5. wait patiently while it downloads everything and reboots.
note that it will start up in chinese or japanese (not sure which, guessing chinese). also note that i am using windows xp, probably works in 32-bit windows 7 but may have problems with 64-bit windows 7. not sure cause i have not tried it. seems that i read that though.
good luck !!!
thanks to stsights for the solution and waqypaqy for uploading the file to a more accessible site!!! you guys make me more happy than u can possibly know...
frootloops said:
Yea, this is the problem. Cant get United States region files. That is the whole issue.
Click to expand...
Click to collapse
If US firmware is not available then install European Firmware
NO NO NO
omr911 said:
If US firmware is not available then install European Firmware
Click to expand...
Click to collapse
NO NO NO!!! This is what got the problem started in the first place. do NOT install european firmware on a US galaxy tab P1010. That will land u in infinite reboot hell. just dont do it.
So i just updated to V20 Europe Open following this tutorial and the update seemed to go through fine, rebooted, and new firmware installed. After finally setting up the phone as i like, i let it sit to synchronize all my contacts and what not. When i pushed the power button to wake up the phone, there were these random lines over the entire screen, look like blinds.
When i do a battery pull or reboot its back to normal, but everyime i let the phone sit for a couple of minutes and then wake it up, i get the same screen..
Ive attached two screen shots
Any ideas on how to fix this? Thanks.
I had the exact same problem, I didn't find any solution so I had to revert back to v10.
Which v20 did you install? The Portuguese one?
Mottz said:
I had the exact same problem, I didn't find any solution so I had to revert back to v10.
Which v20 did you install? The Portuguese one?
Click to expand...
Click to collapse
Use the same method that you use to roll back (LGFlash Tool) and install Euro_open V20A.
There is no difference between the euro and PT.
All needed files you can find them here:
http://forum.xda-developers.com/showpost.php?p=38838927&postcount=7
RuedasLocas said:
Use the same method that you use to roll back (LGFlash Tool) and install Euro_open V20A.
There is no difference between the euro and PT.
All needed files you can find them here:
http://forum.xda-developers.com/showpost.php?p=38838927&postcount=7
Click to expand...
Click to collapse
I tried the HK version as well, still having the issue. Do i just need to roll back to V10? Is it a software issue? How come very few people have it if all the versions are the same..?
faraband said:
I tried the HK version as well, still having the issue. Do i just need to roll back to V10? Is it a software issue? How come very few people have it if all the versions are the same..?
Click to expand...
Click to collapse
Might just be a bad flash.
By flashing with LGFlash Tool you don't need to roll back.
Just make sure that you have official firmware, don't use leaked.
To be a hardware problem, you should have it in ICS too...
RuedasLocas said:
Might just be a bad flash.
By flashing with LGFlash Tool you don't need to roll back.
Just make sure that you have official firmware, don't use leaked.
To be a hardware problem, you should have it in ICS too...
Click to expand...
Click to collapse
I tried 3 different routes to get V20A Euro installed, all the installs were successful but the screen issue is still there:
1. LG Flash Tool
2. KDZ_FW_UPD
3. Using LGKDZ hack and LG PC Suite
All of these successfully got V20A installed, but none solved the lines on the screen. I made sure to wipe before and after each install..
Any other ideas?
Perhaps screen is faulty ?
leolipop said:
Perhaps screen is faulty ?
Click to expand...
Click to collapse
I had no issues when on V10H, and nothing happened to the phone during the upgrade, just remained on my desk. When i revert back to V10H i have no issues also. I tried LGFlashTool to roll back to V10H and now have LG PC Suite find and upgrade the phone on its own, will see if that makes a difference...
Thanks
I see...I ll inform a member in another forum whereas he had the same issue.
faraband said:
I had no issues when on V10H, and nothing happened to the phone during the upgrade, just remained on my desk. When i revert back to V10H i have no issues also. I tried LGFlashTool to roll back to V10H and now have LG PC Suite find and upgrade the phone on its own, will see if that makes a difference...
Thanks
Click to expand...
Click to collapse
If after official upgrade doesn't work, I recommend you to take it to LG Service.
RuedasLocas said:
If after official upgrade doesn't work, I recommend you to take it to LG Service.
Click to expand...
Click to collapse
So i am currently in the US, bought the phone brand new unlocked from ebay. I called LG Support, and the rep said that since the phone is international, they cant do anything.. I would have to contact international LG Support to get help..? wtf
faraband said:
So i am currently in the US, bought the phone brand new unlocked from ebay. I called LG Support, and the rep said that since the phone is international, they cant do anything.. I would have to contact international LG Support to get help..? wtf
Click to expand...
Click to collapse
Same problem here. Not in such scale but I think it is the same. I had just bought the phone and when I did the update from the official site of LG te problem occured. I have sent the phone to service and I am waiting for it. Does anybody know if that phone has an international DOA??
Went to service, came back with the same problem. They had to replace it with a new one. I want risk to update again. Will stick with 4.0.
I just got a similar problem but much worse seen in the photo below attached my phone was working for a few weeks before this problem came as i was sat reading it, it just appeared while the screen was on. it also appears at boot and in cwm does this happen for you guys coz i think it's more a hardware problem for me.
Not sure what is causing it, but i went to 4 different repair stores, and none of them could figure it out. I sent it in for warranty, will report back what happens..
I had the same problem on my screen all the time , It's gone now for some reason, only thing i did is relocked the bootloader and unlocked it again since then it been running without any problems for almost a month now.
I remember i used the old method to unlock the bootloader , relocked it and i ran stock v20a(with locked bootloader) for like a month without any problems so i decided to try again , i used the official lg unlock method and now even on other roms it seems fine.
This bug is really annoying though hope ya'll get to fix it .
Try download an other v20 firmware, if that doesnt work, i can recommend superxe rom, its realy fast and stable.
Sent from my LG-P880 using xda app-developers app
I also think that it is a software problem because mine with the original Poland Rom 4.0 worked just fine.After one day of use I decided to upgrade to 4.1 from the original site of LG in Greece.this caused the problem.I believe that the flash caused some malfunction to the gpu.My cousin has the same exact phone for a year now but has never that problem.Maybe LG should give it a look because it seems pretty serious.
Sent from my LG-P880 using xda app-developers app
I had the same problem with V20A! but now I installed the CM10.1 nightly and also with the cyanogenmod appeared the same problem!! is a hardware problem? :crying: how can I fix?? Help me!! :crying:
this is the screenshot of CM10.1! I cut a little the picture!
Sent from my LG-P880 using xda app-developers app
is anyone elses permanently there. since it came on on mine it has never gone off including when booting up, in cwm and whilst in software recovery from flashing original bootloader. the other thing is screenshots look fine when on my pc.