Related
I have a g2x on the 2.2.2 android version. I tried software updating from the phone but it always gives me -Current version is the latest version- which is definitely not true. How can I fix this? I tried rebooting and hard resetting but nothing works. Also, I cannot do the LG updater thing from the site cause I don't have a laptop or PC I just want to do it manually from the phone I know there's a way. Any help is appreciated!
Could you tell me the device manager server settings for the update? I could tell you how to get to them.
Sent from my LG-P999 using xda premium
arthurgreeeen said:
I have a g2x on the 2.2.2 android version. I tried software updating from the phone but it always gives me -Current version is the latest version- which is definitely not true. How can I fix this? I tried rebooting and hard resetting but nothing works. Also, I cannot do the LG updater thing from the site cause I don't have a laptop or PC I just want to do it manually from the phone I know there's a way. Any help is appreciated!
Click to expand...
Click to collapse
I read that you have to be on 2.3.3 to get the 2.3.4 update. You will need a computer, beg, borrow one.
Hi,
I've got a friend who I helped upgrade from 2.3.5 to 4.0.4 on his i727r. He had his phone rooted with bloat deleted, so I restored the stock rogers 2.3.5 rom from sammobile using Odin with intentions of using Kies to grab the official upgrade to 4.0.4. Unfortunately his phone was low on battery so Kies wouldn't complete the upgrade in the time we had allotted, so we decided to do the 'unofficial' upgrade and flashed the rogers 4.0.4 rom downloaded from sammobile using Odin.
So, I'm wondering, as far as the process of upgrading using Odin compared to Kies, is there any reason why an upgrade through Kies would be more stable/ result in less FC's once he's on ICS? We didnt do a data wipe, so unless somehow Kies does that and then restores app data, I'm not sure what the difference between the two is.
He's had many FC's with TwLauncher and apparently his ram is out of control (I think that could just be a difference from GB to ICS). Anytime I have FC troubles with my TF101 or i9000.. its always a factory reset to fix it, but I was just wondering if somehow the Kies upgrade process would have taken care of that for people who just upgrade the samsung-intended way?
Thanks in advance!
dektoud said:
Hi,
I've got a friend who I helped upgrade from 2.3.5 to 4.0.4 on his i727r. He had his phone rooted with bloat deleted, so I restored the stock rogers 2.3.5 rom from sammobile using Odin with intentions of using Kies to grab the official upgrade to 4.0.4. Unfortunately his phone was low on battery so Kies wouldn't complete the upgrade in the time we had allotted, so we decided to do the 'unofficial' upgrade and flashed the rogers 4.0.4 rom downloaded from sammobile using Odin.
So, I'm wondering, as far as the process of upgrading using Odin compared to Kies, is there any reason why an upgrade through Kies would be more stable/ result in less FC's once he's on ICS? We didnt do a data wipe, so unless somehow Kies does that and then restores app data, I'm not sure what the difference between the two is.
He's had many FC's with TwLauncher and apparently his ram is out of control (I think that could just be a difference from GB to ICS). Anytime I have FC troubles with my TF101 or i9000.. its always a factory reset to fix it, but I was just wondering if somehow the Kies upgrade process would have taken care of that for people who just upgrade the samsung-intended way?
Thanks in advance!
Click to expand...
Click to collapse
There really shouldn't be any problem with using odin over kies method. I've always did my upgrade through odin every since i had my captivate and now for the skyrocket. Personally if i was him i would back up all the apps and data that he wants to save, then do a factory reset and see if that clears up the FC's. Also he should just try another launcher like Apex and see if that gives him any problems...plus its a way better launcher to begin with
I think it trips your flash counter, but there is a fix for that. Google Rogers skyrocket flash counter reset
Sent from my SGH-I727R using xda premium
So I started to read up on the new ICS update for Rogers Skyrocket, and the consensus is that it's slow and laggy. I do want to try it out.... but here's the big question...
If I don't care for it.... can I downgrade back to 2.3.6? With no relative issues?
And how would I go about doing it?
No0b question I'm probably sure... but hey if you don't ask you'll never know!
It would be best to back up. Back up creates a copy of your entire phone so you can swap between the two images if you'd like. If you really have important data then I would back up stuff to your PC first.
Im not finding it slow and laggy at all. But yes, pretty sure if youre gonna downgrade you gotta odin the stock tar from sammobile. Might be able to do it through kies, but im not sure
Its not slow and lagy for me. Works great. I upgraded with the sammobile tar installed cwm and rooted. You can always go back. Just install modem and rom or get tar from sammobile.
Sent from my SGH-I727R using XDA
Well I am downloading a TAR from the site here that I found of 2.3.6 so that's ok... I've backed up the phone from Kies so I at least have a copy there... but for the most part I won't lose anything there either. Most everything I have is backed up on Google...
SO I guess I would jsut load the 236 to my external and then install it if i wanted to?
This is a question. therefor, belongs in Q&A. Moved.
Cheers
Hi, noob here (obviously)
I went ahead to downgraded my Rogers GSII LTE from ICS 4.0.4 to GB 2.3.5. It's the correct stock ROM, as I've used it previously without any problems.
I wiped all data while still on ICS, put the phone in download mode, launched Odin with the option "Auto Reboot" checked, nothing else. Pointed the PDA section to the stock ROM. Flashed it, and after about 4 mins it rebooted.
I get to the Android setup page but I can't even launch the setup.
"The process android.process.acore has stopped unexpectedly. Please try again" and it Force Closes.
Anything I can do to clean the phone properly to reload the stock rom?
prbassplayer said:
This is a question. therefor, belongs in Q&A. Moved.
Cheers
Click to expand...
Click to collapse
No Worries PR.... Thanks for the heads up....
And I notice that it's laggy here and there... especially while texting. I've been using advanced app killer and seems to help a little....
Battery life has increased too which is a good thing. But all in all.... They fell flat. Lots of programs that just aren't ICS ready for the GSII
blanchardc said:
Hi, noob here (obviously)
I went ahead to downgraded my Rogers GSII LTE from ICS 4.0.4 to GB 2.3.5. It's the correct stock ROM, as I've used it previously without any problems.
I wiped all data while still on ICS, put the phone in download mode, launched Odin with the option "Auto Reboot" checked, nothing else. Pointed the PDA section to the stock ROM. Flashed it, and after about 4 mins it rebooted.
I get to the Android setup page but I can't even launch the setup.
"The process android.process.acore has stopped unexpectedly. Please try again" and it Force Closes.
Anything I can do to clean the phone properly to reload the stock rom?
Click to expand...
Click to collapse
factory data reset from recovery.
digitalnights said:
So I started to read up on the new ICS update for Rogers Skyrocket, and the consensus is that it's slow and laggy. I do want to try it out.... but here's the big question...
If I don't care for it.... can I downgrade back to 2.3.6? With no relative issues?
And how would I go about doing it?
No0b question I'm probably sure... but hey if you don't ask you'll never know!
Click to expand...
Click to collapse
2.3.6 is not rogers, im guessing u r not rooted or have cwm, if u want to go back to rogers stock its 2.3.5 , u can use kohanes method but not his firmware files, go to sammobile to get the stock files, use i727r in the search box in the firmware section
I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy
If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?
If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham
Yeah, you can still fix it. No need it to bring to samsung
Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!
Okay so i got my phone (US Cellular Samsung Galaxy S Mesmerize SCH-I500) from ebay and it came with gb 2.3.4 originally and i updated to 2.3.5 then later on to 2.3.6. After doing some homework i want to get back to froyo 2.2.2 but i cant!! I tried to flash back to EE19 via odin and it bricked my phone. Then tried flashing back to EC10 and it worked but what happens is it has no signal whatsoever (baseband is uknown/no phone number) pretty much everything is unknown except the build number/firmware version :crying: I just don't get what i'm doing wrong here guys. Every time i try to make the *228 phone call to activate it, it says phone is in airplane mode go to settings to turn it off to enable connections but it's not in airplane mode!!! I factory reset it took out the battery but nothing works!! Although i was able to flash back to 2.3.4 via odin and root it. But still i want to go back to froyo :/ Please someone help me get back to a working froyo :crying: I would so appreciate this if anyone can look into this for me for i am fairly new to android but i'm getting the hang of it If you figure this issue out get a hold of me anyway you can thanks everyone!!!