I am trying to pass a ROM action on my z2 to force, but the only feedback I have is this "FAILED (remote failure)" ... the script tries to flash but always the same command as response FAULT (remote failure) ... on my fastboot now appears "flashing_locked" ... the phone turns on but no network type works ... and when the cell phone starts the following message is displayed "your device has a different operating system load"
Sorry for my English and I do not know if I'm in the right place for this post
Related
Hi all,
I purchased a One X from eBay and it's got a custom rom on it which is horrendous - just keeps rebooting the phone etc. I'm trying to putting a stock rom back on (or just a better custom rom if it's easy enough to do) so I followed a tutorial I found on this forum for going back to ruu (there's no recovery image on the phone either).
Following those instructions I typed in 'fastboot oem lock'. Since doing that I've been stuck in the boot menu (it now refuses to load the rom that's installed and says 'relocked' at the top), and all I can do is switch between hboot and fastboot. If I run the correct ruu exe it just says it can't find the phone. Giving up on going back to stock I thought I'd just switch to a better quality custom rom but struggling with that as well..
I've just tried to reunlock the phone by following the instructions on htcdev.com, but when typing in fastboot oem get_identifier_token I get the following error:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
...
ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
Infact, it appears to not be able to execute any fastboot commands!
What would you recommend the next step is? Is there any way out of this?
Copy these files and place them looking like this
C:\fastboot\*files i gave with the link*
http://db.tt/ldx3qOOU
and also install the HTC drivers (if you didn't install them yet), after that you put the phone in the fastboot usb mode and open a dosprompt inside the fastboot folder and type
Fastboot devices
This should give the serial in return .... try this all first and we take it from there !
A friend of mine as the same phone as me, the Huawei Ascend P6, and when she said hers was broken I said I would take a look. I have played around with flashing Android Roms etcetera, but I am totally stuck with this problem.
The problem is as follows: when booting the phone it shows the Huawei Ascend logo (as it should) for a couple of seconds, but then instead of the Huawei animation it shows the name "android" and gets stuck there (see attachment).
After some researching I put the UPDATE.APP file from the Huawei website in the dload folder on the root of the SD-card and tried rebooting. I tried a several times, but nothing happened.
Next I successfully booted in recovery mode but even when starting recovery the screen shows errors (see attachment):
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument
Installing a ZIP file, wipe cache and wipe data give even more errors.
So I thought I would try flashing through ADB/fastboot, and used the HuaweiUpdateExtractor tool to get the images. I can get manually in fastboot mode, but when I try to flash an image get the error
Code:
FAILED (remote: flash failure, ErrNo:2)
I tried using different files, USB ports, cables, linux and windows but nothing seems to help. Has anyone an idea what to do next?
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
blueIBI said:
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
Click to expand...
Click to collapse
Since I can not boot and it's not my own phone I have no clue what the version is
Luckily my PC recognizes the phone in fastboot (indeed with a weird name with a lot of ?), but I am not able to flash twrp because every time I try I get a FAILED response... Maybe the file I have is wrong. Could you point me to a thread about falshing twrp?
here is a guide for unlocking bootloader: http://forum.xda-developers.com/showthread.php?p=50724517
here is a twrp for JB roms: http://forum.xda-developers.com/showthread.php?p=47633501
here for KK roms: http://forum.xda-developers.com/showthread.php?p=51718302
maybe you need to unlock your bootloader at first
changes not working
Thanks for the links! I am able to flash an image, but for some reason my changes won't stick. When I boot in fastboot it says it is locked and I am able to unlock it, but everytime I reboot it is locked again. The same happens with twrp, I am able to flash the image but for some reason when I boot back into recovery nothing has changed.
My fastboot commands and output:
Code:
C:\Android>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 1.952s]
finished. total time: 1.952s
C:\Android>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.012s]
finished. total time: 0.012s
C:\Android>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Android>fastboot flash recovery twrp_2_6_3_3_recovery.img
sending 'recovery' (8690 KB)...
OKAY [ 0.259s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.650s
Any idea?
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
blueIBI said:
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
Click to expand...
Click to collapse
That's what I was afraid of..
I think the unlock code doesn't work correctly on this phone for some reason, but I don't think I'll be able to get an unlock code specific for my device from Huawei, without serial number and such which I can't get since the phone doesn't boot.
I hope there is some warranty left...
Results
If anyone is interested (perhaps in the future), the phone was sent for repairs and is working again. They probably replaced the motherboard, but luckily it all fell under the warranty.
Thanks to blueIBI for trying to help!!
I am stuck with fastboot mode error : failed (remote flash write failure)
I am using a G3 phone. Which appeared to have a IMEI of d855 but its motherboard is of 850. I tried to flash kdz for 855 on it.. but now its stuck in fastboot mode with fastboot mode error : failed (remote flash write failure) . Whatever I've tried to do.. The same error appears.. any go around this error ??.. Please any help would be appreciated.. Thank you
LK-1.0.0.0000
Radio-01.01_U11440261_56.02.50306G_2_F
OpenDSP-v20.2.6-00452-M8994_0216
OS-1.32.161.15
Software status: Modified
Unlocked
S-ON
Recovery:
TeamWin Recovery Project 3.0.0-0
Good day,
I am German and can not speak much English. I translate everything from Google
So I hope that you with me bischen re consideration have the probably bad translation.
First time as the problem occurred I had "Android_Revolution_HD-One_M9_14.0".
Now the mobile has sat down in the boatloop overnight.
Have it with wipe of "dalvik cache" and "cache" tried. No success, now it does not hang in the bootloop anymore
It boot it dead.
TWRP points to system Patition "Present: yes" "Removable: No" "Size: 0MB" "Used: 0MB" "Free: 0MB" "Backup Size: 0MB"
Property then TWRP "Install" tried Revolution_HD to Install.Da stands then "set_matadata_recursive: some changes faild"
And as always hangs in the boot.
Then I tried the original Rome of Vodafone
(RUU_HIMA_UHL_L50_SENSE70_Vodafone_UK_1.32.161.15_Radio_01.01_U11440261_56.02.50306G_2_F_release_426771_signed_2_4.exe)
To install with Pc.
But the mobile phone makes every boot attempt of the PC a bootloader rebootart. What I gave up after 2 hours.
I then tried with "fastboot oem lock" it to "Relock". That does not work.
The error comes
" C:\adb2>fastboot.exe oem lock
< waiting for any device >
(bootloader) RELOCK device
FAILED (status read failed (Unknown error))
finished. total time: 0.289s "
Hope all the helpful infos have written with pure you can help me.
Best regards Maik
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
0sm1um said:
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
Click to expand...
Click to collapse
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
demonntlxda said:
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
Click to expand...
Click to collapse
Well sadly Xiaomi locked down EDL mode and that needs people working for Xiaomi to fix it.
Sadly a service center will not fix it because they will convince you to dump your phone in a rubbish bin and buy a new mi 11 because Xiaomi could earn more.
So that is a bummer but your phone needs a new motherboard.