I flashed to both versions listed on http://forum.xda-developers.com/showthread.php?t=1092021 and am seeing the same issues with both.
The time is 4 hours off, I can uncheck auto-time and check it again and the time will be correct for maybe 5-10 min before returning to 4 hours later.
Everytime I try to download apps through the market, I get "Application Name" could not be downloaded due to an error. This is true regardless of wifi vs hspa.
With the pure stock version, superuser is still installed. Should I have unrooted it before attempting this? I simply followed the directions listed on that post.
Flash the original firmware located in Entropy's Ultimate unbrick thread uckd5. That version is pure stock that is not already rooted. To be safe use the included pit file.
Sent from my SAMSUNG-SGH-I997 using xda premium
Bronk93 said:
Flash the original firmware located in Entropy's Ultimate unbrick thread uckd5. That version is pure stock that is not already rooted. To be safe use the included pit file.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
i think the time issue is with the modem.......i got the same thing when flashing the new ones.
try another one and see if the issue sticks
glorifiedQA said:
I flashed to both versions listed on http://forum.xda-developers.com/showthread.php?t=1092021 and am seeing the same issues with both.
The time is 4 hours off, I can uncheck auto-time and check it again and the time will be correct for maybe 5-10 min before returning to 4 hours later.
Everytime I try to download apps through the market, I get "Application Name" could not be downloaded due to an error. This is true regardless of wifi vs hspa.
With the pure stock version, superuser is still installed. Should I have unrooted it before attempting this? I simply followed the directions listed on that post.
Click to expand...
Click to collapse
The time thing is a modem issue. The time worked fine when I used the newer gingerbread leak for a few days.
Sent from my SAMSUNG-SGH-I997 using xda premium
Can you clarify what you mean by a modem issue? Sorry I'm a total noob. I tried GTG's ultimate unbrick and the clock is still off. Market works, but it also worked for about 5-10 min after I flashed it last time.
Thanks for the help so far, hopefully I can get this sorted out.
Also if anyone can suggest a solid GB rom with working activesync/SSL I'd be pretty happy. I tried the most recent Infused, but I really need to be able to sync my corporate email and that isn't possible with Infused.
Edit: Fixed time by checking and unchecking automatic time and it looks like the proper time is staying. Also, the market is also working just fine! Thanks for all the help! Still open to some custom rom suggestions
Edit 2: I'm a liar, rebooted the phone to test and it reboots with the improper time :-\ Market still works on reboot though
Installed Infused 1.6.0 just to have something working on my phone, but that also failed to fix the time. (My phone == my alarm clock, so this has been more than a bit annoying)
Thanks for the continued help!
Not sure if bumping is frowned upon, feel free to yell at me if it is, but I could still use some help!
http://forum.xda-developers.com/showthread.php?t=1265207
Flashed to KI3 and now the clock works, thanks for the tip on the modem.
Related
Hi Guys,
I checked around but I couldn't find anything. I rooted my phone using the 1 click method provided here http://forum.xda-developers.com/showthread.php?t=1096384 This part went swimmingly. I had my phone rooted and ready to go. I then downloaded CPU set and the program would not let me speed up the CPU past 1 Ghz. so then I downloaded this: kernal netarchy-nexus-1.3.0.2-bfs-2.3.3-cm7-compat-signed which supposedly allowed me to overclock my phone. I then placed the zip file into the root directory of my phone. I downloaded ROM manager and used that to install netarchy-nexus-1.3.0.2-bfs-2.3.3-cm7-compat-signed. When I did this the screen went black and the capacitive buttons at the bottom lit up. I can reach the recovery screen but that is it. There is no USB connectivity with the computer. Is there anyway to fix this or did I just turn my phone into a paper weight.
Thanks,
Cloo
Phone processors are a funny thing. Some can handle being overclocked higher than others. I am assuming that you went all the way up to 1400 and your CPU just gets too hot and everything locks up on you. You need to have a rooted Rom on the root of your sdcard and wipe everything from recovery and flash the Rom from recovery and start over. If you go with Netarchy's kernel again I suggest bumping the CPU up to 1200. If it can handle that bump it up to 1300 and obviously it can't handle 1400. You won't see much of a benefit from 1000-1300 for the most part. I keep mine on 1200 and it runs great. Anything higher for me and the phone starts to get hot and lag somewhat. Your phone is not a brick. If you can get to recover and/or bootloader there is always hope.
Also check out these threads to help you get back to 100% stock and start over.
http://forum.xda-developers.com/showthread.php?t=1072698
http://forum.xda-developers.com/showthread.php?t=1103727
Do you have a NS4G which is what the one- click is developed for or a Nexus S, which is what the Kernel you flashed is for? My guess is that you flashed a kernel which is not compatible with your rom.
Sent from my VEGAn-TAB using Tapatalk
You may not have waited long enough for the phone to boot. His bfs based kernels have a bug that most of the time the phone boots to a black screen captive light shows and no boot animation. It will boot but just takes time of you have right kernel. This is spoken about in his thread.
@housry I never got all the way through the switch to netarchy. Once I used ROM manager the screen blacked out upon reboot and nothing happens now. I managed to get the file SamsungSimpleDL onto my phone but when I try to install it aborts. Any thoughts?
@debh I have the NS4G
@Jerry the phone has been sitting with a black screen for about 10 minutes so I think I screwed something up
According to your op, you flashed a 2.3.3 cm7 kernel. Are you running stock 2.3.4? You need to flash the correct kernel for your rom.
Also, I just read your post above and you aren't supposed to flash the simple.zip on your phone. Download and extract the contents onto your computer and run the .exe from there with your phone connected.
Sent from my VEGAn-TAB using Tapatalk
Deb thanks for the quick reply, am I supposed to have my phone in download mode?
Phone is fixed!!! Thanks to all!
Quick question, im sorry, as I didn't know where to ask. Even checked threads and couldn't find an already posted answer. I have a ns4g, rooted, still on stock rom. Will I still get ota's from google when they push newer software than 2.3.4, which is what I run, and also get ota software bug fixes from goolge when they release it? I really hope so, as I want to stay current with the latest builds from google.
Sent from my Nexus S 4G using XDA App
sh4nk said:
Quick question, im sorry, as I didn't know where to ask. Even checked threads and couldn't find an already posted answer. I have a ns4g, rooted, still on stock rom. Will I still get ota's from google when they push newer software than 2.3.4, which is what I run, and also get ota software bug fixes from goolge when they release it? I really hope so, as I want to stay current with the latest builds from google.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
It will be faster to find them on XDA than the wait for OTA
Thank you Plus waiting a little bit will skip any bugs to be fixed lol
Sent from my Nexus S 4G using XDA App
Good Morning XDA!
I've been a lurker on these forums for a while, and I've tried every ROM for the S4G that you incredible devs have released. I haven't had any issues that weren't my fault like forgetting to do something or skipping a step in the flashing process....and I'm sure that's all this issue I'm having now is.
BUT...
I just flashed Somairotevoli's Simply Simple Beta 1.5 and while reading the latest comments in that thread, saw someone had success with bhundven's new KJ6 kernel. I went ahead and flashed that, as well and now everything seems to be running just fine EXCEPT..I keep getting a force close window that says
The process android.process.acore has stopped unexpectedly. Please try again.
Can anyone tell me if I did something wrong when flashing through CWM? I was going to post in the Android Dev section, but I don't have enough posts.
Thanks in advance!
That's an issue with my beta. looking into it.
Sent from my SGH-T959V using Tapatalk
I really appreciate all your work, man. It's not causing anything major, I don't think..just random popup. But the new update looks and runs GREAT! Thanks again!
Weird thing is I thought it was gone as I can't reproduce it. if I flash version 1.0, set it up, then flash my beta, it doesn't happen. So maybe data/factory wipe will fix it, but will have issue fixed before next final
Sent a from my SGH-T959V using Tapatalk
I'll reflash and see if that works. Do you suggest flashing the KJ6 kernel again, also, or just your ROM then your beta update?
Last time, I just flashed your ROM, then beta update, then kernel.
Flash ROM, go through setup.flash update, flash kernel. That's what I did
Sent from my SGH-T959V using Tapatalk
I get the same message. My phone crashed when I rooted it and began trying to kill unwanted apps by deleting files. I reflashed with the first thing I could find that seemed close to stock, KB5, Kernel 2.6.32.9. My firmware version is 2.2.1 and since the phone is a little buggy and slightly slower under load than the stock froyo software, I'm trying to reinstall the original o.s. This will also restore any hardware acceleration that was disabled by the alternate build.
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.
Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App
thanks for the advice guys!
I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?
You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App
This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.
One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.
yep
+1 Valhalla black edition! Installed today and love love love.
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).
UPDATE 6-15-2012: i just wanted to update the beginning of this post to make it a little clearer, the original text is below
to get the v21y base band on your phone over the air, you have to go back to stock
to do this you need a stock rom, either your own backup or the one from this thread
http://forum.xda-developers.com/showthread.php?t=1248644 (the first and second link is a stock 2.3.3 nandroid which is a zip you extract on your pc and run flash.bat from inside that folder)
if you need the drivers, download the third link.
follow the steps in that thread, it works
if you have your own stock nandroid, just boot into ClockworkMod Recovery and restore it (after you backup whats on your phone now)
then reboot your phone
after restoring either your stock nandroid or the one from the post above, shut your phone off and remove the battery and use NVFlash to restore the stock recovery
http://forum.xda-developers.com/showthread.php?t=1056847
reboot your phone
now that you have your phone like it was from the beginning you can go to System Settings/About Phone and click on Software Update. this should pull down the updated Gingerbread version 2.3.4 and the new baseband v21y. IT WILL OVERWRITE YOUR PHONE AND WILL BE PLAIN STOCK
it takes a few minutes so be patient
once it is done and it rebooted your phone you will have to put ClockworkMod Recovery back on it using NVFlash. then you can flash other roms to your phone
please keep in mind that there is a bluetooth issue with both GB and ICS roms on this baseband and that only a few roms actually support v21y. Owain has written an update file that you flash to get support on any rom with v21y, supposedly it does work on any rom (GB or ICS) but i have not tested it, so read up and test if you want.
as of CM7 RC3 all CM7 builds support v21y
please thank the owners of the threads linked above, their methods worked flawlessly for me and i hope they work for you as well. this was a very easy way for me to get the new baseband. good luck!
original post------------------------------------------------------------------------
i was having a heck of a time trying to get the new baseband installed on my phone. i had all the stuff downloaded and all the instructions ready, had the KDZ file, the LG tool, everything...but i could not get anything to work
so what did work?
well using CWM Recovery i restored my stock backup i had made when i first got the phone (best to save this off the phone as well in a safe place) and then using NVFlash i put the stock recovery back on it
once that was done and i was booted back into stock you can go into the About Phone and choose Software Update (or whatever its called) and check for an update. it found one and proceeded to download a 30meg file. asked if i wanted to apply the update, installed it, and rebooted into a nice shiny new 2.3.4 GB setup with v21y and the new baseband installed!
the CM7 nightly build (June 3) is working great. getting ready to try a couple of others (Buru, EB, Genesis (although i was having a problem there, see that thread))
so its only been one day on it but so far calls are good, gps lock is fast, overall loving my phone even more than before!!
Great that the OTA worked for you, I left my phone stock the whole week it was mentioned about sending it and I checked the software update and it always told me the software update check failed/timed out lol
Sent from my LG-P999
I am extremely pleased with the update.
I had been running a rooted stock ROM + CWM Recovery. I had been dismissing the update notice for weeks now. Finally, earlier this week I flashed back the stock recovery and let the OTA proceed.
Current uptime: 67:59:06
I haven't gone a full day without either a random reboot or a sleep of death in a LONG time.
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
edekalil said:
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
which cm7 are you using? i had the last nightly june 3 and could not get mass storage to work
I just did this method too and its a lot easier
---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------
edekalil said:
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
What is the sound update? I thought it was included in the new baseband and is it in the ota update? Thanks
lamdaman said:
I just did this method too and its a lot easier
---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------
What is the sound update? I thought it was included in the new baseband and is it in the ota update? Thanks
Click to expand...
Click to collapse
there were a few people that got a bad motorbooting sound when making calls and lg released an update to the new bb but it was only for people who had the sound issue
its was hard
i swear it was hard trying get it to work but once i found me a stock rom i was all good from there
Can you test if the 6.3.12 nightly has working in call bluetooth?
Joe333x said:
Can you test if the 6.3.12 nightly has working in call bluetooth?
Click to expand...
Click to collapse
i dont believe it was, i just had that installed on my phone and coming to work today i tried to connect it to my car bluetooth and it would not connect. i have an ICS rom on my phone now, hope it works with that...i know it did on EB ICS
updated the first post
Reverted back to stock this morning and installed the OTA update...now i'm back on cm7 with no issues. Great suggestion on an easy way to get the March baseband.
Thanks!
Sent from my LG-P999 using Tapatalk 2
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
adame09 said:
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
Click to expand...
Click to collapse
Use the LG update tool
Sent from my LG-P999 using XDA
adame09 said:
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
Click to expand...
Click to collapse
you are on stock rom AND stock recovery? data connections good otherwise?
A little clarification, if I may...
Could I just flash the stock 2.3.3 nandroid from this thread: http://forum.xda-developers.com/showthread.php?t=1048274 to bring myself back to "stock" then, using NVFlash that's already on my computer from when I first rooted my phone, flash it back to stock recovery? After that, try the OTA to get myself to 2.3.4 or, if that doesn't work, use the LG Updater tool? Then just root my phone again and go back to enjoying custom ROMs?
Seems like it would be easier and one step less if I get the nandroid from that thread rather than following the link in the OP and having to extract something on my computer.
partylikeaninjastar said:
A little clarification, if I may...
Could I just flash the stock 2.3.3 nandroid from this thread: http://forum.xda-developers.com/showthread.php?t=1048274 to bring myself back to "stock" then, using NVFlash that's already on my computer from when I first rooted my phone, flash it back to stock recovery? After that, try the OTA to get myself to 2.3.4 or, if that doesn't work, use the LG Updater tool? Then just root my phone again and go back to enjoying custom ROMs?
Seems like it would be easier and one step less if I get the nandroid from that thread rather than following the link in the OP and having to extract something on my computer.
Click to expand...
Click to collapse
yes that will work as well and whether you get a stock rom from the link i posted or the one you posted makes no difference this was just how i did it
Hey, thanks! I've been wanting to update my BB ever since it became compatible with the new ROMs, just haven't been able to set aside the time to be able to do that. Just wanted to make sure I had it right before I attempted.
Your steps sounded easy and straight forward; it just never hurts makes sure!
Thanks again, bro.
partylikeaninjastar said:
Hey, thanks! I've been wanting to update my BB ever since it became compatible with the new ROMs, just haven't been able to set aside the time to be able to do that. Just wanted to make sure I had it right before I attempted.
Your steps sounded easy and straight forward; it just never hurts makes sure!
Thanks again, bro.
Click to expand...
Click to collapse
you're welcome
there is a bluetooth issue with all roms and the new BB so if you use BT you might want to stick with the stock 2.3.4 that you will get with the upgrade. lots of devs are working on that issue so hopefully it wont be long
suggestions?
I followed the instructions in the first post, and now am back on the stock rom (21e, july 15 2011). However, when I go to try the software update, I get the following message: "current version is the latest version." Is there another way to get the new 21y baseband?
Not getting a cell phone signal at all on my Captivate. very rarely I get it and it stays on until I reboot for some reason, or sometimes goes off on its own. No problem with wi-fi or anything else.
Have had Gingerbread 2.3.5 - KK4 (official) for a long time, and did not have this problem. Here is what I did:
Installed Cyanogenmod 9.0 (ICS 4.0.4) on my Captivate that had the stock Gingerbread KK4. Also installed the gapps-ics package from 29 April 2012
I did this after rooting, and installing clockworkmod.
Even updated it to Cyanogenmod 9.1, but have the same issues.
More detail on it:
- The cellular radio shows no signal, but Wifi is on fine.
- When I press the power button, I see the power off and reboot options, including one that says "Airplane Mode is ON", although it clearly isn't since Wifi is working
- A couple of times, I rebooted into recovery, and did a "repair permissions" and rebooted, and it got a signal, but does not happen always
- Once the signal is on, it stays on for the whole day, but goes off again after a reboot
- Turning Airplane mode on and off does not help
Is this a modem issue, that seems to be a popular problem. It's almost as if there is a software bug that fools the phone into switching off wireless radio
Please help me fix it, or share successful fixes
I had same problem when I went to helly bean then back to remics-jb I flashed back to stock then back up to what I wanted it fixed the problem so I think its the modem.
Sent from my SGH-I897 using xda app-developers app
You need to flash to stock and back.
Sent from my SGH-I777 using xda premium
How do you flash your rom?
Im a little bit afraid to bricked again my cappy.
Sent from my SAMSUNG-SGH-I897 using xda premium
KOROCK is right
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
up_on1 said:
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
Click to expand...
Click to collapse
Not fixed yet. Wheredo I get the stock rom.?
rdugar said:
Not fixed yet. Wheredo I get the stock rom.?
Click to expand...
Click to collapse
A little search/reading goes a long way.. http://forum.xda-developers.com/showthread.php?t=1300843
KK4 is what you'll want to go back to stock but I highly suggest you read this before you do anything http://forum.xda-developers.com/showthread.php?t=1350266
Also, before returning to stock, you could try flashing a different modem.
Check to see if your baseband is still there. If it said "Unknown", you need to restore it. CM9 is supposed to have the modem.bin file included though. Check to see if the /radio folder have modem.bin in it, if it does, and the baseband still say Uknown, then manually delete the modem.bin, do a wipe and reflash a CM rom that have modem.bin included.
If Baseband is still there and still no signal, then check to see if IMEI is corrupted or lost (if its null or doesn't match the back of the phone). You can either copy over the efs backup folder if you have one and "fix permission" in CWM. If not, then you need to ODIN the phone to stock to fix it.