Hi guys,
need some help. I'm tryin to unlock bootloader on .681, but always Failed. I have latest flashtool, drivers, win7 x64. I was unlocked bootloader on .136, than relocked it and lost TA backup. Now with fastboot or flashtool i can't unlock it(sometimes it says - FAILED (remote: Command did not succeed) or FAILED (remote: Device is already rooted)) Need some help.
Update flashtool.
Delete
pharix said:
Update flashtool.
Click to expand...
Click to collapse
latest. Deleted and 2 more times installed.
lewqou said:
latest. Deleted and 2 more times installed.
Click to expand...
Click to collapse
I never used flashtool to unlock bootloader but use other method. Give it a try.
pharix said:
I never used flashtool to unlock bootloader but use other method. Give it a try.
Click to expand...
Click to collapse
unlocking via fastboot gives me a 2 messages : FAILED (remote: Command did not succeed) or FAILED (remote: Device is already rooted)
lewqou said:
unlocking via fastboot gives me a 2 messages : FAILED (remote: Command did not succeed) or FAILED (remote: Device is already rooted)
Click to expand...
Click to collapse
What is the value received? is it 0.5?
pharix said:
What is the value received? is it 0.5?
Click to expand...
Click to collapse
Yes
"fastboot.exe -i 0x0fce getvar version"
"version:0.5"
"finished.total time : 0.03s"
lewqou said:
Yes
"fastboot.exe -i 0x0fce getvar version"
"version:0.5"
"finished.total time : 0.03s"
Click to expand...
Click to collapse
Can you post a screenshot?
Take it
lewqou said:
Take it
Click to expand...
Click to collapse
i was with the same problem, then i got unlock in the latest version of the flashtool, try if you can flashmode with flashtool!
I had same problem on my z... I went to the Sony site again and copied the unlock code again.. In my eyes it was the same as the first time I unlocked... But it worked for me... I must admit that I tried to unlock about 30 times...
So keep on trying...
Sent from my C6903 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2703456 read that thread, the problem is you have relocked without ta partition and Fastboot looks for that. You need to recreate the folder structures in flashtool to force a flashmode unlock.
Sent from my C6903 using XDA Premium 4 mobile app
Related
I have a locked bootloader, and I don't want to unlock it to keep the warranty.
I tried installing Blackrose (to install JB) without success.
I have a SLCD Nexus One with HBOOT 0.35.0017
The automated installer hangs at "*Waiting for device...".
I have installed the drivers and I can see my N1 doing "fastboot.exe devices".
I tried this guide http://forum.xda-developers.com/wiki/HTC_Nexus_One/TexasICS/Installing_Guide
fastboot boot go35.lol
downloading 'boot.img'...
OKAY [ 0.031s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.094s
What am I doing wrong? Do I have to unlock the bootloader?
In the README it says to flash go35.lol to the recovery partition using the flash_image method, but I can't find anywhere anything about it.
I currently have 4EXT recovery.
no i dont have to unlock the bootloader. locked bootloader is fine. connect ur phone when it is booted normally(not in fastboot mode). now run blackrose.exe
installation should begin automatically. also remember to turn of ur antivirus during this process
Sent from my Nexus One using Tapatalk
n1newbie said:
no i dont have to unlock the bootloader. locked bootloader is fine. connect ur phone when it is booted normally(not in fastboot mode). now run blackrose.exe
installation should begin automatically. also remember to turn of ur antivirus during this process
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
I don't think you can install blackrose without unlock the bootloader first.
taodan said:
I don't think you can install blackrose without unlock the bootloader first.
Click to expand...
Click to collapse
no buddy. you can install blackrose wid locked bootloader aswell.
for reference see this post by the dev of blackrose. point 7
http://forum.xda-developers.com/showpost.php?p=20548080&postcount=607
Sent from my Nexus One using Tapatalk
I have a problem to install a ROM or turn on my htc one, when I'm in the recoveryMod I go to install from sdcard but I'm Still an error that says "E: can not mount / sdcard /" the problem is start when I try to install the ROm (Android Revolution HD 7.2) I was on the ROM (Maximus7_5.0.0)
it is possible to fix this problem?
it is possible to return to the original ROM?
I'm really deseprer two days I'm looking for a soulition but I find nothing
thank you
help please
help please
Hi
Greetings,
1. Flash the recovery again and try again
2. You can use abd sideload
For abd sideload you need latest abd drivers.
And search for abd sideload and how to use as iam not an one user and dnt know much about sideload but it will help you install Rom directly from pc
Sent from my HTC Sensation Z710e using xda premium
to flash the recovery type
Code:
fastboot flash recovery recovery_name.img
Code:
fastboot erase cache
and then try again
and yes you can return to stock, just decide what you want to do
I already tried to do but it does not work, still the same error
yes I'd like to return to the original version, coment I do?
mehdi2006 said:
I already tried to do but it does not work, still the same error
yes I'd like to return to the original version, coment I do?
Click to expand...
Click to collapse
well in that case the best option is to flash a RUU easy
run this command and paste your output
Code:
fastboot getvar all
matt95 said:
well in that case the best option is to flash a RUU easy
run this command and paste your output
Code:
fastboot getvar all
Click to expand...
Click to collapse
how can I do?
Reboot into bootloader/fastboot with phone connected to pc
It must say fastboot usb
and in abd command
Type the given code your done
Just select that and copy paste here
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Reboot into bootloader/fastboot with phone connected to pc
It must say fastboot usb
and in abd command
Type the given code your done
Just select that and copy paste here
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
i have this error
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.054s
Hi
Greetings,
Are you typing it correctly ?
Is your device connected properly to pc and can abd find your device?
Sent from my HTC Sensation Z710e using xda premium
mehdi2006 said:
i have this error
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.054s
Click to expand...
Click to collapse
yeah, as i thought... is your bootloader unlocked right?
shrex said:
Hi
Greetings,
Are you typing it correctly ?
Is your device connected properly to pc and can abd find your device?
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes i try it 2-3 times always the same error
ok that's not a problem, we only need the version-main to see which RUU you have to run... type
Code:
fastboot getvar version-main
matt95 said:
yeah, as i thought... is your bootloader unlocked right?
Click to expand...
Click to collapse
yes its unlocked
try the command above
matt95 said:
ok that's not a problem, we only need the version-main to see which RUU you have to run... type
Code:
fastboot getvar
Click to expand...
Click to collapse
version-main 1.29.206.11
i checked but there is no RUU for that version yet, you have to flash a Nandroid backup to turn back to stock...
matt95 said:
i checked but there is no RUU for that version yet, you have to flash a Nandroid backup to turn back to stock...
Click to expand...
Click to collapse
how I should flash?
type
Code:
fastboot getvar cid
matt95 said:
type
Code:
fastboot getvar cid
Click to expand...
Click to collapse
but i dont have any backup :s
Hi.
I have searched for a solution but I couldn't find anything.
I was trying to install GCam and download the file here and when I selected Magisk Module in Magisk app my phone rebooted and didn't boot it was stuck in the screen after Android One logo.
I manually rebooted my phone and it showed me this message.
I can't take a pic of my phone because I don't have a camera or another phone right now but the error is the same in the I uploaded.
Has anyone had the same problem?
I can't flash the stock rom using the MiFlash 'cause it returns an erro: error: "Flash bluetooth_a error"
I solved the problem by unlocking the bootloader again.
gsilva92 said:
I solved the problem by unlocking the bootloader again.
Click to expand...
Click to collapse
I am sorry of course. But how did you unlock the bootlaoder? I just have a mistake
"remote: 'Flashing Unlock is not allowed"
Damir51 said:
I am sorry of course. But how did you unlock the bootlaoder? I just have a mistake
"remote: 'Flashing Unlock is not allowed"
Click to expand...
Click to collapse
Sorry for taking too long to answer.
You can unlock your bootloader by following this guide.
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
Guys I'm in June update I already enabled camera2api in March then I closed my bootloader for getting my mobile serviced under warranty but now I can't able to unlock_critical after unlocking bootloader some one tell me that is it essential to unlock_critical to flash stock ROM in future or I can skip this step to do other flashing stuffs ...
Sivakumar$ said:
Guys I'm in June update I already enabled camera2api in March then I closed my bootloader for getting my mobile serviced under warranty but now I can't able to unlock_critical after unlocking bootloader some one tell me that is it essential to unlock_critical to flash stock ROM in future or I can skip this step to do other flashing stuffs ...
Click to expand...
Click to collapse
I think you have to unlock critical.
mariosenta said:
I think you have to unlock critical.
Click to expand...
Click to collapse
Thanks I also wanted to I'll do further flashing after unlock critical I'll reinstall all ADB and use the latest platform tool and tell you the result
I still got this same error
Sivakumar$ said:
I still got this same error
Click to expand...
Click to collapse
What error? You have to select what to do next. Type "w" and hit enter to erase all
mariosenta said:
What error? You have to select what to do next. Type "w" and hit enter to erase all
Click to expand...
Click to collapse
After erasing do I need to type the command unlock_critical
Sivakumar$ said:
After erasing do I need to type the command unlock_critical
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766 you have very simple guide how to unlock bootloader in this tread. Please read it and folow the guide.
Sivakumar$ said:
After erasing do I need to type the command unlock_critical
Click to expand...
Click to collapse
After "fastboot -w" again my storage is erased but i can't able to do "unlock_critical" i tried even locking ny BL again but after oem unlovk i cant do critical unlock it always show me bunch of commands
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
refresh5 said:
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
Click to expand...
Click to collapse
Just patch boot.img and flash it
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Adnan008 said:
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Click to expand...
Click to collapse
Xperiafirm on xda to download full fw and newflasher to flash it
King081 said:
Xperiafirm on xda to download full fw and newflasher to flash it
Click to expand...
Click to collapse
do we lose data when flashing firmware?
Adnan008 said:
do we lose data when flashing firmware?
Click to expand...
Click to collapse
You can choose using newflasher
King081 said:
Just patch boot.img and flash it
Click to expand...
Click to collapse
Can you tell me how?
zaxdamian said:
Can you tell me how?
Click to expand...
Click to collapse
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
King081 said:
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
Click to expand...
Click to collapse
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
zaxdamian said:
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
Click to expand...
Click to collapse
I don't know what twrp you have, because we don't have one here and clearly your phones bootloader locked, this is about root and not twrp
Ok. I cant unlock bootloader, so how to get boot.img from stock file?
Unlock bootloader:
https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader
I tried it. Either I'm doing something wrong or it's not working
Everything works, I unlocked it myself, I just don't remember which command:
fastboot oem unlock
or
fastboot flash unlock
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
On comand fastboot flash unlock i have "fastboot: error: ANDROID_PRODUCT_OUT not set"
zaxdamian said:
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
Click to expand...
Click to collapse
Did you do that in fastboot or fastbootD
Fastboot D