Develop Bugs

Phone gets stuck on bootloader?

Ok all,
I'm a dev. I compile kernels, AOSP, cook roms, etc. Which is why I feel so stupid lol Whenever I try to boot into recovery from my phone I hold in the power and vol down keys. This loads up the bootloader and then I reboot into recovery from that menu. This worked for the longest time. Now however, whenever I try this it stalls when it checks for PC36DIAG.zip, the first one it looks for. I don't understand why. Whenever I try to do adb shell reboot recovery it works flawlessly. But it would be useful to boot into recovery without a pc or adb. Any ideas why this is happening?

Same thing happens with me and its annoying I agree. I don't know why it checks for that image each time:/
Sent from my PC36100 using XDA App

imaxreed said:
Same thing happens with me and its annoying I agree. I don't know why it checks for that image each time:/
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I know why it checks for that image. It checks for a number of them. HTC's bootloader checks to see if those images are on the sd card so you can flash them. It's how the RUUs work. Thing is it's supposed to check and if the zip file doesn't exist it's supposed to move on to the next one. Unfortunately this doesn't happen. I'm wondering, is it the engineering bootloader we flashed? Maybe there's a bug in it?

[Q] Screen broken, how to flash a new ROM through recovery?

The screen of my HTC Desire (Gsm, slcd-version, I believe) got hit, and broke. The touch digitizer was broken but works, lcd is black. I bought a new (s)lcd screen (should be slcd, like the original one), but no picture there either. After it broke unlocking it would make the edges of the screen flash green.
Is the main board broken (I couldnt see clear physical damage), did I assemble it wrong (tried two time in case of some cable left loose), or could my new display be broken?
Phone does boot up, sound, wifi, buttons, and even the somewhat cracked touch digitizer do work, so its not that it gets stuck in boot or anything. I have tried some of those functions by taking a screenshot with adb, and the estimating where I have to tap the screen.
Q1. Is there any hope to revive the screen? I have pretty much given up on the screen though...
I have thought of using it as a part of a UAV-project(GPS,camera,Acc and gyro sensors,... Pretty nice ). The problem is that I would like to interface it to some other hardware using the Accessory Development Kit, which requires 2.3.something, and my Desire is 2.2. I have tried to flash CM7 using various tools without success (Hard without the screen). My phone was, and is rooted though. It has CWM 2.x.x(I don't remember the exact ver).
Q2. What is the preferred way to flash a new ROM without access to the screen?

updated
I've updated the questions to be a bit clearer...
Anyone?

Take a look at ..
http://tjworld.net/blog/htc-desire-tear-down
Hope it helps
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
Its for a AMOLED screen, but might give you some pointers.

There is only one cable that connects the screen to the main board, so I don't believe assembly is the problem... Do you think putting it into a oven for a while to reflow the solder would help, in case it is the connector that is the problem? In case the board is electronically broken there is not much I can do
Sent from my Nexus S using XDA App

I read from somewhere about it being possible to make some kind of script for the recovery to execute. I think some tablet had such script installed at the factory to keep users from accessing the recovery-menu manually. Can I do this with CWM 2 to make it flash a rom without user interation, and if possible, where could I find instructions on how to do it?

To flash a new rom you could execute the steps on another phone, write them down and do it on your phone - as long as the volume and power buttons still work. Or just use the 2.3.3 RUU, if you don't need root for your plans.

muellersmattes said:
To flash a new rom you could execute the steps on another phone, write them down and do it on your phone - as long as the volume and power buttons still work.
Click to expand...
Click to collapse
Nobody I know has a android phone with CWM, so I can't really do that... I tried to google for images and etc., but cant really find enough. Have the menus changed from CWM v2 (compared to v5)?
muellersmattes said:
Or just use the 2.3.3 RUU, if you don't need root for your plans.
Click to expand...
Click to collapse
I don't think I will need root, but the library I'd like to use is introduced in 2.3.4, so anything below that will sadly not work.

Use this guide:
http://forum.xda-developers.com/showthread.php?t=1096430
It's pretty old, but might still work. There's another similar guide somewhere (read it lately), but i can't find it now.
If you have a Nexus S, look at its recovery, the menu items should be the same. (reboot now, apply update ...)

muellersmattes said:
Use this guide:
http://forum.xda-developers.com/showthread.php?t=1096430
It's pretty old, but might still work. There's another similar guide somewhere (read it lately), but i can't find it now.
If you have a Nexus S, look at its recovery, the menu items should be the same. (reboot now, apply update ...)
Click to expand...
Click to collapse
I dont see that guy telling what recovery he is using, it wont work if its not the same one?
I do have a nexus S, but have the menus changed in different versions of CWM, because my NS has v5.something and Desire was v2.something?

Then just flash the same version of cwm onto the desire? Don't need a display for that...

muellersmattes said:
Then just flash the same version of cwm onto the desire? Don't need a display for that...
Click to expand...
Click to collapse
Of course! I didn't think
I have never installed a recovery to a phone that has already been unlocked, so every time I have flashed a recovery, it included unlocking the bootloader or something similar, and required some kind of interaction on the phone. I guess that is the reason why I never even thought about updating the recovery.

I just saw that fastboot can also flash an update.zip. The command for that would be
Code:
fastboot update <update.zip>
(replace <update.zip> with actual filename.) Don't know if that works well, but you might give it a try.

muellersmattes said:
I just saw that fastboot can also flash an update.zip. The command for that would be
Code:
fastboot update <update.zip>
(replace <update.zip> with actual filename.) Don't know if that works well, but you might give it a try.
Click to expand...
Click to collapse
Thanks, will try that later...

muellersmattes said:
I just saw that fastboot can also flash an update.zip. The command for that would be
Code:
fastboot update <update.zip>
(replace <update.zip> with actual filename.) Don't know if that works well, but you might give it a try.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img -> Fails because image is not signed (is my phone s-on?)
fastboot update update-...-desire.zip -> errorackage has no android-info.txt or android-product.txt
tried to run unrevoked3 to s-off, flash recovery and so on... -> Internal error: installing package failed

varesa said:
fastboot flash recovery recovery.img -> Fails because image is not signed (is my phone s-on?)
fastboot update update-...-desire.zip -> errorackage has no android-info.txt or android-product.txt
tried to run unrevoked3 to s-off, flash recovery and so on... -> Internal error: installing package failed
Click to expand...
Click to collapse
On which stage do you get Internal error: installing package failed?
Did you manage to S-OFF your device?

Alaa said:
On which stage do you get Internal error: installing package failed?
Did you manage to S-OFF your device?
Click to expand...
Click to collapse
Something about "installing service" flashes on the screen before the error...
EDIT: Still FAILED (remote: signature verification fail)
Sent from my Nexus S using XDA

Does anyone have any ideas?
Am I doing something wrong, or is my phone broken somehow?

As your display does not work, you can't tell if you're s-off, right? But you could try to run AlphaRev again to make sure. Unr3voked just roots.
Looks like the fastboot update command is not designed for recovery flashable images. As said, i never tried.

muellersmattes said:
As your display does not work, you can't tell if you're s-off, right? But you could try to run AlphaRev again to make sure. Unr3voked just roots.
Looks like the fastboot update command is not designed for recovery flashable images. As said, i never tried.
Click to expand...
Click to collapse
Well atleast "fastboot getvar security" returns security: on, so I guess I am still s-on. I thought unr3voked also s-offs. Atleast that is the utility I used to flash a custom recovery and root a completely stock phone. I have never used AlphaRev, but I'll look into it...

[RECOVERY]TeamWin Recovery Project - TWRP Touch [v2.2.2.1]

Here is TWRP v2.2.2.1 recovery i made from source
Problems:
---When installing ROM or making backup if text goes over screen recovery doesnt go into new line
---Formatting takes ages, if you dont want to wait go to settings and check use rm -rf instead of format, it should give you the same effect
---You tell me
How to install:
---Download the .zip and put it on your SD card
---Reboot to recovery
---Flash the .zip
---Reboot and say hello to your new recovery
Credits:
---TeamWin
---Cyanogenmod (Used their android_device_htc_hero)
---Shelnutt2 (Taught me how to compile something from source)
---My laptop for giving me it's processing power to build this
Download links:
---19.Sep.2012
http://www.mediafire.com/?glxal7xhmokrrln
Screenshots:

I already did this?
But good job anyway

Yes you did, but that was v2.2.2.0 this is latest build 2.2.2.1 and it's built from source, sorry if i offended you

No no its fine
I'm glad you did it
Oh and I may have fixed the CM10 booting problems, but I wont spam this thread about it

jordfaz said:
No no its fine
I'm glad you did it
Oh and I may have fixed the CM10 booting problems, but I wont spam this thread about it
Click to expand...
Click to collapse
Will you please PM me about the way you did it so i can try too, btw i might try to compile CM9&CM10 from source..

Ill pm you tonight if it works, and I can't wait for you to compile CM9/10

jordfaz said:
Ill pm you tonight if it works, and I can't wait for you to compile CM9/10
Click to expand...
Click to collapse
Well i cant wait either, but im not that sure i can compile CM10, but CM9 i think it's doable

Did you managed to port it ??

Ye its on my Github, its in my signature, just zip it up and flash, havnt tested it yet though.

jordfaz said:
Ye its on my Github, its in my signature, just zip it up and flash, havnt tested it yet though.
Click to expand...
Click to collapse
I cant test it either, my Heros touchscreen is messed up, shows input even when im not touching it, im gonna try to fix it so i could continue development, btw can you PM me about the way you ported or you compiled from source

hi, kemoba,I've got problem here.
I flashed your TWRP touch recovery from CWM, booted into recovery everything works fine. Then i flashed the MTD zip file for CWM ( so stdupid~), which makes my hero bricked: I can't get into recovery mode since it was broken by flashing the MTD file, and can't boot into android system since the system is MTDed.
would you tell me is there some way for me to use adb command again? I think it is the only way to save my hero. Thanks.

Are you S-OFF-ed, to check power off your phone, unplug battery then replug battery, hold VOL-DOWN (vol=volume) + POWER, you will get a white screen with 3 scating androids, and the first row will say something like HERO CVT ENG S-ON or S-OFF. Second thing is, did you try to boot into recovery by powering down your phone then unplugging and replugging battery, press MENU+POWER at the same time and leave it pressed until you boot into recovery, it should boot into recovery after 30 secs to a minute if it doenst work hold it a bit longer just to make sure you cant boot into recovery. BTW, what MTD file did you flash, do you have a link to it ?

Actually it's HOME+POWER to boot into recovery, my bad

Hi, kemoba, thanks for replying. VOL-Down+power or HOME+Power or Back+Power didn't take me to the Hboot or recovery or fastboot, actually only a HeRO logo appear no matter which combination of Power key and some other key(except the vol-up+power one ,this makes three times shake and nonthing) . In short, I can't get into any supper mode, and feel hopless... BTW, ubuntu is my pc system, driver should not problem, and no matter which way to power up my hero, "lsusb" doesn't show up my phone, and "adb devices" shows nothing as well.
Here is the MTD file link:http://forum.xda-developers.com/showthread.php?t=1370963&highlight=mtd
Sorry for my bad english describe.
Any suggestion would be great, thanks very much.

Ummm, VOL-DOWN + POWER didnt take you anywhere ? Im sorry but i think you bricked your HBOOT, when your hero logo showes does it say anything like FASTBOOT USB at top left corner ??? And did you unplug and replug your battery when you tried VOL-DOWN + POWER

So sad to hear that. Volume-down+Power doesn't work, nothing appears but the hero logo. Is there some other key combinations to try? BTW, how to make hero communicate with PC if HBoot and recovery are broken?
Sent from my Transformer TF101 using xda app-developers app

JTAG is the only way, it is a tool that flashes stuff directly to nand memory, you will need to take apart your phone and solder some connections, not to mention you need to get a JTAG module and a JTAG flashable package.. BTW, do you get FASTBOOT USB on top right part when the HERO picture comes

I knew JTAG when i played with my modem some years ago, but since my laptop doesn't have any COM port, i have to send my phone to the repair shop. And only HERO picture appears no matter which key combination pressed, no "FASTBOOT USB" comes out. But thank you all the same.
BTW, TWRP touch recovery is good, great job. I will continue to use this recovery when i get my hero fixed.
And hey, will you take a look at the MTD file? can you port it to your recovery?

I will try to do it, just dont wanna brick my Hero, but im S-OFF so i should be fine, im glad you guys like TWRP you can check out Jordfazs version too. Its a bit older but i think it's less buggy Ill try to fix these bugs and also next version should include my ICS based theme.
Sent from my Hero using xda app-developers app

I get an error while flashing. says
E:Wrong digest: META-INF/com/google/android/update-script
E:Verification failed
any way to fix this and be able to flash? i'm getting this for every rom as well

[Q] Need help fixing my Gnex

Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike

Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.

AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.

So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.

AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong

Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide

nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.

beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.

mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.

Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.

Does anyone have an img with USB debugging enabled?

My LCD is finished, it's just showing horizontal lines, not sure why, there's hasn't been any sort of physical damage. I flashed the latest stock build through fastboot and still no change. I don't have debugging enabled, so I can't use adb. I read I could flash an img through fastboot that has debugging already enabled. Can anyone help me out with this? Thanks.

Does the screen work in fastboot or recovery? If not, the screen is done. I would recommend having that fixed first.

k.s.deviate said:
Does the screen work in fastboot or recovery? If not, the screen is done. I would recommend having that fixed first.
Click to expand...
Click to collapse
It's still messed up in fastboot and recovery, the colors change, but it still shows just lines. It actually seems like the image has been rotated, because when I press the volume keys I can see something moving, just not in the right orientation. I wanted to try androidscreencast, but I need adb working.

Personally I would just replace the screen. Seems like maybe the work your going to put into it would outweigh the benefit. What are you hoping to accomplish? If your wanting to transfer files you could just boot into recovery. (Assuming you have TWRP)

k.s.deviate said:
Personally I would just replace the screen. Seems like maybe the work your going to put into it would outweigh the benefit. What are you hoping to accomplish? If your wanting to transfer files you could just boot into recovery. (Assuming you have TWRP)
Click to expand...
Click to collapse
Possibly, though I'd have to find an OEM replacement screen and hope that the screen is the only issue. I'll probably end up selling it for parts. I've tried manually booting into recovery and it doesn't mount my internal storage or show in adb devices. I've flashed TWRP before doing that, but I honestly don't even know if it's booting into stock recovery or TWRP since I can't see anything on the screen.

What about using wugs toolkit to boot into TWRP. Then you could get files off, hopefully..

Is there any particular reason you haven't contacted Google for a replacement? I've read about this issue at least two times. In each case Google replaced the phones.
Sent from my Nexus 5X using Tapatalk

Just call Google..? There's no way you're out of warranty.

Totally slipped my mind! Just got a RMA. Thanks to all!