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.
Related
First the facts:
I have a Transformer Prime TF201
-l have Cyanogen mod 10-20140104 installed
-I used to have CWM recovery installed (Cant remember witch version)
-I have followed this guide: http://androidroot.mobi/t3_nvflash/ to get nvFlash and AndroidRoot.mobi bootloader (v9.4.2.28r01)
After this i wanted to install TWRP as i had problems taking rom backups with cwm.
I followed this guide http://teamw.in/project/twrp2/93 and downloaded and installed "openrecovery-twrp-2.3.3.0-tf201-JB.img" using fastboot
The ".img" version of twrp seems to be for those who have AndroidRoot.mobi bootloader
after this i was unable to restart from fastboot, so i just did a manual restart with the power button
Now i expected the progress bar to appear, but android just started to boot.
After the boot i tried to boot to recovery using the power menu, just booted back to android again.
Then i tried getting inn to recovery by holding power and vol down, same thing then also. just booted in to android.
I have also tried to install cwm (recovery-clockwork-5.8.3.4-tf201.img) using fastboot with the same result.. no progress bar appears after reboot.
This is the result when installing CWM in fastboot:
C:\android-sdk\platform-tools>fastboot -i 0x0b05 flash recovery cwm.img
sending 'recovery' (5408 KB)...
OKAY [ 2.594s]
writing 'recovery'...
OKAY [ 2.132s]
finished. total time: 4.734s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.553s
(The device is not restarting, i have to do this manualy)
I have also tried installing CWM in android terminal using "dd if=/sdcard/cwm.blob of=/dev/block/mmcblk0p4"
This is the result:
[email protected]:/ $ su
[email protected]:/ # dd if=/storage/sdcard0/cwm.blob of=/dev/block/mmcblk0p4
10816+1 records in
10816+1 records out
5537896 bytes transferred in 6.596 secs (839583 bytes/sec)
So now im left without a recovery at all
Anyone that might have some tips for me?
? I just read the part where you attempted to install from the os. your prime still boots? lucky. where is the nvidia on the splash screen at boot up bottom center or bottom right?
i have same problem also, my tf201 now have bootloader unlock and twrp 2.2.2.0 recovery, i try to upgrade it to the latest version following instuctions on http://teamw.in/project/twrp2/93
on my command prompt, it said that flashing recovery is success, but everytime i boot to recovery, it is still 2.2.2.0
Solved
I was able to get twirp on by flashing an older wersion of twrp (v 2.3.1.0)
svefro said:
I was able to get twirp on by flashing an older wersion of twrp (v 2.3.1.0)
Click to expand...
Click to collapse
you were actually fortunate you did not completely brick your prime. you did twice what you should never do. you tried to put a jellybean recovery on an ICS bootloader. then not knowing if you had jellybean bootloader or not you attempted to install cwm which is strictly for ics. Both of these things are what hard bricks the most primes here. When you do want to upgrade to Jellybean I suggest you go to post 2 of the androwook thread and follow the instructions there.
I assumed i had JB bootloader since i have android 4.1.2 installed.. guess not
is this the thread you are referring to? http://forum.xda-developers.com/showthread.php?t=1674827
and this is the official ASUS JB Bootloader? Update JB Bootloader.zip ?
can i just flash the jb bootloader and then twrp 2.3.3.0?
do i need to do a whipe and reinstall my rom afterwards?
I realy appreciate the help im getting here.
I have xperia s (st25a) phone with android 4.0.4.
I already have rooted it (SU installed) and bootloader unlocked. Fastboot reports the correct version "5".
However, when I try to install TWRP, it gives the following error:
>fastboot.exe flash boot stock-6.1.A.0.452-twrp-2.4.0.0.elf
sending 'boot' (8124 KB)...
FAILED (remote: The Device must be rooted first)
Why does TWRP think it's not rooted? I have setup SU to grant every root request too!
Another issue - when I try to enter recovery with stock image, my phone gets stuck on boot with Sony logo and I have to remove battery to shut it down. Any ideas why wouldn't stock recovery work?
Thanks much for your help!
Help!
Any one has any ideas to try?
NovaSupreme said:
I have xperia s (st25a) phone with android 4.0.4.
I already have rooted it (SU installed) and bootloader unlocked. Fastboot reports the correct version "5".
However, when I try to install TWRP, it gives the following error:
>fastboot.exe flash boot stock-6.1.A.0.452-twrp-2.4.0.0.elf
sending 'boot' (8124 KB)...
FAILED (remote: The Device must be rooted first)
Why does TWRP think it's not rooted? I have setup SU to grant every root request too!
Another issue - when I try to enter recovery with stock image, my phone gets stuck on boot with Sony logo and I have to remove battery to shut it down. Any ideas why wouldn't stock recovery work?
Thanks much for your help!
Click to expand...
Click to collapse
You would have more luck in your device respective subforum.
http://forum.xda-developers.com/xperia-s
Hi, all.
I was messing around with Android Tweaker 2, zipaligning my apps, performing vague system tweaks and the like, when I rebooted my phone for the changes to take effect; however, the phone booted up, finished the booting animation, and where the home screen should be showing up only showed a black screen. From there I can only reboot again, reboot into STOCK recovery, or reboot into fastboot, which has limited function in an Asus device (inability to flash unsigned custom recovery images, inability to flash rom images, stock firmware images are unavailable ANYWHERE, etc.) My device WAS rooted, however, I did a factory reset from the stock recovery in hopes that the problem would be resolved, so I'm not sure if root access was retained. I've tried a lot of things, but what I need is access to adb to push some files, or just figure out what the hell happened to the device.
Any ideas? Thanks in advance.
Details:
Asus Padfone X [4.4.2 stock rom]
WAS rooted
LOCKED bootloader
STOCK recovery
Fastboot is basically useless, given the "safeguards" Asus has implemented
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
daggorlad said:
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
Click to expand...
Click to collapse
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
shattered519 said:
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
Click to expand...
Click to collapse
Glad I was able to point you into the right direction.
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,
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?