Develop Bugs

Touchflo 3d not autolaunching after reset at times.

Is anyone else having the problem where after a soft reset(or a manual shutdown/restart) touchflo3d doesn't autostart?
It happens to me about 50% of the times I reset, but I jus thave to switch it off again and on again and usually it works fine.

Totally different, but I have this sometimes with Touch Flo 2D on my TyTn II. I usually get it if I've installed to much, It always launches if I haven't got the Micro SD card in though.

I've had this happening to me since I got it, and after a few hard resets it still happens... Seemingly at an increasing frequency too.

Yup, I'm experiencing the same problem.
It's really annoying, and more people are having this issue.
There's already a thread about this.
What works for me most of the time is this:
- Disable TF3D in settings.
- Soft reset device with power button
- Enable TF3D again
- Sometimes TF3D starts now, but if not reset again.
I can't wait for a more stable and fast cooked rom
Hope this helps

Oh Sorry, I couldn't find the other thread. I just keep resetting and hopee it randomly decides to starts. Love this phone, just a few things that really annoy me
The inability to find a way to make it autolock(not standby) after X seconds for example. If anyone can help with that, I'd greatly appreciate it.

aiaob said:
Oh Sorry, I couldn't find the other thread. I just keep resetting and hopee it randomly decides to starts. Love this phone, just a few things that really annoy me
The inability to find a way to make it autolock(not standby) after X seconds for example. If anyone can help with that, I'd greatly appreciate it.
Click to expand...
Click to collapse
DId you install any apps?
These kind of problems are mostly caused when 2 programs interfere with eachother. Teh reason why one time it does start up and the other time it doesn't is the sequence of programs starting up. Most of the time touch flow 3d will start later (because it's so big)

i have had this happen a couple of times as well.

quarintus said:
DId you install any apps?
These kind of problems are mostly caused when 2 programs interfere with eachother. Teh reason why one time it does start up and the other time it doesn't is the sequence of programs starting up. Most of the time touch flow 3d will start later (because it's so big)
Click to expand...
Click to collapse
I doubt it's caused by that. I've hard reset it installed core and tomtoma nd had it happen..
and I'm sure it's not just slow to start up, I've tried making calls and simply leaving it for 10 minutes and it still doesnt start up.

It only started haooening to me after I instaled software.
I guess the best thing to do right now, is to install all software with touchflo disabled, then reboot completly the device to finalize the instaltion, and then reboot it again. Now you can reactivate Touchflo again.
This "trick" has worked perfectly on my Pro 2
HastaSSSS

disable startup
Many programs that you install will leave a startup file in the windows\startup directory. Try cutting and pasting them to some temporary directory. I did that with poutlook and slovoed and the problem has gone away for me, without in any way impairing my calendar/contacts or slovoed functioning.

I got the same problem too.. soft resetting a few times do it or disable/re-enable on Personal-Today Items screen
Kinda annoying

Same problem here. Spoke to HTC today and tol them there were more people having this problem. Mine is so serious that it won't start at all! HTC says I was the first and ONLY one in the world with this problem. They told me that if there were more people having this issue they should CALL HTC. It's free to call them... please do so in finding a solution!
Thanks!

I am suffering under the same issue! It is really annoying! HTC should immediately sovle this problem!

Sounds a bit like my thread here: http://forum.xda-developers.com/showthread.php?p=3950507

I copied manila.exe from windows to my start-up folder, now it works fine.

yeah i have the same problem its really annoying. it works about 90% of the time now when i copied the manilla.exe to start up folder. before that i tried to put the phone in airplane mode before booting but that worked like half of the time.

Schijthoos said:
I copied manila.exe from windows to my start-up folder, now it works fine.
Click to expand...
Click to collapse
Does the time on the tf3d homescreen update ok when you use the manila.exe shortcut?

touch flor not loading
My phone is hanging again. I can't get it to load Touch Flo 3D. I get this message that it's trying to activate handsfree network and then it says connected and reboots and goes through the same thing 2 or 3 times. I hard reset back in Dec cause of this and then the same thing happened again about a month ago and out of the blue it loaded touch flo and fixed itself.
But this time it's been a couple days and my phone is so slow it's crazy. It's been trying to remove one program for 20 minutes. I thought removing a few programs might help instead of doing another hard reset but it looks like i'm gonna have to do one more.. I haven't added anything new lately. And I even got a message saying your phone can not boot up because of a program from an untrusted source or something else and it wants me to hard reset. It says press volume up to reset or any key to continue and then it goes to that hands activation screen.
Iv'e tried enableing and disabling bluetooth. Sprint store said I have a bad phone cause of that hands free actication message I keep getting and they want to order me aother phone but it's going to be a refurb so I guess i'll hard reset.. Something is causeing it to hang and not load and I don't know what it is.. But I came here and I tired puttingmy phone in airplane mode and rebooted nothng. I have unchecked and checked touch flo and rebooted..
But I went to windows and saw manilla.exe cause you guys said copy it to start up and I clicked on it and I saw my background and clock again but I don't think Touch Flo fully loaded and my task manager wasn't at the top and I ran clean ram cause it was still slow and it said it freed up 32mb but then my screen went black again. I put it in airplane mode once more and took out the battery. But when I never pasted the manila to start up should I do that? I just clicked on it and saw where my clock and background were back but my clock was off by like 15-20 minutes.. I'm sure I'll probablyt have to hard reset but wanted to ask around a couple more times before doing one.. Rose

I was sitting in my den and my friend said he texted me but I didn't get it. I went to check my phone and it seemed ok but no text. I then went to make a phone call and it hung. I went to turn it to airplane mode and it froze. When I restarted it, now I get the black screen with the top and bottom menu bar but no touchflo 3d loading. I get some weird hands free activation message and then it says successful and reboots my phone. When the phone starts back up it is in the same condition without touchflo 3d and the reboot loop continues unless I click cancel.
If I run manilla.exe it will boot up and my today screen will come back but it is SLOW and it doesn't seem to have completely loaded.
WTF happened and how do I fix this?

Same thing happened to me.. Touchflo wouldn't load phone was so slow hands free message kept coming and saying connected and rebooting. I did a hard reset and was good for a couple months then out of the blue on day it did it again. I turned off phone and left battery off overnight and just got lucky and the next day as I was getting in my car it came back on.
But then a few weeks later it did it again and I took it to a Sprint store. I was told that the handsfree activation is something that only happens once when you 1st get a new phone and they said my phone was defective. They were going to order me another one but it was going to be refurbed so I never picked up and just dealt with a hard reset once again. Don't know what causes this but I've had my phone reset for over a week and I just now tonight started putting apps back on cause I was afraid ut had to do with something I installed I really don't know what causes it.. But my touchflo wouldn't load at all compeltely black screen no today screen at all and boy was my phone slow. I went to windows and clicked on manilla.exe also and saw my today screen but it was still slow and not completely loading up to touchflo like you said. And then I read about putting it in airplane mode turning off BT nothing worked for me this last time so I did a heard reset again..
Maybe someone else knows what causes this but I'm leary and am not going to put everything back on my phone that was on there but I've put most everything back.. Sorry I wasn't much help but same thing for me hands free siad connected and would reboot and over and over.. I kind of want an Android phone now and I don't think Sprint should of offered me a refurb when I just bought this in Sept and it's an expensive phone. But oh well things happen.. Good Luck!
killerz298 said:
I was sitting in my den and my friend said he texted me but I didn't get it. I went to check my phone and it seemed ok but no text. I then went to make a phone call and it hung. I went to turn it to airplane mode and it froze. When I restarted it, now I get the black screen with the top and bottom menu bar but no touchflo 3d loading. I get some weird hands free activation message and then it says successful and reboots my phone. When the phone starts back up it is in the same condition without touchflo 3d and the reboot loop continues unless I click cancel.
If I run manilla.exe it will boot up and my today screen will come back but it is SLOW and it doesn't seem to have completely loaded.
WTF happened and how do I fix this?
Click to expand...
Click to collapse

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.

You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.

Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin

Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.

Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.

Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.

I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.

"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.

[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.

Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.

[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.

15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.

salvaging my internal storage....

so ive had my s2 for a couple years, i wound up dropping it the other day, threw it into a constant reboot.. seemed like a power button issue. i tinkered with that a little but little results. i was able to get it to boot up and did a twrp backup of everything. but since then ive been unable to get it to run for anything more then that, IF even that long. a factory reset aswell locks up just after app optimization. its like.... it get to a certain point on the phone and locks up.. i was able to pull my misco-sd out and get the files off it. but i'd like to get to my internal storage as thats where my camera was saving eveything too.. when i switched roms earlier this summer it must have used different save to locations.. its my photos are what im after.. booting into recovery i can see all my files, plugging in and trying to mount yields no results.. im going to try on my laptop aswell but on my pc its doing nothing.. Im curious if anyone has had the similar situation , near that, or better luck with CWM.. any other info or insight would be awesome.. much thanks..

[Q] S II t989 won't quite load but not quite a boot loop

I need help figuring out exactly what's wrong with my phone as it has very weird symptoms that seem one-of-a-kind to any problems I've been able to find already posted. Basically everytime I turn on my phone it gets stuck on the load screen with the bar near completion but it won't actually boot and it doesn't loop - to make matters more peculiar once I pop out the battery and try again then the Android guy blasts off and my phone turns on. It always takes me a second try for it to boot but it does so without fail - usually. The rare incidences that I can't get my phone to boot then I can easily get into twrp & after wiping both caches/factory reset it will boot immediately after on the 'first try'. Even worse is that my battery power has been extremely reduced to maybe 4-5hrs regardless of how much I use my phone and it will turn off unexpectedly no matter how much power is left.
the only thing I can think of is that it started soon after I put an external sd card in and tbh I don't quite understand how to take advantage of my extra 16gb yet and the fact that I'm bound to wipe my phone again has kept me from exploring my options
please if anyone can help me save my phone and maybe even link to a thread explaining how to use an external sd card properly. I got confused awhile back trying to understand partitioning and Idk which apps have to stay internal or how to retrieve ones on my sd.
Oh, one last thing, I started using a wall charger for my Samsung batteries and now I can't charge my phone thru the usb anymore without it 'disconnecting' immediately
I was using Paranoid Android before my troubles started but I'm back on stock 4.1.2. I've never posted on xda before so hopefully I did so properly and provided enough background information. thank you in advance to any genius out there who can get me my phone back!!!

[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen

[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"

Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart

strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,

I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart