I flashed a custom ROM on a friend's phone, but it didn't have a Chinese interface, which my friend wants. When I downloaded a stock ROM from Samsung Updates, it refused to install. That ROM was type CHT, and I see there is also a TWM for Taiwan, as well as a 4.0.4 WAN. Any idea how to determine which is the correct ROM? I didn't know it made a difference. My friend's phone was bought at Chunghwa Telecom, so the CHT ROM should have been correct.
Jimmy34742 said:
I flashed a custom ROM on a friend's phone, but it didn't have a Chinese interface, which my friend wants. When I downloaded a stock ROM from Samsung Updates, it refused to install. That ROM was type CHT, and I see there is also a TWM for Taiwan, as well as a 4.0.4 WAN. Any idea how to determine which is the correct ROM? I didn't know it made a difference. My friend's phone was bought at Chunghwa Telecom, so the CHT ROM should have been correct.
Click to expand...
Click to collapse
Check with www.sammobile.com
Of course. That's how I know there are CHT, TWM, WAN, and BRI ROMs for Taiwan. The question is which is the right one. I was hoping someone had an idea. I mean, obviously I can try them all, but there's no MD5 check on these downloads, so if I get file corruption it will just make that ROM appear to be the wrong one.
I've downloaded and installed all three Tawan ROMs: CHT, TWM, and BRI, but the recovery immediately aborts installation on all of them. I'm pretty sure that BRI is the correct one because I bought the same phone from the same place as my friend two years ago, and I used BRI. Any clues? It's just bizarre that I can't install a stock ROM, yet Wanam Lite installed no problem and runs fine.
Jimmy34742 said:
I've downloaded and installed all three Tawan ROMs: CHT, TWM, and BRI, but the recovery immediately aborts installation on all of them. I'm pretty sure that BRI is the correct one because I bought the same phone from the same place as my friend two years ago, and I used BRI. Any clues? It's just bizarre that I can't install a stock ROM, yet Wanam Lite installed no problem and runs fine.
Click to expand...
Click to collapse
You flash CUSTOM ROMs via recovery, not STOCK.
Flash via Odin.
Sent from...this is not even my S2
gastonw said:
You flash CUSTOM ROMs via recovery, not STOCK.
Flash via Odin.
Sent from...this is not even my S2
Click to expand...
Click to collapse
But they're zip files. I thought we can only flash zip files via recovery?
Unzip it, you should get a couple of tar files.
Sent from...this is not even my S2
D'oh! Of course. I had originally glanced inside the zip file and just assumed without looking closely. I now see there's a .tar.md5 in there, so I should have know to use Odin and not flash from recovery. thanks.
Related
So i live in saudi. Bought an ace and it came with the JPKC2 firmware. Thats the 2.2.1 middle east firmware. I've been into flashing roms lately. But if I ever want to go back to stock i have to flash the europe or asia firmware because the JPKC2 firmware on samfirmware.com isn't working.
It's a one package file in samfirmware. I downloaded and extracted the tar, downloaded the ops, opened odin, checked "one package", chose the tar file and the cooper ops and started the process. When it came to the close port and reboot step, the phone wouldn't boot. I mean it won't even turn on, at all!!! power button didnt do anything. removing and re-inserting battery, nada....... nothing. download mode still worked so i could just switch to other roms. But i'd really like the option of switching back to the firmware it came with. Are the files corrupted on the site? DId I do something wrong? THing is, this happened a while ago. And today i decided to give it another shot. this time, while flashing in odin it came to the 'system.rfs' step and just got stuck there. Can anyone please tell me what to do? I even tried googling JPKC2 but the link everyone puts up on the net is the same one package. What do I do? Thanks.
You could try hard resetting your phone and flash the froyo version of cwm recovery to backup your current rom. You could flash gingerbread/custom roms safely after that.
Cheers
In one package there is many time prob
first flash multipackage kph then your desired one package firmware thats only solution
nims11 said:
In one package there is many time prob
first flash multipackage kph then your desired one package firmware thats only solution
Click to expand...
Click to collapse
Are you saying I should first flash some other multi package froyo firmware and then flash the jpkc2 one package in odin? Or are you saying i should flash the actual KPH firmware and then the one package? I'm asking because XXKPH is android 2.3 while the one i'm trying to flash, JPKC2,(arabic fw) is android 2.2.1. will that actually work?......... just wanna double check. I already have DDKC1, asia FW 2.2.1. can i just flash that and then the one package??
gganon said:
Are you saying I should first flash some other multi package froyo firmware and then flash the jpkc2 one package in odin? Or are you saying i should flash the actual KPH firmware and then the one package? I'm asking because XXKPH is android 2.3 while the one i'm trying to flash, JPKC2,(arabic fw) is android 2.2.1. will that actually work?......... just wanna double check. I already have DDKC1, asia FW 2.2.1. can i just flash that and then the one package??
Click to expand...
Click to collapse
If you want to flash gingerbread one package then first flash multipackage gingerbread like kph
thats my mean
Hi all,
I'm new to Android but tech-savvy. I bought an AT&T I777 in the U.S. a couple of weeks ago, got it unlocked, and have been using it fine on my UK SIM.
Then, I got into rooting/hacking etc., and long story short I can't make or receive calls any more. The phone does dial out, and incoming calls ring, but once the connection is made there is no audio. It's as if both parties are on mute. Currently I'm on the Unnamed ROM v1.0.4, but the problem exists with any custom ROM I install, even the stock OS. The only thing I haven't undone (not even sure it's possible) is un-root/de-root the phone.
Any ideas?
Thanks,
Chris
Try reflashing the modem. Entropy has a stock Odin flashable modem. Look in the development section. I don't know how to put links up from my phone otherwise I would. He has it mentioned about if losing voice to reflash modem from Odin. Hope this helps and solves your problem.
Sent from my SAMSUNG-SGH-I777 using XDA App
re: no sound
cneal said:
Hi all,
I'm new to Android but tech-savvy. I bought an AT&T I777 in the U.S. a couple of weeks ago, got it unlocked, and have been using it fine on my UK SIM.
Then, I got into rooting/hacking etc., and long story short I can't make or receive calls any more. The phone does dial out, and incoming calls ring, but once the connection is made there is no audio. It's as if both parties are on mute. Currently I'm on the Unnamed ROM v1.0.4, but the problem exists with any custom ROM I install, even the stock OS. The only thing I haven't undone (not even sure it's possible) is un-root/de-root the phone.
Any ideas?
Thanks,
Chris
Click to expand...
Click to collapse
Here is the stock i777 modem (phone) TAR file.
Your audio shall magically return after you flash this:
http://www.megaupload.com/?d=XM8SOP22
You will need to flash this in Odin.
Be sure to put this in the PDA slot in Odin.
Good luck!
Fixed (well, reverted)
Hi,
Thanks for your useful advice. Before reading your replies I managed to get my phone back the way it was by getting hold of the stock ROM (file: Samsung_GALAXY_S2_ATT_I777UCKJ1_.exe). I've read so many forums and wikis today I can't remember where I found it, but it restored my phone to its original state and now everything is working again.
I've learned a lot along the way about rooting, flashing, CWM, etc. etc. so I may well have another go in the next couple of days, and knowing that the modem flash is available will give me the confidence to try again.
Thanks again,
Chris
Misterjunky said:
Here is the stock i777 modem (phone) TAR file.
Your audio shall magically return after you flash this:
You will need to flash this in Odin.
Be sure to put this in the PDA slot in Odin.
Good luck!
Click to expand...
Click to collapse
THANK YOU!!!!! oh how amazing the search tool is.
Thanks for the fixes
Many thanks for posting that file. I have actually fixed my problem another way by flashing the Unnamed ROM, but I'll keep this handy for future reference.
Chris
*bookmark* having this same issue. will try this when i get off work
Misterjunky said:
Here is the stock i777 modem (phone) TAR file.
Your audio shall magically return after you flash this:
You will need to flash this in Odin.
Be sure to put this in the PDA slot in Odin.
Good luck!
Click to expand...
Click to collapse
Saved my ass, I was having this problem too. All hail xda!
thank u techie gods!!!!
Hi,
Please help, the link is broken!
I have I777 CM 10.3.1 BV I777UCMD8, everything works great, but no audio
saqsun said:
Hi,
Please help, the link is broken!
I have I777 CM 10.3.1 BV I777UCMD8, everything works great, but no audio
Click to expand...
Click to collapse
All modems are available in zip format in the sticky thread in the development forum. If you have stock firmware and thus stock recovery, then you can not flash these, but you could flash the full I777UCMD8 package which you can download from the Download Repository. If you have a custom recovery, you can flash these directly from CWM or TWRP recovery. I am not aware of a tar version of any of the modems, so just flash the full stock distribution to get the modem.
creepyncrawly said:
All modems are available in zip format in the sticky thread in the development forum. If you have stock firmware and thus stock recovery, then you can not flash these, but you could flash the full I777UCMD8 package which you can download from the Download Repository. If you have a custom recovery, you can flash these directly from CWM or TWRP recovery. I am not aware of a tar version of any of the modems, so just flash the full stock distribution to get the modem.
Click to expand...
Click to collapse
Hi, thanks for reply!
Unfortunately even after flashing the full stock distribution I still have the problem. Everything works but still no audio. Sometimes after 10 restarts it comes back and I have audio for a while and then for no reason it disappears. Can you help me or suggest something?
saqsun said:
Hi, thanks for reply!
Unfortunately even after flashing the full stock distribution I still have the problem. Everything works but still no audio. Sometimes after 10 restarts it comes back and I have audio for a while and then for no reason it disappears. Can you help me or suggest something?
Click to expand...
Click to collapse
It's always a question, is the issue due to firmware or hardware failure. It is normally considered that the test of flashing back to stock is fairly conclusive on this phone, ie. if you flash back to stock and the problem persists, then it is probably a hardware issue.
You could try flashing an earlier stock, maybe even the original Gingerbread I777UCKH7, and see if that clears the problem up. It never hurts to double check or even triple check your results, but it is beginning to look like a hardware failure.
I have a mac, so no odin, and Heimdall won't recognize my sgs2. Originally i rooted my phone with a shell script. I then used Rom Manager to install Cyanogenmod 7.1. All was good til I decided to give ICS a spin, so I downloaded kp8 from this thread:
http://forum.xda-developers.com/showthread.php
And tried to flash using Mobile Odin. It flashed, rebooted, and now I am stuck at the boot screen. I am guessing that maybe I needed to get a CF-Recovery compatible build??
Anyways, just want to get back in working condition. I currently have no way to mount the sd card (no sd card mount option in normal recovery), so I have to wait until tomorrow when I can borrow a friends phone. Should I just try to update to a CF- kernel?
Do I need a pc?
Thanks
Do you have CWM recovery, or stock recovery?
If you have CWM recovery boot into it and wipe data/cache and it may boot or flash a rom of your SD card.
Otherwise borrow someones PC and use odin to flash back to GB, make sure to flash the GB bootloaders first. (On that note, did you flash the ICS bootloaders? As if you didnt that might be why its not booting)
Do you have CWM recovery, or stock recovery?
Click to expand...
Click to collapse
stock
Otherwise borrow someones PC and use odin to flash back to GB, make sure to flash the GB bootloaders first. (On that note, did you flash the ICS bootloaders? As if you didnt that might be why its not booting)
Click to expand...
Click to collapse
Wasn't aware I needed to, sounds logical. I'll do some more research before trying again.
Thanks
j_s_1 said:
stock
Wasn't aware I needed to, sounds logical. I'll do some more research before trying again.
Thanks
Click to expand...
Click to collapse
Yup, you need new bootloaders for ICS, but beware, the current ICS leaks are buggy and not really ready to be daily drivers.
As you have stock recovery, I would just borrow someones PC and use odin to flash stock gingerbread back.
never mind
Just an update. I got the ability to copy files to my sd card. I have tried to do an update from sd card with
i9100XXKG1
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4
Both resulting in "Signature verification failed".
As you have stock recovery, I would just borrow someones PC and use odin to flash stock gingerbread back.
Click to expand...
Click to collapse
Is my only recourse to find a pc or should I try something else? If I get a pc I will only have access to it for a short time, so want to make sure I am trying the right things.
That flash failed as Rom Manager likely broke recovery (has happened to me in the past, Rom Manager - bad).
PC as previously advised. I'd say you've exhausted all the non-PC options.
j_s_1 said:
Just an update. I got the ability to copy files to my sd card. I have tried to do an update from sd card with
i9100XXKG1
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4
Both resulting in "Signature verification failed".
Is my only recourse to find a pc or should I try something else? If I get a pc I will only have access to it for a short time, so want to make sure I am trying the right things.
Click to expand...
Click to collapse
Ok. And one last question, as far as flashing stock gingerbread (or a diff stock ROM), what would be the best, safest package to try? I do not know my kernel version, and can't find out (as I can't boot)
My phone is the international version of sgs2, purchased in Germany, csc code DBT.
searching for stock gingerbread for my phone seems to come up with a bunch of different builds.
Thanks
KI4 seems to be the most recent in Intra's thread, so I'd go with that. Not that it makes a massive amount of difference tho.
j_s_1 said:
Ok. And one last question, as far as flashing stock gingerbread (or a diff stock ROM), what would be the best, safest package to try? I do not know my kernel version, and can't find out (as I can't boot)
My phone is the international version of sgs2, purchased in Germany, csc code DBT.
searching for stock gingerbread for my phone seems to come up with a bunch of different builds.
Thanks
Click to expand...
Click to collapse
Update:
Got a pc and got odin working. Flashed MultiCSC_OXA_I91000XXKI2.tar . rebooted and it tried to go into recovery mode then gave me a dead robot with a red exclamation point, which doesn't seem good.
Ideas?
UPDATE:
Nevermind, I just had to get the full firmware :
XWKI4
Firmware info
PDA:XWKI4
PHONE: XXKI1
Date: 14/09/2011
Android 2.3.4
for DBT (Germany). Flashed with Odin and I am back. Awesome. Thanks
I did say to get KI4 from Intratech's thread, didn't I ? Anywho, glad you got you phone working again
j_s_1 said:
Update:
Got a pc and got odin working. Flashed MultiCSC_OXA_I91000XXKI2.tar . rebooted and it tried to go into recovery mode then gave me a dead robot with a red exclamation point, which doesn't seem good.
Ideas?
UPDATE:
Nevermind, I just had to get the full firmware :
XWKI4
Firmware info
PDA:XWKI4
PHONE: XXKI1
Date: 14/09/2011
Android 2.3.4
for DBT (Germany). Flashed with Odin and I am back. Awesome. Thanks
Click to expand...
Click to collapse
Yesterday, I plugged in my tab to the charger over night. When I unplugged it today, I restarted it and after that it won't boot. The tab only shows the "Samsung galaxy tab 10.1" text for about 20-30 seconds and then it seems to reboot.
The device is rooted and running this rom. It is a 10.1" P7500 3g version.
Although I can still access recovery and bootloader modes, so I've tried wiping cache (normal cache can be cleared, but not dalvik) and data but nothing happens when I try to do it (It justs stays at formatting data forever when I do a full wipe). I've also tried flashing the same firmware and reinstalling the same rom again. I had an old backup of a earlier version of the rom, which I restored to but then I only get the boot screen to load for 2-3 seconds and then it freezes.
What should I do now?
Solved: Read my latest post.
Flash from scratch with Odin. No other choice.
Misledz said:
Flash from scratch with Odin. No other choice.
Click to expand...
Click to collapse
Alright, what files should I flash? Should I get a hold of a original firmware? Thanks for answering btw!
Ah you're welcome
Just get it off samfirmware.com, get HC 3.2 (Don't go for 3.1 as it is rubbish), Get the european firmware as it is the same and the most stable build (Also the first release for most new firmwares, if ICS were to come out, EU would get the firmware first)
GL and feel free to ask what you lack
Flashing guide's are pretty much simple.
Flash the unextracted file (must be in md5 extension) in PDA slot in odin in download mode and voila.
Ah la fresh tablet minion
Misledz said:
Ah you're welcome
Just get it off samfirmware.com, get HC 3.2 (Don't go for 3.1 as it is rubbish), Get the european firmware as it is the same and the most stable build (Also the first release for most new firmwares, if ICS were to come out, EU would get the firmware first)
GL and feel free to ask what you lack
Flashing guide's are pretty much simple.
Flash the unextracted file (must be in md5 extension) in PDA slot in odin in download mode and voila.
Ah la fresh tablet minion
Click to expand...
Click to collapse
I downloaded a 3.2 firmware from samfirmware.com, more specific:
"P7500XWLB1 3.2 2012 February P7500NSELA1 Sweden (Telia)"
It was zipped, i unzipped it and it was one .md5 file and one .dll file. I flashed the .md5 file with Odin in PDA. Odin tells me it is successful, and then the tab shows some scripts saying everything is succesful and then it reboots into the Samsung Galaxy Tab 10.1 text. After that I get a text saying "Manual mode, updating application..." for a while until it reboots into the same procedure again.
Atm I'm downloading another firmware just to be sure, I'll post when I've tried that one aswell. (It's named7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries)
Really appreciate your help
Edit: Tried the other firmware without any success.
But have you been able to boot into the tablet properly after flashing? Don't worry about the dll, I don't really know what it's for, actually no one know's since Samsung hasn't even told us what it's used for, and phone's don't read dll's
That manual mode updating is the stock recovery building the CSC and everything (Regional settings)
Which firmware didn't work? You can only use 7500 firmware on a 7500 And don't forget to flash a CWM recovery, just might save your life
Misledz said:
But have you been able to boot into the tablet properly after flashing? Don't worry about the dll, I don't really know what it's for, actually no one know's since Samsung hasn't even told us what it's used for, and phone's don't read dll's
That manual mode updating is the stock recovery building the CSC and everything (Regional settings)
Which firmware didn't work? You can only use 7500 firmware on a 7500 And don't forget to flash a CWM recovery, just might save your life
Click to expand...
Click to collapse
I flashed P7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries, and booted it but nothing happened. So I flashed a CWM recovery, and then it boots into Samsungs original-boot animation and then a text says Samsung. And then after a while it reboots again.
I'm at a loss right now, should I try to flash in a different order or flash with the device booting in between?
Ah, you ended up in a bootloop. Sometimes you may need to flash that firmware, then factory reset in recovery to get it to work. Depends if you had something in your previous ROM that conflicts. Or you can save the problem's and flash with a pit file. The overcome thread has a wonderful guide on that
rackadoosing said:
I flashed P7500XWLB1 3.2 2012 February P7500OXXLB1 Nordic countries, and booted it but nothing happened. So I flashed a CWM recovery, and then it boots into Samsungs original-boot animation and then a text says Samsung. And then after a while it reboots again.
I'm at a loss right now, should I try to flash in a different order or flash with the device booting in between?
Click to expand...
Click to collapse
You can try the method described here;
http://forum.xda-developers.com/showpost.php?p=22964943&postcount=4
It will get you back totally to stock, and then you can re-root and reflash.
Hopefully that helps (should fix most problems).
Br,
/primpa
Thanks alot guys!! I followed the "Re-“Stocking” Yer System…"-guide at the bottom of the page you linked, and the tab is now booting correctly. You're my life savers! Thanks again
rackadoosing said:
Thanks alot guys!! I followed the "Re-“Stocking” Yer System…"-guide at the bottom of the page you linked, and the tab is now booting correctly. You're my life savers! Thanks again
Click to expand...
Click to collapse
That method has yet to fail me.
Used to go around suggesting it everywhere but others have used it with success and are stepping in when needed.
Sent from my GT-P7510 using XDA Premium HD app
Greetings,
I have a German T-Mobile GSIII that asked to update itself tonight. The current baseband is BOLF1, it attempted to update to BLH3. The update failed with a code 7. I have CWM loaded and also the Siyah 1.5.2 kernel. I am downloading the full BLH3 file from SamMobile, do I just flash that with CWM or do I need to do something else. I have seen comments on the various boards about opening the .zip and changing a setting to supress version checking, but I am not sure if I need to do that or if that is related to the JB leaks.
Any help would be appreciated.
thanks
Mike
Bump for more visibility.
michaeljwestii said:
Greetings,
I have a German T-Mobile GSIII that asked to update itself tonight. The current baseband is BOLF1, it attempted to update to BLH3. The update failed with a code 7. I have CWM loaded and also the Siyah 1.5.2 kernel. I am downloading the full BLH3 file from SamMobile, do I just flash that with CWM or do I need to do something else. I have seen comments on the various boards about opening the .zip and changing a setting to supress version checking, but I am not sure if I need to do that or if that is related to the JB leaks.
Any help would be appreciated.
thanks
Mike
Click to expand...
Click to collapse
Never take official OTA's when on a custom ROM. If you really want the official OTA, either wait until a rooted version is released, or if you can't wait just go to SamFirmware, download the full ROM (not the OTA file) and flash it with ODIN. It'll overwrite everything except your external SD card.
Product F(RED) said:
Never take official OTA's when on a custom ROM. If you really want the official OTA, either wait until a rooted version is released, or if you can't wait just go to SamFirmware, download the full ROM (not the OTA file) and flash it with ODIN. It'll overwrite everything except your external SD card.
Click to expand...
Click to collapse
Thanks for the help. I am on stock except for the kernel, not sure if the kernel counds as a custom ROM or not. I guess it does. I had renamed a ton of the origional apps (added .bak to the end) causing verification errors. I am slowly going through and fixing each of them. I have the full ROM from SamFirmware (the origional BLFB not the latest) so I should be able to fix this.
michaeljwestii said:
Thanks for the help. I am on stock except for the kernel, not sure if the kernel counds as a custom ROM or not. I guess it does. I had renamed a ton of the origional apps (added .bak to the end) causing verification errors. I am slowly going through and fixing each of them. I have the full ROM from SamFirmware (the origional BLFB not the latest) so I should be able to fix this.
Click to expand...
Click to collapse
It's because OTA ZIP's that are downloaded to the phone only contain the parts of the ROM that need updating, not an entirely new ROM. You can, however, download the update as an entire ROM from SamFirmware.