I came from Das BAMF Remix 1.6.3; performed factory wipe/data reset, wipe dalvik and wiped cache. I flashed the GB Radio via Hboot (update=yes; then updates by doing 2 things, then hit power to restart). I then flashed the ROM.
The first two (2) times I flashed 2.0-4.0 and could NOT get Wi-Fi to work, but I had 3G working no probs as well as GPS. Went out for a couple hours and had no issues. Got Back, and I still could not get Wi-Fi to connect. I reflashed radio..no dice...re-downloaded the ROM, did a complete wipe and reflashed both the ROM and radio. Still would not connect, even after I downloaded Test7 kernel (kernel shouldn't mess with my mobile connection?).
I then went and downloaded 2.0-4.01, and now I can connect to Wi-Fi. Now the problem is that I am stuck on 1x Mobile Data and cannot get 3G. I've re-wiped, reflashed and downloaded Imeseyons new kernel..still stuck on 1x. I have even tried toggling Airplane mode, but cannot get it to 3G connection.
Any ideas?
Dunno if it will make any difference but flash the rom 1st then either battery pull or adb into hboot to flash the radio. Maybe others can confirm if this might help or not.
Not sure if this is the root of your problem, but the directions given by the developers of these gingerbread roms indicate that you should put the rom and radios on the root of sd card, flash the rom first in recovery, don't reboot, get into hboot via adb, then let the radios flash, and reboot. It sounds like you flashed the radios first, and then the rom. Maybe this is causing your problems?
lanceman5000 said:
Not sure if this is the root of your problem, but the directions given by the developers of these gingerbread roms indicate that you should put the rom and radios on the root of sd card, flash the rom first in recovery, don't reboot, get into hboot via adb, then let the radios flash, and reboot. It sounds like you flashed the radios first, and then the rom. Maybe this is causing your problems?
Click to expand...
Click to collapse
Don't think so, cause I have tried both ways. Also, in Ad's posts he recommended both ways.
Either way, if I botched it the first time, it doesn't make sense that with the same radio I was getting 3g but no Wi-Fi, but now I'm getting Wi-Fi and no 3g.
I reflashed back to Remix 1.6.3 and have 3g+Wi-Fi right away.
And 3g returns..On 1.6.3.
Sent from my ADR6400L using XDA App
Someone will correct me if im wrong, however it could ne a kernal issue, had the same problem, flashed imo's 2.4 test 7 kernal, and now i get get service on bamf 2.4, just a thought
Sent from my ADR6400L using XDA Premium App
Thunder Droid said:
Someone will correct me if im wrong, however it could ne a kernal issue, had the same problem, flashed imo's 2.4 test 7 kernal, and now i get get service on bamf 2.4, just a thought
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
When I wiped and reverted back to 1.6.3 I lost a Superuser file. I decided to re-root and start from scratch.
Re-rooted, then flashed 2.0-4.1 and let it startup. Then shutdown and went into Hboot and flashed GB ROM. Went through a normal startup and I had 1x which after a couple of minutes turned into 3G, but very laggy. I then flashed Imo's 2.5.4 kernel and re-started. 3G came up and speeds were just fine.
A lot of work to get BAMF to work, but I'm happy. Now working on adding Launcher Pro, Fancy Widget and a few other personalizations.
ever since I've gone from the original GB leak to Froyo and now back to the MR2 leak and GB I've been having issues with ROM's.
it first started when I went back to froyo, after a few days of being on das bamf 1.7, my phone would go on an endless bootloop and I couldn't get back into it. so I tried reflashing the radio, the rom, fixing permissions, but nothing would help. I wasn't OC'd or anything with das bamf. so I wiped the data and flashed the rom again and I was back up and running on das bamf. About 5 days later, the same thing happened, endless bootloop and I couldn't get back into my phone. Luckily the MR2 leak came out and so I flashed to that along with gingeritis test IX. everything worked well, then I flashed to gingeritis 1.0 when it first came out on Monday.
Today, as I was on the phone with someone, my phone suddenly rebooted and got stuck in an endless bootloop. I cleared cache and did a fix permissions and luckily I was able to boot back up. That is, until I called VZW to report that 4G is out in my area (it wasn't my phone since I had 4G at the office 10 mi away, but not at home and I know of a few other people in my area that didn't have 4g either). I rebooted and now I'm stuck in a bootloop, but this time clearing the cache and fixing permissions didn't work.
I ended up having to re-flash the ROM to get back up and running... I guess my question is, am I doing something wrong, or is something wrong with the phone? I hadn't had any reboot issues at all until I switched back from the leaked GB radio and rom.
This happened to me in froyo when I came back from GB. What I did was flash the second radio on this thread and the problem went away. If you want to stay with bamf remix 1.7.
I hope this helps.
It's a leaked alpha version of a test rom basically, there are going to be bugs.
Brace for EPIC Tale!
So I upgraded, like everyone else, to the MR2, and BAMF GingerRemix 2.1.
Flashed the new Radio (MR2)
Full wipe cache clears all that jazz.
Installed 2.1 worked great, however about a week into it I started getting data drops, and unable to connect to Wifi.
So I tried MR2.5 leak, this seemed ot help for a while but eventually no wifi again.
I didnt think much of this at the time, I wanted to upgrade to a sense 3.0 rom anyway. BAMF was in RC2 and had reported a bunch of bugs so I decided to try GingerTheory 4.2 with the MR2.
Flashed radio, full wipe, cache clear delv everything then flashed ROM.
From the beginning wifi would not connect and data was spotty.
Upgraded to GT4.3 same issues.
Yeserday morning I tried BAMF 3.0 RC3
Full wipe and the whole nine yards. And was already on MR2.0
Again would not connect to wifi, sat on obtaining IP then dropped to disconnecting, tried the wifi security button connect at home and still nothing.
In IRC I was told it was the kernal, so I got Dream 2.3 flashed it and rebooted.
After boot animations I got "process system is not responding" with [force close] and [wait] buttons but touch would not work.
So Drew66 ran me through the steps again checking everything from MD5s on all items to ADB device checks and everything checked out.
We re flashed the kernal and cleared delv.
Into HBOOT and reflashed the MR2
Rebooted and waited a few mins.
All worked fine.
However, again no WiFi. Then playing with settings I lost Data all together.
This morning I rebooted in hopes of getting Data back
Instead I was greeted with, "process system is not responding" again.
I'm thinking of just a full restore but if anyone has any ideas they are most welcome.
Thank you.
I've recently attempted to flash CM7 1.7 with an MR2 radio but it wouldnt boot past the splash screen. So I reverted back to the original stock radio/rom then attempted to reflash my previous working version of CM7 RC .6. However now I have no data connection. I have celluar reception and its magnificent but absolutely no data. Things I have tried:
*Making sure the battery cover is shut (it is as tight as it gets)
*Reflashing the radio and rom (I've actually tried about 4 different roms/radios)
*Reverting back to stock (this actually does get connection but I hate the rom)
Where I am right now as far as radio/rom:
I have flashed to the MR2 radio and CM7 1.6.1 (it works but still no data)
Any ideas?
Hey so I installed eclipse 1.2 via bootmenu and applied the patch, everything is looking good... except im stuck on a mystery gsm network and cannot seems to get the phone to jump over to lte or cdma, I have a cdma phone.
any ideas?
what patch?
Well it was Razr-EclipseICS-v1.2RC1 and your patch from the same forums, I just re-flashed the ROM again after doing a full wipe and wiping the dalvik cache also again.. and now my 4g is working.. seems to be dropping connection to Google but that could just be begining issues.