Did either MR2 or the latest BAMF fix whatever was causing the Gingerbread related bricking that started last month?
Same questions
I'm wondering the same thing, I haven't heard a lot about gingerbread related bricking lately, I'd like to try one of the new gingerbread / sense 3.0 roms, but I don't want to risk bricking
+1, wanting to move to GB for Skype Mobile and Netflix support. I don't think there was ever any concrete evidence as to what specifically was causing the bricking, so I'd say until an official GB update hits, it's difficult to say that the threat is completely gone, however, I'd lean heavily toward thinking the "beta" leaked MR2 radios may have played part in the problem. Since there's an official MR2 radio out now, I'm getting braver and feeling more safe about trying out GB on my Bolt.
My main concern is I bought my Bolt used, so I can't run to VZW and say I dropped it in the pool if/when I brick it
Yeah, there's no real answer as to why the bricks were happening, but they seem to have been related in some way to that first leaked GB radio. The leaked MR2, MR2.5 and the OTA MR2 are all not bricking phones any more than the stock radio, so you shouldn't need to worry too much about that.
If your phone is going to brick, it will brick no matter what you do. Bricks have happened to stock unrooted users too. IMO its not the radio but a flaw in the hardware - processor, or user FUBAR. Careful too of overclocking. It works fine for some bolts, others just don't like it. It's almost like these things are snowflakes, no two are the same.
courtesy of my rooted bolt
Aye. I'm probably going to flash Das BAMF 2.1 tomorrow. I'd do it tonight, but I need to charge the Bolt, it's pretty low, and it'll take longer to charge my extended battery to full than I'll be awake yet tonight
the bricking was hardware and nothing but hardware so please stop trying to start the rumor it was the bamf rom,why do I say that because it was you first statement, not gingetbread but bamf get a grip
Sent from my ADR6400L using XDA Premium App
satseaker said:
the bricking was hardware and nothing but hardware so please stop trying to start the rumor it was the bamf rom,why do I say that because it was you first statement, not gingetbread but bamf get a grip
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
This is 100% correct. The dev's who were investigating the bricks have determined that it was likely a hardware malfunction, because NOT ONLY were there bricks from the people with the GB radio, but also with older radios, and some who weren't even rooted.
The GB had nothing to do with it.
eMMC failure of sorts, not BAMF caused bricking. I remember when everyone was like "well the only people bricking are on BAMF," then someone on gingeritis bricked and everyone **** their pants
The GB had nothing to do with it.
Click to expand...
Click to collapse
Not necessarily.. one of the theories was that the alpha GB radio was causing more writes to the eMMC than it was supposed to, which was causing early eMMC failure.. yes stock TB's bricked as well, but that could have been something else writing to eMMC. Not like we'll ever know anyways, pure speculation.
Related
I heard that there haven't been any bricking issues with the new mr2.5 radio, is this true? I do realize there is always a chance when flashing anything but has anyone heard of any bricks with it?
Sent from my ADR6400L using XDA Premium App
Been on it since it was released on XDA. Seems to run fine. No issues at all. Did however, find that it prefers a 3G over 4GLTE connection.
hksg said:
Been on it since it was released on XDA. Seems to run fine. No issues at all. Did however, find that it prefers a 3G over 4GLTE connection.
Click to expand...
Click to collapse
not true for me. this radio runs 4g great. and to the OP i already asked this... the radio that caused the bricks was pulled long ago.
Were two Threads on the same topic really necessary?
rooting always has a chance of bricking but your going to take the chance anyways. same thing for the radios. if your flashing them correctly, you should be fine
So I have gotten a 3d 2 weeks ago as a replacement through asurion for my broken evo 4g and like most people on xda it is only natural to root it and slap on a rom the second you get your hands on it. I checked the hboot and to my hearts content it was 1.4, and easy as cake to root since I was coming from evo 4g. The dilemma is that I have tried several roms and everyone I have loaded would give me random reboots and eventually it would just keep rebooting as soon it loads to the home screen. Realizing maybe if I just loaded it back to stock it would help. The random reboots have cut down but I still get it and it's really frustrating. I have checked the battery and it is not loose, and at this point I don't know what to do. I realize that if I go to the sprint store I have to be able to show them the problem. I am also worried that they will update my hboot to 1.5 and claim that I didn't update system software and just send me on my way. Anyone experiencing the same symptoms as mine? Should I just bring it in to sprint to see if I can get a new one?
Thank you
Sent from my PG86100 using Tapatalk
They will update it I suggest you use a format all zip and flash a haus stock rooted ROM or run a ruu hour that works the got me that way updated my phone cause it was over heating
Sent from my PG86100 using Tapatalk
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Yeah I loaded the RUU on it and turned S-off back on. Just sucks because when it doesn't random reboot or bootloop it works great.
Sad Panda said:
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Click to expand...
Click to collapse
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Is your battery loose?
I thought I had this problem at first too but I just popped a business card behind the battery and Viola no random reboots
Sent from my PG86100 using xda premium
bakarus said:
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Click to expand...
Click to collapse
Not a problem at all, that is what the community is all about. Free exchange of information, open source advancement of the platform and technology. Everyone gives a little, and takes a little.
I know there is a dialer code that works to give you that information without the need to install any application, or the need for root access, but after lots of research I was unable to find which one would give that info. However, there is a very useful app that you might want to have anyway. It is called "elixir 2", available on the market for free. Once installed, information > click"processor" > more information > processor: (mine says: ....rev. 2 (v71))
Let us know what yours says [for curiosity sake] please
Quick note, if you replaced the phone through asurion and try to replace it doesn't sprint, don't they refer you back to asurion?
Sent from my PG86100 using xda premium
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
kpsingh said:
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I requested then not to and they still did the update
Sent from my PG86100 using Tapatalk
So just an update, I finally decided to bring it in store today with it rooted and s-off. I was just so sick and tired of it randomly rebooting I just walked into the Sprint store. Technician brought it in, updated the hboot 1.5 =*(. I checked bootloader, and of course I see the locked in capital letters, but I am still s-off. Does that mean I can still load TWRP and root it? Or do I have to follow the HTC method to root it? Thanks for all the help guys!
If it still says s-off, i believe you are good! but that sounds odd, because otherwise we should all be able to update are hboot after rooting? If anyone knows about this...but anyway...
It was not the hboot upgrade but the firmware upgrade that you needed. You did not have to take it to sprint to do that, they have the firmware update without hboot flooting around the dev threads. 2.3.4 and above roms require the new firmware or you'll get the problems you had. No that you have the firmware a lot of the more cutting edge roms still get reboots with most advanced kernels, you have to watch your rom kernel combo, or stick with the stock kernel.
As for flashing, if you really are s-off still, then you can flash anything you want just like on the ol 4g Let us know. Lucky bastard, have fun
[edit] Found this a few threads down:
"I did what you did, had 1.40 and flashed the wrong update, got 1.50 LOCKED with S-off. You can still flash ROMs and Kernels with no issues. I just had to reload TWRP recovery. Then I flashed the 1.40 Bootloader and all was well.
You can grab 1.40 and flash from here: http://forum.xda-developers.com/show...eng+bootloader
***To others reading this...do not flash this, unless you are S-OFF with 1.50 hboot***
You do not need to UNLOCK using the htcdev method. Just flash the 1.40 hboot and you will be fine."
So reinstall twrp, flash 1.40, and have 1.40 s-off and flash the good way
Yep just flashed old hboot 1.3 and merrily rooted, so far so good running cleanrom 2.9 and taking sad panda's advice trying to figure out if it's app related. I am suspecting that it is groove ip running in the background. So far just installed cleanrom and added tapatalk and SwiftKey
Sent from my PG86100 using Tapatalk
I wanted to downgrade my HBOOT from 2.21 to 2.11 or 2.10 I've heard that there is way but at a risk to brick your device. so if there any devs out there that needs a Test subject I'm here just Pm me. the only reason I'm doing this is to go back GB and there Radio.
Good luck my good sir. I salute you. If you find a way, let me know plz, as this radio has all but killed cell reception for me.
As it currently stands, I'm hoping that the OTA update on the 6th is a new base with a new radio.
The new radio works so well on ny phone. I'm so happy I upgraded firmware. Sorry that its not the case with you guys
Sent from my ADR6425LVW using Tapatalk
Yeah this radio has been giving me problems its always dropping , I cant keep a stable connection with ICS
young0ne said:
I wanted to downgrade my HBOOT from 2.21 to 2.11 or 2.10 I've heard that there is way but at a risk to brick your device. so if there any devs out there that needs a Test subject I'm here just Pm me. the only reason I'm doing this is to go back GB and there Radio.
Click to expand...
Click to collapse
they already tried this and could not brick it.
To all with problems with radio I had issues and relocked and ran the upgrade again so you could try that it helped my battery drain and signal problems.
htc rezound
Rom: BAMF ICS v2.0
kernel: SebastianFM
I might have to try again.
Seems to me there'd be a lot more complaints about reception if it were a real issue.
It's gotta be either a bad download, or something I'm doing wrong. I don't think I'm doing anything wrong though, cuz everything else is running great.
Will the OTA release require everyone to re-base again? It may be worth waiting for that.
BBEgo said:
I might have to try again.
Seems to me there'd be a lot more complaints about reception if it were a real issue.
It's gotta be either a bad download, or something I'm doing wrong. I don't think I'm doing anything wrong though, cuz everything else is running great.
Will the OTA release require everyone to re-base again? It may be worth waiting for that.
Click to expand...
Click to collapse
Well it doesn't force the to rebase they will choose to which they probably will but if their is a problem for those of us who already upgraded on the leak I'm not sure if we will be left behind or if someone will fix it for us I know I will try like hell but I'm not as good as most of these devs
Sent from my ADR6425LVW using XDA
Curious to hear from the people that are still s-on and flashed the new ICS leak, how is your phone running? Are there any problems youve run into?
v36sedan said:
Curious to hear from the people that are still s-on and flashed the new ICS leak, how is your phone running? Are there any problems youve run into?
Click to expand...
Click to collapse
I tried it. Major change was an updated kernel. Reverted back to BAMF 2.1 with the previous kernel, as it didnt play well with the change. I'm just waiting for the roms to either be rebased or the OTA to be released. No radio changes only an updated hboot and a few fixes in the rom itself.
Would you run it over the gb rom the phone comes with as a daily driver?
v36sedan said:
Would you run it over the gb rom the phone comes with as a daily driver?
Click to expand...
Click to collapse
Mine loves the new radios, so yes. For most users; they have experienced issues with the radios. My suggestion; s-off before flashing either the old or new leak. That way if you do experience said issues, you will be able to rollback. Also, brings up the thought of being OTA compliant, but that shouldn't matter much as most of the devs here would hve a working rom based off the OTA shortly after.
v36sedan said:
Would you run it over the gb rom the phone comes with as a daily driver?
Click to expand...
Click to collapse
Quite honestly, I don't notice a difference one way or another. This leak was played better with my phone regarding mounting and recovery issues I had on the first ICS leak, but that is more an individual issue I had. As far as signal and reception , I think it is just the fact where I live all of the radios have been the same for me. I am in a rural area of wisconsin with just 3G, so haven't benefitted from 4g or difference in signal strength.
In my opinion, it's easier to s off than to flash the new firmware using the s on method and relocking bootloader and then upgrading then reunlocking and installing recovery and a rooted rom. Also, I've helped about the same amount of people with both. For some crazy reason even though the software seems a breeze to me, people get confused with so many steps I guess, and people who are performing s off and ask me to watch over their shoulder are having much better results than upgrading the firmware.
So I feel really dumb because I am S-off and rooted using Tranquility ICS Rom HBOOT 1.12.PRI 2.45_003 PRL 25006 Baseband 1.12.11.0809 but my cell signal just drops when I am making calls. Could I have damaged the radios somehow while getting to root and S-off? Things haven't been the same since I tried to use CM10. I put CM10 on just after I rooted and flashed I put CM10 on it and that is when I started to notice my radios would just drop. Almost as if they were rebooted. Then I takes me a long time to get a good connection back. Could flashing the wrong firmware for your radios damage them? Not sure if I did that or not but I may have.
I was happy with stock but I wanted to tether every once in a while and that is why I did it. I am horrible and a very bad phone guy.(said with a little chuckle even though it is true)
If you can, please lend me some advice.
Thank you in advance. I really should stop playing with my phones as I am not savy enough to not break them. However I love to tinker but I think I will stick with full sized computers as I know how to fix them.
Andrew
Is this the wrong place to put this?
mayford5 said:
So I feel really dumb because I am S-off and rooted using Tranquility ICS Rom HBOOT 1.12.PRI 2.45_003 PRL 25006 Baseband 1.12.11.0809 but my cell signal just drops when I am making calls. Could I have damaged the radios somehow while getting to root and S-off? Things haven't been the same since I tried to use CM10. I put CM10 on just after I rooted and flashed I put CM10 on it and that is when I started to notice my radios would just drop. Almost as if they were rebooted. Then I takes me a long time to get a good connection back. Could flashing the wrong firmware for your radios damage them? Not sure if I did that or not but I may have.
I was happy with stock but I wanted to tether every once in a while and that is why I did it. I am horrible and a very bad phone guy.(said with a little chuckle even though it is true)
If you can, please lend me some advice.
Thank you in advance. I really should stop playing with my phones as I am not savy enough to not break them. However I love to tinker but I think I will stick with full sized computers as I know how to fix them.
Andrew
Click to expand...
Click to collapse
i believe if you flash the wrong firmware your device just wounldnt boot. you are on the latest radio.
might have a defective radio chip in your phone, but i dont know how to check that
You said you're running an AOSP Rom, right? Check this out : http://forum.xda-developers.com/showpost.php?p=32126633&postcount=106
thefoss said:
You said you're running an AOSP Rom, right? Check this out : http://forum.xda-developers.com/showpost.php?p=32126633&postcount=106
Click to expand...
Click to collapse
I think I am going completely back to stock and see if that has any issues. Maybe my radios aren't right so if I return to stock I will take it back to sprint and try to get it exchanged. thanks all
mayford5 said:
I think I am going completely back to stock and see if that has any issues. Maybe my radios aren't right so if I return to stock I will take it back to sprint and try to get it exchanged. thanks all
Click to expand...
Click to collapse
Okay so friday night I went with the stock rotted rom and Kaboom. My radios returned to normal. Not only that but after going with the custom roms I was having major battery issues(only 13 hours worth with limited use). I cleared the battery stats and charged it Friday into Saturday. I didn't need to recharge until tonight. 1day 8hrs 43mins with a good amount of use. I even used the wifi for about 2 hours at home installing all my apps that didn't get a proper titanium backup for some reason. Everything is back to normal. That is very strange because a lot of guys using those roms say they get similar if not better battery life. Could be me. Thanks guys for the info.
Andrew
Glad it worked for you. I've played with the AOSP roms, but I'm holding out til someone ports a Jelly Bean Sense Rom over. Til then, try Viper 2.3