Hi, I was using stock ROM from my operator CLARO Argentina, and about a week ago I decided to try newer ROM from Samfirmware... big mistake because I flashed European ROM and lost 3G and GPS. I don't care much about the 3G actually since 2G works, slow but fine. What I really need is GPS and I can't understand why it doesn't work since it should work globally, it doesn't depend on local frequency bands like 3G.
Now I have:
PDA: I5510XWKD4
PHONE: I5510XWKD1
CSC: I5510LCTIJK2
I've tried every configuration, fix app, doctor and optimization available in market and also some manual tweaking on the phone but nothing... it doesn't even see the satellites in GPSTest. So I think it goes deeper, maybe something driver related? Anyway I've come up with a few possible causes and solutions I would like to ask for your help and experience to figure out if they're reasonable and your opinion on whether they could work or not.
1. Driver related, compile own kernel from opensource.samsung.com and reflash only boot.img (Have all the tools, now learning how to do this) Q: could I brick my phone beyond repair by flashing my own compiled kernel?
I found a few differences between callisto_rev03_defconfig from I5510L and I5510 which I will list but none seem related to the GPS... it seems they apply to storage.
Also I found out that the GPS is integrated into the Qualcomm MSM7X27 chip which both phones have so I'm starting to feel drivers are not the issue here... This is getting disturbing, it seems that none of the model differences have to do with the GPS so... it should work with no problems...
Extra lines in config for I5510L:
Code:
#Derek:Added for Latin Kernel Feature:2010.08.20
CONFIG_SAMSUNG_LTN_COMMON=y
CONFIG_SAMSUNG_LTN_B=n
CONFIG_SAMSUNG_LTN_L=y
I5510L:
Code:
# LinuStoreIII Flash Devices (FSR)
#
CONFIG_RFS_FSR=m
CONFIG_RFS_FSR_STL=m
CONFIG_RFS_STL_DELETE=y
I5510:
Code:
# LinuStoreIII Flash Devices (FSR)
#
#@CONFIG_RFS_FSR=m
#@CONFIG_RFS_FSR_STL=m
#@CONFIG_RFS_STL_DELETE=y
I5510L:
Code:
# Samsung Param support
#
CONFIG_MSM_PARAM=m
I5510:
Code:
# Samsung Param support
#
#@CONFIG_MSM_PARAM=m
I5510L:
Code:
# RFS Filesystem
#
CONFIG_RFS_FS=m
I5510:
Code:
# RFS Filesystem
#
#SCONFIG_RFS_FS=m
I5510L:
Code:
# RFS Core Filesystems
#
CONFIG_RFS_FS_CORE_FAT=m
CONFIG_RFS_FS_FAT_VFAT=y
I5510:
Code:
# RFS Core Filesystems
#
#@CONFIG_RFS_FS_CORE_FAT=m
#@CONFIG_RFS_FS_FAT_VFAT=y
2. App related. I notice there are a few apps that seem related to GPS/location, maybe restoring one of this apps could help? I have Ti backup from before flashing, but don't know exactly which apps could be responsible. Haven't tried this yet.
3. I read in a few places that radio.img could be responsible for both 3G loss and GPS loss, is there anyway to get this radio from somewhere? Perhaps another phone? Remember I have i5510L which is slightly different from plain i5510.
NEW Perhaps replacing system.rfs from original rom into KD4 pda and then reflashing could shed some light whether it's app related or not... is it too dangerous for the phone to do this?
That's all I can come up with now, any help would be greately appreciated. Also if someone knows where to get original firmware would be welcome too. I took my phone to service but they still haven't received samsung repair box so they told me I just have to wait
from what i know amss_phone has the phone's radio.So you will need the amss of your country/carrier.(I was wrong I guess ).
Can you achieve root in recovery mode ?
If yes I can flash Clockworkmod recovery .
http://forum.xda-developers.com/showthread.php?t=831725&page=2
karandpr said:
from what i know amss_phone has the phone's radio.So you will need the amss of your country/carrier.(I was wrong I guess ).
Can you achieve root in recovery mode ?
If yes I can flash Clockworkmod recovery .
http://forum.xda-developers.com/showthread.php?t=831725&page=2
Click to expand...
Click to collapse
radio seems promising since kernel doesn't unfortunately I don't have and haven't found anywhere Odin files for i5510L. But a fellow member of XDA kraka23 was smarter than me and has dumps of all the partitions on his phone. Do you have an idea which partition could be radio.img? If so, I could ask him for it.
On the recovery side, I have no clue... sorry. I don't even know how to check if I have root in recovery, but I'm willing to learn and help... if you are patient with me.
I wouldnt do that .
One wrong move and you could blow off your phone.
Yes flashing partition is dangerous cos there have been instances where people blew off the download/recovery mode.
Thanks for the heads up! That sucks then because Odin files for my original rom are nowhere to be found
Update: I restored as many apps that I could find that seemed related to GPS from my Ti backup but didn't work either... I'm starting to feel hopeless here. I just hope they get the samsung box soon in the service bc it's looking like my only hope... well that or gettin' insurance for it and then making it "sleep with the fishes" (won't actually do that of course)
NEW Perhaps replacing system.rfs from original rom into KD4 pda and then reflashing could shed some light whether it's app related or not... is it too dangerous for the phone to do this?
Well I dont think it will help.
If the radio is in amss file ,how will replacing system.rfs help ?
It wont be dangerous via odin.
Using dd to replace parts is risky and currently we have only 4-5 motivated people losing one will be 20 p.c. damage to the work force ..
Well the care centre in ur area.Be chummy with the dude who is inside .You might be able to wrestle the four files when they receive the "kit".
Edit 1 : I was reading disclaimers on samfirmware and they said that replacing cross continent firmwares may result in loss of 3G connections
Yes I knew there was a chance to mess up 3G but I thought it would be fixable... and it doesn't matter that much to me. But the GPS loss is really weird. I reflashed the firmware to rule out an odd flashing error but it still doesn't work...
I meant flashing a system.rfs to see if Apps were the problem. If I do get radio.img somehow and merge it with KD4 rom and flash with Odin, would that be safer?
GPS is a kind of radio.
I dont think so radio.img will help .You will require CM recovery and it doesnt work on samsung phones.
Yeessssssssssssssssssssss!!!!! I Fixxx the GPSSSSSSSSSSSSS!!!!!!!!!!!
Same problem that splattx_x1!. I lost the GPS after flash the KD4 rom...
Here the solution:
Download this file:
megaupload.com/?d=0BHWKAJ1
This is amss_phone from I5510TVJKD1 brasilian rom!!!!. I came to test with brasilian radio and Eureka!!!! the GPS is back!
I hope I can help if some Latin American countries. I'm from Argentina
Cheers!!!!!
EDIT: I forget the instructions!!
Flash this file with Odin. JUST ONLY THIS FILE (amss_phone)
In the PHONE buttom in Odin, select the "amss_phone_brasil.tar" file an flash it!. I repeat ... ONLY THIS FILE!!
This is awesome news for Latin american users of Galaxy 551, unfortunately I was not very patient and went to my provider and changed my phone. Now I have a galaxy mini... (my phone also kept freezing and shutting down).
But great great news!!! Congrats!!
Did you have this entire package? I5510TVJKD1 ?
dneto said:
Did you have this entire package? I5510TVJKD1 ?
Click to expand...
Click to collapse
Not sure why are you asking that but I guess it's posted in the wrong thread... This thread should be closed since the issue seems to be solved by kraka23
but have a look here:
http://forum.xda-developers.com/showthread.php?t=1032437
splattx_x said:
Not sure why are you asking that but I guess it's posted in the wrong thread... This thread should be closed since the issue seems to be solved by kraka23
but have a look here:
http://forum.xda-developers.com/showthread.php?t=1032437
Click to expand...
Click to collapse
Hi splattx_x,
Sorry for my badly english. My question is about the entire package from I5510TVJKD1 ROM.
PDA, PHONE, CSC.
I´m from Brazil, and having problems with this device. My screen is unresponsive when in charger and freezing. =/
I already tried update or change another version. But now I want revert to Original combination, like new. My original version was I5510TVJKD1
You talk about part (amms) from this version, i think you have entire package.
Thanks for you support.
dneto said:
Hi splattx_x,
Sorry for my badly english. My question is about the entire package from I5510TVJKD1 ROM.
PDA, PHONE, CSC.
I´m from Brazil, and having problems with this device. My screen is unresponsive when in charger and freezing. =/
I already tried update or change another version. But now I want revert to Original combination, like new. My original version was I5510TVJKD1
You talk about part (amms) from this version, i think you have entire package.
Thanks for you support.
Click to expand...
Click to collapse
Ok. Go to the link in my previous post and there's a software to download official ROMS try to see if you can find it there. Still wrong topic since this was only GPS related
kraka23 said:
Yeessssssssssssssssssssss!!!!! I Fixxx the GPSSSSSSSSSSSSS!!!!!!!!!!!
Same problem that splattx_x1!. I lost the GPS after flash the KD4 rom...
Here the solution:
Download this file:
megaupload.com/?d=0BHWKAJ1
This is amss_phone from I5510TVJKD1 brasilian rom!!!!. I came to test with brasilian radio and Eureka!!!! the GPS is back!
I hope I can help if some Latin American countries. I'm from Argentina
Cheers!!!!!
EDIT: I forget the instructions!!
Flash this file with Odin. JUST ONLY THIS FILE (amss_phone)
In the PHONE buttom in Odin, select the "amss_phone_brasil.tar" file an flash it!. I repeat ... ONLY THIS FILE!!
Click to expand...
Click to collapse
Hi, i update my i5510l to ginger and my gps dont sync never... I do this but the phone after this dont boot. Do you know what is the problem?
This solution its only for Froyo!. I dont have gps in Gingerbread too. Try reflashing gingerbread. For more info check this blog:
galaxy551.wordpress.com
kraka23 said:
Yeessssssssssssssssssssss!!!!! I Fixxx the GPSSSSSSSSSSSSS!!!!!!!!!!!
Same problem that splattx_x1!. I lost the GPS after flash the KD4 rom...
Here the solution:
Download this file:
megaupload.com/?d=0BHWKAJ1
This is amss_phone from I5510TVJKD1 brasilian rom!!!!. I came to test with brasilian radio and Eureka!!!! the GPS is back!
I hope I can help if some Latin American countries. I'm from Argentina
Cheers!!!!!
EDIT: I forget the instructions!!
Flash this file with Odin. JUST ONLY THIS FILE (amss_phone)
In the PHONE buttom in Odin, select the "amss_phone_brasil.tar" file an flash it!. I repeat ... ONLY THIS FILE!!
Click to expand...
Click to collapse
Amazing how you fixed this, it tried it too but i couldnt do it. Is your phone rooted?. I also first updated the firmware to gingerbread 2.3.6, and after it, gps never works.
I am from Venezuela, not Argentina, but just maybe the solution is similar.
I tried your fix but it says "an unnamed file was not found", any clue?.
The message box said.
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<0> Destroy instant..
<0> Killed timer
Thanks in advance
UPDATE: Yeah, caught the answer, didn't see it at first, my mistake...
did you also fix the 3G or is that still on the fritz?
Chef Central is NOT a mobile phone helpdesk. Besides, OP changed his phone.
Closed.
Related
Phone: LG P500h - ANDROID v 2.2.1 buildnumber FRG83.
Country: Brazil
Anyway, what I know is that i have to downgrade it to 2.2 in order to be able to root. I've looked through a bunch of tutorials on a bunch of websites but there are a few questions i have about the process that isn't answered anywhere i've looked.
Apparently downgrading requires me to get a stock ROM from LG, there is a topic here for that but it does not have the right ROM for my country, i tried a couple codes but they all got me 404.
Can I just flash any standard ROM from, US maybe, will it work?
And if yes, how do I flash it? Apparently you can do that by booting into recovery mode, but to get there you need it to be rooted which I can't do.
I've read about KDZ and downloaded that but... it crashes a lot in my PC (whenever i try the Read Device) it gives me error and closes the program (windows program not responding dialog).
I'm afraid it might crash in the middle of it if i try flashing and that would brick my device.
Is there a simple way to flash a new ROM? Is that the first thing I have to do in order to get a custom ROM say Ubuntdroid? It says I need a new recovery... but for that I need to downgrade first? It's a lot to do... and I don't really get the order in which I should do it all in...
Can somebody post me a little "do this, then do that, then finally do that" so that I can understand it all finally?
Thanks in advance, and sorry for long post, was trying to be as informative as possible.
This shows what happens when I try reading the phone on KDZ... also a little part showing that I got my device to be recognized by windows...
also disabled the LGE modem on device manager, read that if I don't it'll get bricked.
Well it won't let me link the image so... just paste the name together.
www
novasite.com.br
/1.jpg
1. Find a suitable v2.2 stock ROM for flashing (link)
2. Use KDZ to flash it (I am not aware of another tool capable of doing that). Try doing that on a PC running Windows XP (important - that's where you're stuck now and I guess you're using Windows 7).
3. Root your phone - search for "z4root" on Market, install it.
4. Install Custom recovery, which will replace your current (stock) recovery mode (link - you may need to create an account on another forum in order to download).
5. Using Custom recovery you can now install any custom ROM and create nandroid backups to restore your phone to a certain (working) state.
You will have to use KDZ again if you ever want to flash a stock ROM, also losing the custom recovery. But you will have no reason to do that, except if you need to take your phone to some warranty repairs.
Good luck!
NEW PROBLEM: About step 1... i finally found a way to get my country's rom, but... it's.. the same thats on my device right now, it says V10a_02 and thats the same on my phone (the kdz read phone tells me that) so... won't I just be flashing the same 2.2.1 again?
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500H/ABRABK/V10A_02/V10A_02.kdz <---- the rom the topic tells me to get.
How do I know what version of android is in that rom? and if i can't, can you link me to a rom that does?
I found one from another country that the guy said is 2.2... but... will it work if i flash that one? does it HAVE to be for my country? also my model is p500h (the h) is it different from the p500 (different as in flashing p500 without h roms on it will kill it?)
As for flashing it...
I think maybe a computer with win xp will do the trick for kdz.
i've found this post today:
http://forum.xda-developers.com/showthread.php?t=944881
is it better to use that than kdz? theres no replies on topic saying "hey it worked" so i'm a little worried, but apart from a few errors it seems to work on my win 7....
i guess the reply would be "i only know kdz, do it with kdz" but i thought i might ask...
Indeed, I have not tried that method and therefore I can't recommend it. At least KDZ is successfully tested. If you are patient enough to wait for some replies either here or in that topic, you may find out if it works. I would recommend it only if you have no other choice, like if you're unable to try KDZ on an XP machine.
In the mean time, I remembered that a newer version of Custom recovery is available (v1.2) - here. But you still need to download a file and read the tutorial from that other forum I mentioned in the previous post.
what about the first part of the post? i think i might have added that after you replied i don't know... asking about the rom i found if it isn't the same i have on my phone. and asking if i can just add another country's one...
edumazieri said:
Phone: LG P500h - ANDROID v 2.2.1 buildnumber FRG83.
Country: Brazil
Anyway, what I know is that i have to downgrade it to 2.2 in order to be able to root. I've looked through a bunch of tutorials on a bunch of websites but there are a few questions i have about the process that isn't answered anywhere i've looked.
Apparently downgrading requires me to get a stock ROM from LG, there is a topic here for that but it does not have the right ROM for my country, i tried a couple codes but they all got me 404.
Can I just flash any standard ROM from, US maybe, will it work?
And if yes, how do I flash it? Apparently you can do that by booting into recovery mode, but to get there you need it to be rooted which I can't do.
I've read about KDZ and downloaded that but... it crashes a lot in my PC (whenever i try the Read Device) it gives me error and closes the program (windows program not responding dialog).
I'm afraid it might crash in the middle of it if i try flashing and that would brick my device.
Is there a simple way to flash a new ROM? Is that the first thing I have to do in order to get a custom ROM say Ubuntdroid? It says I need a new recovery... but for that I need to downgrade first? It's a lot to do... and I don't really get the order in which I should do it all in...
Can somebody post me a little "do this, then do that, then finally do that" so that I can understand it all finally?
Thanks in advance, and sorry for long post, was trying to be as informative as possible.
Click to expand...
Click to collapse
First backup your data, then download a factory ROM, it doesn't matter which version u download, what matters is the version. Make sure that it's 2.2 and not 2.2.1 or 2.2.2. Follow all the below steps without skippin any, no matter how simple or stupid they are.
Link for shipped ROM - http://forum.xda-developers.com/showthread.php?t=865479
Now download KDZ updater and uncompress it
http://www.4shared.com/file/UleS4dP3/KDZ_FW_UPD_EN.html
Install msxml.msi from the uncompressed directory
Charge your battery to almost full state (I'm not sure, but it can be reason if phone doesn't start)
Turn phone off somehow (remove battery etc.)
Install drivers properly
Get rid of all usb drivers like Nokia, microsoft visual ++ run time environments
Install the LG drivers by selecting the update manager from the lg site
Disable LGE Virtual Modem. In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.
Press and keep pressed "Volume up"+"Return" and connect USB cable to phone
Yellow screen with text emergency mode should appeared
Shake the handset (I know, it sounds ... strange, but it helps for ones, so... why don't try it?) UPDATE: Read some quotes on bottom.
Run KDZ_FW_UPD.exe (Has administrator).
Select Type : 3GQCT (I have one report that CDMA mod works too)
Select PhoneMode : DIAG (in case of fail try EMERGENCY, and as last chance use CS_EMERGENCY)
I Recommend do not switch phone off. There was some people, which done it and after they was not be able to turn it on again. If flashing failed, just select some another mode and try it again, again, try shake/connect disconnect, again, again....
In KDZ file : Choose the ROM file you downloaded in the first step
Press Launch software update
Shake the handset (I know, it sounds ... strange, but it helps for ones, so... why don't try it?) UPDATE: Read some quotes on bottom.
Now Root it via Z4root - http://forum.xda-developers.com/showthread.php?t=833953
Then install custom recovery - http://forum.xda-developers.com/showthread.php?t=844483
Then download n flash any ROM of your choice, I wud sugget install Void or LOL.
Edit :- By the time I replied, many have already replied. Anyways you can check my reply too :-D
Mithun.
"it doesn't matter which version u download, what matters is the version."
does that mean it doesn't matter what country or operator the rom is for, as long as it is android version 2.2?
i have one from portugal (not my country) and that one is made for P500 mine is P500H... if that makes a difference i don't know, but i do know that rom is android 2.2. can i flash that one?
i also have one that i got from that topic following the instructions of putting my serial number, it linked me to a rom V10A_02... on KDZ when i try to read my device it says i have V10A_02 too. isn't that the same one i have now? with android 2.2.1? if it is it's very pointless to flash the same rom already in it.
any way to check?
because that is my last doubt ;p
edumazieri said:
"it doesn't matter which version u download, what matters is the version."
does that mean it doesn't matter what country or operator the rom is for, as long as it is android version 2.2?
i have one from portugal (not my country) and that one is made for P500 mine is P500H... if that makes a difference i don't know, but i do know that rom is android 2.2. can i flash that one?
i also have one that i got from that topic following the instructions of putting my serial number, it linked me to a rom V10A_02... on KDZ when i try to read my device it says i have V10A_02 too. isn't that the same one i have now? with android 2.2.1? if it is it's very pointless to flash the same rom already in it.
any way to check?
because that is my last doubt ;p
Click to expand...
Click to collapse
Yes.... you can choose any country. I tried the Australian version. Use the below one http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/AAUSBK/V10a_00/V10A_00.kdz
edumazieri said:
what about the first part of the post? i think i might have added that after you replied i don't know... asking about the rom i found if it isn't the same i have on my phone. and asking if i can just add another country's one...
Click to expand...
Click to collapse
As far as my knowledge goes, the LG P500h you have is the same phone as the P500, only branded for Telus. The hardware should be identical, therefore you may use any ROM designed for the P500 family.
The only thing you may miss if you install a ROM not customized for a Brasil (or South America) network operator is the internet acces point name, thus rendering your phone unable to acces the internet trough its data service connection, but only trough WiFi. Nevertheless, the phone's APN can be configured manually, all you need are the correct settings from your mobile operator and you're good to go.
Ok since you guys told me i can go ahead and flash any country ROM i just did and now my device burst into flames and then the flames consumed my apartment.
ok, not. it worked too well actually, i did the kdz procedure on my win 7 anyway, despite the errors when reading device info, and it took like, 1 minute, rebooted, took like 2 minutes on the android screen then it came back, with all my data still there... i thought it didn't do anything but... its now version 2.2
i tried z4root, worked ... got the superuser app and.... i'm happy ^^ thaaaanks!
anyway about the custom recovery thing..
i'm going to install the one in that post you gave me...
but i read something about the best one being clockwork something...
shouldn't i go ahead and install that one?
or can i do everything i need with this one you guys linked?
edumazieri said:
Ok since you guys told me i can go ahead and flash any country ROM i just did and now my device burst into flames and then the flames consumed my apartment.
ok, not. it worked too well actually, i did the kdz procedure on my win 7 anyway, despite the errors when reading device info, and it took like, 1 minute, rebooted, took like 2 minutes on the android screen then it came back, with all my data still there... i thought it didn't do anything but... its now version 2.2
i tried z4root, worked ... got the superuser app and.... i'm happy ^^ thaaaanks!
anyway about the custom recovery thing..
i'm going to install the one in that post you gave me...
but i read something about the best one being clockwork something...
shouldn't i go ahead and install that one?
or can i do everything i need with this one you guys linked?
Click to expand...
Click to collapse
Glad that it worked Install the Amon_RA's recovery!!! Many ROM's for OO won't support clock work I suppose. Amon RA's recovery is neat, I've been using that from the time I had an HTC tattoo.
For your Custom Recovery.... http://androidforums.com/getitnowma...ry-optimus-one-p500-thunderg.html#post1896517
edumazieri said:
anyway about the custom recovery thing..
i'm going to install the one in that post you gave me...
but i read something about the best one being clockwork something...
shouldn't i go ahead and install that one?
or can i do everything i need with this one you guys linked?
Click to expand...
Click to collapse
You can do anything you need with ThunderG. Now that version 1.2 supports backup and restore of ext4 partitons (a feature you don't need if you don't plan on installing a custom ROM... but you will, eventually ), it is complete.
Moreover, in ClockworkMod's first topic says: "This recovery will not allow you to flash every ZIP file". ThunderG does, if you choose to allow flashing of unsigned zip files. Sometimes this is useful.
Peeeeeerfect
Recovery installed, LOL ROM installed, all fast smooth and error-free.
no more screen touch lag, it's soooooo much faster now, overclocked, i have yet to test my emulators but i can only guess they're gonna be at least 150% better lol.
thank you all very much for taking the time to help me ^^
ONE LAST QUESTION: I PLAN ON BUYING A NEW SD CARD, JUST PLUG IT IN AND IT'LL FORMAT THEN CREATE THE NEEDED FILES THEN I INSTALL STUFF BACK ON IT, SIMPLE AS THAT?
Simple as that =D
Although there are some criteria with the sd card or you'll get unmounting problems.
Use a class 4 or higher card
format with fat32
I've never officially tried this method but its apparently supposed to help
allocation unit size: 64kb when you're formatting
edumazieri said:
Recovery installed, LOL ROM installed, all fast smooth and error-free.
no more screen touch lag, it's soooooo much faster now, overclocked, i have yet to test my emulators but i can only guess they're gonna be at least 150% better lol.
thank you all very much for taking the time to help me ^^
ONE LAST QUESTION: I PLAN ON BUYING A NEW SD CARD, JUST PLUG IT IN AND IT'LL FORMAT THEN CREATE THE NEEDED FILES THEN I INSTALL STUFF BACK ON IT, SIMPLE AS THAT?
Click to expand...
Click to collapse
So, how does it goes?!
I´m brazilian too, got a brand new LG Optimus One from ViVo, and a want to know if you´re having any troubles with conections, calls, internet, 3G etc.
OK, id did the flash
I´m afraid that if flash any custom rom, it will break or cause any misfuncition of the 3g service.
Any idea?!
== Updated
Ok, I´ve flashd it with KDZ and the log show´s thats all ok
"14:34:45 : ===FINISHED=== "
BUt its taking like FOREVER to start... almost 30min on android screen. Is this normal?! Should i restart the phone?!
leave it some more time , try shaking it ...
shake trick sometimes helps
Help please..
I did as instructed in the step to step procedures. kdz posted finished but my phone is still at the yellow screen..i did shaking but nothing happens..Is this normal?..SHould i wait..
My samsung galaxy II is constantly losing network but when I put my SIM into my old phone it works fine. I've tried everything I could find on here i.e roooting, upgrading to ICS but have had no luck.
I bought (well I paid out his contract) the phone from a friend who moved overseas and he was on a different network (Optus) and I'm on Vodafone but my SIM works (just not all the time! ) so I don't know if that has anything to do with it! Anyways I wont take it back to Optus because I wasn't their client to begin with and Vodafone wont help,
Any help is much appreciated as I'm really frustrated! Thanks for reading :laugh:
Safixia said:
My samsung galaxy II is constantly losing network but when I put my SIM into my old phone it works fine. I've tried everything I could find on here i.e roooting, upgrading to ICS but have had no luck.
I bought (well I paid out his contract) the phone from a friend who moved overseas and he was on a different network (Optus) and I'm on Vodafone but my SIM works (just not all the time! ) so I don't know if that has anything to do with it! Anyways I wont take it back to Optus because I wasn't their client to begin with and Vodafone wont help,
Any help is much appreciated as I'm really frustrated! Thanks for reading :laugh:
Click to expand...
Click to collapse
Is your phone rooted? If yes try flashing a new modem.. NELP3 works fine..
If not it's most probably a network issue
HElp?
arunreturns said:
Is your phone rooted? If yes try flashing a new modem.. NELP3 works fine..
If not it's most probably a network issue
Click to expand...
Click to collapse
Thanks, I do belive it is rooted, I didnt do it myself but it was done by the previous owner. Sorry to sound like a noob but how do I flash a new modem and where do I get NELP3 Thanks again
Safixia said:
Thanks, I do belive it is rooted, I didnt do it myself but it was done by the previous owner. Sorry to sound like a noob but how do I flash a new modem and where do I get NELP3 Thanks again
Click to expand...
Click to collapse
Even I had a similar problem a while back, any SIM card, would loose signal completely only on the SII turns out it was a hardware issue, I had to give in my phone to the service center.
To flash a modem if you have heimdall installed, open up the command prompt/terminal in the directory where you have downloaded the modem and extracted the modem.bin file, and type in
heimdall flash --modem modem.bin
or you can use the GUI it has an option for modem, but the modems aren't universally good for everyone, they are region specific, in my country [India] I use the DDKL1 modem, you should look for some modem that's native to your region.
OK. What you need to do is read the Stickies & brush up on Android/SGS2 basics.
Secondly, if the phone is rooted & you have CWRecovery (boot into recovery by turning the phone off, then holding power/volume up/home buttons), you can easily flash modem packages.
I'm also using Voda AU, so I'll get you started. The famous DUKJ1 modem has worked well for many people using Voda in Australia. Unfortunately, XDA doesn't seem to want to allow me to attach files to forum posts at the moment, or I would have attached a copy of KJ1 to this post. Sooo....Here's a link where you can get it
Also, if you do a Google search along the lines of "XDA SGS2 modems" or similar (use your imagination), you should find plenty of posts from here which have links to modems you can flash if KJ1 doesn't work well for you. If that is the case (it doesn't work well for you), then it's a matter of flashing as many modems as you have to in order to find one that works well for you.
The issue could also be caused by the gear/spectrum Voda is using in your area (hence your sim works well in another phone). I guess you're only going to find that out if you contact Voda & ask for support (after you've tried every solution you can find on here I guess).
Now, if your phone isn't rooted, the Stickies have all the information you need in order to root it.
Edit - Also, questions go in Q&A ;-)
Thanks guys, MistahBungle will try the DUKJ1
Also would anyone have an idea as to how I can delete all the optus(old carrier) stuff off my phone?? Ta
You need to have a rooted phone to get rid of the bloatware. You can use an app like Titanium Backup Pro (Look for it on Google Play) to uninstall or freeze (which I recommend) apps you don't want. This thread is a good starting point for working out what you can/can't remove/freeze.
To our friend who added the tag to the thread, we know that Captain Obvious, thanks very much. However for someone new/who currently has little Android/SGS2 knowledge & already has a pre-rooted phone, avoiding Odin (and the inevitable problems many n00bs have with it) & using CWRecovery if it's already on the phone sounds like a sensible WTG to me.
hi guys,
I have a Samsung Galaxy S2 (i9100P), originally on orange, but since then I've moved onto T-Mobile. I have been having problems with low signal and many callers complaining that they cannot clearly hear and the sound is cutting out on both sides. T-Mobile have given me a signal booster and although the signal strength has massively improved, I still have poor call quality
Now I could be wrong here, but I think the signal issues have started since I flashed the original orange fw with NeatRom v5.6.
From searching on my pc, I've found my original orange brand fw, which was: I9100PXXLSS_I9100PBVLS2_I9100PORALS6_HOME.tar
Now I want to keep Neatrom, but I want to flash the modem and baseband which are showing as I9100XXMS4 on neatrom....I believe these could be the problem. Where can I get the correct versions that correspond to my mobile and network (EE) and how do I correctly flash these?
Thanks!
Come on guys, someone must be able to help me pls? :crying:
Just flash xxlss baseband (if it was ur original fw) in phone category in odin...
Thanks for helping me dr droid. I'll be honest mate... I don't have a clue what to do.
1. Do you have a link to a step by step guide to flash the modem fw and/or baseband? Could you show me?
2. Where do i get the correct baseband file for t-mobile network?
wowandroid said:
Thanks for helping me dr droid. I'll be honest mate... I don't have a clue what to do.
1. Do you have a link to a step by step guide to flash the modem fw and/or baseband? Could you show me?
2. Where do i get the correct baseband file for t-mobile network?
Click to expand...
Click to collapse
Download the firmware (the actual one which u said was present since the beginning)
Open the fw package with winrar
U will see a modem.bin file
Extract it to a known location
Connect phone in Download mode.
Open odin
Click on phone tab and then select ur extracted modem.bin
Flash ...
doctor_droid said:
Download the firmware (the actual one which u said was present since the beginning)
Open the fw package with winrar
U will see a modem.bin file
Extract it to a known location
Connect phone in Download mode.
Open odin
Click on phone tab and then select ur extracted modem.bin
Flash ...
Click to expand...
Click to collapse
Thanks very much dr droid. The problem I have is that I've only got the original nandroid backup with the following files:-
boot.img
cache.img
data.img
nandroid.md5
system.img
I extracted these using yaffey, but there is no file called modem.bin. Could you please tell me where it is located?
If this is not possible, where can I download the original orange fw with the following details:-
(MODEL: GT-I9100P
ANDROID VERSION: 2.3.4
BASEBAND VERSION: I9100PBVKI2
KERNEL: [email protected] #2
BUILD NO: GINGERBREAD.BVKI3)
Nandroid backups don't include the modem. Download the entire rom from Samfirmware, extract the modem.bin from that, flash as previously instructed.
Thanks mistah.
I've just done that, but it seems that my mobile's fw does not exist on their site anymore:-
Model: GT-I9100P
Product Code: GT-I9100LKNORA
Hidswver: I9100PBVKI3/I9100PORAKI3/I9100PBVKI2/I9100PBVKI3
Filename: I9100PBVKI3_I9100PORAKI3_ORA.zip
File not found
Find the most recent firmware for your country/carrier, download it, extract the modem.bin from it, flash that. If you get no joy from that, try another modem from another rom for your country/carrier. Modems are cross-compatible between roms & don't need to be used with a rom that's the same Android version/whatever, E.G - you can use modems that came bundled with GB roms if you're currently running ICS or JB & vice versa, etc, etc. Basically you can use any modem for the I9100, though I wouldn't recommend using modems specified as being for the I9100T unless you've tried every other modem first as these are specifically 'tuned' for the I9100T/the networks of carriers which sold it.
If you find none of the modems bundled with stock roms released by your carrier work for you, you can either:-
A) Root your phone, and start flashing any CWM flashable modem you can get your hands on (there are dozens, obviously - one for each stock rom released by each carrier around the world, there will be several for each carrier at least). This will be easier than downloading several dozen roms & extracting the modem.bin for each if you do get to this stage
and/or
B) Service centre/local mobile repair shop, though I would be doing A & trying as many modems as I could find on here (you will find dozens with an XDA or Google search) before doing that given that involves parting company with money.
MistahBungle said:
Find the most recent firmware for your country/carrier, download it, extract the modem.bin from it, flash that. If you get no joy from that, try another modem from another rom for your country/carrier. Modems are cross-compatible between roms & don't need to be used with a rom that's the same Android version/whatever, E.G - you can use modems that came bundled with GB roms if you're currently running ICS or JB & vice versa, etc, etc. Basically you can use any modem for the I9100, though I wouldn't recommend using modems specified as being for the I9100T unless you've tried every other modem first as these are specifically 'tuned' for the I9100T/the networks of carriers which sold it.
If you find none of the modems bundled with stock roms released by your carrier work for you, you can either:-
A) Root your phone, and start flashing any CWM flashable modem you can get your hands on (there are dozens, obviously - one for each stock rom released by each carrier around the world, there will be several for each carrier at least). This will be easier than downloading several dozen roms & extracting the modem.bin for each if you do get to this stage
and/or
B) Service centre/local mobile repair shop, though I would be doing A & trying as many modems as I could find on here (you will find dozens with an XDA or Google search) before doing that given that involves parting company with money.
Click to expand...
Click to collapse
Thanks very much Mistah.
1. I've checked on Sammobile.com and there are new i9100P orange firmwares, but since I've now moved to t-mobile, can I still use these? Also does it matter if my phone is a "P" variant?
2. My phone is already rooted with NeatRom v5.6, so how do I:-
a. Backup the current modem incase I flash the wrong modem or mess up?
b. Flash the new modem?
OK...Some clear thinking required...
1) Basically you can use any modem for the I9100 (this includes the I9100P)
2) You can't back up a modem, or not easily at any rate. And you don't need to given how easy they are to flash. If you want to go back to a previous modem, simply re-flash it. If you don't have a copy of your current modem, you might want to find a copy of it somewhere before you go flashing something else (not sure why that would be important to you given your current modem is giving you no connectivity, but, anyways...).
3) CWM flashable modems are flashable in the same manner as any other mod/kernel/rom in CWM. You should already know how to flash stuff in CWM if you're running a custom rom, if you don't, you need to start doing some searching (and how did you get a custom rom on your phone if you didn't know how to flash with it ?).
Right. I've given you more than enough info & won't be posting further to this thread, this stuff is really very simple, and we have guides/tutorials (most of which are stickied near the top of the General section) you can read if you need further info, and everything you've asked can easily be found with a search.
Up to you now...
MistahBungle said:
OK...Some clear thinking required...
1) Basically you can use any modem for the I9100 (this includes the I9100P)
2) You can't back up a modem, or not easily at any rate. And you don't need to given how easy they are to flash. If you want to go back to a previous modem, simply re-flash it. If you don't have a copy of your current modem, you might want to find a copy of it somewhere before you go flashing something else (not sure why that would be important to you given your current modem is giving you no connectivity, but, anyways...).
3) CWM flashable modems are flashable in the same manner as any other mod/kernel/rom in CWM. You should already know how to flash stuff in CWM if you're running a custom rom, if you don't, you need to start doing some searching (and how did you get a custom rom on your phone if you didn't know how to flash with it ?).
Right. I've given you more than enough info & won't be posting further to this thread, this stuff is really very simple, and we have guides/tutorials (most of which are stickied near the top of the General section) you can read if you need further info, and everything you've asked can easily be found with a search.
Up to you now...
Click to expand...
Click to collapse
No worries mate. Thanks for your help and advice.
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.
Hi all,
I installed CM11 onto my S5830i (GB) and managed to get it all working. I had to install S5360_XXMK1 modem and a newer version of CWM to prevent the "Status 7" error. Anyway, it all worked and I had CM11 up and running. Unfortunately, I had to remove it, I couldn't click any links in the browser and the browser was slow as all buggery even on a fast wifi connection. So I fired up Odin and tried to put the stock firmware on (i don't have an original state backup, the phone came with a custom rom on it already). I got these files
CSC_S5830i_BTUMD1.tar.md5
MODEM_S5830i_XXMD1.tar.md5
PDA_S5830i_XXMD1.tar.md5
But something's messing up, after Odin does its thing and the phone restarts, I notice something on the screen during restart saying it failed to format the /data partition. When I let the phone boot up normally it just stays on the "Samsung" startup animation forever. If I go into samsung recovery and try to do a factory reset, this is what I see
Code:
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/stl11
Formatting /cache...
Data wipe complete.
Obviously, something's wrong there, can anyone tell me how to fix it pleeeeese, I'd be eternally grateful.
Thanks
NS
EDIT: I think the CM install may have messed around with my partitioning. I do not have a pit file for the phone (GB Version) and am reluctant to be using the re-partition option in Odin. I can find pit files online, but they're either not the correct version or the poster doesn't even say what version it is. I am just so lost and confused with all this.
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
ehsanotaku said:
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
Click to expand...
Click to collapse
Thanks but you were too technical. I have been to a lot of those pages you linked and it's not all obvious what's going on. You spoke about "base band", I have no idea what that is. I have no idea what RFS, MTD
are (file systems?), not do I know where to get a bootloader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do. I'll re-read the posts you linked to (I had already seen them) and see if something starts to make more sense.
For instance:
"Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11"
May as well have been in Klingon, I didn't understand a word of it.
EDIT:
I've reviewed those threads again. Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions. I need a pit file, there's no info anywhere on how to get that. So I've just done a general google and hopefully I've downloaded one (more info on that is needed in the tuts). And the bootloader is attached to the unbrick thread, but, is that the ONLY bootloader? Do I need a specific one for my region? Do I need a specific pit file for my region? All this info is not supplied anywhere, Newcomers are not going to know this stuff and it needs to be made clear in the tutorials. Most of the tuts have broken links (split fus for instance), so I'm not sure if the stuff I googled is actually the same. Absolute nightmare.
NicSure said:
You spoke about "base band", I have no idea what that is.
Click to expand...
Click to collapse
Please read the link was provided for your convenient. ( Absolutely suitable for beginners).
NicSure said:
I have no idea what RFS, MTD
are (file systems?)
Click to expand...
Click to collapse
"Robust File System" is more or less equivalent to your FAT/FAT32 of your PC ( Samsung file system Format,, not going to add "Journalling system" to the mix, since you are not a sport ,,FYI : You are supposed to know common terms such as MTD , RFS when you are massing with CM11 mate >> Read the first page thoroughly, before start experimenting with Cyanogen stuff,,,
MTD (Memory Technology Device) supports YAFFS2 as a file system residing on it and is considered some type of of Partition Map.
NicSure said:
not do I know where to get a boot loader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do
Click to expand...
Click to collapse
Again actually start reading this topic ( quite self explanatory).
NicSure said:
Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions.
Click to expand...
Click to collapse
This topic contains well made Wipe packages ( European version is compatible with your device, If you are reluctant to register though).
NicSure said:
I need a pit file, there's no info anywhere.
Click to expand...
Click to collapse
Again, Read the topic I mentioned above. You are on Cooperve device, so be aware of wrong file ( "cooperve_0623.pit" resided inside Odin3.v3.07.Cooperve folder) All of the related links already provided , Just take your time and read mate.
I'd already read the posts you linked to multiple times thank you. They may be "straight forward" to you, but I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly.
In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Also, why would changing the base band effect the file system? How could it cause physical damage to NAND memory. I'm confused. I assume you mean physical damage, because if not, why would it be ill-advised to change it if it could just be changed back with no ill-effects?
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
ehsanotaku said:
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
Click to expand...
Click to collapse
Firstly, I'm not complaining, I'm criticizing, there's a difference. I was critical of your language and terminology as it didn't match the links you posted. Also the level of technical talk you used toward a clear newbie who would obviously never understand it without clarification. If that offends you then I'm sorry, I'm just speaking my mind. Help offered, no matter how kindly or freely is useless if it cannot be understood. I generally take a very irritated approach to people who post links (with the implication that the information is freely available if you'd bother to look) in response to perfectly polite questions, especially when I'd already read ALL the posts you linked to before and had trouble with them, that is why I posted, to get a little more basic understanding, not be presented with links to material I'd already read and needed help with. Also, after some researching, with regard to the base-band, I think you're wrong, there's no way flashing a different base-band separately could effect the bootloader, no way at all. I seriously doubt it could even cause corruption, that's liek saying installing the incorrect driver for a graphics card on a PC could corrupt the file system, just no. So far I've flashed many many different MODEM types onto my phone to try to test this, in some caes the phone boots, in some cases it doesn't etc.. Not once has the phone failed to go into Odin flash mode, and if it can get to that, it can be restored. So based on research and some experimental evidence conducted to test your assertion, I'd have to say that my initial findings are that your assertion is probably incorrect.
Also I learn very quickly. My knowledge of the subject had increased dramatically from my first post to my second. I learned c++ in a day for example, and was posting similar newbie questions on programming forums to which I was later replying with a level of knowledge that wasn't consistent with my initial post. It's just me, sorry about that. And thanks for trying to help, but I got it myself.
NicSure said:
... I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly. In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Click to expand...
Click to collapse
Dear NicSure, I am in the same situation as yours, I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
thePanz said:
I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
Click to expand...
Click to collapse
Per your request/confirmation @ development section/twr topic i would resume troubleshooting .
What is your device variation (5830i/C/M/V/5839i ) ? Do you have any Nandroid back up left inside your SD card from your original stock firmware partitions ? Can you see your IMEI number , when you are dialing "*#06#" ? Your original stock CSC/PDA/MODEM you are coming from ? Your Region / Country / carrier you are staying with at the moment and please give me the Totoro Modem part you did flash to get into the CM11 ? and for addressing part of your primary queries , Odin 3.07 works very well with variation I mentioned above ( you could use 3.09 with no harm though , but not recommended ) . Pit file also must be relevant, otherwise you will hard brick your device in many cases I observed .