I Unlocked someones Xperia Z and installed Cyanogenmod and TWRP on it some time ago. It was too unstable for their liking so they reset it to its stock settings using Sony Emma (or whatever its called).
Well now that they've got a nexus 6P, they've given the Xperia Z to me, so i tried to install TWRP and i get errors trying to overwrite the recovery.
Upon inspection of the bootloader lock settings i found it to say "bootloader unlockable: Yes", which indicates it is unlockable but not yet unlocked, and it continues to say this no matter how many times i attempt to unlock it.
Below is a demonstration attempt to unlock the phone and install TWRP:
Code:
[email protected] ~/Desktop $ sudo fastboot oem unlock 0xC431F679A4E1ECEB
...
OKAY [ 0.408s]
finished. total time: 0.408s
[email protected] ~/Desktop $ sudo fastboot erase recovery
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
[email protected] ~/Desktop $ sudo fastboot flash recovery twrp.img
sending 'recovery' (10656 KB)...
OKAY [ 0.337s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.339s
[email protected] ~/Desktop $ sudo fastboot flash boot twrp.img
sending 'boot' (10656 KB)...
OKAY [ 0.337s]
writing 'boot'...
OKAY [ 0.563s]
finished. total time: 0.900s
I've also tried it using flashtool on Windows and similarly it doesn't work.
I can't understand why it would work the first time, but now that its been factory reset the unlock doesn't work.
Have you tried with Xperia z dual recovery? (XZ dual-recovery) . It's very simple to install, for more info please refer to the official thread.
aaronkatrini said:
Have you tried with Xperia z dual recovery? (XZ dual-recovery) . It's very simple to install, for more info please refer to the official thread.
Click to expand...
Click to collapse
To do that i'd need a custom recovery, and i can't install one because the bootloader is locked and there is no recovery present on the device.
EDIT: ah i just saw the install exploit for unrooted devices. I'll give it a shot.
Didn't work unfortunately :/
I wasn't able to to use dual recovery to unlock the phone.
I downloaded and then installed a 10.3.x.x version of a stock xperia Z rom using flashtool, then i ran the dual recovery setup. EVERY operation reported that the file or folder didn't exist,and that the install had failed.
I was able to root the phone using Root Genius. I then installed TWRP manager and tried to install TWRP from there (this worked on that phone before), but it corrupted the rom so now it just freezes and restarts on the boot animation.
Recovering with Emma does not relock the bootloader. So bootloader should still be unlocked. Recovering with Emma also removes root so you need to root your device before you can install a custom recovery.
Sent from my E6653 using XDA-Developers mobile app
You are indeed right! although the problem appeared to be a locked bootloader at first, it now appears it was a corrupted recovery partition.
I, again, set the phone to a stock 10.1.x.x ROM (it was still corrupted from last time so i had to reset it again using Sony Emma) using flashtool and rooted using Root Genius. I then tried to use flashify to install XZ-dual-recovery but it told me the recovery partition was missing.... so i searched around and found the cure to my woes may be DooMKernel, so i set it up, and everything fell into place from there! below is how i believe it worked:
1. Used fastboot on my PC to install DooMKernel v22 as per the official page instructions
2. successfully booted into TWRP
3. used TWRP to install XZ-dual-recovery
4. successfully booted into CWM recovery
5. used CWM recovery to format all internal paritions
6. used CWM to install ROM and root
Thank you everyone for your help!
My xperia z has the 5.1.1 rom and is rooted.
The boot loader is locked and I couldn´t unlock it.
I cannot get into recovery with PC, neither with the buttons.
I like to install a custom 6.0 rom.
any suggestion?
thxs in advance for your support.
Related
HELP ME! I cannot get this recovery image to flash for the life of me. here's the story. I have what was a ere27 build N1. 2 weeks ago I did the manual update to Google's prerelease of Froyo. Now my phone is a FRF50 build. As everyone else found out it's buggy as hell and GPS does not work. I searched for weeks to try and find a fix and I couldn't find anything other than to unlock the bootloader root the device and flash a different rom onto the phone. So I unlocked the BL from instructions here. Then in downloaded Pauls 1.0 FRF50 superboot. I tested the root with torch and it works, so the unlock and root must have worked. This is the first time I have ever used the cmd window and I have tried everything under the sun to get this thing to work so I can flash Pauls froyo and have working GPS again.
I followed the instructions found here, but I keep getting this error.
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
cd C:\fastboot
C:\fastboot>fastboot-windows devices
HT9C*******8 fastboot
C:\fastboot>fastboot-windows flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... FAILED (remote: not allowed)
have you done 'fastboot-windows oem unlock' ?
Yessir. Unlocked padlock on startup.
Try this:
fastboot devices
fastboot flash recovery recovery.img
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Hyper4mance2k said:
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Click to expand...
Click to collapse
I'm having the EXACT same problem.
Did you apply root before flashing recovery? Flash Paul's superboot, then install AmonRA recovery.
ATnTdude said:
Did you apply root before flashing recovery? Flash Paul's superboot, then install AmonRA recovery.
Click to expand...
Click to collapse
The OP says he is rooted. I am rooted as well. We both have had success in fastboot, but our recovery is defaulting to the standard android one, and not the custom one that we flash.
Hyper4mance2k said:
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Click to expand...
Click to collapse
All you need to do is
Fastboot flash recovery recovery-ra.img
Or whatever the image name needs to be.
I think I figured out the problem. I was running a rooted version of FRF72, and for whatever reason, no matter how I tried to flash the recovery, it would not stick. I could use clockwork's app to flash and reboot into the custom recovery, but if I rebooted again, it would always default to the stock android recovery.
I now have the custom recovery working for me at all times. Here is what I did (Keep in mind, I take no responsibility if you brick your phone into oblivion...):
First: Make sure that you have an unlocked bootloader, and are rooted. I used Paul's Superboot for the FRF50 build on my FRF72 build, and it worked flawlessly.
1. Find a custom ROM such as the MoDaCo MCR18 or 19 build if you want something close to the OTA builds.. or whichever one you'd like to flash. Make sure it is not a stock/rooted OTA build! I personally used Paul's MCR18 build over at MoDaCo.
2. Download it, and then rename the rom to update.zip and transfer to your SD card's main directory
3. Download the clockwork ROM Manager app from the android Market and run it.
4. Flash ClockworkMod Recovery from the app
5. Use the feature in the app to "Reboot into Recovery"
6. You should now be in the ClockworkMod recovery
7. Do a nandroid backup!! (that may reboot your phone normally.. if so, repeat steps 4 & 5 to reboot back into custom recovery)
8. If your rom requires you to wipe prior to install, then wipe cache partition from the main menu, and then go to advanced and wipe Dalvik cache prior to the next step. I did not have to wipe, so if this rebots your phone normally, repeat steps 4 &5 to get back into custom recovery.
9. Select the option to "apply sdcard:update.zip"
It will then flash the custom ROM onto your Nexus One
10. Once your phone has been rebooted, download the ClockworkMod Rom Manager from the market again (if it is not already on your phone), and re-flash the custom recovery. It should now always boot into the custom recovery.
Hope that helps!!
I was trying to unlock and root my Vivid and seem to be stuck in a bootloop.
I used the All in one kit v 1.2 (Thanks Hansoon) unlocked my bootloader, and installed CWM.
The problem occurred when I tried to install the HoliCake kernel, after that step I couldn't boot into the base OS.
At the moment I can access hboot, fastboot and CWM.
When I try to boot, all that happens is the HTC logo is visible indefinitely.
Trying to install the stack kernel gives me the following output, and i'm not really sure where to go from here.
Code:
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>adb push Kernels/Module
sStock/system /system
error: device not found
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>adb reboot bootloader
error: device not found
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>fastboot flash boot Ker
nels/Kernel-HereStock/boot.img
sending 'boot' (2838 KB)... OKAY [ 0.658s]
writing 'boot'... OKAY [ 1.578s]
finished. total time: 2.236s
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>fastboot reboot
rebooting...
finished. total time: 1.879s
Thank you all, since this device is also my main phone, it would be appreciated if I could get it working again before the day is out, but even if that's not possible i'm gratefull for all your help.
I use the same tool. It is amazing.
Were I you, I'd download the stock ROM from the "Revert your phone to stock from ICS" thread in the dev section and start over just to be on the safe side.
Sent from my HTC PH39100 using xda premium
Okay, i'm back to stock, now to figure out how to actually mod this thing when adb doesn't seem to want to connect.
Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!
calbertuk said:
Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!
Click to expand...
Click to collapse
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.
majmoz said:
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.
Click to expand...
Click to collapse
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP
calbertuk said:
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP
Click to expand...
Click to collapse
I don't know what you are trying to accomplish but here is a possibility: How to : Flash HTC One Mini with out S-OFF and no need RUU Stock ROM and [ROM][M4 - 4.09.401.3] Official Stock Sense 6 Rom v2 & Firmware
Hi guys I have a problem now when trying to flash custom recovery using adb fastboot this log always appear:
fastboot flash recovery recovery.img
sending 'recovery' (10704 KB)...
OKAY [ 0.341s]
writing 'recovery'...
#FAILED (remote: Command not allowed)
finished. total time: 0.345s
SO,I dialed *#*#7378423#*#* and I found that my bootloader is unlocked
then I USED sony flash tool and flashed official 4.4.2 then tried and nothing
WIPED EVERY THING then flashed official 5.1.1 and tried to flash recovery and nothing happened
so I ROOTED 5.1.1 by KINGOROOT and dowloaded flashify then when tried to flash recovery.img it gives me message (recovery partition not found) and so are the boot (boot partition not found)
what can I do help please !
No one can fix my problem?!!
I just did it .....same problem like you. I rename the recovery img to boot.img then flash it to boot.img . Then it boot up twrp.
tllim73 said:
I just did it .....same problem like you. I rename the recovery img to boot.img then flash it to boot.img . Then it boot up twrp.
Click to expand...
Click to collapse
But thus I will flash boot not recovery, I know it will work because I did that but the orginal problem isn't solved
Hi all,
I'm trying to understand what did I do wrong.
I bought my device with an unlocked bootloader miui V8 (global rom).
I tried to flash TWRP recovey and MIUI PRO rom. I follow the steps that are mentioned here
and got soft brick - the device got stuck on the mi logo (with the unlock sign), even when I wait in patience the device just turned off.
- At the beginning I flashed the TWRP recovery by xuefer, boot into it and flashed the dm-verity disabler (as mentioned in the guide) and got error 1.
I reboot the device and it didn't boot.
- I boot to the recovery again and wipe the data - didn't boot.
Boot to recovery again and wipe to factory
-I flashed the MIUI PRO rom and the device still didn't boot.
I tired to flash the TWRP recovery by iscle - now the dm-verity disabler succeed but the device still didn't boot.
made the wiping steps as above again - and the device still got stuck at the mi logo.
At any step I manged to boot into the TWRP recovery and fastboot mode.
My lest option was to go back to the global stock rom using MiFlash
Now I'm on Global MIUI 9 with locked bootloadr
What did I do wrong?
I want to unlock the bootloader and to get back my control on my device.
Please advice
Thanks
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Thank you all for your answers!
Thank you all for your answers!
ekin_strops said:
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
Click to expand...
Click to collapse
This is exectly what I've done. and I't didn't worked.
Can you please point me to exact TWRP that you meant?
What about the dm-verity disabler ? it isn't necessary?
ondoy1943 said:
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Click to expand...
Click to collapse
I've checked the bootloader status in the Dev menu and with fastboot (fastboot oem device-info).
In addtion to all I had the open padlock sign when the turned on the device.
lightman33 said:
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Click to expand...
Click to collapse
I had the open padlock sign.
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
I want to know the mistake I've done - so I don't fail with it again after I'll get the approval to open my bootloader.
Thanks
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
lightman33 said:
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
Click to expand...
Click to collapse
I'm sorry if you miss understood me, but I meant to the mistake I've made with the TWERP and rom flashing.
I can't figured out what I've did wrong.
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
lightman33 said:
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
Click to expand...
Click to collapse
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
I took the TWRP from this forum, this is my md5 if you want to check yours :
f52ff052971b67df097d4cfa8a2ec162 twrp-3.2.0-0-oxygen.img
And this is my howto :
$ sudo fastboot flash recovery twrp-3.2.0-0-oxygen.img
target reported max download size of 536870912 bytes
sending 'recovery' (16196 KB)...
OKAY [ 0.504s]
writing 'recovery'...
OKAY [ 0.095s]
finished. total time: 0.600s
$ sudo fastboot boot twrp-3.2.0-0-oxygen.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
OKAY [ 0.576s]
finished. total time: 1.063s
For the ROM, I took file here : http://bigota.d.miui.com/7.12.8/oxy....8_20171208.0000.00_7.1_global_93a8045184.tgz
Filename : oxygen_global_images_7.12.8_20171208.0000.00_7.1_global_93a8045184
From forum : http://en.miui.com/thread-1273027-1-1.html
and the command to flash was (after unzip the file) :
$ sudo ./flash_all_except_storage.sh
Beginning of the log :
product: oxygen
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
erasing 'sec'...
OKAY [ 0.021s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.040s]
writing 'crclist'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.040s]
writing 'sparsecrclist'...
Hope it will help you...
ymca said:
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
Click to expand...
Click to collapse
Hi! As others have already told you,
What I would do is to completely format the phone with Mi Flash (download the latest global stable fastboot version from http://en.miui.com/a-234.html), then flash it to the phone using the Flash All option, then flash my recovery or the one from xuefer (the one you prefer, both work), if you are flashing miui pro I think there is no need to flash the dm-verity file, so just wipe system + data + cache and flash miuipro.zip
Thank you all for your replais !
I will try and update right after I'll get the bootloader unlock approval.
Meanwhile you all have a great day !