My Archos Helium 70b is totaly bricked:
Hi all,
I got a bricked phone with following symptoms:
Normal boot stays in an endless bootloop.
Starting up from recovery does the same.
3th option is fastboot: If I want to fastboot from a previously downloaded image with 'fastboot boot boot.img' command I got this:
Code:
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.688s
Any option to unbrick the phone left?
Thx
T
Related
Hello, on March 10th I received a new update on my N5. After update, which finished with no problems as usual, my phone was normally working or about two more hours. In that time no new apps were installed. Then it just shut down, and can't be properly turned on.
It always stuck at Google logo and that is all that it does. I'm able to get to the fastboot mode by holding Power+Volume Up+Volume Down buttons, but I can't get into Recovery Mode option to hard reset it. Nothing show up after selecting that option and Power+Volume Up does nothing. Ok, bad luck, time to flash it nice and clean.
Haha, nice try.
I'm not sure if I had USB debugging on or off, but I think off. Obtained ROM from Google + newest platform tools from SDK and followed all possible manual I could get from Internets, results:
Code:
adb devices
List of devices attached
*nothing*
Code:
adb reboot bootloader
error: no devices found
Drivers are newest from Google, reinstalled several times, device is visible in Windows as Android Bootloader Interface and seem working fine. adb just do not see phone.
Code:
fastboot oem unlock
...
OKAY [ 46.402s]
finished. total time: 46.403s - WORKS!
But rest is just no go:
Code:
fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase cache
********Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.217s
Code:
fastboot erase recovery
erasing 'recovery'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
Code:
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.218s
I tried several more commands, like to install twrp, but all with same results.
Code:
fastboot flash recovery twrp.img
sending 'recovery' (14314 KB)...
OKAY [ 0.653s] writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.835s
I also tried "fastboot boot twrp.img" and it worked but didn't helped much. Internal storage is showing size 0 MB an when I try to do anything it ends with wall of red text about how it's unable to find partitions or mount images, first line:
Code:
E:Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '/data' is not present!
Also when I reboot bootloader, it get stuck and when I get it back with buttons, it is back in its locked state. So my guess is that eMMC went to Silicon Heaven.
Do you guys have any advices? Or is my phone just fancy mirror now?
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
audit13 said:
When the phone is in fastboot mode, does the bootloader state remain "unlocked" after a reboot?
If the bootloader is unlocked, have you tried relfashing a stock ROM?
Click to expand...
Click to collapse
Like i wrote, it get back to locked state.
The emmc chip is defective and cannot be fixed. This is clearly indicated when the bootloader relocks itself at reboot.
Thought so, but wanted confirmation . Thank you.
My Xperia L is soft bricked and its bootloader is unlocked, so Sony PC Companion can't help. I tried Emma ( flashtool for Xperia) too. But it says "No available services matched the connected device." Service log: "Please refer to update session e0251daa-c222-413f-8f3c-5c77b4d9064b if you need to contact Emma support."
The command "adb devices" shows nothing, but "fastboot devices" is recognising my device when connected in fastboot mode. So, following this thread https://forum.xda-developers.com/xperia-l/help/soft-bricked-device-unlock-help-t3240972, I tried to install cwm recovery, using the command "fastboot flash boot boot.IMG". It shows:
Code:
sending 'boot' (6968 KB)...
OKAY [ 0.233s]
writing 'boot'...
OKAY [ 0.474s]
finished. total time: 0.707s
But nothing seems to install on my phone, as when I try to boot into recovery, the phone just tries to boot up and gets stuck in bootloop.
And if I try "fastboot flash recovery boot.IMG" then I get the following:
Code:
sending 'recovery' (6968 KB)...
OKAY [ 0.242s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.244s
How can I fix my phone? Please help! Any help is appreciated! Thanks!!
ankcash said:
My Xperia L is soft bricked and its bootloader is unlocked, so Sony PC Companion can't help. I tried Emma ( flashtool for Xperia) too. But it says "No available services matched the connected device." Service log: "Please refer to update session e0251daa-c222-413f-8f3c-5c77b4d9064b if you need to contact Emma support."
The command "adb devices" shows nothing, but "fastboot devices" is recognising my device when connected in fastboot mode. So, following this thread https://forum.xda-developers.com/xperia-l/help/soft-bricked-device-unlock-help-t3240972, I tried to install cwm recovery, using the command "fastboot flash boot boot.IMG". It shows:
Code:
sending 'boot' (6968 KB)...
OKAY [ 0.233s]
writing 'boot'...
OKAY [ 0.474s]
finished. total time: 0.707s
But nothing seems to install on my phone, as when I try to boot into recovery, the phone just tries to boot up and gets stuck in bootloop.
And if I try "fastboot flash recovery boot.IMG" then I get the following:
Code:
sending 'recovery' (6968 KB)...
OKAY [ 0.242s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.244s
How can I fix my phone? Please help! Any help is appreciated! Thanks!!
Click to expand...
Click to collapse
Please read this post:
https://forum.xda-developers.com/xperia-l/help/how-to-install-twrp-xperia-l-running-t3659340
Or simply use the below method:
Test again with downloading latest TWRP img and flashing it in fastboot mode using command: fastboot flash boot twrp.img
Then power on your phone and immediately press volume up.
It will directly boot to recovery. Screen may fliker, but no problem, just wipe everything and flash your ROM zip file.
Hello guys
I completely formatted the phone including internal data and everything but then i accidentally restarted the device and now its stuck in fastboot mode with device state unlocked and whenever i try to flash twrp for oneplus 6 it gives me this error
PS C:\adb> fastboot boot twrp-3.2.3-1-enchilada.img
downloading 'boot.img'...
OKAY [ 0.638s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.682s
PS C:\adb>
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Why not try installing TWRP via magisk?? Its easier that way
/\ agree /\
:angel:
lawrence_craig said:
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Click to expand...
Click to collapse
Make sure you are using the latest TWRP img.
Never flash recovery. Always boot recovery and then install TWRP zip. Have you not read the instructions?
As others mentioned, easier way to recover TWRP is to flash a magisk patch boot.img and flash TWRP zip in magisk.
Thanks for the tips guys, all sorted!
Hello everyone !
I was trying to put a LineageOS on my OP7P with this rom.
I unlocked the bootloader, boot onto the TWRP image (this one), flashed the ROM and then I got into troubles.
When I flashed the ROM, I didn't see any "go back" button, so I just pressed the "reboot system" one.
I came back to recovery, only of course to see that I have the "basic" recovery menu. So I got into the bootloader mode and tried to fix this, nothing I did fixed it...
I tried and got :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrpop7pro.img
downloading 'boot.img'...
OKAY [ 0.692s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.692s
I have no idea why is it not working. I tried the fastboot oem unlock, but it tells me it's already unlocked.
Then, by seaching, I tried but got this :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-74-guacamole-unified-installer-mauronofrio.zip
target reported max download size of 805306368 bytes
sending 'recovery' (17872 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.405s
Which seemed logical to me as the OP7P has 2 slots, but when I searched alternative to this answer it only brought me back to the first answer.
So now I don't know what to do to boot again on a TWRP and fix all this. Thankfully, I can boot on my main system and my LineageOS is working. But I still want to root it with Magisk and use the NanoDroid installer.
Anyway, if anyone here has any idea to help me, I would be very grateful