Develop Bugs

[Q] Desire z, dead! frezzes in fastboot mode.

Hi,
I have Desire Z, that is dead, the only thing i can access is fastboot mode, yesterday i was able to enter "fastboot oem rebootRUU" and it seems to be ok, but today my phone frezzes every time to something i fastboot mode, og sends comands to it.
can som one help me, my phone is not rootet,
i have tried to flash recovery, but i'm not allowed, i need help, some ideas?
every i have put the P10IMG on Sd card, the phone starts to update, but it frezzes in the first step ( bootloader )
some info:
if you need more, just ask, and i wil provide it.
S-On
Hboot 0.85.0013
radio 26.10.04.03_m
( sorry for my bad english)

thirst thing i would try is to wipe cache...
so enter bootloader, choose recovery = a red triangle should show up then push power & volume up; select wipe cache and reboot
if this didn´t help do a foctory reset = same procedure as above only select factory reset in recovery...
...and remove the PC10IMG.zip from your sdcard so you can enter recovery

I have tried that, but the bootloader, frezzes, and the phone shuts down, and vibrates many times, then its dead again.
every thing i do in bootloader, results in a frezz, and i must start over again.

hm.. not good
another thing you could try is to enter usb fastboot mode (power & tp) connect your phone to pc and then start the ruu (.exe) on pc and maybe it does the update..
after it´s done enter recovery and wipe...
be sure that the ruu is higher or the same like the one previously installed and that it is the right one (asia, europe, bell, ...)
you can´t flash a recovery or anything trough fastboot if you do not have eng hboot or a rooted phone
EDIT: or when you in fastboot mode start cmd.exe go to your tools and type "fastboot oem boot" - maybe you are lucky

When i start the update it stops at the first step ( bootloader ) and its the same version, so it starts, but stops right away.
when i but it in recovery mode, the phone just vibrates a lot, and shuts down.
is there away to install a custom boot, or maybe root the phone now? nothing seems to work.. please help me..
every time i type somthing in cmd, it states to many links as an error. when i type "fastboot oem rebootRUU" the answer is "to many links"

sry, but i think there is not much you can do anymore...
maybe someone else knows better

Flashing new recovery leaves old one and cannot perform fastboot oem lock

EDIT:
Or if anybody knows where I can look for help on this I would really appreciate it.
Hi,
I am searching yesterday and today to solve my problem but no locuk so far.
Yesterday the phone rebooted and since then is staying on "HTC quietly..."
I tried to flash ROM again that was already on my sdcard but recovery said "Bad zip".
Now I cannot access /sdcard from recovery. "Error mounting"
When "fastboot oem lock" I am getting this message:
... INFOLock successfully...
FAILED (status read failed (Too many links))
And then phone reboot and stays at "HTC quitely...."
Flashing boot.img and recovery.img goes OK but the recovery stays the same.
And I have "Low battery level cannot flash". but i can manage to charg the phone a bit.
This is what I have:
HOX Tegra3
hboot 1.39
CWM recovery v5.8.4.0
IC 15.0.1
Does anybody know more about it.
Thank you
EDIT:
Or if anybody knows where I can look for help on this I would really appreciate it.

Re: fastboot oem lock returns error...?
Why do you want to lock the bootloader ?
2 options to charge
1 put the phone inside the recovery, it will charge there
2 put this file in the fastboot folder and boot the phone into the bootloader/fastboot usb mode and execute the bat file ! It will continuously reboot the phone and charge it little by little
http://db.tt/aLqeTpPO

Mr Hofs said:
Why do you want to lock the bootloader ?
2 options to charge
1 put the phone inside the recovery, it will charge there
2 put this file in the fastboot folder and boot the phone into the bootloader/fastboot usb mode and execute the bat file ! It will continuously reboot the phone and charge it little by little
http://db.tt/aLqeTpPO
Click to expand...
Click to collapse
Thank you but charging is not my main issue. Rather that my phone keeps staying on htc quietly... and that i cannot access sd card.

Re: fastboot oem lock returns error...?
Locking the bootloader will not help you, keep the bootloader unlocked and reflash the recovery, try it again after that
Also erase cache afterwards
Fastboot flash recovery recovery.img
Fastboot erase cache

Mr Hofs said:
Locking the bootloader will not help you, keep the bootloader unlocked and reflash the recovery, try it again after that
Also erase cache afterwards
Fastboot flash recovery recovery.img
Fastboot erase cache
Click to expand...
Click to collapse
I did that...no matter what i flash it says OK but nothing is changed.
I tried flashing other recovery ... nothing.
Thank you.
It seams that I have to take it to a service...

Re: fastboot oem lock returns error...?
Strange ???

try this tool: http://forum.xda-developers.com/showthread.php?t=1924003
It has commands which might help you...

Thank you all
Thank you all for your time.
I did everything, including reinstalling drivers and trying all again, and could not solve it.
I took it to the store hoping they will not mind "unlocked" status.
When I get it back I'll be posting it here if someone can benefit from that info.
Cheers:fingers-crossed:

[Q] HTC One X Stuck in Fastboot -

Hi there, this is a last ditch attempt before I send the handset back to Virgin Mobile.
I successfully unlocked my bootloader and rooted my phone, then tried to flash it with Paranoid Android for the HTC One X. This seemed to work and ended up getting stuck on the X loading screen that comes with Nexus devices. It got stuck so I then read up and it seemed like I needed to flash the boot.img that came in the zip file. DId that and the phone then just got stuck on the HTC "Simply brilliant" loading screen.
Clockworkmod is installed, and I have tried to reset the phone with the appropriate RUU. However, now the phone just sits on the HTC simply brilliant screen - that now has a warning about it being a developer version. It then loads only into the Fastboot menu, and all option either reboot the phone to follow that same path (warning, then fastboot screen) or do nothing.
I can no longer get into Clockworkrecovery, and there is also no way of getting a rom onto the phone to work with.
The RUU also only seems to get about half way through until it tells me there has been a communication error.
Please, I hope someone can give me some help. I've tried countless threads, countless downloads and am now just confused about the whole thing.
Oh, and the battery always seems to be low - at least the fastboot menu tells me it is
Could someone give me a step by step guide on how to resolve in possible?
Thanks in advance!

keeno79 said:
Hi there, this is a last ditch attempt before I send the handset back to Virgin Mobile.
I successfully unlocked my bootloader and rooted my phone, then tried to flash it with Paranoid Android for the HTC One X. This seemed to work and ended up getting stuck on the X loading screen that comes with Nexus devices. It got stuck so I then read up and it seemed like I needed to flash the boot.img that came in the zip file. DId that and the phone then just got stuck on the HTC "Simply brilliant" loading screen.
Clockworkmod is installed, and I have tried to reset the phone with the appropriate RUU. However, now the phone just sits on the HTC simply brilliant screen - that now has a warning about it being a developer version. It then loads only into the Fastboot menu, and all option either reboot the phone to follow that same path (warning, then fastboot screen) or do nothing.
I can no longer get into Clockworkrecovery, and there is also no way of getting a rom onto the phone to work with.
The RUU also only seems to get about half way through until it tells me there has been a communication error.
Please, I hope someone can give me some help. I've tried countless threads, countless downloads and am now just confused about the whole thing.
Oh, and the battery always seems to be low - at least the fastboot menu tells me it is
Could someone give me a step by step guide on how to resolve in possible?
Thanks in advance!
Click to expand...
Click to collapse
Do you know how to use fastboot? If so:
1. Flash stock recovery with fastboot flash recovery recovery.img <--- This file in the same location as fastboot
2. fastboot erase cache
3. fastboot oem lock
4. It may reboot or not. Just load back into the bootloader.
5. run RUU

Thank you for the reply,
Unfortunately I can not seem to flash anything using fastboot at the moment as it always says my battery level is too low to flash. It has been on charge for most of the day so can't possibly be empty. I would usually clear the battery stats to get round this but can not longer get into clockworkmodrecovery.
Any advice on that - thanks again!

keeno79 said:
Thank you for the reply,
Unfortunately I can not seem to flash anything using fastboot at the moment as it always says my battery level is too low to flash. It has been on charge for most of the day so can't possibly be empty. I would usually clear the battery stats to get round this but can not longer get into clockworkmodrecovery.
Any advice on that - thanks again!
Click to expand...
Click to collapse
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Put that into notepad and save it as fastbootcharge.bat
Put the fastbootcharge.bat in fastboot location and run it while the phone is in fastboot mode.

https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
:thumbup:

[Q] Boot Loop with after SIM Change?

Following on from this problem:
http://forum.xda-developers.com/showthread.php?p=39472437
Phone has been working fine after install of AOKP (http://forum.xda-developers.com/showthread.php?t=1642443).
Until I swapped SIM cards to try EE vs. GiffGaff for service and running costs.
I switched SIM card back and phone started boot loop.
HTC screen then AOKP screen with Unicorn head, then phone resets and starts loop again.
So tried booting without SD card and SIM get to home page for a few second and then reboots.
So tried wipe data/factory reset and wipe cashe partition, now get as far as first page of new android user, then reboots.
With power button and - key I get:
vision pvt eng s-off
hboot- 0.76.2000 (PC1011000)
microp-0425
radio-26.03.02.18_M3
eMMC-boot
Suggested next course of action? As I assume AOKP and/or Android is damaged.
I have read most of the boot loop topics, but do not seem to cover this version of boot loop (So new topic). Do not want to go any further until I was sure I would not make things worse.

Ive heard a couple people complain about similar things before but truthfully the reason why doesnt make too much sense to me, do you mind capturing a logcat?
also may be interested in reading through THIS PAGE if you havent already. also will find info on logcats here if youre unaware
my guess is there is a corrupt partition somewhere as after doing some wiping you still have a bootloop
to fix it youll be best of starting with a full wipe and format, either by formatting all partitions in 4ext recovery,
flashing a superwipe script, or the aio nullifier script (both linked in the thread above)
or booting into fastboot and wiping from there
fastboot erase system -w
or do all those, im a bit ocd when it comes to wiping so i would
if this fails then it could be within a firmware partition, like radio or hboot, this seems unlikely to me as
there shouldnt be an write to these at all, but your situation is uncommon and a bit strange so
if you want flash a new radio and or hboot via fastboot OUTLINED HERE or go to the 30th thread and flash a PC10IMG.zip
good luck!

I'm facing a similar bootloop and can't figure out why
@demkanator
Can you please have a look at my thread?
http://forum.xda-developers.com/showthread.php?t=2214813

Re: [Q] Desire Z bootloop with JB roms
Can you post a logcat? Also will you boot into your bootloader and write down EVERYTHING on that screen here?
Sent from my Nexus 7 using xda premium

Requested information
demkantor said:
Can you post a logcat? Also will you boot into your bootloader and write down EVERYTHING on that screen here?
Click to expand...
Click to collapse
I only have clockwork recovery 5.0.2.7 on phone, not sure I can put on or use 4ext recovery, flashing a superwipe script, or the aio nullifier script.
I have wipe data/factory reset which got this result
"Formatting /data
Formatting /cache
Formatting /sd-ext
No app2sd partition found. Skipping format of /sd-ext.
Formatting /sdcard/.android_secure
Data wipe complete."
Also did wipe Dalvik Cache:
"Dalvik Cache wiped"
At this point phone will still do reboot loop.
But on booting into fastboot and wiping from there fastboot erase system -w. Phone now sits on HTC screen.
Though I can still get to clockwork recovery and Hboot/Fast boot.
Again here I will stop so as not to make anything worse.
Here information you asked for:
System Info
SN-HT0AJRT03242
LCD-S0
Touch Panel-ATEMEL224_20aaY
Commit-97743036
OS Ver.01.34.707.3
IMEI-352212040170091
CID-11111111
eMMc-unknown 2223MB 4554751sectors
IMAGE CRC:
hboot: 0x6570C0DB
boot: 0x70A9908C
recovery: 0xB983BB96
system: 0x61EF2FF9 (THIS was result before I did fastboot erase system -w")
system: 0x0 (Is result after fastboot erase system -w")
With ADB running I plug USB into phone, phone boots to clockwork recovery menu (Which I can move up and down menu with -/+).
Note: I use the menu for about 25 seconds and regardless of any pressing - or + before screen go's blank. But orange LED on (I assume charging?).
I type: "adb devices"
I Get "HT0AJRT03242 recovery"
I type: "adb logcat > logcat.txt"
File saved has just "/sbin/sh: exec: line 1: logcat: not found"

You are missing the first bit of info in hboot, can you please add this, lines starting at
Vision pvt.....
Also is fastboot working?
Sent from my SGH-T839 using Tapatalk 2

More information
demkantor said:
You are missing the first bit of info in hboot, can you please add this, lines starting at
Vision pvt.....
Also is fastboot working?
Sent from my SGH-T839 using Tapatalk 2
Click to expand...
Click to collapse
Booting phone (Holding power + -Key) I get:
Vision PVT ENG S-OFF
HBoot-0.76.2000 (PC1011000)
MICROP-0425
EMMc0-boot
Aug 20 2010, 16:51:01.
Hboot screen shows "HBoot USB PLUG", when I select FASTBOOT from menu screen displays "FASTBOOT USB".
But with phone on this screen displaying "HBoot USB PLUG" or "FASTBOOT USB", I type "adb devices" and get nothing but text "List of of devices attached" nothing after that.
But if I repeat "With ADB running I plug USB into phone, phone boots to clockwork recovery menu (Which I can move up and down menu with -/+)."
I type: "adb devices"
I Get "HT0AJRT03242 recovery"

adb will only work in recovery and in os (so long as debugging on etc)
in fastboot mode use fastboot, similar but different
HERE ARE SOME TIPS ON FASTBOOT i suggest to study them as they can be just as handy as adb
but for now try to get into fastboot mode and type this is cmd
Code:
fastboot devices
if you see yours good, if not read the linked thread
then go with
Code:
fastboot oem check_emmc_mid
see if it says samsung or sandisk
the above is goo information to know, so check it out and respond back.
but i believe you will find your fix HERE
read and ask questions if needed
good luck!

Contining understanding
demkantor said:
adb will only work in recovery and in os (so long as debugging on etc)
in fastboot mode use fastboot, similar but different
HERE ARE SOME TIPS ON FASTBOOT i suggest to study them as they can be just as handy as adb
but for now try to get into fastboot mode and type this is cmd
Code:
fastboot devices
if you see yours good, if not read the linked thread
then go with
Code:
fastboot oem check_emmc_mid
see if it says samsung or sandisk
the above is goo information to know, so check it out and respond back.
but i believe you will find your fix HERE
read and ask questions if needed
good luck!
Click to expand...
Click to collapse
Typing "Fastbook devices" shows my device.
Typing "fastboot oem check_emmc_mid" I get:
"<bootloader> Manufacturer ID, MID=45
<bootloader> eMMC should be unkonwn
OKAY [ 0.000s]
finished. toal time: 0.016s"
Trying to understand why this happened and what was damaged, but seem next stage is to re-do and clear old install (You link above)?
Could I just put Android 4 rom back on at this point, if that was only damage? or better to check and other parts of install?
These are the guides I originally used to setup Android.
http://wiki.cyanogenmod.org/w/Install_CM_for_vision
http://forum.xda-developers.com/showthread.php?t=1642443

Well I don't like that lit says unknown but there really isn't much more you can do @ this point. I would just flash one of those PC10IMG.zips and if it works flash a new ROM, you'll either have a working phone or be in the same place you are right now
Good luck!
Sent from my Nexus 7 using xda premium

Trouble ahead?
demkantor said:
Well I don't like that lit says unknown but there really isn't much more you can do @ this point. I would just flash one of those PC10IMG.zips and if it works flash a new ROM, you'll either have a working phone or be in the same place you are right now
Good luck!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
PC10IMG.zip on SDCARD booted Hboot and get:
SD Checking
Loading...[PC10DIAG.zip]
No Image
Loading...[PC10DIAG.nbh]
No Image or Wrong image!
Loading...[PC10IMG.zip}
No Image
Loading...[PC10IMG.nbh]
No Image or Wrong image!
There seem to be alot of PC10IMG.zip am I using wrong one? If so do you have a link for HTC Desire Z version?

Use one of the two that I made, dont use others, I linked them to you earlier, the instructions on how to flash is there as well.
The reason you are getting this message though is you either didn't name it right, its not on root of SD, SD is not formatted properly, etc
Sent from my Nexus 7 using xda premium

Up and running.
demkantor said:
Use one of the two that I made, dont use others, I linked them to you earlier, the instructions on how to flash is there as well.
The reason you are getting this message though is you either didn't name it right, its not on root of SD, SD is not formatted properly, etc
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for your help, from a person who just about understand which way up to hold phone
After following your links and all stages and then reinstalling Android Open Kang Project builds for HTC Vision, phone working again (For the moment).
But still trying to understand why this happened, as switching SIM cards should not do this.
So one I had finished setting up phone again I when back to some of your previous questions and comments.
re-tried "fastboot oem check_emmc_mid" result:
"<bootloader> Manufacturer ID, MID=45
<bootloader> eMMC should be Scandisk
OKAY [ 0.016s]
finished. toal time: 0.016s"
Which is different from last time (and was something you did not like before). Let me know I can make any other checks that might help someone else out of the same problem?

Can't say for sure why this happened but you had a severely corrupt partition on the emmc and phone wasn't even reading its id. Changing the sim shouldn't do this and it could have been some kind of coincidence but I've heard others say the same thing before so.... Your guess is as good as mine.
Glad its all working!
Sent from my Nexus 7 using xda premium

Try reflashing the baseband changer.zip and then the simunlock.zip after changing the SIM Cards.

Stock HTC M9 stuck on HTC splash screen after battery died

[Unsolved] Phone sent to HTC service.
Hey Guys,
I'm back again and this phone is breaking my heart. My phone is still stock from the last time I had a similar problem.
My battery died, when I plugged it back in and hit the power button it powered up as far as the splash screen and hangs there.
When I go into recovery mode the log says
Supported API: 3
handle_cota_install: install cwpkg to /cache/cota/cwpkg.zip
handle_cota_install: install cwprop to /cache/cota/cw.prop
E:Fail to open file: /sys/devices/platform/android_usb/host_mode
Write host_mode error handle_cota_install: Can't mount /sdcard
I've tried clearing the cache/partition and rebooting but I'm in work and don't have access to save my info so I don't want to factory reset yet. Is there any thing else I can do or am I stuck with doing a factory reset ..... AGAIN!

Jamballs said:
Hey Guys,
I'm back again and this phone is breaking my heart. My phone is still stock from the last time I had a similar problem.
My battery died, when I plugged it back in and hit the power button it powered up as far as the splash screen and hangs there.
When I go into recovery mode the log says
Supported API: 3
handle_cota_install: install cwpkg to /cache/cota/cwpkg.zip
handle_cota_install: install cwprop to /cache/cota/cw.prop
E:Fail to open file: /sys/devices/platform/android_usb/host_mode
Write host_mode error handle_cota_install: Can't mount /sdcard
I've tried clearing the cache/partition and rebooting but I'm in work and don't have access to save my info so I don't want to factory reset yet. Is there any thing else I can do or am I stuck with doing a factory reset ..... AGAIN!
Click to expand...
Click to collapse
If you can get into bootloader or download mode try "fastboot erase cache"

Thanks for the suggestion thicklizard, I'll give it a shot when I get home and update the post.
Thanks!

?
You unlock Bootloader ,make Root or Soff ? Can you use warranty in HTC.
If u can go to Bootloader you can use Erase option ,or if is RUU for yours Htc verion you can flash to stock.
I dont know what is in without root and unlocked bootloader :/
I always have Unlocked bootloader ,Soff ,root and latest TWRP
If u have TWRP you can flash Rom for yours Firmware version
Sorry for my ENG

Well after a good few hours at the phone last night I'm still in the same position. My hands are a bit tied as I still have S-On but I don't know if I can even get S-off while stuck where I am. I can get in to bootloader/download/ recovery. Have tried Thicklizards suggestion above which didn't work, have also tried a hard reset. Also tried to flash a new recovery image but the error which popped up told me that I can't flash that partition with S-On. I have tried to run a RUU but I may have downloaded the wrong one, also the error which came up during install was that the battery was below 30%, I'm assuming that's an issue as I'm trying to run it from bootloader, I've tried looking around and I can't find any resource that would tell me if trying to run the RUU from bootloader would cause that error. Ive also tried to run the RUU as an image on the SD card but I got an error 99 that said I had a failure with the RU. I'll be away from my laptop for 2 days now but when I get back I'll try this RUU from Nikolay82, I don't know how I missed it before http://forum.xda-developers.com/one-m9/help/htc-one-m9-3-35-401-12-ruu-installer-t3318517. The only issue is that this is an upgrade to 3.35.401.12 and I'm already at 3.35.401.12. The struggle continues.

If your bootloader is locked you can't flash a recovery, is it looked or unlocked?.
but you can try to flash the OTA, still you're with 3.35.401.12, by Nikolay82's method...

bzhmobile said:
If your bootloader is locked you can't flash a recovery, is it looked or unlocked?.
but you can try to flash the OTA, still you're with 3.35.401.12, by Nikolay82's method...
Click to expand...
Click to collapse
Bootloader is unlocked, I did actually try to lock it again using fastboot oem lock and it failed with "unknown command". I think I'll send it away for repair this time instead of fixing it myself again, but that means my phone will be gone for who knows how long.

For the fastboot command, do you have open terminal windows from the fastboot folder?

bzhmobile said:
For the fastboot command, do you have open terminal windows from the fastboot folder?
Click to expand...
Click to collapse
Hi BZH yes I was opening the terminal from the fastboot folder. Fastboot devices command and a few other fastboot commands were working but any fastboot oem command wasn't working.

still searching where the mistake is coming from ???

Jamballs said:
Bootloader is unlocked, I did actually try to lock it again using fastboot oem lock and it failed with "unknown command". I think I'll send it away for repair this time instead of fixing it myself again, but that means my phone will be gone for who knows how long.
Click to expand...
Click to collapse
Could try fastboot oem relock

Thanks for that Thicklizard, That didn't work either I'm afraid. The phone is off to HTC service now so we'll see what comes of that. I'll mark this thread as solved ... or rather unsolved.