Hello. I have an I9300 model (with T-mobile UK). I accidentally broke the phone's software and so I tried to restore to a firmware that I thought was OK for the device which is:
Baseband version: I9300BVLH1
Build number: IMM76D.I9300XXBLG8
But the firmware is buggy. Connecting to Kies doesn't work and the Samsung stock keyboard doesn't allow me to change the settings and the swipe function fails. There are various other issues. It's useable but certainly is not functioning properly.
So what firmware do I need? I found this one by my own research: GT-I9300_BTU_I9300XXALE8_I9300OXAALE8_I9300XXLE8
But that has a modem.bin file. According to heimdall (No windows for me), my phone doesn't want a model.bin file. There is no MODEM partition available for flashing when using heimdall-frontend.
So:
1) What firmware do I need for a correctly functioning Android 4.0.4?
2) Can I upgrade to Jellybean from there?
3) Can I go straight to Jellybean, skipping 4.0.4?
Thank you.
MatthewLM said:
Hello. I have an I9300 model (with T-mobile UK). I accidentally broke the phone's software and so I tried to restore to a firmware that I thought was OK for the device which is:
Baseband version: I9300BVLH1
Build number: IMM76D.I9300XXBLG8
But the firmware is buggy. Connecting to Kies doesn't work and the Samsung stock keyboard doesn't allow me to change the settings and the swipe function fails. There are various other issues. It's useable but certainly is not functioning properly.
So what firmware do I need? I found this one by my own research: GT-I9300_BTU_I9300XXALE8_I9300OXAALE8_I9300XXLE8
But that has a modem.bin file. According to heimdall (No windows for me), my phone doesn't want a model.bin file. There is no MODEM partition available for flashing when using heimdall-frontend.
So:
1) What firmware do I need for a correctly functioning Android 4.0.4?
2) Can I upgrade to Jellybean from there?
3) Can I go straight to Jellybean, skipping 4.0.4?
Thank you.
Click to expand...
Click to collapse
1
You need to start over with secure and proper tested firmware, so first of all root your phone using this excellent guide (fool prof)
http://forum.xda-developers.com/showthread.php?t=1703488
Then dl your chosen JB rom to sd card and flash it from the newly installed recovery (cwm) then your using the built in rom stock kernel and can freely flash the 2 other kernels available for JB at the moment (siyah or Yank555 kernel)
Siyah >http://forum.xda-developers.com/showthread.php?t=2006459
Yank555>http://forum.xda-developers.com/showthread.php?t=2006459
Then your up to date and running JB 4.1.2 and able to flash other roms etc.
(Dont unzip any files ever...flashing from cwm is zips only, id suggest you to stay of flashing via odin/heimdal as long you arent more experienced)
Greetz :victory:
spoonymoon said:
You need to start over with secure and proper tested firmware, so first of all root your phone using this excellent guide (fool prof)
http://forum.xda-developers.com/showthread.php?t=1703488
Click to expand...
Click to collapse
Thanks for the reply spoonymoon. Is there a Mac version of this toolkit (I can build it from source if necessary)? I'm stuck with using a Mac to flash firmwares. Heimdall is the only way I found I could do it. If there is a Linux tool I might be able to get it to work in a virtual machine.
Also my phone is already rooted and has clockwork recovery. All I need to do is have the correct firmware installed... easier said than done.
Ah, the IMM76D.I9300XXBLG8 firmware I flashed contained a modem.bin file but I didn't flash it since heimdall doesn't allow for that. Is that why the phone is buggy, because heimdall couldn't flash the modem partition? Why can't it flash the modem partition and is there a way in which I can get it to flash the modem?
Should I try flashing GT-I9300_BTU_I9300XXALE8_I9300OXAALE8_I9300XXLE8 without the modem?
Related
Hi,
I am with AT&T in the US and recently bought the Galaxy S2. My device happens to be a French version. My firmware is
PDA: KG1 / PHONE: KG1 / CSC: KG2 (XEF). It's 2.3.3.
I'm not happy with my HSPA+ data connection. While streaming online radio in moving car, it would cut out and constantly buffer. Seems like the data stream is not reconnecting quickly enough whenever there's handoff. This has never happened in my old webOS Pre Plus. The streaming on the same route that I drive daily on the Pre Plus was never an issue.
I don't want to mess with flashing to a different ROM (yet), but is it possible to just replace/flash the baseband only? Perhaps I can try the official ATT baseband? I did a search and am overwhelmed with the amount of info on XDA. I appreciate you help. Thank you.
sooby77 said:
Hi,
I am with AT&T in the US and recently bought the Galaxy S2. My device happens to be a French version. My firmware is
PDA: KG1 / PHONE: KG1 / CSC: KG2 (XEF). It's 2.3.3.
I'm not happy with my HSPA+ data connection. While streaming online radio in moving car, it would cut out and constantly buffer. Seems like the data stream is not reconnecting quickly enough whenever there's handoff. This has never happened in my old webOS Pre Plus. The streaming on the same route that I drive daily on the Pre Plus was never an issue.
I don't want to mess with flashing to a different ROM (yet), but is it possible to just replace/flash the baseband only? Perhaps I can try the official ATT baseband? I did a search and am overwhelmed with the amount of info on XDA. I appreciate you help. Thank you.
Click to expand...
Click to collapse
You will need to root it to be able to install different modems using CWM recovery or you can use Odin to do it with out root if you can find modem packaged for Odin, as for the AT&T modem while it will work okay for data your call quality will be terrible so it is not really an option for an international version SGS2.
jhernand1102 - Thanks for your quick reply! I've done some flashing before on other devices, so I'm not totally unfamiliar with the process. So it is possible to install a different modem without completely flashing to a different ROM? I see that you're in the US. Can you suggest a modem? What do you use?
jhernand1102 said:
You will need to root it to be able to install different modems using CWM recovery or you can use Odin to do it with out root if you can find modem packaged for Odin, as for the AT&T modem while it will work okay for data your call quality will be terrible so it is not really an option for an international version SGS2.
Click to expand...
Click to collapse
I was recently in the US and used my SG II on AT&T without any issues.
I have rooted XXKH3 - with Lite'ning Rom V6.1
sooby77 said:
jhernand1102 - Thanks for your quick reply! I've done some flashing before on other devices, so I'm not totally unfamiliar with the process. So it is possible to install a different modem without completely flashing to a different ROM? I see that you're in the US. Can you suggest a modem? What do you use?
Click to expand...
Click to collapse
Yes, it is possible to flash another modem file to your phone.
The easiest way of doing so is to flash it as zip file via CWM.
But you can also flash the modem.bin file (extract the zip file first) via Odin (in PHONE section).
Here are two links to the latest modem files:
1. => http://forum.xda-developers.com/showthread.php?t=1277593&highlight=Modem+XXKI3
But you need CWM to flash this Modem zip files.
2. => http://forum.xda-developers.com/showpost.php?p=17967764&postcount=5
Same here, but you can extract the Modem.bin file out of the zip file and flash it using (Phone section in) Odin.
Good luck!
It_ler said:
Yes, it is possible to flash another modem file to your phone.
The easiest way of doing so is to flash it as zip file via CWM.
But you can also flash the modem.bin file (extract the zip file first) via Odin (in PHONE section).
Here are two links to the latest modem files:
1. => http://forum.xda-developers.com/show...ht=Modem+XXKI3
But you need CWM to flash this Modem zip files.
2. => http://forum.xda-developers.com/show...64&postcount=5
Same here, but you can extract the Modem.bin file out of the zip file and flash it using (Phone section in) Odin.
Good luck!
Click to expand...
Click to collapse
Thanks It_ler. I think your links were truncated, and as a result, it's not coming up. I have Odin on my computer. In your view, is it better to use Odin or CWM?
JackTheMan18 - I don't have issues with voice calls on ATT, but it's the HSPA+ connection when streaming is what I'm not happy about.
sooby77 said:
Thanks It_ler. I think your links were truncated, and as a result, it's not coming up. I have Odin on my computer. In your view, is it better to use Odin or CWM?
JackTheMan18 - I don't have issues with voice calls on ATT, but it's the HSPA+ connection when streaming is what I'm not happy about.
Click to expand...
Click to collapse
Sorry about the truncated links - now repaired.
Searched myself in this forum and while copying&pasting ... something went wrong.
I don't have a personal prefer ... Odin or CWM ?!
If your phone is rooted and you already have CWM, it is the easiest way to flash modem zip file using CWM.
As I am running on CF-Root kernel which has installed CWM Manager app, I would flash the modem zip file using CWM.
But normally, I choose my ROM and modem and CSC before flashing ... and then I flash all the files I want together at once via Odin.
So, it's up to you !
It_ler said:
Yes, it is possible to flash another modem file to your phone.
The easiest way of doing so is to flash it as zip file via CWM.
But you can also flash the modem.bin file (extract the zip file first) via Odin (in PHONE section).
Here are two links to the latest modem files:
1. => http://forum.xda-developers.com/showthread.php?t=1277593&highlight=Modem+XXKI3
But you need CWM to flash this Modem zip files.
2. => http://forum.xda-developers.com/showpost.php?p=17967764&postcount=5
Same here, but you can extract the Modem.bin file out of the zip file and flash it using (Phone section in) Odin.
Good luck!
Click to expand...
Click to collapse
It_ler said:
Sorry about the truncated links - now repaired.
Searched myself in this forum and while copying&pasting ... something went wrong.
I don't have a personal prefer ... Odin or CWM ?!
If your phone is rooted and you already have CWM, it is the easiest way to flash modem zip file using CWM.
As I am running on CF-Root kernel which has installed CWM Manager app, I would flash the modem zip file using CWM.
But normally, I choose my ROM and modem and CSC before flashing ... and then I flash all the files I want together at once via Odin.
So, it's up to you !
Click to expand...
Click to collapse
It_ler - Thank you so much! You've been incredibly helpful! Since you are so knowledgeable, I hope you might be able to answer this follow up question. As I indicated, I'm stuck on the French 2.3.3 ROM.
1. Can I just flash a 2.3.4 or 2.3.5 stock ROM without rooting but using ODIN? Will that be a clean wipe or will it just upgrade and keep all my app and settings?
2. Will doing so prevent Kies from offering me future updates? I don't care about CSC, in fact, half the French customizations on my unit don't work here in the US. My first SGS2 unit that was defective was an UK version (I assume so because it came installed with the BBC app).
3. What's a good stock ROM to put on?
You are awesome!
sooby77 said:
It_ler - Thank you so much! You've been incredibly helpful! Since you are so knowledgeable, I hope you might be able to answer this follow up question. As I indicated, I'm stuck on the French 2.3.3 ROM.
1. Can I just flash a 2.3.4 or 2.3.5 stock ROM without rooting but using ODIN? Will that be a clean wipe or will it just upgrade and keep all my app and settings?
2. Will doing so prevent Kies from offering me future updates? I don't care about CSC, in fact, half the French customizations on my unit don't work here in the US. My first SGS2 unit that was defective was an UK version (I assume so because it came installed with the BBC app).
3. What's a good stock ROM to put on?
You are awesome!
Click to expand...
Click to collapse
I thought that you already knew about the basics, but here they are:
a) To get familiar with flashing ROMs / kernels / etc., find official firmwares, stock kernels, etc. and to learn the "manual" rooting method, read the first post of Intratech's thread => http://forum.xda-developers.com/showthread.php?t=1075278.
Official firmwares are in the second post, and Frankenstein versions (which can be combined with any other modem and/or CSC) are in the third post.
Every ROM is non-wipe - except Intratech has explicitly written that it is a "wipe" version.
Flashing is by using Odin and does not require root.
But Intratech has added a Quick Rooting Guide, just in case you need it.
b) To find the easiest way of rooting, please stick to Chainfire's CF-Root thread => http://forum.xda-developers.com/showthread.php?t=1103399&highlight=CF+Root.
There you learn to root your phone and get ClockWorkMod (CWM) Manager app with CWM recovery mode, system backup&recovery feature, flashing other kernels and zip files, etc..
Nothing to bother. I just flashed CF-Root kernel because it is so easy and I wanted to be able to backup my system.
Now I can answer your questions:
1. Yes, stick to Intratech's description and use a non-wipe ROM to flash using Odin (PDA section).
2. As KIES will only recognize and update official/stock ROMs available in/for your region, flashing any other ROM or kernel will prevent KIES from doing so.
But I don't care too. Flashing with Odin is very easy, fast and as stable as the ROM you are flashing.
I stick to the official/stock ROMs provided by Intratech - they have always doing fine for me.
3. I recommend the latest Frankenstein ROM, which is actually XWKJ1 (which I am running now).
It is Android 2.3.5, good balance between performance and battery life, excellent modem (XXKI3) and you can combine it with any other modem or CSC for your region and/or provider.
Just put this ROM in PDA, your modem in PHONE and your CSC in CSC section of Odin and flash all at once.
If you will find the descriptions and/or files helpful, please remember to push the Thanks button for Intratech and Chainfire, as they both do a great job for all of us.
Wow! It_ler - thank you for all the great info! Just a quick question. Does XWKJ1 have any issues. For example, does google video chat still work?
sooby77 said:
Wow! It_ler - thank you for all the great info! Just a quick question. Does XWKJ1 have any issues. For example, does google video chat still work?
Click to expand...
Click to collapse
I did not recognize any issue yet.
But Google Talk is without Video chat.
You can replace it with a leaked Talk app with Video chat enabled.
Just have a look here => http://www.redmondpie.com/how-to-install-google-talk-1.3-with-video-chat-on-any-android-phone-root-only/
But you have to use CWM recovery mode to install it.
I did not use ROM-Manager as described, I used CWM Manager (of CF-Root) to install it.
Please remember to wipe cache partition and dalvik cache as described.
And make a system backup before ... Just in case ...
Good luck!
Sent from my GT-I9100 using XDA App
It_ler said:
I did not recognize any issue yet.
But Google Talk is without Video chat.
You can replace it with a leaked Talk app with Video chat enabled.
Just have a look here => http://www.redmondpie.com/how-to-install-google-talk-1.3-with-video-chat-on-any-android-phone-root-only/
But you have to use CWM recovery mode to install it.
I did not use ROM-Manager as described, I used CWM Manager (of CF-Root) to install it.
Please remember to wipe cache partition and dalvik cache as described.
And make a system backup before ... Just in case ...
Good luck!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I was able to install XXKI3 radio. It didn't make a difference. Turns out that I needed to disable fast dormancy. The data connection seems more stable. I will have to test it out further on Monday. In regards to Frankensteinrom XWKJ1, is it already rooted?
If I discover problem on my end with that Frankensteinrom, can I flash back to official ROM without wipe? Thanks!
sooby77 said:
I was able to install XXKI3 radio. It didn't make a difference. Turns out that I needed to disable fast dormancy. The data connection seems more stable. I will have to test it out further on Monday. In regards to Frankensteinrom XWKJ1, is it already rooted?
If I discover problem on my end with that Frankensteinrom, can I flash back to official ROM without wipe? Thanks!
Click to expand...
Click to collapse
Neither official nor Frankenstein versions are rooted.
If you want to Root, follow the instructions of Intratech or Chainfire to do so.
You can flash back to an Official ROM.
If you want to flash without wipe, you have to use a non-wipe version.
So, no problem with most of the versions from Intratech's thread.
Sent from my GT-I9100 using XDA App
Hi guyz,
i tried to root my galaxy with CF-Root 4.2 because it was the first time i did it and it seemed the simplest and lightest (the 4.2 version includes only root and CWM) way to do it.
I paid attention in reading the Chainfire's indications and also the "noobs guide" but it wasn't enough...
I downloaded this version of CF-Root complying to my "stock" version ("stock" because i did the proposed update 2.3.3->2.3.4 from Settings->Device info->Software updates), i extracted the .tar and i used Odine (ONLY selecting the .tar file in the "PAD" module and checking "re-partition" was NOT flagged) to flash it.
Odine said the process was succesfully completed and the device restarted but it stopped at the black screen with "Samsung Galaxy S II GT-I9100" and the yellow exclamation point.
There were no ways to make it restart, i tried to re-do the process, to re-flash the original one (GT-I9100_ITV_I9100XWKI4, always complying to my device) but it stops at that damned yellow exclamation point!!
I've no idea of what to do, i'm quite depressed, do you suggest to re-try with another version? Should i try another flashing way? Did i do anything wrong? Could my galaxy be resuscitated?
Thanks in advance.
Regards,
Mark
P.S.: should be fun to know i did it from VBox and Odine caused two crashes of Windows XP(virtualized), then i shifted to Windows 7(virtualized)...could be better a linux flashing way? lol
ErVito said:
I downloaded this version of CF-Root complying to my "stock" version ("stock" because i did the proposed update 2.3.3->2.3.4 from Settings->Device info->Software updates)
Click to expand...
Click to collapse
Sounds like you flashed a 2.3.5 ki4 kernel on 2.3.4 firmware, no wonder it doesn't boot.
You can either go here and flash the stock firmware from your region or flash this rom through odin, its one of the few roms that i found that gets flashed through odin rather than cwm. If you look through the dev section im sure you'll find more roms that you can flash through odin.
Hi All Below I occidentally posted in the Galxy SI900 instead of here< I got the usual replies but was grateful all the same. Maybe someone might help before I revert to stock...
Hi all, I know this has been done and dusted but I am having problems with connecting to kies after rooting. I am running standard jelly bean 4.1.2 and is an Australian GT-I9100. I installed the siyah kernal root system and now all I get on kies is "connecting" Windows 7 recognises and I can access the phone via explorer on the PC. The phone after a while comes up with a message that there is no compatible software on the PC, install kies...
I have tried all the so called fixes including formatting the internal SD and memory. The only thing I did before it stopped connecting was the root and running Triangle away (paid version). I have enabled / disabled USB debugging. The only things I haven't tried is a factory reset which I don't really want to do as I am always sceptical that the backup apps will work after to restore everything.
Any help appreciated
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?p=45907982#post45907982
Hope someone can help...
Regards Ismael
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
jiseuo said:
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
Click to expand...
Click to collapse
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
IsmaelJones said:
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
Click to expand...
Click to collapse
Now I am not using KIES, because I use AOSP ROM (4.3 Slimbean), but in past, when i was using STOCK ROM (XWLSN, XWLSS) I used "PhilZ-cwm6 - Safe Stock Based Kernel" http://forum.xda-developers.com/showthread.php?t=1877270 to root my phone.
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
jiseuo said:
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
Click to expand...
Click to collapse
Okay had a look at this, thanks. I do have a question though, my Kernel (PDA) is XWLSH, I have downloaded the 2 files but I am wondering how to install? Do I use my CW recovery or do I have to revert back to stock? A little confusing as he dowsn't really give instructions and I am pretty much an amateur when it comes to some of these things? Also I am running JB 4.1.2 he only mentions ICS 4.0.4? Help appreciated here...
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
IsmaelJones said:
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
Click to expand...
Click to collapse
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
jiseuo said:
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
Click to expand...
Click to collapse
Hi Again, solved the problem... definitely the siyah root was the culprit. I used mobile Odin to install the stock kernel, once done checked and could connect in kies and was still rooted missing busybox only. After that I again used mobile odin to install philZ, again no problems and all seems fine now. Everything working.
Thanks a million for helping and also many thanks to mobile odin developers as this is a far better tool than most and saves connecting to the PC Odin. Also seems a lot safer...
:good:
Hi guys n girls,
I am sort of new to the Ace section here. I am doing a re-vamp of my mum's phone and said I would spruce it up a little. Shame there is no decent CM 9 versions that I can get working because of lack of RAM....the only one listed (no disrespect to the dev - thanks for making it available on such a low spec device!) but it doesn't work with my Optus GT S5830V (5830I) for some reason?
Anyway to my point, I have downloaded several versions of the stock firmware from Sammobile. The odd thing is that I cannot extract that firmware at all. Every archive program I have sees it as either being not an archive; corrupt or fails to extract it? So I am unable to make my own 4 part Odin recovery package. Making my own will save time; at the moment I have to flash the 4 part Odin (return to stock) package, then reboot into download mode again and then flash the stock firmware?
3 things I noted.
1). The device is not detected by the so called Odin specific for Ace and variants that uses an Ops type PIT file? The device is plugged in and all drivers upto date....it' just plain doesn't see it? It is however detected and flashable (albeit without an .ops file) using the 4 part package on Odin 3.07 made for my Galaxy S3?
2). I am unable to get any detection with EFS pro and it returns no PIT file?
3). All attempts to extract the stock Optus firmware package fail. I have removed the .MD5 file extension (only needed for preserving file naming conventions anyway - i.e. If you rename any .tar.md5 firmware package, in order to be able to flash it you need only to remove the .md5 from the end and leaving it as .tar and the firmware will flash without error. I digress.....What does someone suggest for me to being able to make my own firmware package based on stock?
First off, wrong section.
Jarmezrocks said:
Shame there is no decent CM 9 versions that I can get working because of lack of RAM....the only one listed (no disrespect to the dev - thanks for making it available on such a low spec device!) but it doesn't work with my Optus GT S5830V (5830I) for some reason?
Click to expand...
Click to collapse
1) We don't have a stable CM9 because our devs don't have the source code for all the drivers, not lack of RAM.
2) Have you formatted your system's partitions to the EXT4 filesystem? CM requires an EXT4 filesystem to operate.
Jarmezrocks said:
Anyway to my point, I have downloaded several versions of the stock firmware from Sammobile. The odd thing is that I cannot extract that firmware at all. Every archive program I have sees it as either being not an archive; corrupt or fails to extract it? So I am unable to make my own 4 part Odin recovery package. Making my own will save time; at the moment I have to flash the 4 part Odin (return to stock) package, then reboot into download mode again and then flash the stock firmware?
Click to expand...
Click to collapse
Jarmezrocks said:
3). All attempts to extract the stock Optus firmware package fail. I have removed the .MD5 file extension (only needed for preserving file naming conventions anyway - i.e. If you rename any .tar.md5 firmware package, in order to be able to flash it you need only to remove the .md5 from the end and leaving it as .tar and the firmware will flash without error. I digress.....What does someone suggest for me to being able to make my own firmware package based on stock?
Click to expand...
Click to collapse
The tar.md5 file has to split into the PDA, CSC, Modem and PIT files using Odinatrix. Search for it.
Jarmezrocks said:
3 things I noted.
1). The device is not detected by the so called Odin specific for Ace and variants that uses an Ops type PIT file? The device is plugged in and all drivers upto date....it' just plain doesn't see it? It is however detected and flashable (albeit without an .ops file) using the 4 part package on Odin 3.07 made for my Galaxy S3?
Click to expand...
Click to collapse
The Odin specific for Ace you stated above might be for GT-S5830. For the variants running the Broadcom BCM21553 the Odin version to use is v1.84. Odin v3.07 is more like a universal Odin that works on most devices.
Jarmezrocks said:
2). I am unable to get any detection with EFS pro and it returns no PIT file?
Click to expand...
Click to collapse
I don't know about this.
NightRaven49 said:
First off, wrong section.
Click to expand...
Click to collapse
Why? I was not actually asking for support as such, just sharing what I learnt/noticed.
NightRaven49 said:
1) We don't have a stable CM9 because our devs don't have the source code for all the drivers, not lack of RAM.
2) Have you formatted your system's partitions to the EXT4 filesystem? CM requires an EXT4 filesystem to operate.
Click to expand...
Click to collapse
Yes I am aware of that. I actually did attempt to flash the CM9 developer package several times all without result.
I tried many methods, firstly the conventional method and then several other unconventional methods. I first flashed CWM recovery 6.0.0.x (something around there) and that was ok but it could not detect the partitions....naturally I was on the standard firmware!
So I then flashed Thunder kernel which allowed recovery to see and mount all the partitions as well as prepare for a CM firmware flash. As I knew that CM required EXT4 I was prepared and flashed Rio's Ext4-RFS conversion script via Aroma in recovery. This worked very well. Only issue was that in doing so it corrupts the system partition and then I am unable to mount it anymore to flash CM.
Returning to stock or even attempting a nandroid restore from this point forward was fruitless as you can imagine. I tried several other combinations before retiring the idea. These included full system wipe after flashing CWM recovery (I figured maybe having data on the partitions its self could be interferring with the EXT conversion scripts? Everything seemed fine and ran correctly as expected only no system mounting.
I tried another method of flashing a ROM that included a kernel with it based on CM7 in the hopes that migrating to CM9 would be easier; this was not the case.
I picked a CM7 ROM that had a conversion script built in for BML to MTD. After returning to stock base via Odin I proceeded to flash recovery 6.0.0.x again, then I immediately flashed CM7 in the hope that I would kill two birds with 1 stone and have CM do its conversion on the fly as well as install (alleviating the need for mounting system after migrating to Ext4). This ROM installed without fault. All was well until I rebooted expecting to boot into CM7....this wasn't the case, I received bootloops like crazy. Naturally I booted into recovery (the ROM had downgraded me to version 5.x CWM recovery - that is fine anyway); I proceeded by clearing the caches and performing a factory reset (note This usually a good thing to do anyway regardless if you came from a clean reset factory firmware or not).
After doing this and rebooting the device reboots continuously as it did prior. I again decided to re-install the same zip as I am aware with changing to CM on many other devices it can sometimes require flashing 2-3 (and sometimes even 4) times for a firmware update to stick. Again still no response and forever bootloops. I decided at this point that if I was to waste the time and effort in Odin'ing back to stock AND THEN flashing my standard firmware that I should try another CM ROM.
I had CM9 available and even though half hour prior I was unable to mount the the system partition, I thought maybe that CM7 had been flashed first so if CM9 can see and mount partitions (like it should have originally) then I could flash CM9 in a hope that it might wipe out what ever was causing all the issues with bootloops.
CM9 installed correctly, however again I could not boot the device at all! I had read a post from a forum member's guide saying that if I got some of these issues that I should flash back to base and try it again. I did this another 3-4,5 times at least, various combinations of wiping base firmware, not wiping base firmware, wiping CM7; not wiping CM7......Always the end result = bootloops.
As you can imagine it was rather annoying if I was returning to base firmware (if I wanted to be stock carrier branded again I needed to flash twice, once to return to stock and again to flash Optus firmware.
Overall I was unable to get any firmware booting besides that which was provided as an Odin package AKA stock firmware. If I flashed a custom recovery over stock firmware I was unable to boot again. Oddly enough I found a standalone version of CWM recovery version 5 that was not CM specific and I performed a backup as it was able to see the stock partitions without throwing errors.
I then opted to do a conversion to EXT4 again and hoped that I could just restore my nandroid backup of the stock partitions like recommended in may of the guides for Galaxy Ace.
Unfortunately again I was unable to boot and the partitions become unmountable leading to yet again flashing back to base unbranded, then flashing stock carrier branded firmware (this has the correct modem for the carrier and region).
At this point I retired the idea of custom firmware. I will later root the device and just leave it on 2.3.7 and do internal/external SDcard swap and flash a theme and maybe a few compatible APKs from newer stock firmwares (at least ICS) to achieve the functionality I was hoping to have by flashing and using ICS. I found the best and most simplest way of achieving this was through Moto-Chopper Root method and adb, most of the documented ways of achieving root on the Ace don't work for the S5830V for some reason. So I will stick with what works.
NightRaven49 said:
The tar.md5 file has to split into the PDA, CSC, Modem and PIT files using Odinatrix. Search for it.
Click to expand...
Click to collapse
Thanks for the tip. :good: I have downloaded this ready now, so I will investigate how this goes? It looks very similar to a application I already use TAR.MD5_PACKAGER however I see it has an option for extracting from .tar.md5 files that have malformed header information. So that sounds like it should do the trick!:fingers-crossed: Do you think that this is maybe intensional as a means of stopping people like us from building custom firmware packages?
I mean the .tar.md5 package flashes perfectly as it should do which is very surprising seeming .md5 signature is very easily broken when you rename the file and you have not even opened it. That was what lead me to flashing it in the first place, I mean I figured that if the .tar.md5 was so corrupt as I believed it was, then the worst that can happen will be Odin will spit an error message and not proceed i.e. it won't even attempt to flash the said firmware!
Myself if I download any firmware that doesn't flash and fails due to md5 error, I immediately open it up and inspect it and unless it was extremely difficult to obtain (I have waited close to 30 hours once for an old firmware package to download from the only source I could find - but regardless if it was damaged or not I only wanted the old bootloader so I could integrate it into a new firmware package so the passing md5 was relatively unimportant), I would just re-download it again.
The fact that ALL of these packages for S5830I are like this (regardless of what browser or means I downloaded the package) and the fact that they DO in fact flash like normal packages, and the phone returns to 100% factory condition; tells me that this does look like a means of discouraging custom firmware developers? hmmm
NightRaven49 said:
The Odin specific for Ace you stated above might be for GT-S5830. For the variants running the Broadcom BCM21553 the Odin version to use is v1.84. Odin v3.07 is more like a universal Odin that works on most devices.
Click to expand...
Click to collapse
The device is actually a S5830V...the V devices are relatively undocumented, but they are essentially just the same as the more common i/M variants. I did my homework first with this, and I can most certainly attest that it is NOT the S5830. I wouldn't attempt flashing S5830 firmware, also S5830i firmware boots and functions as normal and has signal albeit not so strong when the modem is not for our carrier and/or region, but function none the less.
NightRaven49 said:
I don't know about this.
Click to expand...
Click to collapse
Well give the fact that I had performed so many download of firmware that I initially believed to be corrupt I was unable to extract the PIT (or in the case of the generic Ace OPS file) from the firmwares.
Being the fact that there was little known about the S5830V I was unsure if to proceed of not? There are few reports on the device and most of them were of owners bricking their device, only 1 report I know of where a V owner claimed he flashed S5830i firmware without a hitch, again he was not from Australia where I am from, so I was flying blind and scared I was going to brick the device.
At the very least if I had a PIT file I could analyse it and could manually make image backup of the EFS/IMEI partition straight after rooting the phone. I have looked already at scripts that scan the whole emmc and I hit a snag when the kernel I am using is not insecure i.e. adb cannot run as root. I have root and confirmed with root checker app but terminal emulator and/or command line are unable to obtain root
Anyway to shed some light for you EFS Pro is a means of doing this that works on most Samsung devices....just not the Ace as far as I can tell.
Yes I am already aware that there is Galaxy Toolbox and I had actually gone ahead and done all that already,but an incident more recently where I had a device I was repairing with a wiped IMEI and it actually refused to boot. This becomes a hassle when restoring the IMEI cause in order to have Galaxy Toolbox you need to be booted and rooted. I wasted a whole day repairing the IMEI. So pretty much the message here is what good is Galaxy Toolbox to me restoring the IMEI if it can't boot? NONE!
I contacted the developer weeks ago and explained my situation and he is still yet to respond. I explained that I had a V variant of the Ace and wanted to ensure I had all bases covered. I requested information on how I could open the IMEI manually outside of the Galaxy Toolbox in the case that it would not boot (as this was how I restored the other device last week and it worked), unfortunately I am still yet to hear a response form him? Slack.
When I obtain this information I will share it here on XDA in the hopes that people in Australia with this variant will search and find some info on it. This is also why I am making this post here so detailed for folks like me who have been searching fruitlessly for answers.
My thoughts are that maybe there is something still not 100% the same between the i and the V because all custom firmwares I tried made for the S5830i never worked?
There is maybe an issue with how they are scripting their installs that is causing issues, but it is worrying enough that flashing so far has lead to partitions becoming corrupted very easily. I have had this before with my own phone more recently because a dev made a simple mistake in an updater script that called an explicit partition by mounting point ID and not by a more generic mounting point like "/system", "system" which lead to lost IMEI and bricked phone.
I am not blaming the dev though because it is easy to assume that a even though the mounting was non-specific for my device and the partition being called was not actually the EFS, it should not have corrupted my EFS....but that is not true, so a discovery was made and a lesson learned from all this. I managed to revive my device and it lived to fight another day, but simple mistakes made in ignorance or lack of information can still be costly mistakes. Need I say more.
I will report back when I have got a proper partition map for the S5830V and all will be happy days
I don't feel like quoting anymore, but I do spot some anomalies.
1) ...we don't have CWM 6.0.0.x. Are you sure you used the 5830i CWM, not the 5830?
2) I was referring to some other version of Odin when you said the Odin version specific to Ace. Which version were you using then?
3) I don't see how rio's multi-formatter can render the system partitions unmountable. In that case try lopicl.00's EXT4 formatter. Go search for it. After formatting flash Biel's Specific Basic kernel.
also you were asking a question, so naturally this should be in Q&A.
I bought a Samsung Galaxy II GT-I9100P today and I want to update the software (currently rocking Android 2.3.6) and install Cyanogenmod. Bearing in mind that this is my first foray into the Android World (though I would say I am fairly tech savvy) would you be able to direct me to some resources for achieving this. Also please note that I only have a mac (therefore I believe I will be using Heindall) and there is no possibility of borrowing, bootcamping or emulating a Windows partition.
Thanks
poliosynthesis said:
I bought a Samsung Galaxy II GT-I9100P today and I want to update the software (currently rocking Android 2.3.6) and install Cyanogenmod. Bearing in mind that this is my first foray into the Android World (though I would say I am fairly tech savvy) would you be able to direct me to some resources for achieving this. Also please note that I only have a mac (therefore I believe I will be using Heindall) and there is no possibility of borrowing, bootcamping or emulating a Windows partition.
Thanks
Click to expand...
Click to collapse
You should update your device first to the latest official firmware (4.1.2) either by using OTA updates or Kies to update your device. That way the installation process will go more smoothly.
regards, gsstudios
gsstudios said:
You should update your device first to the latest official firmware (4.1.2) either by using OTA updates or Kies to update your device. That way the installation process will go more smoothly.
Click to expand...
Click to collapse
OTA does not appear to be working, the phone seems to believe that it has no available updates. Would you be able to send me some resources for updating the phone manually?
poliosynthesis said:
OTA does not appear to be working, the phone seems to believe that it has no available updates. Would you be able to send me some resources for updating the phone manually?
Click to expand...
Click to collapse
Download and install Samsung kies for mac, connect your phone to your Mac, select update firmware in kies.
Please let me know if this doesn't work, so I can give you next set of instructions.
Regards, gsstudios
gsstudios said:
Download and install Samsung kies for mac, connect your phone to your Mac, select update firmware in kies.
Please let me know if this doesn't work, so I can give you next set of instructions.
Regards, gsstudios
Click to expand...
Click to collapse
I downloaded Kies and finally managed to get it to connect to my phone, however the upgrade progress bar sticks at 0%. Is it possible to download the firmware independently of Kies and try to load it then? If not what do you recommend instead?
poliosynthesis said:
I downloaded Kies and finally managed to get it to connect to my phone, however the upgrade progress bar sticks at 0%. Is it possible to download the firmware independently of Kies and try to load it then? If not what do you recommend instead?
Click to expand...
Click to collapse
Firmware update can not be downloaded separately in Kies. Instead, you could try using jodin (google it) to flash the firmware downloaded from sammobile.
Have a look at this post I posted earlier this week: http://forum.xda-developers.com/showpost.php?p=64214982&postcount=2
Instructions should be similar for application use. As you can tell, it's harder to flash roms in Mac OSX.
Regards, gsstudios.
gsstudios said:
Firmware update can not be downloaded separately in Kies. Instead, you could try using jodin (google it) to flash the firmware downloaded from sammobile.
Have a look at this post I posted earlier this week: http://forum.xda-developers.com/showpost.php?p=64214982&postcount=2
Instructions should be similar for application use. As you can tell, it's harder to flash roms in Mac OSX.
Regards, gsstudios.
Click to expand...
Click to collapse
Managed it at last! What now?
poliosynthesis said:
Managed it at last! What now?
Click to expand...
Click to collapse
Now you need to root your device using CF auto root by chainfire or Framaroot. Or you can install custom kernel like siyah kernel on your device (make sure to choose the right version otherwise your phone will bootloop).
- Download required cyanogenmod version (11 or 12.1 in this case) onto your phone
- Download Siyah kernel onto your phone
- Flash custom kernel via jodin (Select under PDA, tick auto-reboot, un-tick repartition)
- Wait for your phone to boot into OS. If it doesn't, you flash the wrong version
- After back into os, check if you have root. There should be SuperSU or Superuser app in your app drawer
- Download kitkatcompatible recovery such as Philz recovery or a kernel like DorimanX 10.XX onto your phone
- Reboot into recovery mode
- Flash kitkatcompatible recovery such as Philz recovery or a kernel like DorimanX 10.XX
- Reboot recovery (not phone, in advanced menu). If it prompts to fix root, just select yes. If it prompts to install root, select no.
- Factory reset, wipe system, cache while in new recovery
- Install cyanogenmod
- Reboot system/device
If you were unaware, if you flash any roms for the i9100 international edition, you will lose nfc.