Database Develop

All calls end after 36 secs-Anyone else?

Looked at the sticky, but did not see this issue. It was happening on my cyan builds once I went to donut. I swapped, updated all, wipe, install per instructions, but the prob found me again. This time I am not the official 1.6(DRC83, 2.22.19.26I) Anyone else have this happen to them?
Fixes?

Okay, so the time ranges between 30 seconds and a minute.
From what I am seeing, I may have to revert back to stock settings and give it a go. If that works, then I will attempt to ROOT again.
I only began having this issue after I upgraded to 1.6 via cyanogen.
I swapped ROMs hoping to solve the issue ( thought it may have been b/c of the experimental/beta version)
But after being on this build for one day, I am already experiencing the issue again. I even went as far as repartitioning and wiping before I started so it would be a clean slate.

ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?

derfolo said:
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
Click to expand...
Click to collapse
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.

ljnick19 said:
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
Click to expand...
Click to collapse
The HTC recovery may have messed your radio up. Try reflashing the radio.

Thanks for the input! I was worried no would have any ideas. I'll give that a shot. Now when reflashing the radio, do I need to do the whole-radio, spl, rom, wipe thing? Or just radio?

I am also using Ra v1.2.2 recovery, could that be causing issues w/ 1.6, Donut ROMs?

One more issue to add: AdvancedLauncher (processandroid.process.acore) has stopped unexpectedly. FC almost every time i press the home button. Made the mistake of making advanced launcher my default home button action...

For the launcher make sure you have the latest version. Then reinstall or run fix permissions. U only have to flash the radio, and the recovery should only affect flashing the roms

Thanks a mill for the help, I really thought this was going to fall flat. I'll attempt later this afternoon and post results.

For those of you that took a moment to not only read, but to assist, THANK YOU!
Results are:
I went from OTA 1.6 to Cyan 4.1.999
I wiped and repartitioned the sd as well as redoing the radio
So far, I have not experienced any FC's. Unfortunately, I have not made a lot of calls either. Crazy thing was that on the OTA build today, calls seemed to be functioning, but the FC's were excessive.
I also ran fix permissions as well as cleared the dalvik cache.
Again, thanks for the support. I hope to pass it on if I am ever able to help, it is appreciated!
LJ

phone reboots when recording video.

Am having some problem with my nexus one ive notice since i wipe my phone and install froyo, i tried going back to my cyano 5.0.6 but my camera isnt working whenever i switch to recorde a video the phones automatically reboots,but when i flash the froyo rom the camera is working perfectly there but when i try going back to my cyanogen its not working, anybody know what the problem is, also today i flashed cy 5.0.7 and am having the same problem.

Infon1 said:
Am having some problem with my nexus one ive notice since i wipe my phone and install froyo, i tried going back to my cyano 5.0.6 but my camera isnt working whenever i switch to recorde a video the phones automatically reboots,but when i flash the froyo rom the camera is working perfectly there but when i try going back to my cyanogen its not working, anybody know what the problem is, also today i flashed cy 5.0.7 and am having the same problem.
Click to expand...
Click to collapse
did you flash the right radio back?

No I didn't flash back the radio, I just wipe then flash back my old cyanogen 5.0.6, if that's the case and for find the radio in this forum?

Infon1 said:
No I didn't flash back the radio, I just wipe then flash back my old cyanogen 5.0.6, if that's the case and for find the radio in this forum?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=654869

4.06 radio and AT&T/Rogers phone incompatibility?

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

Phone can call out, but can not call in

When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.

muziling said:
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
Click to expand...
Click to collapse
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?

kifno said:
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
Click to expand...
Click to collapse
radio: 2.42.02.10.29.zip
PRL: 2.20_003
ROM: aospCMod-HC-20110421-signed.zip
no tweaks
carrier: china telecom

try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions

kifno said:
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
Click to expand...
Click to collapse
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.

muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
Hmp, stick with a rom that works THAT YOU LIKE, not by what I tell you. But did you try these rom's?
- CM v7.0.2?
- GingerSense?
- AOSP 0.9.9.2 Froyo?
- CM6.1-RC2?
- NFX Stock Rom?
- My Sense Roms?
Try all of those and for whichever the phone calls work, take note of that. And then also I'd like for you choose what you like the best. Also did you try the update prl/pri on a sense rom? Try doing it on the rom you're on now
And glad to see it worked for ya bud

muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.

il Duce said:
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
Click to expand...
Click to collapse
Yes oldghost uses a Chinese carrier and I don't think he had any issues at all. But first try updating the prl/pri

Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.

hareofthedog said:
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
Click to expand...
Click to collapse
Try troubleshooting the problem by doing the following things one at a time to see if they work:
- Try a different radio that works for the SPRINT HERO CDMA ONLY (else you will brick your phone, if you need help finding radios let me know)
- Try without firerat's
- Try wiping everything using the latest official clockwork mod 3.0 after backing up everything
- Try s0be's kernel
- Try the official CM7 v7.0.2
i can come up with more options for you to try one by one but that should last you for about an hour or so
after doing all those let me know what happens

Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.

hareofthedog said:
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
Click to expand...
Click to collapse
Glad to see its working now. If you need any more help feel free to PM me or post again in the q n a forum and the community and myself will gladly answer your question asap.

same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in

muziling said:
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
Click to expand...
Click to collapse
if a rom isn't broke, don't fix it...stick with gingerbread, its fresh out the oven
but seriously if cm7 works, then use it. unless if you really don't like cm7....but i doubt that..i hope

[Q] Need some help changing ROM on G1

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.