Develop Bugs

[Q] Help! I think I bricked my brand new Desire!

First of all I have an unlocked Telus Desire. This is running HBOOT.83 and was rooted using Unrevoked.
The first rom I tried to install was LeeDroid 1.8 and I got a boot loop and never was able to get it running.
After installing this rom I noticed the phone started freezing at the white screen where it said HTC. I was able to go into recovery and flash Pinky just fine. I then decided I wanted to try the cyanogen mod rom so I flashed that and it was really really buggy for me.
I was able to flash back to Pinky but then I started getting Force Quits everytime I opened the market. I went to reflash the rom and now my phone doesn't boot at all.
EDIT: Now when I boot into the Rom I get a few errors popping up and then it restarts. So I can get into Pinky but it crashes and boot loops.

maybe try installing fake flash, clear all your caches and batt stats, install a basic rom just to get it up and running before you install a custom rom of choice. I have found it isn't as easy to brick this phone as say my old omnia i900 which was windows based. It could be that installing roms without clearing all yr caches is causing the glitches. I'm not an expert and don't claim to be but I always have a clear out before installing a new rom and it works for me.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk

Thanks for the advice, I will look into Fake Flash as I am not very familiar with that process.
As an update I managed to get into Recovery, and of course I flashed a rom which gave me nothing but a boot loop. Thankfully I was able to mount the SDCard in recovery mode and I am loading on one of the more vanilla sense roms to see if that works.

A lot of custom roms require you to have an ext3 partition on your SD card. This can cause bootloops if you don't have the card partitioned.
I'd also try booting without the SD and see what results you get.

You will all be happy to know the phone is no longer bricked. Recovery mode seems to be working again and I didn't really do anything to do that.

[Q] Rom manager restore problem, please help :(

Was using my dad's Desire (I have my own), and thought I would do him a favour by rooting it, so he could backup. I rooted using unrevoked 3.21, and did a backup using ROM Manager. I've heard this is a bad idea, but I never had a problem with my Desire using ROM Manager, and an older version of unrevoked.
Anyway, after the backup, I tried to restart, and it got caught in a boot loop, never getting past the pink circle. (My dad has a t-mobile, HBOOT 0.75, have since upgraded to 0.93 with android 2.2)
My old backup Roms that I did for my desire work fine on his phone, so I have been able to do the above, but I really wanna get his old system back.
I've wiped the cache, done a full wipe, re-rooted, loaded the backup from Rom Manager, and from recovery, and nothing seems to work. The best I can get is looping from the splash screen, but another variation is getting stuck on the pink arrow circle.
So, what is the deal with unrevoked and ROM Manager not working together, when they used to be fine with old versions? Do I have to now backup by recovery alone? But more importantly, is there any way to get my dad's backup back, or is it gone forever?
Please help,

I'm sorry I can't help but here is an advice, never ever use Rom manager. Gives me lots of problems and scared me badly so many times in recovery. Maybe the plain all recovery methods in the clockworkmod would do fine although it has never worked for me. When I use it I still go into boot loops. Try not to use it but maybe that's just for me. Maybe you could try to get the Rom your dad previously used, flash it and on your SD card, there is a folder called clockworkmod, in it there is a folder named backup. From there maybe you could recover your data. I am not sure how but there is always a possibility. Hope that helps!

Thanks for the reply. I've given the phone back to my dad now. He wasn't best pleased about the wipe, but I was able to pull out his contacts from the data.img, which was the most important thing.
Sent from my HTC Desire using XDA App

[Q] Unable to flash stock

Ok, I have good information for you guys. I'm *fairly* noob, but not too bad. Here's exactly what I did:
I got a HTC Desire HD from Vodafone-Australia yesterday. I thought I'd root it, then consider cyanogenmod from there. I followed the instructions here: <cyanogenmod desire hd full upgrade guide from wiki> very closely.
I have never plugged a SIM into this phone. I've been using WiFi. Using my WiFi I downloaded ROMmanager and flash clockwork 3.0.0.5
I then did a backup. I didn't downgrade because the software number was 1.32.178.5.
I followed the instructions to get temporary, and then full SU access. This all seemed to work without a hitch.
I then flashed the engineering HBoot, specifically because it said it could help if I brick the phone.
I then flashed this radio: <radio in the wiki> Seemed to work, but don't know how to confirm.
NOW. This is where it went pear-shaped. I kind of liked the sense UI, but had been using cyanogen 6 on my nexus for ages. I wanted to see if I could flash Cyanogenmod while keeping the sense apps etc. So I told ROMmanager to flash, but NOT wipe the current ROM. I believe this was Cyanogen 6 (stable.) Can't remember full version number.
It rebooted, it flashed. Then went into a boot cycle. The cool Cyanogen loading screen would rotate a bit, then flicker, repeat. I figured "crap." And so went back into the bootloader -> backup and restore -> restored the latest backup.
I then got stuck on a white HTC screen. I figured, still stuck in a boot cycle... so I tried my other backup I'd taken when I first got the phone. White HTC screen again.
So I did a factory reset... still getting a White HTC screen. I start to panic. I tried variations on the theme of "format/wipe/flash" with no luck.
Eventually what I did was download Cyanogen 7 to the sdcard, then flashed that... and it worked!!!! PHEW. Not a brick at least.
Ok, so I figure - well now I have SOMETHING flashed, I can try flashing back my backups. No luck. Everything else leads to a white HTC screen - I've left it for hours at a time. It just won't boot.
So, ok, I have Cyanogenmod 7 running. However, my wifi now doesn't work. I turn it on, it stays on for about 10 seconds, then switches off. It never detects any wifi. In typing this, I figured I might have formated something to do with the radio... ? So I'll try reflashing the radio.
Anyway - can anyone help me? I'd really like to get back to stock if possible. In a pinch I'll settle for Cyanogenmod 7 with working wifi.
Why does only cyanogenmod 7 work? I've tried cyanogenmod 6, and several clockworkmod backups. Also this stock image <link stripped because I haven't posted enough. It was a link modaco.com>
Why does my wifi not work? Can I get stock back?
PS. I flashed the radio and it worked
PSS. I had to strip out all my links because I haven't posted enough on here.

I might have got it. I flashed Cyanogen 7, and as I said above that worked.
Now I have a working radio, I can download ROMmanager. I got ROMmanager to flash the stock ROM I downloaded -- and it worked.
Now all I have to decide is if I want stock ROM or cyanogen with HTC apps restored via titanium backup

dakuth said:
I might have got it. I flashed Cyanogen 7, and as I said above that worked.
Now I have a working radio, I can download ROMmanager. I got ROMmanager to flash the stock ROM I downloaded -- and it worked.
Now all I have to decide is if I want stock ROM or cyanogen with HTC apps restored via titanium backup
Click to expand...
Click to collapse
HTC Sense apps, in the main wont function without the sense framework which is missing from CM, so dont think you'll have much joy running them.
BTW your problem restoring your backups was due to the fact that you need cwm 2.x to flash pre-gingerbread builds and cwm 3.x to flash gingerbread builds

Rooted, Flashed Evo Classic, Loved it... now it keeps rebooting!

I rooted my Evo for the first time today using the Revolutionary method. Everything went smoothly following the instructions. I downloaded and flashed the latest Evo Classic ROM and I was loving it. It seems to be an awesome ROM. I have 200 MB free space instead of 46MB with all of my apps installed. Everything was great until I went to go to bed. I put the phone on the stock HTC charger and climbed in bed. Less than a minute later it rebooted. The phone has always done that at random times so I didn't think anything of it. Shortly after it booted it rebooted again. It just keeps rebooting over and over as long as it's on the charger! Now it even reboots when it's not charging but the interval is as long as 10 minutes instead of 1.
Has anyone else had this issue? I spent HOURS getting everything just right and customizing settings after flashing this ROM and I really don't want to have to do it all over again. I followed the instructions for flashing the ROM. I cleared the cache and wiped all data. I backed up my apps with Titanium Backup and restored a select number of them. My phone is my alarm clock. Now I can't trust it to wake me up in the morning to go to work!
EDIT: I just restored from my stock NAND backup and it is working fine for tonight. I'm guessing I need to just start from scratch and reflash Evo Classic? I can't seem to find anyone else that had this problem so I assume it was something with my flash or an app I had installed?

I flashed a fresh Evo Classic ROM and started over. Everything was great. I got it all setup and restore my apps. No rebooting problems. Put it on the charger. Worked fine. As a troubleshooting step I opened Sleep, my alarm clock app, and within 30 seconds it rebooted. Obviously something with that app triggered it. I uninstalled it. About a minute later it started a reboot loop in one minute intervals.
Apparently no one has any ideas or I am invisible. I can't post in the Evo Classic thread because I don't have enough posts to earn me the privilege.

Did you wipe dalvik? And what recovery are you using?

I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions.
I only see two options:
Wipe Data/Factory Reset
Clear Cache Partition
I have done both of these each time I flashed. I just flashed again and installed only the Sleep As An Droid app fresh from the market. I opened it and within one minute it rebooted. Obviously this app doesn't agree with this ROM or something isn't going right during the wipe and/or flash.
Any other suggestions for a stable ROM that has the new Sense notification bar with quick settings?
EDIT: I found the Dalvik Cache wipe option under advanced. Doing it now and will reflash and try again.
EDIT 2: Well that failed. I wiped data, cache partition, and dalvik and flashed the ROM. I logged into my Google account, downloaded the app from the market, put the phone on the charger, opened the app, and it rebooted.

Is it rebooting if you don't use that particular app at all?

Evo450 said:
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions..
Click to expand...
Click to collapse
That recovery is called clockwork. You might think about changing your recovery to amon ra since some people have issues with clockwork because it doesn't properly wipe cache and dalvik

Hey there! Sorry about your issues. I don't always check the q&a, so you are usually better off posting on my thread or pm. I just happened to peep on here today
First. Use this. It's the second step on my instructions to flash Classic. Not necessary, but recommended. http://forum.xda-developers.com/showthread.php?t=705026
Second, don't use titanium backup. Instead, use mybackup root (free in market and included with my Rom). Not to bash tb, but mybackuproot has never given me issues while I've heard stories about tb.
Third, once you get amon ra installed, boot into recovery and wipe everything but your sdcard.
Fourth, download a fresh copy of classic from a reliable network, like home computer. Downloading from a phone is bad news (just a tip since you're newly rooted )
Fifth, flash and enjoy!
Please let me know how it goes for you.
Truly,
Tommy
tapatalk signature here. lovely.

Thank you very much for the reply! I will try your suggestions some time this weekend. I need my phone to work 100% as I am traveling so maybe Sunday I will try again.

I followed all of your suggestions and redownloaded the ROM, installed RA Recovery, cleared all data, cache, and dalvik several times, and reflashed the ROM.
I restored my apps and data using MyBackup Root and it took over 2 hours! I opened my alarm app and... reboot. Back to the same old reboot over and over.
I think I'll just go back to the stock ROM and remove the bloatware and call it good.

Theirs one obvious thing nobody mentioned. Google how to check a md5 sum do that with every rom you download and if it does not say its right don't flash, redownload and check again. Also restore as little as possible through mybackup and if you are restoring things like your alarms or any system settings don't.
As for good roms with quick settings like r2r going green lightning fast, or unleashed r6.
Ps I would suggest useing r2r superwipe before whatever you may flash n wipe both caches a few times first it might help
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Also id recommend copying all contents of SD card to computer and wipe SD card then reload everything back onto SD card. I know sometimes the SD card can become corrupt and cause bootloops and random reboots

I checked the Md5 sums of everything I downloaded. I only restored my apps, text messages, and Bluetooth pairings. I even ended up buying a new, larger SD card yesterday and I formated and used it when I flashed.
This afternoon I flashed my latest backup of my stock ROM and used Titanium Backup to removed all of the Sprint bloatware. My phone is running very fast now with over 110 MB of internal memory available so I can't complain.
Maybe next weekend I will try another ROM but for now I need me phone to be working since I do not have a land line and I rely on my phone for work.

You said this happened before you ever rooted? Maybe its a factory defect if u got a.warrenty I would suggest unrooting and sending to them.
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.

Its not normal they keep giveing you defects... I have never heard of.this problem anyway... I would take it bac
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
My girlfriend had the same issue with her second evo. She had the Black Evo at first than a friend of hers swapped her to the white Evo. She had the issue only on the white evo. She ended up having to replace the phone with another one. That one did the same thing for awhile so we thought it was an issue with an app she was running. I have the black evo and made a exact copy of her phone. I never once had the issue.
Sprint ended up replacing it agian with a line that something was different in the white Evo from the black one that was causing the issue. Ever since that day she hasn't had a problem with her phone. I just rooted and did her rom last night.
My question would be does the phone get hot? Or feel hot? The reason I ask is that the phones processor may restart the phone (in effort to cool it down) randomly. That is something to consider.

Glad I got the black
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
I kept getting the same thing when i flashed classic. I went back to shooter port which runs butter smooth and is fantastic looking with sense 3.0.
DO THIS TO TRY TO GET EVERYTHING WORKING (no more soft reboot)
-connect your sd card to your computer
-copy contents to your computer for a backup
-copy PC36IMG.zip to your sd card make sure it is on root of sd card(attached to message)
-disconnect usb cable then pull battery
-enter bootloader (vol down + power)
-when it asks if you want to install the new update select yes
-after thats done pull the battery again
-enter bootloader then select recovery ( you should now have amonRa 2.3 )
-flash zip from sd card (vrsuperwipe.zip *thanks to virus*)
-go back and go into wipe menu, wipe dalvik-cache, wipe sdext, battery stats, and rotate settings.
-go to partition sd card and partition for a gingersense rom if you have not done so already. (0 swap, 1024 or 2048 ext2, remaining FAT)
ABOVE PROCESS COULD TAKE SOME TIME, MAKE SURE YOUR SD CARD IS MOSTLY EMPTY BEFORE YOU DO THIS (ONLY HAVE PC36IMG.ZIP ON IT)
-select usb mass toggle and connect to computer
-copy over your choice of rom, i suggest the shooter e3d port by team nocturnal.
-flash rom
-go to flash zip from sd card again this time select TeamNocturnal folder and pick a kernel to flash (try all of them if you would like, some phones run better with different kernels. mine runs well with HDMwIn kernel.
-wipe dalvik-cache one more time and you are ready to reboot with no more random restarts hopefully.
good luck - and please hit the thanks button if any of this works for you

[Q] boot loop...(sort of)

I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)

Gzerner said:
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Click to expand...
Click to collapse
K. The reason you aren't getting to the old version of CWM is because you flashed Codename. Codename is an AOSP ROM which has been known to cause bricks when flashing with Rogue. Because if the bricks the developers opted to but include CWM of any kind in the kernel. What you need to do is find a replacement ROM and download it. Once you've downloaded it you need to flash the EL26 stock CWM (you can find it in the OP of the link below) then use it to flash your new ROM.
http://forum.xda-developers.com/showthread.php?p=295021
Well you're at it is suggest reading the How Not To Brick Your Phone thread in general.
Good luck!

Codename rom is an AOSP rom so your external SD storage will be under /emmc and not /sdcard/externalsd. That's why it wasn't showing up. Same thing with CM9 and AOKP, not because it doesn't work. Also I wouldn't recommend flashing anything ICS related from rogue recovery, js.
And recoveries changed because with our phones, the recovery is packed into the kernel itself so when you flashed Codename, the recovery changed to the stock recovery included with the roms kernel. Hope that clears it up lol.
Sent from my SPH-D710 using Tapatalk

If you want a fresh install, the best way is to Odin the el29 kernal. From there, get into your recovery and wipe and flash away.
Sent from my SPH-D710 using XDA