Hello,
I'm trying to do Flash TWRP Recovery, this is the error message i'm getting:
==========================================================
C:\adb>fastboot flash recovery twrp-3.2.3-0-pollux_windy.img
sending 'recovery' (11774 KB)...
OKAY [ 0.374s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.376s
==========================================================
Info:
Sony Xperia Z tablet (SGP311)
Android Ver. 5.1.1
Build 10.7.A.0.228
Bootloader is unlocked
Device is not rooted.
Is there a tutorial to make this work?
mcwheelz said:
Is there a tutorial to make this work?
Click to expand...
Click to collapse
There is no recovery partition on this device.
Look here.
Cannot boot into TWRP Recovery
Thanks for your reply. it worked!:victory:
I did the follwing steps:
- Root my SGP311 sony tablet (WiFi)
- backup the TA
- unlock bootloader
- install twrp version (twrp-3.3.0-0-pollux_windy.img)
- backup the current rom
- after installing the rom, ( lineage-15.1-20190429-nightly-pollux_windy-signed.zip) i cannot boot into twrp anymore to install the GAPPS
at startup i repeatedly press vol -/+ to access twrp recovery, but the recovery screen of lineageOS appears
I'm able to startup into LineageOS
Do you know a way to access TWRP recovery?
(i tried everyway, with vol up + power and vol down + power)
I hope you can help me! it's very frustrating
Rootk1t said:
There is no recovery partition on this device.
Look here.
Click to expand...
Click to collapse
mcwheelz said:
Do you know a way to access TWRP recovery?
(i tried everyway, with vol up + power and vol down + power)
I hope you can help me! it's very frustrating
Click to expand...
Click to collapse
If you installed TWRP to boot partition, no surprise it was overwritten after you flashed lineage-15-1....zip.
If you need TWRP to stay permanently, you need to flash it to FOTA partition, or use kernel from unofficial 15.1 thread with built-in TWRP.
Related
I'm going to upgrade it to MR, but i can't have it root after try whole the night, i tried
AndroPlusKernel v4 and v10 but none of them did the work, what i'm following is successfully verified by a few people, can some help on this?
I'm a HK version with '28.0.A.8.260' firmware.
Here is my command output.
#[email protected]:/ $ su
/system/bin/sh: su: not found
#[email protected]:/ $ reboot bootloader
#fastboot devices
CB5A26CPBC fastboot
#fastboot oem unlock **************
...
FAILED (remote: Device is already rooted)
finished. total time: 0.008s
# fastboot flash boot boot.img
sending 'boot' (40420 KB)...
OKAY [ 0.996s]
writing 'boot'...
OKAY [ 0.330s]
finished. total time: 1.325s
#fastboot reboot
rebooting...
finished. total time: 0.060s
#adb shell
[email protected]:/ $ su
/system/bin/sh: su: not found
DId you also flash the TWRP recovery from AndroPlus? Also, from there you need to flash the SuperSU 2.46 .zip file.
jelbo said:
DId you also flash the TWRP recovery from AndroPlus? Also, from there you need to flash the SuperSU 2.46 .zip file.
Click to expand...
Click to collapse
Thanks a lot for your help.
No, the link what i'm following tells it's enough by just unlock and flash the boot.img.
I tried flashing TWRP, but i can never boot into recovery mode both by hold the 'Volume -' and 'Power' button or by executing 'adb reboot recovery', the display never light up and will go to normal boot after a while, looks like the flash don't make sense, is it possibly caused by the firmware version? i'm at 28.0.A.8.260.
# fastboot flash recovery ../TWRP-2.8.7.0_adb_shell_only.img
sending 'recovery' (11653 KB)...
OKAY [ 0.315s]
writing 'recovery'...
OKAY [ 0.123s]
finished. total time: 0.438s
# fastboot reboot
rebooting...
finished. total time: 0.052s
[[email protected] Root-img-v10]# adb reboot recovery
get the latest recovery from Androplus' website - the shell only thing was a first attempt
as jelbo writes you need to flash SuperSU
adb reboot recovery is OK if volume up does not work on device normal boot
Wei Xu said:
Thanks a lot for your help.
No, the link what i'm following tells it's enough by just unlock and flash the boot.img.
I tried flashing TWRP, but i can never boot into recovery mode both by hold the 'Volume -' and 'Power' button or by executing 'adb reboot recovery', the display never light up and will go to normal boot after a while, looks like the flash don't make sense, is it possibly caused by the firmware version? i'm at 28.0.A.8.260.
# fastboot flash recovery ../TWRP-2.8.7.0_adb_shell_only.img psending 'recovery' (11653 KB)...
OKAY [ 0.315s]
writing 'recovery'...
OKAY [ 0.123s]
finished. total time: 0.438s
# fastboot reboot
rebooting...
finished. total time: 0.052s
[[email protected] Root-img-v10]# adb reboot recovery
Click to expand...
Click to collapse
Hi,
Don't use the recovery TWRP-2.8.7.0_adb_shell_only.img but use the twrp 2.8.7.0(not)fixed.img. Shut down the tablet
Press and old down the power button when the light become yellow press volume down button the led become orange released the power button and volume down button. The twrp screen must be appear
killdozer56 said:
Hi,
Don't use the recovery TWRP-2.8.7.0_adb_shell_only.img but use the twrp 2.8.7.0(not)fixed.img. Shut down the tablet
Press and old down the power button when the light become yellow press volume down button the led become orange released the power button and volume down button. The twrp screen must be appear
Click to expand...
Click to collapse
Great, this is caused by the recovery.img version, i tried 2 other img in official link, both of them failed,
'(not)fixed' works well.
when i used TWRP to install the MR ROM, it refused to continue with 'could not find 'META-INF/com/google/android/update-binary' like error.
so i unzip the ROM and booted to recovery mode to make a manual flash, but it hangs up for 15 minutes and stills don't finish, is this abnormal? should i wait for it to complete? does it will crash the system if i terminate it forcely?
I had brush CM 12 on an OnePlus One before, looks it's very fast and often finished within 10 mins, what's the matter?
# fastboot flash system system.img
sending 'system' (859570 KB)...
Wei Xu said:
when i used TWRP to install the MR ROM, it refused to continue with 'could not find 'META-INF/com/google/android/update-binary' like error.
so i unzip the ROM and booted to recovery mode to make a manual flash, but it hangs up for 15 minutes and stills don't finish, is this abnormal? should i wait for it to complete? does it will crash the system if i terminate it forcely?
Click to expand...
Click to collapse
What is this MR ROM you speak of? There is no such thing as MR ROM for the Z4 Tablet. Afaik we only have AOSP 5.02, 5.1.1, 6.0 and the latest stock 5.0.2 ROM. Flashing anything else would likely end up in it hanging, like you experience.
With the current state of ROMs, I advice to just flash the official stock ROM, benefit from it's stability and full copmpatibility, SuperSU it, try Xposed (v79, sdk21, arm64) and freeze/uninstall system bloatware with an app like Titanium Backup.
jelbo said:
What is this MR ROM you speak of? There is no such thing as MR ROM for the Z4 Tablet. Afaik we only have AOSP 5.02, 5.1.1, 6.0 and the latest stock 5.0.2 ROM. Flashing anything else would likely end up in it hanging, like you experience.
With the current state of ROMs, I advice to just flash the official stock ROM, benefit from it's stability and full copmpatibility, SuperSU it, try Xposed (v79, sdk21, arm64) and freeze/uninstall system bloatware with an app like Titanium Backup.
Click to expand...
Click to collapse
OK, MR is MarshMallow, i did see someone has made an AOSP ROM works and i'm eagerly to have a try, i terminate it forcely and now it hangs on 'starting apps', looks it's already upgraded because i lose
adb connection, anyway to rescue this?
Hi
I have Mm 6.01 installed via adb sideloading from lollipop without any wipe. Somehow it worked.
The reason I had to do it that way is that phone is encrypted but when I boot to TWRP it does not recognise my decryption Pin so I couldn't flash from recovery.
I was using the seraja recovery.
Anyone got access to the encrypted partitions through TWRP? I don't know how to install TWRP 3.0.2 which might have a fix for the pin problem. Each way I try doesn't work. Any ideas?
Sent from my D6503 using XDA-Developers mobile app
fezzawinkle said:
Hi
I have Mm 6.01 installed via adb sideloading from lollipop without any wipe. Somehow it worked.
The reason I had to do it that way is that phone is encrypted but when I boot to TWRP it does not recognise my decryption Pin so I couldn't flash from recovery.
I was using the seraja recovery.
Anyone got access to the encrypted partitions through TWRP? I don't know how to install TWRP 3.0.2 which might have a fix for the pin problem. Each way I try doesn't work. Any ideas?
Sent from my D6503 using XDA-Developers mobile app
Click to expand...
Click to collapse
Since you was on a twrp recovery so you made your bootloader device unlocked so you can easily install twrp 3.0.2 which maybe help you in solving your problem
To flash Twrp 3.0.2 follow this:
1- Download Twrp 3.0.2 from this link: https://dl.twrp.me/sirius/twrp-3.0.2-0-sirius.img.html
2- By using Fastboot you have installed on your PC, Put the twrp 3.0.2 you have downloaded in step 1 in the folder of ADB and Fastboot and you can flash twrp 3.0.2 by using this command: fastboot flash recovery twrp-3.0.2-0-sirius.img
If there is any question or a problem with this guide just tell me and i will help you
I hope that i had helped you.
Mostafa Sherif said:
Since you was on a twrp recovery so you made your bootloader device unlocked so you can easily install twrp 3.0.2 which maybe help you in solving your problem
To flash Twrp 3.0.2 follow this:
1- Download Twrp 3.0.2 from this link: https://dl.twrp.me/sirius/twrp-3.0.2-0-sirius.img.html
2- By using Fastboot you have installed on your PC, Put the twrp 3.0.2 you have downloaded in step 1 in the folder of ADB and Fastboot and you can flash twrp 3.0.2 by using this command: fastboot flash recovery twrp-3.0.2-0-sirius.img
If there is any question or a problem with this guide just tell me and i will help you
I hope that i had helped you.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, however, it doesn't work because the encryption prevents it writing to the partition.
C:\adb>fastboot flash recovery twrp-3.0.2-0-sirius.img
sending 'recovery' (11570 KB)...
OKAY [ 0.380s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.403s
C:\adb>
Any ideas?
fezzawinkle said:
Thanks for your response. Unfortunately, however, it doesn't work because the encryption prevents it writing to the partition.
C:\adb>fastboot flash recovery twrp-3.0.2-0-sirius.img
sending 'recovery' (11570 KB)...
OKAY [ 0.380s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.403s
C:\adb>
Any ideas?
Click to expand...
Click to collapse
Sorry, I thought my bootloader was unlocked, but apparently not. Doh!
fezzawinkle said:
Thanks for your response. Unfortunately, however, it doesn't work because the encryption prevents it writing to the partition.
C:\adb>fastboot flash recovery twrp-3.0.2-0-sirius.img
sending 'recovery' (11570 KB)...
OKAY [ 0.380s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.403s
C:\adb>
Any ideas?
Click to expand...
Click to collapse
fezzawinkle said:
Sorry, I thought my bootloader was unlocked, but apparently not. Doh!
Click to expand...
Click to collapse
So your problem has been solved or not??
If not you have to unlock your bootloader which will allow you to install twrp recovery from adb command successfully.
Tell me the final result
I have a Sony Xperia Z5C (E5823) which is running android 5.1.1.
I want to install Lineage OS on this system so I unlocked to bootloader. The bootloader status is now:
Code:
Rooting status:
Bootloader unlocked: Yes
I then used this thread to install TWRP. I downloaded recovery_v3.2.1_02.05.2018.img and installed it using adb and fastboot:
Code:
$ adb reboot bootloader
$ fastboot flash recovery recovery_v3.2.1_02.05.2018.img
target didn't report max-download-size
sending 'recovery' (17356 KB)...
OKAY [ 0.589s]
writing 'recovery'...
OKAY [ 0.151s]
finished. total time: 0.741s
$
Everything seems to go well, I'm happy.
But when I try to reboot to recovery, I get the Sony Xperia white splash screen and the the powered by android splash screen, then it boots under android, nor recovery. I get this behaviour when I try to boot with Power + Volume down, and when I use adb:
Code:
adb reboot recovery
I don't understand why, but my Z5C can't boot to TWRP. I'm then unable to install Lineage OS.
I think that the recovery is ok as some people reported that the recovery worked with their device. Thanks @GreyLeshy for this great work. I then think that there is something wrong with my device, but I can't guess what. If anybody has an idea, he will be more than welcome as I really need some help now. I'm unfortunately stuck...
successful!
I tried to get some help on Freenode #lineageos where I found a helpful guy (LuK1337). He advised me to upgrade the stock rom of the smartphone (from Android 5.1.1 to Android 7) before trying to flash TWRP.
I tried to do so, and I finally managed to boot to TWRP without any problem.
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
pim8181 said:
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
Click to expand...
Click to collapse
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
kilroystyx said:
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
Click to expand...
Click to collapse
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
pim8181 said:
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
Click to expand...
Click to collapse
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
kilroystyx said:
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
Click to expand...
Click to collapse
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
pim8181 said:
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
Click to expand...
Click to collapse
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
pim8181 said:
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
Click to expand...
Click to collapse
No, you are doing right. Can you post the output from fastboot during the installation?
kilroystyx said:
No, you are doing right. Can you post the output from fastboot during the installation?
Click to expand...
Click to collapse
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
pim8181 said:
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
Click to expand...
Click to collapse
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
kilroystyx said:
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
Click to expand...
Click to collapse
It didn't work , maybe I can flash the stock system image from fastboot?
pim8181 said:
It didn't work , maybe I can flash the stock system image from fastboot?
Click to expand...
Click to collapse
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
kilroystyx said:
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
Click to expand...
Click to collapse
I don't know how to get these ones can you explain it to me?
pim8181 said:
I don't know how to get these ones can you explain it to me?
Click to expand...
Click to collapse
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
kilroystyx said:
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
Click to expand...
Click to collapse
It worked, many thanks for your help!
For those that have issues with the programme, I had to uncheck the verify header checksum button in the settings file in order for it to work properly.
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
pim8181 said:
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
Click to expand...
Click to collapse
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
kilroystyx said:
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
Click to expand...
Click to collapse
My TWRP is completely lost and the tool doesn't seem to work, I wiped data cache and dalvik.
When you flash a rom aren't you just supposed to flash the rom itself, when I bricked my phone by installing Xposed I just reflashed the rom it's sytem image and a boot image. How should I do it?
Hi,
my Xperia Z2 (runs on Android 4.4.2) is rooted with Kingroot app, the bootloader is unlocked and I flashed recovery with fastboot to TWRP and got the notify flashing was finished.
[email protected] ~ $ fastboot flash recovery /home/mint/Desktop/twrp.img
sending 'recovery' (13302 KB)...
OKAY [ 0.528s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.408s
Click to expand...
Click to collapse
When I open the ROM manager app it says my recovery system is TWRP.
My problem: I can't boot in TWRP!?! Intention is to flash system to Lineage OS 17.1.
Not with Volume down+power, not via adb command "reboot recovery" and not with some apps I tried with reboot options, nothing works.
Meanwhile I flashed 3 different TWP images, 3.0.2-0, 3.2.3-0 and 3.3.1, always with the same results like listed above. Booting in TWRP is not possible. Of course I would try it with an similiar image like clockworkmod, but couldn't find one for my device.
I've the same problem in the moment...
Do you've a solution for me?