Cannot boot into TWRP from phone, only from PC using fastboot boot .. - Sony Xperia X Compact Questions & Answers

Yep, its 2021 and I just have set up a new XC Kugo - bootloader unlocked, TWRP.img flashed as well manually via fastboot as well as using the flashable Zip. Can boot into bootloader either manually (Vol+) or the reboot menu (Lineage 14.1), but cannot reboot into recovery from the phone. Flashed the latest Kugo TWRP 3.4.0, but still no way to boot into recovery from phone, the only way is to use the PC and $>fastboot boot twrp.img. That works fine. The strange thing: when I change settings in TWRP, it obviously saves them on the phone, as they are set, when I boot into TWRP using fastboot. Also pressing Vol+ when the violett light comes on during boot process will not call up TWRP (nor does the reboot menu of course) it just commences with normal boot process and starts Lineage.
Is there a bug in my bootloader? Can it be fixed?

I remember from this thread:
[stock 8.0][Unlocked bl][34.4.A.2.19; ...32; ...85] Root and Recovery (3 clicks)
Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks. You need: Stock O ftf (best to use Flashtool/Xperifirm) Modded boot img for 34.4.A.2.19 -...
forum.xda-developers.com
that I had to flash a costumized boot.img when setting up TWRP for the first time. Maybe that's the step you are missing. Fingers crossed!

Thanks very much. I indeed did not flash a customized boot.img... :-(
The big question is: can I do that still? And: will that work with my lineage or woould I have to go back to Sony stockrom Android 6.0 then?

LBsys said:
Thanks very much. I indeed did not flash a customized boot.img... :-(
The big question is: can I do that still? And: will that work with my lineage or woould I have to go back to Sony stockrom Android 6.0 then?
Click to expand...
Click to collapse
No idea, sadly. Afaik (!, no guarantees) flashing a seperate boot.img does only work well with Treble ROMs. But I really am not sure about that.
I'd recommend starting from zero again, that is, going back to stock. That's at least how I'd do it.

Spaceoid said:
No idea, sadly. Afaik (!, no guarantees) flashing a seperate boot.img does only work well with Treble ROMs. But I really am not sure about that.
I'd recommend starting from zero again, that is, going back to stock. That's at least how I'd do it.
Click to expand...
Click to collapse
Problem solved, pressed the wrong key (Vol+ instead of Vol-). Still booting into recovery from boot menu doesn't work, but that's ok ;-)

Related

[Guide][How to]Update Bootloader/Firmware to OOS3/H2OS2 w/o installing OOS/H2OS

Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app

[D5803][Z3C][UB] Russel5's TWRP 3.1.1-0 FOTA Recovery MOD

Guys.
I made a bit modified version of @russel5 very nice work for our Z3C:
- A bit more colors, nice navbar buttons and new navbar background (fits to main screen background)
- More img flash options (be carefull with img flash because wrong flashes can brick you phone)
- More partition backup and restore options (boot is also included for sure - but not shown on the pic)
- New with 3.1.0-0: Additional partition for backup/restore: mmcblk1p2 ext4 mounted to /sd-ext - This is second partition on external SD Card, if available.
- New with 3.1.1-0: All above mentioned changes and official ones: https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Too beauty to keep it only for me
Requirements
Only for Unlocked Bootloader (UB)
New Bootloader needed: LA3.0_M_3
Information
Maybe NOT working with 7.x.x ROMs like (LineageOS/Carbon) - Only tested with MM and stock-like ROM (like SLiMM 3.8).
Please visit corresponing threads for help with TWRP and any 7.x.x ROM.
Installation - 2 Options:
a) Flashable zip via TWRP to update existing.
b) Extract twrp-3.x.x-0-z3c_Vxx.img from zip-file and flash via fastboot: fastboot flash recovery twrp-3.x.x-0-z3c_Vxx.img
Start FOTA Recovery:
Shut down phone completely - wait 5-10 secs - Press Power and Vol Down until short vibration - release both keys and wait - done.
UPDATE 18.06.2017
New 3.1.1-0 from Russel5 - Modded by me. Thanks to Russel5 and TWRP-Team.
UPDATE 15.03.2017
New 3.1.0-0 from Russel5 - Big thx again to him! Say thanks to him - not me!
Thanks to @russel5 - This is his work:
https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113
@fluffi444 I flashed the recovery.img in fota with twrp and recovery is still 3.0.2. Any idea why?
doriandiaconu said:
@fluffi444 I flashed the recovery.img in fota with twrp and recovery is still 3.0.2. Any idea why?
Click to expand...
Click to collapse
Maybe i have an idea.... You know how to start FOTA Recovery correctly?
Shut down phone completely - wait 5 secs - Press Power and Vol Down until short vibration - release both keys and wait - done.
Looks like you still booting your system or kernel recovery....
Otherwise check your bootloader - must be LA3.0_M_3 (Service Menu - Service Info - Software Info - S1 Boot Version)
UPDATE 15.03.2017
New 3.1.0-0 from @russel5 - Big thx again to him! Say thanks to him - not me!
can someone please explain/summarize for me the differences of twrp recoveries that we have on the z3c. if i got it right, there is (1) old bl recovery = kernel 'attached', (2) new bl recovery = seperated img from kernel and (3) fota recovery wich uses an unused partition of unlocked bl.
is that correct?
whats the advantage of fota? can every custom rom use all the different recoveries? can (2) + (3) be flashed both on the same device?
i am really confused wich version i wanna install and keep on my phone...
thanks
filou76 said:
can someone please explain/summarize for me the differences of twrp recoveries that we have on the z3c. if i got it right, there is (1) old bl recovery = kernel 'attached', (2) new bl recovery = seperated img from kernel and (3) fota recovery wich uses an unused partition of unlocked bl.
is that correct?
whats the advantage of fota? can every custom rom use all the different recoveries? can (2) + (3) be flashed both on the same device?
i am really confused wich version i wanna install and keep on my phone...
thanks
Click to expand...
Click to collapse
Yes - this all can be confusing!
I'm trying to be complete as I can be - I will mention only the last dev of the tools - Actually many more are involved and often it's an growing work of many - Especially No 1.
1) For LB - We have recovery (and root) for LB - Here the last (and best) rooting and TWRP method is the one from russel5:
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This installs recovery files to SYSTEM partition folder /system/etc/mm_twrp_recovery
This is file: recovery.twrp.cpio.lzma
2) Only UB - Recovery integrated in Kernel a) and b)
a) Rootkernel (tobias.waldvogel) https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
afaik this was one of the first tools which can integrated automaticly very resource-conserving recovery to kernel - Disadvantage: Hard to change TWRP if new version is out.
b) PoC TA Tool (munjeni) https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Great quite new tool which can also integrate TWRP (but here the complete fota recovery.img) to kernel: Advantage easy to change TWRP to new version, because full fota revovery.img is used
3) Only UB - Recovery to FOTA partition (now known as recovery partition) - newer bootloader needed
This is the recovery.img you can download from official TWRP page or from russel5 (img to be flashed via fastboot) or from this thread (flashable.zip).
Those recovery.img's are complete bootable images with zImage and ramdisk (TWRP is in ramdisk).
That all means that it's indeed possible to have THREE recvoerys running on one phone! But this is senseless of course !!!
Option 1 is only recomended if you are on LB! But works also for UB. But its away if you flash complete new ROM (as TWRP is on SYSTEM)
Option 2 is.... for what? Let me say: Only if you really need the function to reboot to recovery directly from system.
Option 3 is my favorite (but only for UB) - this is bootable no matter what you did to system or even with kernel!
It's on his own seperate partionen and save for unwanted modifications, wrong boot or system flashes, etc
Only (and actually not really an) disadvantage is that you have to start this from shutted down phone... Reboot to recovery is not working!
fluffi444 said:
Yes - this all can be confusing!
I'm trying to be complete as I can be - I will mention only the last dev of the tools - Actually many more are involved and often it's an growing work of many - Especially No 1.
1) For LB - We have recovery (and root) for LB - Here the last (and best) rooting and TWRP method is the one from russel5:
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This installs recovery files to SYSTEM partition folder /system/etc/mm_twrp_recovery
This is file: recovery.twrp.cpio.lzma
2) Only UB - Recovery integrated in Kernel a) and b)
a) Rootkernel (tobias.waldvogel) https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
afaik this was one of the first tools which can integrated automaticly very resource-conserving recovery to kernel - Disadvantage: Hard to change TWRP if new version is out.
b) PoC TA Tool (munjeni) https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Great quite new tool which can also integrate TWRP (but here the complete fota recovery.img) to kernel: Advantage easy to change TWRP to new version, because full fota revovery.img is used
3) Only UB - Recovery to FOTA partition (now known as recovery partition) - newer bootloader needed
This is the recovery.img you can download from official TWRP page or from russel5 (img to be flashed via fastboot) or from this thread (flashable.zip).
Those recovery.img's are complete bootable images with zImage and ramdisk (TWRP is in ramdisk).
That all means that it's indeed possible to have THREE recvoerys running on one phone! But this is senseless of course !!!
Option 1 is only recomended if you are on LB! But works also for UB. But its away if you flash complete new ROM (as TWRP is on SYSTEM)
Option 2 is.... for what? Let me say: Only if you really need the function to reboot to recovery directly from system.
Option 3 is my favorite (but only for UB) - this is bootable no matter what you did to system or even with kernel!
It's on his own seperate partionen and save for unwanted modifications, wrong boot or system flashes, etc
Only (and actually not really an) disadvantage is that you have to start this from shutted down phone... Reboot to recovery is not working!
Click to expand...
Click to collapse
Wow, thanks a lot @fluffi444!! It's even more complicated than I thaught. WHAT A MESS! :silly:
Well I'am still on Concept Rom --> Bootloader LA3.0_L_Hero_16. I guess that one is close to LA3.0_M_3? Don't remember where I got my TWRP 3.0.0.0 version from, but i flashed it as recovery.img, so it should be fota-type, right? Actually I can reboot from system to recovery ...
I think I'll keep this one as is and see if I need a newer version one day, when i change system to any Nougat rom.
filou76 said:
Wow, thanks a lot @fluffi444!! It's even more complicated than I thaught. WHAT A MESS! :silly:
Well I'am still on Concept Rom --> Bootloader LA3.0_L_Hero_16. I guess that one is close to LA3.0_M_3? Don't remember where I got my TWRP 3.0.0.0 version from, but i flashed it as recovery.img, so it should be fota-type, right? Actually I can reboot from system to recovery ...
I think I'll keep this one as is and see if I need a newer version one day, when i change system to any Nougat rom.
Click to expand...
Click to collapse
Yes - flashing by fastboot goes to FOTA/Recovery partition... Yes - keep it - I don't even know how Concept N or M will react...
Did anyone tried to do backup/restore with this recovery?
I am using it since flashing to LineageOS 14.1 and did multiple backups. Tonight I broken my google account in the ROM, so I wanted to restore to last backup. I already tried four of my backups and all of them are bootlooping, so I am starting to suspect the recovery, as all of those backups were done from perfectly working system.
johny.mnemonic said:
Did anyone tried to do backup/restore with this recovery?
I am using it since flashing to LineageOS 14.1 and did multiple backups. Tonight I broken my google account in the ROM, so I wanted to restore to last backup. I already tried four of my backups and all of them are bootlooping, so I am starting to suspect the recovery, as all of those backups were done from perfectly working system.
Click to expand...
Click to collapse
Yes - fully working here. Even Restore. But I still use 6.0.1.
But sometimes (not recovery version related) its not enough to restore only DATA or only SYSTEM.
It happens to me that only an complete restore of all saved partition did the trick...
But as I said that happens also with older recoverys or/and not modded.
fluffi444 said:
Yes - fully working here. Even Restore. But I still use 6.0.1.
But sometimes (not recovery version related) its not enough to restore only DATA or only SYSTEM.
It happens to me that only an complete restore of all saved partition did the trick...
But as I said that happens also with older recoverys or/and not modded.
Click to expand...
Click to collapse
Then it must be something either with my setup, or with 7.1.1 itself.
I tried everything: partial restore, full restore, new flash with recovering of data partition only... Everything was bootlooping.
I am not sure what finally worked, as I was trying it desperately for hours, but most probably the last mentioned thing without flashing Magisk.
johny.mnemonic said:
Then it must be something either with my setup, or with 7.1.1 itself.
I tried everything: partial restore, full restore, new flash with recovering of data partition only... Everything was bootlooping.
I am not sure what finally worked, as I was trying it desperately for hours, but most probably the last mentioned thing without flashing Magisk.
Click to expand...
Click to collapse
Try twrp 3.0.2.0 or 3.0.3.0. Some said they have problems with 3.1.0.0 an LOS.
UPDATE 18.06.2017
New 3.1.1-0 from Russel5 - Modded by me. Thanks to Russel5 and TWRP-Team.
Hi,
This recovery its amazing because i am trying to have a 6.0.1 With TWRP 3.x.x with Magisk, root and Xposed. At the moment when i ve Magisk and root, i miss Recovery by Magisk mod boot image.
Any idea why screen appear as out resolution or refresh. At least ... it seen enter on Recovery, BUT I CANT reset With Vol+, Vol-, Cam , Power...
at least i can connect by adb and restart.
¿Any idea?
Thanks
zeryors said:
Hi,
This recovery its amazing because i am trying to have a 6.0.1 With TWRP 3.x.x with Magisk, root and Xposed. At the moment when i ve Magisk and root, i miss Recovery by Magisk mod boot image.
Any idea why screen appear as out resolution or refresh. At least ... it seen enter on Recovery, BUT I CANT reset With Vol+, Vol-, Cam , Power...
at least i can connect by adb and restart.
¿Any idea?
Thanks
Click to expand...
Click to collapse
Hi, i know the sad answer... the problem its the screen, Original Screen (broken touch panel) show perfect Recovery but the "new" screen its the problem... its compatible but not 100% :_(
It´s curious a normal Recovery show OK but not FOTA
Hi there,
booting this current version of TWRP from `recovery/fota` is not working for me. The device just reboots but should load TWRP. I flashed it via `fastboot flash recovery [twrp.img]` without any errors.
TWRP is booting if I flash it to `boot` instead of `recovery`. I flashed CarbonROM this way but lost TWRP after that of course. I also tried [russel5's TWRP 3.1.1-0] which is not booting from `recovery/fota` either. However, an older TWRP version by Tomascus I found -> here <- is booting fine from `recovery/fota`.
Maybe this is bootloader related but I am not entirely sure. If so, how can I update the bootloader?
Sony Xperia Z3 Compact D5803
- Bootloader: 1286-7314_S1_Boot_MSM8974AC_LA3.0_52-2
- ROM: CARBON-CR-5.1-MOO-RELEASE-z3c-20170918-1012
TWRP's tried:
- Russel5's TWRP 3.1.1-0 FOTA Recovery MOD by fluffi444
- [D5803,z3c,aries]Twrp_3.1.1-0_img_for_unlocked_bootloader by russel5
- Tomascus TWRP 3.1.0-0
Andi- said:
Hi there,
booting this current version of TWRP from `recovery/fota` is not working for me. The device just reboots but should load TWRP. I flashed it via `fastboot flash recovery [twrp.img]` without any errors.
Click to expand...
Click to collapse
My MOD is technically the same as original one from Russel. So please ask in his thread (you did this already... btw: please do not post the same question in several threads)
I never tried 7.x.x-based ROMs. So I cannot say anything reladed to the compatibility I'm afraid. MM with stock-like ROM is working with 3.1.1.0 (from Russel).
I will make an note in OP...
And note this: https://forum.xda-developers.com/showpost.php?p=71882082&postcount=12
I am trying to install a newer TWRP for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have Xperia Z3C with unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.
Piospi said:
I am trying to install a newer TWRP for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have Xperia Z3C with unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.
Click to expand...
Click to collapse
To which partition have you installed the TWRP image file? Starting with your phone turned off, f it's been sent to the FOTAKernel partition, hold both the power and the volume down buttons until your phone vibrates (as if it was booting up normally), when you should release the power button. When the screen lights up, release the volume down button.
Otherwise, if you installed TWRP in the recovery partition, boot your phone up as usual. When you see the led lit up, press the volume button.
casouzaj said:
To which partition have you installed the TWRP image file? Starting with your phone turned off, f it's been sent to the FOTAKernel partition, hold both the power and the volume down buttons until your phone vibrates (as if it was booting up normally), when you should release the power button. When the screen lights up, release the volume down button.
Otherwise, if you installed TWRP in the recovery partition, boot your phone up as usual. When you see the led lit up, press the volume button.
Click to expand...
Click to collapse
Thank you very much for the answer. Starting the phone with Power + VolUp does not do anything. The phone shows the Sony logo and the system starts.
I installed the IMG file in recovery / fota and the ZIP version doesn't ask for locations.

Infinite Loop

Today I wanted to install the lineage os, but, to ensure, I installed the stock rom in my moto g4 plus.
I wiped dalvik, system, data and cache.
Then I flashed the rom and the gapps, but when I did the reboot the cell phone was in an infinite loop, but not normal, the bootanimation of the lineage appears but it never stops.
what do I do??
Sorry for the spelling mistakes, I used google translate
Try lineage oms. https://forum.xda-developers.com/showthread.php?p=69421261
Sent from my Moto G4 using Tapatalk
robot_head said:
Try lineage oms. https://forum.xda-developers.com/showthread.php?p=69421261
Sent from my Moto G4 using Tapatalk
Click to expand...
Click to collapse
I can't acces my custom recovery and can't install trough my computer
advanced_gamerBR said:
I can't acces my custom recovery and can't install trough my computer
Click to expand...
Click to collapse
Which stock ROM and custom recovery did you install, by the way?
echo92 said:
Which stock ROM and custom recovery did you install, by the way?
Click to expand...
Click to collapse
I installed Lineage OS 14.1 2017/02/21 nightly
The stock rom is this https://mega.nz/#!2skAzDKL!9VB2h6GpbrqINSpsiMLoenZEpuuCbTVGi8QtR8lWKf0
And the custom recovery is TWRP 3.0.2-0
advanced_gamerBR said:
I installed Lineage OS 14.1 2017/02/21 nightly
The stock rom is this https://mega.nz/#!2skAzDKL!9VB2h6GpbrqINSpsiMLoenZEpuuCbTVGi8QtR8lWKf0
And the custom recovery is TWRP 3.0.2-0
Click to expand...
Click to collapse
Thanks, can I ask what region/what device you have as well? I'm just wondering if that's the correct stock firmware for your device/region. Did you let your device update on OTA before flashing the LineageOS build? Are you able to roll back to a backup of your Marshmallow installation?
Also, there's a newer version of TWRP available: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 Might be worth looking into installing given the TWRP version you've installed hasn't been maintained in a while. TWRP 3.0.3n2 is a good option to go for, since it's running stably for me.
Finally, though some bugs appear to have been fixed in the latest Lineage OS nightlies, might be worth using the 13/02 build (or robot_head's suggestion of the unofficial Lineage OMS ROM) to rule out any issues with the ROM, until at least we can get your phone booting again with a custom ROM.
echo92 said:
Thanks, can I ask what region/what device you have as well? I'm just wondering if that's the correct stock firmware for your device/region. Did you let your device update on OTA before flashing the LineageOS build? Are you able to roll back to a backup of your Marshmallow installation?
Also, there's a newer version of TWRP available: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 Might be worth looking into installing given the TWRP version you've installed hasn't been maintained in a while. TWRP 3.0.3n2 is a good option to go for, since it's running stably for me.
Finally, though some bugs appear to have been fixed in the latest Lineage OS nightlies, might be worth using the 13/02 build (or robot_head's suggestion of the unofficial Lineage OMS ROM) to rule out any issues with the ROM, until at least we can get your phone booting again with a custom ROM.
Click to expand...
Click to collapse
I think that's the correct stock firmware because I already installed it before and there wasn't bugs .
The problem is I can't rool back to a backup because I can't access de TWRP or use the fastboot.
Thank you for helping me, I was able to access TWRP when my battery ran out, which interrupted the loop
advanced_gamerBR said:
I think that's the correct stock firmware because I already installed it before and there wasn't bugs .
The problem is I can't rool back to a backup because I can't access de TWRP or use the fastboot.
Click to expand...
Click to collapse
Hmm, so what happens if you power off your phone by pressing the power button for 2-3 [edit: minutes] (credit: https://forum.xda-developers.com/showpost.php?p=70973812&postcount=5), as this may cause a hard reset and possibly break the bootloop?
What do you mean by fastboot not beng useable, as in your device does not show up in ADB or that you cannot boot into fastboot?
Alternatively, are you able to access the bootloader/fastboot mode by powering off, then holding down the power and volume down keys? If so, you may be able to re-flash your stock ROM as before.
echo92 said:
Hmm, so what happens if you power off your phone by pressing the power button for 2-3 seconds (credit: https://forum.xda-developers.com/showpost.php?p=70973812&postcount=5), as this may cause a hard reset and possibly break the bootloop?
What do you mean by fastboot not beng useable, as in your device does not show up in ADB or that you cannot boot into fastboot?
Alternatively, are you able to access the bootloader/fastboot mode by powering off, then holding down the power and volume down keys? If so, you may be able to re-flash your stock ROM as before.
Click to expand...
Click to collapse
I said I could not use fastboot because I was stuck on the Lineage loading screen
It was like if the boot animation was infinite, then when I tried to use the fastboot the cell phone was not recognized.
But the "loop" stopped when the battery ran out, so I was able to initialize the TWRP
advanced_gamerBR said:
I said I could not use fastboot because I was stuck on the Lineage loading screen
It was like if the boot animation was infinite, then when I tried to use the fastboot the cell phone was not recognized.
But the "loop" stopped when the battery ran out, so I was able to initialize the TWRP
Click to expand...
Click to collapse
So you're back into TWRP now? Okay, are you restoring your backup or re-flashing your stock ROM? I'd like to check your device can boot normally again and is up to date before trying again with the custom ROM.
By the way, I made an error in my last post - I miswrote how long you hold the power button down for, it's 2-3 minutes and should achieve the same as when your battery ran out - allowing you to boot back into TWRP.
echo92 said:
So you're back into TWRP now? Okay, are you restoring your backup or re-flashing your stock ROM? I'd like to check your device can boot normally again and is up to date before trying again with the custom ROM.
By the way, I made an error in my last post - I miswrote how long you hold the power button down for, it's 2-3 minutes and should achieve the same as when your battery ran out - allowing you to boot back into TWRP.
Click to expand...
Click to collapse
I've re-flashed the stock rom and it's working well

Blocked on "Please lock the bootloader" screen A2017G

Hi guys,
First, English isn't my first language so, sorry if it hurts your eyes :/
Second, I'm new to TWRP / root etc... (since yesterday) and I don't fully understand the exact meening of all words like flash / rom etc...
So: I'm actually blocked in the "Your device can't be checked for corruption. Please lock the bootloader". Apparently it's a normal screen now, when we boot we always see this. OK ( at least that's what I read)
My volume keys aren't doing anything and I can't access my phone anymore.
I can access TWRP if I want.
Thx for responding :good:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
coremania said:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
Click to expand...
Click to collapse
How can I know if ADB recognize my phone?
I can access TWRP so I don't need to flash it again ? Is there a difference between just flash TWRP and flash TWRP with fastboot ?
Sry, my bad, i miss read that you can access twrp, sry, I thought you can't, what happens if you flash a rom, which twrp is installed, what were your steps that you end stuck on bootloader message ?
Edit: if your issue is that you don't know how to start flashing, read the Los thread and follow the op.
Instructions:
1. Install the Universal bootloader and your model specific modem.Failure to do so will not allow flashing the ROM!
2. Update recovery [Recommended -> Official TWRP for Axon7
3. Factory reset if coming from another ROM.
4. Install ROM
5. Install GApps (optionally) [Recommended -> Open GApps (arm64) (7.1) 2017-02-01 or Newer
Download all files from the thread and put them on to your microsdcard, if your twrp is up to date you don't have to do this again. Flash the zip files in the order of the instructions, just press install at twrp and choose the zips, you can add multiple and flash them together.
Man, trust me, I'm not a lazy man and all I want is to have my phone back even if it's stock
I don't understand what you're trying to make me do, sincerely
If you can give me a link where I can have a guide steps by steps or make this guide for me that would be the best thing of my day...
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
I really don't know your issue, except you seem not to read enough. What guide you want ? How I flash a custom rom to my phone ? How to use twrp ?Why you unlocked your bootloader ? How did you manage to have the stock recovery back ?
I have to guess what you want and what you already did . If you need a guide, here are severals in the guide section.
https://forum.xda-developers.com/axon-7/how-to
TheGreatNarchy said:
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
Click to expand...
Click to collapse
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
JTruj1ll0923 said:
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
Click to expand...
Click to collapse
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Choose an username... said:
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Click to expand...
Click to collapse
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
JTruj1ll0923 said:
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
Click to expand...
Click to collapse
The thing is, after you flash the universal bootloader, the TWRP on the sd gets replaced. but the TWRP that you are using is loaded in RAM. So even if you install a TWRP version you'll stay in the version you flashed before until you reboot. If you install the universal bootloader and then install the TWRP img you'll keep everything as-is on the next reboot. I discourage rebooting without a system especially on a G because any interruption might lock the phone in DFU. On an a2017U that wouldn't be a problem because the phone boots into edl if any software error is present

Help Plz...Stock recovery missing and unable to install any recovery !

Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Baron Zemo said:
Thanks in advance......i'm so frustrated feel ripping my **** off.. being struggling with this for 3 days...
I was on official stock 7.0 nougat (generic russian), genesis kernel drmfix & Twrp for about a year with no issue. In fact that's my 1st and only attempt in flashing this phone. Decided to upgrade to 8.0. Big mistake!?!
Used Emma flash to flash the latest stock 8.0 release for my region, Asia. It booted up fine, all was well. I read that flashing stock will simply remove root and twrp. But i realized stock recovery was missing as well. And i can't restore any kind of recovery no matter what i tried. Suggestions please !
When i tried to enter recovery, the phone simply vibrated twice, and then 3 times quickly. If i continue holding the buttons, it goes into a loop of black screen and boot screen.
Tried flashing twrp via adb/fastboot. It appeared successful . No error messages. File size and time taken was also reported. But no recovery upon rebooting.
Fastboot flash recovery twrp.img
I can only flash roms using Emma, Flashtool ftf always fail with a 'no loader' found message.
Tried re-flashing mm, nougat and oreo via Emma. Phone runs well for all but again no stock recovery.
Don't know what else to do or what the problem is......
If i reflash to stock rom and relock boot loader without any recovery, it that dangerous?
Click to expand...
Click to collapse
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
levone1 said:
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
1. Download 'Modded boot img for 34.4.A.2.118' from that thread
2. Flash stock with Emma
3. Don't turn on the phone, go to fastboot and flash the boot img and TWRP img
Click to expand...
Click to collapse
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Baron Zemo said:
Hi, Thanks for the reply
1. Done
2. Which do i choose in Emma? Software update content (erases user content) or Firmware update versions.
Also must i choose the stock rom which must tally with boot img 34.4.A.2.118? ie. the rom version which ends with .118?
3. Fingers crossed.
Click to expand...
Click to collapse
Yes, flash 118 fw. If you want to save data, back it up first.
levone1 said:
Yes, flash 118 fw. If you want to save data, back it up first.
Click to expand...
Click to collapse
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Baron Zemo said:
I have given up I followed the instructions explicitly.
Tried flashing latest stock from different regions via Emma, Flashtool/xperifirm and ftfs from online depositories. Then flashed with the corresponding downloaded boot.img, then TWRP without any rebooting inbetween. Even created patched boot.img from extracted .elf files to try. There was no error messages or anything.
Recovery runs fine. But starting normally it either boot loops are stuck at Sony logo.
Is there any other way to get the drm restored? Can i root it via common methods and work my way from there?
Click to expand...
Click to collapse
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
levone1 said:
Did you full wipe before flashing, or when flashing, (check boxes in 'wipe' section)?
Click to expand...
Click to collapse
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Baron Zemo said:
If i use flash tool, i ticked all boxes under Wipe sin during stock rom flashing. All the rest (exclude sin & misc TAs) are unchecked. No other wiping during the process.
If i use Emma, there's no chance to wipe anything, it's auto flash stock rom, then flash boot.img, then flash Twrp, then reboot to a boot loop.
btw, i've tried latest twrp 3.2.3 and 3.2.1
Also, when i flash stock, is stock recovery supposed to return? Twrp just gets removed, and i don't have any recovery at all.
Am i cursed?
Click to expand...
Click to collapse
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
levone1 said:
I don't think you can boot to Sony stock recovery. If you flash stock 118, then flash modded boot img and TWRP, and reboot, I don't know why it wouldn't work. Many have done it. Just to be sure -
1. To enter recovery, you power off, then press power and volume down together, until vibration.
2. First boot takes a while. Wait a good 10 minutes to be sure.
Click to expand...
Click to collapse
There's why it's so odd to me. Not the 1st time i'm doing this too. I would have waited even longer if it was stuck, but it was looping continuously back to the start.
I suspect could simply be a hardware fault developed. Anyway, i've given up. Probably best excuse to get a new phone
Many thanks for trying to help :good:
I haven't been able to get mine to reboot to recovery either, so i just boot recovery.img from fastboot anytime I want to mod. Kinda annoying but I haven't figured a way around it.

Categories

Resources