failed to flash boot with unlocked bootloader (solved) - Sony Xperia Z Ultra

I got Z Ultra C6833
I can't run that command.
Every time i did, i got that failed remote thing
bootloader is unlocked and i am on latest firmware 270
I tried it on 290, it didn't work either
I tried with normal cmd or with run-as-admin mode, no news.
I tried with debug on/off, same result.
I can install dual recovery on 290 though, if i flash cm12 zip/gep zip from twrp, i got a dead z ultra.
No response at all. When i press power button, it will just vibrate once. That's all.
Then i need to re-flash the firmware.
So can someone tells me what i did wrong?
It was working fine most of the procedure to install GPE previously.
Thanks anyway.
--------------------------
It turned out my bootloader is locked
Once it is unlocked by following this
http://forum.xda-developers.com/showpost.php?p=58070067&postcount=34
All good to go. Thanks!

anyone?

u cant boot a cm kernel on a stock xperia rom or the other way around...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you want to install a stock xperia based rom from zip file, xperia stock or scrubbers gpe port.
Start ur device in fastboot and flash a stock rom kernel with fastboot flash boot
Now push a recovery to the device with fastboot flash recovery
Reboot to recovery
Click to expand...
Click to collapse
If you are currently on stock rom and want to flash a cm based rom. You can do this by some metods.
Alternative A
This is if you want to do it from scratch. ie from stock rom and stock kernel and have no recovery.
Start ur device in fastboot and push a recovery to the device with fastboot flash recovery
Reboot to recovery
Flash cm based rom
Now extract boot.img from the cm based rom .zip file.
Start ur device in fastboot and push the boot.img to the device with fastboot flash boot
Reboot.
Click to expand...
Click to collapse
Alternative B
Or if you already have a working kernel and a working recovery.
Then you are already able to flash a cm rom. But when you reboot you will discover that the phone is "softbricked" as we call it.
The phone vibrate once and then turns off.
Start ur device in fastboot
Now extract boot.img from the cm based rom .zip file.
Push boot.img to your device with fastboot flash boot
Reboot.
Click to expand...
Click to collapse
You can get twrp from here https://dl.twrp.me/togari/
or from any boot.img file that has one recovery or many recoveries included in the .img file. For example stock based roms or kernels. But most easy is to use twrp.
I hope I didn't miss any detail. Just as if you have more questions. The heat today is making me ...tired..hard to concentrate

SÜPERUSER said:
u cant boot a cm kernel on a stock xperia rom or the other way around...
If you want to install a stock xperia based rom from zip file, xperia stock or scrubbers gpe port.
If you are currently on stock rom and want to flash a cm based rom. You can do this by some metods.
You can get twrp from here https://dl.twrp.me/togari/
or from any boot.img file that has one recovery or many recoveries included in the .img file. For example stock based roms or kernels. But most easy is to use twrp.
I hope I didn't miss any detail. Just as if you have more questions. The heat today is making me ...tired..hard to concentrate
Click to expand...
Click to collapse
Hey, Thanks for your lengthy reply.
I think i did your Alternative A,
stock rom, flash dual recovery from dual recovery installer,
then go to recovery and flash cm zip and die.
Then go to fastboot mode and flash the boot.img and i got that failed remote blah blah blah error.
I tried with unlocked bootloader/locked bootloader, still the same command.
I tried from cmd with or without admin privilege, I tried via flash tool, all failed.
So my question is why fastboot command failed on me? My understanding is if bootloader is locked, i can't fastboot.
This is the first time it is happening on my Z Ultra. This is my 3rd Z Ultra.
I had flashed GPe rom before and it has no such a problem.
I just need to have custom recovery and then flash the GPe zip file, that's it.
Thanks anyway.

pls copy paste the output from the terminal here

sending 'boot' (13408 KB)...
OKAY [ 0.427s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.432s

Enter *#*#7378423#*#* in the dialler, then look in Service info -> Configuration. It will say "Bootloader unlocked: Yes" if it's unlocked.
Click to expand...
Click to collapse
I doubt that the bootloader is unlocked

SÜPERUSER said:
I doubt that the bootloader is unlocked
Click to expand...
Click to collapse
Thanks. I will try when my phone is alive again. Now looks like it is dead after formatting system and rebooted.
Trying to reflash the firmware.
Thanks

Bootloader unlock allowed: Yes

leme ask u what operating system you are using?
Perhaps try to use the admin account.
Run cmd as admin
Activate admin account with net user administrator /active:yes
logout and login as administrator
Delete all drivers related to android and your phone.
Download system wide ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
Direct link: https://drive.google.com/file/d/0B0MKgCbUM0itVVFWRC02Q0VBQnc/view?usp=sharing
answer y on all the questions.
Now you can start a cmd from any folder by holding down left shift + right click and start command window here and then type the fastboot command

unlock bootloader failed
...
FAILED (remote: Command did not succeed)
finished. total time: 0.022s

win 7 running cmd with admin privilege.

unlock bootloader failed
...
FAILED (remote: Command did not succeed)
finished. total time: 0.022s
Click to expand...
Click to collapse
What? u said ur bootloader is unlocked?
Okay. Lets start from the beginning.
Pls upload a screenshot of the dialer with that page saying bootloader unlock allowed: XX etc etc
Enter *#*#7378423#*#* in the dialler, then look in Service info -> Configuration. It will say "Bootloader unlocked: Yes" if it's unlocked.
Click to expand...
Click to collapse

SÜPERUSER said:
What? u said ur bootloader is unlocked?
Okay. Lets start from the beginning.
Pls upload a screenshot of the dialer with that page saying bootloader unlock allowed: XX etc etc
Click to expand...
Click to collapse
there you go

good. Now edit your post and remove the image. No need for it anymore.
There is personal details in the pic like imei number so dont keep it here on the forum visible.
It says that bootloader is allowed to be unlocked. It does not say that it is unlocked.
So what I am saying is that your bootloader is still locked.
You need to UNLOCK your bootloader. Follow the steps here to do so
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
There are also video guides showing how its done https://www.youtube.com/watch?v=iIdJg7KNH3A
IMPORTANT. skip the Android SDK part described in the guides. You do not need this. You already have fastboot working.
In short words what you need to do is to write down your imei number and paste it onto sony website when you are about the send the email.
Now go to your email inbox and check your mail. There should be a code from sony dev.
Start phone in fastboot mode and do
fastboot -i 0x0fce oem unlock 0xKEY <- replace the word KEY with the code you received in the mail.
If the output succeeded your bootloader are now unlocked.

SÜPERUSER said:
good. Now edit your post and remove the image. No need for it anymore.
There is personal details in the pic like imei number so dont keep it here on the forum visible.
It says that bootloader is allowed to be unlocked. It does not say that it is unlocked.
So what I am saying is that your bootloader is still locked.
You need to UNLOCK your bootloader. Follow the steps here to do so
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
There are also video guides showing how its done https://www.youtube.com/watch?v=iIdJg7KNH3A
IMPORTANT. skip the Android SDK part described in the guides. You do not need this. You already have fastboot working.
Click to expand...
Click to collapse
Thanks. I am aware that, already cropped the image and uploaded the cropped one.
I don't think it is unlocked.
There are two messages when i tried to unlock from cmd
First one is
...
FAILED (remote: Command did not succeed)
finished. total time: 0.022s
Second one is
...
FAILED (remote: Device is already rooted)
finished. total time: 0.008s
this is the command i run from cmd with/without admin
fastboot -i 0x0fce oem unlock 0xUNLOCK_KEY

tell me exactly what you write in the terminal. Exluding the code from sony, don't paste it here.
I don't understand why you get two different answers?

pm-ed you.

I am on a custom rom but I get the same result as you.
C:\Users\Administrator\Downloads>fastboot getvar version
version: 0.5
finished. total time: 0.005s
C:\Users\Administrator\Downloads>fastboot oem unlock
...
FAILED (remote: Device is already rooted)
finished. total time: 0.014s
Click to expand...
Click to collapse
What .ftf file did you flash when going back to stock after having a "dead device"?
Can you provide link? Name? Is it from here on the forum?
For example the ftf thread?
http://forum.xda-developers.com/xpe...tf-depository-sony-firmware-releases-t2829387
or here?
http://forum.xda-developers.com/xperia-z-ultra/general/ftf-14-5-0-270-customized-hk-t3114261
One method you can try but that is a bit outdated. Waaay outdated. From when this device was released on the market.
But you could try the method of unlocking it with flashtool
Quote from other post.
This will wipe your phone, so backup your stuff
You only need to unlock the bootloader if you want to run either a custom kernel or a custom ROM. Most ROMs based on the Sony releases will run on a locked bootloader.
Instructions:
Go to Sony's Developer site
Request the unlock key and check your mail straight away. Email is quick these days.
Open the latest Flashtool on your computer
Click the "BLU" icon
Follow the steps and enter your unlock key
Click to expand...
Click to collapse
If you do not have flashtool installed. Pls install.
Link: https://docs.google.com/uc?id=0ByK8JL7P6wDTdmtKYUpPcW93Zjg&export=download
Using older version cause newest version has weird issues with "pls move files from administrator folder to XXX X...."
This is the main window of flashtool
Click the BLU button
Follow the instruction... On z u this is holding vol down when plugging in the cable
It will now ask for the code.
Fill in the code and proceed.
Notice that my window says "relock". This is because my bootloader is already unlocked. In your case the window should say "unlock".

Hey, thanks for the help, I followed this and it works. I mean i can unlock it. Time to have fun now. Thanks for your time and help.
http://forum.xda-developers.com/showpost.php?p=58070067&postcount=34

Related

Wiperd partitions can't go to CWM

Hei. Yesterday i unlocked m xperia z ultra, after process i install cwm, then i went to recovery and before install CM i wiped all partition.
Now i have a problem to go in CWM and phone is stucking on SONY logo ( is normal because is no any system on it )
How can i reflash it?
Is any possibility to lock bootloader and flash it via SEUS?
Or any other suggestion?
Dabman said:
Hei. Yesterday i unlocked m xperia z ultra, after process i install cwm, then i went to recovery and before install CM i wiped all partition.
Now i have a problem to go in CWM and phone is stucking on SONY logo ( is normal because is no any system on it )
How can i reflash it?
Is any possibility to lock bootloader and flash it via SEUS?
Or any other suggestion?
Click to expand...
Click to collapse
No system = No boot
We actually need some of the sony stuff on the phone to get the custom ROMs to work, and you may well have deleted those bits.
To be safe I would download a generic US/EU 757 FTF and flash that with Flashtool https://unrestrict.li/flashtool in flashmode. there are guides on here for doing that if you dont know how.
after that you will need to flash a recovery again, the best one to use is the on in the kernel that is in the ROM's zip (boot.img) this can also be flashed with flashtool (fastboot mode this time). Once you have recovery flash the ROM and just wipe data/cache/dalvik
blueether said:
No system = No boot
We actually need some of the sony stuff on the phone to get the custom ROMs to work, and you may well have deleted those bits.
To be safe I would download a generic US/EU 757 FTF and flash that with Flashtool https://unrestrict.li/flashtool in flashmode. there are guides on here for doing that if you dont know how.
after that you will need to flash a recovery again, the best one to use is the on in the kernel that is in the ROM's zip (boot.img) this can also be flashed with flashtool (fastboot mode this time). Once you have recovery flash the ROM and just wipe data/cache/dalvik
Click to expand...
Click to collapse
i have phone in fastboot mode ( blue light )
and phone is detected like "Android ADB Interface"
it was S1Boot and i installed ADB Drivers
so wat's now? because phone is not reconized in this mode by flashtool
ps. how can i get stock boot and lock now recovery ? ( i will be able unlock it after i will lock it now? )
Dabman said:
i have phone in fastboot mode ( blue light )
and phone is detected like "Android ADB Interface"
it was S1Boot and i installed ADB Drivers
so wat's now? because phone is not reconized in this mode by flashtool
Click to expand...
Click to collapse
Can you get it into flashmode? Vol down when connecting to PC, led will flash (green?) for about .5 sec before going out.
If you can get it into flash mode it should be an easy fix.
blueether said:
Can you get it into flashmode? Vol down when connecting to PC, led will flash (green?) for about .5 sec before going out.
If you can get it into flash mode it should be an easy fix.
Click to expand...
Click to collapse
yes green for 0.5 sec but then is nothing... after few second is trying to boot with sony logo
Dabman said:
yes green for 0.5 sec but then is nothing... after few second is trying to boot with sony logo
Click to expand...
Click to collapse
What is the output to flashtool then you do both fastboot and flash mode?
@LordManhattan, you around? I'm off to sleep as I've got 500km to drive tomorrow
blueether said:
What is the output to flashtool then you do both fastboot and flash mode?
@LordManhattan, you around? I'm off to sleep as I've got 500km to drive tomorrow
Click to expand...
Click to collapse
"Wait for flash mode..."
and instruction how to go to flash mode.
and... i try to install use adb sideload... after uploading on phone and starting installation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Download QuickIMG
- Download BOOT.img
- Put your Ultra in Fastboot (Blue LED)
- Open QuickIMG
- Flash BOOT.img
- Disconnect your Ultra and power it on. Press VOL UP a couple of times when the LED turns on. You're now in Recovery. Flash CM11 or whatever again.
LordManhattan said:
- Download QuickIMG
- Download BOOT.img
- Put your Ultra in Fastboot (Blue LED)
- Open QuickIMG
- Flash BOOT.img
- Disconnect your Ultra and power it on. Press VOL UP a couple of times when the LED turns on. You're now in Recovery. Flash CM11 or whatever again.
Click to expand...
Click to collapse
Even after flashing is stuck on SONY logo...
EDIT: CM is working great. GPE don't boot, anyway is enought. Thank U
Dabman said:
Even after flashing is stuck on SONY logo...
Click to expand...
Click to collapse
I think you need to get into flash mode and flash loader/partitions/elable/kernel/rpm/etc no need to flash system. I hope that you can get it back
blueether said:
I think you need to get into flash mode and flash loader/partitions/elable/kernel/rpm/etc no need to flash system. I hope that you can get it back
Click to expand...
Click to collapse
Now imei imei lost.
Hmmm custom is working but imei is gone, and flash tool is not working :/
just don't see phone even in this is in flash mode.
Dabman said:
Now imei imei lost.
Hmmm custom is working but imei is gone, and flash tool is not working :/
just don't see phone even in this is in flash mode.
Click to expand...
Click to collapse
So you have a booting ZU now, but imei is missing?
the imei issue is from a non compatible, but in your case maybe missing, baseband. If you go to settings/about phone what is the baseband?
After a little reading I found these instructions for flashing a ftf via adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=1562110
Extract the ftf (you may need to change the extension to .zip) then you will get something like 10 *.sin files, kernel.sin, system.sin, userdata.sin, etc
Should be able to then flash them with the fastboot command
fastboot flash boot kernel.sin
fastboot flash system system.sin
fastboot flash userdata userdata.sin
...
Flash all of them to go back to a stock system
This is untested by me so use with caution, you might want to do a bit more research on fastboot/adb and flashing
you might have to install adt-bundle
blueether said:
So you have a booting ZU now, but imei is missing?
the imei issue is from a non compatible, but in your case maybe missing, baseband. If you go to settings/about phone what is the baseband?
After a little reading I found these instructions for flashing a ftf via adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=1562110
Extract the ftf (you may need to change the extension to .zip) then you will get something like 10 *.sin files, kernel.sin, system.sin, userdata.sin, etc
Should be able to then flash them with the fastboot command
fastboot flash boot kernel.sin
fastboot flash system system.sin
fastboot flash userdata userdata.sin
...
Flash all of them to go back to a stock system
This is untested by me so use with caution, you might want to do a bit more research on fastboot/adb and flashing
you might have to install adt-bundle
Click to expand...
Click to collapse
D:\android-sdk-windows\sdk\platform-tools>fastboot flash boot kernel.sin
sending 'boot' (9562 KB)...
OKAY [ 0.312s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.312s
Dabman said:
D:\android-sdk-windows\sdk\platform-tools>fastboot flash boot kernel.sin
sending 'boot' (9562 KB)...
OKAY [ 0.312s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.312s
Click to expand...
Click to collapse
Code:
fastboot flash <PARTITION_NAME> <PARTITION_FILE.sin>
as in the post above
blueether said:
Code:
fastboot flash <PARTITION_NAME> <PARTITION_FILE.sin>
as in the post above
Click to expand...
Click to collapse
yes partition name BOOT and file name kernel.sin...
or another?
Dabman said:
yes partition name BOOT and file name kernel.sin...
or another?
Click to expand...
Click to collapse
sorry, I misread your post.
What partitions did you wipe fs_1 and fs_2? I think these will be stopping the radio working. anythig else that you wiped (not worried about data and system and cache)
It would be much easier if flashmode worked
Exactly what happens then you do this:
Turn off phone
Hold vol. down key
Connect to PC
How long does it stay in flashmode and you say flashtool doesn't see it in flashmode?
blueether said:
sorry, I misread your post.
What partitions did you wipe fs_1 and fs_2? I think these will be stopping the radio working. anythig else that you wiped (not worried about data and system and cache)
It would be much easier if flashmode worked
Exactly what happens then you do this:
Turn off phone
Hold vol. down key
Connect to PC
How long does it stay in flashmode and you say flashtool doesn't see it in flashmode?
Click to expand...
Click to collapse
phone is detected in flash mode, about 1min tjen is boot to sustem. but it cant be flashed... flasher dont reconize phone.
i was thinking about using dd and on working system overwrite partitions. extracted files on sd write to partition by dd.
Dabman said:
phone is detected in flash mode, about 1min tjen is boot to sustem. but it cant be flashed... flasher dont reconize phone.
i was thinking about using dd and on working system overwrite partitions. extracted files on sd write to partition by dd.
Click to expand...
Click to collapse
I'm having trouble understanding the first line.
Have you tried to uninstall all the drivers and reinstall them?

[MOD] OnePlus One Unlocker: Reset Unlock & Tamper Bit

Reset Unlock & Tamper Bit for OnePlus One​
My Friend @Polarfuchs has confirmed that our unlocker zips are working fine, after new CM11S 30O OTA update.
see post -- http://forum.xda-developers.com/showpost.php?p=54827475&postcount=182
==================== IGONE THIS WARNING ==========================
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
INTRO / CONCEPT
Click to expand...
Click to collapse
Most of us know that we can flash custom roms or can root device only after UNLOCKING the bootloader from fastboot mode.
If you relock your bootloader, you will need to do a full backup-and-restore whenever you decide to unlock it again.
This mod will allow you to unlock the bootloader without wiping the userdata as oppose to fastboot oem unlock command.
============================================================================
Note:
Many users having trouble to UNLOCK their device for the FIRST TIME by using this script.
Let me clarify few things for this mod.
The main purpose of this script is not UNLOCK Bootloader without wiping data.
It's main purpose is to reset tamper bit, which can not be done by any other way.
UNLOCK Bootloader without wiping data -- is another outcome of this MOD.
If you have not unlocked your device before (atleast for 1 time) by using command "fastboot oem unlock", then the script might not work for you.
In case your device is locked and you want to install this script from custom recovery like TWRP/CWM,
it will be possible only if, you can boot temporarily using command -- fastboot boot <custom_recovery.img>.
If this command failed, you will not be able to run the unlocker script and hence device will not be unlocked without wiping data
In which condition the device can be booted to custom recovery by using command -- fastboot boot <custom_recovery.img>, is still not very clear.
before running the command , check your device status "fastboot oem device-info"
and report your error with the following points
1) Did you unlock your device before by any means ? (or by fastboot oem unlock) ?
2) What is the recovery already installed in your device ?
3) What is the status of your device ? "fastboot oem device-info"
4) What error msg you got when tried to run command fastboot boot <custom_recovery.img>.
5) Steps you tried.
There are 4 possibilities of the the value set of the 2 bits ( unlock bit & tamper bit)
1) Unlock Bit - FALSE , Tamper Bit - FALSE
2) Unlock Bit - FALSE , Tamper Bit - TRUE
3) Unlock Bit - TRUE, Tamper Bit - FALSE
4) Unlock Bit - TRUE, Tamper Bit - TRUE
After getting proper error report from you , we can give confirmation about, in which of the above state,
fastboot boot <custom_recovery.img> will work and hence installing the unlocker script/mod/zip can help you to
UNLOCK your Bootloader without wiping DATA.
Kindly report your issues as I mentioned above...
Thanks
=================================================================================
There are generally 2 bits present on some partition of the phone for keeping track of unlocking.
1) lock / unlock bit
2) tamper bit
Both bits are initially FASLE. We can unlock bootloader by using command
Code:
fastboot oem unlock
and can see the device information by
Code:
fastboot oem device-info
like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you unlock, both bits will come TRUE. This mod will write the 2 bits in aboot partition and can reset
both bits (TOGGLE Bcsically) without factory reset as opposed to fastboot command fastboot oem unlock
So for One Plus One...
Code:
Partition - aboot (bootloader)
Unlock Bit Position - 0x000FFE10 Hex - (1048080) Decimal
Tamper Bit Position - 0x000FFE14 Hex - (1048084) Decimal
By @Polarfuchs
CREDIT
Click to expand...
Click to collapse
Credit to our Senior Member @Polarfuchs for finding out the partition & hex position that store the bits
Actually we both tested this concept and modified the script by @osm0sis and applied on our devices and got success.
We just added support for OnePlusOne (A0001)
You can check the following threads ...
1) http://forum.xda-developers.com/showthread.php?t=2796286
2) http://forum.xda-developers.com/showpost.php?p=54060253&postcount=11
3) http://forum.xda-developers.com/showpost.php?p=54060141&postcount=395
But it is in Beta State, may be more testing required, we will make an app for it like Nexus 5 Unlocker later...
Main Credit goes to our Recognized Contributor @osm0sis for his Nexus BootUnlocker script, flashable from recovery
http://forum.xda-developers.com/showthread.php?t=2239421
Thank you Sir - @osm0sis
WARNNING
Click to expand...
Click to collapse
Since this mod writes on aboot (bootloader) partition to reset the 2 flags, it may brick your phone.
Requesting developers to test it first, then give feedback here. After that any normal user can use it.
We will not be responsible for any damage or bricking of your phone. Install this zip at your own risk.
Edit:
Many users tried this and we can say that it is working , not beta anymore ...
DOWNLOAD
Click to expand...
Click to collapse
This script can be installed from CWM / TWRP recovery
Another trick for installation is
Code:
[B]fastboot boot <path/name of the recovery twrp img>[/B]
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
Download Here : View attachment OnePlusOne-BootUnlocker.zip
Download Bootloader lock-unlock Toggle Only Script View attachment OnePlusOne-OnlyBootloaderToggle.zip (not tested yet)
Download Tamper Bit Toggle Only Script View attachment OnePlusOne-OnlyTamperBitToggle.zip (not tested yet)
THANK YOU ALL
Click to expand...
Click to collapse
If you like this MOD please hit thanks button
Thank you all...
Worked for me when I was on locked bootloader and twrp and I could not unlock the bootloader with Fastboot OEM unlock
thank you
tkdsl said:
Worked for me when I was on locked bootloader and twrp and I could not unlock the bootloader with Fastboot OEM unlock
thank you
Click to expand...
Click to collapse
Thank you for your feedback...
Awesome work, it solved this issue:
http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-totally-locked-t2817735/page2
Thanks for implementing this and thanks to @Polarfuchs for finding out the flags location.
It worked for me as well, thanks!
Works great on my device. Problem solved :good:
Time to start flashing again and now i need not worry anymore cos if bootloader gets locked....the solution is right here
Flash by TRWP/CWM
Scann69 said:
Works great on my device. Problem solved :good:
Time to start flashing again and now i need not worry anymore cos if bootloader gets locked....the solution is right here
Click to expand...
Click to collapse
Do you just need to flash thru custom recoveries?
paztine said:
Do you just need to flash thru custom recoveries?
Click to expand...
Click to collapse
Yes. In my case I was stuck with TWRP recovery but it worked.
Scann69 said:
Yes. In my case I was stuck with TWRP recovery but it worked.
Click to expand...
Click to collapse
Thanks for a quick answer..
drakester09 said:
Awesome work, it solved this issue:
http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-totally-locked-t2817735/page2
Thanks for implementing this and thanks to @Polarfuchs for finding out the flags location.
Click to expand...
Click to collapse
sayeef said:
It worked for me as well, thanks!
Click to expand...
Click to collapse
Scann69 said:
Works great on my device. Problem solved :good:
Time to start flashing again and now i need not worry anymore cos if bootloader gets locked....the solution is right here
Click to expand...
Click to collapse
Thank you all friends...
paztine said:
Do you just need to flash thru custom recoveries?
Click to expand...
Click to collapse
Yes, But if you don't have custom recovery installed...
you can try
Code:
fastboot boot <path/name of the recovery twrp img stored in your pc>
I love this fix! Love it!
It absolutely cured my issue for not being able to unlock my bootloader as described here:
http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
can it work on stock cwm
Sent from my One using XDA Premium 4 mobile app
No since you can't flash unsigned zip I think. But you don't need to install a custom recovery. Instead you can boot into a custom recovery once with this command:"fastboot boot <name of custom recovery>"
Pls correct me if i am wrong:
This method is only usefull when you already have a recovery or root...
Because before the first unlocking you cant boot a custom recovery..
Or is possibly to boot a custom recovcery from fastboot when your device is locked??
Thank you
Enviado desde mi GT-S6500D usando Tapatalk 2
manudroid19 said:
Pls correct me if i am wrong:
This method is only usefull when you already have a recovery or root...
Because before the first unlocking you cant boot a custom recovery..
Or is possibly to boot a custom recovcery from fastboot when your device is locked??
Thank you
Enviado desde mi GT-S6500D usando Tapatalk 2
Click to expand...
Click to collapse
I've never tried to do this on a locked bootloader, but maybe you can "fastboot boot" the recovery image
I want to reset my phone to factory state, because i want to sell it.
I flashed the latest original ROM (including recovery and everthing else) and afterwards i locked the bootloader with "fastboot oem lock".
Unfortunately the tampered is still true:
Code:
C:\cm-11.0-XNPH25R-bacon-signed-fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.008s]
finished. total time: 0.011s
Can i set the tampered bit to false with this mod or is this not possible (yet)?
Just use the mod twice. The first time it will unlock and untamper, the second time it will lock.
Is the size of the zip 2,13k only?
Yes that is correct
Polarfuchs said:
Just use the mod twice. The first time it will unlock and untamper, the second time it will lock.
Click to expand...
Click to collapse
Worked! Great! Thanks!

Install new Recovery and Stock-ROM without IMEI and TA-Backup

Hi,
i've a little (big?) problem with my xperia tablet z (wifi; pollux_windy). 2 years ago i've rooted the stock-rom (4.2 or 4.4) and installed dual-recovery. a while a did nothing with the tablet. later i installed cyanogenmod 11 using the installed recovery. someday in 2016 i updated to cyanogenmod 12, but i can remeber how i did this exactly - maybe with a update-app? after the update to cm 12 the dual-recovery was overwritten with a cyanogenmod-recovery.
i don't know whether the bootloader is unlocked. i've unlocked i to root the device for the first time. when i search for the imei in "about tablet / status / imei" there is only "unknown". so at the moment i can't unlock the bootloader again.
when i boot the device in fastboot mode and try to flash twrp with
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
i get this error
fastboot flash recovery twrp.img
sending 'recovery' (10688 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
Click to expand...
Click to collapse
maybe this is because the bootloader isn't unlocked anymore? how can i find out that? how can i unlock the bootloader again without the imei or how can i find out the imei?
a user in a german forum said i can use the sony tool emma, this should reset the tablet. but WHAT will emma reset? can i flash twrp after that? can i root it again?
pieremallao
From fastboot you have to type
fastboot flash boot twrp.img
Click to expand...
Click to collapse
what is the different between
Code:
fastboot flash recovery
and
Code:
fastboot flash boot
?
PiereMallao said:
what is the different between
Code:
fastboot flash recovery
and
Code:
fastboot flash boot
?
Click to expand...
Click to collapse
as far as I have understood they are two different partition, Sony devices have the recovery in the boot partition whereas other phones, such as my OnePlus One, have a dedicated partition.
But what I'm sure is that when I flashed TWRP in my OPO I used the "fastboot flash recovery twrp.img" but in my pollux_windy I had to use "fastboot flash boot twrp.img"
doesn't work. i tried this on ubuntu 16.04 and in terminal i see the message
Code:
sending 'boot' (10688 KB)...
since 30 minutes. maybe this is because the bootloader isn't unlocked? but i'm not sure about that? how can i check this?
I remember very well the code I entered to get TWRP, now I'm also thinking you have somehow a locked bootloader...
PiereMallao said:
how can i check this?
Click to expand...
Click to collapse
if you use a stock ROM try: contacts/press three dots/Settings/press a place above home knob for few sec/it will appear Enter service Code/type *#*#7378423#*#*/Service info/Configuration
no, i dont use a stock, i use cyzanogenmod 12. i dont have the contacts app on mz tablet installed. i have tried to install google apps but the cyanogen recovery cant install the gapps. can i tried the service codes with an other app?
PiereMallao said:
can i tried the service codes with an other app?
Click to expand...
Click to collapse
Try to download ExDialer - Dialer & Contacts and launch the code from there. I tried with it but it didn't work (probably because I'm on RR) so I doubt it will work for you but give it a try.
With the same app try
Code:
*#*#759#*#*
and I have "OEM mode = off" but I'm not sure if it means that your bootloader is unlocked.
Or download Secret codes, the app's icon is a magick stick with a star at the and it shows some codes and you can lauch them from the app itself. I think it only shows the codes available to your phone/tablet because it doesn't show 7378423.
-Pepe said:
Try to download ExDialer - Dialer & Contacts and launch the code from there. I tried with it but it didn't work (probably because I'm on RR) so I doubt it will work for you but give it a try.
Click to expand...
Click to collapse
On CM there is no service menu, so it won't work.
Unlocking is possible with Flashtool or fastboot commands.
deleted

Can you unlock bootloader with the rom 26S?

Hello, the question is very simple: does anyone who has installed the rom 26S in x722 have been able to then unlock the bootloader or install another rom?
We know that in the rom 20S with the one that comes from the factory you can unlock the bootloader and install twrp, we know you can upgrade to the 26S, we know that there are people who have upgraded to 26S, but no one who has upgraded to 26S has Commented that it was able to install another rom then, only comment that the bootloader is blocked with the 26S.
All those who have updated to 26S you have to stay with her because you can not change?
Well if someone has succeeded, it would be nice to say how he did it.
Greetings.
*** TODAY, THE ONLY WAY TO LEAVE OFFICIAL 26S IS TO INSTALL THE ROM 01D, THAT UNLOCK THE BOOTLOADER AND ALLOWS US TO INSTALL ANY OTHER ROM. ***
My phone came with 20s shoprom and the bootloader is unlocked. I checked. So I will wait for a twrp before I update to 26s. Is the x720 twrp compatible with our phone to flash?
I have not tried it, but according to the comments of this and other forums, with the 20S factory version it is easy to unlock by ADB, and it allows you to install twrp from x720 which by comment works fine.
The problem is that if you upgrade to version 26S, the bootloader can no longer be unlocked and as the recovery is changed to the stock, you can not reinstall Twrp or any other ROM (I suppose you can install another official ROM, but The only one that exists is the 26S, there is not even the 20S with which it comes from the factory)
In short, if you upgrade to version 26S, the bootloader is blocked, and you can not reinstall twrp or anything that is not official, and for the moment there is nothing more.
Greetings.
It's not like there are so many ROMs
The bootloader changes in 26s and it makes device bootloader locked.
I would suggest to stay on 20s until a workaround is available for unlocking bootloader also on 26s.
I guess anyone who already has the 26S version will have to wait. But for the one who has a hard-brick with the blocked bootloader should try to get a copy of bootloader of 20S and with some flash tool try to change it.
Also it could be that with a flash tool install the rom 26S and before restarting change the bootloader by the 20S version. In some terminals, this has worked.
Greetings.
I have a nandroid copy of 20S Shop ROM boot. I made nandroid copies of all major partitions (the same ones that have stock ROM) before installing 26S Stock. I used the TWRP of the X722 version to install the ROM. Everything worked. Then I installed the GApps and gave it some error and rebooted. Now I have the bootloader locked, it does not go into recovery mode and it does not start the system. Totally brick.
And the worst: QFIL does not work here. I have tested on different versions, different computers, different drivers and nothing. He always gives this error:
Code:
15:47:28: ERROR: function: rx_data:247 Error occurred while reading from COM port
15:47:28: ERROR: function: sahara_main:924 Sahara protocol error
15:47:28: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
And Windows emits the disconnected device sound.
Here is a detailed log using the command to send the FireHose through the CMD:
Log.txt
Does anyone have any idea what this error is? And how to solve it?
Hello DK Boneco, I can not tell you how to solve it, but I can give you an idea.
The fault is because the bootloader is locked.
Look for another tool that does not use qfil and that allows you to flash with locked bootloader. Surely there must be some.
And by the way, if you have a copy of the complete 20S version, I would try to flash this one.
Greetings.
DK Boneco said:
I used the TWRP of the X722 version to install the ROM.
Click to expand...
Click to collapse
Can you please post a link
ziaba said:
Can you please post a link
Click to expand...
Click to collapse
Hi, this thread talks about "unlock bootloader with rom 26S" not from twrp.
Anyway there is no twrp for x722 but it works for x720.
Query in twrp threads or create one in section x722 for more information.
Greetings.
F.J.V said:
The fault is because the bootloader is locked.
Click to expand...
Click to collapse
A friend who has the same smartphone with unlocked bootloader did the same process and the exact same error happened.
F.J.V said:
Look for another tool that does not use qfil and that allows you to flash with locked bootloader.
Click to expand...
Click to collapse
Do you know another method? All that I looked for, ending up using the background QFIL to get the job done.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
ziaba said:
Can you please post a link
Click to expand...
Click to collapse
Here's the link: https://twrp.me/devices/leecolepro3.html
DK Boneco said:
A friend who has the same smartphone with unlocked bootloader did the same process and the exact same error happened.
Click to expand...
Click to collapse
The hard brick came from gapps on top of 26s. Never flash Gapps on top of stock ROMs. Never.
The 26s firmware locked bootloader blocking the CRITICAL partition, so you must unlock it first, then unlock the bootloader.
Try this sequence, in fastboot mode:
fastboot devices
fastboot device info
- when in fastboot device info, check CRITICAL partition unlock status. if FALSE, then try
fastboot flashing unlock_critical
fastboot device info
- now CRITICAL partition unlock status should be TRUE, try unlocking
fastboot oem unlock-go
- if you succeded unlocking, check status with
fastboot device info
fastboot reboot or fastboot flash recovery twrp.img
- if you still cannot unlock, you could try flashing a different emmc_appsboot.mbn file. You can extract emmc_appsboot.mbn from x722 20s firmware or from x720 firmware.
In fastboot mode
fastboot flash aboot emmc_appsboot.mbn
- if flashing is successful
fastboot reboot
adb devices
adb reboot bootloader
fastboot oem unlock-go
- if unlock is succesful
fastboot device info
fastboot reboot or fastboot flash recovery twrp.img
Flounderist said:
The hard brick came from gapps on top of 26s. Never flash Gapps on top of stock ROMs. Never.
The 26s firmware locked bootloader blocking the CRITICAL partition, so you must unlock it first, then unlock the bootloader.
Click to expand...
Click to collapse
I tried this and several other ways to try to unlock the bootloader. I could not find a way. It does not allow flash any partition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DK Boneco said:
I tried this and several other ways to try to unlock the bootloader. I could not find a way. It does not allow flash any partition.
Click to expand...
Click to collapse
Would you try
fastboot format userdata
fastboot format data
fastboot reboot bootloader
fastboot device info
Check if (bootloader) is_allow_unlock: changed from 0 to 1. If it is still on 0 try
fastboot erase userdata
fastboot erase data
fastboot reboot bootloader
fastboot device info
If still on 0....try also formatting or erasing cache.
It seems that kernel does not allow any tampering attempt if value is =0, hence critical partitions are locked.
Hello DK Boneco, the error is reading the COM port.
Is the phone charged?
It appears that the phone is disconnected or exits EDL mode.
It may be a driver problem, or some phones exit EDL mode within a few seconds if the flash has not started.
Try not to take more than 4 or 5 seconds from the time the phone enters EDL until the flash starts.
You can also try the flash with MiFlash Xiaomi, say that can flash any modern phone and is quite effective, look for a manual and test.
Greetings.
DK Boneco said:
And Windows emits the disconnected device sound.
Click to expand...
Click to collapse
You may need to install drivers to your pc to recognize your, thats why it emits the disconnected device sound.
Hello DK Boneco, try these steps:
1. Method published with flashone2.0 and zip qfil.
2. When the fault appears, disconnect the USB phone.
3. Reconnect the phone in EDL mode (vol + and vol- and connect to USB)
4. Without losing time, in flashone2.0 press the "Refresh" button, select the COM port, press the "Flash" button and then "NO" (do not unzip it again).
From connecting the phone to USB until you press the "NO" button as fast as possible, without wasting time.
I hope it serves as something, what I see is that the phone goes out of EDL mode and that's why it fails.
Greetings.
To be sure to stay in EDL mode, you can type
fastboot reboot edl or fastboot reboot-edl
Be sure to install Qualcomm driver properly on PC.
Anyway it seems that QFIL is missing for X722 device. I assume that this device lacked a lot of development due to company failure, or it was developed exclusively for CN market (no google play support and locked bootloader from kernel to avoid any hacking activity).
Qfil is a Qualcomm tool for any Qualcomm smartphone, no matter brand or development.
Qfil should work for any phone with chip qualcomm, another thing is that the phone requires some specific configuration, or that the zip that is intended to flash is not correct.
Greetings.

Fastboot can't flash anything after upgrade to B389

Hi~
My phone is huawei honor 7.
Fist, I'm sure I have unlocked my bootloader.
I upgrade to B388 today by fastboot flash cust.img and boot.img and system.img which extract from huawei's official update.app.
Then the phone reboot and I leaved for a while, but when I come back, I found it has replace my twrp by official recovery.
So I just reset my phone and wipe cache. When I reboot to system, I receive an OTA update, and I choose "Download latest full package" then the phone finish update by itself. So my phone now running EMUI 4.0.3 B389.
Finally, I enter fastboot model by "adb reboot bootloader" and try to flash twrp, it tell me:
Code:
PS E:\Root\platform-tools> fastboot flash recovery E:\Root\twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (25890 KB)...
OKAY [ 0.563s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.570s
I try to flash some old version system, but I got same error. But I type " fastboot oem get-bootinfo" It shows that I was unlocked.
So how can I flash twrp again and Root my phone?
--------------------------
By the way, I found I even can not relock my oem by now!
Code:
C:\Users\omicron3069>fastboot oem relock 23**********9971
...
FAILED (remote: stat not match)
finished. total time: 0.000s
C:\Users\omicron3069>fastboot reboot
rebooting...
finished. total time: 0.125s
hmmmm... solve this weird problem by turn on "unknown source " switch in security setting.
I have the same problem. After B396 update I can not load anything in bootloader mode. I also get a "Software Install Failed" error when I try to return to an older version using dload or update.zip.
Edit: My bootloader is unlocked but i can't relock or unlock it again.
How can i solve this problem? Please someone help me!
alperenadalar said:
I have the same problem. After B396 update I can not load anything in bootloader mode. I also get a "Software Install Failed" error when I try to return to an older version using dload or update.zip.
Edit: My bootloader is unlocked but i can't relock or unlock it again.
How can i solve this problem? Please someone help me!
Click to expand...
Click to collapse
1. If you want to downgrade your firmware version, you need flash a downgrade package first by use dload method. Generally, you can find this kind of package in huawei hiclub ROM thread.
This is Chinese hiclub (club.huawei.com/thread-7268260-1-2.html) that contain this kind of package.
2. I solve this problem by open that unknown source switch . If you don't know where it is, just search it in settings.
3. I know a tool named HiSuit, which may can help you to downgrade your system.
4. Also, make sure you have turn off that f**ing "Phone Finder"!! This is just a s**t made by huawei!!
Hope those can help you~
omicron3069 said:
1. If you want to downgrade your firmware version, you need flash a downgrade package first by use dload method. Generally, you can find this kind of package in huawei hiclub ROM thread.
This is Chinese hiclub (club.huawei.com/thread-7268260-1-2.html) that contain this kind of package.
2. I solve this problem by open that unknown source switch . If you don't know where it is, just search it in settings.
3. I know a tool named HiSuit, which may can help you to downgrade your system.
4. Also, make sure you have turn off that f**ing "Phone Finder"!! This is just a s**t made by huawei!!
Hope those can help you~
Click to expand...
Click to collapse
I will try downgrade package. I already turn on unknown sources and disbled phone finder but still i can't flash any firmware nor image via fastboot or recovery.
alperenadalar said:
I will try downgrade package. I already turn on unknown sources and disbled phone finder but still i can't flash any firmware nor image via fastboot or recovery.
Click to expand...
Click to collapse
Have you wiped system? That could be the error that twrp gives.
Edit: Don't forget to make a backup of system and data!
Even if the bootloader screen says that the phone is unlocked, in reality it isn't and that's why you are getting the command not allowed text. Just type fastboot oem unlock and your code to unlock it again. The same problem is present on many Huawei phones like the P8 and P9 Lite I've tested after installing an update.
if you want to emui4.0 to 3.0 it was impossible
HUAWEI big chrysanthemum and foolish engineer doesnt want you to flash emui3.0 But you can use the hisuite to demotion.I hope reply is very useful to you

Categories

Resources