Develop Bugs

[Q] can't get past fastboot/bootloader

hello
i rooted my desire with Unrevoked, already turned my sdcard to Golden card earlier...
i tried to install (the downgrade of ps3) .img file on it in the recovery mode... as i was reading on a site that you need to install it through recovery mode...(later i found out you need to install it through pc) since i'm an idiot i tried all possible features in the recovery mode... i clicked on format boot, and since then i can't get past fastboot/bootloader. (I still have access to recovery mode). i tried rerooting it with unrevoked but in fastboot/bootloader adb devices do not recognise phone. It is recognised in recovery mode (adb devices) - but unrevoked says: Device */sbin/sh: getprop: not found* is not supported at this time. I don't really know what to do to get it to normal mode. Also tried factory reset = clear storage but same story. I know i should have back-upped, but what's done is done and i guess i learned the hard way. Anyway hopefully you can help me.
ps: i read the similar title threads but no useful information to resolve this

Well, you say you can get in recovery, so did you try then to put a rom on the SD and flash it?

thanks for your help works like a charm

Good to hear that but it was a rather an obvious solution.
The hard part was to read the whole post .

i tried to be specific in order the sollution wouldn't be as simple as that

have another question ... i'm trying to flash the ps3 downgrade img through fastboot. But i always get the message:
sending .......... OKAY
writing ˙recovery˙... INFOsignature checking...
FAILED <remote: signature verify fail>
what is wrong?

What recovery are you using?
If you go s-off you shouldn't get this error as far as I know.
Look in development for s-off guide.

i'm using ClockworkMod Recovery v2.5.0.7
i don't know if that's a must but i can only begin with flashing when i'm in fastboot usb mode in other mods (recovery and normal mode) i get <waiting on device> message

[Q] problem on flashing custom recovery

I want to flash ra-desire-v2.0.1.img recovery . I tried some methods such as fastboot and flash_image but I can't flash it .
The error on fastboot method is : "FAILED <remote: signature verify fail>..." and on flash_image method is : "no space left on device.... " .
Plz help me to solve this problem because I need a custom recovery. Thanks.

"no space left on device" probably means that you can't write to recovery. Is the device rooted?
If your device is not rooted yet, instructions are here: http://forum.xda-developers.com/showthread.php?t=788044.
Also, please check that you have the proper USB drivers installed. You can get them by installing HTC Sync (or by following instructions above).
Finaly, I did get a similar error message once when writing a new radio image through a .zip. That was because I was using an alternate partition table and there probably wasn't enough space on whatever partition the thing used for temporary storage. If that's your problem then flashing through fastboot should still work.

martijn_bakker said:
"no space left on device" probably means that you can't write to recovery. Is the device rooted?
If your device is not rooted yet, instructions are here: http://forum.xda-developers.com/showthread.php?t=788044.
Also, please check that you have the proper USB drivers installed. You can get them by installing HTC Sync (or by following instructions above).
Finaly, I did get a similar error message once when writing a new radio image through a .zip. That was because I was using an alternate partition table and there probably wasn't enough space on whatever partition the thing used for temporary storage. If that's your problem then flashing through fastboot should still work.
Click to expand...
Click to collapse
thank you for your reply.
my device is rooted and I've installed android drivers and full wiped my phone so I should not have a space problem. the message I got in fastboot method is :
"remote : signature verify failed"
what can i do?

Flashing via fastboot requires S-off, i believe you can change recovery with unrevoked if you are still S-on.

TheGhost1233 said:
Flashing via fastboot requires S-off, i believe you can change recovery with unrevoked if you are still S-on.
Click to expand...
Click to collapse
Yesss. that's it. thak you very much for your help. I did S-off and then flash custom recovery with fastboot command. thanks again.

[Q] Bricked T-Mobile G2?

My mom brought me her phone last night because it's stuck in HBOOT. It refuses to boot into anything except HBOOT, and the keys are unresponsive in HBOOT.
I can't seem to find an uncorrupt PC10IMG.zip file to try flashing it, and any commands I send it through fastboot say completed or failed <status malformed>.
EG, fastboot reboot says it finished, but the phone doesn't reboot. Fastboot reboot-bootloader gives me the status malformed error.
Any ideas?
edit: the Shipped ROMs website zip is corrupted. Windows won't open it, and when I tried it in fastboot, it said "failed to access zipdata in <random ascii string>". I'd appreciate it if somebody could link me to a PC10IMG.zip of the official 2.3 rom.
edit2: Never mind. This thing's fragged, I give up.

The PC10IMG.zips will always say corrupt in windows as they are signed, and windows explorer does not handle signed zips at all.
You can use a program like 7zip or winrar to open them up.
You should probably check the md5 of the zip before flashing, to make sure it isn't corrupt.
-Nipqer

The MD5 matches, but the phone won't flash them for some reason. It pauses on the PC10IMG.zip when it goes through the list, but it won't flash and just goes right back into HBOOT.

Maybe try flash it via RUU mode.
Check the 'fastboot downgrade' method in this guide for instructions on how to do it.
-Nipqer

Nipqer said:
Maybe try flash it via RUU mode.
Check the 'fastboot downgrade' method in this guide for instructions on how to do it.
-Nipqer
Click to expand...
Click to collapse
Unpossible; ADB doesn't see the device when it's in HBOOT and it won't boot into anything else.
I think the eMMC is fragged.
Stupid refurbs. Also, all fastboot commands return "Failed (status malformed)". I tried updating the HBOOT using the file from htcdev.com, but it just says the battery isn't charged enough even if I charge it while off till the green light comes on.

[Q] Incredible boot loops at white screen, tried many things

I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51

GreyhoundX said:
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
Click to expand...
Click to collapse
I would flash an ruu thru hboot and then do a factory rest from hboot. Then if it boots fine flash cwm recovery thru hboot and then the su binaty thru recovery to regain root. Once you have recovery working again then flash back to cm7 or another rom of your choice thru recovery.
Or you could try to just reflash cwm recovery thru hboot, and then if you can access recovery wipe everything in mounts and storage except sdcard and emmc, and then restore a nandroid or flash a new rom.
RUU's - http://pvillecomp.com/?page_id=22
Latest cwm recovery - http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
Latest su binary - http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
How to flash with hboot - http://pvillecomp.com/?page_id=79
You may also want to upgrade to the newest radio 2.15.10.07.07 - http://pvillecomp.com/?page_id=18

I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07

GreyhoundX said:
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
Click to expand...
Click to collapse
Try flashing the recovery and then see if you can access it.
If you have adb setup and have fastboot, you can try to erase the recovery partition by typing " fastboot erase recovery " without quotes into a cmd prompt on your pc. And then flash the recovery from above. Sounds like something is either messed up with your boot or recovery partition or img.
You can also try to use fastboot to erase the boot partition " fastboot erase boot " and then try an ruu again.

I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.

GreyhoundX said:
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
Click to expand...
Click to collapse
That red triangle is the stock recovery, try to do a factory reset now or try the sugestions i added to the post above.

Factory reset doesn't work. It shows me a phone with a green circle then goes into the boot loop.
I'll try the ADB stuff later today when I'm back from work. I've never used it before. Thanks so much for helping.

How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.

GreyhoundX said:
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
Click to expand...
Click to collapse
Adb will not work in hboot but fastboot will. You can use adb in recovery though, not just booted to the os. The error device not found is probably because you were trying adb from hboot, or because you dont have the correct drivers on your pc. Adb and fastboot are 2 different programs, fastboot is not an adb command. If you need the fastboot.exe file or the drivers you can get them here. http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip

I ran "fastboot erase boot" and it said "erasing 'boot'...FAILED (remote: not allowed)". Can I try running or flashing something else?
If I run "fastboot devices" it shows my device ID with fastboot next to it so I know it's connecting.
Thanks for putting up with this, can't imagine what caused this.

Hmm not sure, seems it may be some sort of hardware issue or disk failure. If you cant get it to boot after an ruu, and you cant factory reset or access a custom recovery or get fastboot to erase or flash, im not sure what else you could do. My only other sugestion would be to try the ruu.exe that you do from your pc with the phone connected. Flash the stock recovery PB31IMG.zip first before doing so as i believe its required for the ruu.exe. It may work and it may not im not exactly sure how the ruu.exe works as i have never used one, but i believe you just boot into hboot and then run the exe on your pc.

I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?

GreyhoundX said:
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
Click to expand...
Click to collapse
Take a PB31IMG.zip ruu ( http://pvillecomp.com/?page_id=22 ) and rename it update.zip
Put the update.zip file on your pc in the same folder as the fastboot.exe file. (Where adb is installed)
Boot into hboot with the phone pluged in to the pc. Make sure it says fastboot in red at the top of the hboot screen.
Open a cmd prompt to the directory where fastboot.exe is (eg C:\ADB\)
Type without quotes " fastboot update update.zip " and hit enter.
Here is some good info on fastboot.
http://wiki.cyanogenmod.com/wiki/Fastboot

Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'

GreyhoundX said:
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
Click to expand...
Click to collapse
Use 7-zip, winzip and winrar dont work the best for android files.

Think I'm just going to give up on this one since the flashing doesn't work...what a hassle. I wish there was some diagnostics tool that would just tell me if the phone is physically broken.

[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix

[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix
Hey,
I have a ZE551ML and want to install CM. I am following the guide here. I have run into a problem on the first step which points to the guide here. At step 7 of this guide it has me use the command: fastboot flash system system.img. This fails with the error in the title of this post: FAILED <remote: Permission denied>. I have been googling this and no one has a concrete solution. Currently my phone will not even boot as the three fastboot commands before this one worked just fine and replaced the files. Any help would be greatly appreciated!
Cheers,
Eric.

Even though it'll say permission denied, flashing recovery WILL work. From there you can either flash a custom ROM (from twrp) or reflash stock firmware (through stock recovery).
That's the only fix I've found. To flash a usable ROM and boot into it. May need to turn on USB debugging in dev options. But after doing those two things, fastboot will stop with the permission denied issues.

Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.

eric_lensherr said:
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
Click to expand...
Click to collapse
Found a guide here dealing with this error, working on it.

Hey,
So I got my phone unbricked by flashing the recovery with the stock ASUS firmware "ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V2.19.40.22 for WW SKU only" available at the ASUS official website and following a guide at an outside link that I can't post.
Now, I have enabled developer mode and turned on USB debugging but am now getting the permission denied on all fastboot commands of the OTA guide, step 7.
Does anyone know a good next step?

Hey, managed to root the phone with: Temporary CWM

After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!

rlaw said:
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
Click to expand...
Click to collapse
Yes, I did do this but I have now checked the check mark to make it always trust my computer. I then booted into fastboot but still get permission denied despite having root through CWM and having this checked off.
When I got root through CWM by the fastboot tethered recovery it gave me permission denied on all steps but it still booted into CWM recovery. I was then able to install SuperSU to root it, though it gave me an error, and I used Root Checkerr to see if the phone was rooted. It says it is but I am still unable to flash any images onto the phone since I re-installed the stock firmware.
I'm super confused about this whole thing, IDK what to do now.

Flash stock recovery again and adb sideload the stock firmware all over.
This is the latest up-to-date 2.20.40.59 firmware: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.59-user.zip
If that doesn't work then idk. You can Google the permission denied errors for fastboot like I did and there are various possible problems/solutions.

So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.

eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.

rlaw said:
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
Click to expand...
Click to collapse
How can i tell if twrp recovery is successfully installed?

Hey, took a few days to cool off.
So it does seem I can replace recovery even though it says permission denied. I do this by using fastboot to flash the recovery, then from the bootloader on the phone I select restart bootloader and then when the bootloader re-appears I enter recovery mode ( I do this to prevent the possible replacing of the custom recovery by the stock OS). However recovery mode never boots when the latest twrp recovery is on the phone, I just end up back in the bootloader. When I flash the stock recovery back on this method successfully enters recovery mode. This also occurs if I just directly enter recovery mode after flashing twrp recovery.
Any thoughts?

eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
Same here. I'm using elevated cmd, and fastboot is recognizing my device. But I can't flash anything, can't erase cahce, can't reformat partitions. Always failed due to permissions. And I'm stuck in a bootloop, and can't get to recovery (it just goes back into the bootloop when I try). Literally the only avenue I have to interact with this phone is fastboot, and I can't do anything with it.