Database Users

[Solved] NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb

Hi all!
I have a big problem...
My Hero wan't boot so I go in the Recovery Console.
But if i want to restore a Backup this message appears:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
E: Can't mount SDCARD:
I tried several SDCARDs... same message.
I've wiped all several times. Reformat the SDCARD...
Access via ADB brings:
error: device not found
Fastboot mode is possible... but
fastboot boot cm-hero-recovery.img
in the konsole brings: "downloading 'boot.img'... FAILED (remote: not allow)"...
What can i do?

This might help?.....
http://forum.xda-developers.com/showthread.php?t=681583
then go to .....
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/

Thanks for the links...
I could re-flash the T-Mobile ROM (2.73.111.26)... The Hero starts and now it works with Android 1.5 ...
I have access to the SDCARD ... but the USB Connectivity doesn't work...
No ADB and no storage Device in Windows...
"fastboot oem eraseconfig" doesn't work... think about the false HBOOT (HBOOT-1.76.0007)...
flashrec also doesn't work... there comes "Flash FAILED: could not run command"
Any ideas?

Had exactly the same.
Forget about the rom, it doesn't matter (i.e. flash whatever you like).
You already got your SD card support back, for the rest you need to update the SPL (search for an unlocked version for your hero, double-check because it can _really_ brick your device if this fails). After that fastboot oem eraseconfig works and your usb is back to normal.
Did that yesterday, worked like a charm and actually makes sense (unlike other suggestions like "reflash N times", "unplug and replug usb or change the cable" and "send in for service"). Your USB is fine (as seen in fastboot), it's just not working after your kernel booted -> Due to messed up configuration parameters in the flash area. Basically the kernel commandline, if you will..

Wich version of SPL I do you flash?
How do you flash it? Like...
fastboot oem rebootRUU
fastboot flash zip SPL_image.zip
in the fastboot konsole?
RecoveryConsole is not useable to me... My Hero is not rooted anymore... And it seems to be very difficult to get root again :-/

What do you mean by?
Swerner1975 said:
I have access to the SDCARD ... but the USB Connectivity doesn't work...
Click to expand...
Click to collapse
According to BTDAGs guide, flashing 2.73.61.5 should enable you to use flashrec to do the custom recovery again.

[solved] NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb
Thanks for your help. I have solved the problems...
- first I flashed the T-Mobile D ROM like described in the Link (extract rom.zip and flash)
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
- then I have detected, that flashrec does'nt work on the ROM
- then I created a GOLD Card
- with this I flashed in the OEM fastboot Mode (described here) the HTC Update ROM (_HTC_Hero_RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe)
- then flashrec was working and I was able to flash a Recovery Image
- in the Recovery Console I flashed the unlocked Modaco SPL (from here)
- now it was possible to erase the config, which locked the USB after Kernel Boot (fastboot oem eraseconfig)
- after that I restored the last Nandroid Backup...
- Now I'm happy

Re: NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb
Excellent news.
-------------------------------------
Sent via the XDA Tapatalk App

Can't mount cache... can't change droidboot and recovery

hello xda community
I made sure to try everything (or almost) before post here
my ZenFone 5 show a message that it cannot mount the cache partition and I am stuck on the Asus logo (I can access droidboot and recovery but I cannot replace them)
factory reset and cache wipe does not make any change (they return the same "can't mount cache" error.
I am trying to change the current droidboot and recovery to fastboot and TWRP but not matter how much I flash them, it does not take change (yes, I am unlocking the bootloader)
I am also executing a script to get the original partitions table back but when sec_offline_update_image.cmd executes the command "fastboot oem partition /tmp/partition.tbl" I get the error "FAILED(remote: GPT command failed)"
as this came out of thin air, I didnt have the chance to activate developer mode on my phone
I starting to get concerned .... any help?
thnk you very much in advance

@dgadelha any help ?

What are the specs of your Zen 5?

dgadelha said:
What are the specs of your Zen 5?
Click to expand...
Click to collapse
ZenFone 5 - A501CG T00J
Serial # with 0123456789ABCDEF issue
Box info: A501CG2 / A501CG-1F589 / CPU Intel Clover Trail Plus + Dual Core 1.6 Ghz, Purple, 8GB RAM
I already checked basically all links on Google related to the above issues (4 days Googling it already).
I really don't know what to do anymore.

A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!

jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Hi,
Did you have any kernel mods when using BlueLight?
Sorry but I don't know if it had a custom kernel, but a custom one could have lead a storage drive crash.
Also, xFSTK will just attempt to restore your droidboot and dnx/ifwi, not the partition table or w.e.
Maybe you could try extracting the Jelly Bean RAW file with 7-Zip, flash the droidboot signed image (should be like, fastboot flash fastboot file.img, or fastboot flash droidboot file.img), the droidboot signed image name might be something like droidboot.signed_POS.bin (it's an img file too, but with a bin extension).
After flashing that droidboot image, reboot your bootloader and try running the sec_offline_image_update.cmd again.
I wish I had Zenfone Assist active yet, but had to take down it.
Thanks

Hey jaabax, were you able to fix your device ?

Hi @vikrammarkiv.
Sorry for the big delay in response... I am not using this e-mail anymore and I quit fixing my phone.
Unfortunately I could not fix it and I ended up buying another phone.
Could you fix it?
Sorry again and hope you fixed it.
Best regards.

same issue, anyone got any update on fix?

jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Same problem, only fastboot and GPT failed (Asus zenfone 2 ze551ml). No solution

Exactly the same problem. It appears there are no fixes. How did the xf... thingy go?

Оh man.. I have the same issue, and can't fix it...

[HELP] [SM-G530FZ] Can't flash / Can't wipe / Fastboot doesn't detect device

Hello !
I'm stuck on the following problems, stock SM-G530FZ:
I tried everything to get access to the fastboot commands on this device, but nothing worked... (is that true Samsung doesn't support fastboot mode ??)
Via Download Mode, I tried fastboot under Win7 (tested every USB drivers I could find ^^), Ubuntu 16.04, Mint 17, FWUL, different computers, different USB cables, etc...
But my phone is never detected (nothing showed, and if I launch a command, fastboot is "Waiting for device").
I can't boot normally because I cannot pass the lockscreen, I've a FC of " com.android.systemui" and the phone reboots.
So I can't activate adb to try to submit "adb reboot-bootloader".
I can't flash anything (ODIN, heimdall GUI and CLI, jOdin3) because the bootloader is locked.
I tried to wipe everything via stock recovery but I've the followings 2 errors:
Code:
E: format_volume: make_ext4fs failed on /dev/block/bootdevice/by-name/userdata
E: format_volume: make_ext4fs failed on /dev/block/bootdevice/by-name/cache
ADB is not working via stock recovery, just the sideload option seems to work.
Kies is useless (what an understatement !).
As I cannot access the OS, I thought my only way was to unlock bootloader via fastboot command, but...
So... I'm out of options, what can I do ?
Is someone have any idea ? I think that the system is very corrupted but maybe I'm missing something.
A correct debrick.img file could do the work ?
Thanks a lot in advance for your time.

Up
I tried to re-partition with the correct PIT file, but the process stops after PIT upload with the following error:
Code:
SECURE CHECK FAIL : PIT

Help!!! My Axon 7 is dead (Boot into fastboot and EDL only)

My phone was working fine, until it suddenly freeze and reboot. After that, it runs into bootloop at zte logo.
I had miflash the phone with stock rom. Flash successful, but the phone still bootloop at zte logo (can't enter system).
I can enter fastboot only (recovery + system => reboot);
try:
0. boot to system => definitely failed
1. hold volumn up + power button => failed
2. fastboot boot recovery => failed
3. fastboot boot twrp.img => failed
4. axon7tool -w recovery = successful , but failed when boot recovery
5. axon7toolkit : flash twrp = successful, but failed when boot recovery
6. miflash A2017 rom = successful, but failed when boot system + recovery
7. miflash A2017 rom = successful, but failed when boot system + recovery
:crying: I am desperate here.
Any help would be appreciate!! Thank you!

Try going into your recovery and formating as ext4. If you were using f2fs, edl won't work.

My edl is working, and miflash successful but then the device cant boot system (and cant boot recovery also)

tamahouse02 said:
My edl is working, and miflash successful but then the device cant boot system (and cant boot recovery also)
Click to expand...
Click to collapse
First of all, redownload the stock EDL file. If you already have it, just check that it's not corrupted or anything. I'd advise redownloading it, which the files can be found from this thread.
Flash the stock EDL, then before booting, go into stock recovery (Hold volume up button whilst powering on). Do a factory reset, and also wipe cache. Now try booting. It should boot, and if it doesn't, then the only thing I can think of is either a corrupted EDL file or physical damage inside the phone to the memory chip.

I had miflash two different edl roms (china and us). And facing the same issue. It may be the hardware problem.

tamahouse02 said:
I had miflash two different edl roms (china and us). And facing the same issue. It may be the hardware problem.
Click to expand...
Click to collapse
Everyone is telling you that you have to format your data partition, but you're not answering that: did you or did you not? If you have Fastboot, enter it and issue
fastboot format userdata
and hit enter

Choose an username... said:
Everyone is telling you that you have to format your data partition, but you're not answering that: did you or did you not? If you have Fastboot, enter it and issue
fastboot format userdata
and hit enter
Click to expand...
Click to collapse
I did. The phone enters system for 1 minute then keep reboot itseft again

Bricked phone doing factory upgrade to B04. Stuck in EDL mode, but wont connect :(

Bricked phone doing factory upgrade to B04. Stuck in EDL mode, but wont connect
Device manager shows QUSB_BULK but no tool will see the phone. Any ideas guys.
I have installed quailcom drivers etc , no difference

You can try this tool:
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229

Hi , I did try that. The port manager in the app does not show anything. It as if the phone is not connected. Even though it is listed in windows device manager as QUSB_BULK

Wait until batterry fully discharged, try enter edl mode again and flash using edl tool or miflash

the_hoho said:
Wait until batterry fully discharged, try enter edl mode again and flash using edl tool or miflash
Click to expand...
Click to collapse
Hi,
I waited till the battery discharged. Went into EDL mode. They only success I had is with axon7tool.exe
Miflash will not detect the phone. As seen believe I can read and write with axon7tool.exe
Is there any recovery I can put back on the phone that will run? The bootloader is unlocked. Thanks
H:\TRWP AXON 7>axon7tool -r recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Reading recovery ...
Success!
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...

> H:\TRWP AXON 7>axon7tool -r recovery
Your command with option "-r" (for read) only backuped the existing recovery to your PC.
There was no effect on the phone. It read your phone recovery and downloaded (=backuped) to your PC (probably with name recovery-backup.bin).
Since your booloader is unlocked, you can write official but unsigned TWRP recovery to the phone. This official but unsigned TWRP recovery
will run correctly (since bootloader is unlocked). So you need to 1) download latest official TWRP recovery, then 2) write it to the phone.
1)
On your PC:
Go to https://eu.dl.twrp.me/ailsa_ii/
Download the recovery twrp-3.3.1-0-ailsa_ii.img (14 897 152 bytes, md5 0d57b791c6b7c7d979ea70b0951c519d) with the link:
https://eu.dl.twrp.me/ailsa_ii/twrp-3.3.1-0-ailsa_ii.img.html
Copy the file to the directory containing your axon7tool.exe ("H:\TRWP AXON 7").
Then copy twrp-3.3.1-0-ailsa_ii.img to recovery.bin (command: "copy twrp-3.3.1-0-ailsa_ii.img recovery.bin")
(this means you have a new recovery.bin file which is exactly the same as twrp-3.3.1-0-ailsa_ii.img file).
Explanation: this to prepare to write TWRP recovery to the phone, the axon7tool.exe syntax "-w recovery" requires a file named recovery.bin
which has the content of the recovery you want to put (in your case, latest official TWRP recovery twrp-3.3.1-0-ailsa_ii.img).
On your PC, go to H:\TRWP AXON 7 directory:
H:\TRWP AXON 7>
type "dir" command, you should have files: axon7tool.exe, recovery.bin (identical to twrp-3.3.1-0-ailsa_ii.img), twrp-3.3.1-0-ailsa_ii.img and other files.
2)
Put you phone in EDL mode as you did before.
On your PC, type the following command to write TWRP recovery to the phone:
axon7tool -w recovery
(Explanation: the above command will write (-w) the recovery to the phone using the file named recovery.bin (= twrp_rec_tenfar.img) found in your PC.
You can then boot to recovery, using menu in bootloader at start (use Vol-Up, Vol-Down for selection, Power to Confirm selection).
Other way: if phone is power off: Vol-Up + Power to get into TWRP recovery.
Afterwards, with TWRP you have total control on the phone, custom ROM etc...