[RECOVERY][UNOFFICIAL]TWRP Recovery Project 3.5.2 Micromax IN 1 (E6746) - Miscellaneous Android Development

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
*/Your warranty is now void.
We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers./*
Click to expand...
Click to collapse
FLASH GUIDE
1. Unlocked your bootloader
2. Download twrp-3.5.2-e6746.img
3. Run this Following commands
1. adb reboot bootloader
2. fastboot --disable--verification flash vbmeta vbmeta.img
3. fastboot flash recovery twrp-3.5.2-e6746.img
4. fastboot reboot recovery
Click to expand...
Click to collapse
DOWNLOAD
Device Tree
Working
• Decryption
• fastbootd
• MTP & ADB
Bugs
• spam me in support group
• Tell me
Support group
• here
Credits
• TEAM WIN FOR TWRP
• @ZanGhoul in TG
• and @uknowndevice in TG

where is vbmeta.img
I am trying to backup stock recovery using
fastboot boot <recoveryname>.img
says ok but boots to stock recovery not TWRP.

sieger007 said:
where is vbmeta.img
I am trying to backup stock recovery using
fastboot boot <recoveryname>.img
says ok but boots to stock recovery not TWRP.
Click to expand...
Click to collapse
Much better fastboot flash twrp.img, but if you backup stock recovery, just try to pull it via adb

ok I dont have root. How can I backup recovery and other partitons without root

sieger007 said:
ok I dont have root. How can I backup recovery and other partitons without root
Click to expand...
Click to collapse
Try, reboot to recovery mode if, pc read your device adb pull /dev/block/by-name/recovery

mastersenpai05 said:
Try, reboot to recovery mode if, pc read your device adb pull /dev/block/by-name/recovery
Click to expand...
Click to collapse
that is the problem
fastboot boot recovery does not boot to TWRP & I dont have root - I am stuck

if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?

sieger007 said:
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
Click to expand...
Click to collapse
Yeah, stock rom issue need to root sir, but I will fix it sir.

sieger007 said:
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
Click to expand...
Click to collapse
Not in stock firmware sir? The stoc recovery.img?

mastersenpai05 said:
Not in stock firmware sir? The stoc recovery.img?
Click to expand...
Click to collapse
I meant I tried .... fastboot boot <thisTWRPfile>.img after running vmeta and it will still boot into stock recovery. If I boot in stock recovery - adb shell will not run cos stock recovery does not support it. Problem is there isnt so far stock firmware available , so if I mess up and no backup - I have to run to service center and more $

sieger007 said:
I meant I tried .... fastboot boot <thisTWRPfile>.img after running vmeta and it will still boot into stock recovery. If I boot in stock recovery - adb shell will not run cos stock recovery does not support it. Problem is there isnt so far stock firmware available , so if I mess up and no backup - I have to run to service center and more $
Click to expand...
Click to collapse
MICROMAX IN 1 E6746 http://mtk-p.micromaxinfo.com/product/E6746/Software/India/MMX_E6746_SW_V10.0._HW_V1.0_20210416.zip

mastersenpai05 said:
MICROMAX IN 1 E6746 http://mtk-p.micromaxinfo.com/product/E6746/Software/India/MMX_E6746_SW_V10.0._HW_V1.0_20210416.zip
Click to expand...
Click to collapse
thanks i will check it out. Just wanted to check if this TWRP support USB OTG.Want to transfer Nandroid backup to FLash Drive

sieger007 said:
thanks i will check it out. Just wanted to check if this TWRP support USB OTG.Want to transfer Nandroid backup to FLash Drive
Click to expand...
Click to collapse
Yes sir, I want to know that too. Not yet try but try to check then tell me

TWRP installed fine . OTG works. Now the other 3 letter problem .....OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?

sieger007 said:
TWRP installed fine . OTG works. Now the other 3 letter problem .....OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?
Click to expand...
Click to collapse
I don't think so if possible to use twrp in ota update, but you can use twrp for flashing recovery rom ( stock recovery rom)

mastersenpai05 said:
I don't think so if possible to use twrp in ota update, but you can use twrp for flashing recovery rom ( stock recovery rom)
Click to expand...
Click to collapse
I don't know what are the exact criteria for successful OTA update from a vague idea I think it check whether there is original boot and recovery image otherwise says no
in that case would flashing this DM verify no encrypt module remove this checking and after installing this we should be able to to install periodic OTA updates
or as a long-term procedure every time I have to install OTA I have to restore original boot and recovery or should I just restore recovery

as follow up - I could install OTA by restoring stock r'y . There isn't a need to restore boot. You can keep it this way or else if TWRP is restored the same proc ought to repeat before the next OTA.
I am attaching stock boot and recoveries here in case they could be of use.
Boot-recovery--mmx1

sieger007 said:
as follow up - I could install OTA by restoring stock r'y . There isn't a need to restore boot. You can keep it this way or else if TWRP is restored the same proc ought to repeat before the next OTA.
I am attaching stock boot and recoveries here in case they could be of use.
Boot-recovery--mmx1
Click to expand...
Click to collapse
Nice thank you so much! You can also join in micromax in 1 group in telegram

Update : it never worked. I thought it did but that update notice sprung and it wanted to do it all over again. I restored stock recovery. No Luck OTA's keep failing. I then restored stock Boot after removing magisk . Still got veriification error. My BL is unlocked. What does it take to get my OTA zip file working.... do I flash dm verify force encrypt . Why does it refuse. Should BL be locked as well anyone have luck push OTA update after rooting IN 1

Do you have kernel source code

Related

Bricked S7 - Imei lost

I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
{
"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"
}
darkalez said:
Click to expand...
Click to collapse
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?
MAX 404 said:
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?
Click to expand...
Click to collapse
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp
darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)
darkalez said:
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp
Click to expand...
Click to collapse
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?
darkalez said:
I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
Click to expand...
Click to collapse
DroidHackeR said:
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)
Click to expand...
Click to collapse
MAX 404 said:
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?
Click to expand...
Click to collapse
Looks like OP has tried ODIN already
/data is likely encrypted, so it's not surprising that it doesn't mount, but it looks like you may have corrupted your EFS somehow. This is actually really REALLY bad. The EFS is device unique and by design irrecoverable. Previous Samsungs could regenerate it if you wiped it from recovery and then flashed stock with Odin, but AFAIK this hasn't worked since the S5. If you decide to wipe it make sure you dd your existing partition first, but if that doesn't fix it you may need to take it to a service centre and pay for a repair
Always backup the EFS first before flashing ROMs
flashing stock won't fix IMEI. Looks EFS is broken.
Try to find some1 with box.
*Detection* said:
Looks like OP has tried ODIN already
Click to expand...
Click to collapse
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did
MAX 404 said:
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did
Click to expand...
Click to collapse
BTW, to address that error he needs to format data. But backup his stuff 1st.
starche_old said:
BTW, to address that error he needs to format data. But backup his stuff 1st.
Click to expand...
Click to collapse
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)
MAX 404 said:
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)
Click to expand...
Click to collapse
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.
starche_old said:
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.
Click to expand...
Click to collapse
Hi
No really , as long as you dont use the data partition with TWRP is not necessary , check their thread , that step is no longer listed on the OP
1 In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2 Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
3 Extract Odin_3.12.3.zip to your computer.
4 Install Samsung Mobile Phone Drivers for Odin to find your device.
5 Download a .tar image of TWRP for herolte.
6 Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + v[Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
7 Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
8 Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
9 At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
10 If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
11 Go to [Reboot] -> [System].
12 Wait 2-5 minutes for your device to finish setting itself up
As i said in stock ROM , custom roms may vary
Regarding IMEI you are totally right if he does not have a EFS back up
Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.
starche_old said:
Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.
Click to expand...
Click to collapse
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.
As I SAID I can't flash stock firmware with odin, because of efs folder problem.... I already tried it.
I haven't got a rom installed on my s7 and I can't flash any, it'll not boot.
I gived it to a local shop.... I wait for his reply
darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
Try this guide to repair your efs.
Might be worth looking into re-partitioning here
If you can get into download mode, then there is always hope! Please excuse me if I missed any info, didn't read through the whole thread. Good luck! :good:
MAX 404 said:
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.
Click to expand...
Click to collapse
Agreed.
And sorry everyone for off-topic
@darkalez: Since you have TWRP, you can flash other ROMs without any problem. I guess there are .ZIP files with stock ROM, although that won't reflash the recovery.
Why do you want to flash stock? If it's just to use that ROM, then do so via TWRP. Else you are in loss.

[cofface] [3.1.1-0]Twrp recovery for Huawei Nova2

Hi guys,
I made the TWRP from TeamWin official sources for Huawei Nova2 . You can download the img and flash it from fastboot.
Bootloader unlocked required!
Installation:
Unlock bootloader (skip if you have already unlocked it)
Reboot into fastboot mode
Flash using
Code:
HTML:
fastboot flash recovery cofface_pic_al00_recovery_en.img
Reboot
Download:
AndroidFileHost
Bugs:
When device is encrypted you can't see the files into recovery
Let me know if there are others
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc:fingers-crossed:
PAYPAL DONATION LINK
email:[email protected]
Unfortunately It is not working!
After flashing your file there is still the Huawei EMUI Bootloader and no TWRP. Bootloader was unlocked before. Fastboot was working fine.
Any idea?
Problem with Google GAPPS
Hi,
Thank you for your tuto and your ROM
I have bought my nova 2 in china.
Do you know how to install GAPPS. I have tried different version (stock, pico,.. ) but it's no use.
Do you know if I have to change the region first ?
Is it ok with your ROM ?
Regards
Perfect
Perfect, thank you!
Not working
Hello,
TWRP ist not working for me, I still have the EMUI bootloader after flash and reboot.
Boot into TWRP Recovery ("fastboot boot cofface_pic_al00_recovery_en.img") is aborted with:
"FAILED (remote: Command not allowed)"
Is there anything I've done wrong?
Thx!
dr.luther.1517 said:
Perfect, thank you!
Click to expand...
Click to collapse
did it work with your Nova 2?
i have got a demo device ( from germany ). Can some one upload his OEM info for a normal device ?
And yeah... it works
Success
Works very well, Thanks !
But ... while playing with it I lost the stock ROM for my Huawei Nova 2.
Since there is no download source available, could anybody share a stock ROM backup so I could restore using Twrp ?
Thanks !
My Nova 2 (PIC-LX9C432) automatically encrypts the disk after the first run, and then TWRP is unable to read /data partition nor do nandroid backups as a result. Can someone guide on how to disable encryption or get TWRP to decrypt data.
I read elsewhere that newer versions of TWRP are able to decrypt if you set a password / screen lock.
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
jusma said:
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
Click to expand...
Click to collapse
Perhaps you could get some tips from nova (1) thread there we had the same problems. But so long we have a working twrp with backup possibility.
Hi, i used this Twrp, but did not notice the error mesaje when i "create" a back up for all my data, then when deleting some things, i went off the road and ended deleting the complete operative system, and know i dont seem to be able to find a room for my phone is a huawei p10selfie(in my country) or huawei nova 2 plus (in the rest of the world) model BAC-L03, sry if i dont use the correct words, since english is not my native lenguaje
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
iamramanlmc said:
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
Click to expand...
Click to collapse
Nova 2i is Mate 10 Lite! https://forum.xda-developers.com/ma...e--roms-kernels-recoveries--other-development
{
"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"
}

[Recovery][Official] TWRP 3.4.0-15 [T860/5][22.Jul.2020]

{
"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"
}
Official TWRP 3.4.0 for SM-T860 + SM-T865
Telegram thread
Built using OMNI source 9.0
TWRP v3.4.0
See post #2 for install steps
Changelog...
v1
Initial build
MTP, OTG and SDcard all working
Encryption not working, but being implemented later
* There is a kernel in the download folder for the T865, flashing this after booting into TWRP should give T865 full function.
v2
Added T865 support
Updated kernel to SI3
v3
Fixed img flashing
v5
Encryption support added
Fixed brightness function
v7
Now using a recovery_dtbo
v15
Updated to 3.4.0 twrp
Updated kernel and dtbo (TF2 Android 10 only)
TWRP Downloads
Download TWRP 3.4.0 folder T860
Download TWRP 3.4.0 folder T865
WETA Kernel
Telegram thread
Thanks to @geiti94 and @klabit87 for allowing me to constantly pick their brains
--------------------->
Beer fund
XDA:DevDB Information
Galaxy Tab S6 TWRP, Kernel for the Samsung Galaxy Tab S6
Contributors
Mentalmuso, mentalmuso
Source Code: [Kernel Source
Version Information
Status: Stable
Created 2019-09-30
Last Updated 2019-09-30
TWRP installation changed
Download folder.T860
Download folder.T865
WETA Kernel
* Unlock bootloader first
* Reboot recovery and reboot system now behave normally after flashing.
* No more patching in Magisk manager at all.
* Be aware, first clean boot, hangs on building cache, hard reboot after waiting about 3min and you'll boot past this
* If simply updating your existing TWRP, v9 upwards, you only need to flash the TWRP.img in recovery. No need to reflash kernel and Magisk.
Process from bone stock
1. Flash TWRP.tar in Odin
2. Reboot directly into TWRP
3. Format data, reboot recovery
4. Flash custom kernel (Android 10, this is optional)
5. Flash encryption disabler.
6. Unmount system, Flash Magisk 20.4
7. Reboot system
Process from existing TWRP
1. Flash TWRP.img to recovery
2. Reboot recovery
3. Flash Kernel zip
4. Unmount system and Flash Magisk zip
5. Reboot system
--->
WooHoo!..and THANKS! and WooHoo!
If anyone tries flashing this on the LTE device let me know if it works out fine, including booting into system and checking WiFi and everything works.
Go stuck at file analysis in Odin with my T865. Tried to download the TWRP.tar many times still got the same problem. Thanks anyway.
Sent from my SM-T865 using Tapatalk
sbluescab said:
Go stuck at file analysis in Odin with my T865. Tried to download the TWRP.tar many times still got the same problem. Thanks anyway.
Click to expand...
Click to collapse
This is quoted from a Google search.
"It's almost always the fact that you didn't have Odin up and running with all the info in ahead of time before you plug the tablet into the USB port"
I'll check the tar file when I get home, but i doubt it's the file. I could be wrong but...
Mentalmuso said:
This is quoted from a Google search.
"It's almost always the fact that you didn't have Odin up and running with all the info in ahead of time before you plug the tablet into the USB port"
I'll check the tar file when I get home, but i doubt it's the file. I could be wrong but...
Click to expand...
Click to collapse
I can flash firmware and root my T865 with Odin without any problem.
Sent from my SM-T865 using Tapatalk
My current stat. Rooted with Odin.
Sent from my SM-T865 using Tapatalk
sbluescab said:
My current stat. Rooted with Odin.
Click to expand...
Click to collapse
Ok I'll check the tar file later. You can try since you are already rooted, pulling the recovery.IMG out if the tar, and using dd to flash it in an terminal emulator if you're Keen.
Or create another recovery.tar using 7zip to flash in Odin.
It may be checking the device number and denying it
sbluescab said:
My current stat. Rooted with Odin.
Click to expand...
Click to collapse
Im uploading a different tar for you to try in Odin
Try this, it's recovery only, you will need to be pre rooted
https://nextcloud.justbeca.us/s/tDaTRQ5B5bkLpwB
https://nextcloud.justbeca.us/s/tDaTRQ5B5bkLpwB
Try this, you will need to be pre rooted, this tar doesn't include the boot.img or nulled vbmeta.img.
And I used a different tool to package the tar
Mentalmuso said:
https://nextcloud.justbeca.us/s/tDaTRQ5B5bkLpwB
Try this, you will need to be pre rooted, this tar doesn't include the boot.img or nulled vbmeta.img.
And I used a different tool to package the tar
Click to expand...
Click to collapse
Thanks. I will give it a try.
Sent from my SM-T865 using Tapatalk
Successful flash with Odin but I couldn't boot into TWRP. Stuck in this screen for about a minute then the tablet booted into the system.
Sent from my SM-T865 using Tapatalk
sbluescab said:
Successful flash with Odin but I couldn't boot into TWRP. Stuck in this screen for about a minute then the tablet booted into the system.
Click to expand...
Click to collapse
The whole time holding onto the vol up and bix button? If so I may need to supply a different kernel for the t865
sbluescab said:
Successful flash with Odin but I couldn't boot into TWRP. Stuck in this screen for about a minute then the tablet booted into the system.
Click to expand...
Click to collapse
Did it boot to a rooted system or stock?
If you could go into the telegram thread and we can chat about it in there, id like to get this sorted out for other users
Finally, I could boot into TWRP after using dd to flash it in an terminal emulator. After that I flash the encryption disabler and format data then I try to reboot into TWRP again but it did not. In stead it's booting in to the system now. Still stuck in Samsung logo now.
Sent from my SM-N975F using Tapatalk
The tablet is running fine now. Magisk is working right after the tablet booted. But it just can't boot into TWRP. Tried to reboot to recovery from Magisk and manually still not working. Seems to stuck about a minute or 2 at this screen everytime I reboot or try to boot into TWRP then it just boot straight to the system.
Sent from my SM-N975F using Tapatalk
sbluescab said:
Finally, I could boot into TWRP after using dd to flash it in an terminal emulator. After that I flash the encryption disabler and format data then I try to reboot into TWRP again but it did not. In stead it's booting in to the system now. Still stuck in Samsung logo now.
Click to expand...
Click to collapse
First clean boot, you need to hard reboot after 3min
sbluescab said:
The tablet is running fine now. Magisk is working right after the tablet booted. But it just can't boot into TWRP. Tried to reboot to recovery from Magisk and manually still not working. Seems to stuck about a minute or 2 at this screen everytime I reboot or try to boot into TWRP then it just boot straight to the system.
Click to expand...
Click to collapse
You can't boot to recovery from magisk. It won't work.
You need to manually reboot to recovery.
Hold down vol up and bix button until the splash screen, then let go and reapply the buttons again quickly, while the red writing is present. Keep holding them. That is how I get to recovery.
But they're may be more going on seeing as though you got a t865
sbluescab said:
Finally, I could boot into TWRP after using dd to flash it in an terminal emulator. After that I flash the encryption disabler and format data then I try to reboot into TWRP again but it did not. In stead it's booting in to the system now. Still stuck in Samsung logo now.
Click to expand...
Click to collapse
Seems like that tar file was screwed up somehow. It wouldnt flash formme either, I've repackaged it and now it does. And I boot into recovery no issues.
Are you still having trouble getting into recovery?

[RECOVERY][3.4.0-0][doha]Unofficial TWRP recovery for Moto G8 Plus (Testing)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decrypt works
- Removed TWRP app
- Backup still have some problems use it carefully
- Fastboot boot works
- Touch works
- Vibration works
- Rom Flashing
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Other Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
{
"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"
}
8. Choose the recoveryimgfilename.img
9. Swipe to install
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.4.0-0 Unofficial by mauronofrio
TWRP 3.4.0-0 Unofficial Installer by mauronofrio
TWRP 3.3.1-23 Unofficial by mauronofrio
TWRP 3.3.1-23 Unofficial Installer by mauronofrio
TWRP 3.3.1-19 Unofficial by mauronofrio
TWRP 3.3.1-19 Unofficial Installer by mauronofrio
TWRP 3.3.1-17 Unofficial by mauronofrio
TWRP 3.3.1-17 Unofficial Installer by mauronofrio
TWRP 3.3.1-16 Unofficial by mauronofrio
TWRP 3.3.1-16 Unofficial Installer by mauronofrio
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_motorola_doha
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
Thanks to @ath0 for hard testing
Thanks to vache for the help with touch fix
Thanks to @Electimon for some tips
Created 2020-02-27
TWRP 3.3.1-17 Motorola Moto G8 Plus (doha) by mauronofrio:
- Fixed touch for focaltech panels.
TWRP 3.3.1-17 Unofficial by mauronofrio
TWRP 3.3.1-17 Unofficial Installer by mauronofrio
Rom updates
TWRP 3.3.1-19 Motorola Moto G8 Plus (doha) by mauronofrio:
- Fixed Rom flashing;
- Partially fixed format data.
TWRP 3.3.1-19 Unofficial by mauronofrio
TWRP 3.3.1-19 Unofficial Installer by mauronofrio
sorry for my bad English..
so... if I want to stay in the stock rom and install TWRP, the only way is to root with magisk?
and after that the stock ROM rooted with magisk will be stable to daily use?
Hello thanks for the TWRP recovery port. It works great!
Now, a few days after I flashed it. Motorola pushed a firmware or security update . I didn't install it yet but I would like to. I think I have to go back to stock recovery in order to install the update. Might you have a guide on how to do this? I already have the stock rom downloaded but I don't know how to get the stock recovery
When flashing the installer or using the "Install Recovery Ramdisk" method, the touchscreen won't work
Hello,
I've got a Moto G8 Plus which I rooted using Magisk after unlocking the bootloader. It works just fine as it is, but I would like to install TWRP so I can have a backup of it. However, I'm afraid of installing TWRP and breaking something or losing the root.
Can I flash this version of TWRP over a Moto G8 Plus already rooted with Magisk without losing root or breaking Magisk or something else?
irex102 said:
Hello thanks for the TWRP recovery port. It works great!
Now, a few days after I flashed it. Motorola pushed a firmware or security update . I didn't install it yet but I would like to. I think I have to go back to stock recovery in order to install the update. Might you have a guide on how to do this? I already have the stock rom downloaded but I don't know how to get the stock recovery
Click to expand...
Click to collapse
That is just a security update let it be it will **** things up trust me
Hi there,
Thanks for your efforts puling together a TWRP for our phones!
I've got a question because I'm not quite clear about your response to the previous question about the security update. I've been using the stock recovery, rooted with Magisk and went through the whole process of accepting the security update and then re-rooted etc.
Will I wind up F'ing up my phone if I go to install your TWRP since I've already accepted the security update? Or would I be better off just compiling TWRP on my own ( it'll be my first foray into that area ) taking that route instead?
Any and all opinions welcome
Hamaruka said:
When flashing the installer or using the "Install Recovery Ramdisk" method, the touchscreen won't work
Click to expand...
Click to collapse
Same issue here. Works only when I fastboot boot off my laptop.
did not work for my phone, Moto G8 Power purchased 4/17/2020 fully unlocked bootloader, no root, attempted to boot to img, failed to boot.
[email protected]
sorry im doing a lot of research and looking, i basically accidentally soft bricked my phone, my wife and i have the exact same phone, and i cant seem to pull the factory images from it, nor can i make the various versions of OEM recovery images or boot loaders function on the phone.
maybe im just doing something wrong. pardon the typos.
FoxDroid1214 said:
did not work for my phone, Moto G8 Power purchased 4/17/2020 fully unlocked bootloader, no root, attempted to boot to img, failed to boot.
[email protected]
sorry im doing a lot of research and looking, i basically accidentally soft bricked my phone, my wife and i have the exact same phone, and i cant seem to pull the factory images from it, nor can i make the various versions of OEM recovery images or boot loaders function on the phone.
maybe im just doing something wrong. pardon the typos.
Click to expand...
Click to collapse
I have played a little with Moto G8 Plus (XT2019-1). And i'm not worried about brick it. Have done a few times, but always recovered with blankflash.. After blankflash it will start bootloader, and then i can flash stock firmware. I found Stock FW and also blankflash on lolinet. I prefer using Fastboot for flashing. Don't need TWRP for flashing. Have locked, and Unlocked bootloader many times..
If needed, i can make a description on how to use blankflash as it can be hard to get started..
Check lolinet for stock FW and blankflash.. You need to know code name for your phone..
mirrors.lolinet.com/firmware/moto/
can i flash latest magisk straight through twrp? or does it have to be the patch boot process?
Allright, I installed successfully TWRP (install to ramdisk) and Magisk, rooted phone is fine etc, but when I boot into recovery again touch does not work and I am stuck in bootloop into recovery until I flash both again. Any hints?
hendrack said:
Allright, I installed successfully TWRP (install to ramdisk) and Magisk, rooted phone is fine etc, but when I boot into recovery again touch does not work and I am stuck in bootloop into recovery until I flash both again. Any hints?
Click to expand...
Click to collapse
Seems a common bug, i need someone with which test this thing
What would testing imply?
My guess would be: flashing experimental twrp, praying it doesn't brick your phone, reading logs?
mauronofrio said:
Seems a common bug, i need someone with which test this thing
Click to expand...
Click to collapse
The same error any solution?
I could help by flashing the recoverys and submitting the logs but beyond that I'm helpless

[SOLVED] Poco X3 NFC - Bootloop after Wiping & Flashing Custom ROM

Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you
DrakMC said:
Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you
Click to expand...
Click to collapse
You didn't explain your Problem quite well. Does it reboot to fastboot or does it reboot to system? (aka a Bootloop). if it reboots to system, here's what to do:
Boot into a custom recovery (twrp/Orangefox) and flash the required recovery MIUI ROM mentioned in your custom ROM's thread instructions.
Flash the custom ROM/Gapps, followed by Formatting /data using the Advanced Options in the wipe menu.
Reboot.
If you can't find the format option (which is mandatory before a new boot of a custom ROM), you can use this command while in fastboot mode:
Code:
fastboot erase userdata
Formatting /data is required for Encrypted devices to reset the encryption key and avoid a Bootloop. Please refer to this thread for more Custom ROM flashing instructions. If all else fails, you could EDL flash your device through MI flash tool/Command line, this process costs money (you need an Authorized Xiaomi Account) to complete.
Thank you very much for your help!
Slim K said:
Does it reboot to fastboot or does it reboot to system? (aka a Bootloop).
Click to expand...
Click to collapse
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)
DrakMC said:
Thank you very much for your help!
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)
Click to expand...
Click to collapse
Again, when I say FORMAT, I meant formatting by typing ”yes".
Also, you haven't looked at the ArrowOS thread close enough, see:
{
"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"
}
It says latest R firmware, basically V12.0.7.0.RJGEUXM. Another point I mentioned is the fact that a recovery MIUI is flashable through TWRP/Orangefox and not Fastboot/Mi flash tool, It comes in a .zip archive.
Regarding returning to stock, have you tried booting into stock recovery after fastboot flash and factory resetting? That could work.
Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
I'm using TWRP 3.5.2_10-1-surya.
DrakMC said:
Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
View attachment 5307411
I'm using TWRP 3.5.2_10-1-surya.
Click to expand...
Click to collapse
Error 1 just means a mismatch between the underlying stock and the newly flashed ROM, just ignore it and flash ArrowOS, Format data and reboot. If it still doesn't work, then return to stock through fastboot. (I never encountered so many problems as you did)
I followed your instructions. When I turn on smartphone, the Poco logo is displayed, then the ArrowOS animation will appear and freezes. After a while, the mobile phone restarts and this is repeated over and over again. (If I flash MIUI using the Mi Flash Tool, I also have a bootloop.)
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!
sevachcomunist4 said:
just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!
Click to expand...
Click to collapse
You're welcome! I'm glad I could help someone! It took me about 40+ hours to resolve this issue before trying all possible methods.
DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
please give me link
DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.
DP FH said:
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.
Click to expand...
Click to collapse
You are welcome. I'm glad I could help someone.
I was whole week without the phone until I've fixed it. It took me over 40 hours to fix the issue.

Categories

Resources