Related
There seems to be a major issue with the 4.06 radio and my phone - every time I have tried to flash it (from both validated .img's and update.zips) my phone becomes extremely unstable afterwards.
It goes into booting loops, hangs at the X, when I get it to boot it crashes while using heavy 3G or WiFi data, reboots when plugged into USB and receiving a call and it becomes almost impossible to get into recovery mode etc, etc.
The only way to get back to a working phone is to revert to stock 4.04. I have tried 5 different times over the last 2 weeks now with the same results every time.
I am starting to wonder if it is a AT&T/Rogers N1 issue or something specific to my device. If it was my device I would think that flashing back to 4.04 would also cause problems but that is not the case. This makes me believe there is there maybe an incompatibility with the leaked Froyo radio.
Appreciate any thoughts/comments.
I'm not having that problem. I flashed Modaco's first FroYo repack with root and the new radio, and things have been fine. To be honest, the only thing I've noticed is that Bluetooth seems to sync a lot faster to the head unit in my car.
Did you do a complete wipe before you installed the update and what applications have you added that may not like the radio?
Edit to add: By the way, you guys have a kick-ass little HTC Magic up there. It may not be a Nexus One, but it more than holds it's own running cyanogen. I have an import that my wife is playing with. I really like it.
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
I just verified my version - it's definitely the 4.6.00.12_7 Froyo radio firmware.
codesplice said:
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
Click to expand...
Click to collapse
I tried the 12_7 last night and after flashing it using fastboot, my phone got stuck in a reboot loop. I could get back into fastboot and saw the new radio version on the screen but could not for the life of me get my phone to boot into either the rom or recovery mode - I pulled the battery, took out the SD card etc but nothing worked. This prevented me from flashing a ROM and I could not get into Recovery. After about an hour of trying, I managed to get the 4.04 radio flashed using fastboot and then my phone booted with no problems.
Previously, I tried the various Froyo builds and with no additional apps installed I would still get random roboots when using data via either 3G or WiFi - usually when I try to do something big like downloading/syncing a large file.
This is the story every time I try a 4.06 radio. 4.04 is rock solid.
Have you tried flashing the 4.6 radio via an update.zip as opposed to through fastboot? It's about the only other idea I can think of lol...
Just checked, I flashed the 2_2 last night, not 2_7.
I have flashed the radio via update.zip before and my phone worked but would be unstable. I will have to double check which version I used, could have been 2_2 as well.
codesplice said:
Come to think of it, that's the radio version I'm currently using, and that's where I got mine while I was running his ROM. So yes, flash that zip, flash Kangorama, and you should be square.
Click to expand...
Click to collapse
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Maybe try the 12_7 radio from http://forum.xda-developers.com/showthread.php?t=692609 ? I'm fairly certain that is the same radio update that I have applied on my AT&T N1.
edit: disregard....
I'm running out of ideas, dude
codesplice said:
I'm running out of ideas, dude
Click to expand...
Click to collapse
I appreciate your input. Thank you. I will try _7 again.
DvTonder said:
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Click to expand...
Click to collapse
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
attn1 said:
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
Click to expand...
Click to collapse
The crashes started just after I got the Rom installed.
I did the following:
- Nandriod backup (thank goodness for this!)
- I wiped all as per instructions
- Installed radio, rebooted OK
- Installed ROM (Rodriguesstyle 1.6)
- Booted OK into setup
- Configured my phone - first crash just after entering my gmail ID and the syncing of all the apps from the market started
- Rebooted, configured my phone again - apps installed this time but while configuring ChompSMS the phone rebooted again
- Rebooted, phone came up clean, ran OK all day
- Got home and tried syncing Audible content - phone crashed
- Could not get into recovery or boot the phone normally for almost an hour (pulling battery etc did not help)
- Pulled the SD Card and the phone booted, shut down, put the sd card in again, phone booted OK
- Got a phonecall, phone rebooted
- Got fed up and restored 4.04 radio and stock ROM
- Phone stable since
I was running the following apps:
- Autokiller
- Doubletwist Player
- Audible beta
- Silent Sleep
- ChompSMS 4.2
- Switchpro Widget
- Barcode Scanner
- ADW Launcher
- newsRob
- File manager
- Backgrounds
- Rom Manager
DvTonder said:
The crashes started just after I got the Rom installed.
I did the following:
...
- Installed ROM (Rodriguesstyle 1.6)
...
Click to expand...
Click to collapse
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
attn1 said:
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
Click to expand...
Click to collapse
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
DvTonder said:
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
Click to expand...
Click to collapse
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
attn1 said:
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
Click to expand...
Click to collapse
Point taken. Back to the basics.
I came straight from Rodriguesstyle 1.6 with the included add-on OV/UV kernel to Kang 0.8b1 without any issues. Even got the 720p hack working beautifully
well i am using the new froyo radio with my ATT nexus one, and its been no different than the old radio. no crashes or anything. however, i had NO idea that there were 2 froyo radios. is that what someone just posted on the first page?
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Let's hope that's not OPs issue, though the problem seems to be pointed in that kind of direction. Hope you get your situation resolved under warranty.
chordmasta said:
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Click to expand...
Click to collapse
So Bell Canada and Samsung both have terrible technical support.
My phone is i9000m, Bell Canada, running 2.3.3 (UGKG3). It had 2.2 in the box, and I upgraded through kies pretty recently.
Since the upgrade I have a few new problems that I didn't have before:
-GPS, which used to give me useful and reasonably accurate tracks for my walks and bike rides now spits out a bunch of garbage.
-Download mode still works, but recovery mode doesn't.
-Serious power drain under "Android OS." Upwards of 90% in an hour. Goes away if I kill "google services."
Do a factory reset if you haven't done one already. Most of the time that clears up any update bugs...
Sent from my GT-I9000 using xda premium
ccrows said:
Do a factory reset if you haven't done one already. Most of the time that clears up any update bugs...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
This did nothing for me except give me the headache of re-installing all my apps (again). Still no recovery mode, shoddy GPS, and crazy battery drain... oh and my bluetooth keyboard no longer pairs? What's up with that!?
Anyone have any other ideas???
New issue:
Market hangs at white screen after starting install on 10th app. Reset sometimes allows installing another one or two, but after that it'll hang again.
guardianfox said:
New issue:
Market hangs at white screen after starting install on 10th app. Reset sometimes allows installing another one or two, but after that it'll hang again.
Click to expand...
Click to collapse
Fixed, rolled back to previous version of Market.
New issue since another factory reset (2nd), 10 second delay between button press and lock screen.
I am sorely tempted to defenestrate my phone...
Why don't you flash a custom rom?
Sent from my Galaxy S using XDA Premium App
woolf clubs said:
Why don't you flash a custom rom?
Sent from my Galaxy S using XDA Premium App
Click to expand...
Click to collapse
If I could find a rom that fills all my needs better than stock 2.2, I'd be all over it. I have a lengthy list of requirements though, and warranty eligibility is in the top 3 (especially if I defenestrate the thing).
Can anybody recommend a rom with bluetooth working for wiimote and keyboards, netflix working smoothly (2.2 doesn't, stock 2.3.3 does), good power consumption, and stability?
In the mean time, I'm still dealing with the other issues outlined in this thread.
Flashing a custom rom would almost definately sort all your problems. As to which rom, you seem perfectly capable of reading. If you are worried about warranty, you can simply flash back to stock...........
Sent from my Galaxy S using XDA Premium App
woolf clubs said:
Flashing a custom rom would almost definately sort all your problems. As to which rom, you seem perfectly capable of reading. If you are worried about warranty, you can simply flash back to stock...........
Sent from my Galaxy S using XDA Premium App
Click to expand...
Click to collapse
For me that`s a last-ditch solution. I`m usually in a hurry when I break a phone and I`d want to be able to just plop it down at the bell booth during the work day, rather than taking it home first and flashing it (assuming it`s not broken beyond that point).
Hi,
I recommend you to try perform a Hard Reset with code *2767*3855# in dialer ( formats also your internal SD), flash the phone again (better with Odin) with a "standard" version.
Optional make a new Hard Reset (in special if didn't repartition the phone).
After that you can use a custom rom if you want. In past I used DocRambone rom, but now I preffer S.U.R.F.A.C.E. rom with Hardcore kernel and GO Launcher. GPS, phone, browser ....running without problems and battery keeps me over 50 h of medium use without GPS.
Tried hard reset and flashing the same stock 2.3.3 UGKG3 rom. No change. Still can't get into recovery mode, still crap gps, still 10 second lag between button press and screen on, still crazy battery drain.
Rolled back to 2.2, everything works except recovery mode and having weird problems with market imagining that I have apps I've never even looked at before and difficulty downloading. Market cache clear doesn't help. Hard reset doesn't help.
Upgraded through kies to UGKG3 again. Same problems as before, but market works at least. If no solutions available today, I'm taking it to Bell for service and maybe exchange. If that doesn't resolve I'll flash a custom rom.
DSGE said:
Hi,
I recommend you to try perform a Hard Reset with code *2767*3855# in dialer ( formats also your internal SD), flash the phone again (better with Odin) with a "standard" version.
Optional make a new Hard Reset (in special if didn't repartition the phone).
After that you can use a custom rom if you want. In past I used DocRambone rom, but now I preffer S.U.R.F.A.C.E. rom with Hardcore kernel and GO Launcher. GPS, phone, browser ....running without problems and battery keeps me over 50 h of medium use without GPS.
Click to expand...
Click to collapse
New update...
GPS borked entirely this time. Gets a fix, but the fix doesn't follow me. If I run My Tracks, it just stays in a 10 meter area while I walk in a 4km circle away from and back to that area.
guardianfox said:
Tried hard reset and flashing the same stock 2.3.3 UGKG3 rom. No change. Still can't get into recovery mode, still crap gps, still 10 second lag between button press and screen on, still crazy battery drain.
Rolled back to 2.2, everything works except recovery mode and having weird problems with market imagining that I have apps I've never even looked at before and difficulty downloading. Market cache clear doesn't help. Hard reset doesn't help.
Upgraded through kies to UGKG3 again. Same problems as before, but market works at least. If no solutions available today, I'm taking it to Bell for service and maybe exchange. If that doesn't resolve I'll flash a custom rom.
Click to expand...
Click to collapse
Phone was sent in for repairs and returned to me this morning. GPS still broken (completely, no signal period). Everything else seems fine.
the issues you are having suggest to me the problem is with the KG3 stock rom.
Before getting even more frustrated with both your phone and Bell, I would advocate:
1. do a complete phone clean with sd card reformat (sent you a pm with a link)
2. flash the stock JVR pda in odin and also flash the KG3 modem and CSC at the same time
3. you are then still on stock Samsung, official firmware and within warranty even if that firmware has yet to be released in Canada
4. then if you want you can still flash a custom JVR kernel and a custom JVR rom if you want to improve performance and/or alter features beyond stock
lgsshedden said:
the issues you are having suggest to me the problem is with the KG3 stock rom.
Before getting even more frustrated with both your phone and Bell, I would advocate:
1. do a complete phone clean with sd card reformat (sent you a pm with a link)
2. flash the stock JVR pda in odin and also flash the KG3 modem and CSC at the same time
3. you are then still on stock Samsung, official firmware and within warranty even if that firmware has yet to be released in Canada
4. then if you want you can still flash a custom JVR kernel and a custom JVR rom if you want to improve performance and/or alter features beyond stock
Click to expand...
Click to collapse
Thanks for your help. I'll look into it.
Before I do that, do you or anyone else have the stock settings under *#*#3214789650#*#* (AngryGPS)??? The settings for the SUPL Settings section are all BLANK!!! I can only assume the rest of the settings in AngryGPS are too. That seems bad.
On both wi-fi & 3G, my One either times out while downloading from play store, or takes FOREVER when searching for on google, youtube etc. It seems like a data issue, as even the stock browser takes years to open a page. Anyone else have this issue?
I have this issue too except WiFi is fine, random slow data or drops data completely. Also my cell radio will completely drop at random times as well as the data drops and it only occurs on a GE ROM, stock 4.2.2 or 4.3.
On a sense ROM I don't get data/radio drops. I have an actual Playstore GE One and I took the 4.3 update, still the same problem. Its not my service in my area because my Nexus 4 is rock solid.
Anyone have any solutions?
Sent from my Nexus 4
May be like this
http://forum.xda-developers.com/showthread.php?t=2286616
or this
http://forum.xda-developers.com/showthread.php?t=2405521
Explained there ( for Samsung)
http://www.androidnz.net/2012/06/at-your-own-risk-how-to-disable-fast.html
Thanks for the suggestions, but I don't think it's Fast Dormancy. Why? Because the issue is present on both wi-fi and mobile data connection. It seems to stop receiving data for a period, than starts up again all of a sudden. I've seen a 40mb download take 20 mins on a wireless connection - on my Galaxy S ii it takes approximately 1-2 minutes.
What ROM are you using? Rooted, unlocked, updated radio? I am testing some build.prop additions from ARHD12.3. My problem seems to be gone over the last 24 hrs on GE 4.3 when previously I could only get good connection on sense based Roms. I added most all of the ro.ril.xxxx. lines into my build.prop. Might be worth a shot if your rooted and unlocked.
Sent from my HTC One
Copperhed said:
What ROM are you using? Rooted, unlocked, updated radio? I am testing some build.prop additions from ARHD12.3. My problem seems to be gone over the last 24 hrs on GE 4.3 when previously I could only get good connection on sense based Roms. I added most all of the ro.ril.xxxx. lines into my build.prop. Might be worth a shot if your rooted and unlocked.
Sent from my HTC One
Click to expand...
Click to collapse
Rooted stock ROM, 4.2.2. Haven't changed anything apart from rooting - is there a .zip I can flash from recovery to try out your fix? I'll restore form a nandroid in case things go wrong.
What firmware are you on? I need to get the build.prop from the stock ROM your running. The easiest way for you to test is to make a backup of your current ROM and then do a wipe full data wipe (not SD card wipe) and install ARHD 12.3 and see if that fixes your problem. ARHD is a stock 4.2.2 sense ROM with under the hood enhancements. Give it a try. If that doesn't work, the build.prop additions I made won't help either.
Sent from my HTC One using XDA Premium 4 mobile app
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?
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Magicnet2 said:
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Click to expand...
Click to collapse
First thing I would do is just factory reset it through recovery (power on while holding home) and see if all works after this. Super d is for sure one of my favorite donut ROMs and it shouldn't be having the issues you have.
If that does little or nothing than write down all info from bootloader (power on while holding camera) here and the version of recovery you have (written in recovery screen)
Sent from my Nexus 7 using Tapatalk 2
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Magicnet2 said:
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Click to expand...
Click to collapse
Yes it is strange, try finding a ROM called donut by Laszlo, search is down right now but it should be within the first five pages or so in developers thread. Put on sdcard along with this
http://www.androidfilehost.com/?fid=23212708291678371
First flash super wipe in recovery and then flash new ROM
If it all does not work still we will go from there
Sent from my Nexus 7 using Tapatalk 2
Right, so I've got some new info on this. I wanted to go reflash, but just for the sake of it, I re-wiped though recovery and nothing changed. then on the second time, the market suddeny started working through wifi, which it has not for the past few months, even after 3 or 4 wipes. So it started working, but the signal kept failing. It found the first application, downloaded, installed, then "network problem" so I reflashed using the files you mentioned. It worked beautifully on the first fly, for which I am grateful. This was my main concern - I had no idea, whether I needed to change the radio or bootloader or anything prior to trying to flash the rom. So the rom works nice, the market and facebook and teamviewer do connect now using wifi, but I keep loosing the signal. Better said - he stays connected to wifi, just that the applications keep throwing network errors and loose connection. So I presume, it will be either hardware related, or I was wondering, if a change of radio might help... Secondly, I keep getting one more problem I had with the old Rom and that is - when using ES File explorer, when I close by pushing the back button, it closes and then an error says it stopped working and needs force closing. Wondering how this kind of error can transfer between different Roms. Again - posibly hardware related? I don't know.
Anyway, the rom works nice, so I'll try it out and see if it's better than the previous one. One question though - when flashing to a different Rom, do all of them have specific requirements for radio and bootloader and recovery and so on, or is the setup I have ok for flashing anything, that is suited for the G1?
EDIT: One more thing I just remembered. The Superwipe, as I read the description, was supposed to wipe everything + the SD card as well. First of all I noticed that it took just about a second or two, which I thought was a bit too quick, but the SD card was not wiped at all, so I'm thinking, that theoretically there could be a file on there, that causes the problems, that have transfered from Rom to Rom, as it was not wiped at all. I'll reformat the SD card, superwipe it, reflash the Rom and see what will happen. Will post the results first thing tomorrow.
It only wipes ext partition not fat32
Only newer ROMs will require a different bootloader/radio, which also will give you more ram so it is preferred. See ezterrys post on the 2708+ update or read the through the thread below this on where I discussed the benefits of upgrading with another dream user
Sent from my Nexus 4 using XDA Premium 4 mobile app
Right, so from what I see from the other thread of yours, CM5 should be a good Rom to try. I will definitely wanna go there, cause while the current Rom seems a bit better than the Super D, it seems it uses up more memory - can't install as many apps as before and I'm keeping it pretty low on apps. And I definitely want to see, whether it will improve any of the lingering problems I've been having, or whether it'll be worse. So judging by what you told the other guy, I already have the right bootloader as I have the 2005 with fastboot enabled, but I'll have to update the radio. Here's what I'm not sure and that is, which to choose. Should I stay with the current SPL and get the same radio the other guy had (RADIO-2.22.19.26i) or should I go straight for the 13d SPL with radio-2.22.27.08? I would say, for now would be safer to stay with current SPL, update the radio and then flash Rom + Gapps and see what it does. Plus if I remember right, you said that to get the ramhack I need the 13d spl, which doesn't support fastboot...
You got it all, well you don't need to change radios, the one he has is a Europe version, yours is more us. Both work fine for cupcake, donut and eclair ROMs. You can try out the other if you were getting poor reception but not needed
Cm5 will work fine for you as of now, just full make a backup, wipe, superwipe, fastboot -w whatever, then flash ROM, then gapps then reboot
The ram hack is awesome but so is learning fastboot. I do recommend you at some point upgrade to the .13d SPL but I think its a good idea to flash a few things first and be comfortable before doing so. If you have issues having fastboot is helpful in fixing things
Sent from my Nexus 4 using XDA Premium 4 mobile app
Ok. So what I did is partition the SD card using the nice "Mini tool partition wizard" and went for a 250 MB ext4, made a backup, left the radio be so far, wiped, flashed the CM5 and Gapps and I have to say I'm impressed at how swift the Rom works. It appears to be generally faster than both the SuperD and Laszlo Donut Roms. I have been testing it only a short while yet, but the wifi, although it shows constantly weak signal (one or two lines), it hadn't lost connection yet, which gives me hope and the apps2ext seems to work perfectly right away. At least I'm able to move them around and it installs straight there, without any failure so far and the apps work so thumbs up.
This deserves a big thanks to you for the supplied info. Before I wrote this thread, I was about to try one of the long guides - which would take me through downgrading and everything - you saved me a lot of stress man I'll play around with this and will try going for the ram hack a bit later. I'll let you know any bugs I notice...
P.S.: You were right to suggest getting familiar with fastboot and adb - it's a great thing and it's good to know I've got it set up and running fine.