Database Develop

[Q] Flashing recovery problem

Hi all,
I have following problem. I rooted my Xperia T and I also Unlocked my Bootlader. The next step I wanted to flash a recovery to be able flash new ROMs.
In the command prompt I put following:
C:\SDK\platform-tools>adb reboot bootlader
C:\SDK\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' <7650 KB>...
<bootloader> USB download speed was 16118kB/s
OKAY (0,511 s)
writing 'recovery'...
<bootloader> Flash of partition 'recovery' requested
FAILED <remote: Partition not found>
Finished. total time 0,534 s
It means, that it went wrong at the end? How can I solve this? Lets say: how can I flash modified recovery to be able to try new ROM's?
Many thanks for answer.
fipo

Sony phones doesn't have separate recovery partition. Its recovery is incorporated to the boot.img, which contains also the kernel.
Custom kernels normally comes with the recovery. You only need to "fastboot flash boot boot.img"
Tapatalked from my TX

just flash doomkernel using fastboot. (Extract the boot.img from the .zip)
then flash doomkernel again in recovery (The .zip) so you get the wifi modules installed

Thanks a lot for answers ... I am looking for the kernel you mentioned, and I've downloaded this one:
http://d-h.st/b8h
.. I unzipped the file, and nothing like boot.img found ...
What did I download? Will you post a link for me, please?
Thanks a lot ...
fipo

Apologies, it's called kernel.elf
Use fastboot flash boot kennel.elf
Sent from my star trek communicator
Sony Flagship device circa 2145

Rycon33 said:
Sony phones doesn't have separate recovery partition. Its recovery is incorporated to the boot.img, which contains also the kernel.
Custom kernels normally comes with the recovery. You only need to "fastboot flash boot boot.img"
Tapatalked from my TX
Click to expand...
Click to collapse
I love you

i was getting same error then i replaced "recovery" with "boot" so succeed in flashing TWRP.
but after that when i selected reboot into system it again reboot me into twrp. i can't reboot nomally.
Please help!
---------- Post added at 02:05 PM ---------- Previous post was at 02:03 PM ----------
Rycon33 said:
Sony phones doesn't have separate recovery partition. Its recovery is incorporated to the boot.img, which contains also the kernel.
Custom kernels normally comes with the recovery. You only need to "fastboot flash boot boot.img"
Tapatalked from my TX
Click to expand...
Click to collapse
i was getting same error then i replaced "recovery" with "boot" so succeed in flashing TWRP.
but after that when i selected reboot into system it again reboot me into twrp. i can't reboot nomally.
i can still get into fastboot mode.
Please help!

saved my day
This thread saved my day :good:
@gregbradley: you rock !
@fipo: xperia SP does not have recovery partition. After you boot in twrp, you can use 'adb push' to copy the image of your choice (e.g. lineageos) to your device, and use 'install' from the twrp menu.
Hope it helps.

[Q] Help getting HTC One Stock

Hello xda community, I'd like to start with saying all the work done on this forum for open-source, freeware, and general android tweaks is awesome! Thank you.
So awesome in fact that I got a little bit ahead of myself with my new "Sprint HTC One". I followed this guide http://forum.xda-developers.com/showthread.php?t=2244060 to Unlock the bootloader, and root my phone. I then went a step further and wanted to flash a custom Rom. I followed this video, but strayed a little bit (whoops!). I went into twrp recovery, and flashed the "Beanstalk" super custom 4.3 (9/24/2013), along with smw6180_superwipe, and 4.3 gapps.
This actually was working for about 4 days, but now it won't connect to the mobile network even when toggling on and off airplane mode (A temp fix for the ROM). I went ahead and looked for solutions, namely to just get back to stock to see if the problem is bigger than just custom ROM. I relocked my bootloader, following http://www.youtube.com/watch?v=0WWNZpaQBh8&list=PLE395F615E026133D&index=11 Thus running into my current issue of Error 140 when trying to flash the RUU.
I'm asking anyone that could help, to offer suggestions on getting my phone back to stock. I would also like a couple suggestions for more stable ROM's (again, i knew what i getting into; ie disclaimers) that offer cool customization!

did you put the stock recovery back on before you locked the bootloader? Also are you super cid?

olorolo said:
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
Click to expand...
Click to collapse
No i don't believe so, Well now its not even going into twrp recovery. It displays tampered relocked security warning, s-on, hboot 1.44.0000 and This is the only screen i have for fastboot and the bootloader

I've seen this issue before let me take a quick look I think your ok
Sent from my HTCONE using Tapatalk 4
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
You caught me in the middle of flashing the s-off firmware myself
Sent from my HTCONE using Tapatalk 4

Good to hear! Thank you for your time sir

get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
---------- Post added at 07:28 PM ---------- Previous post was at 07:18 PM ----------
once you have twrp back flash the s-off firmware http://forum.xda-developers.com/showthread.php?t=2467607 then the 4.3 rom of your choice

olorolo said:
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
Click to expand...
Click to collapse
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.

Pug4567 said:
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Click to expand...
Click to collapse
twrp has to be renamed to recovery.zip try fastboot flash then type flash recovery then the name of the zip which is recovery.zip then fastboot reboot

I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582

Pug4567 said:
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
try hassoons all in one toolbox

I got twrp back by unlocking my phone again. Should i proceed with the 3.04.651.2 firmwre? beanstalk is now hanging on splash screen.

The phone isn't being recognized on my computer it seems, it shows as m7wls under device manager, when in twrp 2.6.3. When in bootloader it shows as One device, but neither is accessible.

Also tried flashing the s-off firmware, but got 'error cannot load firmware.zip'
Any more help would be appreciated, almost thinking of taking it back to sprint, i have a protection plan. But i would like to avoid that, im currently going to buy an otg-usb cable as well.

Cant install recovery / can't unlock [Xperia Z]

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.

I'm new, I dont know how to unlock bootloader on Emui 3.1, android 5.1.1

Hello everyone, I'm new in the Android world.
I have been trying to unlock my bootloader with the sticky guide, but it doesnt work for some reason.
In the cmd (after i got into the "Device locked" screen) it gives me an error and i dont know how to fix it.
I would like to see a full working 2k17 guide for how to unlock bootloader for a Huawei P7 running android 5.1.1 with Emui 3.1
Hope someone can help me.

What error do you get?
Does it appear right after entering fastboot mode?

RangerP7 said:
What error do you get?
Does it appear right after entering fastboot mode?
Click to expand...
Click to collapse
Im getting into fastboot without problem, but when i try to unlock it gives me the (Failed to write) error? Maybe its the guide that doesnt work

What guide do you use?
Did you install your driver (HiSuite)
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
Before you are flashing try the command "fastboot devices". Is your devices listed?

RangerP7 said:
What guide do you use?
Did you install your driver (HiSuite)
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
Before you are flashing try the command "fastboot devices". Is your devices listed?
Click to expand...
Click to collapse
I used this guide: https://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
I got HiSuite installed and updated.
It is listed as "0123456789ABCDEF fastboot" ?
F:\Overførsler\ADB Flash Tools>fastboot flash boot BOOT_EMUI3.0_619_UNLOCKED.img
target reported max download size of 536870912 bytes
sending 'boot' (8038 KB)...
OKAY [ 0.309s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.309s

So you are trying to flash a KitKat boot image on a lollipop device?
But the guid works, I rooted my device the same way

CalloDK said:
I used this guide: https://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
I got HiSuite installed and updated.
It is listed as "0123456789ABCDEF fastboot" ?
F:\Overførsler\ADB Flash Tools>fastboot flash boot BOOT_EMUI3.0_619_UNLOCKED.img
target reported max download size of 536870912 bytes
sending 'boot' (8038 KB)...
OKAY [ 0.309s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.309s
Click to expand...
Click to collapse
if you have emui 3.1 you can't flash a kernel for emui 3.0
a question: is your bootloader unlocked? (in fastmode under the green robot there is written in red letters phone unlocked)
EDIT: in your first post you write that the phone is locked...so you need an unlock code from huawei site in order to unlock bootloader, otherwise you will never be able to flash kernel or recovery
use this guide https://forum.xda-developers.com/ascend-p7/general/guide-root-huawei-p7-t3311424
and at point 8-9-10 use this https://forum.xda-developers.com/ascend-p7/orig-development/recovery-t3314665

usb2 said:
if you have emui 3.1 you can't flash a kernel for emui 3.0
a question: is your bootloader unlocked? (in fastmode under the green robot there is written in red letters phone unlocked)
EDIT: in your first post you write that the phone is locked...so you need an unlock code from huawei site in order to unlock bootloader, otherwise you will never be able to flash kernel or recovery
use this guide https://forum.xda-developers.com/ascend-p7/general/guide-root-huawei-p7-t3311424
and at point 8-9-10 use this https://forum.xda-developers.com/ascend-p7/orig-development/recovery-t3314665
Click to expand...
Click to collapse
I tried to install it on 2 computers, but i dont get any desktop shortcut?

What shortcut do you mean adb/fastboot?

RangerP7 said:
What shortcut do you mean adb/fastboot?
Click to expand...
Click to collapse
It says in the guide that it will create a shortcut on the desktop, otherwise i dont know how to continue

You don't need any shortcut
Just go to the path, you installed it via cmd
How did you get it work in your first post?

RangerP7 said:
You don't need any shortcut
Just go to the path, you installed it via cmd
How did you get it work in your first post?
Click to expand...
Click to collapse
I didnt set a path, it just got installed.
I used another cmd, where i was just going to open it and run it

CalloDK said:
I didnt set a path, it just got installed.
I used another cmd, where i was just going to open it and run it
Click to expand...
Click to collapse
There schoulkd be a folder calld "adb" at C:
So open cmd "cd C:/adb"

RangerP7 said:
There schoulkd be a folder calld "adb" at C:
So open cmd "cd C:/adb"
Click to expand...
Click to collapse
I got a folder called ADB Flash Tool? Can i use that?

Yes of course

RangerP7 said:
Yes of course
Click to expand...
Click to collapse
It worked and now im rooted, thanks. But I cant find the cyanogenmod which works with P7

Because there is no one for Android L.
Or look at the developer channel, there you will find another custom roms

I cant flash the recovery in my honor 4x

hello to all, accidentally delete the recovery of my smartphone and I have not been able to flash it using adb commands in Windows 10 therefore I can not restore the smartphone to the factory mode. please help

What error it gives when you type command 'fastboot flash recovery <recovery_file>'?
How did you deleted the recovery?
Also the end ("I can not restore the computer from the factory") doesn't make any sense.

keikari said:
What error it gives when you type command 'fastboot flash recovery <recovery_file>'?
How did you deleted the recovery?
Also the end ("I can not restore the computer from the factory") doesn't make any sense.
Click to expand...
Click to collapse
1. I think I deleted the recovery when I rooted the smartphone with kingroot.
2. the error that gives me is the following:
" S C:\adb> fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (9304 KB)...
OKAY [ 0.222s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.234s ".

crhistiandavidbonilla47 said:
1. I think I deleted the recovery when I rooted the smartphone with kingroot.
2. the error that gives me is the following:
" S C:\adb> fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (9304 KB)...
OKAY [ 0.222s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.234s ".
Click to expand...
Click to collapse
Can you still boot normally and do you have root access?
---------- Post added at 08:33 PM ---------- Previous post was at 08:29 PM ----------
Also try to re-unlock bootloader and if it doesn't work, re-lock and then unlock again. So we can be sure you don't have problems with that, because possible fix would otherwise make your phone worse.

keikari said:
Can you still boot normally and do you have root access?
---------- Post added at 08:33 PM ---------- Previous post was at 08:29 PM ----------
Also try to re-unlock bootloader and if it doesn't work, re-lock and then unlock again. So we can be sure you don't have problems with that, because possible fix would otherwise make your phone worse.
Click to expand...
Click to collapse
yes i can still boot normally, i erase kingroot so i think that i dont have root access

crhistiandavidbonilla47 said:
yes i can still boot normally, i erase kingroot so i think that i dont have root access
Click to expand...
Click to collapse
Well then your best choice is probably to try to re-install firmware and hope this does something. Do it with dload and force update method, because it doesn't use default recovery.
Or if you happen to have root access you can try this https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en or similiar app to flash recovery while device running. (Or 'dd' command)

keikari said:
Well then your best choice is probably to try to re-install firmware and hope this does something. Do it with dload and force update method, because it doesn't use default recovery.
Or if you happen to have root access you can try this https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en or similiar app to flash recovery while device running. (Or 'dd' command)
Click to expand...
Click to collapse
Nothing works

I had a similar problem: in fastboot I can install twrp successfully, but when I reboot, boot always to the stock emui recovery...
I don't know why.
I thought it was already installed twrp, I don't know why now boots to the stock one...
Does anyone can help me? Thanks.