Database Info

[Q] Anyone having freezes, reboots, ALSO in CWM recovery?

I have had my TF for a week or so, and have had no issues whatsover. I have am rooted, running a custom kernel.
All of the sudden I am having the TF reboot at random places, and now it is freezing even in CWM recovery. I wiped everything and went back to stock and still having the problem (on 3.1). Anyone else with this issue, and does it sound like hardware at this point? I think I may return it today, but I am nervous since the screen on this one is perfect.. don't want to get one with light bleed like my last.
Thanks guys.

yes. A quick search will show you the multitudes of threads regarding this issue.

skydirt said:
yes. A quick search will show you the multitudes of threads regarding this issue.
Click to expand...
Click to collapse
Yeah.. I get that.. I have been on XDA for 4 years.
I understand the freezes and reboots happen and are happening and other people are having them happen, however per my subject line I was looking for people who are having it happen while they are in their recovery mode. I have had the tab freeze after booting into recovery, as well as during a restore and backup. I wasn't having any issues for an entire week and without any kernal or rom mods this just started. (SPECIFICALLY IN RECOVERY MODE AS WELL AS NORMAL MODE)

If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras

sassafras_ said:
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
Click to expand...
Click to collapse
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.

superevilllama said:
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
Click to expand...
Click to collapse
Hey there superevilllama, glad to see you back on XDA. Question, are you running custom firmware, ie. custom kernel, ROM, etc? If so, I would suggest downloading the stock firmware from ASUS and flashing back completely to stock and see if that alleviates any issues. If this continues to happen on a completely stock system, you might have faulty hardware.

It was the kernel...
Alright guys.. It was the kernel. I wiped and reset to stock, thinking I had already went back to stock kernel but apparently flashed the same kernel instead of stock.
I checked Clemsyn's kernel thread and # 17 of his had other people getting lockups and reboots too, OC or not. Gave me a scare because I did a bunch of things at one time.. updated kernel, got a new keyboard dock, updated setcpu.
I kept freezing all over the place and rebooting, OC or not. Thought I restored back to stock kernel but I didn't. Thought it was wierd as I had no issues before. Back to 16 of Clemsyn's kernel and all is well, both when not overclocked and OC to 1.5ghz.
I appreciate your help guys. Glad to know my TF is still in good shape. Good thing because the replacement I got had bbaaadd light leakage. Now I can just take it back.

Yes, it was the kernel.
More importantly, it looks like it was the clock speed.
sassafras

It is wierd that it froze in recovery mode tho. I thought recovery had its own kernel, I didn't think it used whatever kernel I had flashed. Eh either way I am glad it is working.

Refurbished G2X and Flashing ROMS

I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernals...
Is anyone else having this problem? This kind of makes sense for me.

TeldenW said:
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernals...
Is anyone else having this problem? This kind of makes sense for me.
Click to expand...
Click to collapse
That should not be the case. The only difference in a refurbished handset is the model number. Other than that, and the fact is is previously used but everything reflashed to stock by LG or TMO, the ROMs should work the same as a DW model phone.

jboxer said:
That should not be the case. The only difference in a refurbished handset is the model number. Other than that, and the fact is is previously used but everything reflashed to stock by LG or TMO, the ROMs should work the same as a DW model phone.
Click to expand...
Click to collapse
I'm all out of ideas then... Do you have any idea why I'd have so much trouble loading other ROMs?
Like I mentioned, I'm no pro, but I've Flashed enough ROMs to think that I'm "good" at it.
I'm completely stumped.

TeldenW said:
I'm all out of ideas then... Do you have any idea why I'd have so much trouble loading other ROMs?
Like I mentioned, I'm no pro, but I've Flashed enough ROMs to think that I'm "good" at it.
I'm completely stumped.
Click to expand...
Click to collapse
Before flashing a new ROM did you do a factory data reset, format the system partition and clear the Dalvik cache? If not you will have problems as you described. You need to wipe the phone clean between flashing different roms. If upgrading to a new version of the same rom you might get away without a wipe. But if you are changing roms the steps I mentioned above are essential or you will often get bootloops or the phone will lock up during boot.

jboxer said:
Before flashing a new ROM did you do a factory data reset, format the system partition and clear the Dalvik cache? If not you will have problems as you described. You need to wipe the phone clean between flashing different roms. If upgrading to a new version of the same rom you might get away without a wipe. But if you are changing roms the steps I mentioned above are essential or you will often get bootloops or the phone will lock up during boot.
Click to expand...
Click to collapse
JBoxer, I make SURE to Reset/Wipe/Format/Clean everything EVERYTIME.
That's what I can't get figured out. I've been meticulous about it!
And I still get the frozen bootscreens and the lock ups.
Any other ideas?

Are you using rom manager because mine does that unless I use the cwm I installed from my computer
Sent from my LG-P999 using xda premium

monte666 said:
Are you using rom manager because mine does that unless I use the cwm I installed from my computer
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I'm using the NVFlash method.

Best ROM I found with the least problems
TeldenW said:
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernels...
Is anyone else having this problem? This kind of makes sense for me.
Click to expand...
Click to collapse
the Best I've found if you want gingerbread style is Hellfire phoenix
or if you want ICS style is Hellfire sandwich v1.6 (which is what I am using for a while now)
the only problem that I found is the video camera but other than that everything else works fine on my G2X. they update couple times a month for the last 4 months so they are always trying to make things better for their users. if you have problems they are more than willing to try to help you with it. if you are using with a simple mobile setting it has a funny setup but it work very good (better wifi & phone signals)

adeptustech said:
the Best I've found if you want gingerbread style is Hellfire phoenix
or if you want ICS style is Hellfire sandwich v1.6 (which is what I am using for a while now)
the only problem that I found is the video camera but other than that everything else works fine on my G2X. they update couple times a month for the last 4 months so they are always trying to make things better for their users. if you have problems they are more than willing to try to help you with it. if you are using with a simple mobile setting it has a funny setup but it work very good (better wifi & phone signals)
Click to expand...
Click to collapse
Second that but i'm on the GB til video can work good
Sent from my LG-P999 using xda premium

My original g2x could handle oc and UV big time, anything the devs put out . My replacement can only handle kernels with stock voltage and oc is unstable anything past 1.1ghz. So to answer your question, may be a coincidence or may just be bad luck on our part. Remember, not every processor is created equal despite being the same phone. I get tempted to get an additional replacement every once in a while but laziness tells me otherwise.
Sent from my LG-P999 using xda premium

TeldenW said:
JBoxer, I make SURE to Reset/Wipe/Format/Clean everything EVERYTIME.
That's what I can't get figured out. I've been meticulous about it!
And I still get the frozen bootscreens and the lock ups.
Any other ideas?
Click to expand...
Click to collapse
Possibly cleaning and wiping everything soo good that you clean the new rom right off your sd card?? lol. just a thought. ive done that when i 1st started flashing roms. or possibly flashing gapps on roms that dont require you to?
edit: i just realized how old this post is. lol

the reason refurbs night have worse luck is because of all the people who send their phones back because of that, they make up a reason to tell Tmobile and get a nice shiny new one. The old one is reset and passes all the "official" stability tests and gets sent out again.
Sent from my LG-P999 using Tapatalk 2

wifi error on every ROM

long story short, my phone was shipped with prerelease software. After rooting and flashing a customer recovery, my original nandroid was corrupted.
The only option for me now is custom ROMs, but unfortunately my wifi gives me an error on every single ROM available.
Anyone know of a quick fix?
The only thing i can think of that would solve the issue is to possible flash the stock US ROM once it's available, then hopefully that would fix my wifi issues and i'd be able to flash to any other ROM with no problem.
Alternatively - could someone please post a flashable ZIP of the stock ROM, or at least post a stock nandroid that i would be able to restore onto my phone to see if the wifi issue gets resolved.

Did flashing the stock img work
Sent from my PC36100 using Tapatalk 2

I have a fix for you. I'm releasing it tomorrow though.
I'm releasing a stock T-Mobile nandroid final firmware and newest software.
I'm also releasing a rooted version.
Sent from my HTC VLE_U using XDA

Full wipe on everything?
Sent from my Galaxy Nexus using Tapatalk 2

MikeyCriggz said:
Full wipe on everything?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.

Reviewers said:
I have a fix for you. I'm releasing it tomorrow though.
I'm releasing a stock T-Mobile nandroid final firmware and newest software.
I'm also releasing a rooted version.
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
Thanks, hoping this will solve the problem!

suhailtheboss said:
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Click to expand...
Click to collapse
It's because all roms now are based on European firmware not T-Mobile firmware.
Tomorrow I'm uploading the first ever T-Mobile Rom and it'll fix everybodys problem.
Sent from my HTC VLE_U using XDA

suhailtheboss said:
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Click to expand...
Click to collapse
Definitely sounds like a firmware or driver issue. Have you tried resetting your router or updating its firmware? Also, what kernel version are you running.
Sent from my Galaxy Nexus using Tapatalk 2

MikeyCriggz said:
Definitely sounds like a firmware or driver issue. Have you tried resetting your router or updating its firmware? Also, what kernel version are you running.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
tried connecting to a different router on update stock firmware and teh issue still exists.
I was hoping that with the stock TMO-US ROM the problem would be fixed, but unfortunately not.
Now i have really no idea. It's impossible for me to live without wifi on my phone for good.

suhailtheboss said:
tried connecting to a different router on update stock firmware and teh issue still exists.
I was hoping that with the stock TMO-US ROM the problem would be fixed, but unfortunately not.
Now i have really no idea. It's impossible for me to live without wifi on my phone for good.
Click to expand...
Click to collapse
Do this:
1. Delete /data/misc/wifi folder using a file browser.
2. Clear cache using recovery. Reboot. Wifi will regenerate its data.
3. Try wifi again.
Let me know if this works. It's a shot in the dark so I don't know if that's gonna work for you, since you already seem to have performed a fac reset.

nickmv said:
Do this:
1. Delete /data/misc/wifi folder using a file browser.
2. Clear cache using recovery. Reboot. Wifi will regenerate its data.
3. Try wifi again.
Let me know if this works. It's a shot in the dark so I don't know if that's gonna work for you, since you already seem to have performed a fac reset.
Click to expand...
Click to collapse
Thanks for the tip, unfortunately this didn't work either. I'm totally out of ideas at this point. Might just end up exchanging the phone and paying the out of warranty fee if they find out the boot loader was unlocked. Not really sure what's left for me to try.

Flash my T-Mobile Nandroid in recovery.

Reviewers said:
Flash my T-Mobile Nandroid in recovery.
Click to expand...
Click to collapse
I did within ten minutes of you posting it. Unfortunately it did not solve the problem. I thought that would be the fix...

One thing I didn't notice was a clear description of the problem. Please describe what your issue is. You say the wifi gives you an error. What does that mean?
Please describe everything in detail from start to finish, before trying to return it.

WiFi will turn on, display available networks, once a network is selected it will not connect and then says "error"
then after about ten seconds the phone will reboot, then reboot after it turns on. never-ending.
only way to have the phone work is to do a master reset, but the problem starts again when you attempt to.connect to WiFi.
also the phone will not stay off when stuck in the WiFi reboot loop. if i choose "power down" it will turn off, then turn back on within 10 seconds.

That sounds very very strange. Almost like a kernel error (unlikely since kernel is included w/ ROMs), a radio issue (more likely), or a hardware issue (most likely, in my opinion). If you've already done a full wipe and wiped /system and /sdcard to be sure, then it sounds like you've done your due diligence.
At this point you might want to go ahead and reflash the stock ROM (see Reviewer's post with a nandroid of the stock ROM), reflash the stock recovery, and relock the bootloader. Unless someone else can chime in here. Also, if you return it, there's no promises that they won't look for TAMPERED or anything in the bootloader, so beware. The important thing is to have the stock software and recovery loaded and it relocked. Then they can flash it in the store, and it'll probably fail, in which case they may replace it.

nickmv said:
That sounds very very strange. Almost like a kernel error (unlikely since kernel is included w/ ROMs), a radio issue (more likely), or a hardware issue (most likely, in my opinion). If you've already done a full wipe and wiped /system and /sdcard to be sure, then it sounds like you've done your due diligence.
At this point you might want to go ahead and reflash the stock ROM (see Reviewer's post with a nandroid of the stock ROM), reflash the stock recovery, and relock the bootloader. Unless someone else can chime in here. Also, if you return it, there's no promises that they won't look for TAMPERED or anything in the bootloader, so beware. The important thing is to have the stock software and recovery loaded and it relocked. Then they can flash it in the store, and it'll probably fail, in which case they may replace it.
Click to expand...
Click to collapse
Yeah i'm clueless. I've literally done absolutely EVERYTHING that i could imagine to fix the issue.
I actually work for T-Mo, we dont have any abilities to flash anything in store. Also exchanging the phone is a little bit more difficult for me, because the phone was not purchased through tmobile, it was given to me by HTC a week before launch.
Either way, I'm going to reload all the shipping stuff when i get home tonight then go ahead and try to process an exchange. Worst case scenario they will charge me ~100 bucks as an out of warranty fee. (due to having the *TAMPERED* logo on the bootloader scren. Although I'm fairly certain they don't check that, they shoudl only check for physical/liquid damage. I have processed many exchanges for rooted customers, who had manufacturer defects.

also another thing i just noticed, my baseband is: 0.15.31501S , but my friends retail version is 0.16.
any way for me to update this?

Early Adopters
I just got the One S myself and I'm a bit forlorn from the lack of available ROMS. Then again when I was in the Apple Ecosystem, there was no ROMS, just tweaks so different environment different timelines I guess.

Not sure if it can help in this case, but this solved my wifi error problem.
I had a "wifi error", my One S coudn't connect any AP.
The problem was a bad permision on the file /data/misc/wifi/wpa_supplicant.conf.
Logcat gave me that :
"Cannot set RW to /data/misc/wifi/wpa_supplicant.conf"
So, using Es Explorer (as root), i changed the chmod of this file to rw-rw-rw and wifi started to work again. (no reboot needed in my case).
Hope this help.

Cant connect to google services.

Well, strange issue here that I'm going crazy over. Recently I've rooted and such but run stock Rom on my one s. I downloaded a google play patcher and freedom apks to check them out and suddenly lost connection whenever I would open google play store so I knew right away it was a result of those apks. I uninstalled them and tried again with no luck. I then reinstalled google play store apk and cleared all the data/cache with still no results. At this point I decided to back up my important apps via titanium backup and did a complete factory reset. Setting my phone back up it asked me for my google account to synch contacts and such. Full signal 4g and full signal WiFi both fail to connect to google. Aside from trying to flash a new Rom and try I'm at a loss. I don't want to use a custom Rom I only want root access on my phone. Does anyone know how I can fix this ? I know the google patcher and freedom jacked my phone up and I do intend to avoid them for good now. Thanks.

RussianBoots said:
Well, strange issue here that I'm going crazy over. Recently I've rooted and such but run stock Rom on my one s. I downloaded a google play patcher and freedom apks to check them out and suddenly lost connection whenever I would open google play store so I knew right away it was a result of those apks. I uninstalled them and tried again with no luck. I then reinstalled google play store apk and cleared all the data/cache with still no results. At this point I decided to back up my important apps via titanium backup and did a complete factory reset. Setting my phone back up it asked me for my google account to synch contacts and such. Full signal 4g and full signal WiFi both fail to connect to google. Aside from trying to flash a new Rom and try I'm at a loss. I don't want to use a custom Rom I only want root access on my phone. Does anyone know how I can fix this ? I know the google patcher and freedom jacked my phone up and I do intend to avoid them for good now. Thanks.
Click to expand...
Click to collapse
Reset wont work if the patcher patched an apk. If you got TWRP or CWM you could try flashing gapps to see if that works.

Thanks for the quick reply ill try to figure it out. Would gapps be on already or do I have to go find it somewhere?

RussianBoots said:
Thanks for the quick reply ill try to figure it out. Would gapps be on already or do I have to go find it somewhere?
Click to expand...
Click to collapse
Get gapps here and make sure you get the right one.

Thanks again but how do you determine which one? I run stock Rom. Those appear to be for cyanogenmo. Would I need to flash that beforehand? I'm not experienced really in doing any of this and I know its not your problem so I really am quite thankful for the assistance. The only thing I've done is unlock bootloader, flashed TWRP and installed superuser. Flashing other rims I wanted to avoid as I'm content with the stock and didn't want to move away from the familiar. If its the only way to recover my google access then ill have to though I guess.

RussianBoots said:
Thanks again but how do you determine which one? I run stock Rom. Those appear to be for cyanogenmo. Would I need to flash that beforehand? I'm not experienced really in doing any of this and I know its not your problem so I really am quite thankful for the assistance. The only thing I've done is unlock bootloader, flashed TWRP and installed superuser. Flashing other rims I wanted to avoid as I'm content with the stock and didn't want to move away from the familiar. If its the only way to recover my google access then ill have to though I guess.
Click to expand...
Click to collapse
If its 4.0.4 then use the one for CM9 and if its 4.1.1 then you want the CM10. If that don't work and don't want custom rom the you need a RUU to get it fully stock.

Well phone told me 4.0.4 so ill give it a try. Thanks again, ill report back if it worked.

Well, I downloaded, booted recovery, flashed it, rebooted and now all the google apps just force close so I can't even get the connection error. I'll try flashing a Rom later or the ruu. If anyone has any ideas much appreciated.

Did you clean cache and dalvik-cache after you flashed it? You also need to clear the data for the google apps (done in settings -> apps in the phone) alt. factory reset it.

Goatshocker said:
Did you clean cache and dalvik-cache after you flashed it? You also need to clear the data for the google apps (done in settings -> apps in the phone) alt. factory reset it.
Click to expand...
Click to collapse
Yup already done. Both actually, I cleared the data/cache in the settings and I did a factory reset twice. No luck. I'm going to attempt flashing a custom ROM if I can find one that is actually decent but most appear to have issues with WiFi or something that'd drive me nuts. flash the partition patch is recommended like with the viper but after readying 20 pages I have no idea still wth they're talking about.

As far as I can work out, it seems the wifi issues is mainly with t-mo devices. Ive never had any wifi issues on mine with hboot 1.14.

I have a TmoUS HTC ONE S S4. Not entirely sure what hboot is. Like I said i'm still kinda new but I did read enough to see that there's WiFi issues so I don't want to push it. Ive been reading through all the ICS ROMS and half seem to be outdated and broken.

If you want an ICS rom, go with ViperS 1.2.1. Great rom
hboot is listed in the bootloader.

Viper is the rom that's apparently having wifi issues from what I read where it says to flash the partition or whatever and I couldn't find out what they were talking about. I'm checking out some JB rom now called jellybam, if I can manage to install it hopefully it works out. As for the hboot thing still no idea lol I'm honestly not going to try to figure it out. I simply want my phone with root access and working google again I don't want a custom rom at all but I apparently have no choice

RussianBoots said:
Viper is the rom that's apparently having wifi issues from what I read where it says to flash the partition or whatever and I couldn't find out what they were talking about. I'm checking out some JB rom now called jellybam, if I can manage to install it hopefully it works out. As for the hboot thing still no idea lol I'm honestly not going to try to figure it out. I simply want my phone with root access and working google again I don't want a custom rom at all but I apparently have no choice
Click to expand...
Click to collapse
Try Viper 1.2.1 and if you have issue then there is a TrickDroid thats T-Mobile base so it should be fine there.

I've successfully flashed Viper 2.0 and have access to google again now finally. Only issue is that sine I had the 4.04 update my wifi no longer works so I have to figure out how to fix that. There's flashing of something but I have no idea what he was talking about as he simply said that and provided no links or explanations.

RussianBoots said:
I've successfully flashed Viper 2.0 and have access to google again now finally. Only issue is that sine I had the 4.04 update my wifi no longer works so I have to figure out how to fix that. There's flashing of something but I have no idea what he was talking about as he simply said that and provided no links or explanations.
Click to expand...
Click to collapse
You can't fix it without upgrading to JB which you can't yet or downgrade the Hboot, so you better off trying Viper 1.2.1 and see how that goes for wifi.

xD exactly the reason I didn't want a non-stock ROM lol Honestly after the headache I'm just going to keep what I have. I thought the H signal was pretty much the G network but it turns out that it's fast like my normal 4G which it keeps bouncing between 3G and H. Makes no sense to me but as long as i'm not down in the basement I should have 4G signal. All this flashing and having to reinstall everything and update blah blah just isn't worth the trouble and effort. I have half the mind to revert back to stock rom and just reroot and leave it there hopefully working.

RussianBoots said:
xD exactly the reason I didn't want a non-stock ROM lol Honestly after the headache I'm just going to keep what I have. I thought the H signal was pretty much the G network but it turns out that it's fast like my normal 4G which it keeps bouncing between 3G and H. Makes no sense to me but as long as i'm not down in the basement I should have 4G signal. All this flashing and having to reinstall everything and update blah blah just isn't worth the trouble and effort. I have half the mind to revert back to stock rom and just reroot and leave it there hopefully working.
Click to expand...
Click to collapse
I think this is the best time to do it since you not settled with it yet and I like I said there is T-Mobile TrickDroid so you wont even lose wifi calling and also pretty much stock.

For some reason that didn't work either. I relocked bootloader, reflashed stock Rom and rerooted. Everything works again, thanks again for the help though guys. This thread can be closed now.
Sent from my HTC VLE_U using xda premium

Re: [BeanStalk][1.179] Phone freezes after call

Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over

qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.

bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.

qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.

bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo

OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548