Related
Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
go0dlife said:
Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
Click to expand...
Click to collapse
Unlock the bootloader, go to adb/fastboot folder and store your ROM's boot.img there. Shift + Right Click within that folder and Open command window (be in fastboot mode on your phone in the meantime) :
fastboot flash boot boot.img
fastboot erase cache
Go to recovery, wipe all except SD (you can if you don't need your files) and flash a fresh ROM. Also, lock the bootloader and never ever flash any custom ROM again if you're going to call it crap whenever you fail.
edit: it isn't that easy to brick the device, and finally, your topic doesn't belong in this subforum.
how to update hboot version? i need 1.31
ok i unlocked now i have hboot 1.12.0000
but i cant install the rom i followed your instruction and get bootloop..
go0dlife said:
Today i tried to install this crappy Custom Rom http://forum.xda-developers.com/showthread.php?t=1705334&highlight=bootloop Renovate 1.1 i installed 2 other Roms before and all of those was succesfully , then i tested this and i got into a bootloop , so i restored my backup , this bootloops too and the 2 other roms bootloop too , i tried so much things now i can go to bootloader but its Relocked Security Warning what can i do?
Click to expand...
Click to collapse
The rom is crap because it didn't work or because you don't have a clue what your doing? It's not nice to say the roms crap when so many people have used without problem and without a doubt the problem will be down to you. People put a lot of time and effort into roms for free so try to be more respectful.
Sent from my Nexus 7 using Tapatalk 2
Agree
As previously said - These guys are all doing soooo much work for us (the community) and it's NOT paid - anyone who makes a ROM, ANYONE - needs to be applauded even for trying, but I'm sure that most ROM chefs test their roms to a point before releasing them and that you've probably missed a step or flashed incompatible zips or something...
Did you extract the boot.img from the roms zip file and "fastboot flash boot boot.img" it? It sounds like you might have been playing with ROMS which all worked on the same kernel and now you've flashed one which uses a different one, resulting in a bootloop like you say - I'm a noob and have done this a few times. Boot into bootloader, fastboot flash your boot.img, then boot into recovery and flash the rom (factory reset / wipe all data / cache / dalvik) and you might be lucky enough to boot into the rom!
These steps MAY not fix your problem if it is something else - but from my experience they are not steps which will brick your device, if you don't think you've flashed the boot.img - then I'd start there.
With our HOX's you ALWAYS need to remember (ALWAYS ALWAYS ALWAYS) to flash (in fastboot mode) your boot.img (which is 99% of the time, included inside the roms ZIP file...
Hope I've helped!
(Hit thanks if I did! )
Before saying those "crappy" words to the rom. Read alot first. All the answers are in the forum. Rom chefs dedicate time to cook a good rom.
Sent from my HTC One X using xda app-developers app
Guys......its not the rom, its not the boot.img.........surprise ! Its his hboot (1.12)
Get that updated otherwise it will never run.
And please loose the attitude towards roms that don't boot. They all boot but check the requirements first
Its your phone/hboot that does not support it
AW: HTC One X brick? Help me
http://m.youtube.com/#/watch?v=wwleOote5M0&desktop_uri=/watch?v=wwleOote5M0&gl=DE
hey guys,
I loaded the unofficial, then the official versions of LineageOS, as well as SlimRom
after successfully installing both the rom and the gapps 7.1 via recovery, I can't get past the initial android OS screen
my phone simply reboots, and stays in this loop forever
is there something wrong with my phone or did I mess up the install somewhere?
Try an older version of Gapps
maxgohan said:
hey guys,
I loaded the unofficial, then the official versions of LineageOS, as well as SlimRom
after successfully installing both the rom and the gapps 7.1 via recovery, I can't get past the initial android OS screen
my phone simply reboots, and stays in this loop forever
is there something wrong with my phone or did I mess up the install somewhere?
Click to expand...
Click to collapse
Most of the 7.1.1 ROM doesn't work for Canadian network. So far, only one ROM that worked i.e. https://forum.xda-developers.com/htc-one-m8/development/rom-t3430080
Give it a try
ckpv5 said:
Most of the 7.1.1 ROM doesn't work for Canadian network. So far, only one ROM that worked i.e. https://forum.xda-developers.com/htc-one-m8/development/rom-t3430080
Give it a try
Click to expand...
Click to collapse
thanks so much!
I flashed this rom and it works!
I was beginning to think something was wrong with my phone...
My Mi Max is unlocked, rooted and runs LinageOS 14.1.
I have been wanting to try out MIUI again and downloaded the recovery Rom from the MIUI Forum.
I have been using nijel8's TWRP but tried others.
Installing the ROM works with no problems but afterwards I get the message that no OS is installed and when I try to boot nothing happens even after 60 Minutes.
Am I missing something?
Thanks in advance
entermaxx said:
My Mi Max is unlocked, rooted and runs LinageOS 14.1.
I have been wanting to try out MIUI again and downloaded the recovery Rom from the MIUI Forum.
I have been using nijel8's TWRP but tried others.
Installing the ROM works with no problems but afterwards I get the message that no OS is installed and when I try to boot nothing happens even after 60 Minutes.
Am I missing something?
Thanks in advance
Click to expand...
Click to collapse
reboot to twrp and flash the rom again this time it should boot fine. I'll also facing this issues several times when I'm on miui rom only flash it again should solve the problem.
Zasnizas said:
reboot to twrp and flash the rom again this time it should boot fine. I'll also facing this issues several times when I'm on miui rom only flash it again should solve the problem.
Click to expand...
Click to collapse
Thank you. But unfortunatly is does not make a differnece. Still doesnt boot. I have also tried every combination of 'wipe' with this Flash.
The ROM doesnt even boot. The Phone doest post, but it does not try to boot as in the boot Animation does not show.
entermaxx said:
Thank you. But unfortunatly is does not make a differnece. Still doesnt boot. I have also tried every combination of 'wipe' with this Flash.
The ROM doesnt even boot. The Phone doest post, but it does not try to boot as in the boot Animation does not show.
Click to expand...
Click to collapse
Flash lazy_flasherhttps://androidfilehost.com/?fid=457095661767111293 after flashing stock ROM, it should boot after that
Sent from my Mi Max Prime using Tapatalk
T.kum1993 said:
Flash lazy_flasher after flashing stock ROM, it should boot after that
Sent from my Mi Max Prime using Tapatalk
Click to expand...
Click to collapse
Thank you. That was it. I have read about that file bevore but all the versions i came across did not work.
hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that
logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.
so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D
cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards
Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/
daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?
NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way
daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers
Since there hasn't been any up-to-date TWRP for the Z2 Tablet recently, I finally compiled a new one, which can also handle Android 10 encryption.
I have only tested it on Android 10, but I assume it should work on Android 9 as well (please report if you try).
For older Android versions, I recommend using older TWRPs.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Download
https://www.androidfilehost.com/?w=files&flid=313349
Use "castor_windy" for the WiFi variant, and "castor" for the LTE variant!
Installation
fastboot flash recovery twrp.img
Sources
Manifest for TWRP:
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0
Kernel source:
https://github.com/AICP/kernel_sony_msm8974/tree/q10.0
Device tree source:
https://github.com/SpiritCroc/android_device_sony_castor_windy/tree/TWRP-9.0
https://github.com/SpiritCroc/android_device_sony_castor/tree/TWRP-9.0
Contributors - huge thanks for their work on TWRP for related devices!
@NeoArian
@115ek
Thank you for the update SpiritCroc!,
Have ran through all the basic functions in TWRP, and have not had any issues. Will test further in the next week, but so far working great for me. Thank you again!!!
Working fine, I flashed the latest build with it.
Only an error message on a recovery map file when booting to TWRP.
Thank you !
Working great on castor, flashed the latest build with it.
I flashed the Recovery, but I can't seem to boot into it. What is the button combination in order to boot into recovery mode?
KOAO said:
I flashed the Recovery, but I can't seem to boot into it. What is the button combination in order to boot into recovery mode?
Click to expand...
Click to collapse
Turn on the device, and when the sony screen comes up and the LED flashes magenta, press any volume button. Then, the LED should switch to yellow and TWRP should come up.
This procedure requires support for booting to recovery from your ROM (or more precisely, your kernel/bootimage), so it might be different based on what you use.
If you use a ROM which works with other recoveries but not this one, please report, then I'll put a note in the first post - I have only tested it with AICP 15.0 so far.
SpiritCroc said:
Turn on the device, and when the sony screen comes up and the LED flashes magenta, press any volume button. Then, the LED should switch to yellow and TWRP should come up.
This procedure requires support for booting to recovery from your ROM (or more precisely, your kernel/bootimage), so it might be different based on what you use.
If you use a ROM which works with other recoveries but not this one, please report, then I'll put a note in the first post - I have only tested it with AICP 15.0 so far.
Click to expand...
Click to collapse
I use the stock rom, since I had to downgrade to 4.4.2 in order to backup the TA Keys before unlocking the bootloader. Maybe that's why it doesn't work?
KOAO said:
I use the stock rom, since I had to downgrade to 4.4.2 in order to backup the TA Keys before unlocking the bootloader. Maybe that's why it doesn't work?
Click to expand...
Click to collapse
If you are on SONY'S OS i.e. STOCK ROM with STOCK KERNEL, you should be using NUT'S Dual Recovery. Search NUT'S Dual Recovery on XDA, then you can select our tablet.
Here's the link - https://forum.xda-developers.com/showthread.php?t=2794175
Hope this helps...
_Sherrif said:
If you are on SONY'S OS i.e. STOCK ROM with STOCK KERNEL, you should be using NUT'S Dual Recovery. Search NUT'S Dual Recovery on XDA, then you can select our tablet.
Here's the link - https://forum.xda-developers.com/showthread.php?t=2794175
Hope this helps...
Click to expand...
Click to collapse
Huh, alright. Didn't think I'd need this since this existed, first time dealing with a sony device, very complicated lol. But thank you nonetheless!
After flashing 3.4.0 it just reboots when I try to reboot to recovery. I am on CarbonROM (Android 8). TWRP 3.3.2.1 works fine.
flymetothemoon said:
After flashing 3.4.0 it just reboots when I try to reboot to recovery. I am on CarbonROM (Android 8). TWRP 3.3.2.1 works fine.
Click to expand...
Click to collapse
I have the same problem.
flymetothemoon said:
After flashing 3.4.0 it just reboots when I try to reboot to recovery. I am on CarbonROM (Android 8). TWRP 3.3.2.1 works fine.
Click to expand...
Click to collapse
hunterb21 said:
I have the same problem.
Click to expand...
Click to collapse
Thanks for reporting, I guess it only works for newer Android versions then. Updated the OP.
flymetothemoon said:
After flashing 3.4.0 it just reboots when I try to reboot to recovery. I am on CarbonROM (Android 8). TWRP 3.3.2.1 works fine.
Click to expand...
Click to collapse
Could you please post a link to TWRP 3.3.2.1 since I can't find it anywhere?
ad_on_is said:
Could you please post a link to TWRP 3.3.2.1 since I can't find it anywhere?
Click to expand...
Click to collapse
Sure. It was in the CarbonROM thread:
https://forum.xda-developers.com/xperia-z2-tablet/development/7-x-x-carbonrom-cr-5-1-t3654983
The one for windy you find here: https://mega.nz/#F!3NYBQKCA!jO0NQBZr08RaYqIbU7whxA
I am also coming from Carbon ROM and it is really not working... I now tried via Fastboot to install another older TWRP version. But the tablet is not reacting on 'adb reboot bootloader' (it shows the device for 'adb devices'). All it shows is a black screen and the blue LED light. Any idea how to flash the older TWRP version without bootloader? Normal Carbon ROM is working fine... Thanks!!!
emartino said:
I am also coming from Carbon ROM and it is really not working... I now tried via Fastboot to install another older TWRP version. But the tablet is not reacting on 'adb reboot bootloader' (it shows the device for 'adb devices'). All it shows is a black screen and the blue LED light. Any idea how to flash the older TWRP version without bootloader? Normal Carbon ROM is working fine... Thanks!!!
Click to expand...
Click to collapse
I tried with the Sony-Emma Tool which of course removed Carbon ROM - but left the bootloader as it was. So ADB / Fastboot is still not working. How did all th others that were involved solve the corrupt bootloader?
emartino said:
I am also coming from Carbon ROM and it is really not working... I now tried via Fastboot to install another older TWRP version. But the tablet is not reacting on 'adb reboot bootloader' (it shows the device for 'adb devices'). All it shows is a black screen and the blue LED light. Any idea how to flash the older TWRP version without bootloader? Normal Carbon ROM is working fine... Thanks!!!
Click to expand...
Click to collapse
@emartino,
If you are seeing a BLACK SCREEN with BLUE LED you are in Download mode (FASTBOOT mode). Try "fastboot devices" without quotes, and you should see the device serial number, or the tablet ID number. If you do not see the device number, you will need to install the fastboot drivers. They are different than the adb drivers. This can be done through device manager for WINDOWS. Info available in the forums if you need assistance with fastboot driver install.
To install TWRP, place the TWRP.img you want to use in your ADT-BUNDLE/sdk/platform-tools folder, or whatever your path is. Then open an elevated cmd prompt, while the tablet is in DOWNLOAD MODE, and enter this command "fastboot flash recovery recoveryname.img" no quotes. The recoveryname is the name of the TWRP img file you have downloaded and put in your platform-tools folder. After the flash completes enter "fastboot reboot-recovery" must put the DASH between reboot and recovery. This will boot into TWRP.
I may have given a little more instruction than you needed, but wanted to be clear.
Hope this helps....
ALSO, i seen requests for the older TWRP. Here is a link to my SHARED GOOGLE DRIVE folder. The older TWRP will be in the folder labeled the same. https://drive.google.com/drive/folders/0BwBZlgiV0lNiV2x5SFYwMGlmNUU?usp=sharing
Everything in my shared folder was shared within XDA. Original authors and devs can be found in the threads. Locate them and hit the thanks button for them sharing their work.
Thanks for the great description! As ADB was working I neglected to verify in the Windows Device Manager if the Fastboot drivers were also ok. And they were not... With the help of Zadig I then solved this driver-issue. Now fastboot was working fine and I could flash recovery with success. Only the mentioned 'fastboot reboot-recovery' was not available in the 'Minimal ADB and Fastboot' Version of fastboot, but this was then available once I installed the Android Studio + SDKs...
But still one thing is missing - I still cannot enter TWRP. Neither via the fastboot command, nor with Power-On + VolumeUp or VolumeDown... I always end up with the Android 6 standard Sony UI. Any additional idea what could have gone wrong? I even tried various TWRP versions (3.1, 3,2, 3.4), none could be started.
emartino said:
Thanks for the great description! As ADB was working I neglected to verify in the Windows Device Manager if the Fastboot drivers were also ok. And they were not... With the help of Zadig I then solved this driver-issue. Now fastboot was working fine and I could flash recovery with success. Only the mentioned 'fastboot reboot-recovery' was not available in the 'Minimal ADB and Fastboot' Version of fastboot, but this was then available once I installed the Android Studio + SDKs...
But still one thing is missing - I still cannot enter TWRP. Neither via the fastboot command, nor with Power-On + VolumeUp or VolumeDown... I always end up with the Android 6 standard Sony UI. Any additional idea what could have gone wrong? I even tried various TWRP versions (3.1, 3,2, 3.4), none could be started.
Click to expand...
Click to collapse
@emartino,
So when you flash the TWRP recovery img, through fastboot, then reboot to recovery or power off and then on when the led turns PINK (i think that is the color) start tapping the volume up button and the led should turn orange and boot to TWRP. I may have the colors off. But when you attempt to boot to TWRP what exactly does it do? Does the system boot to AICP or stock android recovery or what? Sorry not understanding the Android 6 Sony UI. Also, do you know the firmware you are running? If your not sure, no big deal, just tell us if when you turn the device on, does it show the SONY name in the center with XPERIA across the bottom?
Wait!!!!! are you installing TWRP on SONY Stock OS???? The versions of TWRP here are for custom roms. If you are using AICP or similar custom rom, then the above questions will help us narrow down the issue.
Hi, i can't boot into recovery after flashing.
When I try to boot directly into recovery, I get the following message:
Code:
% fastboot boot TWRP-3.4.0-sc-1_castor_20200606_1421.img
Sending 'boot.img' (13266 KB) OKAY [ 0.418s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Could you please help?