Develop Bugs

[Q] Does your phone require multiple battery pulls to boot up?

Ever since I flashed LeeDroid 1.8b, I've been having this odd problem. I've wiped the phone since and have flashed Open Desire 3.1.0 and I love it but I'm terrified to reboot my phone.
The phone will boot and freeze at the HTC white screen. This happens even if I try to boot into Recovery, (I can hold down vol+down and power button) but as soon as I select Recovery, it will freeze there at the HTC screen.
The only solution I have is to pull the battery and try again. It will do it around 2 - 3 times before it finally boots into Clockwork Recovery Mod SLCD or boot into Open Desire if I don't boot into recovery. This is the same if I decide to REBOOT the phone or power down and boot up.
This problem never happened when I originally flashed Cyanogen. I'm thinking there's still some files or something left that causes this freezing.. I also did a wipe and delete cache before flashing a new rom.
Does anyone else have this problem or help me sort it out?
Edit: Ah shoot.. wrong forum My bad..

no one?

Although Lee newer acknowledged it, I think it has to do with his ROM. I experienced the same issue while running 1.8b, with 1.8c I haven't rebooted by now, but still I have experienced this only after switching to his ROM and I noticed I am not alone on the ROM thread (other people are complaining too about getting stuck at the bootscreen).
I have changed many ROMs (generic 2.1, generic 2.2, pays, adamg ROM...) and never had such an issue, that is why I think it has to do something with lee's ROM.
If you have OpenDesire I would suggest to reboot it just to see how it will go.

Thanks for your response man! The problem is that I've wiped and everything and flashed Open Desire and I'm still experiencing the issue. Is there another way I can completely delete/format any traces of any previous ROM? I believe there's still some sort of remnants of his files left that are causing this!
THanks,
JD

A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.

TheLastOne said:
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
Click to expand...
Click to collapse
I will definitely try that.. do you ever have problems booting though? I freeze on the HTC screen during boot up as well and have to do 2 - 3 battery pulls before it finally decides to boot!

I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?

I have, but the only wipe I perform is the one in the Clockwork Recovery. Also deleted the cache, but never have deleted or wiped dalvik cache?
I will try this later today and see what happens.. thanks!
TheLastOne said:
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
Click to expand...
Click to collapse

Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.

Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App

Tawm said:
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Click to expand...
Click to collapse
I believe it was an issue with 1.8b..
LeeDroid said:
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hmm.. anyway to confirm this? It's a brand new device, barely two weeks old and never had this issue until I flashed 1.8b.. I'm going to try to wipe it completely and go from there, hopefully that solves the issue.
What's a nand?

Hi Quazis,
I have had a very similar problem with my Telstra desire after rooting and installing a Lee based rom called NexTSense. After that I installed Open Desire and experienced the same problems.
I am just now re-rooting my phone and going to install Pinky.
Just out of interest are you running on the 850mhz Rogers network? If so have you updated to the latest radios (5.09.20 I think?)? Telstra runs off this frequency also and I think it may have something to do with incompatible radios. -- Can anyone confirm this?
If this is the case maybe try Open Desire without updating the radios?

Hey,
We got the A8182 version of the Desire which has 850/1900 (I believe), so both bands that run on 3G.
Before I flashed LeeDroid, I had updated the radio (.20) and was on Cyanogen nightly build. I had no booting problems with that ROM, but I wanted something a little more stable. I modded it as well and the phone booted up no problem, also into recovery.
Once I flashed LeeDroid, that's when my problems arose. I only wiped/formated data and the cache.. I never formated that dalvik cache. I will wait until Open Desire 3.2.0 releases today and try that a full wipe/format.
Another member said he doesn't touch anything on the phone when he boots into recovery until the phone does the SD card check.. I tried it once and it went into recovery with no issues so maybe pressing buttons before the SD check does something??

I don't, but I did a full flash, and used my separate test sd card.

plasmafire said:
I don't, but I did a full flash, and used my separate test sd card.
Click to expand...
Click to collapse
I'm going to do this.. thankfully I have't customized my phone a lot so I'm going to format both the FAT32 and EXT3 partitions and full wipe.. to do a full wipe.. there's only data/factory, cache, davlik cache and battery stats correct? If I wipe those 4 items in Clockwork, that's considered a full wipe?
JD

Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.

I don't have this issue with the same ROM as you.
-----------------------------------
- Sent via my HTC Desire -

Yes, not everyone has that problem (in that case we wouldn't need to talk about it - we would KNOW it). Just some people have this issue with that ROM. I would say 5% of the people have the bootloop problem, and 10% of the people have longer-than-average the bootscreen.
Still, it worths taking a look since 3-4 people from 10 participants on this thread say they have this problem with -this- ROM.
My 2 cents.

ljesh said:
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
Click to expand...
Click to collapse
Why won't a full flash help? I don't have LeeDroid anymore, I had it for about 10 minutes because I didn't like it. I've since gone to Open Desire and the issue still persisted.. but it never happened when I had Cyanogen installed.
I'm scared to re-root because it requires a reboot and sometimes the HTC screen never goes away.. lol

hey there, its intresting to see that you have the same problem as me,
http://forum.xda-developers.com/showthread.php?t=755835&highlight=Recovery+Issue
the people who are saying they dont have a problem, i'd like to know what recovery you are using?
and what hboot you orignally came from, i.e. do you have a SLCD screen? and how did you root?
because it is now becoming obvious that leedroid rom is causing this issue as a lot of people are having problems.
during the weekend i will try flash the RUU for WWE with the hboot 0.83 included (using gold card)
and start from scratch and flash another.
no disprespect to the developer of leedroid, his work is good. just a lot of people on hboot 0.83 with the SLCD screen have issues.

[Q] T-Mobile G2 Bootloop

T-Mobile G2 Bootloop
I have a T-Mobile G2 which is bootlooping on CM7 and Virtuous GLite 1.0.1. I have been running CM7 without problems since it was released. The bootloop started during the night without any prior symptoms. I have searched the xda and other sites extensively for days and tried so many things to fix this, some of which I was unsure about, but figured 'what the hey' since I had such limited success reflashing roms, clearing data, dalvik cache, etc...
Here is some information:
If I immediately put the phone in airplane mode upon bootup while running CM 7.03 it will not go into bootloop. I can use it indefinitely in this state (it seems) but there is only so much fun you can have in airplane mode...
With CM7.03 installed, here is the info from my 'about phone' section:
Model: HTC Vision, Android Version: 2.3.3, Baseband Version: 12.28b.60.140eU_26.03.02.26_M, Kernel Version: 2.6.32.40-cyanogenmod [email protected] #1, Mod Version: CyanogenMod-7.0.3-vision, Build Number: GRI40
I have Rom Manager v4.2.0.2
-----
Some other information:
I am, however, able to run another mod, Stock w/root (http://forum.xda-developers.com/showthread.php?t=836042) which I was able to flash, along with pershoot's kernel (http://forum.xda-developers.com/showthread.php?t=847672). When I run this mod I am not able to activate WiFi. I click to enable it and after a few seconds I get an error and it turns itself off.
Interesting to note- the first boot-up after flashing CM7 I get about 20-30 seconds before it starts bootlooping. During this time I tried to quickly activate WiFi and it errored out the same way is it did running the "Stock w/root" mod listed above.
This made me think (in my limited knowledge) that it could be related to a radio issue... so I tried to flash a couple different radios claiming to be for the G2/desire. No luck there.
-------
I am able to access recovery mode, flash roms, restore roms, etc...
-------
The bottom line for me, I want to run CM7... I know it works(ed) on my phone. How many layers do I have to strip away to get to the point that whatever bad thing is causing my phone to do this with multiple roms is gone?
Rom? Kernel? Radio? what else is there to fix? Any suggestions on where I go from here? What about the no WiFi issue?
I have already searched the forums as I stated, so linking the first 'G2 bootlooping solved' thread you can find probably wont help me. Maybe understanding more about what could be causing this so I can have a direction to persue this further would be most helpful.
Thanks very much!

Did you wipe your phone before applying CM7?

re: did you wipe your phone
blackknightavalon said:
Did you wipe your phone before applying CM7?
Click to expand...
Click to collapse
Yes- in recovery mode I performed a wipe, then cleared cache and dalvik cache before flashing.
---------
Also, to add more info to the original bit of information I shared- last night I flashed CM6 without any bootlooping issues, but the WiFi problem is still there.
Is it possible to set a radio image to read only so that a recovery wipe/dalvik cache clear will not have permission to clear it? If so, maybe when I flashed a radio before I set it that way without knowing (I honestly can't remember, but I do know that at one point a guide had me flashing something using fastboot and setting chmod something-or-other).
^ I guess I can just press Vol down and Power to check my radio version to see what one I am running and check if it is compatible with CM7.
Any suggestions?

Crazy coincidence.. This morning at 7:45 am my wifes G2 started boot looping. I know it was 7:45, because it was about the time the alarm was supposed to go off.
Hers appears to be a bit worse off, as while I can get into hboot, it won't let me into recovery (and it boot loops before i see cyanogen logo).
I curious to see if anyone else is seeing this, and what the fix might be. I haven't really tried much except getting into recovery since I'm cautious to screw it up further.
Anyone have any ideas?

I now firmly hold the hypothesis that my individual bootloop problem is being caused by my wifi adapter. I am able to flash any rom that doesn't use a kernel based on CM7. On every rom that works ('Stock w/root', Cyanogen6, GingerSense) the WiFi is the only problem. On CM7 and another rom I flashed which was based on the CM7 kernel it bootloops.
So, I am convinced that something in the CM7 kernel polls my wifi adapter when it starts up, figures out that it is borked and then craps out and goes into a bootloop. To further reinforce this idea, as I mentioned in an earlier post- I can boot into CM7 based roms while in airplane mode and use them indefinitely that way. As soon as airplane mode is disabled it goes bonkers.
I'm done t/s this issue for my problem, going to replace the device.

sgshanaf said:
...I can get into hboot, it won't let me into recovery (and it boot loops before i see cyanogen logo).
Click to expand...
Click to collapse
What happens when you select recovery from hboot? If nothing, what about trying a factory reset from hboot? I neither work you should have access to fastboot, but I understand your hesitation if that is the only option you have. Some things I have come across in my searches that could cause bootloops were sim cards, sd cards, and a mess of other things. You can try pulling out the two of those one at a time and doing a normal startup to see if anything changes. Let me know how far you get with the HBoot options and I will try and suggest some other things based on that.

Thanks for responding. I spent a lot of time reading all the different posts I could find with similar issues and decided to take the plunge on this solution:
http://forum.xda-developers.com/showthread.php?t=912399&page=4
and it worked for me.
**UPDATE: below I was having a problem not being able to instal a rom. For whatever reason CM 6.1.1 worked fine. I was then able to go into rom manager and update that way to CM 7.03, and that time it worked. No clue what happened, maybe a bad rom .zip, maybe my SD card is getting flakey. /Shrug
The Phone is booting into that rom fine. Interestingly, while the phone now has eng hboot and working CWM recovery (in addition to still reporting S-OFF), I can't get past the "HTC" splashscreen after installing cyanogen 7 update.zip for the phone. GAPPS or not. I am doing the cache and data wipes
I can get back into recovery fine, but it's just not taking the rom install.
Scott
greenguitar28 said:
What happens when you select recovery from hboot? If nothing, what about trying a factory reset from hboot? I neither work you should have access to fastboot, but I understand your hesitation if that is the only option you have. Some things I have come across in my searches that could cause bootloops were sim cards, sd cards, and a mess of other things. You can try pulling out the two of those one at a time and doing a normal startup to see if anything changes. Let me know how far you get with the HBoot options and I will try and suggest some other things based on that.
Click to expand...
Click to collapse

[Q] Battery overheating, causing reboot

Okay, so I'm brand new to this board, so I appreciate any input you can give. I have an HTC Droid Incredible, have had it over a year. Have had the phone replaced 3 times due to excessive rebooting.
I have the OEM HTC extended battery, and have had numerous issues on the battery overheating and rebooting the phone. It seems to happen mostly when using the GPS in the car. Its also happened while excessively texting.
After having the phone replaced three times, I decided to root, and am now on CM7. It was working fine for a couple weeks, then rebooted again. I then took the phone to the Verizon store, and they replaced the battery. The phone still tends to reboot!
Please give me any advice you guys might have. I'm at my wits end here!
Again, Dinc, rooted, on GB, and using CM7.
Thanks!

Undervolt. Use incredikernel and incredicontrol. Drop the minium 25 or 50 and do the same to the Max.
-My life is a shooting range, people never change-

Thanks so much, but I have no idea what you're talking about. I downloaded Incredikernel, and it bricked my phone....Any other ideas?

ari-nj said:
Thanks so much, but I have no idea what you're talking about. I downloaded Incredikernel, and it bricked my phone....Any other ideas?
Click to expand...
Click to collapse
It bricked your phone? Can you give some more details at to what happened?

It just came back on the "HTC Incredible" white screen and did nothing. Had to reboot, and restore.

Well at least your phone isn't "Bricked". If it was your phone would not work period. How long did you let the phone sit? I'm running CM and I have Chad's latest Incredikernel and it runs like a champ! I'm assuming you are running the latest AOSP kernel correct?

I have no idea what an AOSP Kernel is, so I highly doubt I am. Last night, I had my phone in my hand for a few minutes, when to download something from the App Market, and it kept resetting. Do you think I might need to uninstall and re-install the App Market? I'm at a loss here...

CM is an AOSP Rom and needs an AOSP Kernel to run not the sense kernel. If u go to the downloads section at incredikernel.com you will see the AOSP Kernels. Download the latest version and flash it when you reboot just set the phone down and be patient. As far as the app that you installed, what app was it? You can uninstall the app and see if that fixes ur reboots
Sent from my Droid Incredible

I downloaded the kernel, and when I went to flash it from the sd card, I still get the same thing. The white "htc Incredible" screen comes on and nothing else. I've let it run for 10 minutes, then I have to pull the battery and the restore to my last backup. Am I doing something wrong?
Thanks again for your patience, I'm just a little retarded when it comes to this stuff...Btw, I like your sig, I actually sell Jager, so I truly appreciate it!

I just wanted to bump this back up to the top to see if anyone else has any ideas. I did a restore to when I first rooted the phone, and everything seemed fine. However, last night, I was watching a couple Youtube videos, and in about 5 minutes the phone reset.
I have tried to flash kernels, but cannot figure that out, so I'm still using the stock kernel from CM7. PLEASE help, I'm beyond clueless, and am about to throw this phone out the window!
Thanks in advance!

If you are flashing the latest AOSP (Gingerbread) Incredikernel it should work. You can try wiping your dalvik cache in CWM and then flash the kernel again. I have read in many posts that people have waited up 15 minutes after flashing a kernel for there phone to boot. Try that and be patient.

ok so the reason why incredicontrol didnt work is because the stock kernel doesnt have HVAS. so do this.
download :http://www.incredikernel.com/wp-con...php?id=2.6.38.8-incredikernel-gb-11272011.zip
also can you tell me which hBOOT you are running and what radio you have.
to find out what hBOOT you are running please turn of the phone.
once off hold power and vol -
at the top left of the screen please post all that is there.
for radio go into settings > about phone > Baseband Version
please post this info.
boot into CWM do not use rom manager to install.
flash zip above.
reboot and wait. it should take up to 2 min for the phone to rebuild dalvik and boot into the os.
then install incredibcontrol from market.
go to the HVAS tab and lower min by 25 and max by 25.
reboot.
report back please
(note the instructions above will only work for CM7.)

Wow, thanks for all that info! I'm working on installing that kernel now, but before I do anything, I am on Baseband version 2.15.00.07.28
It also says:
Incrediblec XC Ship S-Off
HBOOT-0.92.0000
Mircrop-0417
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010,18:06:51
I will report back later on with my progress.
Thanks again!

I'm trying to reboot into hboot, but now I cannot get into CWM...I have no clue what's going on! HELP!

ari-nj said:
I'm trying to reboot into hboot, but now I cannot get into CWM...I have no clue what's going on! HELP!
Click to expand...
Click to collapse
What happens when you try to go in recovery (CWM)? Don't freak out, if you can't get into recovery you may just need to reflash it. This can be done with Rom Manager or Hboot.
Also you need to update your radio to a Gingerbread radio if you are using CM7. That is more than likely the reason your phone stays on the HTC screen after you flash the Incredikernel. If you have never updated your radio do some research first or just ask and I'll help you thru it.

I have to research the new radio... I was trying to backup from rom manager, and it still stuck on the white screen. Any suggestions on the new radio? I had no clue that it had to do that as well.
Sent from my ADR6300 using XDA App

ari-nj said:
I have to research the new radio... I was trying to backup from rom manager, and it still stuck on the white screen. Any suggestions on the new radio? I had no clue that it had to do that as well.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Go here http://pvillecomp.com/?page_id=18 and download the 2.15.10.07.07 (Gingerbread) radio. All you need to do is name the file PB31IMG.zip and place it on the root of your SD card, basically not in any folder. Just to be safe make sure you don't have any other PB31IMG files on the root of your SD card. Then go into Hboot (Volume down = Power button), just wait (like 5-10 seconds) and you will see that it will auto load the file. When it is ready it will ask you if you will like to install, accept by pressing the volume up button. Let it do its thing, when its done it'll ask you if you want to reboot, hit the volume up button to say yes. Make sure you have a good charge or leave it plugged in to your charger. After you do this wait and see if the phone boots properly, wait like 10 minutes or so. Let me know how that goes...

I'm at a loss here...I did just what you said, and when I get into Hboot, nothing happens....I really don't know what else to do. Is there any way to un-root the phone, and start from scratch? At this point, I cannot get into CWM, and cannot revert back to a restore, so what are my options?

Is your SD card in FAT32 format? You can check on you pc/laptop, just right click on it go to properties. If it is not in FAT32 format you will need to reformat your SD card. Before you reformat it copy everything from your card and paste it to a folder on your desktop. Then reformat your SD card to FAT32, then paste everything back to your card. This could be why your phone is not loading the PB31IMG file (The radio you are trying flash in Hboot).

Ok, stupid me renamed it .zip, as opposed to not...got the radio on there, but still cannot get it to boot into CWM. I feel I'm making a little progress. However, when I go to into Hboot, it still comes up asking if I want to upgrade the radio...It shows Radio 2-15.10.07.07

Unfixable boot loop... Help?

Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.

Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App

Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened

Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.

Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....

I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA

shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?

Problem with touch of blue 2.2

Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled

Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled

devnulled said:
Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled
Click to expand...
Click to collapse
The 2am reboots are not a phone issue, it is a known issue with the latest ota. I cant believe they would rather give you a new phone than to admit they sent out a messed up ota.
Try fixing permissions and wiping data as you said.
If 2.2 is installed you should not get a nag to update, as its based on the latest ota.

devnulled said:
Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled
Click to expand...
Click to collapse
Vzw backup was removed from the rom as most people dont use it. If you want it back, flash this http://dinc.does-it.net/APKs/VZW_Backup.zip, thru recovery.

Thank you cmlusco,
clearing cache and fixing permissions has fixed it, sorry for saying there was a problem. Verizon almost got back 3 phones (an eris that i was given, my old palm pre plus, and my incredible) at the same time with a certified letter having me cancel my contract 6 months early when the phone started rebooting back around the 4th of july. They replaced it last summer/fall when they rolled out gingerbread and my phone got half of it installed when it locked up and would not finish the update but was enough there to lock it from being fixed by ruu even.
I agree that it was not the phone, I told tech support I had it rooted for different skins and roms and to fix buggy software and they suddenly wanted to send out a new phone under warranty. I think they just wanted to get out a phone that was a little harder to root and get s-off rather than fix what was obviously a software bug issue. the new phone was supposed to be fully updated, but it wasnt installed, was still on the prior OTA and had a helluva time getting it to accept a custom recovery to begin with. Would goto the white HTC screen, then flash once or twice and go black with white bars down each side. took 3x to get it to accept it and ended up having to flash an older version first .92 i think (was 3 weeks ago now).
I will flash the backup software this time as my contacts were all edited on the website. Thank you again for the best rom Ive played with in a long time.
(forgot to add when I asked about the mods, I meant in a stock rooted rom that was similar to the old stock+ in use/appearance, but didnt get a nag screen, not that touch of blue did not have it. sorry for the confusion)
devnulled

Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?

dibmem said:
Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?
Click to expand...
Click to collapse
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.

cmlusco said:
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.
Click to expand...
Click to collapse
Thanks for the reply... I wonder what's doing the damage - The dedicated Gmail isn't on my phone. My wife is running TOB as well with the same symptoms. She runs a lot more apps than I do and we were looking for the ext4 fix when I found TOB.
Maybe it's another app? Let me know if you want a list...
Planning to load your rooted stock this weekend and see how things go.
If, in the meantime, you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.

dibmem said:
Thanks for the reply! I saw your rooted stock build - Most likely will go with that.
I wonder what's doing the damage - I could pull Gmail off for the evening and see if mine is stable. My wife is running TOB as well with the same symptoms. We were looking for the ext4 fix when I found TOB.
If pulling Gmail doesn't work - I'll load your rooted stock and see how things go.
If you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.
Click to expand...
Click to collapse
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.

cmlusco said:
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.
Click to expand...
Click to collapse
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?

dibmem said:
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?
Click to expand...
Click to collapse
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.

cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)

dibmem said:
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)
Click to expand...
Click to collapse
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.

cmlusco said:
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.
Click to expand...
Click to collapse
Results post: Ended up flashing TOB 1.3, radio 2.15.10.12.20, and CMW 5.0.2.0. Updating the radio via hboot ended up being very easy (as long as I verified md5 beforehand.) Our phones are stable overnight - no reboots. Signal sucks here at home, but seems to be slightly better - hopefully will be better around town. If not, there's plenty of other radio versions to try out.