I was areading a couple of treads saying GB radio will brick you and etc (http://forum.xda-developers.com/showthread.php?t=1096104)
My Tbolt is running fine, but is it recommended I revert back to Froyo?
if so Do I just flash a Froyo ROM and use an MR1 radio?
You should be fine, I've been running Gingerbread for some time now. I believe it was concluded to be a hardware problem, not software.
I agree. I have been running several different GB ROMs with no problem. Some of the ROMs do have specific recommendations for the particular radio based on the testing by the ROM developers.
That being said, I recommend that you run a radio from an official release. For example, I did not update to the leaked radio, I waited until the last OTA was released and the radio had been yanked out of it for separate installation.
You should be fine. It seems like the vast majority of the people are on GB now. Understand tho that there is always a small risk of bricking your phone even on something that people deem "safe".
There's always a possibility of your phone bricking. It wouldn't matter if you were running Froyo or a GB ROM.
Related
Hey all,
I've been perusing these and "other" forums trying to decide if I should perform the stock update and reflash one of the new roms.
I'm currently running Vegan 5.1.1 and loving it. Everything works like I want it to, it's very stable, and I've spent a lot of time "making it mine."
With the new update, and subsequent new roms released by our dear friend Roebeet, I was wondering if there would be much of a benefit for me to Nvflash to stock, perform the stock update, then reflash one of the newer roms, ie Brilliant Corners, Mountain Laurel, or his newest Adam based rom?
I've always been of the school that if it's not broken, don't fix it. I figured that these new roms were intended for those that received their gtablet with the already updated 1.2 bootloader, but I've read people on forums going from 1.1 custom roms, back ot stock, then to 1.2 then reflashing a newer rom. Most of them only report on bugs etc in the new rom, but I've not seen anyone comment on whether it was actually better than their 1.1 rom, or what, if any benefits they saw from it.
I planned on using my current setup until it's outdated significantly. For instance, if Nvidea provides drivers, and VS creates a GB update, then the wonderful devs that are working on gtablet make a true working, supported gingerbread rom, THAT'S when I'll update.
so, bottom line, would it be worth it to nvflash to stock, update to 1.2 bootloader, then install Brilliant Corners? or an I best just not fixing what isn't broken?
thanks for the replies, and I apologizse if this was addressed in another thread. I've searched, read, and couldn't find anything this specific. I've read what the update contains, and what it does, and the problems with it, but I have not read anyone adress a direct comparison betweeen the options that are currently available.
This is probably a silly question, as I'm sure the answer will be yes, but I figured I'll ask either way.
Once the official GB OTA drops, will someone release a stock rooted ROM of it? I just bought my TB, and I'm still waiting for it to arrive, but just trying to do a little planning. I'm sure it will be easier for me to root before the official OTA drops, so I'm definitely going to be doing that.
On the back side, will someone release the official radio that comes along with it too?
The answer to your first question is most probably definitely yes. unless the bootloader is signed in such a way that the awesome devs around here can't unlock it. That shouldn't be the case, so expect a rooted ruu a few days, hours or minutes after the official GB is released.
There already is a working GB radio available. In fact there are two. Search for MR2 and MR2.5 radio. I have been using the MR2 radio without issue for a couple of weeks. Others have found the MR2.5 a better fit for their phones. In any case, they both work with any of the released custom GB Roms. As always, ymmv.
These fourms are full of some great step by step "how to's", from rooting to installing radios. And If you get stuck someone around here will help you out.
Enjoy your new Thunderbolt and the wonderful world of a rooted Android.
Flashing roms and radios is no biggie for me, I've ran a ton of different roms and radios on my Incredible. Rooting will be a little different, I used unrevoked with my Inc, and I've never used adb, so that will be an adventure, but I'm sure I can handle it.
What was the whole frying emmc/bricking/whatever scare with GB? Was it the leaked radios or the ROMs that were the proposed culprit? I read a bit about it on here.
adb is not hard to figure out. If you're ever used command line interface, you will have no problem. jcase posted an excellent root guide using adb commands, all you have to do is copy/paste the commands into the adb window.
I don't think anyone has really figured out why the bricks happened. afaik, all the bricks occurred with the first GB radio leak. I don't think anyone has bricked with the latest radio. The IRC channel may have more info.
I just got around to rooting my TB and have attempted to install a couple of liquids roms. I had to revert back to the original backup both times due to loss of service? is it a requirement to flash a radio right after rom installatio?? Both of my Moto Droids were romed, but the Tb seems to be a different animal.
Any help appreciated, Thanks
ROMs are radio specific, older froyo ROMs use the MR1 radio. GB and most newer Froyo ROMs use MR2 and up. The wrong radio will cause you to lose service, the OP of your ROM thread usually lets you know which radio to run.
setexascustoms said:
ROMs are radio specific, older froyo ROMs use the MR1 radio. GB and most newer Froyo ROMs use MR2 and up. The wrong radio will cause you to lose service, the OP of your ROM thread usually lets you know which radio to run.
Click to expand...
Click to collapse
Thanks for the help, still learning!
No problem, that's what we're here for.
Hello everyone, I'm trying to do a buddy of mine a favor by upgrading his Vibrant to something a lot better (he's on stock) but I'm a bit unclear on a few things. First of all let me get out of the way that I'm a Fascinate (Verizon) owner that recently modded my own phone to run AOKP ICS Milestone 6 with great results, so I figured since he pretty much had the exact same phone I could do it for him. The problem I'm running into is the procedure I used to flash my phone doesn't seem to apply to the Vibrant (or at least what I was searching for) so I just wanted to clear up a few steps before I try to flash his phone.
He's not a very tech savvy guy, so he won't be updating ROMs on the bleeding edge or anything, he just wants his phone to run better so I figure ICZen is the way to go right, considering it's based off of what I'm using now (AOKP M6)? Everything needs to work, so that pretty much rules out any JB right now because of the GPS issues. Okay now onto the specific flashing questions:
1) This thread seems to be the go to thread for flashing the Vibrant, but it hasn't been updated since Dec '11, so would I just follow the same procedure for the newer ICS roms?
2) Here is the guide I used for my Fascinate (see section 4), which has a few extra steps that I notice are lacking for the Vibrant... namely installing cwm4 fixed for cm7 first, then installing THS Build 2, then flash over that with whatever ICS Rom you need.
3) Devil Kernel is what's considered best on my phone running AOKP M6... is that true as well for ICZen?
4) Since the Vibrant never got 2.3, what is the best modem to be using? On the Fascinate the EH03 (GB) stock modem is best, but I'm unsure what the deal is for the Vibrant since they never got an official GB update. Also along the same topic, Verizon has a code you can input that updates your PRL and improves reception... does T-Mobile have such a code or not?
I appreciate any and all input, as I want this to go as smoothly as possible. Thanks
You seem to have a pretty good grasp on what your doing.
From stock, install gingerbread bootloaders then go to recovery via volume rocker down and hold power button, until the logo. Might have to practice it a couple times.
Once in recovery click reinstall packages, might have to do it s couple of times. This installs your update.zip
From here I always perform wipes and flash a custom Froyo ROM. Maybe overkill but, only takes a second and I don't mind.
From here I flashed the latest CM9 nightly and on to Helly Bean.
Do your wipes in between flashes, and you should be fine.
I haven't ever heard about a T-Mobile code for tower updates, I think its automatic.
Well I didn't have to worry about bootloaders on my Fascinate since I was already on GB, so that's a bit new to me... but doing a quick google search I found this guide. Is that an accurate guide to follow? Alright so basically what you're saying is before I root at all I need to do this?
Also like I was saying earlier, he wants everything to work so I think Helly Bean is out of the question because of GPS, right? I was thinking ICZen looks the cleanest, with everything working nicely, and it's based on what I'm currently using on mine.
Can you clarify on why you're flashing a custom froyo rom? I won't mind to do that either, if it has any benefit.
Also, I checked his phone last night and it's on stock 2.2, not 2.1 if that makes any sort of difference. Thanks again
First root and get cwm recovery then flash bootloaders. The vibe never got an official GB, so that's why boot loaders are recommended. The guide you have is fine. Second the GPS on the vibrant has been notoriously hit or miss. I have a captivate, the GPS works great but my vibe couldn't get a lock to save my life.
Now as far as iczen or hellybean, you have to weigh the options:
Iczen is a great ROM and might have a better chance getting a GPS lock. IMO if you can get a lock with ICS you will probably get a lock with JB. But with ICS you have to be concerned with the EU bug. What's that you ask:
There has been an issue with people randomly looking at phone and a message saying encryption unsuccessful press to reset. If you press the button you have basically just locked up your internal SD card. If you don't press you MIGHT be able to recover it. There is a workaround if this happens, to use ext SD only but your friend will not like that.
I'm currently running hellybean on both of my devices and I love it. Like I said, cappy gps works great and my vibrant not so much. If you really want stable go with bionix as toast recommended or one of moped Ryder's ROMs . If you want to be wowed, go with hellybean.
There are some things you can try with it to get a GPS lock. The general consensus is turn on GPS, reboot, wait it out till you get an initial lock. After that locks will be quicker. I hope this helped in some way, if so hit thanks. As far as the guides etc you are good to go.
its peanut butter jelly(bean) time
That did help quite a bit, thank you. I have never even heard of that bug, do you know if that's Vibrant specific or can that happen on any of the others? I have been wanting to try Helly Bean on my Fascinate, but unfortunately my sdcard isn't very stable and I don't trust to flash anything until I can buy a new one. Honestly, I don't even think he cares much about the GPS, my original point was more along the lines of that I wanted to give him as much of a glitch-free experience as possible, so my fault for not being more specific. If Helly Bean is as stable as you're saying, then maybe I'll just do that instead then, especially after you explained that glitch. Also, since I don't have any Helly Bean experience myself, does it offer as much customization as AOKP? I've grown quite fond of all the little tweaks they include
Hellybean is pretty stable. When I did my vibrant I didn't have to use a boot loader I went straight to ICS then jellybean. If you want ICS then you may want to try aokp for his vibe its nice. If you end up trying aokp milestone 6 and have unknown baseband let me know and I'll link you to a linario build that should fix that
Sent from my SGH-T959 using xda app-developers app
I have a complete guide to install ICS ROMs in my signature if you feel so inclined. PM me if you need any of the files or I may just host them on my Dev-Host account. I'll be out most of the day, but I can upload them later on tonight.
When I need to go back to stock and root and flash cwm I use the AIO toolbox. I just put the rom on the internal flash and then use AIO to get cwm on it from the flash custom rom option. Then cancel the file and the phone will reboot into recovery where you install packages twice and should end up in cwm.
The EU bug has hit vibrant and captivates that I know of. It seems rare though, if you think about the number of users compared to the reported number of cases of the EU bug, its a small percentage.Hellybean doesn't have nearly as much customization but it does offer theming and some launcher/lock screen tweaks. You could always use a custom launcher. There are a few other jellybean ROMs you could try. Honestly any way you go will be better than stock!
*I forgot to tell you, you will need to Odin back to stock 2.1!
its peanut butter jelly(bean) time
Yeah.. I don't think root is actually necessary to do any of this. You'll be rooted when the process is complete however. The custom ROMs come with root access.
But to elaborate on Samsgun357's last post, if you are currently on Froyo 2.2 stock, you'll need to Odin back to stock 2.1 prior to starting, because Samsung fixed the bug that allows installation of custom recovery when they released 2.2
It's simple to do, search the forums and you'll find a guide on Odining back to JFD. That's stock Eclair. If I have time in a few I'll locate it for you and post it.
There are YouTube videos about it with links to the files as well. I think djeddie1west posted a good one with links to all files needed, if they are still working links.
Edit: http://forum.xda-developers.com/showthread.php?t=1117990
There's the link for installing GB bootloader.
Also, I am on my phone and haven't tested links, but as long as they work, near the bottom of the post you'll find the files needed to Odin the JFD files.
Eh, I just gave up and told him to go get an iPhone instead, to increase his hipster status.
Or... that's right, I'd rather be dead than own one of those ugly bricks.
You have all been extremely helpful, and I think I have more than enough to go on. I think for now I'll just throw ICZen on his phone since it's based on the rom I'm most familiar with... and when I have more experience with Helly Bean (I finally ordered a new sdcard that's on the way, so I can play with it on my own phone soon enough :good I'll just flash his again. He'll be okay with the risks mentioned so far in this post, and honestly his upgrade is coming up soon so I'm sure I'll be drooling over his S3 when that time comes.
@Woodrube That guide you made to install ICS was exactly what I was looking for, and I wish I had found it earlier so thank you for making such an excellent post.
I'll post back here with the results, thanks for all the help once again
Years ago a friend installed CM7 on my Atrix and now it's pretty unstable. I would like to reinstall the ROM fresh. The question is, which ROM should I install. (He didn't backup before installing CM7)
I'm thinking it would be nice to go back to an official ROM but, there is CM10.1. I'm leary of going back to CM because the 10.1 ROM is not official and it doesn't seem there will be much improvements for CM on an Atrix 4G.
I'm leery of going to an official ROM because I see all the banter of bricking it with Gingerbread.
Suggestions?
Atrixor said:
Years ago a friend installed CM7 on my Atrix and now it's pretty unstable. I would like to reinstall the ROM fresh. The question is, which ROM should I install. (He didn't backup before installing CM7)
I'm thinking it would be nice to go back to an official ROM but, there is CM10.1. I'm leary of going back to CM because the 10.1 ROM is not official and it doesn't seem there will be much improvements for CM on an Atrix 4G.
I'm leery of going to an official ROM because I see all the banter of bricking it with Gingerbread.
Suggestions?
Click to expand...
Click to collapse
The real question is what version of android do you want to run? CM7/7.2 is the only official CM ROM. CM10.1 is not official b/c of the kernel issues, which is still being worked. Does it really matter if a ROM is official or not? No. "Doesn't seem there will be much improvements for CM on an Atrix 4G."? Really? I'm not even going to post the link, I'm just going to say go google android version history and see what CM9, 10, and 10.1 have that CM7 does not have, and then restate that noob statement. Seriously, you have no idea what you are talking about.
Multiple users, including myself, have unlocked, rooted, restored to stock, many times over the past 3 yrs. In addition, there are guides readily available to help you through the process of preparing your device for custom ROMs. So the concern of bricking is a non issue unless you don't know what you're doing. Banter of bricking it only exists if you flash the incorrect sbf. Its not that hard. Sit down, read guides, ask questions as needed.
Let me be the first to admit that I am a noob and have no idea what I'm doing because this is my first foray into the world of smart phones (we all have to learn somewhere).
I went ahead and put CM10.1 on there and after adding the fixed gapp package it seems to be working fine.
Does anyone have a working link to a gingerbread ROM that works for an AT&T Atrix 4G? The links on this tread are dead: http://forum.xda-developers.com/showthread.php?t=1163342