Database Users

[Q] Help me to unbrick my HTC legend

Hi Everybody,
I am a newbie, i was trying to install aliba's gingerbeard rom via rom manager, but i dont know what happenend and just my device stopped working, and hanging on cyanogenmod symbol,
Pls guide me to unbrick, i have read some threads in our XDA itself, i am not so clear from where to start to unbrick,
and i placed some roms in sdcard/update.zip via card reader and used the recovery screen (i knew that recovery is not clockwork mod) but the error is
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
and finally after retry 10 it is showing
E: Can't find /sdcard/update.zip
Installation aborted.
Pls help me to sort out this,
Thanks in advance

This should be in general (I wish I was a moderator, I'd do it myself)
Get clockworkMOD recovery (look for FakeFlash), and flash a STABLE ROM

Hi,
Thanks for your reply,
before installing Aliba's Unstable rom i made a nandroid backup,
Now my legend is booting on phone's recovery where i could not find to restore my nandroid backup,
Already bricked phone, can you please guide me how to get clockwork mod recovery on it,
as i told i am newbie, dont know where to start and how to get clockwork mod recovery
Thanks

FakeFlash. Search. All the info is here.

Hi, Grammarfreak
I tried fake flash, unfortunately no use,
i downloaded clockworkmod recovery and kept in my root of sd card as update.zip
and in the recovery screen i click Apply sdcard: update.zip,
Again same problem,
E: Cant mount /dev/block/mmcblk0p1(or /dev/block/mmcblk0)
No such file or directory
E: Cant find /sdcard/update.zip,
Installation aborted
Please note whenever i go to recovery screen i can see below in yellow letters
E: Cant open / cache / recovery/command
I feel may be problem with my sdcard?
Oh Nooooooooo, i tried 3 different cards, all the cards same error
E: Cant open/ cache / recovery /command

chandramohan1986 said:
...
E: Cant open / cache / recovery/command
I feel may be problem with my sdcard?
...
Click to expand...
Click to collapse
I see the same errors when I go into recovery, but I can still launch the fake flash version of recovery. Make sure the update.zip is the correct version.

Recovery is failing to mount your SD card. I'm not sure what the issue is

Did you try USB Unbrick?

year!
http://www.megaupload.com/?d=RTEY0Q97
get that adb.zip
then you should get some recovery files. Hmmm, how to upload??
pull recovery files to the "files" folder.
just run:
adb push files /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
you could get into recovery and flash rom again.

try searching on youtube

Put the Clockwork Mod update.zip and your backup or another ROM (as zip file) on your SD Card. Then press Volume down + Power Button. Afterwards select Recovery and wait until you see the red triangle. When you see the red triangle press Volume up + Power and wait until the Recovery screen appears. There you select Apply update.zip and your phone should boot into Clockwork Mod Recovery. From there you can flash a new ROM or restore your NANDROID Backup.

heres another way... go download this http://www.megaupload.com/?d=XBAOCSWZ
and find testimage.zip in it. Put it on your phone's sdcard renaming it to LEGEIMG.zip
off the phone and go to boot loader and start back from unrooted eclair...
the link above is form got it form this post http://forum.xda-developers.com/showthread.php?t=894465
but anyway... since you like e2 recovery so much... you did not do a factory reset... go do that and the loop should go away....

@spiritusrector
THANKS SOO MUCH lol...you just saved me 35 bucks

answer
go on youtube and search for androidreviews123....he has a guide on how to unbrick

unbrick
heres the link
http://www.youtube.com/watch?v=lVmH6l0xssA

[Q] secure boot img SOS check sum fail!

Hi
I am currently trying to install thor_rom_v14.2.zip (ROM) to my
Pb liberty tab said to be the same as acer iconia A500.
The stuck version is android is 3.0.1
But every time I try to start it in recovery mode I get
"secure boot img SOS check sum fail!" and the boot process stops.
I've rooted it with gengerbreak
installed ROM manager from app store. It does not recognize the product under the installation and asks me to confirm that it is an asus transfomer which I did although it was certainly not an asus trnasformer. All the things I tried with ClockworkMod Recovery (CWM) led only to a boot that stopped by "Secure boot img SOS check sum fail!"
So I tried with acer recovery install v2.74. But here I got exactly same result. I could not get past the "secure boot img SOS check sum fail!".
So my question obviously is. How do I get about this "Secure boot img SOS check sum fail!"
Should I perhaps get hold of an older version of the Acer Recovery Installer that has ClockworkMod Recovery rev.1.3.4 by thor2002ro with it? If yes how to I get it?
Other proposals... could I do this in a completely different manner? like from a USB connection from a remote computer or with Unix dd command or???.. How could I get about this?
/Mikkel

[Q] Boot verified failed and APX driver problem

Hi!
I have tried to flash unlocked bootloader V3 from civato's guide, and I could not pass step 6 (flashing bootloader with nvflash or blacthund3r's tool). None of this method didn't work (Nvflasher didn't flash anything, and blackthunder tool was stuck at formating some partition (can't remeber which one).
Last successful step was flashing ICS rom (full leaked version of 1.031.00).
After that I could boot up, and rom worked all fine.
But, after that, I got my self in trouble.... I pressed Vol- & PWR, tablet did his thing, and when reeboted, I got stuck in Acer logo screen with red writing "Boot verified failed"
I understand that I have messed boot somehow... And to fix this i have to flash new bootloader through nvflash and apx mode. I tried to put update.zip on sd card, but it didn't helped (I still get boot verified failed)
Here, I got another problem. When I have connected tablet in apx mod to pc, i got message "driver not installed". Now, in devices I have "unspecified APX device".
BTW, adb doesn't see my device?!
I hope that You guys can help me with these problems, so that my tablet is operational an running again.
Thanks in advance!

boot verified
I have the same problem but I can not find the v3 bl and CWM Recovery Package to flash with the apx flash utility. If you find them let me know.
This what you have do:
Your recovery is borked so u have to put a new one on there, the best way to
go about doing this is to:
Download the V3 AND CWM Recovery package and apxFlash that.....Done!!
your need to flash the WHOLE PACKAGE b/c ARI reports yr BL as plain old stock
You cannot replace the failed recovery with CWM with the plain old stock BL!!
You have to flash the patched BL as well, so again
You must flash the whole pckg just like in the guide OK
if later u want the stock recovery back u can use ARI to do that but after the apxflash!!!

Thanks for your replay! I'l try to do this and hope it will work...
By "WHOLE PACKAGE" you mean unlocked bootloader and CWM? Or, something else?
Check this thread for V3 and CWM.

boot verified
Yes "WHOLE PACKAGE" unlocked bootloader and CWM
The tread you sent me I do not know how to use the nvflash never works for me.
I have been trying for 3 days and no luck.
Let me know if it works for you or how you make out

zozo10k said:
Hi!
I have tried to flash unlocked bootloader V3 from civato's guide, and I could not pass step 6 (flashing bootloader with nvflash or blacthund3r's tool). None of this method didn't work (Nvflasher didn't flash anything, and blackthunder tool was stuck at formating some partition (can't remeber which one).
Last successful step was flashing ICS rom (full leaked version of 1.031.00).
After that I could boot up, and rom worked all fine.
But, after that, I got my self in trouble.... I pressed Vol- & PWR, tablet did his thing, and when reeboted, I got stuck in Acer logo screen with red writing "Boot verified failed"
I understand that I have messed boot somehow... And to fix this i have to flash new bootloader through nvflash and apx mode. I tried to put update.zip on sd card, but it didn't helped (I still get boot verified failed)
Here, I got another problem. When I have connected tablet in apx mod to pc, i got message "driver not installed". Now, in devices I have "unspecified APX device".
BTW, adb doesn't see my device?!
I hope that You guys can help me with these problems, so that my tablet is operational an running again.
Thanks in advance!
Click to expand...
Click to collapse
Did you install acer usb drivers.

EDIT: SOLVED!
Mods, you can close this thread.
shaun298 said:
Did you install acer usb drivers.
Click to expand...
Click to collapse
Hi!
Yes, I have dl the drivers from Acer site and installed them. But pc only recognize tab in APX mode. And adb doesn't see my tab.
Every method that I have tried (APX flash tool and nvflash) hangs at some part. APX flash tool hangs at "Flashing bootloader EBT - stage two, and nvflash hangs at formating partition 4.

Hi, I´m having similar troubles to get acer drivers working on windows 7 32. I installed newest acer web drivers, ADB works OK. When I get to apx mode I need to manually point to drivers, I have an APX driver with a sign and turns to Acer Picasso USB Boot-recovery driver. The problem is that not any of the tools sees this as a connected tablet in apx mode (afterota or apxflash).
I am doing something wrong? I know a500manager shows me the tablet is in apx mode "please install drivers" when i get APX driver with Sign, after installing the driver manually it just doesn´t show connected anymore.
thanks

hernborc said:
Hi, I´m having similar troubles to get acer drivers working on windows 7 32. I installed newest acer web drivers, ADB works OK. When I get to apx mode I need to manually point to drivers, I have an APX driver with a sign and turns to Acer Picasso USB Boot-recovery driver. The problem is that not any of the tools sees this as a connected tablet in apx mode (afterota or apxflash).
I am doing something wrong? I know a500manager shows me the tablet is in apx mode "please install drivers" when i get APX driver with Sign, after installing the driver manually it just doesn´t show connected anymore.
thanks
Click to expand...
Click to collapse
Download and install the Google USB drivers.
Google.... Android USB Drivers, and you should get the page for the Android SDK with google drivers.
In Apx mode, go to device manager on your PC, and manually install the drivers. Don't let it search automatically, do it manually. If you get a compatibility warning, ignore it.
Should hook you up with normal, ADB and APX drivers.

zozo10k said:
EDIT: SOLVED!
Mods, you can close this thread.
Hi!
Yes, I have dl the drivers from Acer site and installed them. But pc only recognize tab in APX mode. And adb doesn't see my tab.
Every method that I have tried (APX flash tool and nvflash) hangs at some part. APX flash tool hangs at "Flashing bootloader EBT - stage two, and nvflash hangs at formating partition 4.
Click to expand...
Click to collapse
THANKS FOR NOT TELLING US HOW YOU SOLVED IT:good::good::good::good:

[Q] Need to unbrick Defy+ - Strange problems

Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis

If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2

Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.

I think I brinked my phone. Please help [SOLVED!]

Hello. I tried downgrading from the latest ASUS firmware to Android 6.0.1
I used this tutorial to install the raw firmware: http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html
Went all the way to the last step when the app hanged. ASUS Flash tool went all the way saying
Code:
Run flash image script ...
It was hanged there. And as per this video, went all the way to the end where it showed the "code bar" on the right (https://www.youtube.com/watch?v=P8xg7A-P7Ak)
This is when the "Android" uninstalled driver showed up in Windows. This is under "Other devices - Android". I tried updating this driver using the ASUS_Android_USB_drivers_for_Windows found here: https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ but it wouldn't install the drivers.
Note that I used these ASUS USB drivers to get the ASUS ADB Interface installed. As per the tutorial I showed in the very first paragraph, I never got the "ASUS Android Bootloader Interface". This is what I think this "Other devices - Android" is found under Computer - Manager - Device Manager.
Most tutorials on the internet shows that the "ASUS Android Bootloader Interface" should be installed using these drivers found on ASUS website, the ASUS_Android_USB_drivers_for_Windows.
Now of course because I unplugged the phone, it will continously stay on the Android splashpage showing the loading circle infinitely.
As a last attempt I tried installing the "stock", not "raw" firmware (the one I wanted to install WW_13.16.5.49 but ASUS would not let you downgrade using the recovery "power+volume down" and using "Apply update from microSD card". It would give the
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
)
Well, after it brinked, I tried it again and this time it DID install WW_V13.16.5.49. Was succesfull. But after the ASUS splashscreen it's still stuck in the booting process.
I am very sorry if my post is convoluted but I tried explaining everything I did. Any way to un-brink it? I think maybe if I figure out how to properly install the ASUS Android Bootloader Interface, I can try again ASUS Flash tool and install the raw image and maybe that will fix it?
Please help. Any questions if my thread is too confusing, please let me know and I will answer it. I can't even turn off the phone. While it's stuck into the load splash screen, if I press the power button it just restarts, not turn off.
I still have access to fastboot (pwr + volume up) or recovery (pwr + volume down)
EDIT: Phone won't get recognized anymore in ASUS Flash Tools. Serial number won't show up to select

Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.

wang1chung said:
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
Click to expand...
Click to collapse
Thank you, this actually worked!!
Aaaand, it's actually on the version 13.16.5.49!!!! THIS IS EXACTLY WHAT I WANTED!
So apparently by brinking my latest nougat 7.0 update from ASUS via the ASUS Flash Tool trying to flash the .RAW 13.20.10.137, the standard recovery system (power+volume down) allowed me to install the 13.16.5.49 version. Then I assume remnants files didn't allow to properly boot, and your idea to wipe cache and factory reset fixed that!
What is so great is that I was scared that because the .RAW firmware was newer than the version I needed (13.16.5.49), I wouldn't have been able to install it. It was the same problem initially, when I tried to install 13.16.5.49 directly via recovery over the latest nougat 7.0 version from ASUS, but it was giving me
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
I think this error was due to the fact that ASUS won't allow older firmwares to be installed over newer ones, as per their webpage
https://www.asus.com/support/faq/1009748
Code:
You can not change the SKU from one to another, e.g., WW -> TW, and also can not downgrade your firmware, e.g., V2.20.40.13 -> V2.19.40.18
So in the end, what allowed the 13.16.5.49 stock firmware to be succesfully installed? The installer not detecting a proper firmware anymore because of the damaged update due to ASUS Flash Tools hanging because my computer won't install ASUS Android Bootloader Interface?

Glad you got it going :good: