Database Info

Cause of GB reboot and possibly prevent brick

OK Guys and Gals, Here is what is going on with the radio issue. No Matter WHAT radio combos you may be using. As some of you may know by my earlier posts I live in a huge 4G network and never get anything, but 4G and (3G only for a min on boot) This is why I didn't have ANY issue's until I got curious and wanted to try something. On our tbolts, if you try to make a call while in 3G the 3G will drop out until the call is over. I went back to froyo, got pissed and went strait back to GB (doesn't matter what Rom as all the dev have clearly stated) when I did go back to GB things were tight as usual. worked like a charm. I used it as I normally would and everything was fine. upon a self induced restart, before my phone had a chance to obtain 4G (still in 3G) I decided to make a test call to see if the 3G would drop. It didn't. Quickly after I ended the call the phone booted in to bootloader. Thank God I had removed the GB RUU because I don't have a card reader to remove the RUU. I forgot to mention I do have the latest Rom Mgr and was able to get into recovery and simply reboot. After that reboot I would get to my home screen, but this time the 3G only would come up and then reboot. Time after time of rebooting I tried other things such as toggle radio to just grab 4G, then the phone rebooted again! upon the next full boot I quickly moved the original froyo radio strait to the sd card. And yet another reboot. This time I got a Rom Mgr error and noticed that Rom mgr was no longer flashed!!! I flashed it real quick because I knew another reboot was on its way. Rom mgr flashed and I told it to boot in to recovery. Thank **** I flashed Rom manager because if not I would be in continuous boots like the unfortunate others. Once in recovery I Realized that I had told my phone to go in to recovery via Rom mgr. and if I did a restore, the phone would have booted back up with my froyo rom but with the GB radio! so I told CWR to just reboot so I could tell the phone to go into recovery via the pwr restart option (thus not restarting after I flashed my froyo recovery) Once recovery of my froyo rom was complete I used ADB to reboot bootloader and SUCCESS! Bottom line you can not make a call while on 3G with any of the current GB radios, you gotta be quick, Make sure ROM mgr is actually flashed!!!! and hopefully can dump the froyo radio on to your SD card before an inevitable reboot happens! and have some ADB knowledge. I'm certain this is whats going on! People make a call while in 3G and its all down hill from there. So dont bother with telling radio settings to stick with one band. Once this happens, there is no turning back. Any questions PM me. I'm glad I tried this out before Vaca tomorrow with a FUBAR Tbolt
Hope this helps developers somehow. Good luck!
Also check a couple quotes from the development thread. Remember I'm going on vacation n won't be able to reply to many comments. Maybe just share your experience. Thank you
Sent from my ADR6400L using XDA Premium App

The people with the reboots can't get to Rom manager or recovery or anything. It reboots even if you try to gget in Clockwork.

I live in a 3g only area and make calls all the time on 3g. I have myine set to cdma auto so its always on 3g and mine hasn't done it yet. I'm on the gb radio
Sent from my ADR6400L using Tapatalk

smalltownbird said:
I live in a 3g only area and make calls all the time on 3g. I have myine set to cdma auto so its always on 3g and mine hasn't done it yet. I'm on the gb radio
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Yes this is true because your phone doesn't try to toggle to the 4g lte radio
Sent from my ADR6400L using XDA Premium App

corenojoe said:
The people with the reboots can't get to Rom manager or recovery or anything. It reboots even if you try to gget in Clockwork.
Click to expand...
Click to collapse
They can't get into rom Mgr because they didn't notice rom manager needed reflashed right before first reboot.
Sent from my ADR6400L using XDA Premium App

I live in a 4G area, was running GB Bamf rom. Made plenty of calls on 3G and on 4G lte. Never had this happen.

dopediculous said:
They can't get into rom Mgr because they didn't notice rom manager needed reflashed right before first reboot.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.

refresh my memory, my poor old brain is on overload from all the brick posts....
Aren't the "bricked" phones also unable to stay in hboot for more than a few seconds without rebooting? If so, then what the OP is stating is NOT the same thing others reported because he states he could reflash the radio, suggesting a stable hboot/bootloader.
Seems like if you've got a stable hboot, you're not truy bricked, as the first post here shows....

bp328i said:
Ask me how I know
Click to expand...
Click to collapse
If you have a bricked device please go post in the stickied thread in app/dev.
Oh and OP - Paragraphs are a good thing. Just sayin...

bp328i said:
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.
Click to expand...
Click to collapse
I ment while in rom Mgr to make sure cwr is actually flashed. Mine was then after reboot I noticed cwr was no longer there. In rom Mgr it just said what the current cwr would be if I choose to flash it. If people miss this after a stupid reboot, the next reboot may not be so kind...
Sent from my ADR6400L using XDA Premium App

bp328i said:
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.
Click to expand...
Click to collapse
In fewer words that's exactly what I was saying. Seems like he thinks Rom Manager is recovery.

distortedloop said:
refresh my memory, my poor old brain is on overload from all the brick posts....
Aren't the "bricked" phones also unable to stay in hboot for more than a few seconds without rebooting? If so, then what the OP is stating is NOT the same thing others reported because he states he could reflash the radio, suggesting a stable hboot/bootloader.
Seems like if you've got a stable hboot, you're not truy bricked, as the first post here shows....
Click to expand...
Click to collapse
Mine was a TRUE bricked phone but my bootloader stilled would stay on. The bootloader screen was the only thing that would not bootloop. I was able to flash the stock RUU and stock bootloader and it still would not go past the splash screen.

funkybside said:
If you have a bricked device please go post in the stickied thread in app/dev.
Oh and OP - Paragraphs are a good thing. Just sayin...
Click to expand...
Click to collapse
Mine was bricked last Saturday, I don't have the phone anymore. It's been sent off for repair. Lucky me gets to rock my DInc for the next 2 - 3 weeks, DAMN 3G is slow.

dopediculous said:
I ment while in rom Mgr to make sure cwr is actually flashed. Mine was then after reboot I noticed cwr was no longer there. In rom Mgr it just said what the current cwr would be if I choose to flash it. If people miss this after a stupid reboot, the next reboot may not be so kind...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Your phone will still reboot without a recovery. There was an issue awhile back when I had my OG Droid with ROM Manager wiping out recovery. People would try to boot into recovery to fix something and oops no recovery.
You can flash a recovery image via adb.

bp328i said:
Your phone will still reboot without a recovery. There was an issue awhile back when I had my OG Droid with ROM Manager wiping out recovery. People would try to boot into recovery to fix something and oops no recovery.
You can flash a recovery image via adb.
Click to expand...
Click to collapse
yeah, that was annoying. Believe that's when they told everyone to check the "erase recovery" option in the Rom Manager settings and that seemed to help.

PJnc284 said:
yeah, that was annoying. Believe that's when they told everyone to check the "erase recovery" option in the Rom Manager settings and that seemed to help.
Click to expand...
Click to collapse
Really funny thing was that was going on right when the Froyo leak came out for the OG Droid and the first ROM I flashed I hated. So when I went to flash my nan-droid there was no recovery and I did not know about the issue so I ended up sbf'ing back to stock and rerooting again.

I have seen a bootloop on a phone that was not running GB or rooted. A guy I work with brought me his phone a few weeks ago and wanted me to let him use my battery to boot his phone. When I put my battery in and saw what it was doing i booted it into Hboot (of course S-on) so I couldn't do much for him. Of course the Verizon Tech's weren't much help to him either, but they did send him a CLN Device. You can pass this along to jcase as I don't have enough posts to be able to post in the DEV forum yet. I read and rarely post unless I believe I have something useful to add.

Bricked after all this time

I had a lunch TB4g and it just bricked today, I was running ShiftAOSP 1.2 (I believe unrelated) and the .802 radio (possible) but it will just go to the HTC screen and reset and keep trying to boot. I can get into HBOOT and FASTBOOT, I have tried to reflash a root friendly RUU but it didnt fix anything and still cant boot. Just giving you a heads up. I had it overclocked to 1.22, I had it in my car on the way home, sent one text, 23% battery and I plugged it into my CPU USB to charge for a little waiting for some friends to show up and that is when it went into bootloop. Heat was not an issue as I had used it minimally the whole day sending small texts. It did sustain a major G shock 2 days prior but no excessive G or roughness today. Since it can get into HBOOT it might be recoverable but thats to the devs to decide, I have the unlocked 1.04 hboot installed.

i doubt the radio caused it, but that sucks man. see if you can talk verizon into a bionic for a replacement.

Does it bootloop in recovery?
Sent from my HTC Thunderbolt

JBO1018 said:
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.

fixxxer2008 said:
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
Click to expand...
Click to collapse
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt

JBO1018 said:
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.

it will boot to hboot and not reboot, but it will not boot to recovery

Have you tried flashing one of the recoveries that were modified to install through hboot? you can take your sd card out, and using a computer, place the PG05IMG.zip (search here @ XDA) and place it on the root of the card, flash through hboot. then using the computer again, remove the PG05IMG.zip from the sd card and go back into hboot and select recovery. i had to do this not too long ago and it worked for me, maybe it will help you.

I pulled the battery and wont plug it in all night to see if it resets some error it maybe had, my new phone is delivered tomorrow so its not a big deal.

fixxxer2008 said:
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
Click to expand...
Click to collapse
I would agree. The whole reason I asked about recovery boot looping is because if it is thats pretty much identical symptoms everyone who had the boot loop of death "brick" thing had. If that is what the situation is I would get it s-on and get VZW to replace because I doubt he caused it.
Sent from my HTC Thunderbolt

fillyo said:
All you cheap ****ers trying to get something for free, if he bricked, his loss. Period.
Click to expand...
Click to collapse
Ditto. He probably told insurance he lost the phone and paid his $100 bucks.
People are so greedy these days. All for nothing and nothing for all.

Doesn't sound design like there was much effort to fix it either.
Questioned posted and shortly after a new one is on the the way?
Keep an extra phone around for instances like this.
Not everything is an insurance claim.
Sent from my A500 using XDA Premium App

You wonder why all the major companies are starting to hate people who root phones. Some people will flash a Rom everyday just to do it and if they miss up their phone they don't seem to care. Now do I think a thunderbolt is worth 700 bucks retail hell no it only cost about 125 to build. But people need to hit up these forums to try to fix their phones before they call Verizon. I read a few post of guys who buy bricks phone fix them and sell them so any bricked phone can be fixed as far as he said. Read up and don't be so quick to clear data as first sign of a problem. Always try what got me out of the bootloop of death.
1. Battery pull
2. Power and hold down volume button
3. Never and I mean never keep a radio stored on root of SD card after install this will cause Hboot to install radio and that is not what we want to do here.
4. Go to recovery
5. Under download folders in your SD card always keep a updated ROM of what ever ROM you are currently using or at least a stable build inside that folder if you are using AOSP keep a stable ROM that last worked for you so no data clear is needed if you are using Sense do the same.
6. I never flash a recovery at this point follow this it saved my phone. Clear cache, clear delvik, format system under mounts and storage.
7. Format is most important since it will not delete recovery if you need to try again. Go to install zip file, select zip file, and install your fresh ROM or a stable build I never have flashed a normal ROM or have I flashed back to a down graded GB ROM.
8. Reboot after ROM has flashed and your phone will boot correctly.
I hope this has helped it saved me a few times in boot loop of death. Stop clearing data you lose your recovery and stop flashing old GB ROMs thinking they will save you, it might but message me so I can say I told you so.
****NOTE also make sure you are updated to newest CWM there was a problem with bootlooping after flashing a kernel and maybe Rom. I had the problem with flashing a kernel sent me into a bootloop. Update or roll back.******
Sent from my ADR6300 using XDA App

The OP probably gets into recovery for a few seconds then bootloops randomly. If you are not bootlooping in hboot, you are not bricked. Find the stock ruu file and flash that through hboot. Although you will lose root, the phone should work again.

If it's bricked, throw it to the ground and stomp on it til it breaks and claim insurance..... That should piss some people off here
Seriously tho some guy mentioned something about a HBoot friendly RUU. You should look into it
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App

As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt

JBO1018 said:
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
Sent from my ADR6400L using XDA App

Grnlantern79 said:
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
If he can't think of a way to fix it send it to me will have it running in a couple of google searches.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App

I tried to get into recovery a few times before doing anything, it would just go black and reboot to the HTC logo. As a last attempt I tried to load a rooted a ruu, it installed but didnt not boot. I have the 1.04 modded hboot so I dont think I can overwrite recovery. Either way, contrary to your beliefs I will not claim insurance on it, although this is a warranty issue, these phones are dropping left and right. I just moved to tmobile this week and my sensation 4g and G2x are supposed to be delivered today.

Thanks for your ideas but I tried to reflash recovery and it installed through hboot but it will just reset before it loads. I still have s-off and my emmc was the sem08g. I am going to plug it in and just let it boot loop all day while I am at work, maybe it will get out, maybe it wont, either way is it wont hurt anything.

ClockworkMod Recovery Touch on Inspire 4G?

Has anyone tried the touch recovery on an Inspire?
http://www.clockworkmod.com/rommanager
There's only a DHD version and my understanding from the ICS development threads is that DHD and Inspire have different touch screen drivers?

Elbob10s said:
Has anyone tried the touch recovery on an Inspire?
http://www.clockworkmod.com/rommanager
There's only a DHD version and my understanding from the ICS development threads is that DHD and Inspire have different touch screen drivers?
Click to expand...
Click to collapse
Didn't know CWM had a touch recovery out. Very cool.
Try it, the worst that will happen is you'll have to flash a different version of recovery on top of it. I haven't heard anything about the DHD and Inspire having different touch screen drivers, they're the same device. 4EXT Touch works on the Inspire and I believe the version is a DHD version

homeslice976 said:
Didn't know CWM had a touch recovery out. Very cool.
Try it, the worst that will happen is you'll have to flash a different version of recovery on top of it. I haven't heard anything about the DHD and Inspire having different touch screen drivers, they're the same device. 4EXT Touch works on the Inspire and I believe the version is a DHD version
Click to expand...
Click to collapse
We have different screens (atmel vs synaptics). When 4ext touch came out their was a brief moment where touch accuracy was an issue compared to our dhd brothers.
Same thing occurred with the ice devoloment

marsdta said:
We have different screens (atmel vs synaptics). When 4ext touch came out their was a brief moment where touch accuracy was an issue compared to our dhd brothers.
Same thing occurred with the ice devoloment
Click to expand...
Click to collapse
ah...guess I didn't stay up on those issues well enough

So, I flashed it, and I can confirm that it works. However, compared to 4Ext Touch, 4Ext takes the cake.

Joshp406 said:
So, I flashed it, and I can confirm that it works. However, compared to 4Ext Touch, 4Ext takes the cake.
Click to expand...
Click to collapse
I would hold judgement on a comparison for now. From what I understand, the CWM touch is still in beta. I'm sure it will improve when the "official" version is done.

marsdta said:
We have different screens (atmel vs synaptics). When 4ext touch came out their was a brief moment where touch accuracy was an issue compared to our dhd brothers.
Same thing occurred with the ice devoloment
Click to expand...
Click to collapse
I have actually had the opportunity to replace digitizers in a A9191, Inspire A9192, and a Telus Desire HD A9192. All 3 models had synaptics digitizers and were replaced with the same. I have heard that the atmel digitizer was found in A9191's and A9192's but I have yet to see one.
Edit: Ironic here. My personal Telus Desire HD has not had the digitizer replaced. But I just checked it with Elixir and I would be damned to see that it is reported as having an atmel touchscreen. Now I want to take it apart to verify for myself. lol

Touch works amazingly for me. No issues.

Anyone getting server issues right now while trying to download?

Joshp406 said:
So, I flashed it, and I can confirm that it works. However, compared to 4Ext Touch, 4Ext takes the cake.
Click to expand...
Click to collapse
4EXT FTW
I got your 10 char right here
abso Bacon Mod

esiedlecki said:
Touch works amazingly for me. No issues.
Click to expand...
Click to collapse
I'm using it right now...I love not having to volume mash.
Sent from my Inspire 4G using xda premium

Works like a charm for me.

Used it enough to know that it's stable and functional. Not currently, but have recently...
Sent from my Inspire 4G using XDA App

how do you flash it? when i tried fastboot flash recovery touchimage.img it failed

kormsbee said:
how do you flash it? when i tried fastboot flash recovery touchimage.img it failed
Click to expand...
Click to collapse
To install it that way you need eng S-OFF. You need to flash a PD98IMG.zip, but make sure you have the .txt file as well. In the Hack Kit folder is an example of recovery.
Sent from my Inspire 4G using XDA App

alternative method for 4EXT recovery: download 4EXT Recovery Control from the market. it will download and install the touch recovery for you in the same way that ROM Manager downloads and flashes the CWM recoveries. Plus it'll let you set up your entire flashing process without ever having to go into recovery. it's quite nice actually. set it all up, execute it and let 4ext do its thing.
word of advice though: if you use any of the format/superwipe or anything methods that are selectable before installing your zip(s), it does those BEFORE flashing anything. so if you're like me and use ROM Cleaner to backup all your apps, don't use 4EXT's super wipe method, use one of the actual superwipe scripts. you might have to go into the updater-script and delete a line that makes it reboot the phone though so the install process doesn't get interrupted

I flashed the newest version of CWM touch but am getting an error when backing up. I am not for sure what is going on but I guess I will go back to 4ext for the time being.

I've been using it for a couple weeks, its the cats pajamas
Sent from Inspire using can & string ver .2a

I realize that this is kind of a Necro-bump, but this is relevant. Here's a link to d/l CWM touch 5.8.1.5 already rolled into a PD98IMG.zip
http://dl.dropbox.com/u/8241559/CWM Recovery Touch/PD98IMG.zip
MD5: E19E4461F73AB6449760D70AE906341D
Props to adikavoor on the DHD boards.
PS, If I missed this in a sticky, sorry..... if not, please add to a sticky. Thanks

ST3ALTHPSYCH0 said:
I realize that this is kind of a Necro-bump, but this is relevant. Here's a link to d/l CWM touch 5.8.1.5 already rolled into a PD98IMG.zip
http://dl.dropbox.com/u/8241559/CWM Recovery Touch/PD98IMG.zip
MD5: E19E4461F73AB6449760D70AE906341D
Props to adikavoor on the DHD boards.
PS, If I missed this in a sticky, sorry..... if not, please add to a sticky. Thanks
Click to expand...
Click to collapse
Most people dont use CWM in the roms as it has been known to cause issues when flashing roms and mods. But thanks for the link.

[Q] Connecting to AC charger while the phone is OFF boots into CWM recovery

so the phone works fine but i cannot charge with it off as regardless or rom while it is off if i plug the charger in it boots into recovery mode. IF my battery was to completely drain i would'nt be able to charge it with out a standalone battery charger
due to this fact i'm looking for solutions to the actual problem not someone to say don't let it die. it probably never will as i would just switch it off but still i'd like to be able to turn my phone off and charge it if i wanted to
Has anyone else experienced this or heard about this and have actual useful info, i don't need to be told flash a new rom etc i'm always flashing roms. It's not an urgent issue i'd just like to know seeing as i seem to be one of the only people experiencing this

I think you have an old recovery that doesn't allow charging.
Update to latest 4EXT.

Jack_R1 said:
I think you have an old recovery that doesn't allow charging.
Update to latest 4EXT.
Click to expand...
Click to collapse
thanks looking into this now, when i install the 4ext recovery updater is that going to replace CWM or Rom manager premium :S
dw i found the answer *EDIT*

switching to 4ext solved it thanks again !

So this is a recovery problem? I also have this but I don't wanna change recovery.
Sent from my HTC Desire S

MarlX said:
So this is a recovery problem? I also have this but I don't wanna change recovery.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Then you stay with your problem.
Yes, obviously it's a recovery problem. Recovery that supports charging was done starting CWM 5.0.0.6 (hack) and 5.0.0.8 or so (official). The latest CWM should support charging too. Personally, I fail to see even one smallest reason not to upgrade recovery.

MarlX said:
So this is a recovery problem? I also have this but I don't wanna change recovery.
Sent from my HTC Desire S
Click to expand...
Click to collapse
i had the latest cwm touch and couldn't charge, 4ext is alot better though, the free version has nearly every rom manager premium feature i'd switch if i was you, well i did switch lol

Okay, thanks. I'm not changing ROM often so I guess I can stay with CWM. The only prob that I have is that it boot to recovery while charging (when off) but I also doesn't shut down my phone when charging, so it doesn't matter that much.
GGLDN said:
i had the latest cwm touch and couldn't charge, 4ext is alot better though, the free version has nearly every rom manager premium feature i'd switch if i was you, well i did switch lol
Click to expand...
Click to collapse
Jack_R1 said:
Then you stay with your problem.
Yes, obviously it's a recovery problem. Recovery that supports charging was done starting CWM 5.0.0.6 (hack) and 5.0.0.8 or so (official). The latest CWM should support charging too. Personally, I fail to see even one smallest reason not to upgrade recovery.
Click to expand...
Click to collapse
Sent from my HTC Desire S

You would certainly see multiple benefits from upgrading to 4 ext recovery, especially writhe touch version....even the free version although would recommend that you buy the paid version to support the quality developer
Swyped from my DesireS

Battery life

I bought this phone off ebay and I got two batteries. I am wondering if it is just me butt the seller said the battery was a month old and this thing won't last 3 hours off normal continuous use.and sometimes it just shuts off without giveing me a battery message, of any kind (when im doing something battery intensive)
Also before I knew about the chip issues I flashed and all.I used the method on unlockr.com and when I reached the part to get s off the root.sh wouldn't give me s off so some where in the comments I found a g free script ran it in the terminal emulater in the placer of root.sh and then returned to unlocker and continued to flash with visionary.apk and all is well. Flashed a few roms but im itching to flash like hell as that's, what I'm use to, so is it a case where the chip gets worse everytime I flash or can it go any time? Does it have to go?
I have read the posts and just need a little more clarity.
RUDE COMMENTS ARE NOT WELCOMED
sent from my doomed chip HTC glacier or mytouch 4g

xanda143 said:
I bought this phone off ebay and I got two batteries. I am wondering if it is just me butt the seller said the battery was a month old and this thing won't last 3 hours off normal continuous use.and sometimes it just shuts off without giveing me a battery message, of any kind (when im doing something battery intensive)
Also before I knew about the chip issues I flashed and all.I used the method on unlockr.com and when I reached the part to get s off the root.sh wouldn't give me s off so some where in the comments I found a g free script ran it in the terminal emulater in the placer of root.sh and then returned to unlocker and continued to flash with visionary.apk and all is well. Flashed a few roms but im itching to flash like hell as that's, what I'm use to, so is it a case where the chip gets worse everytime I flash or can it go any time? Does it have to go?
I have read the posts and just need a little more clarity.
RUDE COMMENTS ARE NOT WELCOMED
sent from my doomed chip HTC glacier or mytouch 4g
Click to expand...
Click to collapse
If the chip dies there will be likely be no warning. It will simply fail. Most don't. There are a lot of us with the "bad" eMMC that have flashed hundreds or even thousands of times.
I would flash a new ROM and compare battery life and behavior.

estallings15 said:
If the chip dies there will be likely be no warning. It will simply fail. Most don't. There are a lot of us with the "bad" eMMC that have flashed hundreds or even thousands of times.
I would flash a new ROM and compare battery life and behavior.
Click to expand...
Click to collapse
Ok I'm feeling a but more comfy now.and obviously I won't blame you should something go wrong. Thanks.makes no sense living in fear might as well enjoy it while it lasts
sent from my doomed chip HTC glacier or mytouch 4g

xanda143 said:
Ok I'm feeling a but more comfy now.and obviously I won't blame you should something go wrong. Thanks.makes no sense living in fear might as well enjoy it while it lasts
sent from my doomed chip HTC glacier or mytouch 4g
Click to expand...
Click to collapse
If your on stock battery will probably suck. It did for me
Sent from my HTC myTouch 4g using xda app-developers app

N_otori0us_ said:
If your on stock battery will probably suck. It did for me
Sent from my HTC myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
yeah i notied the huge diffrence when i switched to the viper rom........haveing a little trouble finding a compatible kernel that will give me smartass v2 tho.
quick question does a nandroid backup also backup the kernel that i was on when i made the backup?

crap i made a mistake and flashed a wrong kernel(fusion dragon and now the phone dosnt want to boot into recovery). i think the kernel was for the one S i didnt notice that. Anyway i know androids so am not worried about anything except my emmc chip can anyone give me the fastbood instructions to flash the various things on the glacier or are they the same for all phones also. a kernel that i can flash the will work with this viper rom would be nice.
i was trying fastboot flash zip rom.zip and that fails.
was really trying to avoid haveing to flash a PDM15.img but it as that would erase my ext4 recovery which i figure isnt working because the kernel i flashed was not for the phone and being touch based is messed up. so anyone knoe the fastboot commands to flash a rom in its zip form

xanda143 said:
crap i made a mistake and flashed a wrong kernel(fusion dragon and now the phone dosnt want to boot into recovery). i think the kernel was for the one S i didnt notice that. Anyway i know androids so am not worried about anything except my emmc chip can anyone give me the fastbood instructions to flash the various things on the glacier or are they the same for all phones also. a kernel that i can flash the will work with this viper rom would be nice.
i was trying fastboot flash zip rom.zip and that fails.
was really trying to avoid haveing to flash a PDM15.img but it as that would erase my ext4 recovery which i figure isnt working because the kernel i flashed was not for the phone and being touch based is messed up. so anyone knoe the fastboot commands to flash a rom in its zip form
Click to expand...
Click to collapse
Download the 4ext recovery image and
fastboot flash recovery recovery.img
Then boot into recovery and try flashing the zips. If you can't find the recovery.img, cwm images are available. You can easily switch back to 4ext later.

estallings15 said:
Download the 4ext recovery image and
fastboot flash recovery recovery.img
Then boot into recovery and try flashing the zips. If you can't find the recovery.img, cwm images are available. You can easily switch back to 4ext later.
Click to expand...
Click to collapse
i already have fastboot flash zip PD5IMG.zip and it worked ok and gave me back clockwork and official sesnse but should flashing an incompatible kernel damaged my recovery? seems flawedish seeing as i always saw recovery mode as my safe heaven. being its a touch recovery i can understand tho. if i had not flashed a eng bootloader i probly would have been screwed now. well lesson learned any info on a kernel that can work with the viper rom android 4.04 sense?

xanda143 said:
i already have fastboot flash zip PD5IMG.zip and it worked ok and gave me back clockwork and official sesnse but should flashing an incompatible kernel damaged my recovery? seems flawedish seeing as i always saw recovery mode as my safe heaven. being its a touch recovery i can understand tho. if i had not flashed a eng bootloader i probly would have been screwed now. well lesson learned any info on a kernel that can work with the viper rom android 4.04 sense?
Click to expand...
Click to collapse
Not sure about the kernel. I can tell you that different devices have different partition setups. The bootloader, system, recovery, etc. don't reside on the same partitions on every device. In fact, doing what you did can cause a hard brick on many devices.

what kernal did you use?

kkm323 said:
what kernal did you use?
Click to expand...
Click to collapse
The kernel wasn't for this phone so he got messed.
Sent from my myTouch 4g using xda app-developers app