i have a Karbonn A30 with 5'9" screen.i want to create a CWM recovery for the device.
i have tried many ways but its not working.the original recovery is attached below.
michael.the.don said:
i have a Karbonn A30 with 5'9" screen.i want to create a CWM recovery for the device.
i have tried many ways but its not working.the original recovery is attached below.
Click to expand...
Click to collapse
Have you tried running it through the official Clockworkmod Recovery builder? Or have you taken a look at the guides Porting ClockworkMod Recovery to a New Device and [GUIDE] Compile CWM Recovery?
i have tried porting it. i dont knw if its working or not.because its a MT6577 device and i cannot get it to flash the recovery partiton. even AIO flasher hangs when i try to flash recovery.can u tell me if the below given build is a successfull port.i used the online builder for this.
how did u extract recovery.img??
rakesh1988 said:
how did u extract recovery.img??
Click to expand...
Click to collapse
First you have to figure out which block is the recovery partition this can be found by either typing in terminal emulator or ADB shell "mount" or running a command similar to "cd dev/block/platform/{SoC Name Here for example mmci-omap-hs.0}/by-name" then once in that directory "ls -l" noting the block name of the recovery partition. After you have done that then you can dump the recovery partition to your phone by running the command "dd if={path to recovery partition you obtained earlier from one of the above mentioned commands} of={path to SD Card or output destination}/recovery.img".
michael.the.don said:
i have tried porting it. i dont knw if its working or not.because its a MT6577 device and i cannot get it to flash the recovery partiton. even AIO flasher hangs when i try to flash recovery.can u tell me if the below given build is a successfull port.i used the online builder for this.
Click to expand...
Click to collapse
Try flashing it through MobileUncle Tools, worked on MMX A110, another MT6577 device.
MobileUncle Tools doesnot flash.anyway bricked my device using sp flash tools.it will be back tomm from servicing.
michael.the.don said:
MobileUncle Tools doesnot flash.anyway bricked my device using sp flash tools.it will be back tomm from servicing.
Click to expand...
Click to collapse
is there no stock rom for a30 which can be used to flash the phone using sp flash tool??
i tried to get recovery img dump on sd card
i was at cd dev/block/platform/abcd(soomething was der)/by-num
after that i get list of mmcblk0p1 to mmcblk0p6
how to confirm that which is a recovery ?
arkerio said:
i tried to get recovery img dump on sd card
i was at cd dev/block/platform/abcd(soomething was der)/by-num
after that i get list of mmcblk0p1 to mmcblk0p6
how to confirm that which is a recovery ?
Click to expand...
Click to collapse
The directory should be by-name not by-num. After you are in the correct directory type "ls -l" the recovery partition should be the partition with the "SOS" name listed. If you only have by-num directory you can try running (Make sure to be running the shell as superuser by typing "su" in terminal emulator or ADB shell first) "cat /proc/mtd" and if that doesn't work try (Also with superuser permissions) cat /proc/emmc both of this commands if they return a value the recovery partition will be named "recovery". Let me know if you still have questions .
here is s gscript that lets u dump all the partitions.a ful rom backup.
i have a full dump.only the PRELOADER and DSP_bl is corrupted.
i cant get them to load in sp flash tools
see the attached gscript.for complete backup use the "back_mt6575_a4_v2c" script.
i have attacher the scatter file if some one needs it.my device is still in servicing.so i cant go foreward.
{credits for the "back_mt6575_a4_v2c" script to original developer.i fount it not mine.i dont knw whos it is.}
M very noob in all this things and i dnt know how to use above scripts
but from the reply above -1
i got it how to backup recovery img
cat /proc/emmc this command works
learning learning learning will ask question if i stuck
preparing ubuntu pc
here is the turorial how to use the gscript.http://forum.xda-developers.com/showthread.php?t=1825722
see the section where it says rombackup.
but instead of using the script mentioned in the tutorial.use the one i have given above.u dont need any commands here.it will backup automatically/.
Hi
m getting error while unpacking recovery.img
"Error: the input file does not appear to be a valid file. at ./unpack-mt65xx.pl
line 45."
but the recovery.img which is attched to firsth post is getiing unpack perfectly
what m doing wrong
i got recovery by following commands
one is - cat /dev/block/mmcblk0p2 > /mnt/sdcard/recovery.img
&
second is if=/dev/block/mmcblk0p2 of=/mnt/sdcard/recovery.img
using both the command i get recovery.img but it is of 5MB
and the recovery which is attached at 1st post is of 6MB
EDIT:
michael.the.don i have used ur given script and m able to get all img as backup
and i have also created cwm as per guide given by you
let me know how you bricked ur device ?
what you were trying ?
How did you get that scatter file ?
my recovery is attached but yet no tried it
cherry mobile titan CWR,TWRP and Stock Recovery
High Guys here is the different recoveries from our rebranded Karbon a30 to Cherry Mobile Titan TV
Clockworkmod - CWMR - 6.0.1.5
https://mega.co.nz/#!YUgEkSKC!JjokMRNW9dmpk5XbVVSBKz4LAi9fjcAWkzuChCDuE4s
TWRP Lewa Recovery - 1.0
https://mega.co.nz/#!oVoS2ABB!TGXNFF0dL6V5J2enBS0juGYWXKRhwOpPddJV0GC_q_g
TWRP Lewa Recovery - 2.3
https://mega.co.nz/#!9d5FxIpT!XqBoqyiDJg914Tfajwp4i3xioMAjo9ZVI2zf5LqjRbc
Stock Recovery
https://mega.co.nz/#!dAZSDCba!CP49czZxvdpbKBG3gWzPMzSv3bxdFRi8AQKvEI2-5z4
Enjoy
rnovino
Junior Member
Join Date: Nov 2012
Posts: 16
cherry mobile titan CWR,TWRP and Stock Recovery
High Guys here is the different recoveries from our rebranded Karbon a30 to Cherry Mobile Titan TV
Clockworkmod - CWMR - 6.0.1.5
https://mega.co.nz/#!YUgEkSKC!JjokMR...cAWkzuChCDuE4s
TWRP Lewa Recovery - 1.0
https://mega.co.nz/#!oVoS2ABB!TGXNFF...OpPddJV0GC_q_g
TWRP Lewa Recovery - 2.3
https://mega.co.nz/#!9d5FxIpT!XqBoqy...9ZVI2zf5LqjRbc
Stock Recovery
https://mega.co.nz/#!dAZSDCba!CP49cz...Ri8AQKvEI2-5z4
Enjoy
Click to expand...
Click to collapse
These are .img files and need to be flashed using Mobile Uncle from Play Store
Once you have downloaded any of the recovery file you need to download the MOBILE UNCLE MTK TOOL on google play store for you to port the recovery update on your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and then copy the RECOVERY.IMG from the recovery image you have downloaded either the CWMR and TWRP on the root of your sd card or internal storage
now open the MOBILE UNCLE MTK TOOL and click the RECOVERY UPDATE and you will see the RECOVERY.IMG at the top that you have copy on the root of your storage.
NOTE: be sure to check the spelling that it is spelled as “recovery.img” without the quotes or else it will not be detected on the folder
now just click ok then ok again and it will reboot to recovery, after rebooting it will now be on the recovery mode that you have chosen , in this example i used the TWRP v2.3.2.3.
and now you can select backup and check all the things you want to backup and swipe the handle on the bottom part and wait for it to finish
to check if you have backup successfully you can click the restore mode and you will see the backup you have made, and from there you can choose on what backup you want to restore.
ALL THE BEST GUYS!!!!!
SOURCE:http://pinoyscreencast.net/cherry-mobile-titan-tv-and-karbon-a30-stock-cwmr-v6-0-1-5-and-twrp-v2-3-2-3-recovery/
If You find my post helpful, Hit Thanks!
Thank you. Flashed CWMR successfully on Karbonn A30
ApplePriest said:
Thank you. Flashed CWMR successfully on Karbonn A30
Click to expand...
Click to collapse
AWESOME!!!!!
Twrp (karbonn a30) link is asking for decryption password, please share the same
Sent from my Micromax A110 using Tapatalk 4 Beta
Hoe to download recovery. Img from above link
Sent from my Karbonn A30 using XDA Premium 4 mobile app
Related
Team Win Recovery Project v3.0.0.0 for D605
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HOW TO INSTALL:
Flash from old recovery:
Reboot to your current recovery.
And flash the archive.
Flash recovery.img without custom recovery:
Extract contents on your PC
Copy loki_flash and recovery.img to you phone's SD card via MTP connection
Download and start Android Terminal Emulator from Play Store
From terminal emulator type: $ su
Then type (assuming files from zip were copied to external SD card root) :
# cp /storage/external_SD/loki_flash /storage/external_SD/recovery.img /data/local/tmp
# cd /data/local/tmp
# chmod 777 loki_flash
# ./loki_flash recovery recovery.img
# reboot recovery
DOWNLOAD:
Link to flash from recovery:
https://mega.nz/#!fo8DCDbb!wvN9GTN7xzuTGnNMBfu4UwmAo7culclt88qb-qJoZLI
Link to flash without recovery:
https://mega.nz/#!y1dk0KwS!HAwU-Pi6jgfQPe3c1yID9WmX76X_afdNpTpToPbfqSA
STATUS:
Stable (but I have not tested)
Nice work, thx (will you end cm12?)
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Downgrade to jb
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Ag0n1a said:
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Click to expand...
Click to collapse
I have win 10. And i bricked (Hard) LG l9 II
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Ag0n1a said:
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Click to expand...
Click to collapse
I don't know where you guys get your information from but stop saying phones are not possible to hard brick and spread this word around. It is very easy to hardbrick any phone with root.
I will go just in a little bit of detail to show you.
How does your computer boot?
The hardware you have (CPU, GPU, Memory etc) are searched for (physical addresses) by the motherboard by the BIOS. Delete or erase the BIOS and I bet you any sum that your computer will stop doing anything (starts and sits idle just fans spinning).
With this analogy the BIOS of any mobile device is the bootloader. In the bootloader, that is located on the eMMC (embedded Multi Media Controller; like an SSD but with the controller of memory in the silicon die). eMMC is partitioned like a hard disk.
Your phone has an integrated Primary Loader in the CPU (this is what Qcom 9008 is). By shorting pins you change the boot order. If you short correct pins you can send data into memory (RAM) from the CPU and then write it on the eMMC (if you have the correct communication). This is where the HEX programmer comes in. This is how Qualcomm tools know how to communicate with the SOC.
The 2nd loader is on the eMMC. By default all CPU's boot from eMMC. SBL1->aboot and so on is the bootchain. Where hardware is initialized and recognized. Destroy and of those partitions and you will have a hardbrick (either fallback to 9008 automatically because eMMC is empty or not recognized at all).
Well I ended up giving you kind of a full information. Just stop trowing around this thing "phones can't be hardbricked". Hardbrick describes the state where a phone can't enter the last emergency mode provided by the manufacture (Emergency in this case). And generally buttons don't work, screen isn't either and so on.
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Ag0n1a said:
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Click to expand...
Click to collapse
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
A
neutrondev said:
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
Click to expand...
Click to collapse
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Ag0n1a said:
A
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Click to expand...
Click to collapse
Yeah you are right. That is just a message it will not flash it for you. But if you see that message and try to flash a lower aboot without flashing full KDZ you are in big trouble.
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
AWESOME1092387456 said:
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
Click to expand...
Click to collapse
For me the installation works but don't install it... i've installed cm12 and it sayed secure booting failed
and backup/restore doesn't work, it corrupted /data partition but i resolved it.
Kaszke said:
Downgrade to jb
Click to expand...
Click to collapse
How? I couldn't find a working link for a stock jb.
Cristi73 said:
How? I couldn't find a working link for a stock jb.
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=37
Find the kdz that coresponds to your region/carrier.
goooooooooD!!!! amazing job ))))
JackPOtaTo said:
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Click to expand...
Click to collapse
hey here is the solution body
II Flash
GOTO D605 RECOVRY (folder) hold shift and right click on the mouse then open window command here
then copy the commands on the cmd
you need to have adb driver installed and here the download link http://www.mediafire.com/download/u6pdpy77sonjyqh/D605+RECOVRY.rar
1 adb push aboot.img /data/local/tmp
2 adb shell
3 su
4 dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4 exit
5 exit
6 adb push loki_flash /data/local/tmp
7 adb push recovery.img /data/local/tmp
8 adb shell
9 su
10 cd /data/local/tmp
11 chmod 777 loki_flash
12 ./loki_flash recovery recovery.img
13 reboot recovery
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
sedi21 said:
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
Click to expand...
Click to collapse
but how did you unlock it? because i don't know how to unlock mine and i don't think its possible
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bismillahi Alrahmani Alraheem
(in the name of God the most gracious, the most merciful)
Finally Unoffoicial TWRP 3.0.2 is here for Dual sim version of XPERIA Z3 (D6633)!!
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
And much more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
Notes About Sony Devices:
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here:
https://github.com/Dees-Troy/extract_elf_ramdisk
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
DOWNLOAD:
Please notice that it won't work in stock based roms, only custom roms will run it
20160907 (img)
20160907 (zip)
Installation methods
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/recovery-twrp-302-z3dual.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Fastboot method:
you should have fastboot in your pc (either downloaded separately or with android SDK)
fire up Terminal (Linux and OS X) or CMD window (MS Windows) in the folder you have the image on it and it is preferred to copy the image to the folder of fastboot so the following command work then type:
Code:
fastboot flash FOTAKernel recovery-twrp-302-z3dual.img
don't forget to put ./ before 'fastboot' if you are using OS X or linux (./fastboot)
ZIP method:
flash the zip using any recovery
Themes and colors:
HERE
(Read Post #2 in the link if you want to customize, I'll be making pre-made themes later on inshaaAllah (God willing) )
NOTE: You are free to repack it and even sharing it without taking my permission
Please Donate If you want me to support Z3 dual more and more, it is back to you
XDA:DevDB Information
TWRP 3.0.2 for Z3 Dual D6633, Tool/Utility for the Sony Xperia Z3
Contributors
Muhammad Ashraf
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Testing
Created 2016-06-25
Last Updated 2016-09-07
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
sorry for the late reply, I am not sure why does it act like that
i'll try to make a zip file for that issue
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Oh, I am SOOOOOOOO Sorry, You have noticed me, By mistake I have uploaded Cyanogenmod Recovery instead of twrp
figuring that out now
I am sorry all of you
thanks man
EDIT: DONE
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Unlocked or Locked bootloader?
(Does this require an unlocked bootloader?)
I cannot get to recovery mode using DD or fastboot
Command will go through but adb reboot or h/w combos wont get me recovery. How do I install recovery ? . I have a ROM that can only be installed via recovery pl help
I cannot get to recovery mode using DD or fastboot
FAILED (remote: Command not allowed)
it always says "FAILED (remote: Command not allowed)"
should the bootloader be unlocked ?!
what is the problem here?!
Hi, i flashed the .img using my twrp, the only option on "select partition" was kernel, i know i shouldn't have done it, but i did. Now the phone doesn't boot, it keeps on a black screen. I think i need to flash a new kernel, can someone help me? Thanks
edit
Locked bl
Excellent WORK +++++
Bismillahi Alrahmani Alraheem YOU are my god!
Well done. You are the man. Exellent work with this TWRP for my D6633 (z3 dual)
it saved my life!
bryantshurley said:
I cannot get to recovery mode using DD or fastboot
Click to expand...
Click to collapse
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
"fastboot flash boot recovery-twrp-302-z3dual.img" got me to a new recovery screen and can no longer boot the system.
rzepek2pl said:
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
Click to expand...
Click to collapse
That was a bad advice. Now I only have TWRP on my phone. Only boots into this!
Can it be saved? How?
Your 20160907.zip based on TWRP 3.0.2 was put into root & flashed with TWRP v2.8.7.0 which did not update, when re-launching recovery I was still on v2.8.7.0
Hello guys,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lenovo K6 Power k33a42 is a new device released by lenovo on Dec 16, as many of you have bought this phone i would like to share how this phone can be rooted and how we can install twrp on this phone
UNLOCKING BOOT-LOADER :
Unlocking your Android phones bootloader is the first step to rooting and flashing custom ROMs
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
1) Download the View attachment K33a42_bootloader_unlock.zip and View attachment drivers.zip zip archive attached here
2) On your device, turn on USB debugging and allow OEMunlocking
if there is no developer options in settings - go to the " Settings -> Device Info " and click on the item " Build number " until the display shows that " you became a developer
go back to the device's main Settings menu and go to Developer options tick "OEM unlocking " and " USB debugging'
when you connect for the first time using debugging via USB you will need to confirm the RSA fingerprint key to trust the PC
3) Extract the Unlock bootloader zip to any directory
4) Connect the device (K33a42) to a PC via USB-cable.
5. Go to the extracted directory and execute Unlock_Bootloader.bat and expect to complete the unlock process.
after the process is completed the boot loader will be unlocked.
INSTALLING TWRP :
1) Extract the folder View attachment TWRP.zip archive to any drive.
2)On your phone, turn on USB debugging (drivers for ADB must be installed).
Connect your phone to a PC via usb-cable
3) You have 2 options either you can try the TWRP (only run one time) or else you can replace the stock recovery with twrp
Use accordingly
run Flash-TWRP.bat (replace stock recovery) or
run Run-TWRP.bat (for one time only).
4) Wait for the phone to boot into TWRP.
You can now disconnect the usb-cord.
Installation is finished.
and also at the starting of the twrp recovery the language will be in Russian because the creator in SevenMaxs from lenovo-forums.ru (I'am looking forward to modify default lang to english)
here is the video which shows how to do so
https://www.youtube.com/watch?v=KOhR92EKD7A
* In the stock firmware Secure Boot is enabled by default , so any changes made to the system partiton lead to a bootloop. Therefore, when you first start TWRP set the system mode to Read Only !
So in order to proceed we need to disable the secure booting in the kernel
Now to disable Secure Boot verification in the boot.img
1. Extract boot.img using twrp backup of boot partition
(you can use android image kitchen for extracting)
2. Make changes in the ramdisk \ default.prop file
change the following line:
ro.secure = 1
to
ro.secure = 0
3. repacked boot.img and flash into the device using twrp.
I know this part may be tough for some uses hence voila i have the secure boot disabled boot image , flash this to boot partition using twrp
ROOTING
Flashing SuperSU zip via TWRP Recovery
Download and transfer the View attachment SuperSU-v2.79-201612051815.zip zip file attached here to your device’s storage.
Boot your device into TWRP recovery.
Tap on Install and select the SuperSU zip file that you transferred to your device in Step 1.
After selecting the .zip file, do Swipe to Confirm Flash on the bottom of screen to begin the flashing process.
Once SuperSU is flashed, you’ll get Reboot System option, select it.
Congratulations! Your device should be rooted now. Look for the SuperSU app in app drawer.
INSTALLING XPOSED
1)Install the xposed installer from playstore
2)Open the installer, and tap the ‘Install/Update’ button. Don’t worry if the app seems stuck here; just give it time and it will eventually show you a Superuser request, which you should make sure to grant and click reboot
Almost all the modules should work on stock rom as it is close to Aosp
modules which i can confirm to work are
: Android N-ify
; Gravitybox
: Bootmanager
:fingers-crossed:
All the credit goes to SevenMaxs
for creating the recovery
and for his guides for proper installation
orginal forum thread
please thank him :fingers-crossed::fingers-crossed:
Thank you
Thankzz.
Sent from my CAM-L21 using Tapatalk
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Plzz, fix it
Sent from my CAM-L21 using Tapatalk
I found another SuperSU, that worked for me: https://www.androidfilehost.com/?fid=385035244224405790
Thank you again ArjunrambZ and SevenMaxs!
LoverOfLife said:
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Click to expand...
Click to collapse
i will take a look at the zip, may be upload problem, well any super su zip will work,, this was thw one that i tried
Sent from my VIBE K6 Power using XDA Labs
LoverOfLife said:
Thank you
Click to expand...
Click to collapse
taweng7 said:
Thankzz.
Click to expand...
Click to collapse
taweng7 said:
Plzz, fix it
Click to expand...
Click to collapse
will uplpad today
also the secure boot disabled boot img also
:laugh:
Sent from my VIBE K6 Power using XDA Labs
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
ilfastidio said:
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
Click to expand...
Click to collapse
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Click to expand...
Click to collapse
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
ilfastidio said:
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
Click to expand...
Click to collapse
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Click to expand...
Click to collapse
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
ilfastidio said:
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
Click to expand...
Click to collapse
okay, firstly im also ain't any expert, but i get your point
i dont know why secure boot was enabled in recovery
but when i tried the procedure as explained in the thread i didnt get bootloop ( keeping secure boot in recovery) hence i came to the conclusion that it may not be valid.,, and i may be completely wrong here, if some one could clarify if would be better
Sent from my VIBE K6 Power using XDA Labs
Rooting panasonic eluga note 32GB ROM
Please provide rooting mothod for panasonic eluga note
amnv said:
Please provide rooting mothod for panasonic eluga note
Click to expand...
Click to collapse
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
Click to expand...
Click to collapse
Its ok brother.. Thanks
My wifi is not working can someone help me? I did this process and after that it's not working
foRgaK said:
My wifi is not working can someone help me? I did this process and after that it's not working
Click to expand...
Click to collapse
i havent experienced this issue
but if u can attach a log file of turning on tbw wifi ,we can help
Sent from my VIBE K6 Power using XDA Labs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
Unlocked Honor 7x : See this [But don't flash twrp from anywhere else before backing up your device. Use twrpimgmount_ramdisk for backing it up first.]
Download:
TWRP Complete Backup
TWRP Img mount not tested yet
Instructions:
Flash twrpimgmount_ramdisk.img through fastboot
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
Press and hole both volume + power on to boot to erecovery OR volume up + power on to boot to twrp (i don't know which combination is of which one) i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Backup/restore and flash image functions are tested for system/vendor/product/version/cust/oeminfo/recovery/recovery2/boot rest of them are not tested by me but should work.
Note: It is suggested to make a complete backup in memory card before rooting your Honor 7x.
After backing up, flash TWRP Complete Backup Ramdisk
Join Telegram group if you are willing to test latest stuff
Credits:
Ported form Honor 6x : OP
Follow next:
1. Flash Magisk 16.0+ to root
XDA:DevDB Information
[OREO]TWRP COMPLETE BACKUP, Tool/Utility for the Honor 7X
Contributors
Sudeep Duhoon, Pretoriano80, zxz0O0
Version Information
Status: Testing
Created 2018-03-17
Last Updated 2018-04-07
For Nougat : Go Here
Reserved
TWRP on my OREO Beta Not Detecting My Phone on Pc no Response Please Check Ur Recovery
Can I do this with the Bnd-L24 model that has the bootloader unlocked with TWRP installed?
Great bhai
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Sudeep Duhoon said:
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Click to expand...
Click to collapse
one further note, using the "complete_twrp_ramdisk.img" TWRP was able to see the installed OS, and offered to install the TWRP app.
Sudeep Duhoon said:
i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Click to expand...
Click to collapse
What does this mean?
---------- Post added at 10:08 AM ---------- Previous post was at 09:36 AM ----------
I couldn't get it to backup. It always fails at data or system (If I don't select data).
Tried both images.
how can i flash the stock recovery? i was able to brick my device
Edit: nvm i fixed it
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Hi, I'm glad to report that although the first recovery that is twrpimgmount_ramdisk.img failed to backup system as I got the same error message as above but I was able to flash some other partitions like kernel, recovery etc... I actually selected a bunch of them.
Anyway most importantly after flashing the complete_twrp_ramdisk.img, I was able to backup system successfully. I'm using the Indian variant BND AL10 MODEL. I hope this helps some one out there.
I have a dumb question: Now, that the system is backed up with twrp, if I mess up my phone ever, can I simply restore this system img and be able to boot back into the os? Do I need to install any other partitions? I don't care about data. Please let me know.
Hi, I flashed this complete_twrp_ramdisk.img and now I want to go back to stock recovery of oreo which is bnd_recovery_nocheck.img from the other post. I tried using adb and it fails. I tried using the this twrp but it shows a lot of partitions to choose from and I'm confused example: ramdisk recovery, recovery_vendor, recovery_ramdisk etc... there are sooooooo many. I tried recovery_vendor and also ramdisk but it doesn't work. Can you please tell me how to install the stock recovery?
Does anybody have a BND-L21 backup of the system partition?
Edit: nvm i found it
Can someone tell me how to install stock recovery after installing the above complete_twrp_ramdisk.img as I'm unable to flash using adb. I tried "fastboot flash recovery recovery.img" and also "fastboot flash recovery_ramdisk recovery.img" I tried flashing the BND_recovery_nocheck.img from the other post which is a stock one.
I also tried flashing it using this twrp to the partition recovery_ramdisk and gives the error saying "the size is larger than the device" Please someone help.
I have tried couple times to install new release
twrp_ramdisk_oreo_7-4-18.img
Click to expand...
Click to collapse
But I can only get to twrp splash screen.
OP change-log has no information about this new release, so maybe is still not ready.
telegram group has mention of this , but did not help Yet.
**EDIT**
It was suggested by DEV in telegram to just be patient and try again. This third time installed 4-7-2018 released version it loaded right into recovery, without any delay.
Don't know if it is coincidence or not but before I was on RRos ROM. and now I am back on EMUI 8
Well, the mess here you have gentlemen, nichrome you do not understand where the root for 7ku, where to 8ku, what tvrp to put for 8ki for everyday needs.
---------- Post added at 03:56 PM ---------- Previous post was at 03:52 PM ----------
Which TWRP can I put in order to flush the root on the 8th oreo?
What TWRP should I be using on RROS Room? In order to install Magisk?
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
darkmage1991 said:
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
Click to expand...
Click to collapse
Afaik they are test builds (ports) of data decryption enabled twrp.
I had them working when on the Oreo beta but cannot get to work on RR or the new official Oreo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: twrp-montana-3.2.3.0.img
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2 @lohanbarth
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.3-0
Stable Release Date: 2018-10-08
Created 2018-07-05
Last Updated 2018-10-08
I think i have found a error. Cant decrypt files. TWRP from Squid a could do that. Your TWRP gives failed password error with correct password.
lohanbarth said:
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Source Code:
Github
Contributors
@[email protected]@[email protected]
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.2-0
Stable Release Date: 2018-07-05
Created 2018-07-05
Last Updated 2018-07-05
Click to expand...
Click to collapse
Support on Arm64 rom's?
Adamask said:
I think i have found a error. Cant decrypt files. TWRP from Squid a could do that. Your TWRP gives failed password error with correct password.
Click to expand...
Click to collapse
go to wipes and click on data format.
rssxda said:
Support on Arm64 rom's?
Click to expand...
Click to collapse
Yes
twrp 3.2.3 in op.
after wipe data and reboot the phone twrp is not there
Cesarcami53 said:
after wipe data and reboot the phone twrp is not there
Click to expand...
Click to collapse
it's normal you have to flash a .zip file so that it stays
Where is the twrp zip..??
Hello ! guys ... I'm without pc can I flash it for this app?
zanduo said:
Hello ! guys ... I'm without pc can I flash it for this app?
Click to expand...
Click to collapse
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
lohanbarth said:
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
Click to expand...
Click to collapse
I have root and twrp and bootloader .... the problem and that I am without pc ...
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
lohanbarth said:
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
Click to expand...
Click to collapse
Thanks man i use flasify And Works! Thanks ! Now i waiting for 64 roms
I have another problem. I managed to flash the recovery.img sucessfully (as described) and I can start TWRP. It functions properly, however every time I do a backup (not recovery!) after reboot the TWRP is gone.
How is that possible? Why the recovery partition gets overwriten or damaged by a simple backup?
How do I permanently flash the recovery partition with TWRP without need to reflash it every time?
RuKlowd said:
I have another problem. I managed to flash the recovery.img sucessfully (as described) and I can start TWRP. It functions properly, however every time I do a backup (not recovery!) after reboot the TWRP is gone.
How is that possible? Why the recovery partition gets overwriten or damaged by a simple backup?
How do I permanently flash the recovery partition with TWRP without need to reflash it every time?
Click to expand...
Click to collapse
flash a .zip file (magisk or a custom rom) to fix it
ur backup gets the original recovery of stock rom.. then, if u recovery u lost the twrp, but, if u recovery and reinstall twrp from twrp for .img, u dont lose him..
lohanbarth said:
flash a .zip file (magisk or a custom rom) to fix it
Click to expand...
Click to collapse
Thanks, it worked! So the recovery partition won't really (permanently) flash unless you root the device, right? Do I always need to root to permanently flash any other partition, too?
ilovepanda said:
ur backup gets the original recovery of stock rom.. then, if u recovery u lost the twrp, but, if u recovery and reinstall twrp from twrp for .img, u dont lose him..
Click to expand...
Click to collapse
Sorry, I had difficulties to understand you :/
if you make a backup, the backup will also add the recovery stock, so when restoring, it will also restore the backup of the recovery stock, it would be better to install the stock and before the first boot, install the twrp via .img
is this recovery only fot the xt1792, or can i also use it for the xt1794 ?
PhoenixGamer said:
is this recovery only fot the xt1792, or can i also use it for the xt1794 ?
Click to expand...
Click to collapse
You can