Develop Bugs

Device strange issue will not stop giving problems!

This is a list of events that I have gone through today. I received a new charger because the old one I had became defective & was charging my phone up & then it would go back down to 0% & then shut off & it would end up in a problem where the phone would not turn on unless I pulled out the battery while the AC was in & then it was able to charge but still it would turn on, on its own to drain the battery when off & this was very frustrating. The charger I have now works but the device acts strange over the last few months doing a task29 & flashing the first ROM after would make that ROM not work & then I had to flash a totally different ROM to make it work. I was using Android & it had died a few times & also I experienced the same thing I did when it would charge up & go back down to 0%. please read below:
I got my new charger today & at 62% of charge I decided to flash to a custom ROM via mem card again well the ROM was a success but when pulling battery out to restart it didnt want to work. So I went to flash again in bootloader by memory card it shut off on me in the middle & restarted into bootloader again & shut off again right away. I did a task29 it worked got it out of bootloader & now the orange led flashes off & on when its off & now ive gotten that to stop. What exactly is wrong with this device?
it was @ 73% and finally setup a ROM NRGY however it ended up shutting off on its self & going into a power boot loop constantly restarting until that ROM can no longer start & now its stuck on the boot screen w/ its info.
I flashed the stock SPL on USB now im going to try to flash the carriers ROM back.
Stock SPL = Successful!
2nd Touch Pro 2 ROM Version Flash = Successful!
Its working for now. Battery is @ 80%
AHH! After charging to 100% idk what it did but when I went into the other room to check out its all possessed.
I have a black screen w/ white text that says:
The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source.
Press Volume Up to reset your device or press any other button to cancel.
This operation will delete all your personal data and restore the device to its factory default settings.
IDK how this happened.
When I hit any key it didnt do anything it was stuck until I did a battery pull. Then I restarted the device it was stuck at the boot screen w/ its red info. It erased the entire ROM. Then I tried to do recover mode & it did nothing. I tried to flash the stock ROM again & no results & then again & still no results. I think its now not accepting the ROM at all since from: in the ROM update utility is blank.
Now it decides to get past the boot screen but then it malfunctions again & restarts itself & it tries to setup a 2nd time then after it does & its on sense home for a couple of mins it reboots twice & now its stuck on the boot screen again.

Things that I can think of.
- Isn't your batterie just broken? You will break your batteries when you deplete them completely. Maybe try a new batterie, because you said that you let it die for a few times. It could be that this is causing your problems.
- Did you flash true usb when you were in the bootloader? Give that a try, because I believe that the customruu performs some sort of checks. Maybe this is nonsens, but you can try it.

The battery was fully charged & it was working better than before.
I reflashed the Stock SPL to flash the carriers ROM back & that worked but at anytime it just rebooted for whatever reason to make it so the ROM was unusable at any time I would reboot it would decide to actually go past it seldom. I experienced that at one point oddly it went into setup n it did it again after a while its just acting strange.

If you're back to stock SPL and stock ROM, can't you just send it back for a warranty replacement ?

IDK how old it is. I bought it brand new from ebay.

Viper Matrix Wireless said:
IDK how old it is. I bought it brand new from ebay.
Click to expand...
Click to collapse
No warranty bro...
You can try but no warranty 9/10 times.
What ROM are you using? I used to have that issue with my betas.
It wld destroy itself after softreset and I would have to reflash.
Try to flash, turn off right after it boots, turn on and see how that works for ya.

Rep had told me I could get it replaced & they know I bought from ebay. But I havent called them on this yet.
It doesnt work. It usually doesnt go past the boot screen. Flashing does nothing to help it. Whenever it feels like it it may have to stay on for a few mins to go into setup but most of the time it will stay there & reboot, reboot, reboot, reboot each time its a different # of times & it will reset itself at anytime. Ive even had bootloader shut off on me & restart itself during flashing its a pain. I had another issue I didnt mention my device on any custom ROM when I had 0.85 olinex SPL the device would just freeze & not respond every time. Now this is a different situation. I am back of SPL 0.87 which is the default. I flashed the entire carrier ROM which 0.79 was rewritten w/ 0.87 & that was successful but its still rebooting & causing fatal problems including the black screen w/ white text.
UPDATE: I just walked into the kitchen. Somehow the device turned on by itself & now its sitting on the sense home screen. I know its not fixed but idk why it would turn itself on.

Moved as not ROM Development.

Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....

I got so frustrated I just got done calling T-Mobile Tech Support & they are going to ship me a replacement.

ultramag69 said:
Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....
Click to expand...
Click to collapse
I thought I would reply to you.
This is what started my problems is when I did a task 29 my device was acting funny afterwards. I did it again about a month later cuz I flashed way too much & it kept getting worse. But Task29 didnt help this time its what caused me to have to flash 2 different ROMs cuz the first one I flash after doesnt work.

I received the battery & it didnt do anything.
I'm still waiting on the replacement to come.

[Q] possible brick need help!!

ok here's the deal,
a friend of mine has a htc desire with a weird rom on it, he asked me to change it to something more "normal".
So i flashed Pays-rom v2.2 a2sd+. it all went fine untill i tried to install apps, i always wend back to the splash screen and then back. so i desided to flash a new radio on it. i flashed radion 32.44.00.32U_5.09.05.30_2 on it and after it went totally fine, rebooted and it was all ok, but when i rebooted it again it refused to start.. i tryed everyting and it simply would not start. i plugged it in the charger and the led didnt turn on.. but after several times of pulling the battery in started anyways, and worked just fine.
I showed it to him, and he wanted to have an overclockable kernel so i downloaded one, through Rom Manager i set it to flash it, and upon reboot it never woke up again.
I tryed to pull the battery several times and still no turning on and still no led on charge . i dont understand, because on my phone (htc hero) i never had sutch problems.
any help would be apreciated.

Do u have access to your recovery menu
If so then load it by
Pulling the battery an putting it again
Thn hold volume down and power
Thn navigate by the arrow keys to recovery and press the power button
Now your in recovery
Mount as usb storage
And put a new rom on the memory card and flash it
That's it
Remember that next time you should do a nandroid backup from the recovery menu everynow and then especially before flashing themes and radios
Sent from my HDfied HTC Desire

Really hope this helped you because when it happened to me i was actually freaked out
Sent from my HDfied HTC Desire

Nope, could not power up at all. But I figured out that if I pull the battery for 2 hours, I could get it to boot. So I reverted everything back to how it was and as long as it does not power off it work thanks anyway
Sent from my HTC Hero using XDA App

MildWild CM-4.6 start up freeze

Hello,
I've installed MildWild CM-4.6 on my HTC Desire and it was running perfectly until yesterday, when I have installed a Camera patch.
Now the phone won't start up (freezes on the first white screen with the green HTC logo).
What should I do to solve this problem?
Thanks a lot!

boot back in to recovery (pull the battery then put it back, vol down+power, select recovery)
then try flashing the original rom.zip straight over the top without wiping anything. you shouldn't lose any data by doing this.
if that doesn't work, you'll probably have to full wipe and flash again.
in future, get into the habit of making a nandroid backup before flashing anything. it avoids situations like this, as you can just a backup if you can't get it to boot. i don't know which camera patch you are referring to, but is it even compatible?

Thanks a lot for your help!
I was missing the "vol down+power" part...
It worked just ok! Had to reinstall de ROM again and the phone come back to life!
The camera patch I used was not the right one, so I guess it caused the crash...
Cheers!

[Q] accidentaly bricked my phone? plz help!

So here's the deal..
So I'm no newb when it comes to flashing roms. my Dinc is my 3rd phone with a custo.m ROM. Well what happened is. I flashed to cm9 kangs from cm7 v13. Well after about a week I was sick of the instability and having to install apps twice just got annoying.. soo... I decided to go back to cm7 but I didn't have it on my sd anymore so I pulled it from my comp and flashed through ROMmanager. Well upon booting it got stuck in a bootloop (which is the first time I've encountered this.) So I took out the battery, and I held down both volume and the power button and the phone vibrated 5 times and the LED went from flashing red to green and the screen stayed black. Now I can't boot into recovery.. nothing. Almost thinking its bricked... is there any way to save this phone?
Thanks for any help u can gived.

XCmaster said:
So here's the deal..
So I'm no newb when it comes to flashing roms. my Dinc is my 3rd phone with a custo.m ROM. Well what happened is. I flashed to cm9 kangs from cm7 v13. Well after about a week I was sick of the instability and having to install apps twice just got annoying.. soo... I decided to go back to cm7 but I didn't have it on my sd anymore so I pulled it from my comp and flashed through ROMmanager. Well upon booting it got stuck in a bootloop (which is the first time I've encountered this.) So I took out the battery, and I held down both volume and the power button and the phone vibrated 5 times and the LED went from flashing red to green and the screen stayed black. Now I can't boot into recovery.. nothing. Almost thinking its bricked... is there any way to save this phone?
Thanks for any help u can gived.
Click to expand...
Click to collapse
If you can access hboot its not bricked. You need to do the five vibes fix herehttp://pvillecomp.com/?page_id=33, if you can get to hboot to use fastboot. If you cant access hboot you are out of luck.

well an update. what i did was pulled the battery and held down the power button for 10 seconds, then put in the battery and plugged the charger in. and it forced it back into the bootloop. i was then able to access hboot and try and reinstall. well both cm7 and cm9 both started the bootloop. so i went through and factory reset the phone and formatted the sd. and also wiped the dalvik and cache. also formatted system/data/cache, and reinstalled cm7 and it started force closing EVERYTHING. so i completely wiped the phone and reinstalled cm9 and everythijg worked fine, so i went back to cm7 and now everything is working as before. didnt have to enter code in the terminal emulator blahblah.. just an easy fix for me dont think itll work for most but did here so its worth a try i guess.

Z-Play boot loop, even after doing a factory reset

So I've had my Play for a while now, and it's been a lovely phone, no issues (until now), great device.
I was laid in bed last night and as I was feeling poorly I just wanted my phone off completely so I shut it down (power button -> Power Off). This morning I woke up (feeling better, thanks for asking) and turned my phone back on (held power button until the screen came on) and went about my morning routine. I came back to my phone a good 10 or so minutes later and noticed it was still booting, which I thought was strange, so I watched it and it would start loading and then turn off again and start booting up again. I did a bit of Googling and found very little (which is not surprising for a new phone) but I tried some of the X solutions, such as going into recovery mode (power+vol down) and clearing the cache (made no difference) and doing a factory reset (made no difference, soo glad I have backups). One of the things I noticed in the kernel logs is that the date is 01-01-1970: epoch. I have posted a 5 minute video of it booting, and scrolling through the logs on YouTube, but as a new user cannot post a link to it, the video's ID is xoCfPCB6Gmk
Any idea on how I might fix this, or is it a warranty job?

My advice would be go to the ROM section of these forums. Find the thread about the stock firmware. Then first find your region and download the stock firmware. Follow the instructions on how to flash that. If you're still not out of a boot loop then you want to put it in for warranty. Do not flash a custom firmware or root as that will void your warranty.

Awesome idea thanks.
I just gave it a go, and as my Play's SD card is encrypted (formatted as internal storage) I copied the image to a different SD card, then I thought about the enycryption and I tried booting it up normally with no SD card and it worked! So whetever the issue was, it was related to the encypted SD card.
Thanks for the inspiration, I hope this post helps someone else in the future!