Develop Bugs

EVO Bricked? Please Help

I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….

Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk

What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw

did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.

@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted

Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com

Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.

Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse

Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...

Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse

Yes your just not rooted anymore. Run whatever process worked for you the first time

Try whitslack's method.
EDIT: Nevermind, no can do.

What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse

xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first

Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse

I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse

latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!

Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!

Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse

I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse

Some assistance is requested

Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!

If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.

robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV

the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....

master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not

You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse

master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..

You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse

master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.

I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse

master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?

It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse

master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!

Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.

Stuck in boot, Will pay whoever solves the issue and provides me a step by step fix

Hello,
I'm looking for help as I have exhausted all of my search on google and xda developers and the answer doesn't seem to be there. I'm afraid I might be unable to get out of this one.
I have a huawei ascend P6-U06 I bought it and it came with the international firmware, I had rooted it and flashed miui v5 into my phone, everything was fine but one thing, I was unable to use themer, so about 3 days ago I finally decided to flash omni rom.
I downloaded omni rom and installed CWM recovery and once into the system I selected the zip from my sd card and flashed it, only to find that the phone would not go pass the first screen (stuck in boot and could not be shutdown or anything)
Since I did not do a TWRP recovery (and I don't know how, I'm just a beginner) I was unable to do anything other than the "3 button method" so I looked and found that I could put the UPDATE.APP file on the dload folder and it should work, so I tried it and the UPDATE.APP firmware version is the B125, all good I think this was the Chinese version but it had English and other languages as well, but Chinese seemed to be the main one.
Anyways I had the phone back and it did an update, after the update everything was working fine, I deleted the dload file from the sd card, also I saw that the "system" or the phone itself created a dload file on the internal storage but then once I had themer on the phone I saw myself that I hated the emotion ui and in the first place that was the reason I had put miui into my phone, I still wanted to try omni rom and persistently I tried a second time.
Now this time since I already new that I could just do the dload thingy I thought (what could happen) so I tried again with CWM to flash the omni rom (the latest version) but it gave me an error saying something like the installation was aborted or something like that.
So I went back to having the phone stuck in boot, I put the B125 UPDATE.APP and created a dload folder on the sd card, but when doing the "3 button method" the system gave me an error, I tried downloading the B122 and the B132 and also the B510 but although I have put the UPDATE.APP on the dload folder it just doesn't do it's magic like it previously did.
Now I don't really have money to buy another phone, if I did I would just buy another one (I like the p7) but I don't so I need to fix this issue otherwise I don't have a phone.
The error I get first it gives me some sort of error which disappears once the Android system recovery menu comes up. then the only thing I'm able to see says:
Checking Module MD5RSA.. OK
Checking Module CRC.... OK
Checking Module CURVER.... OK
Checking Module VERLIST....
Huawei SD card update fail.....
cust copying files...
copy cust files successed!
===================
FAIL
===================
Please help me, I'd appreciate if you can do your best explaining as I'm dumb in this matter, (just a beginner as said before) Also I'm attaching a picture of the error message being received when entering the system recovery through the "3 button method"
And as I said on the tittle, I will pay whoever helps me to solve this issue, I need a step by step (with a good explanation if possible) on how to fix it, I will pay $60 via paypal to the person that provides me with the solution.
Thanks for all of your time, I DO appreciate your help and if you have any questions please just ask! I really need to fix this!

Ok, first of all, your picture shows that you already have the KitKat recovery.
Which version of B510 have you downloaded? Is it the update.zip? I'm assuming it is...
Please download the complete update package from here: http://www.huaweidevice.ro/user/con...001C00B510_Firmware_Android 4-4_EMUI--2-3.zip
That is the official, and full firmware update from Huawei Romania.
Once your download has completed, unzip the zip file, and copy the dload folder onto your sd card.
BEFORE placing your sd card back in your phone, try the 3 button method again. You should get into recovery mode, then do a data/factory reset, and clear cache.
Once that is done, put your sd card back in your phone, reboot your device, and reboot using the 3 button method.
Hopefully this will work.
If it fails again, you need to try formatting your sd card, and do the steps above again, without doing a factory reset.

Dear op.... Did you solve your problem? How?

miz_pimp said:
Ok, first of all, your picture shows that you already have the KitKat recovery.
Which version of B510 have you downloaded? Is it the update.zip? I'm assuming it is...
Please download the complete update package from here: http://www.huaweidevice.ro/user/con...001C00B510_Firmware_Android 4-4_EMUI--2-3.zip
That is the official, and full firmware update from Huawei Romania.
Once your download has completed, unzip the zip file, and copy the dload folder onto your sd card.
BEFORE placing your sd card back in your phone, try the 3 button method again. You should get into recovery mode, then do a data/factory reset, and clear cache.
Once that is done, put your sd card back in your phone, reboot your device, and reboot using the 3 button method.
Hopefully this will work.
If it fails again, you need to try formatting your sd card, and do the steps above again, without doing a factory reset.
Click to expand...
Click to collapse
I tried it but it's still not working. :/

blackrose1 said:
Dear op.... Did you solve your problem? How?
Click to expand...
Click to collapse
I"m still looking for a solution, actually it's been so long that I'm offering to pay whoever provides me with the solution

Try what I did here to solve a similar problem that I had: http://forum.xda-developers.com/showpost.php?p=54124890&postcount=18

sko4a said:
Try what I did here to solve a similar problem that I had: http://forum.xda-developers.com/showpost.php?p=54124890&postcount=18
Click to expand...
Click to collapse
I have a question, how can I install TWRP if the adb fastboot is not recognizing my phone? I think it's because I'm missing the drivers but I haven't been able to find them.

DanRioja said:
I have a question, how can I install TWRP if the adb fastboot is not recognizing my phone? I think it's because I'm missing the drivers but I haven't been able to find them.
Click to expand...
Click to collapse
Don't you just need Hisuite, the driver who comes with the phone when you plug in your USB cable? That made asb fastboot to recognize my phone at least.

You don't need ADB, only fastboot. Shut down the phone. Then hold the Vol- button and plug in the usb cable. Release the button after the you see the AscendP6 logo - now you are in fastboot and can flash TWRP. Windows Update should install the drivers (I've never installed HiSuite), just let it search online.

First delete your sd card to FAT32 not NTFS and put update.app to dload folder. then dowbload: http://forum.xda-developers.com/showthread.php?t=2765202
Power up your phone with volume down. and use Huawei tool kit from that link. select KitKat , unlock bootleder first from dropdown menu, then install stock recovery.
And try to update from stock recovery "3 buttons method"

ADHDDHDA said:
First delete your sd card to FAT32 not NTFS and put update.app to dload folder. then dowbload: http://forum.xda-developers.com/showthread.php?t=2765202
Power up your phone with volume down. and use Huawei tool kit from that link. select KitKat , unlock bootleder first from dropdown menu, then install stock recovery.
And try to update from stock recovery "3 buttons method"
Click to expand...
Click to collapse
Hey so far this is the most promising option I've gotten, the only problem is when I go to unlock bootloader it's giving me an error that says "error phone not connected" I've tried getting the drivers from many different ways, one from the hi suite, another letting windows look for it, the other one was I downloaded a .exe named "driver tools" but it doesn't work either, when I connect the phone it does make the sound just as when you connect any device on USB but other than that it doesn't recognizes it on the huawei toolkit. Any ideas?
sko4a said:
You don't need ADB, only fastboot. Shut down the phone. Then hold the Vol- button and plug in the usb cable. Release the button after the you see the AscendP6 logo - now you are in fastboot and can flash TWRP. Windows Update should install the drivers (I've never installed HiSuite), just let it search online.
Click to expand...
Click to collapse
I only get to see this screen: http://s3.amazonaws.com/f01.justanswer.com/JACUSTOMERd2wl5hbc/2013-01-26_122110_huawei.jpg
Tungieee said:
Don't you just need Hisuite, the driver who comes with the phone when you plug in your USB cable? That made asb fastboot to recognize my phone at least.
Click to expand...
Click to collapse
I've tried with the hi suite, downloading a .exe driver named "driver tools" and having windows look for the driver, but it doesn't recognizes it, I mean when I connect the phone it does make the sound when you're connecting something but other than that the adb is not recognizing the phone.

I had a similar problem but for me it would say verlist fail. However you should try this anyway if you haven't already: http://forum.xda-developers.com/showpost.php?p=52744051&postcount=23
What is important is that you use the recovery in that specific post. That's what fixed it for me.

blacklord9 said:
I had a similar problem but for me it would say verlist fail. However you should try this anyway if you haven't already: http://forum.xda-developers.com/showpost.php?p=52744051&postcount=23
What is important is that you use the recovery in that specific post. That's what fixed it for me.
Click to expand...
Click to collapse
I have a question, how can I flash the stock recovery? I mean I have tried with the adb fastboot but it doesn't recognizes the phone :/

Try this methode, it defently works!!! I had EXACT the same problem! P.s. You dont need to flash a other recovery!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2781977

HTC One M9 Down - Need Help

HI all. I am in serious need of help please.
My wifes M9 is stuck on a screen with only a backlight. How this came about is after several failed attempts of updating the system via Wi-Fi. South Africa does not have a RUU available and only over the air updates are available
After about 2 days on the net, searching and reading and trying and failing I have determined the following.
What I have tried
1. Boot to Bootloader and tried recovery. This give me an Error - "Failed to boot to recovery"
2. Tried a Official RUU from HTC, this failed due to CID - Error wrong Customer ID
3. Learned a bit of ADB but this is no use as It seems USB debugging is disabled on the phone
4. Tried Custom ROM's via the SD card but this is blocked as the phone is **Locked** and **S-On**
5. Fastboot sees the phone as I can push reboot commands but because of locked status I can not do much
6. I can not get a unlock token as OEM is locked and this must be unlocked for ADB command to get token to get unlock.bin from HTCDEV
Basically it seems like I am at a dead end as it appears that I need to get into a boot status to enable debugging and enable developer mode from phone settings to be able to work from ADB
So here is the Million dollar question, How can I "wipe" the phone with a SD card boot image/loader or does any one know of a RUU-.exe for South Africa CID_016 that I could flash the phone with or possibly any other methods to get a ROM on it that we can use it again
I repeat, phone goes to blank screen with only backlight after HTC Logo, S-on, USB debugging seems to be disabled and it is in Locked status. I am able to boot in download mode and bootloader and fastboor does see the device. ADB devices does not see the phone, even after trying loads of different drivers, ADB USB ADB Interface etc etc
Please I need help

I'm suffering from the same fate. Except I had rooted it before, then I tried to update it to 5.1 and I relocked my bootloader. Android 5.1 loaded successfully but it got stuck while booting and now I can't unlock my bootloader. I have tried EVERYTHING!

https://www.google.com/url?q=https:...261000&usg=AFQjCNEBlBxkVmymaiJO1eaxKcHsKsE-wg
1.download this zip file
2. Rename the file to 0PJAIMG.zip (zero not O)
03. Copy the file to the root directory of a SD card which is formatted to fat32
04. Put the card into your phone and boot to Download Mode.
05. You will be asked whether you want to flash the file. Confirm with the volume up button.
06. Your phone will reboot at least one time. Depending on your current firmware version it may reboot to Android instead of rebooting to Download Mode. If this happens you just need to shut your phone down and manually boot it to Download Mode.
07. Flashing may take some time.
08. At the end you will be asked to push the power button. You phone will shut down if you do so.
09. Wait some seconds and then turn your phone on, again.
10. First boot may take a while.
11. Congrats! thanks to flippy

YES!!! OP I tried this and it works!!! My phone is finally alive again thanks to flippy's instructions.

Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Thank you so much for taking the time to answer this Degerli43! I know virtually every answer possible is available on this forum, but finding it is the trick!
Note to anybody else doing this, be sure to locate the correct image file for your provider and area, as the link above and the one below may not be the correct one for you. I am a T-Mobile US customer and used this one -
https://www.androidfilehost.com/?w=...6ce7fb817fc1524b58f67fe05270f032107d2306abcd4
This worked perfectly after I could not boot or enter TWRP recovery. Anybody who can still access Android Recovery the Downloader should be able to use it to get un-bricked to a clean carrier state if the image file will take.

ksnax said:
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Click to expand...
Click to collapse
Did you ever visit the general section? :silly: There's a sticky thread with stock files and linked instructions for recovering TWRP backups and flashing RUUs. Read the OP, follow it's instructions to my google sheet and you will see where the steps that helped you out are taken from.
Sent from my HTC One S using XDA Labs

Helps with Download mode

Need some help on how to get the download mode back.
so i have HTC 10, Nougat. S-off and unlocked bootloader,
had some issues with my phone so i formatted the user data from TWRP, the went to flash the original stock ROM, something went wrong obviousely so now i lost the ability to get into download mode.
if i press the power and volume down the phone just gets stuck in boot screen, i can get into the bootloader and recovery (not the TWRP) by pressing power and both volume buttons, bot from recovery I seem to fail flashing the ROM again, it fails on the signature check and even via ADB i cannot boot to download mode.
Any advice on how to get this issue sorted. i want to get the twrp or reinstall the rom again.
PS placing the rom.zip on the SD card is not doing anything as the phone bypasses that step automatically
thanks in advance

Avo_GH said:
Need some help on how to get the download mode back.
so i have HTC 10, Nougat. S-off and unlocked bootloader,
had some issues with my phone so i formatted the user data from TWRP, the went to flash the original stock ROM, something went wrong obviousely so now i lost the ability to get into download mode.
if i press the power and volume down the phone just gets stuck in boot screen, i can get into the bootloader and recovery (not the TWRP) by pressing power and both volume buttons, bot from recovery I seem to fail flashing the ROM again, it fails on the signature check and even via ADB i cannot boot to download mode.
Any advice on how to get this issue sorted. i want to get the twrp or reinstall the rom again.
PS placing the rom.zip on the SD card is not doing anything as the phone bypasses that step automatically
thanks in advance
Click to expand...
Click to collapse
Go into download mode from bootloader.

yldlj said:
Go into download mode from bootloader.
Click to expand...
Click to collapse
I cannot, when i pick download mode it goes straight into a boot loop and gets stuck on the HTC logo screen nothing else happens

push vol down vol up and power

Since the computer can talk to the phone, I would try the RUU executable.
(hard to help troubleshoot not knowing what you did but flashing "original stock ROM" via TWRP is a problem)
If you're getting a signature check fail, investigate that. What file are you flashing? How are you trying to flash it? Does downloading it again and comparing the two show any differences (if there isn't a hash to verify it)?

Rolo42 said:
Since the computer can talk to the phone, I would try the RUU executable.
(hard to help troubleshoot not knowing what you did but flashing "original stock ROM" via TWRP is a problem)
If you're getting a signature check fail, investigate that. What file are you flashing? How are you trying to flash it? Does downloading it again and comparing the two show any differences (if there isn't a hash to verify it)?
Click to expand...
Click to collapse
thanks for your comment,
I will try the RUU method tonight and see if that makes any difference.
I was flashing the Original Stock ROM, but i did that from SD card not TWRP, but during the flashing the phone rebooted multiple times and then i ended up with this issue. i am pretty sure I am trying to flash the same file, but will check the Hash just to be sure.
the issue the annoys me is that i cannot access the download mode, if i could then i will flash TWRP again and restore from backup images i have.

I want to say there's a condition where you have to flash twice but I'm not certain on that but it wouldn't hurt.
The signature fail is a concern; hence getting a new file. Are you exctracting 2PS6IMG.zip from the RUU via the decrypt tool? That's what I've always done to ensure I have the correct file and intact.

Rolo42 said:
I want to say there's a condition where you have to flash twice but I'm not certain on that but it wouldn't hurt.
The signature fail is a concern; hence getting a new file. Are you exctracting 2PS6IMG.zip from the RUU via the decrypt tool? That's what I've always done to ensure I have the correct file and intact.
Click to expand...
Click to collapse
oh thanks for that tip, I used a zip file downloaded from easy-firmware.com
but tonight will try to extract from the RUU. will see how that goes.
really appreciate you taking time to respond

Avo_GH said:
oh thanks for that tip, I used a zip file downloaded from easy-firmware.com
but tonight will try to extract from the RUU. will see how that goes.
really appreciate you taking time to respond
Click to expand...
Click to collapse
Yeah, there's a lot that can go wrong there, like downloading the wrong one, the poster making a mistake, not to mention its an unknown source--especially since you're S-OFF.
Ensure you get the correct version from htc.

Rolo42 said:
Yeah, there's a lot that can go wrong there, like downloading the wrong one, the poster making a mistake, not to mention its an unknown source--especially since you're S-OFF.
Ensure you get the correct version from htc.
Click to expand...
Click to collapse
ok here is the latest development, wondering if anyone has any advise,
firstly extracting the file from the RUU and flashing it did not work. however i managed to find a little app called Windroid that allowed me to flash TWRP from the bootloader (without the need to go to download mode)
but I soon found out that the phone lost all its partitions. so i cannot wipe, format, install anything, but i can see a bunch of folders and filed via the TWRP file manager.
used ADB fdisk -lu I only see one single partition end was only able to remount /dev/block/mmcblk0p1.
any advice will be highly appreciated I am not sure how to proceed here
thanks in advance

Avo_GH said:
ok here is the latest development, wondering if anyone has any advise,
firstly extracting the file from the RUU and flashing it did not work. however i managed to find a little app called Windroid that allowed me to flash TWRP from the bootloader (without the need to go to download mode)
but I soon found out that the phone lost all its partitions. so i cannot wipe, format, install anything, but i can see a bunch of folders and filed via the TWRP file manager.
used ADB fdisk -lu I only see one single partition end was only able to remount /dev/block/mmcblk0p1.
any advice will be highly appreciated I am not sure how to proceed here
thanks in advance
Click to expand...
Click to collapse
If you're still in this trouble: -Search for your actual installed ROM (the firmware zip with a lot of other zips inside), deRUU it (search on google how to decompress a RUU) and flash via BOOTLOADER the hosd_signed.img image (this is "download" and "RUU" modes). You can boot to BOOTLOADER holding both volume buttons and power together (try more times if it wont boot).

vladmitra said:
If you're still in this trouble: -Search for your actual installed ROM (the firmware zip with a lot of other zips inside), deRUU it (search on google how to decompress a RUU) and flash via BOOTLOADER the hosd_signed.img image (this is "download" and "RUU" modes). You can boot to BOOTLOADER holding both volume buttons and power together (try more times if it wont boot).
Click to expand...
Click to collapse
thanks for the response, I want to try this method too, just wondering do you have any idea how to flash the file form bootloader, given i donot have fastboot, or more precisely fastboot would not see my device, but adb does. (but if I try to reboot to download/fastboot from adb the phone just goes to sleep)
thanks in advance

Avo_GH said:
thanks for the response, I want to try this method too, just wondering do you have any idea how to flash the file form bootloader, given i donot have fastboot, or more precisely fastboot would not see my device, but adb does. (but if I try to reboot to download/fastboot from adb the phone just goes to sleep)
thanks in advance
Click to expand...
Click to collapse
Flash in bootloader the hosd image for your actual firmware and you should be able to use fastboot/download