Hi, I flashed the FOTA Kernel with TWRP 2.8.7 onto my phone and inside TWRP I flashed the recovery with the 3.0.2 TWRP image (telling me "Successfully flashed")
But after rebooting I still have TWRP 2.8.7
Using windows command line and "fastboot flash recovery "TWRP.....img" I get this "FAILED" message.
What am I doing wrong?
I even flashed the phone back to stock and then followed these instructions but same result.
Is my phone broken or sth?
Hi H4NNE5, the Xperia M does not have a recovery partition. The TWRP recovery is included in the boot partition when flashing the kernel. Try to upgrade with the TWRP-Manager if your phone is rooted.
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
H4NNE5 said:
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
Click to expand...
Click to collapse
Try this command
fastboot flash boot twrp_name.img
Related
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.
It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help
Hi,
I've just tried and failed to install the "cm-12-20150218-NIGHTLY-nicki" ROM on my phone. Specs are:
Official Android 4.3 Firmware
Model: C1904
Timeline:
Unlocked bootloader according to instructions at http://forum.xda-developers.com/showthread.php?t=2484428
Phone then got stuck in official boot animation (the colourful one)
Didn't bother flashing the "Elixer" kernel as suggested in above thread
Used fastboot to flash the boot.img from the CM zip file
Booted to recovery
Wiped data & cache
Flashed CM & GApps from external SD card
Restarted phone
Phone showed big Android robot animation and then went back to CyanogenMod Recovery
Looking at logs showed "Cannot load volume /misc" error
Found a forum post saying this thread helped with the above error: http://forum.xda-developers.com/xperia-m/development/cwm-twrp-recoveries-cm12-lollipop-t2979752
Tried flashing TWRP recovery (http://forum.xda-developers.com/xpe...very-cwm-twrp-recoveries-custom-roms-t3016507) within CyanogenMod Recovery, but it said the file integrity was bad or something
Used "fastboot flash boot FOTAKernel.img" to flash the above, which worked
Tried to wipe data from within TWRP, but got "failed to mount /data" errors
So the phone is now in a state where:
I can only boot into TWRP
I can't use ADB since the program on the computer won't detect the phone
Fastboot still works
I can't boot into Android
Something seems wrong with "/data"
Any ideas about where to go from here?
I was able to use Flashtool to flash the official firmware back on and boot into it as normal. After doing that and restarting the procedure to install CM12 2015-02-19, this time it installed just fine.
Although I still got errors about "Cannot load volume /misc". Hopefully they don't matter...
Now you have CM12 installed and it is working?
Had the same errors when I tried to flash CM12. Flashing CM11 worked fine but I could not get CM12 to boot...
xa.fr said:
Now you have CM12 installed and it is working?
Had the same errors when I tried to flash CM12. Flashing CM11 worked fine but I could not get CM12 to boot...
Click to expand...
Click to collapse
Yeah; it's installed and working fine. When I flashed the official firmware, (Android 4.3) I told Flashtool to flash everything including the kernel. That seemed to put the phone back into a good state, which allowed me to install CM12.
I'm not sure what caused the problem in my case. Maybe it was unlocking the boot loader.
Can anybody advise me how i can keep my recovery (TRWP), every time i try a new ROM zip it gets wiped and a new type of recovery tool gets installed ie CWM or CM recovery which then makes it impossible to restore a TWRP back up. I then have to set up FlashTool and Fastboot install a .img from a rom with TWRP recovery. Then i can restore. Seems a pain in the but. I have previously rooted other devices ie Kindle Fire hd and never lost or over written recovery sectors when flashing new roms.
[email protected] said:
Can anybody advise me how i can keep my recovery (TRWP), every time i try a new ROM zip it gets wiped and a new type of recovery tool gets installed ie CWM or CM recovery which then makes it impossible to restore a TWRP back up. I then have to set up FlashTool and Fastboot install a .img from a rom with TWRP recovery. Then i can restore. Seems a pain in the but. I have previously rooted other devices ie Kindle Fire hd and never lost or over written recovery sectors when flashing new roms.
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/xpe...-recoveries-custom-roms-t3016507/post58515438
The reason this happen is that Xperia smartphones do not have recovery partition. The recovery is part of the kernel (boot.img), so the kernel comes with a recovery. The link above has a recovery with is flashed onto the FOTA (over-the-air) upgrade partition, which is not used if you have an unlocked bootloader.
Works great
Thanks for that. I had previously tried it but used the latest twrp zip file instead of the 2 in lower box and recovery was totally unstable. However now done FOTA-TWRP.zip and flashed 2 different roms retaining twrp recovery everytime.
Hey guys, I just recently got some parts for my old One X to start playing with it again (bored with ios). I was running an older version of ViperXL and wanted to get lollipop so my goal was to put CM12.0 on my phone. My recovery was twrp but a version that was older so I had to update it. The in app update wasn't working so I updated cwm instead. When I did this I tried to boot to recovery and it would attempt to go to recovery but then boot back to the os.
Then I was trying to flash the recovery using fastboot which resulted in the same problem. Somewhere in there I flash the recovery.img as my boot image (sudo fastboot flash boot recovery.img) This made my phone repeatedly try to boot into recovery. I tried flashing new ViperXL boot.img as well as a couple others but none let me get into my os again. Now it is just a bootloop trying to start my phone up.
When I try flashing a .zip I get the error 'FAILED (remote: not allowed)'. Flashing recovery and boot images work though.
I've tried a lot and done a lot of searching but nothing can get me into recovery or even out of any sort of bootloop.
I'm using Ubuntu and my phone is S-On if that means anything.
Thanks!
Try restoring any backups of old roms from the recovery. Make sure Recovery is written properly in recovery partition. If this works fine , the appropriate boot.img shud be automatically flashed , i guess.
If u dont have a backup , try finding another one x user using a custom recovery, create a backup from his mobile and copy it to ur sd card by mounting it thru recovery and restore it.
If it doesnt work , wipe all the partitions - System , cache, boot and recovery.. then try flashing a Recovery and then a Boot.img and a rom.
I havent faced such a situation. Just my suggestions as no experts have responded.
Cheers if u have already sorted it out !!!
Has anyone noticed the recovery image is no longer a part of the full factory image?
I thought i had a bad/corrupt download at first, but after downloading on my other pc i got the same results, no recovery image.
Its nice that i dont have to boot and flash twrp after a factory flash, but i noticed some other weird things.
first time i flashed the January image after the process was completed it booted straight into twrp, i hit reboot to system, and when it booted all my personal data was still there. it remembered my password, wallpaper, all text and calls were still there, etc. i hadnt removed -w from the script and i couldnt figure out why it was like this.
All of this aside, anyone know why google didnt include the recovery in the latest factory image?
Recovery is included. It's just a part of the boot.img. They share the same partition.
This is also one of the reasons flashing on this device can be a pain in the a**.
If you flash TWRP then fastboot flash the stock boot image, your custom recovery will be replaced by the stock recovery.
Pain-N-Panic said:
Recovery is included. It's just a part of the boot.img. They share the same partition.
This is also one of the reasons flashing on this device can be a pain in the a**.
If you flash TWRP then fastboot flash the stock boot image, your custom recovery will be replaced by the stock recovery.
Click to expand...
Click to collapse
Thats the thing though. twrp was not replaced, and even in the terminal as it was going through the commands stated recovery and sig not found.
oddly enough i tried again late yesterday and everything was normal (fresh download)
noidea24 said:
Thats the thing though. twrp was not replaced, and even in the terminal as it was going through the commands stated recovery and sig not found.
oddly enough i tried again late yesterday and everything was normal (fresh download)
Click to expand...
Click to collapse
Pain-N-Panic is correct, recovery is included in the boot.img and your TWRP installation *should* have been replaced by stock when flashing a full factory build. Every build I've flashed has always said recovery.sig not found. That is normal as far as I'm aware. I've noticed that it all depends on how the flash-all script/an OTA flash handles seeing a TWRP installation. There have been a few circumstances where my TWRP installation stayed in tact as well.