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?
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
Hello. Today i tried to flash the phone to the stock ROM twice but it didnt work probably cause unlocked bootloader and custom recovery (TWRP).
So i brick the phone and now i cant access the rom or the recovery. All i can do is access the fastboot mode. I tried to install the new recovery through fastboot but it doesnt work.
I tried the twrp 3.0.2.0 and 3.0.1.0 for yuga.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.342s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.347s
Tried various of commands that i found on google and this forum but nothing worked. I unlocked the bootloader before when i was installing various of custom roms. Could somehow stock rom affect the bootloader when i was flashing through flashtool ? I tried to only boot the recovery from the img, the command worked but the recovery did not boot.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.341s]
booting...
OKAY [ 0.033s]
finished. total time: 0.378s
Tried to check the status of bootloader but the command is just showing ... and nothing happend. Tried to get the IMEI through fastboot getvar command but no output is given. Im desperate. Sorry for english not my native language. I'll appreciate all the help.
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.
I tried to install lineage OS 17.1 on a Moto-Z with Android 6.0.1, and failed.
Here is one error I'd like to solve - this command:
fastboot flash recovery twrp-3.3.1-0-griffin.img
Results in:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20536 KB) OKAY [ 0.443s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.481s]
Finished. Total time: 0.932s
twrp-3.3.1-0-griffin.img is the lastest image, from here.
The same error appears when I try to flash the lineage recovery:
fastboot flash recovery lineage-17.1-20201211-recovery-griffin.img
So what is wrong here?
I've been flashing a Moto e5 Plus today, and the ADB messages were the same, except without the "has slot" line. I think they are standard.
I also had trouble getting TWRP to "stick". What ended up working was booting into the bootloader, flashing TWRP and instead of rebooting I selected "recovery" with the volume buttons.
The TWRP site says this in its instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
but holding Power + Volume Up after reboot didn't seem to work for me.
mfs-ness said:
What ended up working was booting into the bootloader, flashing TWRP ...
Click to expand...
Click to collapse
How did you flash TWRP - from the bootloader?
Or from the PC via fastboot - in which case there is always the above error, not just with TWRP images.
This is how I flashed TWRP from a linux desktop:
Code:
./adb -d reboot bootloader
sudo ./fastboot flash recovery ~/Downloads/twrp-3.4.0-0-hannah.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (19798 KB) OKAY [ 0.795s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.552s]
Finished. Total time: 1.352s
The first line results in the screen with the open-chested android. Then I ran the fastboot command. Then I selected "recovery mode" on the phone.
mfs-ness said:
This is how I flashed TWRP from a linux desktop:
...
Click to expand...
Click to collapse
Not different from my technique.
So we seem to have different conditions on the phone, firmware, whatever.