Develop Bugs

[Q] Please help - Desire very poorly.

Hi. I hope someone can help.
I've been using my desire rooted and S-OFFed running Defrost for sometime, all has been fine. Was playing Angry birds yesterday and the phone froze.
Pulled the battery and rebooted, carried on playing. Froze again.
Pull the battery again but phone stuck on the first splash screen. Fiddled a bit, couldn't get into recovery. So I left the phone on charge until the light went green, then removed the battery and left it overnight.
This morning I put the battery in and switched it on. It booted fine, but froze when I tried to unlock it.
I've tried pulling the battery again and again. I can get into HBOOT, but the phone isn't recognised for ADB or fastboot commands via USB. It often freezes even in fastboot mode.
I tried to do a clear storage, but that froze as well. Although a subsequent attempt appeared to work but the phone still won't boot normally.
So I can't reflash or do anything else. HAs anyone actually sent a phone back for repair with custom firmware/splash screen installed, as I don't think I'm going to be able to revert it to stock.
I've tried numerous restarts with and without a sim and an sd card inserted. Not sure what else to try.
Any help greatly appreciated.

did you wipe the dalvik cache through recovery?
try this if you can.

No I haven't wiped the dalvik cache. I have managed to get in to recovery on a couple of occasions. But the phone has frozen again navigating the menu.
I will try that if I get into recovery again though.
Thanks

Quick update.
After leaving the battery out for a couple of hours. I tried again and the phone started to boot. It got to the splash animation and the wipe had obviously worked because it was the DeFrost default of the X. This then looped a few times then froze.
I pulled the battery and managed to get in to Clockwork Mod recovery and did a wipe from there, which appeared to work, but then it rebooted by itself and I still didn't manage to do a dalvik wipe.
Now I'm back to the same point again. I can't get into recovery.
I guess I'll try again after leaving the battery out for a while.
One thing I did notice when in recovery was that the trackpad didn't work. I had to use vol and power keys. If I get into recovery again, I'll try a keytest if I get into recovery again.

And another update.
I got into recovery again and did a wipe dalvik cache.
I got the following error.
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Dalvik cache wiped.
So I'm not sure if it actually did it or not.
I then tried to do a nandroid restore and got a similar error.
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Then the phone froze again.
So I'm guessing something is corrupted here.
Should I try formatting the SD card. (I have backed up all the data I could using my PC).

i think your dalvik will have been wiped. i always get the same message.
have you tried it again but without trying to restore a nand?

Yes, I tried it again. I only seem to be able to get in to recovery after leaving the battery out for a while.
This time I did a dalvik wipe then rebooted, but it's just stuck on the initial splash screen again.
I'm pulling my hair out here (what little I have)

have you considered going back to a stock rom using an RUU or PB99IMG?
then you'd have to root again and restore your nand if possible/needed.

I'd be happy to try reverting to stock, but don't you need to get the phone to boot before you can do that?
I have sent this phone back for repair previously and done just that (it suffered from the overheating problem and had a whole new motherboard less than months ago).
After leaving the battery out again for a while, a normal switch on got to the animation splash then rebooted twice before freezing again.
Is this likely to be a corruption in the flash memory, or a hardware problem?

Hello,
I've got exactly the same problem! The phone freezes on the first splash-screen (not the Rom's bootanimation) and I can't get into recovery.
I'm running Oxygen Rom (2.0-RC6) and using Apps2SD in combination with an 8GB Transcend microSD card. I've only "rooted" it once using Unrevoked (long time ago), so I assume it is still S-On. I'm using clockwork's recovery, too.
At the moment I really don't know what to do.
What could I try?
pc99mk:
At the moment I'm leaving the battery out the phone until afternoon, hoping to get into recovery
Thank you in advance for every bit of an answer

Read up on the PB99IMG process if you can get into recovery (power & vol down).
Otherwise, the RUU will work if you can boot into fastboot (power & back key).
Sent from my HTC Desire using Tapatalk

Hi spadoleo.
Sorry to hear you're having similar troubles.
I'm sure mine must have some sort of hardware problem now.
After leaving the battery out for a while again last night, I managed to get into fastboot and flash the latest alpharev hboot, and clockworkmod 3.0.0.5 in the hope that my freezing problems there were due to a slight corruption.
Clockworkmod has definitely updated as the colour of the menu has changed, but it still freezes soon after entering.
I just want to try and get the phone looking as much like a stock phone prior to sending it back now.
Does anyone have a fasstboot flashable image of the following:
UK TMobile 'Pink Circle' splash1 image
Standard HBOOT
Standard recovery
Otherwise I'm just going to have to send it back to HTC as is, and hope they still fix it under warranty.
Or is there any way of getting a RUU to start doing anything with the phone in fastboot?
Or indeed anything else I can try?

See my post above.
You can run an RUU in fastboot.
Sent from my HTC Desire using Tapatalk

Hi mikep99.
Ok thanks for the advice. I'll have a read of the pb99img stuff.
I tried the RUU this morning in fastboot mode, but every time it justs sits at the 'Verifying information on your Android phone' for a while, then times out with a USB connection error.
I seem to have best results after leaving the battery out for a while (no idea why that should make any difference but it does), so I'll try it again in an hour or so.
Cheers

Install htc sync if you haven't already.
And try turning off antivirus and firewall on your PC
HTH
Sent from my HTC Desire using Tapatalk

Ok. I read up on the PB99IMG process.
I found a PB99IMG.zip file posted by Teppic74 which is a stock Froyo.
I copied it to the root of my goldcard and booted the phone.
It loaded the file and came up with
Incorrect CID error
update fail
I then kicked myself. I created the gold card to revert the phone to stock before sending it to HTC previously.
They replaced the motherboard. Would this have changed my CID?
I then thought 'no problem I'll just go through the gold card creation process again'
But although I can do stuff on the phone in fastboot mode, adb doesn't work in that mode. So trying adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
just gives an error.
So if my CID has changed, any idea how I can create a gold card with the phone in this state. Should adb only work when the phone is booted, or should it work in hboot or fastboot?

i'm not sure which PB99IMG you're trying to flash but i'd use this (if its not the same):
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.zip
with regards to the goldcard, have you mounted the sdcard when in recovery? and then running
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
again?
if that doesn't work, you can use another TMobile Desire to create it.
therefore, i don't think the mbo change should affect your goldcard????
EDIT - when you got your phone back from repair, was it completely wiped? Tmobile may have wiped/swapped etc.. the goldcard you previously made.

I think it was that image that I used. But I'll download it again just to be sure.
When the phone was repaired before, I sent to HTC directly and I didn't send any sd card or battery. So it should still be as it was.
So if the CID isn't motherboard specific it should still work.
Is there any way to check whether it is still a goldcard? I may have formatted it again (don't recall).
Although thinking about it, I still have the image file emailed to me when I created the gold card originally, so I could just reapply it and try again.
I'm out tonight, but will try a few things and post back with my results.
Thanks for your help so far.

Another update and things have moved forward.
It turned out I'd trashed my gold card, but I did still have the image file so I recreated it.
I then booted the phone again and it loaded the PB99IMP.zip file.
It then asked me if I wanted to perform the update. I said yes, and it updated the bootloader and rebooted. Then it froze on Checking PB99IMP.zip....
After leaving it 10-15 minutes I pulled the battery again and left it for a while.
I tried again just now.
I can see that it has updated the HBOOT, so I'm no longer S-OFF.
Just now I thought it was going to work it got about halfway through updating the system partition before freezing.
If only it had updated the splash1 image before the system, I might've had the phone in a suitable state to return. But it still shows my custom splash1 screen when powering on normally - then it changes to the piccy with the green arrows.
I'll try it again later after leaving the battery out for a while.
But the fact it freezes in the middle of such an update suggests it's definitely a hardware problem of some sort.
If anyone has any other ideas I could try, please let me know. But once again thanks for all the help so far.

Sounds like you're getting somewhere
Just keep on trying every now and again.
Hopefully it'll go through...
Sent from my HTC Desire using Tapatalk

[Q] Help, semi-bricked DZ

My Desire Z stopped working the other day when trying to update angry birds rio, my phone would just freeze everytime it tried to resume the download (stopped at 92%)
The only way I could use my phone was battery pulls, and disabling all data connections.
After a fair few battery pulls (trying to cancel the download and what not) my phone would stop booting up (stayed at splash screen for ages)
Clockworkmod recovery can't find/mount cache, and won't let me either restore a backup or flash a new rom (I used superwipe).
I've tried everything I can think of, installing different versions of clockworkmod, using RUU's, flashing RUU's via PC10IMG and nothing works.
I can't boot into android to use adb, and I don't think I have an eng hboot so all fastboot commands I've tried have failed.
Hboot:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
RADIO-26.08.04.30_M3
eMMC-boot
Oct 11 2010,20:10:38
I was running SenseGinger 3 with rmk's oc kernel when this first started.
Any help will be greatly appreciated as I'm onto my third day of not been able to use my phone.
-Nipqer

Do you have a warranty on your phone? If so we can all the way brick it using adb, and get it replaced.
Sent from my shiny metal G2 w/ meXdroid V3

If you can get into recovery you can do adb in there, there is something bout that error in recovery that can fix the error, I jus don't remember where, and purposly bricking phone nor gonna do much, try to fix it you can still get into hboot and recovery which is good, what you could do is downgrade phone and reroot, but that's another option after you try fixing recovery

Nipqer said:
My Desire Z stopped working the other day when trying to update angry birds rio, my phone would just freeze everytime it tried to resume the download (stopped at 92%)
The only way I could use my phone was battery pulls, and disabling all data connections.
After a fair few battery pulls (trying to cancel the download and what not) my phone would stop booting up (stayed at splash screen for ages)
Clockworkmod recovery can't find/mount cache, and won't let me either restore a backup or flash a new rom (I used superwipe).
I've tried everything I can think of, installing different versions of clockworkmod, using RUU's, flashing RUU's via PC10IMG and nothing works.
I can't boot into android to use adb, and I don't think I have an eng hboot so all fastboot commands I've tried have failed.
Hboot:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
RADIO-26.08.04.30_M3
eMMC-boot
Oct 11 2010,20:10:38
I was running SenseGinger 3 with rmk's oc kernel when this first started.
Any help will be greatly appreciated as I'm onto my third day of not been able to use my phone.
-Nipqer
Click to expand...
Click to collapse
1 no such thing as semi-brick
2 flash it ?
3 enjoy ?

I see you posted in the other thread that was started about the cache errors, so your best bet is to stick to that thread since it is directly about your issue. Random people coming into this thread will just throw suggestions out that won't work. Or hit the irc chat and see if someone is online that can help right away.
Sent from my T-Mobile G2 using XDA App

Please help! Bricked my phone :(

Hello, after applying the 4.1.2 GSM PRIMOU AOKP ROM ( http://forum.xda-developers.com/showthread.php?t=1882990 )my phone was stuck in a boot loop. What happened was I followed this guide:
http://www.theandroidsoul.com/aokp-for-htc-one-v-gsm-installation-guide/
Well It wasn't that exact guide, but it was quite similar. The only difference was that after you install the files, you flash the boot img. What I did wrong first was install the files and since I was in the recent CWM the only way to go back was to reboot. SO what happened was that it got past the HTC screen, but it got stuck in this "INITIALIZING SWAGGER" screen. After about 20 minutes I forcefully shut off the phone (held the power button until the buttons flashed like 10-15 times and shut off)
After this, I redid the upgrade, but I followed the guide I posted above. This time it did not get past the HTC boot up screen. All I see now is that whenever I start it up, it goes to the HTC logo screen and then to the HTC logo screen with the red text and stays in a loop. And when I applying the upgrade I did wipe the data.
Here is what I have tried so far:
- nandroid backup/restore, it does not work. I made the backup before I did anything with the ROM. After doing the restore, I am still stuck in the same HTC logo red text boot loop
- I tried reinstalling the ROM multiple times, no solution.
What I hope will save me:
-I have not done the RUU yet. BUT here is the problem. I have a fairly new plan with rogers (still 2 years to go). The HTC One V is from koodo, but I bought it from someone and it came unlocked. All the RUUs I have seen are for telus or do not apply. I am wondering that if I do the RUU and my phone is locked to koodo/telus, and somehow my nandroid backup works after this, will the phone be unlocked (because I have to use rogers)? Or do I have to pay money to get it done =( ?
-also I can connect another phone with the micro SD HC. So I might be able to put files onto it and then try stuff on the bricked phone.
-my nandroid backup might just have something wrong with it, I'm also guessing that the countless "wipes" I have performed with each attempt to get the ROM installed probably doesn't do anything to the recovery. HOPEFULLY there is another "stock" nandroid backup that may work for me (as I can access the microsd).
Another few things to note:
- I didn't do anything with the "Latest boot.img" - I installed the "boot-TK-USB-CM10-OC-VDD-201210112240.img" but I didn't use it... It might be the reason this didn't work for my GSM phone.
The phone info on HBOOT:
- *** UNLOCKED ***
- PRIMOU PVT SHIP S-ON RL
- HBOOT - 1.18.0000
- RADIO-3831.19.00.120
- eMMC-boot
- Jul 2 2012, 20:51:45
Someone please help. This is causing me much distress. Any ideas are welcome. If anyone can even point me in the right direction with the nandroid backup or RUU (but also keep in mind my dilemma with rogers and unlocking the phone) that would also be great. Thank you in advance.

johnpetrucci said:
Another few things to note:
- I didn't do anything with the "Latest boot.img" - I installed the "boot-TK-USB-CM10-OC-VDD-201210112240.img" but I didn't use it... It might be the reason this didn't work for my GSM phone.
Click to expand...
Click to collapse
What does this mean?
Have you flashed the kernel or not?
You MUST flash the kernel using fastboot
fastboot flash boot boot-TK-USB-CM10-OC-VDD-201210112240.img

maxwen said:
What does this mean?
Have you flashed the kernel or not?
You MUST flash the kernel using fastboot
fastboot flash boot boot-TK-USB-CM10-OC-VDD-201210112240.img
Click to expand...
Click to collapse
WOW. Thank you. I will do this right away. The guide told me to extract a file "boot.img" from the ROM itself... I'm guessing this bricked my phone.

It worked!! Thank you so much!!! The guide didn't specify to download 3 files (one being the boot.img with the really long name) and said the dw just the 2 zip files. You are a life saver!! Also can you explain to me how the overclocking works? As I used the OC boot.img

Go to rom control in the settings A's then click on performance then over clock but do not over clock above 1497 or u may fry ur phone
Sent from my One V using xda app-developers app

Please ask all questions in the Q&A section. Thread moved there.

Bootloop of Death Without Recovery

Yes, it is another infinite boot loop thread. It was working fine this morning and I was reading a book with Aldiko, then I hit homescreen and locked. From that point it went into the loop.
Okay so I'm somewhat new to the modification scene i.e. I haven't worked with fastboot etc. but I have gathered from other threads some of the information you'll be needing.
Here is my info from the HBOOT screen
Code:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
So here are a couple of things I've tried already..
Using HBOOT to boot to recovery causes it to go back into the boot loop.
I originally had CWM Recovery, so I reflashed recovery (RA-supersonic-v4.3-smelkusMOD) successfully and attempted to then enter recovery mode with the same result - boot loop. I have not tried re-flashing CWM, but I would assume it would produce the same result.
I downloaded the RUU exe that corresponds to my radio, but when running the program it gives me a USB Connection Error code 170. It does mention that the phone has to be turned on, however in what capacity I can have it "turned on" I don't know.
Thank you in advance, please advise if there is any additional information needed.

Coldhands said:
Yes, it is another infinite boot loop thread. It was working fine this morning and I was reading a book with Aldiko, then I hit homescreen and locked. From that point it went into the loop.
Okay so I'm somewhat new to the modification scene i.e. I haven't worked with fastboot etc. but I have gathered from other threads some of the information you'll be needing.
Here is my info from the HBOOT screen
Code:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
So here are a couple of things I've tried already..
Using HBOOT to boot to recovery causes it to go back into the boot loop.
I originally had CWM Recovery, so I reflashed recovery (RA-supersonic-v4.3-smelkusMOD) successfully and attempted to then enter recovery mode with the same result - boot loop. I have not tried re-flashing CWM, but I would assume it would produce the same result.
I downloaded the RUU exe that corresponds to my radio, but when running the program it gives me a USB Connection Error code 170. It does mention that the phone has to be turned on, however in what capacity I can have it "turned on" I don't know.
Thank you in advance, please advise if there is any additional information needed.
Click to expand...
Click to collapse
It has to be booted up, being in bootloader won't allow ADB to connect to the device and thats why you're getting the error for the USB connection in the RUU
Try going into recovery (if you can) and clearing EVERYTHING
/data, /system, /cache, dalvik cache, /sd-ext (I would suggest multiple times, or superwipe it if you have that)
Sent from my PG06100 using xda premium

Thank you for the reply, CNexus.
I am unable to get into recovery, but I was able to obtain the rom.zip file that the RUU exe contained and flashed it by renaming it to PC36IMG.zip. The process of flashing was successful on all 6 parts, however, I still have the same issue unfortunately - infinite boot loop, and recovery still looping as well.
I think it may be time to throw in the towel with my Evo unfortunately, barring any information anyone else can provide.
I just am thankful that my upgrade is available on the 1st of the year - but due to extenuating circumstances I will make Sprint give it to me early :laugh:

Coldhands said:
Thank you for the reply, CNexus.
I am unable to get into recovery, but I was able to obtain the rom.zip file that the RUU exe contained and flashed it by renaming it to PC36IMG.zip. The process of flashing was successful on all 6 parts, however, I still have the same issue unfortunately - infinite boot loop, and recovery still looping as well.
I think it may be time to throw in the towel with my Evo unfortunately, barring any information anyone else can provide.
I just am thankful that my upgrade is available on the 1st of the year - but due to extenuating circumstances I will make Sprint give it to me early :laugh:
Click to expand...
Click to collapse
Ah that was a good idea, it sucks that it didn't work though
Good luck then, sorry about your phone
Sent from my PG06100 using xda premium

[SOLVED] Bootloop with no access to recovery (S-OFF)

SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.

Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.

I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".

Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.

Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.

Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?

Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?

Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.

Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.

You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!