Hi,
Yesterday my nephew wanted to show me a cool trick, getting to the settings menu. Although i had seen that already, i let him..
If only i hadn't, as he clicked on the radioband button with only "US" as a choice, and now i can't receive calls or call out myself.
As i can't risk losing data, i can't reflash, there is just too much i can't backup (Like Google Authenticator, i would have to disable it on 50+ accounts first)
So found the following link https://talk.sonymobile.com/t5/Xperia-Z1-Compact/WARNING-Never-Change-Radio-Band/td-p/905055/page/4, where all you need is ADB and your phone in fastboot / bootloader.. So, i have my Z5 in Developer mode, enabled USB Debugging (Also tried OEM unlocking as well), installed the latest ADB ( I tried both "Minimal ADB and Fastboot" and "platform-tools-latest-windows") and installed the "latest_usb_driver_windows". (After Phone started in fastboot, updated the S1.. Fastboot hardware drivers with the ones downloaded)
All seems OK, devices are found, but after i give the commands i get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 0.001s
All that works is: fastboot reboot..
It looks like the phone doesn't accept the commands, as even when i try a not existing one like "fastboot erase notexistingfolder, i get the same response..
Is it the software on my Xperia Z5, 7.1.1 (32.4.A.1.54)?
Is it my Windows version (W10 Pro x64, 1709)?
Do i need a special/other ADB+driver combo? I already installed the Sony Android .inf (disabled Driver Signing)
I used ADB before, never run in so much problem getting it going.. It doesn't need to have a unlocked bootloader for this, right?
As anything like that defeats the purpose of restoring calls without erasing the device..
Any help is appreciated. Willing to install W7/8 if needed to get it to work or use some sort of bootable W7/disk..
Thanks, allegro16
allegro16 said:
Hi,
Yesterday my nephew wanted to show me a cool trick, getting to the settings menu. Although i had seen that already, i let him..
If only i hadn't, as he clicked on the radioband button with only "US" as a choice, and now i can't receive calls or call out myself.
As i can't risk losing data, i can't reflash, there is just too much i can't backup (Like Google Authenticator, i would have to disable it on 50+ accounts first)
So found the following link https://talk.sonymobile.com/t5/Xperia-Z1-Compact/WARNING-Never-Change-Radio-Band/td-p/905055/page/4, where all you need is ADB and your phone in fastboot / bootloader.. So, i have my Z5 in Developer mode, enabled USB Debugging (Also tried OEM unlocking as well), installed the latest ADB ( I tried both "Minimal ADB and Fastboot" and "platform-tools-latest-windows") and installed the "latest_usb_driver_windows". (After Phone started in fastboot, updated the S1.. Fastboot hardware drivers with the ones downloaded)
All seems OK, devices are found, but after i give the commands i get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 0.001s
All that works is: fastboot reboot..
It looks like the phone doesn't accept the commands, as even when i try a not existing one like "fastboot erase notexistingfolder, i get the same response..
Is it the software on my Xperia Z5, 7.1.1 (32.4.A.1.54)?
Is it my Windows version (W10 Pro x64, 1709)?
Do i need a special/other ADB+driver combo? I already installed the Sony Android .inf (disabled Driver Signing)
I used ADB before, never run in so much problem getting it going.. It doesn't need to have a unlocked bootloader for this, right?
As anything like that defeats the purpose of restoring calls without erasing the device..
Any help is appreciated. Willing to install W7/8 if needed to get it to work or use some sort of bootable W7/disk..
Thanks, allegro16
Click to expand...
Click to collapse
You are fu*ked up! To use fastboot commands you have to unlock phone bootloader first, so you will loose data (as boot unlock always factory reset phone)
EugenStanis said:
You are fu*ked up! To use fastboot commands you have to unlock phone bootloader first, so you will loose data (as boot unlock always factory reset phone)
Click to expand...
Click to collapse
That would indeed be the case then.. I'll wait for Sony Mobile support.. If it's THIS easy to set the band to US, it should be easy to reset for them as well, right?
If i'm forced to reset / erase the Z5 in any way, i might as well change brands again and get a new unit.. At least then i can copy everything over piece by piece in time..
Thanks anyway.
Related
Hello,
i am using my Toshiba Folio as a playground for new ROMs. I have already successfully installed different mods but since the last one, my Folio seems to be broken.
I followed this guide here: http://forum.xda-developers.com/showpost.php?p=31004271&postcount=9 but when i issue the fastboot commands i always get this:
[email protected]:~/Downloads/adt-bundle-linux/sdk/platform-tools> fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 0.001s
[email protected]:~/Downloads/adt-bundle-linux/sdk/platform-tools> fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 0.002s
Click to expand...
Click to collapse
My Folio says:
Failed to process command getvar: partition-type:xxxx error(0x2)
Click to expand...
Click to collapse
where 'xxxx' is the partition i try to access accordingly.
Can anyone help me out or do i have a brick now? I definitly have done something wrong.
Greetings,
Alex
problem
hello good, I have the same problem as you, could you fix it?
Just popped here to say how I managed to get arround this:
fastboot -u -S 0 flash linux boot.img
and it worked.
My understanding is that 'fastboot' changed and has new capability of getting 'partition-type' from device.
Folio doesn't seem to understand that command, so it's either -u or -S 0 that makes it work.
Cheers my friends!
I had the same problem!! The working parameters is "-S 0"
Tried everything // getting failed // found a way
I spent the whole day to understand how to make this work...
I did the factory reset via Settings in Android menu, I connected the tablet to PC and the only thing I could do using fastboot was "reboot".
I forgot all "erase" functions and I tried "fastboot boot <filename.img>" and it worked!
Then you follow http://forum.xda-developers.com/showpost.php?p=31004271&postcount=9
Just try this if anything else fails.
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.
HELP CAN ONLY ACCESS FASTBOOT MODE AND LOCKED BOOTLOADER AND STUCK
Recovery not working, boot not working, only fastboot&rescue mode working but the problems is that i relocked the bootloader and now i cant unlock it and fastboot dont allow me to flash anything like recovery.img
also tried to flash update.zip but cmd says not enough space.? so anyone have i clue what to do? can i get rid of the out of space error? somehow flash something or an command in cmd fastboot to get my phone working?
PLease help
getvar:all FAILED (remote: Command not allowed) it says command not allowed even in that command. and its bootloader lock is on any workaround so i can install update.zip without cmd says not enought space? or some workaround or command in fastboot to bootloader unlock with fastboot or any other idees?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36998 KB)...
OKAY [ 0.786s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.786s
C:\Program Files (x86)\Minimal ADB and Fastboot>
ALWAYS GETTING FAILED (remote: Command not allowed)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update update.zip
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
i think YOU ARE DOOMED??
only thing you can do is getting it back to the service center..gud luck buddy...
goran85 said:
HELP CAN ONLY ACCESS FASTBOOT MODE AND LOCKED BOOTLOADER AND STUCK
Recovery not working, boot not working, only fastboot&rescue mode working but the problems is that i relocked the bootloader and now i cant unlock it and fastboot dont allow me to flash anything like recovery.img
also tried to flash update.zip but cmd says not enough space.? so anyone have i clue what to do? can i get rid of the out of space error? somehow flash something or an command in cmd fastboot to get my phone working?
PLease help
Click to expand...
Click to collapse
same problem,, how to solve it??
writing 'recovery'...
FAILED (remote: Command not allowed)
sometime happenned to me and when installed the correct drivers in windows installed ok
Hello
after i succesfully used DC Phoenix to recover Huawei Mate 8 (NXT-L29C432) i cannot flash TWRP or anything on my phone , as im still getting the "FAILED (remote: image verification error)" from fastboot. So i also cannot root and use the device as before
Im sure im not alone with this issue, but i cannot find any clear solution for this. Can you please help or advice me further??
I spent 15€, recovered the phone, but with this, its still partial success.
I basicaly followed https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
Here some outputs:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22140 KB)...
OKAY [ 0.530s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.562s
Before the use of DC Phoenix, i always get this number.
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
QHC0216327001941 fastboot
Now:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0123456789ABCDEF fastboot
In Fastboot mode, on phone screen i see:
PHONE Unlocked
FRP Lock
DC - Unlocker 2 Client 1.00.1308 reports:
FB LockState: UNLOCKED
USER LockState: LOCKED
unlocked
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ -0.000s]
finished. total time: -0.000s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
In Developer menu i have the
"Allow OEM unlock" grayed & disabled, im unable to swich it on..
Can you please explain what happend and how to fix this?
Thank you for further help.
Solved with mighty HCU client, i was able to import the just the SN back without problems. Then as usual.. unlock the bootloader, TWRP, SU... and now the phone is back in shape
I hope I can recover my Mate 9 Pro.
Maybe 15€ is have to spend but FunkyHuawei is more expensive.
Hi. I have same problem., I unlocked Huawei WAS-AL00 bootloader via Miracle Huawei Tool, it unlocked successfully. But, I can't flash TWRP, it says-FAILED (remote: image verification error)
Whent type fastboot oem lock-state info in CMD, it shows:
FB LockState: UNLOCKED
USER LockState: LOCKED
There is not FRP or OEM lock option in settings, becuse this is China version model and doesn't support Google Play.
What is USER LOCK STATE? Please help me. Thanks.
Remote:image verification error.
When i try to flash Mate 8 nxt l29 twrp recovery its says remote:image verification error..the phone fastboot is unlocked .i tried many twrp images but still the same problem
hello, i want to root my phone with magisk, adb and fastboot, i get this error when i want to root it in fastboot mode
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot magisk_patched_pEtAo.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.009s
I even wanted to download twrp recovery and still the same thing appeared in fastboot mode
yukan2007 said:
hello, i want to root my phone with magisk, adb and fastboot, i get this error when i want to root it in fastboot mode
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot magisk_patched_pEtAo.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.009s
I even wanted to download twrp recovery and still the same thing appeared in fastboot mode
Click to expand...
Click to collapse
Follow the root tutorials in the forum, rooting by flashing using the terminal is a deprecated method