Hello everyone!
I'm here to ask help with my Xperia ZL.
I unlocked the bootloader, flashed the last TWRP odin available as boot.img through fastboot (fastboot flash boot boot.img), flashed LineageOS 14.1, Open GApps, SuperSU and everything is ok, phone working 1000x better than the stock Sony rom and rooted.
The problem is that my TWRP gone from the recovery. The recovery available is the LineageOS recovery, very limited. After some google, i found that sony don't have a recovery partition, so the custom os overwrite the recovery and bla bla bla.... So, i found that is possible to flash the recovery to the FOTAKernel to maintain my TWRP after flash a custom rom. I tried using the Xperia Recovery Manager, but the app stuck on my device when i try to format or flash fota, i tried Flashfy, but the app stuck when i go to select the file to flash...
So, i'm here to ask to you: "How is the best way to flash twrp in my fotakernel, to maintain it as my primary recovery even after flash any custom rom?"
I'm available for discuss and waiting for you help. Thanks anyway
The TWRP homepage lists using a terminal emulator in LOS as an option: (Link)
whether flashing to the FOTAKernel partition is dangerous?
[email protected] said:
whether flashing to the FOTAKernel partition is dangerous?
Click to expand...
Click to collapse
My device is Z5. Flashing TWRP to the FOTAKernel is working, recovery parition is not
Related
attached is a semi-working recovery, you can flash it with "fastboot flash recovery recovery.img".
update: the recovery can flash boot.img's too, if the custom rom uses "dd" instead of "write_raw_image" to flash the boot.img. i hope mike updates his rom
don't use anything except for "install from sdcard"
i take no responibility for any harm to your device or data
it's basicaly a repacked cwm recovery combined with the stock 1.26 recovery kernel/ramdisk with modifications to init.rc
it is intented for developers wanting to toy around with custom roms, until someone makes a real recovery
no support nor updates will be made for this
is it tested or not yet.
I've tested it
ok thanks, since currently there is no other option to unlock bootloader other than htcdev & lack of RUU sources is too risky to flash custom recovery at this point. so technically it will skip zip package signature check? so we can start working on working custom rom.
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
looks nice!
could you maybe share your knowledge about creating this recovery? i'm trying the same for the one s but can't get it packed together correctly...
blubbers said:
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
Click to expand...
Click to collapse
Understand. My concern is no RUU for my device available yet & im afraid to use from other region stock rom Thanks for ur effort.
Do I have to unlock my phone to install this recovery?
moom999 said:
Do I have to unlock my phone to install this recovery?
Click to expand...
Click to collapse
yes, there are only 2 ways of installing a recovery.
fastboot and adb
fastboot requires you to unlock in order to "fastboot flash recovery"
and in order to possibly do it through adb you need root and in order to get root at the minute you need to be able to flash an insecure boot image through fastboot, which again, you need to unlock in order to "fastboot flash boot"
Hi blubbers,
There is a guy on general thread who wants to dump a developer phone. It's s4 not tegra but might help.
http://forum.xda-developers.com/showthread.php?p=24496390
sent from my HTC one X using tapatalk
I just noticed a few things. The stock based roms are using the Dual Recovery in their rom, but CM based roms, like Resurrection Remix, uses Cyanogen Recovery.
So when I flash RR, it automatically replaces my recoveries with the Cyanogen Recovery.
Is there any way to avoid that? Or is there any way I can flash my Duel Recovery back after installing RR?
SethPDA said:
I just noticed a few things. The stock based roms are using the Dual Recovery in their rom, but CM based roms, like Resurrection Remix, uses Cyanogen Recovery.
So when I flash RR, it automatically replaces my recoveries with the Cyanogen Recovery.
Is there any way to avoid that? Or is there any way I can flash my Duel Recovery back after installing RR?
Click to expand...
Click to collapse
It's not all cm-based ROMs that use cm recovery. Each ROM is different. It's discussed in the RR thread, and it's in the 2nd post that cm recovery is built in to that ROM. There's links there for other recovery options. I like to always have Rashr on hand to easily flash IMGs, so I can access my backups from other recoveries. Dual recovery is just not going to work on every ROM.
levone1 said:
It's not all cm-based ROMs that use cm recovery. Each ROM is different. It's discussed in the RR thread, and it's in the 2nd post that cm recovery is built in to that ROM. There's links there for other recovery options. I like to always have Rashr on hand to easily flash IMGs, so I can access my backups from other recoveries. Dual recovery is just not going to work on every ROM.
Click to expand...
Click to collapse
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.[/QUOTE
I haven't used RR since 1st build, but I know it's been addressed in the thread. I would be glad to try it out to help. Meanwhile, I would try to flash twrp with fastboot, (you said you used Flashtool - maybe the same, but worth a try), and also try flashing M5, (which you need recovery to do, but you could use a temp. boot.img to get into recovery, then flash M5), which may work better with recovery. There's also Nut's PC installer. And search the RR thread.
I'll attach a copy of twrp 2.8.7.0 to try. Hope this helps.
(File too big to attach. Let me know if you want it and I'll send a link)
Click to expand...
Click to collapse
levone1 said:
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.[/QUOTE
I haven't used RR since 1st build, but I know it's been addressed in the thread. I would be glad to try it out to help. Meanwhile, I would try to flash twrp with fastboot, (you said you used Flashtool - maybe the same, but worth a try), and also try flashing M5, (which you need recovery to do, but you could use a temp. boot.img to get into recovery, then flash M5), which may work better with recovery. There's also Nut's PC installer. And search the RR thread.
I'll attach a copy of twrp 2.8.7.0 to try. Hope this helps.
(File too big to attach. Let me know if you want it and I'll send a link)
Click to expand...
Click to collapse
You can't because CyanogenMod uses its own Recovery based of CWM ( I think? ). You could try however, using a custom kernel that has its own Dual recovery ( for e.g. PhilzTouch and TWRP )
Click to expand...
Click to collapse
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.
Click to expand...
Click to collapse
I just remembered something else. See my post here- http://forum.xda-developers.com/showpost.php?p=62114382&postcount=534 - latest version of Rashr doesn't seem to work on some ROMs. Try this one...
Edit - I just successfully flashed twrp 2.8.7.0 on latest RR using Rashr. Make sure to use this version, not the latest Play Store.
Okay so I tried what @levone1 said. I installed that Rashr which you uploaded. I tried flashing the recovery with this, and it worked! Thank you very much guys for your help!
hey thanks to levone1 i got twrp running on crDroid rom.:good::good::good:
i did it like he said: Use his Version of rashr and flash his twrp. done!
I was on OOS community build 3.5.3 with modified twrp-3.0.2-19-oneplus3.
I wiped everything except internal storage after that I tried to flash official TWRP.
After installing official twrp via modified TWRP. Niether I can boot into my recovery nor able to install any recovery via fastboot.
it I use "fastboot flash recovery recovery.img"
after installing recovery with this command My bootloader get stuck then I have to again restart my bootloader.
please help
You're probably stil on 3.5.2 firmware which isnt compatible with official twrp. Try and get into fastboot and try flashing modified twrp again. Then reboot in recovery and flash 3.2.6 firmware (not the rom) from modified twrp. Then reboot and flash official twrp from recovery or in flashify app.
i had this problem the other day, fixed this by flashing the modified recovery from a post here turn it off the booted it up by holding vol down + power and somehow it worked i was able to go into twrp
innocentwoolf said:
I was on OOS community build 3.5.3 with modified twrp-3.0.2-19-oneplus3.
I wiped everything except internal storage after that I tried to flash official TWRP.
After installing official twrp via modified TWRP. Niether I can boot into my recovery nor able to install any recovery via fastboot.
it I use "fastboot flash recovery recovery.img"
after installing recovery with this command My bootloader get stuck then I have to again restart my bootloader.
please help
Click to expand...
Click to collapse
I have same issue it is called half-brick go to full brick post here (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)
read whole post and prefer method 2 it will work like charm and i got when i am installing freedom os CE version and if it work then thank me
are you stuck with a black screen when booting to recovery if yea then wits the same situation i was in.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56 that recovery helped me
Seagorilla2 said:
You're probably stil on 3.5.2 firmware which isnt compatible with official twrp. Try and get into fastboot and try flashing modified twrp again. Then reboot in recovery and flash 3.2.6 firmware (not the rom) from modified twrp. Then reboot and flash official twrp from recovery or in flashify app.
Click to expand...
Click to collapse
yes.. tried that only and it worked...
thanks
danxtian said:
are you stuck with a black screen when booting to recovery if yea then wits the same situation i was in.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56 that recovery helped me
Click to expand...
Click to collapse
that helped me to thanks
Hi there.
I'm using Global Developer ROM(MIUI9, 8.4.19).
And I'm trying to flash TWRP and install Custom ROM.
I asked Xiaomi for unlock my bootloader, and after 72 hours I could unlock my phone.
After that, I flashed TWRP 3.2.1-4.
Method to flash :
1. Boot into fastboot mode(vol down + power)
2. On windows command prompt, type "fastboot flash recovery twrp.img", "fastboot reboot"
but I can't boot normally, only can boot fastboot & TWRP recovery.
I tried several methods.
1. Try LazyFlasher - bootloop, nothing was changed.
2. Try to flash another ROM(8.1 OmniROM) and gapps(OpenGapps, ARM64 pico) - same bootloop, with Omni bootlogo.
3. Try to flash OmniROM and LazyFlasher - same bootloop.
I can revoke my phone by Fastboot ROM and have no problem without trivial permission reset, but I can't use TWRP still.
Any methods to flash TWRP without bootloop?
flashing twrp doesnt cause bootloop. you went wrong somewhere. did you format system partition before flashing new rom?
yusoffb01 said:
flashing twrp doesnt cause bootloop. you went wrong somewhere. did you format system partition before flashing new rom?
Click to expand...
Click to collapse
Of course.
On the other hand, definitely, just flashing TWRP causes bootloop. I assume that stock beta rom might cause bootloop by incompatibility of TWRP, but I can't return to stock stable rom because I can't use TWRP recovery so I would lose all of my data.
try using stable rom. when i bought this phone2 years ago, i could flash twrp and root miui just fine
How does one get back to stock recovery for the Mate SE BND-L34?
My phone is rooted with TWRP/Magisk but would like to try AOSP to see if it will fix my issues but AOSP says it won't work with twrp. Thanks
teatimecrumpet said:
How does one get back to stock recovery for the Mate SE BND-L34?
My phone is rooted with TWRP/Magisk but would like to try AOSP to see if it will fix my issues but AOSP says it won't work with twrp. Thanks
Click to expand...
Click to collapse
ASOP will work with both TWRP and Magisk. The install is different as you flash just a system image from fastboot instead of through TWRP. The only other issue that I know of is with a factory reset/wipe which is needed when installing a GSI like most of the ASOP stuff. If you do a factory wipe through TWRP, you will brick your device. The factory wipe has to be done through the stock recovery. Basically, download the firmware for your phone and extract either 'recovery' or 'recovery_ramdisk' depending on if you are on Oreo or Pie. Flash that file through fastboot "fastboot flash (name of reovery partition on your device) (name of recovery file in the fast boot folder) for mine it looks like this "fastboot flash recovery recovery.img"
You will have to reinstall magisk after you install your choosen GSI