Related
Hi my 1st post on the forum been browsing for a couple of weeks after getting my XT890 & as I like to mod/hack everything I own, So decided to unlock & root my Razr I ..
I successfully unlocked the boot loader without issue, & proceeded to root it,(usb debugging mode) then I came across problems tried various methods motofail2go on my x86 pc but had problems with the MTP driver not installing?
So tried the batakang method on my Win7 x64 pc only when I run the batch file all seemed well until the phone rebooted to fastboot & started to download. there it stuck on downloading... no response for several minutes.
I reattempted the procedure numerous times, & had to restart my phone & cause of flash failure on fastboot with an error like downloaded -1 bytes download failed,
So I had to RSD lite an retail GB firmware tried both (31 & 39) to restore the phone I read there are some issues with rooting on 39 but still got the same problem on 31?
I have searched & cannot find an answer to why it wont root?
Do I need a sd card in the phone for the hacks to work that is the only reason I can think of but seems unlikely, I have the latest drivers ect installed tried various fastboot commands to reflash the boot.img ect but same problem it wont download to the phone & I have to RSD recover.
I would like to thank the people & members of the forums for the information I have already read & hopefully shall receive :good:
im having trouble trying to root my phone again after it crashed and had to start from beginning. When i try fastboot flash boot Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img it gives me fails and says FAILED <Remote: command not allowed> does any body know what im doing wrong? I managed to root it teh first time no problem.
Cheers
sturtz1987 said:
im having trouble trying to root my phone again after it crashed and had to start from beginning. When i try fastboot flash boot Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img it gives me fails and says FAILED <Remote: command not allowed> does any body know what im doing wrong? I managed to root it teh first time no problem.
Cheers
Click to expand...
Click to collapse
Is you bootloader unlocked?
krabappel2548 said:
Is you bootloader unlocked?
Click to expand...
Click to collapse
yes the bootloader is unloack but i had my phone rooted before then had to use pc companion to repair it, ive unlocked it again to be sure.
It seems driver problem.
I met the same problem as well as others yesterday, when I unlock, relock, re-unlock, root locked, root unlocked, flash recovery... for some crazy reason.
Try these:
Connect to flashtool (beta2 or beta4) with device power-on debug off, to see if flashtool can recognize it, and how much it can recognize.
Connect to flashtool with device power-on debug on , to see if flashtool can recognize it.
Connect to flashtool with device in fastboot mode, to see if flashtool can recognize it.
Connect to flashtool with device in flashmode, to see if flashtool can recognize it.
Flashtool may fix some driver error. I just succeeded after hours of bungling like that.
Good luck.
orc.x.lei said:
It seems driver problem.
I met the same problem as well as others yesterday, when I unlock, relock, re-unlock, root locked, root unlocked, flash recovery... for some crazy reason.
Try these:
Connect to flashtool (beta2 or beta4) with device power-on debug off, to see if flashtool can recognize it, and how much it can recognize.
Connect to flashtool with device power-on debug on , to see if flashtool can recognize it.
Connect to flashtool with device in fastboot mode, to see if flashtool can recognize it.
Connect to flashtool with device in flashmode, to see if flashtool can recognize it.
Flashtool may fix some driver error. I just succeeded after hours of bungling like that.
Good luck.
Click to expand...
Click to collapse
Thank you i got it by turning of debugging mode, strange it worked but cheers
I have this problem as well, tried doing above things, uninstalling drivers, reinstalling - help appreciated.
and Phone is working normal but after 5 second reboot and FC 's
Plz Help
same issue...
Has anyone found a sure fix for the issue presented by the original post? I am having this issue and I have tried different drivers, ftf's, computers, adb/fastboot/versions and flashtool versions. I have unlocked and relocked. Is rooting status "unknown" normal after bootloader unlock? -Z Ultra 6833 EU
Still no solution?
With my C6603 it does not allow to write boot aswell. Any final solutions?
edit: solution found: bootloader was not unlocked
Error flashing kernel
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
aravindjr said:
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
Click to expand...
Click to collapse
This is the wrong forum to ask this. This is the Xperia Z section.
Despite that, you need to unlock your bootloader to flash kernels via fastboot.
Sent from my C6603 using Tapatalk
After months using stock everything I decided to flash CM11 yesterday, I'm doing exactly same step as I was doing when on 4.1/4.2 but it seems like it doesn't works, I'm not even sure that my BL is unlocked despite success message, when trying to reboot after unlock BL I had a bootloop and when trying to recover with Sony's Flashtool it says 'device not unlocked'. So I repaired with PCC and restarted from scratch but same results today.
I'm totally lost as like I said I was doing exactly same thing on the same PC.
Edit : Now my XZ doesn't even start! I have the red led blinking while connected with usb, power+ Vol+ doesn't do anything, no vibrations at all!
I was on latest sony official ROM
Edit2 : Tryied again to recover with Sony's Flashtool but it says "Mobile Locked" that's crazy!
aravindjr said:
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
Click to expand...
Click to collapse
Check PM
Relax!
4.3 introduced a new security feature. Look up "unlock bootloader 4.3 xperia z" for help :good:
babylonbwoy said:
After months using stock everything I decided to flash CM11 yesterday, I'm doing exactly same step as I was doing when on 4.1/4.2 but it seems like it doesn't works, I'm not even sure that my BL is unlocked despite success message, when trying to reboot after unlock BL I had a bootloop and when trying to recover with Sony's Flashtool it says 'device not unlocked'. So I repaired with PCC and restarted from scratch but same results today.
I'm totally lost as like I said I was doing exactly same thing on the same PC.
Edit : Now my XZ doesn't even start! I have the red led blinking while connected with usb, power+ Vol+ doesn't do anything, no vibrations at all!
I was on latest sony official ROM
Edit2 : Tryied again to recover with Sony's Flashtool but it says "Mobile Locked" that's crazy!
Click to expand...
Click to collapse
BatteryAidFree said:
4.3 introduced a new security feature. Look up "unlock bootloader 4.3 xperia z" for help :good:
Click to expand...
Click to collapse
I know I'm late but thanks anyway, just updated to 4.4.4 today, I'll look to your advice, thanks for replying, you're the only one that took time to write few words to help.
Hope it goes well!
babylonbwoy said:
I know I'm late but thanks anyway, just updated to 4.4.4 today, I'll look to your advice, thanks for replying, you're the only one that took time to write few words to help.
Click to expand...
Click to collapse
You're welcome! The only thing I can think is if you want to install/rate 5 stars my app, would be greatly appreciated! ("Battery Aid" - I can't post the link apparently, "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!")
use flashtool to writ kernel
fastboot remote command not allowed Xperia Z3
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
stevenmanzano said:
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
Click to expand...
Click to collapse
Look in the service menu to confirm if your bootloader is unlocked.
Enter *#*#7378423#*#* in the dialler, then look in Service info -> Configuration. It will say "Bootloader unlocked: Yes" if it's unlocked.
Sent from my C6603
solved remote command not allowed
stevenmanzano said:
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
Click to expand...
Click to collapse
By installing FLASHTOOL by Sony I was instantly notified that my bootloader was not unlocked, even though I had already unlocked it three or four times without any errors. So I unlocked it again. Then fastboot flashed my images just fine.
Hello everyone,
I bought an HTC one off ebay, having in mind I would flash custom rom on the device which I prefer for obvious reasons. But each time I open Hasson2000 Tool to get ID token I get this error in command prompt below:
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
'error: device offline
I have tried searching for solutions but I cant get one to actually fix my own issue, I do know the HTC bootloader has been unlocked and rooted because I can boot to bootloader menu, boot to recovery mode and on top on the screen it says *****TAMPERED***** just below it says ***UNLOCKED*** I figured the previous owner tried locking bootloader before selling it off.
I noticed other commands dont work like reboot device on the tool probably because of that error or my htc is not recognised am not sure. am running Windows 8.1 Pro on my laptop.
What I have done so far
Rebooted phone several times
Rebooted my laptop several times
Unplugged and plugged in usb cable
Used different usb ports it recognises my htc because I can view my SD card or transfer files between laptop and phone.
Please guys I neeed your help with this, thanks.
Infoseye said:
Hello everyone,
I bought an HTC one off ebay, having in mind I would flash custom rom on the device which I prefer for obvious reasons. But each time I open Hasson2000 Tool to get ID token I get this error in command prompt below:
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
'error: device offline
I have tried searching for solutions but I cant get one to actually fix my own issue, I do know the HTC bootloader has been unlocked and rooted because I can boot to bootloader menu, boot to recovery mode and on top on the screen it says *****TAMPERED***** just below it says ***UNLOCKED*** I figured the previous owner tried locking bootloader before selling it off.
I noticed other commands dont work like reboot device on the tool probably because of that error or my htc is not recognised am not sure. am running Windows 8.1 Pro on my laptop.
What I have done so far
Rebooted phone several times
Rebooted my laptop several times
Unplugged and plugged in usb cable
Used different usb ports it recognises my htc because I can view my SD card or transfer files between laptop and phone.
Please guys I neeed your help with this, thanks.
Click to expand...
Click to collapse
I'd usually get this message if I forget to press "Fastboot" when in bootloader mode. So you still might actually be in bootloader mode but not in Fastboot mode too.
I tried several times now it says error: device not found now am confused
hello, my xperia sp has been soft-bricked! im trying to get it back to normal, but i can't!
i downloaded the stock firmware for my phone c5306( .205 ) and im trying to flash it via flashtool.
a hundred times i have got the system.sin error! drivers updated, tried with different pcs, different cables! no result, same error!
i also tried excluding system.sin from the right column, all other files are flashed normally! but when i try system.sin, error!
also, my phone shows green light after sometime after i plug it into the charger! when i remove it and hold power button for 2sec, the red led flashes and goes off, if i hold it it keeps flashing!
also it will only show sony logo after flash mode has been exited!
please help me! i have spent 3 days on it(day and night) but still no solution!:crying:
i just got this phone 1 week ago!
i have also attached the image of the error!
please help devs! i will be very greatful!
the reason i think is that when the system.sin is almost done, the phone is exiting flashmode? this might be the reason?
if yes please give solution!
( i checked by disconnecting phone while the flashing was halfway through, same error!)
Firstly, try flashing some different FTF files, as this is most likely the problem.
If that doesn't work and you are already on unlocked bootloader, you can try the following:
1. Flash everything in the .ftf file using the latest Flastool, except system (system.sin).
2. Open the .ftf file using 7zip and extract the system.sin.
3. Flash the system.sin using fastboot: fastboot flash system system.sin.
The above method has worked for others with similar problems. Again, only for unlocked bootloader.
If that fails you might also have corrupted or broken NAND memory. Hardware issue is surely a probability.
Other might have other suggestions...
Gamm86 said:
If you are already on unlocked bootloader, you can try the following:
1. Flash everything in the .ftf file using the latest Flastool, except system (system.sin).
2. Open the .ftf file using 7zip and extract the system.sin.
3. Flash the system.sin using fastboot: fastboot flash system system.sin.
The above method has worked for others with similar problems. Again, only for unlocked bootloader.
If that fails you might also have corrupted or broken NAND memory. Hardware issue is surely a probability.
Other might have other suggestions...
Click to expand...
Click to collapse
somehow i flashed ftf! but now the phone reboots only after flash/fastboot mode, first it used to show only sony logo, but now it shows sony,xperia, xperia bootanimation, off!
if i flash system.sin through fastboot, where should i place the file?
moosa27 said:
if i flash system.sin through fastboot, where should i place the file?
Click to expand...
Click to collapse
In the folder where you extracted fastboot.
Fastboot is a program on it's own. I'm not talking about the fastboot mode in flashtool. (http://forum.xda-developers.com/showthread.php?t=2588979)
Again, ONLY FOR UNLOCKED BOOTLOADER.
If you haven't unlocked it, this methode won't work.
Try flashing a different FTF, as I mentioned after editing my post.
Gamm86 said:
In the folder where you extracted fastboot.
Fastboot is a program on it's own. I'm not talking about the fastboot mode in flashtool. (http://forum.xda-developers.com/showthread.php?t=2588979)
Again, ONLY FOR UNLOCKED BOOTLOADER.
If you haven't unlocked it, this methode won't work.
Try flashing a different FTF, as I mentioned after editing my post.
Click to expand...
Click to collapse
now whats happening is, when i press power button for 2 or more secs, the red led flashes! when i connect the phone to wall charger, red led stays on.
i took device into fastboot mode and rebooted into device via flashtool......
then the device booted normally and showed android id upgrading......... app 49 of 179 then off!
does this mean i should charge it? as far as i know, i have 70-80% battery.......
Leave phone in charging overnight and stay calm
Sent from my C5302 using XDA Free mobile app
moosa27 said:
then the device booted normally and showed android id upgrading......... app 49 of 179 then off!
does this mean i should charge it? as far as i know, i have 70-80% battery.......
Click to expand...
Click to collapse
Your battery is dead, but since android said it was upgrading apps, this means your problem is most likely fixed.
Let it charge for a few hours.
Gamm86 said:
You battery is dead, but since android said it was upgrading apps, this means your problem is most likely fixed.
Let it charge for a few hours.
Click to expand...
Click to collapse
Thanks.for all your efforts my phone was back normal yesterday
moosa27 said:
Thanks.for all your efforts my phone was back normal yesterday
Click to expand...
Click to collapse
Glad you got everything sorted.
Unless an Xperia SP has hardware problems, i'm quite sure it cannot get fully bricked.
I have exactly the same problem
Could you give me the steps to fix this problem? I have exactly the same problem when i try to install android with flashtool. No matter the version:
"24/017/2014 23:17:58 - ERROR - Processing of system.sin finished with errors.
24/017/2014 23:17:58 - INFO - Ending flash session
24/017/2014 23:17:58 - ERROR - 31 : A device attached to the system is not functioning.
24/017/2014 23:17:58 - ERROR - Error flashing. Aborted"
And when i try to power up a red led is blinking. If i connect the charger the red led stays on. Also, its hard to enter flashmode (green led) and fast boot (blue led) doesn't seem to work in Flashtool (in order to select system.sin to Flash). Despite the blue led is on, Flashtool doesn't let me to reboot into fastboot mode.
You got yourself a driver problem. Reinstall the drivers
i have the same problem. any solution for locked bootlader?sir please help i always get system.sin error when i flashed the stock rom.
ohmygel said:
i have the same problem. any solution for locked bootlader?sir please help i always get system.sin error when i flashed the stock rom.
Click to expand...
Click to collapse
you cant be hard bricked on locked bootloader . it hapenned to me. solutions:
1. get another ftf files, sometimes ftf can get damaged.
2. install custom drivers.
3. try different pcs (My Solution )
4. charge the phone 1 day (24hrs)
5. unlock bootloader and flash custom kernel and flash a rom, then u can flash stock and relock bl
6. change ur cable.
if no one of this solutions fix ur problem u are so bad
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
MAAAN!!! this worked!! I was spending many days and nights wondering WHY??? Thank you!!! :laugh::laugh:
I could flash 4.4.4 normally with the latest flashtool but no 5.x.x version would work!
If this is important enough maybe Androxyde will take a look into that...
Anyways , I am happy now^^
knauji said:
MAAAN!!! this worked!! I was spending many days and nights wondering WHY??? Thank you!!! :laugh::laugh:
I could flash 4.4.4 normally with the latest flashtool but no 5.x.x version would work!
If this is important enough maybe Androxyde will take a look into that...
Anyways , I am happy now^^
Click to expand...
Click to collapse
Lol its not a known problem and please do not notify Androxyde about it. Version post 0.19.8.6 but prior to 0.19.9.1 uses a template file called fsc to accommodate new xperia devices. This breaks support for older xperia devices that doesn't have the fsc template. The template can be created of course, but it seemed no one from the xperia sp community want to contribute lol.
So the versions that will make ftf flashable again is 0.19.8.6 and 0.19.9.1+. You could have solve this by yourself if you read the note given on the website properly.
TechnoSparks said:
Lol its not a known problem and please do not notify Androxyde about it. Version post 0.19.8.6 but prior to 0.19.9.1 uses a template file called fsc to accommodate new xperia devices. This breaks support for older xperia devices that doesn't have the fsc template. The template can be created of course, but it seemed no one from the xperia sp community want to contribute lol.
So the versions that will make ftf flashable again is 0.19.8.6 and 0.19.9.1+. You could have solve this by yourself if you read the note given on the website properly.
Click to expand...
Click to collapse
Well, I don't know what FSC is and the changelog on the website says the new version is compatible with all xperia devices....so that is what I used. How could I know..?
but it works now, that's all I need^^
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
Thanks button is broken but THANKS ! It was driving me crasy !!! :highfive:
BTW, the version is 0.9.18.6
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
I seach like crazy and ask Questions w/out an answer! THX a lot!!! It worked!!!
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
can you provide me the download link of flashtool 0.18.6
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
small update:
after updating to 52.0.A.8.50, I made "factory settings" to reset it to the old version.
But when I restart without wifi, I find build 52.0.A.8.50 again
And now the OEM unlock option, which was usable before, has turned gray !! Mystery for me.
Obviously he wants me to update to 52.0.A.8.85 !!!
SOLVED INFORMATION:
I was wrong in writing IMEI of my device, and I put a wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
bibibabi said:
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
Click to expand...
Click to collapse
Try .131 vor wait for September
For wait for Q, maybe Sony will remove more DRM TA protection like it did with P
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
bibibabi said:
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
Click to expand...
Click to collapse
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
MartinX3 said:
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
Click to expand...
Click to collapse
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
bibibabi said:
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
Click to expand...
Click to collapse
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
MartinX3 said:
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
Click to expand...
Click to collapse
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
bibibabi said:
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
Click to expand...
Click to collapse
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
MartinX3 said:
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
Click to expand...
Click to collapse
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
bibibabi said:
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
Click to expand...
Click to collapse
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
MartinX3 said:
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
Click to expand...
Click to collapse
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
bibibabi said:
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
Click to expand...
Click to collapse
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
MartinX3 said:
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
Click to expand...
Click to collapse
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
bibibabi said:
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
Click to expand...
Click to collapse
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
MartinX3 said:
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
Click to expand...
Click to collapse
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
bibibabi said:
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
Click to expand...
Click to collapse
Should be impossible without a computer for initial installation
MartinX3 said:
Should be impossible without a computer for initial installation
Click to expand...
Click to collapse
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
bibibabi said:
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
Click to expand...
Click to collapse
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
MartinX3 said:
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
Click to expand...
Click to collapse
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
bibibabi said:
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
Click to expand...
Click to collapse
Please use the August .131 firmware and my matching stock twrp