Hello,
on my X Compact I can just boot directly into TWRP using fastboot. I like this method because I doesn't do any permanent changes on the phone. However, it does not work on the Z5. The phone just freezes when I try to boot directly into TWRP (I tested 3.0.2 and 3.1).
If I flash TWRP on the recovery partition, can I expect it to work? What do I do if it doesn't work?
Am I still able to flash FTF files with Sony's flash mode after installing TWRP? How to get into the flash mode?
Best,
ypnos
Related
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
also it says invalid "boot image header!" in red letters
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
P.Kosunen said:
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
Click to expand...
Click to collapse
Alright thankyou!
I got everything to work again but I still can't flash roms. They just bootloop :S
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
You do know flashing stock again removes root, so it has to be rerooted again ?
aradalien said:
You do know flashing stock again removes root, so it has to be rerooted again ?
Click to expand...
Click to collapse
Yes I am very aware and followed through with root with that outcome.
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
Click to expand...
Click to collapse
CWM doesn't work it. It boots up (Im used cyanogenmod) the cyanogenmod boot animation but just stays there.
P.Kosunen said:
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Click to expand...
Click to collapse
I've flashed twrp too and came out with the same outcome.
stuck in fastboot
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
Exactly i am also facing same problem....
mobile unable to instal firmware...
still i am searching for solution ...
guys plz help me
I thought I am the only one with this problem..After mailing the phone to SC and got it back after 2 months, the phone still looks the same, just like they did nothing to fix it.
I bought this phone so I can get access to a lot of different roms... I'm trying to install twrp as my recovery or cmw but when I flash it after unlocking the boot loader with cmw it doesn't stay installed and revert back to the original request and the twrp I get an error message in twrp about original recovery and then the phone goes into a boot loop. It has the latest OS version running with April Security fixes... please help
Flash twrp as it is a more versatile and widely supported recovery.
Flash twrp in fastboot mode. After flashing, use the power and volume buttons to boot directly to twrp, do not reboot the phone until after you have entered recovery.
audit13 said:
Flash twrp as it is a more versatile and widely supported recovery.
Flash twrp in fastboot mode. After flashing, use the power and volume buttons to boot directly to twrp, do not reboot the phone until after you have entered recovery.
Click to expand...
Click to collapse
did exactly what you said and im getting thr error / system to prevent the stock rom from replacing twrp...
whats happening
I recommend flashing the latest stock rom to make sure the phone boots properly.Then, I would flash twrp again.
audit13 said:
I recommend flashing the latest stock rom to make sure the phone boots properly.Then, I would flash twrp again.
Click to expand...
Click to collapse
Did that and flashed twrp and I'm still getting the error...
I unlocked boot loader
Flashed twrp
With USB still plugged in I selected recovery from the fastboot menu...
Boots to recovery and still get that error message
Am I doing something wrong
You're flashing 2.8.7 for the hammerhead?
audit13 said:
You're flashing 2.8.7 for the hammerhead?
Click to expand...
Click to collapse
No I'm flashing the latest 3.0.2 version is that the problem?
I would try 2.8.7
Hi there, a friend of mine soft-bricked her oppo F1 plus (x9009). Now it's stuck at recovery mode. I tried to flash the latest stock firmware (X9009EX_11_OTA_022_all_201609101758) but the phone does not seem to boot into system. So the questions are: how do I un-brick the phone (or simply bypass recovery mode and boot into system)? Could (or should) I try flashing custom recovery (TWRP for example) using ColorOS recovery?
Actually all I need to do is recover the data stored in internal storage of the phone. I came up with two ideas:
1. Flash stock firmware WITHOUT wiping data & cache. This option does not seem to work since the phone is still stuck at recovery mode.
2. I'll flash TWRP since I could access internal storage from TWRP. I'm a bit worried about this resort since if anything goes wrong, the phone will be hard-bricked since booting into fastboot mode to flash zip appears to be impossible as Oppo locks bootloader
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
qqzzxxcc said:
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
Click to expand...
Click to collapse
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Kungfu73 said:
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Click to expand...
Click to collapse
Thanks, that helped me so much!
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
qqzzxxcc said:
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
Click to expand...
Click to collapse
Glad that it worked for you and you finally could get latest one!
I forgot to mention that in first method, after installing LP ROM, install recovery installer app and flash TWRP v2.8.7.2 and use that to install latest one !!! and LoL very long way
I just wanted to say that it is possible!
Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!
fibonazi said:
Recently I decided to try flashing a custom rom onto my old phone, a Gionee F103 Pro. Since it is quite obscure it isn't officially supported by twrp, but I managed to find an unofficial build. I unlocked the bootloader and flashed twrp using fastboot, and according to the console it was successful. When I booted my phone twrp began to load, but then there were multiple 'unable to mount' and 'failed to mount' errors and it rebooted. This has been repeating for almost an hour now. It's unresponsive to any button presses, and it won't show up on the device manager either. The only way I've got it to stop was by removing the battery. I've tried fastboot mode, recovery mode and regular boot but they all end up the same. I'd be grateful if anyone could could help me fix this.
Thanks!
Click to expand...
Click to collapse
Can you flash a copy of stock recovery.img via fastboot?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Can you flash a copy of stock recovery.img via fastboot?
Click to expand...
Click to collapse
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.
fibonazi said:
I tried to boot my phone into fastboot but it goes straight to twrp instead. My PC doesn't seem to detect it either.
Click to expand...
Click to collapse
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If there is a LineageOS ROM or some other custom ROM available for your device, try flashing a ROM.
If that doesn't work...
Flash a copy of stock recovery.img via TWRP. TWRP has the ability to flash .img files.
Or, if you can find a copy of your stock recovery that has been converted into a TWRP flashable .zip, you can flash that .zip via TWRP then reboot the device into recovery mode to see if it boots stock recovery.
If you can't get that to work, TWRP has a terminal emulator built in, you can try flashing stock recovery.img using dd commands in the TWRP terminal. You'll have to research your devices partition structure to get the correct dd command to make sure that the recovery gets flashed to the correct partition.
I'm only saying to do all of this because it seems that screwing with the recovery partition caused the issue, maybe, restoring/repairing the recovery partition might fix the issue.
If not, you'll have to find a fix that involves flashing your stock firmware or stock system.img.
Click to expand...
Click to collapse
Actually, the problem I'm having is that twrp runs into an error and shuts down before I can do anything on it. It is stuck in an endless boot loop and is unresponsive to any button or screen presses. I have a lineage os rom, but I don't have any way to flash it right now. Is there any way to make it responsive again? Or any way to connect it to a pc?