• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Das BAMF 2.0 Gingerbread Beta!!

AllyWonders said:
Huge problem... I occasionally get FC on the phone signal... and sometimes i dont even get text messages but there is 3G... i only have 3G where i live and I did change the settings to CDMA auto (prl). even when the settings were on CDMA + LTE/evDo auto i got some FC ...
the way that i flash the radios was i loaded up the GB ROM then flash the the radios with Boot loader with in the phone, not by adb anyone think thats the problem?
Click to expand...

i dont think the way you flashed the radio was a prollem. youd did check the md5 of the radio before you flashed it,correct? :eek: if it didnt match,youre prolly lucky its working at all,and you should download it again and relfash it.

i had some issues on the stock rom/kernel with 3g disappearing on occasion. on bamf i got the same or simiilar FC a couple times,but it didnt make my phone not work. i think both times,i was actually talking on it. it also made all my mms turn into phone numbers instead of the contact id name. i didnt miss any texts that i know of.

reboot fixed the contact name to phone number thing. no 4g here yet,either,so ive also been running mine in cdma auto.
 
ThrillKill said:
so let me get this straight. I first flash the GB 2.04 BAMF ROM using ROM manager after downloading the file to my SD card. Then I need to download the GB radio to my SD card to replace the current PBIMG file, and it will automatically be flashed as it searched for the IMG file? Why is it that with all other ROMS I have never had to flash the radio separately? Is there a package deal?
Click to expand...

please dont do this using rom manager.

do it in recovery. if you want to do it the way its reccomended in the original RUU post,read thru this thread:
http://androidforums.com/thunderbolt-all-things-root/336846-leaked-gingerbread-ruu.html there are some more pointers on using ADB

in a nutshell:
-download rom and radio. move both to SD card. rename radio to PG05IMG.
-check md5 sums on phone using astro file manager or scary aliens "android file verifier". if they dont match,STOP. delete files,redownload,try again. flashing a bad or incomplete file in hboot can brick your phone.
-use rom manager or quickboot to boot directly into clockworkmod recovery.(alternatively,use adb to boot directly to recovery)
-make a backup
-wipe data/cache/dalvik
-flash rom
-plug the phone into PC,use adb to reboot into bootloader. if you dont have adb,pull the battery,then power on while holding vol -. this will also take you to hboot(original instructions were to use adb,so pull your battery to get to hboot at your own risk)
-hboot will find your file(assuming FAT32 sd card,and correctly named file),unpack it,check it,and ask you to update. tell it yes.
-reboot
-immediately delete PG05IMG from your sd card

alternatively,you could do the first 2 steps,then:
-power off
-power on to hboot(power and vol -)
-yes to update
-when finished,no to reboot
-select recovery using vol keys and power button
-make backup
-wipe data/cache/dalvik
-flash rom
-reboot
-delete PG05IMG

*just be aware that the origianl instructions were to flash the rom,then the radio. i do not think flashing the radio first will matter,but im not an expert,so do so at your own risk.

*if these instructions are still too complex,you might want to hold off on this for awhile.
 
scotty85 said:
please dont do this using rom manager.

do it in recovery. if you want to do it the way its reccomended in the original RUU post,read thru this thread:
http://androidforums.com/thunderbolt-all-things-root/336846-leaked-gingerbread-ruu.html there are some more pointers on using ADB

in a nutshell:
-download rom and radio. move both to SD card. rename radio to PG05IMG.
-check md5 sums on phone using astro file manager or scary aliens "android file verifier". if they dont match,STOP. delete files,redownload,try again. flashing a bad or incomplete file in hboot can brick your phone.
-use rom manager or quickboot to boot directly into clockworkmod recovery.(alternatively,use adb to boot directly to recovery)
-make a backup
-wipe data/cache/dalvik
-flash rom
-plug the phone into PC,use adb to reboot into bootloader. if you dont have adb,pull the battery,then power on while holding vol -. this will also take you to hboot(original instructions were to use adb,so pull your battery to get to hboot at your own risk)
-hboot will find your file(assuming FAT32 sd card,and correctly named file),unpack it,check it,and ask you to update. tell it yes.
-reboot
-immediately delete PG05IMG from your sd card

if these instructions are still too complex,you might want to hold off on this for awhile.

alternatively,you could do the first 2 steps,then:
-power off
-power on to hboot(power and vol -)
-yes to update
-when finished,no to reboot
-select recovery using vol keys and power button
-make backup
-wipe data/cache/dalvik
-flash rom
-reboot
-delete PG05IMG

*just be aware that the origianl instructions were to flash the rom,then the radio. i do not think flashing the radio first will matter,but im not an expert,so do so at your own risk.
Click to expand...


I guess it may be a bit complex for me. I am currently running DS BAMF 2.6.32.21. I did not need to separately add a radio and this ROM works amazingly well on my phone. I red somewhere that I may already have the necesary radio built in to DAS BAMF..is that correct?
 
ThrillKill said:
Then I need to download the GB radio to my SD card to replace the current PBIMG file, and it will automatically be flashed as it searched for the IMG file?
Click to expand...

after i read this again,this last part bothered me. you should always delete IMG files right away after flashing. leaving it there will cause the phone to find and check it every time you enter hboot,wich could be bad if your in a bootloop or some other situation without a bootable rom.


ThrillKill said:
Why is it that with all other ROMS I have never had to flash the radio separately? Is there a package deal?
Click to expand...

there is not a package deal at this point. jcase has packaged up a couple hboot flashable rooted RUUs,and even 1 that does change the radio(mr1). why he did not do this for this rom,i cant say,im not him. but im sure he had good reason :) you actually should be glad that all you have to do is flash the radio thru hboot. flashing whole RUUs in hboot is time consuming,and IMO, a lil scary :eek: the radio by itself flashes fairly quickly,and minimizes the "biting your nails waiting for it to finish" time. ;)

other roms that you have flashed in recovery have not had a seperate radio flash simply because you didnt need a new radio for them to work... they utilized the radio that you allready had.

the leaked GB rom,however,needs the new radio to work. trust me,flashing them seperately really is the safest,and least scary way to do it.
 
ThrillKill said:
I guess it may be a bit complex for me. I am currently running DS BAMF 2.6.32.21. I did not need to separately add a radio and this ROM works amazingly well on my phone. I red somewhere that I may already have the necesary radio built in to DAS BAMF..is that correct?
Click to expand...

actually,the radio is flashed at a level higher than the rom. the rom flashed in recovery does not modify the radio.

when the 1.13.607.7 firmware(mr1 ota) was leaked,there was a radio along with it. if you flashed a rooted version of this thru hboot,then you did in fact flash the new radio then.

if all you have done is flash das bamf,and never flashed a radio or RUU in hboot,then youre still operating with the stock radios. if it aint broke,dont fix it :)

also,nothing wrong with feeling its alittle over your head at the moment. you will learn :) im guessing at this point youve only used rom manager to make backups and flash roms? if so then,id highly reccomend that you become comfortable with the menus,and manually doing things in recovery.

i know that some folks have never had a prollem with rom manager,and thats great,but a bad flash or bad file can easily leave you in a situation where youre in a bootloop,or in an nonfunctioning rom,and rom manager will not be available to you. in that situation,youll be in a moment of panic,not knowing how to recover your phone. at that point the only way to fix it will be to enter recovery and manually reflash a rom,or restore a backup,so becoming familiar with it prior to having prollems,while your phone is still fine and functional,will put you ahead of the game :)

my 2 cents,for what they are worth :)
 
Guys with the slower LTE speeds, try the newest test Imoseyon released. The one I have listed in my signature. With the .3 test 7 I was getting around 10 down and since flashing the latest .4 test 4 I'm back to normal speeds like I had with Froyo.

On a side note, I was trying to hold back flashing GB until it was more stable, but besides 2 reboots after the very first flash, no problems and so glad I made the switch. Hoping I'll be switching to Remix though sometime today. Know its on its way, just waiting for zhp_pilot to finish theming it. He did say it will be worth the wait though and if you guys have seen his froyo work on Remix, you gotta believe him.:cool:
 
gregnice37 said:
Guys with the slower LTE speeds, try the newest test Imoseyon released. The one I have listed in my signature. With the .3 test 7 I was getting around 10 down and since flashing the latest .4 test 4 I'm back to normal speeds like I had with Froyo.
Click to expand...

Also, the modded adrynalyne 2.5.3 kernel has normal LTE speeds. Last night I was reading that the newest kernel (2.5.4) has some issues so I haven't flashed it yet. While I'm loving the stability of gingerbread, I miss the great battery life that froyo provided. With my previous setup and ROM/kernel I was able to go 40-48 hours up time regularly. On gingerbread I have to plug in every night before I go to sleep because I'm usually around 35-40%. I should mention I turn LTE off when I'm not using it. All in all not terrible considering we don't have a source code released yet
 
WormDoes said:
While I'm loving the stability of gingerbread, I miss the great battery life that froyo provided.
Click to expand...
i agree there... i think the issue is the radio. ive tried the leaked ruu,bamf,and now im on gingervitis,and all have similar battery life.

i cant get thru a day of normal useage without pluigging in during one of my longer runs. it sucks,but it doesnt suck quite badly enuff for me to want to go back to froyo :p

i keep 4g off as well,since we dont have it here yet.

hopefully well get another leak soon that will offer some radio stability :(
 
Just to clarify a bit, the only way to flash a radio is through hboot. Whether that flash (the filename must always be PG0IMG.zip) is a rom containing a radio or simply a radio matters not. Knowing that this GB rom is an alpha leak, it's probably best not to flash if you don't *really* know what you are doing. Pulling a battery is usually not a great idea in the middle of a flash unless you are experienced.
If you are knowledgeable then use adb to reboot bootloader after flashing the rom in CWR. Even if the PG0img.zip file is on the sdcard root you can boot to cwr and bypass the bootloader flash, mount the card and then delete the file if you wish.
 
Agreed. But the battery pull they are talking about is while the phone is rebooting AFTER, flashing the Rom. So its not as dangerous as it might sound.
 
also,while its not possible to install a radio in recovery on the TB right now,it may be sometime in the future,as our technology advances ;)

it was possible to install radios via recovery on the eris.

remember,we did have to flash kernels in hboot or fastboot at first,and now those are recovery flashable.

battery pull in hboot while flashing=very,very bad(likely brick)

pulling battery in recovery after rom flash=not so bad,prolly harmless(tho im not reccomending it,as who knows?do it at your own risk)
 
Yes Scotty and JReed, you are correct. However, you two know what you are doing. The only reason to do a batt pull to get to hboot is if you are not near a computer and you desperately want to flash this. I saw this at the very beginning when it first came out but not lately. You really should be able to connect via adb just in case something very weird happens. The only real help you'll be able to get at that point is through adb shell from what I'm seeing.

Nonetheless, this rom is rocking. I'm getting very good batt life even on 4G whereas before my LTE would kill this phone. I'm even OCing now a bit just to push the envelope. Can't wait for Remix today.
 
i agree with you 100% bj. when i flashed the radio,i personally used adb,not the battery pull.

hmmm, gingervitus is runnin pretty good,but 2.0 remix will persuade me back over :D
 
Well, looks like I completely jinxed myself regarding battery life. I haven't touched my phone since I got to work at 8:00am and it had 90% charge when I got here. I have LTE turned off and my desk is right next to the office's WiFi router so I'm constantly getting around -40dBm. In 3 hours it's gone down over 20% :eek: There's no rogue apps, it's just this radio sucking my battery dry. This sucks! If this doesn't levels out over the rest of the day It looks like I'll be switching back to froyo this evening.

Side note, does anyone use widgetlocker? I keep having this strange bug with the 3.0 lock screen and wl where I'll unlock my phone and both lock screens will be overlapping each other and I can't get to my home screen.

BTW, down another 5% since typing this :mad:
 
Ouch,mine isn't quite that bad(knocking on plywood wall ;)) that sucks!

I don't use widget locker with this,but I'm definately gonna have to give it shot sometime.
 
[Update] i flash the lates of das bamf and i flash the radios by adb as well ... no FC on signal(yet) and everything seems pretty good... my battery is 3hr and its 75% i dont have apps yet and I have just been using it to text...
 
I love my Bamf 1.6.3nte And I am using all the add ons. Black market, Black backgrounds, black mms,contact screen dark. DARK DARK DARK! Can we possibly use those with this?
 
i dont see why not.. the ROM is deodexed .... am not an expert and this deodexed and Oxed thats what gets me confusing... not my best bet...i am not responsible for your phone but ill try it... personally i like stock roms...
 
You must log in or register to reply here.
Back
Top Bottom