Related
Hey!
First things first, I've never had an android phone before so please keep in mind that I'm an absolute noob .
Basically, battery life is something important to me and would therefore like a recommendation between the two roms.
I'm currently on Miui 1.5.13 MCG2.1v and I'm not so impressed by the battery life. It barely lasts one whole day and the phone sits on my desk most of the time. I tried the suggestions from the Miui thread but I hardly noticed much difference.
I am also not prepared to make my phone even thicker with a fatter battery.
Despite loving the Miui interface and such, I will be prepared to switch to Darky's if battery life is much better.
A another small question, whats a good app I can download (Preferably free) which can help monitor the battery. For example, show how much % per hour the phone uses up.
Thanks!
Thats due to the fact MIUI is based of CM7 (CyanogenMod) which has battery issues but nevertheless 1 day seems a bit weird, with CM7 or MIUI the phone lasted at least 2 days with medium usage (gaming, benching, OCing, Messaging, surfing).
But even this can depend on the used Kernel. And Darky is based of the original Sammy Firmware which in case is more or less optimized for the SGS but i recommend a battery whipe after switching Roms.
And for Battery Monitioring Gingerbread (2.3.x) itself has this feature in the Settings under (About Phone -> Battery Use -> just click on the top Bar.
According to my phone settings, the kernel version I have is "2.6.35.7_platypus-miui-quorra-r9..."
If there is better versions of the Miui rom, I'll be willing to try it but if ultimately Darky's rom is the best option, I think switching to Darky would be the better idea.
As you can tell, I'm slightly confused on what to do next
Any input would be brilliant.
I have been on MIUI since RC3 - a few months back. any how since then battery life for me has improved drastically
i used to get about half a day, now i can get 2 days + if i use it minimally, or 1 full day if i use it excessively.
for me thats good i didnt get much better results using other custom ROMs, besides, there is not 1 single ROM out there that compares to MIUI so its well worth it for me
Try the TK-Glitch kernel... see if that's better for ya.
Prasad007 said:
Try the TK-Glitch kernel... see if that's better for ya.
Click to expand...
Click to collapse
forgot to add that !!
try a little undervolting with this kernel and that can also increase battery life
MIUI is very good indeed......on everything except battery life.
For battery life darky's rom is better for sure.
Thanks!
Okay, I'll try TK-Glitch's v10A kernel. Now for an even noob'er question , how do I install it
I figured I have to put my phone in to recovery mode and use odin3. If this is correct, why can't odin3 find the kernel I downloaded via PDA? I'm 100% positive its there or am I doing something wrong
tk glitch kernel is flashable thru recovery no need for odin
Done! annnnnnnnnnnnnnnnnd no service!
go into settings and system > mobile and network settings, and select use only 2g networks.
that should give u a signal, also check your IMEI number is not been changed.
Can't switch to 2g which I'm assuming, is because there is no service.
I tried to check my IMEI using *#06# and all I get is 'IMEI' and thats it. No number or anything
thats ya problem.
its easy to fix just restore the efs backup that you SHOULD of made when flashing MIUI
http://forum.xda-developers.com/showthread.php?p=14275826
you can also do it using root explorer
I have something called galaxy-efsbackup on the phone which I'm assuming is what your talking about?
So for clarification recovery mode, install zip from sdcard and choose the file?
Thanks for the help so far by the way
no that is the .zip file which backs up the efs, you should of applied that before flashing MIUI for the first time,
in result that would of left a folder on your sd card called 'backup' with a subfolder inside called 'efs' << that is what needs to be restored.
if it is not there, and you do not have a copy elsewhere, try to flash back to the version you was on earlier - or the kernel you used before this happened, that might sort it out.
however if it doesnt, you will need to flash back to froyo and start the whole process again it happened to me last week
Okay I have it
It has IMEI and Android sub folders within it with other files as well. What do I restore it?
Edit: I hope I needed to select back up and restore > backup because I accidently selected it. I have however copied the file "back up" on my laptop a couple of minutes ago before the massive **** up.
*Sigh* Sorry -_-
im confused as to what you have done lol
the nv_data.bin is what needs to be restored, use a app such as root explorer or similar
navigate to /system /efs ---> nv_data.bin <-- replace with the one on your sd card
reboot, Job done !!
I dont have 'ef' under systems
Should i just create one?
shizer said:
I dont have 'ef' under systems
Should i just create one?
Click to expand...
Click to collapse
my apologies. are you using root explorer or do you use another app
if using root explorer its just there on the first page, not under any / subfolder
Ah, I'm blind.
I've done everything and nothing. Didn't work
Everything in the ef folder hasn't been modified since I last rooted and installed the Miui rom.
help!
Hi I found a similar article on androidforums.com so I thought id make one here as a lot of people still seem to not know how to flash basebands and go from there. Ill start from the beginning.
For those who don't understand what this is about.
Old Baseband = If you have the Stock Froyo (2.2) Android system on your phone then you have the OLD BASEBAND, and you do not need this unless you updated to past 2.2.2 then continue reading if you wish to root your phone the easy way.
New Baseband = If you updated to the Stock Gingerbread (2.3) Android System on your Optimus One, then you fit this category, Lg have implemented a new baseband in this update which makes any Roms based on the old baseband not function, as well as making it more difficult to root your phone
FLASHING OLD BASEBAND
If you're already on official Gingerbread version you will need to downgrade your version to Froyo 2.2.2 using KDZ Updater. This is because the new Gingerbread contains the new baseband, and the Froyo firmware is the old baseband.
To do this please go onto this link that contains kdz and the stock Froyo 2.2.2 Rom required to flash. The reason you need 2.2.2 is its the easiest and proven version to work with Gingerbreak to root your device.
http://forum.xda-developers.com/showpost.php?p=13396506&postcount=1
Notice: If by some ACCIDENTAL reason, your phone gets stuck in EMERGENCY MODE during flashing, follow the instructions on this link how to use KDZs functions to continue flashing the firmware you downloaded in Emergency mode.
http://forum.xda-developers.com/showthread.php?t=1275523
FLASHING NEW BASEBAND
The Kdz File for new baseband is below, use the same method as above only using the v20G .kdz file instead of the 2.2.2 v10E update.
This will update your phone to the official LG 2.3 firmware, in which the new baseband originated.
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/ANEUBK/V20g_00/V20G_00.kdz
If then stuck on LG Logo OR boot animation, try pulling and putting in your battery, turning on your phone and holding down volume down and home key, this should reset your phone to factory and then you will be able to boot into the stock gingerbread.
ROOTING
The easiest way to get root privileges on Old Baseband (2.2.2) firmware device is by using Gingerbreak apk. Just download it, install it and run it.
forum.xda-developers.com/attachment.php?attachmentid=600902&d=1305802958
To get Root access on the New Baseband (2.3.3) use SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
Or direct link to the latest version
forum.xda-developers.com/attachment.php?attachmentid=778098&d=1320906597
Make sure, after you download the program, you go into your cmd, then go into the ADB folder, drag the ABD exe file into command prompt, delete the .exe part and add devices, so it look like this
OR
Download the ADB.zip attachment on this post, EXTRACT it so cmdXP and cmd7 are located inside the ADB folder in the Superoneclick directory, and run either version, depending on your windows version (This links you directly into ADB app, instead of manually dragging ADB.exe int cmd, really its just for your convinience.)
Then all you have to do is type the following lines.
adb devices
press enter
adb shell
press enter
then type in the following directly after
echo 1 > /data/local/lge_adb.conf
press enter.
Then go into Superoneclick.exe, select auto method and run root, this should then eventually root your device.
***WARNING***
Some Antivirus softwares will detect Superoneclick as a Virus.
IT IS NOT A VIRUS, just the types of exploite code it uses makes some antivirus software think of it as malicious. Just disable your AV for 5 mins before you extract Superoneclick.
RECOVERY
There's two popular custom Recovery versions for O1 - AmonRa and ClockworkMod
The easiest way to flash ClockworkMod Recovery is by downloading ROM Manager app from the Market (free or donate version doesn't matter) and choose to flash the latest recovery version and choose the option to Reboot in Recovery mode.
For Other Recoveries including Amonra there are a few links, but here is the one that has flashable zips
http://forum.xda-developers.com/showthread.php?t=1523050
Just flash the zip files in Clockworkmod recovery menu, after you install that through Rom Manager if you wish to use a different recovery.
Now that you got the right baseband + your device is rooted and loaded with a custom recovery you may install any Rom you wish that is based on the correct baseband such as
Mik_os 6.5.8 Cyanogenmod port (OLD BASEBAND).
http://forum.xda-developers.com/showthread.php?t=946354
[UNOFFICIAL][DEV/GEEKS-ONLY] Cyanogenmod 9 (Android 4.0.3)[BETA][NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1558213
OFFICIAL CYANOGENMOD Rom [NEW BASEBAND]
http://get.cm/?device=p500
Oxygen ROM 2.3.2 (Android 2.3.7)[NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1325386
Next time, search better
Also posted in wrong thread, this is developmentthread...
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
fundoozzz said:
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Guys i did a search and looked into the sticky how to, and the only thing about downgrading baseband is using LGMDP, and kdz is only "mentioned" as a tool for unbricking your phone and flashing old firmware, new users would not know to use kdz.
Also this is a universal guide to root ANY lg optimus one together with having the old baseband, without having to mess around with SDK or LGMDP.
All members have to do now is look at this thread and all their questions are answered hopefully...
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
I hear a lot about the new baseband making ROMs incompatible, but is there any advantage to the new baseband?
its not that they are making roms incompatiable, its that they are not designed for those Roms,
So far there has been no reports of any advantage having a new baseband, Lg engineers obviously decided on it for some reason, but the old baseband is more than fine, and in fact i have read several reports that with the new baseband gsm reception got worse in areas that they used to have fine reception, but thats all speculation.
Your best bet is to try for yourself, but if you want to make use of Roms such as miks cyanogen mod or others you have to use the old baseband.
There are other Roms available on the new baseband, so its upto you.
I suggest what rom you would like to install on your phone first, then pick the baseband it requires, as its only a simple flashing of your firmware.
Also note Gingerbreak.apk doesnt root any stock firmware past the 2.2.2 update.
Personally i pick the functionality and advantage of having a custom rom such as cyanogenmod over an update to the baseband
Does this guide work for Optimus T (LG P509) ? I have got one recently and currently using stock 2.2 on it. I don't know the difference between LG p500 and LG P509. I'm coming from T-Mobile G1 on which I'm using CM 7.1. Thanks for guidance.
Sent from my Dream/Sapphire using xda premium
Hi,
Doing a little search i found this thread
http://forum.xda-developers.com/showthread.php?t=960278
looking at it, i assume you can use this guide for p509, but i can not be 100% sure, try finding the t-mobile 2.2 kdz file, but yes not 100% sure the main difference.
deniso177 said:
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
Click to expand...
Click to collapse
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
As you already quoted it, i said that this method is different from Doks.
As for wiping all data completely, so its all brand new and neat, then try to fiddle around with internals and possibly have a bug result from it.
KDZ is what is used to UNBRICK your phone in the first place, so go do some research before posting unnecessary things.
Lastly how about you show some respect and keep your negative and rude comments to yourself, if you dont like this method dont do it, dont abuse people in the process.
terratrix said:
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Click to expand...
Click to collapse
And yep exactly, i personally prefer completely reinstalling something to make it work properly, then doing things dodgy.
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
ichigo200 said:
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
it means your phone is past the firmware update that gingerbreak works on,
as it says in the first post, use kdz and the file in the link to flash your phone to that firmware, and then gingerbreak will work
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
A warning to anyone tempted to do this. Like the original poster, I also have an LG Optimus T. I am technically savvy (15 years IT experience) and I followed the directions to the letter, but the end result is a bricked, unrecoverable phone. Had I known the risks involved, I would have been perfectly content with Froyo and waited for the official upgrade to arrive.
Here is how mine failed: during the kdz update process, while the phone was on the "Emergency Mode" screen, the kdz updater program threw an exception and crashed. This caused the phone to be permanently locked in emergency mode. The buttons are unresponsive and the only way to turn it off is to remove the battery. With the battery in, it immediately goes to the emergency screen. No combination of button presses (eg, hard reset) does anything. The computer will still see the devices but only if I remove the battery and start the phone up by inserting the USB cable.
I have tried every method for recovery I could find including the following. In each case, I tried it with the modem device listed in device manager both disabled and enabled, as instructed in other recovery threads I found.
Flashing the original .kdz ROM in emergency and cs_emergency modes. When I did, it failed with an exception 4008.
Flashing the original .dz ROM with all of the tools I could find. LGMDP and LGDP2 could see the phone's COM port but beyond that, they could not communicate with the phone in any way. I couldn't even retrieve the IMEI number.
Updating the phone with the LG update software. It actually detects that the phone needs an update and starts to do one but it fails at the point where it tries to communicate with the phone.
Based on other posts I found for the same problem, I believe the phone is completely unrecoverable. I spent over six hours trying to solve the problem and I'm kicking myself for even trying this. I have put in a repair claim with LG and I'm waiting for instructions on how to proceed.
I would not recommend you try this unless you are not worried about destroying your phone. I imagine most installs go without a hitch but if the buggy kdz updater software crashes like it did for me, your phone will likely be bricked permanently.
Click to expand...
Click to collapse
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
In short, don't mess with KDZ unless you really have to.
Click to expand...
Click to collapse
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
I have used KDZ more than 2 dozen times -.- Just used it again this morning. I never ended up with a bricked phone mind you. They favour LGMPD since it's more updated, while KDZ is a little old but still very good.
There is a fairly equal share of bricked phones using LGDMPD, eventhough they got it back by using other people's NV2, they need to hope they are lucky to escape the long arm of the law.
Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
Mate your the one who clearly doesnt get it.
And i read your post on androidforums, you even managed to brick your phone installing custom recovery, clearly your phone software is buggy, not kdz, kdz is capable of recovering while in emergency mode as well, but of course there are freak accidents.
EVERYTHING has a WARNING.
Every single Rom, Kernel, Recovery also carry a chance of bricking your phone.
I have used Kdz dozens of times and never had a problem with it, in fact, its what solved my problems in the first place.
And exactly wat terra said, the way LGDMPD works can also cause bricked phoes or taking shortcuts to make things half work.
You have to know what your doing, and follow instructions TO THE WORD, and you should be fine, if your going to skim read then you brick your phone doing the simplest of tasks (such as repeatedly flashing zips without reloading recovery...)
I will always prefer kdz as thats what the firmware comes with originally + i prefer doing clean installs any day.
Please Help...
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
shreyas.kukde said:
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
Click to expand...
Click to collapse
Hey mate, well no gsm is normally caused by the wrong baseband, so flashing back to the old one should fix the problem, try to re-flash the stock froyo given in the link on first post and see if that works, and if still no coverage then its a hardware problem and Lg should replace it for you, just dont forget to flash back to stock again if you rooted it, then they should fix it within the warranty.
For starters I have not tried using Thrill Seeker 3.0/3.1 or v21e. I also have not tried CM7, Nightlies, or anything since my transition from Froyo to Gingerbread.
Right now my gripes with Gingerbread are ghost calls and the phone running rather slow at times. However, I do enjoy that I am still able to use the 3D gimmick. As far as the HDMI goes... I've never used it. If I get noticeably better performance by using a Nightly build I could certainly do without the 3D.
Should I switch my software version for my LGP925 from V20p to V21e or something else? Also I just noticed that my Build number is Thrill Seeker 2.0. I see that my Android version is 2.3.5, and my Kernel version is 2.6.35.7+ if that helps any.
I know how to make backups and have done so already. That's also very important to me. I want to make sure that whichever software I use still allows me to root my phone and use software like Root Explorer, Titanium Backup, Superuser, etc.
I appreciate any help!
gniblack said:
For starters I have not tried using Thrill Seeker 3.0/3.1 or v21e. I also have not tried CM7, Nightlies, or anything since my transition from Froyo to Gingerbread.
Right now my gripes with Gingerbread are ghost calls and the phone running rather slow at times. However, I do enjoy that I am still able to use the 3D gimmick. As far as the HDMI goes... I've never used it. If I get noticeably better performance by using a Nightly build I could certainly do without the 3D.
Should I switch my software version for my LGP925 from V20p to V21e or something else? Also I just noticed that my Build number is Thrill Seeker 2.0. I see that my Android version is 2.3.5, and my Kernel version is 2.6.35.7+ if that helps any.
I know how to make backups and have done so already. That's also very important to me. I want to make sure that whichever software I use still allows me to root my phone and use software like Root Explorer, Titanium Backup, Superuser, etc.
I appreciate any help!
Click to expand...
Click to collapse
Update to v21e. That will solve ghost calls. My experiences with CM7 and roms based off it it is that I've had some wifi connectivity problems but a reboot will fix it and every once in awhile the camera has problems. I really like the speed of CM7. It's a lot faster than stock and battery is about the same for me.
Over in the Optimus 3D section, you'll find a lot of great stuff. Thiaiz 2.8 and the promethius project are my favorites. Acuras roms are great for long battery life. If you want to stay on v20p, thrill seeker 3.0/3.1 is pretty great. There's also a non v20p version of you'd also like to switch to v21e.
Sent from my LG-P920 using xda app-developers app
Thanks for the response. I remember I had difficulty to updating the baseband to v20p, but after some research I got it working. Is there a good place to download v21e from along with a good set of instructions on how to install it? I forget if I can do it straight through the phone's recovery mode or if I have to do something different.
Also I was under the impression that only a Froyo baseband would work with CM7. Is this correct?
The instructions for the Optimus 3D seem fairly straightforward, and I figure that the v21e baseband for that phone is also compatible for the Thrill 4G. I guess once I have it on my SD card I just need to do a md5 checksum to ensure that I do not brick my phone.
Thanks for the response. I remember I had difficulty to updating the baseband to v20p, but after some research I got it working. Is there a good place to download v21e from along with a good set of instructions on how to install it? I forget if I can do it straight through the phone's recovery mode or if I have to do something different.
Also I was under the impression that only a Froyo baseband would work with CM7. Is this correct?
The instructions for the Optimus 3D seem fairly straightforward, and I figure that the v21e baseband for that phone is also compatible for the Thrill 4G. I guess once I have it on my SD card I just need to do a md5 checksum to ensure that I do not brick my phone.
Click to expand...
Click to collapse
If you flash the v21e baseband with the kdz method (check the Optimus 3D dev section, there's at least 2 good guides) its almost impossible to brick your phone. The O3D CM7 nightlies are gingerbread compatible. If I remember right, the Dark Lestat has a link for the kdz and a very great guide with it. Just don't try to flash the kdz through cwm, it won't work since it doesn't flash basebands. Just do some poking around the other dev section and you'll be set. V21e still has great connectivity with att, just set up the right apn and you're good to go.
I'd give you links but I'm on my phone :/
Sent from my LG-P920 using xda app-developers app
KDZ Files Available
Just click on the tab for it and it's the last one.
Cm7 8-26 nightly
I have been using the CM7 8-26-2012 Nightly build and it has been running great. I've used almost every ROM available for this phone and CM7 (When everything got sorted out) has been the most reliable and has incredible performance. The RAM management keeps my phone from getting bogged down and it seems to be the most lightweight. It's lacking 3D and HDMI output as of now, but if you aren't using them it's a great choice.
The Dark Lestat said:
KDZ Files Available
Just click on the tab for it and it's the last one.
Click to expand...
Click to collapse
Thank you. I had a huge headache last night and couldn't go on any longer. I appreciate you posting this. I followed similar sets of instructions, but they did not work. I hope this does the trick. Anyway, once I reach step 4 and attempt to install BC2AppSetup.exe I receive the following error:
The only way I could manage to get the BC2AppSetup.exe to install from the Software folder was by editing the host file and adding a pound symbol "#" in front of the line reading "127.0.0.1 csmg.lgmobile.com". I did the same last night. Once I reach step 7 and run UpTestEX_mod2_marwin I follow the steps until I hit Upgrade Start. Then I have the following window pop up and it freezes at this point:
On my system I had Avast installed, but it was disabled. I thought it could be the culprit so I uninstalled it. That made no difference. My system is running Windows 7 Ultimate x64 SP1. I also have two laptops. One runs Windows XP Home Edition x86 SP3 and the other Windows 7 Home Premium x64. At this point should I just give one of those a try?
I am leaving for work right now. I just tried it on my Windows 7 laptop and had the same problem at step 4.
After I made it home I attempted to give it another go. The steps did not work on either of my Windows 7 systems, but they did work on my laptop running Windows XP aside from a minor change in the steps. Step 3 says to change the hosts file already. This created a problem for me when installing B2CAppSetup.exe. Not until after I performed that step did I change the hosts file.
Now I am trying to figure out how to root the phone again after all of these changes. I did a reset on the phone so I lost my root. At least I am guessing that's what caused it. What steps should I follow to root it?
I think I found the trick. Everything seems good so far. http://forum.xda-developers.com/showpost.php?p=22417769&postcount=1
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
nickpb said:
Firmware: 2.2
Click to expand...
Click to collapse
It would be simpler just to connect it to KIES and let it update your ROM according to its specs without any worries, If it fails than you can chose latest ROM from here its based on region, so chose latest for your region
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
nickpb said:
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
Click to expand...
Click to collapse
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
AlwaysDroid said:
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
Click to expand...
Click to collapse
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Hi.
I think if u be in GB ROMs , it's better , then go to new bases like ICS or JB slowly.
Hey I recommend you just to update it via Kies. You will probably get 2.3.6 GB Value Pack. Its pretty good, and stable, atleast for me. If you are not satisfied with preformace that you get with it, you can install custom kernel, such as semaphore, so it would get better,
If you lived with froyo till now, you wont need anything more than GB. And you can be sure about stability, good signal, no restarts and so on, that you can get on some custom ICS and JB roms...
snapper.fishes said:
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Sent from my GT-I9000 using xda premium
AlwaysDroid said:
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Click to expand...
Click to collapse
Please don't be misleading. CM10 is certainly good in it's own right, but there are quite a few things that are not working.
For instance, Google+ instant upload is completely non-functional because of an incomplete implementation in both the camera and gallery apps. This is clearly a rom problem.
The gallery app also has no settings. There is a menu option to access settings, and one would expect to see a settings screen similar to the one in CM9 when that settings menu is clicked. Instead the user is greeted with a blank screen.
Users need to be fully aware of what they are getting when choosing a rom and making statements like "it is almost perfect" is subjective and can be misleading.
Finally you say that CM10 has "almost no bugs" and then follow it with "... nothing" which is an obvious contradiction. Which is it, almost none, or absolutely none?
I have a S3 Mini I8190N, Baseband I8190NXXALL6, on Three Ireland.
I've tried all of Maclaw's CM10.2 roms for the last month, along with some of OliverG96's releases, and none of them show up any network signal for me, and won't let me search for networks, almost as if the rom can't use the hardware radio.
The stock 4.1.2 rom works perfect.
I've tried changing my baseband from I8190NXXALL6 to I8190NXXAMG1, and that made no difference.
(Stock still has perfect signal, Maclaws CM10.2 has no signal at all)
I've also looked through the build.prop files and compared them to the working stock build.prop, but I don't really think tweaks in there will fix this.
Seeing as this possibly could be a hardware issue, is there a file defining what radio hardware my phone has, like /proc/cpuinfo does for the cpu?
Anyone have suggestions on how i could fix (or help fix) this issue?
I can test suggestions and provide logcats if anyone requires?
EDIT:
Problem solved! seems there were some issues with my modemfs, and golden-guy's suggested fix here worked.
did you make a clean or dirty install?
if dirty try a clean install.
Same bug here and also Oliver96 has the same problem s.s
Sent from my GT-P3100 using xda app-developers app
JackoMJ said:
did you make a clean or dirty install?
if dirty try a clean install.
Click to expand...
Click to collapse
I've tried a dirty install, a clean (factory reset) install, and I've even went into ODIN, flashed a complete stock rom, TWRP, and then put CM10.2 on after that with a factory reset.
alexmarra3000 said:
Same bug here and also Oliver96 has the same problem s.s
Click to expand...
Click to collapse
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
same problem
i have got the same problem too.
got back to original samsung firmware und stock recovery... nothing
i am from germany und tried out any available basebands... nothing
on any stock, theres no problem, but if i want to get some roms e.g. from maclaw.pl i cant get signal at all
greez
EccTM said:
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
Click to expand...
Click to collapse
No, I have the I8190 normal version like OliverG96, and I don't know if he is working on a fix.
The strange thing is some users have the bug and some users not.
Also I have this bug with paranoid rom, pac rom and aokp.
On the contrary with Dmod v6 I don't have any issue, probably because it is based on official firmware, I don't know sincerly.
Sent from my GT-P3100 using xda app-developers app
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
mausdefekt said:
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hi, i also use O2 (directly) and had never problems with any CM-ROM of Maclaw.
You checked the APN??? Maybe you have to use a different one.
build.prop tweaks
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
I did not try these myself, as I don't have any RIL issues, so use them at your own risk. Reboot afterwards for the changes to apply.
Source: http://geekyogi.tumblr.com/post/24692879082/android-build-prop-tweaks-root-only
Hi
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
golden-guy said:
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
Click to expand...
Click to collapse
I compared the maclaw 10.2 build.prop with my own functioning stock build.prop and changed most of the attributes about with no luck. I've also tried both those suggested options, but they seem to be more for improving signal strength rather than actually getting a signal, I didn't see any changes using them.
stenc55 said:
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
Click to expand...
Click to collapse
Like mausdefekt, I get two slightly different results from *#06#.
My IMEI matches up, but when i'm running a non-stock based rom, my IMEI SV is 00 for some reason.
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
joelalmeidaptg said:
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
Click to expand...
Click to collapse
Ive tried that too, no difference. Also tried it with factorymode set both on and off.
I'm using Maclaw's TWRP 2.6.3.0 with kitkat support atm, I've never used any non-TWRP recovery.
mausdefekt said:
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hey,
I am running CM-10.2 on my S3 Mini (Oliver's cm-10.2-20131116-UNOFFICIAL-golden) and RIL is working just fine. So I would not think that there is a general issue with RIL on custom ROMs. Rather, the way how you switch from stock to custom might have an impact on RIL...
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Since when I switched from stock to custom, I exactly did that. And I never had any issue with RIL on any custom ROM I have installed since then - which was basically all versions since the 20130928 release.
Cannot tell if that works out for you, but it's definitely worth a try
Btw, I did not check the additional "/01" in the IMEI output when I was still on stock. Running custom I get the very same output - just the IMEI, without this suffix. In the "about phone" section, the relevant IMEI SV entry does read "01" for me.
I wonder if your cellphone is SIM-locked...
hi
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
I've tried setcpu to raise min. cpu to 1ghz, nothing.
What's wrong? On AC all works fine!
golden-guy said:
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Click to expand...
Click to collapse
I factory reset, flashed back to complete stock I8190NXXALL6 (it's 4.1.2) using ODIN, and everything worked perfect. From there I followed your guide to flash CWM recovery, then flashed maclaw's cm 10.2 (20131123) but I still had the same RIL issue.
Then I tried flash the stock rom with heimdall instead of ODIN initially and then follow your guide, same result.
Then I downloaded the odin version of maclaw's CM 10.2 (20131122) and flashed it directly with heimdall. same result.
After that, I took apart both the stock and odin cm 10.2 versions, and tried use heimdall to flash a hybrid version of the two:
Stock: STEboot1.img, STEboot2.img, Modem.bin
CM10.2: boot.img, system.img, recovery.img
Still had no signal at all, so I flashed TWRP 2.6.3.0 recovery and restored back to my usual stock-based backup.
joelalmeidaptg said:
I wonder if your cellphone is SIM-locked...
Click to expand...
Click to collapse
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Timewolf said:
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
Click to expand...
Click to collapse
I just tried to see if i'd get any sort of signal on maclaw roms by plugging my phone into AC... no joy for me there either
Does it have signal if its plugged in then the phone is turned on, or can you get signal at any time just by plugging into AC? like:
*Turn on phone* > standby (on battery) - no signal > *plug into AC* > standby (on AC) - signal > *unplug AC* > standby (on battery) - no signal
Sounds like your problem could be more hardware based than mine? something to do with voltages possibly? I'm really not sure what to suggest.
EccTM said:
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Click to expand...
Click to collapse
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
joelalmeidaptg said:
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
Click to expand...
Click to collapse
So assuming thats the issue, would getting a network unlock code allow me to use custom kernels and roms?