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
Related
So I am thinking about isntalling the gingervitis 1.0 rom, I am currently on 1.12.605.6 radio and stock os w/root, I was wondering what radio i need to be on for this rom( he does have a link for a radio but dont know if it is ok to upgrade from the verison i am on) and after i do flash this radio and rom, and say i dont like the rom, if i restore back to stock os w/root am i able to keep the radio i upgraded to or am i going to have to downgrade to a different one, sorry about posting this in general i tried in the actual thread and got no answers.
You should be fine upgrading as long as you follow his steps.
As far as going back, I don't think that radio works on froyo roms. That's why when you flash the radio first and boot your phone back up, you don't have service. I could be wrong, but that's what I've gathered from everything.
I have GB right now and the only problem I've had so far is my text messages are out of order. Other than that, everything works great. I do know a lot of people are having trouble placing phone calls, and having random reboots though. It seems pretty hit or miss, but the developers are working hard trying to get everything as stable as possible.
Seems like every day since the leak a new version comes out with more bug fixes and different sense 3.0 additions. If you don't like the downfalls you see today, wait until tomorrow and see if they've fixed it yet.
I've been very impressed with the amount of bugs have been fixed so far and how fast they've fixed them.
I was having Force Close issue on beta 6 but beta 5 rocked
k i think i am going to do it, do you know if its easy enough to just flash the old radio back on it or am i going to run into problems if i decide to restore back, also when he comes out with updates i should just be able to flash the newest beta on top the other or should i do a wipe and then install again.
I'm having serious charging problems with this rom and the test 4 kernel. Talking like, 3% charged in 45 minutes off the wall.
I'm using the beta 6 Rom with the kernel that came with it and no problems so far not even reboots, have tried the newest kernel by imoysen?
Sent from my ADR6400L using Tapatalk
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...
Ok so i've done just about everything i can think of to stop these reboots except ask and now i'm at that point.
I'm running:
das bamf remix 1.8 ROM
2.6.32.21_bamf_4.47 KERNEL
I used to use 1.7 and still had reboots, switch to bamf 2.1 for GB, and still had reboots, and have tried all 4 radio downloads from the obligatory radio thread. The reboots are truly random. I've had them while charging, idle, browsing web (went and downloaded another browser (which im thoroughly enjoying)) and using pandora.
So what's left at this point? I doubt it's the kernel, but i really don't know, and i want to download the control freak 2.1 kernel because i had it on 1.7 and loved the battery life.
Should i look for more updated radio downloads or just wait and see what happens with verizon?
Go back to stock, call Verizon and get a refurb. Then start new from there. If you have done that much already it may be a hardware problem.
I see. I have a warranty on mine, i can probably take it back to the store. I made a backup of my phone just after i finished rooting, if i wanted to go this route should i just flash that backup and unroot? Or just install the stock rom, kernel and radio?
Follow this
http://forum.xda-developers.com/showthread.php?t=1009423
thank you for that
I rooted my phone using this guide. I wanted CM7 on here, so I flashed the MR2.5 radio. My phone came with MR1. It flashed properly, but now I have no signal and it shows me as having no baseband.
What did I screw up? From my knowledge of radios from my DInc, I can't flash 2.5 again or it'll brick (can't flash the same radio twice in a row).
Would I be able to flash MR2, then MR2.5 again? Basically, wtf do I do, and why did this happen?
you flashed the wrong cm7...there are two versions...one for the mr1 radio and another for the mr2 radios
I didn't even flash CM7. I said I flashed the MR2.5 radio.
When this happened to me I made a backup of my ROM, flashed the file found here, http://forum.xda-developers.com/showthread.php?t=1082114, loaded my backup, and tried again with a different download of the MR2 radio. My theory on why the no baseband thing happened to me was a bad download... I've since started checking MD5 sums every time I flash anything through HBOOT which I should have been doing all along.
I'll try that. It shows me as no baseband, no phone number, no anything. Crap.
if you didn't flash a rom then its normal. You can't flash a 2.0+radio with an mr1 rom and have signal. Nothing is wrong just flash an mr2 rom.
Sent from my HTC ThunderBolt using XDA Premium App
Alright I'll try flashing CM7 then. I hope this works. This is a lot more involved than my Incredible, haha.
Edit: Yup, that's definitely it. I flashed my original MR1 ROM and radio and I'm fine.
Thanks guys!
If you have the MR1 rom, the MR2.5 radio will not work for it due to the new RIL.
And I have flashed radios twice in a row before and nothing has happened...but if you take my word for it it's on you
Yeah it was just something I heard when I was working with radios on my incredible. No clue how true it was, but it's not worth the risk.
I got everything sorted out, thanks guys!
pspkicks316 said:
Yeah it was just something I heard when I was working with radios on my incredible. No clue how true it was, but it's not worth the risk.
I got everything sorted out, thanks guys!
Click to expand...
Click to collapse
Bricks like that don't happen on the thunderbolt if you flash the radio twice in a row, but I still wouldn't recommend it
Before you reply - let me lay a story for ya!
I bought a bran new TBolt off of my friend. I was using a fascinate up to that point and never had any issues. I loved my fassy - it was fast, reliable, and everything worked well.
Now onto the TBolt - I got the SOFF, rooted, got recovery, and got a few Roms. It is still working fine. What's the issue?
Well, I posted this on this forum and other forums more than once, but I can never seem to get an answer. After a few ROMS - Infected, Vicious, ThunderShed - I get a splash screen, or if it does boot it freezes as soon as it accesses the radio components. I have CM7.1 on it right now, ran liquid, vicious miui and other roms. Most roms do work in fact without any problems - but the few that I heard are amazing - do not.
What I have done:
Made sure my recovery is upgraded: I have tried latest CWM, EXT, CWM Touch, and the other one that was popular - all updated and did not work.
Always make sure to wipe: I always format all partitions. I have even used the Superwipe script as well, but to no avail.
I have installed a stock rom, wiped and then installed: Someone said that would work - it did not.
Double, no - triple checked my roms': Checked the MD5 sum of all ROMS and Recoveries.
Different Radios: My phone came with newest radios, and I downgraded, upgraded, and nothing.
Now, I do not mean to sound picky - but I am not happy with the TBolt at all. It works at half the quality that I had from my fassy. Wifi errors out sometime, Tether errors out sometime, it lags some of the time, and most of all - no ICS. Liquid worked well, but the touchscreen wouldn't respond during some games - not that I use it for gaming much anymore - but the idea remains.
It sounds like you are trying all of the right things, so unfortunately I don't really have anything helpful to offer. Just curious though, If you were happier with the fascinate, why stop using it? Did it break?
As far as your issues, I have found CM 7 based ROMs (or any roms not based off of sense builds) to be less reliable and have more "glitches" than sense roms. That certainly could explain some of your gripes with the TB. Have you been able to install any Sense roms other than stock?
I have long since settled on Chingy's gingeritis rom as the most reliable and feature filled, but obviously that opinion differs depending on who you talk to.
To answer your question first: I started using the TBolt because it was 4G and that was important for me at the time (I was a student and had no reliable internet). Things have changed now and I am most likely going to change back sooner than later.
I haven't tried many Sense roms. Which would be the most reliable and recommended?
I know you said you tried downgrading your radios and that your phone came with the newest ones flashed but if you haven't already done so, check this out.
http://forum.xda-developers.com/showthread.php?t=1048128
and here is the radio I've been using with no problems:
gu1dry said:
From the 2.11.605.3 RUU:
CDMA: 1.48.00.0906
md5: c6a5a9eee78e0f33267fa80ced3c49b8
LTE: 0.01.78.0906
md5: 6f33809cf2253c38a3c6bb970f030eee
Click to expand...
Click to collapse
One thing with switching to a AOSP rom from a sense based rom is that you have to use very specific radios. this page will help you find the exact radios you need to use for the rom you are running.
I am running Thundershed 1.6 with these:
http://forum.xda-developers.com/showthread.php?t=1605557
newest leaked radios and they work fine for me.
I use...
I use these with no problems.
Rom: http://forum.xda-developers.com/showthread.php?t=1409703
I use the 605.19 Radios.. http://forum.xda-developers.com/showthread.php?t=1605557
Flashed this kernel.. http://rootzwiki.com/topic/603-kern...minimalistic-kernel-620-6312-camcorder-fixed/
Click the "v6.2.0dev13 - Fixed camcorder again." link at the bottom.
I am running the kernel in "normal" mode.
No issues that I know of but I am still a noob with a post count of 2...
Alright. Thx for the help guys - for the time being I am back to the fascinate, but I will try your suggestions.
One thing I am also trying is the using the "non-semsung" micro sd card in the TBOLT.
I will report back after this weekend with the results.