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
Related
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
I just rooted my Nexus yesterday to Cyans mod. I ve rooted before (tons of ROMS on my G1) so Im not a complete noobie. The ROM runs absolutely perfect and smooth EXCEPT for when I try to record video. Every time, and I do mean every time I try to record a video, the phone freezes for like 3 secs, and then reboots.
Camera shoots photos fine, and this is the only problem I have, but it is becoming a problem, considering I just bought the phone I searched the forms for this problem, and used multiple search strings and found no results.
Has anyone ran into this problem, and if so have you found a fix for it?
**MODS..I deeply apologize if this is in the wrong section.I worked a 10 hour shift and am half asleep while writing this. Please feel free to move if you see fit**
**EDIT..ok..NOT COOL...I just tried to watch a video, and that also no longer works. Anyone know of a fix for this?
Same issue here. Meh...
Ended up switching to Froyo. Hope Cyanogen keeps up.
drpfenderson said:
Same issue here. Meh...
Ended up switching to Froyo. Hope Cyanogen keeps up.
Click to expand...
Click to collapse
If you've flashed the 'Froyo' radio then you'll have to downgrade it before video will work, or move (back) to Froyo.
If you haven't changed radio then I have no idea!
same here. the test video i took when i got the (ph)one was amazing quality so i'm looking forward to this working again!
If you guys were EVER on Froyo. It updated your radio. If you then went back to CM builds, you will need to downgrade your radio to the eclair radios in order for the camcorder to work properly.
The phone hasnt been on Froyo (that I know of), so thats not causing my problem. I tried to flash the prerelease before I was rooted, but it was US only and didnt work. I didnt however update my radio when I flashed to Cyan, but I was told this wasnt causing the problem. At this point, anything to get my cam and videos working again!
Would be awesome if Cyan, the man himself, could hook us up with a fix or some advice on this one!
Dai323 said:
The phone hasnt been on Froyo (that I know of), so thats not causing my problem. I tried to flash the prerelease before I was rooted, but it was US only and didnt work. I didnt however update my radio when I flashed to Cyan, but I was told this wasnt causing the problem. At this point, anything to get my cam and videos working again!
Would be awesome if Cyan, the man himself, could hook us up with a fix or some advice on this one!
Click to expand...
Click to collapse
if you attempted to flash the froyo stock update, it included the new radio. its very possible that it successfully flashed your radio, but failed to install the froyo ROM. you can easily check if you have the new radio by going into your settings and checking the baseband version. i bet you are on the new froyo radio, which is known to break video with all 2.1 ROM's. and vice versa, the old radio breaks camcorder on 2.2 ROMs.
so each time you jump between a 2.1 and 2.2 ROM, you have to flash the associated radio as well.
GOOD POINT BRO. I will check this now...
**EDIT** that was it..I must have went to Froyo radio unknowingly. I flashed the stock Nexus radio, and vids and video recording are now working just fine.
Hope this thread helps the others. I foolishly searched "cant record videos" and found nothing, when I should have searched "cant play videos", as there are many threads on that one.
Again, thanks for your help!! Didnt expect a solution so quickly!!
It also seemed to give me 3g problems when I just flashed back, but I ll deal with that one tomorrow after work
Same issue
I have a n1 with 5.0.7.1 and my phone also reboots upon trying to launch the camcorder feature. I'm going to try out the new 5.0.8 test3 with 720p hack add-on and see how that goes.
htctouch1313 said:
I have a n1 with 5.0.7.1 and my phone also reboots upon trying to launch the camcorder feature. I'm going to try out the new 5.0.8 test3 with 720p hack add-on and see how that goes.
Click to expand...
Click to collapse
Any luck? I recently upgraded to CyanogenMod 5.0.8 and immediately after updating I noticed the change. I can watch videos in Gallery just fine, but trying to record (or open Settings) in the camcorder mode causes the phone to hang and then reboot.
I never once tried to get anywhere near Froyo. I'm still waiting for CM6. Any advice on how to restore video functionality? Should I downgrade to the previous version of CyanogenMod? Is that even possible?
As I said, I highly doubt this is a Froyo issue, but it's clearly related to upgrading to CM 5.0.8.
ronocdh said:
Any luck? I recently upgraded to CyanogenMod 5.0.8 and immediately after updating I noticed the change. I can watch videos in Gallery just fine, but trying to record (or open Settings) in the camcorder mode causes the phone to hang and then reboot.
I never once tried to get anywhere near Froyo. I'm still waiting for CM6. Any advice on how to restore video functionality? Should I downgrade to the previous version of CyanogenMod? Is that even possible?
As I said, I highly doubt this is a Froyo issue, but it's clearly related to upgrading to CM 5.0.8.
Click to expand...
Click to collapse
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
prettyboy85712 said:
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
Click to expand...
Click to collapse
I am not aware of ever having modified any "radio" functionality on my Nexus One. I bought the phone retail at the beginning of May, so it had stock 2.1. About a week later I flashed via USB to whatever version of CyanogenMod was current then. (I'm sorry and embarrassed I can't be more specific.) Everything worked flawlessly.
Then about three days ago, I downloaded the CyanogenMod Updater app from the Marketplace and used that to move to CM 5.0.8. I also performed a backup with Titanium, from which I restored after updating to CM 5.0.8. Since this was done, I my phone freezes and reboots whenever I try to record video. I mentioned the Titanium backup because perhaps the Restore System Data feature resulted in broken settings. But I do recall seeing "720p video" in the changelog to CM 5.0.8, so I'm guessing that's probably the culprit.
I don't understand how the radio would be affecting my camera, but I'm willing to try anything. If we assume that somehow the CM update did change my radio settings, how would I go about correcting that? Should I just wait for CM6, or is this radio problem likely to persist if I don't address it specifically? Is regressing to an earlier version of CM an option?
prettyboy85712 said:
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
Click to expand...
Click to collapse
D'oh. This was clearly it. Because I got CM 5.0.8 via the CyanogenMod Updater app, I did not see that I was supposed to update the radio to Froyo independently of installing CM.
I tracked down the radio image (the Full Update Guide has all the info, for any interested persons) and flashed with that, and sure enough, I know have smooth 720p video recording.
Thank you so much for bluntly and persistently calling my attention to the radio image issue. I'm going to go back to playing with my favorite toy now. =)
I'm posting here because I don't know what else to do, my phone freezes using any froyo rom. It happens randomly and sometimes will not happen until I reboot the phone, but it makes my phone pretty much unusable. I've tried the leaked froyo rom, BB, CM 6 1&2 and countless others. I've tried wiping data / cache and formating the SD card (worked until i put my music back on), and I'm about to just try stock 2.2 and exchange it for a new one if it wont work.
Anyone else have this problem that could help me?
One thing I didn't see you do...
Have you at all root your phone to install the desired froyo rom for your phone?
Yes I am rooted, I'm currently on CM 5.0.8 and very happy but I would really like to get froyo working.
Alright. This is what I've done to get Froyo working on my Droid: I rooted my phone, downloaded BB v4 and changed the name of the file to update, installed Rom Manager on my phone(then found out I can download the roms from here as well), reboot into recovery through rom manager, wiped data & cache, selected install zip, then selected reboot phone. It took a bit to register but it converted over with BB v4.
I think I've found my problem
droidforums.net/forum/tech-issues-bug-reports-suggestions/67526-music-sd-card-causes-bb-4-freeze.html
this sounds like my exact problem, I'm going to look through my library and see if there is a corrupt file then try again
Hopefully that is the source of the issue and that'll be solved quickly. Good luck to ya
So i've been running the stable version of cm9, 9.1.0 i believe, i flashed my captivate with this version around the time it came out. I never had any issues with it before except the occasional data not working but i didn't mind that. So now randomly i came back from the gym and i got notifications saying a few things stopped working. If I remember correctly, it was Gapps, something .core (either google.core or something or android.core.something) and Talk stopped working. Basically it did not allow me to access any apps as they also kept closing before i could finish a task. So i chose to restart the phone and now it is just stuck at the cm9 boot screen with the background glowing blue and the guy has his eyebrows down and what not. i tried taking out the battery and everything! I do have a nandroid back up though
Desiloader said:
So i've been running the stable version of cm9, 9.1.0 i believe, i flashed my captivate with this version around the time it came out. I never had any issues with it before except the occasional data not working but i didn't mind that. So now randomly i came back from the gym and i got notifications saying a few things stopped working. If I remember correctly, it was Gapps, something .core (either google.core or something or android.core.something) and Talk stopped working. Basically it did not allow me to access any apps as they also kept closing before i could finish a task. So i chose to restart the phone and now it is just stuck at the cm9 boot screen with the background glowing blue and the guy has his eyebrows down and what not. i tried taking out the battery and everything! I do have a nandroid back up though
Click to expand...
Click to collapse
I'd use heimdall one-click KB2, then Heimdall one-click Speedmod, then flash again with bootloaders. Finally, reflash CM9.
This will establish a sane base, then flash a kernel that handles all flashing operations and finally flash the bootloaders required to run newer versions of Android.
Sounds like your /datadata is getting full. I recommend you try the datafix app. But since you are stuck, you will need to wipe data in order to get back in.
Sent from my SGH-I777 using xda premium
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.