I've read a bunch of forms and I still don't know what is exactly wrong. I believe I did everything right by doing a complete wipe and dalvik; all of that. I then attempted to flash the Das Bamf 2.0.5 file and everything went smooth, then I did adb to get into the hboot and I flashed the new radio for the BAMF file which also looked fine when complete. Once I booted my phone the thunderbolt symbol came up and the BAMF title came up at the bottom then booted into the phone but this is where there's a problem. The HTC background stock skin appears and the notification bar (time, service bars) and that's it! I re-flashed several times but still the same result. Does anyone know why this is happening?
And why is it so important to delete the PG05IMG.zip file after you flash? I've read that people sometimes have to do it but I never have, could that be the problem?
You delete the radio file so if you have to boot into recovery they hboot it doesn't try to update the radio each time, as far a it not working, you flash the room they recovery, not room manager or hboot.
sent from my motorola V60 runnin' bamf gb sense 3 pr 4 for the TB
Your radio file might be bad, try downloading it again.
sent from my motorola V60 runnin' bamf gb sense 3 pr 4 for the TB
Check MD5sums. Reflash in recovery. No wipe.
^_^_^
I redownloaded the radio a few times and I went to youtube and got links from different videos which all pointed me to the same xda form that I found in the beginning.
how do I check the MD5sums?
I read a lot of threads and they say to always do a wipe when flashing the GB roms...
Related
I found the solution to the problem described below. It was ROM Manager that was sabotaging me, for whatever reason. I went into CWM manually, wiped everything obsessively 3 times like I've seen other people describe, installed 1.6, and it worked perfectly. Too early to say how it actually runs for me but I least I've got it fully installed!
PROBLEM:
I started from stock rooted S-off ROM and installed Das BAMF 1.5, wiping everything as recommended. Under Settings/About Phone/Software information, the baseband, kernel, build number etc were all correct. Things ran OK, although battery life was pretty bad. But there were a number of anomalies. The Verizon bloatware still seems to be present. The location reticule is still present in the notification area. Etc.
Today I installed 1.6 over 1.5, again wiping everything even though it is said not to be essential. I did the install through ROM Manager. Everything proceeded as expected, the boot animation screen shows BAMF 1.6, all the About Phone information is correct for 1.6. But again, the location reticule is still present; signal strength indicator is 4 bars instead of 6, Verizon bloatware still present.
I know the real action is in the development thread but I still need a few more posts before reaching that exalted status. Anybody else seen/solved an issue like this? Any help is appreciated and if some kind moderator feels led to move this to the other thread, all the better!
[EDIT] A couple other anomalies are the extended Power Options and Reboot menu options shown in the 3rd and 4th screenshots at the beginning of the Das BAMF 1.6.1 development thread-- I don't have those. On the other hand, I do have BAMF Toolbox, Call Recorder, and other expected apps included with the ROM.
Thanks very much.
I'm having the exact same results. Frustrating!
Are you installing with ROM Manager, or directly from CWM?
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Here's the thing I don't get. What's the fricking point of wiping 3 times?
If wiping == formatting a partition, then what good does it do to do it 3 times? None that I can imagine.
If wiping == deleting everything in a directory tree, then again, what point is it to wipe 3 times? What is accomplished on the second and third time that isn't on the first?
Just my opinion. I've never had a problem with wiping just once.
johnkc1975 said:
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Click to expand...
Click to collapse
I would try hbooting the unsigned stock RUU. Then try flashing the rom of your choice through Cwm not rom manager. This should start you back at scratch with s off along with clearing up any bugs you can't seem to get rid of.
I had the same problem. Don't use Rom Manager for this Rom. Do it manually and everything will be like it should.
Ditto to that. All my unfruitful efforts were due to initiating the process via ROM Manager. Doing it all via CWR did the trick.
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.
I am rooted and using BAMF 1.63, and want to do a clean move to 2.0 Beta 5 without errors.
I've been told that I don't need to do the entire AutoRoot w/MR1 program, but that I should instead just flash using the MR1 rom. The link below is where the files are located here on XDA, but see 3 files listed.
I assume that what I need is the last one, the custom ruu with MR1 included...BUT, will I also need to download the exploits file that contains busybox, wpthis, psneuter, su, readme.txt, misc.img, and hbooteng.nb0?
http://forum.xda-developers.com/showthread.php?t=996616&highlight=prerooted+RUU
You shouldn't need to do the whole root process again, when I switched from 1.6.3 to 2.0, all I needed was the new GB radio. I haven't had any issues with it & I didn't do any of the MR1 stuff
So, that process then would be to:
place radio file on the SD root and reboot so it will flash.
Remove the radio file, and then boot into Recovery and install 2.0 Beta5 ReMix using CWM
That's it? Sounds too easy. lol
have you read jcase's notice about the leaked gb radio, you might want to give it a read before taking the plunge,
I just came back to froyo, bamf remix 1.6.3 style
ibsk8 said:
have you read jcase's notice about the leaked gb radio, you might want to give it a read before taking the plunge,
I just came back to froyo, bamf remix 1.6.3 style
Click to expand...
Click to collapse
I'm new to all this and monitor androidcentral more, only coming here for info on released files. When I tried BAMF 2.0 Beta4 recently I didn't do the radio file, and the phone was dead with no signal. I'd like to avoid that so flashing with a radio file is necessary. What or where is the concern with the leaked radio file? Instead of what not to do, are you able to offer a link to a good radio file compatible with the new BAMF Beta5? Thanks!
EisBlade said:
I'm new to all this and monitor androidcentral more, only coming here for info on released files. When I tried BAMF 2.0 Beta4 recently I didn't do the radio file, and the phone was dead with no signal. I'd like to avoid that so flashing with a radio file is necessary. What or where is the concern with the leaked radio file? Instead of what not to do, are you able to offer a link to a good radio file compatible with the new BAMF Beta5? Thanks!
Click to expand...
Click to collapse
A few people are getting bricked TBs from the GB radio they are thinking. Enough people are having this happen that the ROM devs are advising everybody that has gone to a GB ROM, to go back to a Froyo ROM until we get an updated GB radio.
leoingle said:
A few people are getting bricked TBs from the GB radio they are thinking. Enough people are having this happen that the ROM devs are advising everybody that has gone to a GB ROM, to go back to a Froyo ROM until we get an updated GB radio.
Click to expand...
Click to collapse
Well, I didn't get bricked, but I was without connection/service to anything after doing the latest radio file followed by BAMF 2.0 b5, until I restored to my last working backup. Not fun. I downloaded TeslaCoil to give it a try, but my TB has turned off on its own 3 times now in 3 days.
EisBlade said:
Well, I didn't get bricked, but I was without connection/service to anything after doing the latest radio file followed by BAMF 2.0 b5, until I restored to my last working backup. Not fun. I downloaded TeslaCoil to give it a try, but my TB has turned off on its own 3 times now in 3 days.
Click to expand...
Click to collapse
You didn't brick because you weren't running the GB radio. In order to run any GB ROM with signal and whatnot, you need the leaked ALPHA GB radio, which is supposedly causing some phones to brick. And just because you run the GB radio fine for a few days doesn't mean you are in the clear. This has been happening to people a couple days after running it.
still not sure why the whole brick thing vanished as fast as it came, nobody bother to ask the simple question "was your phone having alot of reboots befor,root no root stock ruu or custom rom". my original tbolt was rootet cause it would reboot all the time as stock, was running bamf 1.63,never had gb on it,well it started doing it again,so when the ota came out i put the phone back to stock s-on did the ota and 2 days later it had the reboot contious could not do anything, that tells me it was hardware and it was replaced no probs,htc and verizon have been aware of the problem
Sent from my ADR6400L using XDA Premium App
Just flashed the GB radio, wiped the heck out of the data in CWM and then I installed the Das BAMF 2.0-5 ROM. After about ten minutes it takes me to the HTC Setup Wizard. I go through it, login with my Gmail account and at the very end the Setup Wizard FC's.
All I get after that is a black screen, I can pull down the Notification bar, I see the 4G indicator and battery and signal strength but I can't do anything. I wait about ten minutes and nothing. If I hit the lock screen button it gives me the Sense 3.0 lockscreen but it takes me back to that black screen after unlocking it. I try pulling the battery and then it gets stuck on this Thunderbolt logo and I can't get past it.
Any ideas?
Re-download the rom file, may have been corrupted, and re-wipe everything (data/cache/davlik) and flash the rom again.
Well now I got into the ROM but have no connectivity...ugh...I have the correct GB radio and I made sure I wiped everything before hand, any ideas why this would happen?
g00s3y said:
Re-download the rom file, may have been corrupted, and re-wipe everything (data/cache/davlik) and flash the rom again.
Click to expand...
Click to collapse
That's exactly what I did, it just randomly rebooted and now I have connectivity again, lol. I think I should be fine now, thanks!
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.