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
Related
Hey all,
I'm still a newbie, so I wasn't able to follow-up directly in the Das Bamf 1.5 Remix thread.
First off, awesome ROM and thanks for all your hard work. I love the recent apps replacement and battery enhancement.
However, I'm noticing that my phone has randomly shutdown a few times today. Does anyone have any insight on that?
Thanks
Are you overclocking? What kernel are you using?
Nope and I was running Adrynalyne's 4.4.2 experimental kernel (stock speeds), but I just downgraded to 4.3a.
In hindsight, maybe it was just a symptom of using the experimental kernel, however I didn't see the random shutdowns while using Bamf Remix 1.4.
Thanks for the quick response.
I had one as well... it happened only once so far. I'm running 4.4.2 kernel with the remix as well.
MoshingPanda said:
Nope and I was running Adrynalyne's 4.4.2 experimental kernel (stock speeds), but I just downgraded to 4.3a.
In hindsight, maybe it was just a symptom of using the experimental kernel, however I didn't see the random shutdowns while using Bamf Remix 1.4.
Thanks for the quick response.
Click to expand...
Click to collapse
Try running "fix permissions" in RM?
Sent from my ADR6400L using XDA App
I've have had no reboot, wiped all on install, oc at 1200+ on smartASS gov.....
Sent by my ThumperBolt
Thanks for the comments I'm going to give a full wipe a try
If your going to use something other than 4.4.2 I strongly recommend 4.3c. Very stable OC kernel.
4Geezy ON DopeDiculous's ROOTED TBeezy!
Hi,
I just installed BAMF Remix 2 days ago, and I did a full wipe and am not running any different Kernel's other than what came with it. And I and getting random reboots and shutdowns.
Thoughts???
I ended up unrooting my phone to exchange it with Verizon for another reason. However after getting my new phone, I rooted it, flashed the radio RUU and then Das Bamf and haven't gotten any reboots since. A clean wipe seems to fix it.
ive never had a random reboot on this rom until this morning. been pretty stellar so far
Yeah, I had the Radio he recommended and wiped everything, followed all the instructions, and this has been the worst ROM to date for me. Im not one to enjoy Sense in the first place. I used it for about 48 hours, it was pretty sluggish, and titanium backup took about 3 hours, when it takes about 20 minutes on other Roms. I got the random shutdowns, where it would just turned off without notice. I fixed the Permissions and it just wouldnt turn around. So im back to boLTEd .35 and part time CM7 - alpha
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 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
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
What gingerbread roms have you tried? Also, what kernels were you using?
Sent from my ADR6400L using Tapatalk
don't have this issue on Synergy 3.0 running the latest ziggy kernel
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
I would try wiping, then installing the setup in my signature, but don't restore any apps at first or sync with Google so they're downloaded automatically. I think that you've got an app and a kernel that's interfering with one another. Try the ROM bone stock before you start restoring apps and see if the problem is there.
Rooted Thunderbolt on BAMF Sense 3.0 RC 4 with MR2 radio and latest dreamKernel.
Silentdawn3 said:
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
Click to expand...
Click to collapse
when you say both kernels are you referring to the radios? cause mr2 and mr.5 are radios not kernels
Silentdawn3 said:
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
Click to expand...
Click to collapse
I share your pain with this exact problem. I have been doing all types of testing these last two days to see if there is any combination of ROMS and Kernals that would work for me.
I can flash any ROM I want, and the only Kernal that I can successfully use is this one:
Imoseyan GB Stock Kernal
With this Kernal, I can use my phone all I want, let the screen go black, hit the lock screen button and I have never had a reboot.
I have run Thunderstick, BAMF 2.1, BAMF 3.0, Gingertheory, with this kernal and it will run fine.
When I change to any of these Kernals, I get the constant reboots when my screen goes off, just like the OP described.
* Imoseyon Lean Test
* Imoseyon 184mhz
* Imoseyon USBfix
* Imoseyon 2.5.3 test 7
* Nerozehl's dreamkernal 2.3.2
Of course, when flashing any ROMS and Kernal combinations, I would do a complete wipe before doing so. I should also mention that I am using MR2 radio. I can also use MR2.5 with the GB Stock Kernal and it runs fine.
So like the OP, it seems to be something to do with the kernal that my phone does not like and can't figure out. Anything other than the stock kernal, and my phone will constantaly reboot after the screen goes black.
I should also mention that I have used the speektweah.sh in terminal emulator and tried all of the different voltage settings and it had no effect. Also disabled it and tried using SetCPU and no luck either.
I have also tried all of the ROMS without allowing any apps to update by skipping the google account sign in. So basically all of the ROMS were running in their native state, and the outcome would be the same.
FOR THE OP
Try running the stock kernal and let us know if that works for you. You should just be able to flash it in CWM, reboot and you will know right away if it is working correctly.
The real question I need to figure out is this. What is different about the GB Stock Kernal from all the others that would be having this impact on our phones?
I've tried all of this except installing the above kernel. I'll give that a shot, thanks.
As for installing without apps, I've tried that. Tried everything. Lets hope the stock kernel works!
I've been running Das BAMF Gingerstripped with Imo's kernel and never had this issue. It sounds like maybe something is bad with the cpu profiling becoming unstable when screen-off profiles kick in.
sg1dan said:
don't have this issue on Synergy 3.0 running the latest ziggy kernel
Click to expand...
Click to collapse
I can confirm that this one worked for me too. Synergy 3.0 running Ziggy's Kernal and everything works well.
Anyone know where to grab just the Kernal? Can't seem to find the latest download.
I should also add, that when I do flash the Stock GB kernal so that my ROM will be stable.... my camera freezes everytime I try to take a picture. Happens in every ROM I mentioned above. However, it works fine before I flash the stock kernal.
running "stock kernel" it looks to be fixed. Looks like I tried this before as I already had the file but.... works now for some reason
Thanks.
Will report back if it ****s up
I'm hoping I can provide information that may be helpful to developers about the Thunderbird's random rebooting problems.
For my phone it seems related to the ROM I'm running, so maybe this will help ID the problem?
ROMS w/o reboots:
Got the phone, got the OTA update, no reboots. None.
Rooted the phone, configured and ran PG05IMG_MR1_upgrade.zip, no reboots.
After bad experienced, unrooted, back to stock, no reboots.
OTA update again, no reboots.
Re-rooted, again ran the updated rooted ROM, no reboots.
Several listed below caused problems so I'm on Synergy with no reboots.
ROMs with reboots:
Liquid 1.5, reboots 2-3 times/hour
Liquid 1.4, reboots several times/day
Liquid 1.6, reboots several times/day
PUR3A05PTH3ORY v 1.2.2 reboots several times/day
Gingervitis 1.2, no reboots, powers off and won't come back on until I do a battery pull!
I'm really hoping this will help someone take a stab at fixing the problem! Changelogs for Liquid should help, why is 1.5 worse than 1.4 or 1.6? What's included or missing in the ROMs that fail as compared to the roms that work?
Every phone is different, just because a certain version of a rom isn't working well for you, doesn't mean that is the case with everyone. Each phone is different in you have to find what works best for you.
For example, I used Gingeritis based off of the GB leak and was getting a lot of reboots, but I tried BAMF and wasn't getting any. Meanwhile others get reboots on BAMF and don't on Gingeritis. Android is some trial and error before everything works just how you want it, IMO.
I was getting a lot of reboots almost non-stop from PUR3A05PTH3ORY. and I get 1 once in a while with CM7.
I know some TB's even rebooted a lot with the stock rom unrooted. My first one was like that.
I've flashed the mr2 radio and have used it for all roms and I've had no reboots
Bolted Down....
g00s3y said:
Every phone is different, just because a certain version of a rom isn't working well for you, doesn't mean that is the case with everyone. Each phone is different in you have to find what works best for you.
Click to expand...
Click to collapse
Partially true but there are common factors such as many having reboot problems with Liquid 1.5, etc.