I had unlocked, installed dual recovery and rooted my phone with LP. This latest update (270) removed my root and locked my bootloader (Service meuu says unlock allowed = Yes) . I tried to unlock it again using flash tool and adb cmd and both seem to fail. In flashtool it keeps saying that my code is wrong (I created a folder in custom folder with ulcode name and a txt file with the ulcode) still din work. In adb cmd i am getting
version: 0.5
finished. total time: 0.003s
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
I have installed all drivers in my system too. Any help?
ravi_buz said:
I had unlocked, installed dual recovery and rooted my phone with LP. This latest update (270) removed my root and locked my bootloader (Service meuu says unlock allowed = Yes) . I tried to unlock it again using flash tool and adb cmd and both seem to fail. In flashtool it keeps saying that my code is wrong (I created a folder in custom folder with ulcode name and a txt file with the ulcode) still din work. In adb cmd i am getting
version: 0.5
finished. total time: 0.003s
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
I have installed all drivers in my system too. Any help?
Click to expand...
Click to collapse
Try unlocking from Sony's site ( official method ) http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Good Luck :fingers-crossed:
Found the solution
Please check my post here http://forum.xda-developers.com/showpost.php?p=61450689&postcount=390
Related
I cant unlock my bootloader on xperia z
Bootloader unlock allowed: Yes
I used fastboot.exe -i 0x0fce getvar version to see if the device was attached properly
version: 0.5
finished. total time: -0.000s
also when I use fastboot.exe -i 0x0fce oem unlock 0x(my key from sony site)
It said FAILED (remote: Command did not succeed)
Try typing the command correctly. oem-unlock. Its a dash not a space
error: invalid vendor id '0x0FCE.oem'
Try to remove .exe from the command so it will be like "fastboot -I 0x0fce oem unlock 0xYOUR KEY" I was getting the same error before but it's worked after I did that.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
it's not working!
dragac90 said:
I cant unlock my bootloader on xperia z
Bootloader unlock allowed: Yes
I used fastboot.exe -i 0x0fce getvar version to see if the device was attached properly
version: 0.5
finished. total time: -0.000s
also when I use fastboot.exe -i 0x0fce oem unlock 0x(my key from sony site)
It said FAILED (remote: Command did not succeed)
Click to expand...
Click to collapse
Unlock it via flashtool.
Reinstall your driver package and reboot pc
dragac90 said:
I cant unlock my bootloader on xperia z
Bootloader unlock allowed: Yes
I used fastboot.exe -i 0x0fce getvar version to see if the device was attached properly
version: 0.5
finished. total time: -0.000s
also when I use fastboot.exe -i 0x0fce oem unlock 0x(my key from sony site)
It said FAILED (remote: Command did not succeed)
Click to expand...
Click to collapse
In linux you must have root priviledge.
Because i try it in my user and it say
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
and i use same code with root priviledge and it work.
...
OKAY [ 0.180s]
finished. total time: 0.180s
And in windows, i don't try it but i think you must execute fastboot code or bat script in administrator priviledge
Edit: Also in my first try it's not unlocking. But all time second time unlocking it. But IDK why it's not opening in first try
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
stygianblizzard said:
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
Click to expand...
Click to collapse
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
gee2012 said:
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
Click to expand...
Click to collapse
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
stygianblizzard said:
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
TWRP cannot flash the stock images. Only flash able zips. The modified zips linked by @gee2012 should work
gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
Just few mins got img downloaded. That was bloody awesome. I dont know how to thank you :laugh::laugh::laugh::good:
Superb
Its working again!!!!!
There HTC 626G, revision 1.79.401.100. During the study, on new devices starting with the revision (build) 1.72.401.101, with modified firmware recovery phone goes bootloop. Initially it was assumed that the problem was incompatible version recovery (old and new versions). new recovery was made under my revision, and after flashing turned bootloop.
When loading stock version:
fastboot flash recovery recovery_stock.img responses with:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
Since version error recovery not confirmed, it remains an unlocked bootloader.
When you enter the command:
C:\Users\bugae\Desktop\android>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
C:\Users\bugae\Desktop\android>fastboot oem identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\Users\bugae\Desktop\android>fastboot oem token
...
FAILED (remote: unknown command)
finished. total time: 0.020s
fastboot oem unlock (the tablet responses with a question screen where I can select "yes, unlock bootloader" and "no, don't unlock bootloader", but when I select yes it responses with an error "Unlock failed - Err:0x7000")
Standard methods do not work!(
How to be? What to do?
Backup 4pda.ru/forum/index.php?s=&showtopic=756527&view=findpost&p=53005677
Try using win droid toolkit, I had the same issue with my 626 and I fixed mine here's a link
http://forum.xda-developers.com/devdb/project/?id=1314#downloads
https://forum.xda-developers.com/showpost.php?p=77300835&postcount=2
Hi frend.
What do I have!
HTC 626G is written in the phone and on the box.
HTC 626ph on the phone cover.
626G and 626ph = from one box at purchase
CPU MTK6592
Android 4.4.2
build 1.78.401.100 and 1.79.401.100
When you enter commands: fastboot
fastboot: getvar version
fastboot out: getvar:version FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: getvar:version-bootloader FAILED (remote: not support on security)
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: getvar:version-main FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar serialno
fastboot out: getvar:serialno FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar product
fastboot out: getvarroduct FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar modelid
fastboot out: getvar:modelid FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar cidnum
fastboot out: getvar:cidnum FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar build-mode
fastboot out: getvar:build-mode FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar boot-mode
fastboot out: getvar:boot-mode FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar security
fastboot out: getvar:security FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar imei
fastboot out: getvar:imei FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: oem get_identifier_token
fastboot out: ...
FAILED (remote: unknown command)
finished. total time: 0.003s
Click to expand...
Click to collapse
fastboot oem get_identifier_token - error!
$ fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.003s
Click to expand...
Click to collapse
fastboot oem unlock - error! Unlocked, perhaps?
$ fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7000
)
finished. total time: 110.541s
Click to expand...
Click to collapse
I made backups
Backup HTC 626G 1.79.401.100 (for SP Flash Tool)
Backup HTC 626G 1.78.401.100 (for SP Flash Tool)
Backup HTC 626G 1.72.401.101 (for SP Flash Tool)
Instructions such!
If their upload to the phone via SP_Flash_Tool_v5.1348.01_SEC + download_agent MTK_AllInOne_DA.bin, phone is loaded. but there is no picture on the display (LСD), only backlight.
I have even copied preloader! by command dd if=/dev/preloader of=/mnt/sdcard/preloader.bin count=262144 bs=1 When copying he 256 KB. STOCK 1.79-1.78 Preloader
if it is open WinHEX and to edit the original 114kb (as in 0PM1100_A32MG_DUG_K44_SENSE53_htc_asia_1.03.707.1_Radio_MOLY_WR8_W1315_MD_WG_MP_V62_P4) and downloaded into the phone, it does not start. Not respond to the button.
Upload preloader in Backup HTC 626G 1.03.707.1 (для SP Flash Tool) (0PM1100_A32MG_DUG_K44_SENSE53_htc_asia_1.03.707.1_Radio_MOLY_WR8_W1315_MD_WG_MP_V62_P4)
Phone is turned on. No image, just backlighting. but it works.
There are still a similar patient. After loading TWRP recovery, It hangs on the splash screen HTC and reboots (bootloop). When downloading files from a backup of the original, nothing changes. (bootloop)
I can not understand why I can not get them to work. What else can be done?
Three weeks I can not understand.
I recommend to view a selection of photos on my topic.
c:\adb>fastboot devices
7XVKYLNZROBAIVFQ fastboot
c:\adb>fastboot oem unlock
FAILED (remote: 'unknown command')
Finished. Total time: 0.009s
warmachine20 said:
c:\adb>fastboot devices
7XVKYLNZROBAIVFQ fastboot
c:\adb>fastboot oem unlock
FAILED (remote: 'unknown command')
Finished. Total time: 0.009s
Click to expand...
Click to collapse
I have the same device, the same issue.
i have 5033F
the same issue
fastboot flashing unlock_critical
FAILED (remote: 'not allowed in locked state')
Finished. Total time: 0.003s
OEM Unlock enabled in developers option