Related
Need to get back to stock rom, or GB2.3.3, already rooted and want to keep it that way, spent las 3 hours looking here and nothing is working, downloaded 4.53.651.1_Rooted_Odexed_Signed and that didnt work, gave me FCs. The stock odex did the same. what else is there?
So you have already flashed a stock ROM based on the latest OTA and you are getting problems? I have been reading that the latest OTA has bugs and people who have never been rooted have been getting restarts and FCs. Perhaps the reason for your problems is due to the OTA itself and not a corrupted stock rom. I have flashed the same 4.53.651.1 rom as well (expcept it was deodexed) on my spare EVO; however, I have not played with it to see if there are any problems with it as I do not have enough time and I am just getting ready to get rid of it. If you would like the deodexed rom, I can dropbox it for you... Let me know.
gellybelly said:
Need to get back to stock rom, or GB2.3.3, already rooted and want to keep it that way, spent las 3 hours looking here and nothing is working, downloaded 4.53.651.1_Rooted_Odexed_Signed and that didnt work, gave me FCs. The stock odex did the same. what else is there?
Click to expand...
Click to collapse
Did you do a total wipe,except the SD card?Theres a reason your getting FC's,heres a good sock rom with the new update... http://forum.xda-developers.com/showthread.php?t=1412005 ,also concider partitioning your sd card... http://forum.xda-developers.com/showthread.php?t=1158993
yeah did a full wipe and partition first time, with the first one, and then the same with the second time. Going to try the one you linked.
Diablo67 said:
Did you do a total wipe,except the SD card?Theres a reason your getting FC's,heres a good sock rom with the new update... http://forum.xda-developers.com/showthread.php?t=1412005 ,also concider partitioning your sd card... http://forum.xda-developers.com/showthread.php?t=1158993
Click to expand...
Click to collapse
That one worked great thanks, I'll have to sticky this one for later usage, on other tester phones.
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Did you do a full wipe ???
ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).
Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.
I have noticed a few people complaining of call echo with AOSP ROMs (even with "noise suppression" checked), as well as some stock based ROMs. I was having the same problems. Stock based ROMs were better, but echo was still there. I tried several radios without avail.
What finally worked for me was going back to stock through Kies (keep in mind this will wipe your internal sd as well, so move your backups off your phone). I have since been able to flash PACman ROM without call echo. I have not tried any others but I assume the result would be the same. If someone is willing to test other ROMs/radios and report back that would be great. I just don't have the time.
Also, I did not flash a different radio after going back to stock. I assume it would be okay to do so, but I am not a dev so that is only a guess. What I think going back to stock fixes is some missing/corrupted libraries that are somehow surviving ROM flashes (like in a protected storage or something like that).
Anyway, I hope this helps someone else.
EDIT: This doesn't work all the time, and has only really worked for me once. I have done it twice and it worked great the first time, and not really the second. It's worth a shot, but just keep this in mind.
:::Specifics:::
Essentially all I did was go to the latest stock rom image from T-Mobile. Kies upgraded my phone to UVLI1, which is T-Mobile's latest 4.0.4 stock rom. Kies essentially wiped everything from my phone (except external storage) and imaged it with the latest factory image which includes the latest radio. I have since been able to root, install TWRP and flash an AOSP based rom without degradation in call quality. I did not flash over the radio that was installed by Kies, and I did not wipe android secure in TWRP (don't know if that made a difference).
What you should try if you are having call quality issues:
1. Go back to stock unrooted (use your method of choice, I used Kies but that doesn't work for everyone so try Odin or Heimdall)
2. If you didn't go to the latest stock unrooted image from T-Mobile and Samsung, do that through Kies which should now work for almost everyone (as of Jan. 1, 2013, the latest stock image is UVLI1/TMBLI1)
3. You should now be able to root and flash any rom you like without call quality degradation (if this is not true for you please let me know --- see above for what I did at this point)
I'd be interested in getting some feedback from this. Keep in mind that I am not always available and may only be able to reply once a day or less. Again, this is just what worked for me, it may not work for you. Please give yourself plenty of time when going through this process as Kies is not very fast (at least in my opinion).
UPDATE:
Here is how I got Kies to update my phone while still rooted and even running an AOSP rom. As always, do this at your own risk. I accept no responsibility for broken devices or lost data/pictures/music/etc. However, I have done this twice now, so just read and understand what you're doing and you should be fine.
Keep in mind that this WILL WIPE YOUR INTERNAL STORAGE! You have been warned.
1. Disconnect your phone from your computer
2. Launch Kies and click on Tools>Firmware Upgrade and Installation
3. Input model number (it's case sensitive !?) and hit OK
4. Input serial number (found under battery) and hit OK
5. Hit okay on windows until it starts downloading the latest firmware for your phone
6. After it's finished downloading it will tell you to put your phone in download mode and connect it to your computer. Do it, check "I understand..." and hit OK (I also opted out of the sending of information to Samsung)
7. Wait until it's finished. It will likely launch a window saying it's downloading a file for emergency recovery of your device.
8. When it's (finally) done it will tell you it was successful (hopefully). Your phone will automatically reboot and all will be well with the world and your phone.
Hope this helps.
kies fails recognize my phone. already have the phone drivers installed.
You have an interesting post, but it would be of more use to people if you specified the exact information about what's on your phone. Such as which stock ROM version you were able to flash through Kies and what radio version you are currently using.
There are different stock ROMs and radios on the forums, so it doesn't solve anything if you haven't told us what exactly works with your phone that others should try.
Here is the rub. I haven't been on stock unrooted rom since buying the phone in March. I have bounced around roms and radios quite a bit (probably at least one or two a week on average). My wife has complained of call echo for a long time (multiple roms, multiple radios and AOSP and touchwiz based roms). Touchwiz based roms had better call quality but echo was still present. I decided to Odin back to stock unrooted and see if it was a hardware issue or not. It wasn't a hardware issue because call quality was great. So I rooted the phone, installed the latest TWRP (2.3.3), but wasn't happy with stock rooted so I decided to try an AOSP rom. I wiped only cache, dalvik cache, system and data (not android secure, don't know if that made a difference or not). It works great; i.e. no call quality issues. I did not flash a radio.
So, essentially what I did was:
1. Went back to stock unrooted (Kies put me on latest 4.0.4 from T-Mobile, which flashed a radio, the rom and cleared internal storage)
2. Rooted and installed TWRP
3. Flashed my rom of choice, but not a radio and I didn't wipe android secure (not sure if that matters)
Honestly I don't know what about that process fixed the echo issues, all I know is it did. If you can't go back to stock unrooted through Kies then use Odin. There are great threads giving step by step instructions on how to do that. I just decided using Kies would be easiest for me, and it worked for me.
I hope these are the details you are looking for FineTalent. And thanks.
Excellent lol. If you own the d30 case from tmobile take it off. Worked for me as well.
I do have the d30 case but taking it off didn't seem to make a difference. Besides, the wife didn't like the idea of my phone going commando.
I used odin to go back to stock and the call quality was great. But as soon as i installed an AOSP rom (All Star Rom V6) the echo was back.
I did not know that LI1 was the latest 404 ROM ?
I can only get VLH1 as the latest ROM.
I know there is a LI1 radio available, but have never seen the LI1 rom itself, especially not on SamMobile/Firmware site.
Any links to the "official LI1 ROM"
Thanks
bert269 said:
I can only get VLH1 as the latest ROM.
I know there is a LI1 radio available, but have never seen the LI1 rom itself, especially not on SamMobile/Firmware site.
Any links to the "official LI1 ROM"
Thanks
Click to expand...
Click to collapse
It was simply the latest one Kies found for my phone. I believe it was labeled as UVLI1/TMDLI1, but I suppose I could be mistaken. If you install Kies on your computer (shudder, I know) and plug your phone in it will compare the rom version on your phone to the latest known rom from tmobile/samsung. You will need your phones serial number I believe. At least, it was needed when I "upgraded" anyway.
whytechapel_x said:
I used odin to go back to stock and the call quality was great. But as soon as i installed an AOSP rom (All Star Rom V6) the echo was back.
Click to expand...
Click to collapse
Can you give the following information:
1. Method of obtaining root
2. Custom recovery odined when obtaining root (I assume it's cwm 5.0.2.7)
3. Custom recovery used to flash AOSP rom
4. Steps taken to flash AOSP rom (I don't want this thread to become a "this is how I flash" thread, but I want to know what was different between your experience and mine, so wipe and install steps would be great)
5. Any mods flashed/done before testing call quality (or was it completely clean, i.e. just rom and gapps)
6. Which gapps did you flash (mine was latest for 4.1.2, so gapps released on oct. 11, anything later is for jb 4.2 and not compatible with 4.1.2 according to release notes)
monkeybuttons said:
Can you give the following information:
1. Method of obtaining root
2. Custom recovery odined when obtaining root (I assume it's cwm 5.0.2.7)
3. Custom recovery used to flash AOSP rom
4. Steps taken to flash AOSP rom (I don't want this thread to become a "this is how I flash" thread, but I want to know what was different between your experience and mine, so wipe and install steps would be great)
5. Any mods flashed/done before testing call quality (or was it completely clean, i.e. just rom and gapps)
6. Which gapps did you flash (mine was latest for 4.1.2, so gapps released on oct. 11, anything later is for jb 4.2 and not compatible with 4.1.2 according to release notes)
Click to expand...
Click to collapse
1.Well i didn't root my stock phone. After using odin
2.I used cwm 6.0.1.5
3.Same.
4. Well i followed the steps in the all star thread which is wipe data/factory reset. Then flashing rom and wiping cache and dalvik cache.
5. The all star rom is heavily modded so idk. I tried it with "noise suppression" on and off.
6. All star gapps.
I want to point out that as soon as i flashed jedi knight 6, the call echo was gone but i want to be able to use my AOSP roms without call echo.
Since I'm not a dev I can't really diagnose the problem. I only hoped that what worked for me would work for others as well.
When I went back to stock I rooted, but didn't like stock. TWRP has been my go to recovery for a while now and the options available in PACman rom have me by the heart strings, so those are the first things I tried. I wish I had time to fiddle around with it and truly try to find out why it worked for me but I just don't have that option right now. Sorry I'm not of more help.
Its OK. But can a dev clarify if maybe clockworkmod is what is causing the call echo? Probably not flashing AOSP ROMs right?
whytechapel_x said:
Its OK. But can a dev clarify if maybe clockworkmod is what is causing the call echo? Probably not flashing AOSP ROMs right?
Click to expand...
Click to collapse
CWM is in no way linked to the call echo issue, however, using the latest version will assist in ensuring your ROMs installs properly. Rather than using CWM I recommend flashing ROMs through TWRP 2.3.3.0, it is the most up to date recovery system for our phones at the moment.
FineTalent said:
CWM is in no way linked to the call echo issue, however, using the latest version will assist in ensuring your ROMs installs properly. Rather than using CWM I recommend flashing ROMs through TWRP 2.3.3.0, it is the most up to date recovery system for our phones at the moment.
Click to expand...
Click to collapse
OK. I went on and installed TWRP anyways and flashed tweakwiz and got call echo once more. I am aware that it flashes the blaze radio but still. Does this mean that my phone came out defective? But why is it that i get absolutely no echo on stock ics and luckily, jedi knight 6 neither? When i was using jedi knight 6,i was using the stock radio uvlh1? But if i have this same radio on AOSP roms or in other ones, i still get call cecho.
whytechapel_x said:
OK. I went on and installed TWRP anyways and flashed tweakwiz and got call echo once more. I am aware that it flashes the blaze radio but still. Does this mean that my phone came out defective? But why is it that i get absolutely no echo on stock ics and luckily, jedi knight 6 neither? When i was using jedi knight 6,i was using the stock radio uvlh1? But if i have this same radio on AOSP roms or in other ones, i still get call cecho.
Click to expand...
Click to collapse
I am not able to exactly help you with your issue as I am using a different ROM than you. However, if you have tried different radios and they did not seem to fix the issue, can you possibly try installing a different kernel? Also, check the phone settings and see if there is an option to turn on 'Noise reduction' which has been mentioned on here before, it seemed to have worked for some people.
So i noticed that i get call echo on all jellybean roms no matter if they are touchwiz or not...frustrating
whytechapel_x said:
So i noticed that i get call echo on all jellybean roms no matter if they are touchwiz or not...frustrating
Click to expand...
Click to collapse
Keep in mind the Touchwiz jb roms are actually built off the leak for the Skyrocket. The same thing happened with ICS way back when and call echo was a rampant problem then as well. I don't recall if anyone really solved the problem before official ICS dropped for Hercules, but I know a lot of devs were working on it.
Call echo in stable AOSP based roms shouldn't be happening. That's what we're trying to correct here.
If you have the time (or are willing), go back to stock unrooted (so you get the radio and everything) and try flashing cm10 stable. Then report back and let us know if call echo still exists. I'm not trying to knock All Star roms, I am just trying to get to the root of your problem and that involves avoiding flashing a radio. As far as I can tell, the flashing of the radio is the biggest difference between your experience and mine.
monkeybuttons said:
Keep in mind the Touchwiz jb roms are actually built off the leak for the Skyrocket. The same thing happened with ICS way back when and call echo was a rampant problem then as well. I don't recall if anyone really solved the problem before official ICS dropped for Hercules, but I know a lot of devs were working on it.
Call echo in stable AOSP based roms shouldn't be happening. That's what we're trying to correct here.
If you have the time (or are willing), go back to stock unrooted (so you get the radio and everything) and try flashing cm10 stable. Then report back and let us know if call echo still exists. I'm not trying to knock All Star roms, I am just trying to get to the root of your problem and that involves avoiding flashing a radio. As far as I can tell, the flashing of the radio is the biggest difference between your experience and mine.
Click to expand...
Click to collapse
will do. but if i remember, i would still get call echo on aokp milestone 1
whytechapel_x said:
will do. but if i remember, i would still get call echo on aokp milestone 1
Click to expand...
Click to collapse
Have you tried any ICS based AOSP roms? Like cm9.1 or AOKP (I can upload the file for you if you want; it is no longer on goo.im). I think I kept ICS AOKP the longest of any rom.
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
JonoPorter said:
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
Click to expand...
Click to collapse
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d a bad flash in a custom recovery but everytime I have to use Odin I get extremely nervous.
Read Beerdroid's guide and you can't go wrong
hednik said:
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d abad flahs in a custom recovery but everytime I have to use Odin I get extremely nervous.
Click to expand...
Click to collapse
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
xBeerdroiDx said:
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
Click to expand...
Click to collapse
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
JonoPorter said:
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
Click to expand...
Click to collapse
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
hednik said:
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
Click to expand...
Click to collapse
i'm an advocate of AOKP, but thats just my 2 cents. there is a very solid 4.1.2 milestone out and their 4.2.2 milestone will be released very soon.
although faryaab is a great kid and puts some good stuff together, remember that supernexus is a port and you could experience bugs (as i did). again, just my opinion
Hi
Guys i need your help. Pleas can someone tell me for now what mods is much better for I927R (Also withe very stability and with much less bugs) ?!
I found Liquid Smooth but it have some problem so i need your guide about other mods.
Thank you
ICS Roms are the best and most stable... Stock ICS from AT&T UCLJ3 or any roms based off of it ... Dman's daily driver, Ice Pop Rom by RawRaw, LiteRom by TheGreaterGood...
Unfortunately none of those are being maintained but I had been running Dman's for the last couple months, great battery life when paired w/ JuiceDefender (20+hours of heavy use when I'm not sleeping).
Now the newest CM10.1 by Spyke seems pretty solid ... Just a couple of issues.
ICS is the only one you'll get bug free, though. Stock is hard to compete with when we're pairing up roms without a true Devdeloper.
On this subject, I've just reverted back to using IcePop ROM after (unhappily) downgrading from Spyke's latest 10.1 ROM - just mainly because of the Bluetooth headset issue, which I really need working for work purposes.
I'm just wondering if there are any ICS builds that have GPS working correctly? I tried flashing the Rogers modem (since my phone was originally a Rogers import, flashed to AT&T ICS, then played with ICS from there) and first time I ran GPS status it took 771 seconds... I'm going to keep trying just in case that was the first time only, but 12 minutes is still a very long time for an initial fix .
Also - I've found that I'm getting more and more bootloop problems even with clean installs - so wiping cache, data, dalvic, etc. Is there some way to do a *thorough* wipe without bricking the phone? I can back all my data up no worries, but next time I move to JB (in the optimism that the BT issues will be fixed soon, judging by the positive progress being made by Spyke ) I would like to do a clean build from scratch and not have to gamble being able to start the phone up again
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
I, also, had reverted to using JB Because GPS wouldn't work ... There's a thread in here (search for it) that shows the solution to the GPS fix, its editing sirgps.conf and gps.conf ... I was getting a fix on GPS in under 30 seconds.... GPS was a huge let down in the stock ICS rom, Even when using TheGreaterGoods LiteRom w/ GPS fix I found after a couple of days my gps didn't hold....
Thanks for the reply.
I was considering formatting /system this morning when I was getting stuck in a boot loop from trying to get M3 running, but decided it was a risk I'd have to check up on first . Next time I do a build from scratch (I'm going to resist until the BT stuff is working - fingers crossed!) I'll do that.
I remember having a look at the gps.conf fix but don't recall anything about sirgps.conf - so I will look it up, thanks!
As an aside, I've been checking the GPS fix a couple of times since my last post and it is coming up in under 30 seconds each time... I'm wondering if my attempt to flash the Rogers modem did in fact fix the issue... I'd do a reboot but I'm too scared I won't get the phone up again XD
EDIT:
Found the fix, I did a few of the changes (rather than all of them), and it's now picking up 8 satellites instead of 3-5, and getting a stronger signal from each... and all I did was point it to the AU ntp server, and tell it I'm not on the ATT network . I'll save the suggested settings to a text file on my SD card so next time I'm out and about and if it plays up I'll have access to the details.
yohan4ws said:
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
Click to expand...
Click to collapse
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
davidpartay said:
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
That has to be very concerning to you, I've never had an issue booting any ROM. And very strange flashing the Kernel separately would resolve your booting issues...
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
If I were in your position I would try and do a full revert back to the earliest version of gingerbread I could find on samfirmware and then use Kies to udpate - THEN I would retry flashing to a newer JB or ICS Rom.
Pretty time consuming but that is the price we pay to mod
davidpartay said:
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
yohan4ws said:
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
Click to expand...
Click to collapse
Not yet. I'll have to check which ones I have - I'm certain I have the AT&T ICS rom from November but then I'd have to go digging through my email for the unlock code again, so I'm trying to avoid doing that at this point . If i can find the stock GB Rogers rom at some point I might flash that one back on before I do any more upgrades. The phone is up and running at this point though, so I'm not too fussed. I've also noticed that it's a little quicker than before so I think the version of LiteKernel I installed was a good idea anyway.
bubor said:
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
Click to expand...
Click to collapse
I've tried pulling the battery a few times, but probably no longer than 30 seconds. Next time I'll give it a couple of minutes. I tend to do this late at night when I'm not expecting any calls (except fire brigade but I have a pager for that too) so time without a phone is no issue to me
Yesssss
After much irritation at continually getting stuck in boot loops again, I've 'Oneclicked' the phone twice, got fed up with the AT&T ICS ROM within about 5 minutes, gave up on IcePop because of buggy GAPPS...
And thought, bugger it. Format /system. Factory reset. Clear cache + Dalvik. Installed in this order:
Jellybean 4.2 ROM from 0217
Spyke's M3 update
PAC rom
GAPPS dated 0427
"Kick-ass Kernel"
and it BOOTED FIRST GO
I am pleased
Does JB need already to be installed before putting the M3 revisions on? Maybe that's where I've been going wrong all along, because my attempts at running both the standard M3 and PAC ROM (even immediately after OneClicking) resulted in boot loops or eternal boot loading.
Uhh... what do you mean by "One Clicking" ??
I know there's a "superoneclick" that will flash and root the rom all at once, but I never personally found it to work for our glides.
Using CWM and installing the ROM through the CWM boot menu is severaly key presses so ... not too sure what you're referring to.
Also, I've always downloaded to a hardwired computer then copied over USB to my phone and flashed ... sometimes the download will have errors if I grab it from my phone.
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
davidpartay said:
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
Click to expand...
Click to collapse
Interesting... for future reference, www.samfirmware.com has the stock firmwares, then there's the superUser file floating around the forums that allows you to root by flashing it. Passed that, remove bloat.
Glad you got it working! Welcome to JB