{
"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"
}
Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
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, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
BUGS:
You tell me.
FLASHING INSTRUCTIONS:
fastboot erase recovery
fastboot flash recovery twrp-3.x.x-x-togari.img
Click to expand...
Click to collapse
Changelogs:
2022/12/13
Updated to TWRP 3.7.0.
2021/10/03
Fixed SONY boot logo.
2021/09/24
Fixed touch issues.
Click to expand...
Click to collapse
CREDITS:
@ 115ek on Github for his amami base trees.
SOURCE CODE:
device-tree: LINK
DOWNLOADS:
DOWNLOAD
On C6802 3g model, There is no recovery partition. Only boot and FOTAkernel partitions. So I got boot into this recovery by "fastboot boot twrp-3.5.2_9-0-togari.img". Touchscreen not works. Seems adb working but have no idea what should I do.
Bikkoism said:
On C6802 3g model, There is no recovery partition. Only boot and FOTAkernel partitions. So I got boot into this recovery by "fastboot boot twrp-3.5.2_9-0-togari.img". Touchscreen not works. Seems adb working but have no idea what should I do.
Click to expand...
Click to collapse
Thanks for reporting, but since i don't have this device in hand so i can't really debugging with the touch issues, can you grab dmesg from adb for me?
tarkzim said:
Thanks for reporting, but since i don't have this device in hand so i can't really debugging with the touch issues, can you grab dmesg from adb for me?
Click to expand...
Click to collapse
Something more serious problem is going here. After boot into your twrp once, and then reboot to system by adb reboot, My device stuck at bootloop. At last, after factory reset(Originally installed bootstrap recovery), my device got blackscreen bricked. I need to handle this problem first.
Edit: My device can not boot into system now but I could managed get into your twrp again. So I attached dmesg file. https://www.mediafire.com/file/tassxmx7fac9qwm/dmesg.txt/file
Bikkoism said:
Something more serious problem is going here. After boot into your twrp once, and then reboot to system by adb reboot, My device stuck at bootloop. At last, after factory reset(Originally installed bootstrap recovery), my device got blackscreen bricked. I need to handle this problem first.
Click to expand...
Click to collapse
Damn it... sound not good bro,
I found a scripts in XDA for fixing touch issues, maybe i can integrate it into my TWRP...
Bikkoism said:
Edit: My device can not boot into system now but I could managed get into your twrp again. So I attached dmesg file. https://www.mediafire.com/file/tassxmx7fac9qwm/dmesg.txt/file
Click to expand...
Click to collapse
Thanks for your dmesg logs, it seems like the driver was loading fine, i will see what i can do.
BTW, for your current ROM, maybe you should try to flash the boot.img of it again?
tarkzim said:
Thanks for your dmesg logs, it seems like the driver was loading fine, i will see what i can do.
BTW, for your current ROM, maybe you should try to flash the boot.img of it again?
Click to expand...
Click to collapse
I flashed stock 14.6.A.1.236 customized US to unbrick. Fortunately It revived.
If you mean that I should flash your twrp on boot partition, It also not fix touchscreen issue. Here is the log when your twrp actually flashed on the device.
Bikkoism said:
I flashed stock 14.6.A.1.236 customized US to unbrick. Fortunately It revived.
If you mean that I should flash your twrp on boot partition, It also not fix touchscreen issue. Here is the log when your twrp actually flashed on the device.
Click to expand...
Click to collapse
Oh that's not what i mean, but glad you unbricked it.
I will try to include a fix for touchscreen and upload it again, thanks.
New build released - 2021/09/24
Fixed touch issues.
New build released - 2021/10/03
Fixed SONY boot logo.
on my device C6833 is replaced LCD screen. try flash your recovery and system but touch not works. on stock rom 5.1.1 touch works. Its posible get working touch screen on device with replaced screen?
thanks
kluknawa235 said:
on my device C6833 is replaced LCD screen. try flash your recovery and system but touch not works. on stock rom 5.1.1 touch works. Its posible get working touch screen on device with replaced screen?
thanks
Click to expand...
Click to collapse
Actually all supported touch screen firmwares were already included in both of my recovery and ROM, and those are extracted from STOCK ROMs, so it shouldn't happen...
Do you have your C6833 stock rom backup file that i can take a look?
tarkzim said:
Actually all supported touch screen firmwares were already included in both of my recovery and ROM, and those are extracted from STOCK ROMs, so it shouldn't happen...
Do you have your C6833 stock rom backup file that i can take a look?
Click to expand...
Click to collapse
HERE is twrp backup stock rom. I use hot boot kernel with twrp 2.7.0.0. this recovery works good. on my device.
firmware version is 14.6.A.1.236_R2D android 5.1.1. all is included in mega folder.
Another twrp 3.0.0.0 and android 7.1.2 roms work for first time. but if screen is turn off and then i turn on touch not work. or if device is rebooted. I must completly turn off device and then turn on. thed touch works.
after replace device screen now works only stock rom
kluknawa235 said:
HERE is twrp backup stock rom. I use hot boot kernel with twrp 2.7.0.0. this recovery works good. on my device.
firmware version is 14.6.A.1.236_R2D android 5.1.1. all is included in mega folder.
Another twrp 3.0.0.0 and android 7.1.2 roms work for first time. but if screen is turn off and then i turn on touch not work. or if device is rebooted. I must completly turn off device and then turn on. thed touch works.
after replace device screen now works only stock rom
Click to expand...
Click to collapse
Can you try this TWRP image? (See attachment)
i try but touch not work. only OTG
kluknawa235 said:
i try but touch not work. only OTG
Click to expand...
Click to collapse
Try this one instead.
tarkzim said:
Try this one instead.
Click to expand...
Click to collapse
Same. As older recocery. Not works
kluknawa235 said:
Same. As older recocery. Not works
Click to expand...
Click to collapse
Well, I have no idea then...
Because I've already included the firmware update scripts from stock with stock binaries.
Can't help with your replaced touch panel for now, sorry.
Its ok. Thanks for your time
I just restored my XZU from a soft brick. Does the touch screen work with this version of TWRP?
Related
Unofficial TWRP Recovery for LG Optimus L9.
{
"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"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Use Flashify / Rashr from the PlayStore to flash.
Screenshots::
Download links:
- P60/P765/P768:
twrp-3.0.2-0-p760.img
- P769:
twrp-3.0.2-0-p769.img
XDA:DevDB Information
TWRP 3.0 for LG Optimus L9, Tool/Utility for the LG Optimus L9 P760, P765, P768
Contributors
EdwinMoq
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2016-04-08
Last Updated 2016-04-08
Ohhh my God!!!!!! i can't believe it!!!! Man you are the master.
Really Really thanks for your great works!
Tested,and works perfect!!!
yeah dude awesome :* thanx it"s work great i test it now !!!
Great. This time I was using Rashr instead of Flashify. Can reboot to recovery without problems.
But I haven't got the cojones so far to check, whether the Power-Volume-Menu combo will brick the phone, as happening with the previous version. I will only get to know once the next build of CM13 arrives, and that again won't even work good enough to let me boot into recovery to restore the nandroid...
Can't access my exFAT formatted SD card. How do I fix it?
Casserole said:
Can't access my exFAT formatted SD card. How do I fix it?
Click to expand...
Click to collapse
Huh? I should be able to access any file system. Can you get the recovery.log by getting to Advanced --> Copy log and post it here?
Thank you for this gift but i want to install pa 4.4.4 and it display error 7. How can i resolve? thanks
satiryco said:
Thank you for this gift but i want to install pa 4.4.4 and it display error 7. How can i resolve? thanks
Click to expand...
Click to collapse
Check that the rom You're installing is made is made for your phone. The error 7 usually means that the user is trying to install on an incompatible device.
lecorbusier said:
But I haven't got the cojones so far to check, whether the Power-Volume-Menu combo will brick the phone, as happening with the previous version.
Click to expand...
Click to collapse
I didn't know that issue before today (yep, I bricked my phone). After fixing it and doing software reboots (through adb) I got everything working. Everything else is working perfectly. Thanks, Edwin. Got your TWRP 3.0.2 and CM13 running by now.
So is it even possible to flash back to stock after installing this?
bulletfreak said:
So is it even possible to flash back to stock after installing this?
Click to expand...
Click to collapse
Can't you flash stock using LGFlashTool? I don't see how to twrp would prevent you from doing so.
bulletfreak said:
So is it even possible to flash back to stock after installing this?
Click to expand...
Click to collapse
Yes... if before you do a rom (stock) backup with twrp
I was able to get to TWRP 3.0.2.0 at boot several times, unlike Twrp 2.8.
However, I got a rather serious brick later, with the P760 restarting every 3 seconds, and no access to TWRP and Fastboot. After unbricking, D/L mode still worked, and installing Twrp anew, I haven't tried that again, always rebooting into recovery.
For the Fastboot problem under Win8.1 and 10 it may help to deactivate all powersave settings for usb hubs and host controllers. I haven't tried that yet.
If TWRP's boot screen won't disappear, hit power twice, and you're in TWRPs lockscreen.
I have just rooted my Galaxy Note 2014, which has an official TWRP 3.0.2. I can tell that that one has more issues than this,despite being official.
Can i ask, please, if i want to switch from cwm to twrp, could o just flash this img? I want to flash your marsh rom afterwards
Thanks in advance
Sent from my LG-P760 using Tapatalk
besnaglista said:
Can i ask, please, if i want to switch from cwm to twrp, could o just flash this img? I want to flash your marsh rom afterwards
Thanks in advance
Sent from my LG-P760 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the img with Flashify or similar.
If Flashify don't work, install Rashr and reboot, for safety. For some people Fastboot don't work, so the option to flash via PC don't exist. This incurs extra circumstances, if something goes wrong.
I had an old version of twrp on my P760. To flash new one I replaced the old one in flashable zip with this new one, then flashed it on twrp like installing a rom. It successfully flashed. I'm sharing the flashable twrp 3.0.2-0 zip file if it helps. It should aslo work on P765 and P768. https://mega.nz/#!LAggTZbR!58cGt1xxGtIXo_AOSXf4w1RNHTm1I4WgTGDQBuq4Vts
Big thanks to @EdwinMoq
I have reverted to stock weeks ago, to use the phone as a mobile AP with a data SIM. So far, probably because of missing SIM, 5ghz wifi and gps don't work. The dead sensors in CM12/13 came back to life.
As Fastboot don't work with L9 & Win10, i had to root using Kingo Root. I don't like the Kingo superuser tool. Days ago, for the second time, the phone bricked while trying to install SuperSu. It's still in that state.
I was using Edwin's TWRP, which worked fine with CM12 & 13. The older Twrp from Artas had the habit to brick the phone while trying to access it at boot. Rebooting from Android to Twrp was no problem, however. If you go further back in time, there was only CWM. I was using CWM along with stock years ago, seems i have to get it again.
Boot to Recovery?
EdwinMoq said:
Yes, just flash the img with Flashify or similar.
Click to expand...
Click to collapse
How to acces with power offe device? Power+ Vol- combination does not work and I have to access using Advanced Reboot
{
"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"
}
Introduction
Hi to all dear Z3 users. This is my first TWRP build, I used omni minimal TWRP source and kernel from Sony git.
I hope you enjoy this.
How to install
Fist of all you MUST flash lastest 23.5.A.1.291 firmware with FlashTool at least one time, for upgrade the bootloader (You need this upgrade for boot on recovery).
Via fastboot
Reboot your phone on fastboot mode.
Flash recovery using this command:
Code:
fastboot flash FOTAKernel <filename>
Via zip (You need a working recovery installed)
Download the zip and put it on your internal or external memory.
Reboot to recovery.
Flash the zip.
Via Official TWRP App (You need root)
Install the app from Google Play Store and download the zip.
Extract recovery.img and copy it to your internal or external memory.
Open the app, give root permissions and tap on TWRP FLASH.
Tap on Select a file to flash...
Select the recovery.img and flash it.
Download
TWRP
Thanks to
@GreyLeshy a lot of thanks for this great dev, he helped me a lot for make this possible, build this recovery and he had a lot of patience with this noob dev.
@Dees_Troy for TWRP.
@omni Team for TWRP Minimal Source.
XDA:DevDB Information
TWRP for leo, Tool/Utility for the Sony Xperia Z3
Contributors
ShadowElite, GreyLeshy
Source Code: https://github.com/ShadowElite117/android_sony_shinano_twrp
Version Information
Status: Stable
Created 2018-09-01
Last Updated 2018-09-01
FAQs
Q. How boot on recovery?
A. With the device turned off, press power and vol- at same time until it vibrates.
Q. Does it works with Z3 dual sim?
A. It should work, since Z3 and Z3 dual sim are like 99% the same device, but is not tested (yet) so you Z3 dual users have to test it and report.
Q. Does it works with stock or custom ROMs?
A. At this momment I know that it is fully compatible with stock ROMs (or stock based ROMs) but at this momment is not tested with custom ROMs, so you users have to test it and report.
Thank you so much for the latest TWRP for our device. I use it with official CarbonROM from
https://forum.xda-developers.com/z3/orig-development/8-1-x-carbonrom-cr-6-1-t3771546
and it works like a charm. The only recovery I could find, which enables full-featured OTA updates and installation of ROM and GApps without up- and downgrade cycle.
Keep up the good work
Jo
Thanks for your work bro
I noticed after using this recovery on Z3 dual that when I flash a custom rom, baseband version and imei codes disappear
ShadowElite said:
FAQs
Q. Does it works with stock or custom ROMs?
A. At this momment I know that it is fully compatible with stock ROMs (or stock based ROMs) but at this momment is not tested with custom ROMs, so you users have to test it and report.
Click to expand...
Click to collapse
Yes, this work on custom rom.
- D6603 with latest CARBON Rom.:good:
Openrecoveryscript issue
@ShadowElite the recovery not execute "openrecoveryscript"
D6603, CARBON CR 6.1
please question friend, and thanks.. i flash recovery.img with flashtools? this is kernel? because is zip, my phone xperia z3 android 6.0.1 and .291 thanks
danilo_scala said:
please question friend, and thanks.. i flash recovery.img with flashtools? this is kernel? because is zip, my phone xperia z3 android 6.0.1 and .291 thanks
Click to expand...
Click to collapse
This is custom recovery please read OP carefully, already clearly. If you still didn't got the point, please stay away because can brick your phone
Hi,
every time i enter recovery i have to setup time (not working), language...
Anyone?
gsausalito said:
Hi,
every time i enter recovery i have to setup time (not working), language...
Anyone?
Click to expand...
Click to collapse
Can you mount data partition? If not, then you coud try to format data.
@ShadowElite so its a recovery for Android 6 Mashmallow compatible with higher Android versions? amazing. EDIT: doesn't boot up.
Hi. Thanks for your work.
I installed this TWRP on my Sony Xperia Z3 (D6603) running Marshmallow 6.0.1 (23.5.A.1.291) and it only booted in recovery mode. Then i installed OMNI ROM (7.1.2) and since then it only boots into system. Is there any way to boot recovery mode and also have the system working? Anything to flash? Thank you in advance.
This recovery is compatible with carbon, but with omni results with sim not being detected for me.
This recovery working on d6633????
At first... my English is not good. SRY.
LOOK..
my TWRP is 3.0.2-0. (on 23.5.A.1.291)
I attempted to install TWRP_3.2.3-0 with TWRP is 3.0.2-0. It was successful
but, after reboot phone and back too TWRP, No change! my TWRP version still 3.0.2-0!!!
What to do???
I can not update from TWRP 2.8.0.1 to 3.x.x.x. ,please help...
Technoolli said:
I can not update from TWRP 2.8.0.1 to 3.x.x.x. ,please help...
Click to expand...
Click to collapse
Turn your phone off. Then, hold its volume up button whilst connecting it to the computer through an USB cable, until you notice its led lighten up in blue color. Let's suppose your TWRP image file is named recovery.img. Then, in a terminal command window, enter:
fastboot flash FOTAKernel recovery.img
Replace recovery.img by the actual name of your TWRP image file. And everything else is case sensitive. If you have a Windows computer and don't have the fastboot command yet, search xda for 'Minimal adb & fastboot'.
To enter TWRP after flashing it, starting with your phone turned off, hold both the power and volume down buttons. When your phone vibrates (as if it was being turned on), release the power button. Some seconds later, release the volume down button.
Sent from my Xperia Z5 Compact using XDA Labs
casouzaj said:
Turn your phone off. Then, hold its volume up button whilst connecting it to the computer through an USB cable, until you notice its led lighten up in blue color. Let's suppose your TWRP image file is named recovery.img. Then, in a terminal command window, enter:
fastboot flash FOTAKernel recovery.img
Replace recovery.img by the actual name of your TWRP image file. And everything else is case sensitive. If you have a Windows computer and don't have the fastboot command yet, search xda for 'Minimal adb & fastboot'.
To enter TWRP after flashing it, starting with your phone turned off, hold both the power and volume down buttons. When your phone vibrates (as if it was being turned on), release the power button. Some seconds later, release the volume down button.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
I wanted to install the following recovery as follows: fastboot flash FOTAKernel twrp-3.3.1-z3-20200212.img but after restarting I'm still on the old version 2.8.0.1
I can update to version 3.2.3.-2 twrp_z3_2019-03-13.img but not to the latest ...
Technoolli said:
I wanted to install the following recovery as follows: fastboot flash FOTAKernel twrp-3.3.1-z3-20200212.img but after restarting I'm still on the old version 2.8.0.1
I can update to version 3.2.3.-2 twrp_z3_2019-03-13.img but not to the latest ...
Click to expand...
Click to collapse
Install new version
Power off
Hold power+volume up
Release power after vibration
3dguru said:
Install new version
Power off
Hold power+volume up
Release power after vibration
Click to expand...
Click to collapse
Then I'm back to the old version, how do I get the new version ... Need it to switch to Android 10 ... Thank you
{
"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"
}
Code:
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.
WORKING:
Decryption userdata with eu roms
Screen brightness settings
Correct screenshot color
MTP
ADB
Vibration
Sideload
To flash the TwrpDownload the recovery and copy to adb folder
Open terminal
Code:
fastboot flash recovery nameofrecovery.img
fastboot boot nameofrecovery.img
or
fastboot reboot with vol + to boot
Source Codehttps://github.com/geoanto555/android_device_xiaomi_gauguin
https://github.com/TeamWin/android_bootable_recovery
Prebuilt Stock Kernel
Thanks to TeamWin Recovery Project
all testers and developers
Thanks to Μιχάλης (chariPower) for the information(sideload)
Download Link-stwrp_gauguin_3.5.A10_05-01-2021
twrp_gauguin_3.5.A10_07-02-2021 fixed sideload and mtp
twrp_gauguin_3.5.A10_18-02-2021 fixed backup data error 255 (/data/extm)
twrp_gauguin_3.5.A10_05-03-2021 Fixed Mtp after format data & reboot recovery. (if the MTP does not open, try reboot in twrp again)
twrp_gauguin_3.5.1.A10_30-03-2021 fixed fastbootd
it’s first time i am using xiaomi phone. my device is RMN9P5G and waiting for unlocked. can i flash your recovery and install the latest stable EU rom in mifirm.net: V12.0.8.0.QJSCNXM immediately after unlock success？i’m worry a bit because some members report that internal, user data be encrypted and cannot access..
kien_vip said:
it’s first time i am using xiaomi phone. my device is RMN9P5G and waiting for unlocked. can i flash your recovery and install the latest stable EU rom in mifirm.net: V12.0.8.0.QJSCNXM immediately after unlock success？i’m worry a bit because some members report that internal, user data be encrypted and cannot access..
Click to expand...
Click to collapse
From my experience, the recovery cannot decrypt the stock ROMs, you have to flash a custom ROM (Arrow and Lineage are the only 2 right now), or flash a xiaomi EU ROM.
Copy the rom to sdcard or usb otg.
Format data
Reboot recovery
Flash rom.
With xiaomi eu decryption works...
Decryption on stock rom works if I hotboot TWRP (fastboot boot twrp.img). If I flash it, TWRP doesn't prompt me for a password when started and keeps data encrypted.
Hi there, thank you for the TWRP. Is there any chance to decrypt also user 999 for the Dual apps on the .eu ROMs?
not for now. I will upload new version soon
ilyachelsea said:
Is there any chance to decrypt also user 999 for the Dual apps on the .eu ROMs?
Click to expand...
Click to collapse
twrp_gauguin_MI10TL-RN9P5G_MI10I_3.5.A10_18-02-2021_BL-L
Fixed backup userdata (error 255 for data/extm)
User 999 can be decrypted only with default password ( without pattern-pin-pass) for now.
Thank you, but my password is PIN, anyway the recent twrp can't decrypt user 999. It is the message in red: "Failed decrypt user 999"
Only without pin,pass,pattern can be decrypted user999
It's a pity. I intend to back up also user 999 to keep my dual banking apps with the access data. If I first remove the PIN, and backup user 999 with the TWRP, after restore I will have to set up access again. This kills the benefit of the decryption and makes backup of 999 useless.
Thank you anyway and I hope, NO PIN is the temporary requirement of this version.
Hello everybody! Last week I unlocked the bootloader of my gauguin and initially I tried the official TWRP Recovery released by TWRP official page but it didn't work correctly and I couldn't flash zips, so I tried this beta version released by geoanto555 and it worked smoothly, I flashed zips and I had root permissions... But last night the smartphone had the battery low and it turned off, when I connected it to the charger it automatically reboot in fastboot and I can only enter in recovery mode. Sorry but I'm new in the modding world and I don't know what to do.. First brick.. What I did wrong? Anybody can help me? Is there anything I can do or I have to buy a new phone? Thanks to who will answer . Good evening.
devedel said:
Hello everybody! Last week I unlocked the bootloader of my gauguin and initially I tried the official TWRP Recovery released by TWRP official page but it didn't work correctly and I couldn't flash zips, so I tried this beta version released by geoanto555 and it worked smoothly, I flashed zips and I had root permissions... But last night the smartphone had the battery low and it turned off, when I connected it to the charger it automatically reboot in fastboot and I can only enter in recovery mode. Sorry but I'm new in the modding world and I don't know what to do.. First brick.. What I did wrong? Anybody can help me? Is there anything I can do or I have to buy a new phone? Thanks to who will answer . Good evening.
Click to expand...
Click to collapse
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
AnibalSP said:
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
Click to expand...
Click to collapse
In my device the rom is still the original. Do I have to do it anyway? What can happen if I try to flash a custom rom? If I only do the factory reset will I lose also TWRP?
AnibalSP said:
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
Click to expand...
Click to collapse
I'm trying to do this with XiaoMiTool v2.. Thanks
devedel said:
In my device the rom is still the original. Do I have to do it anyway? What can happen if I try to flash a custom rom? If I only do the factory reset will I lose also TWRP?
Click to expand...
Click to collapse
If you can boot to android, or boot to TWRP / Orangefox, you don't need to flash again miui stock
If you flash a second rom, the worst thing that can happen, is that the rom may not work, but you wipe the internal memory (dalvik cache and data) and it should be running again
If you loose twrp for some reason, you can flash it again with xiaomitoolv2, or with fastboot
I'd recommend to you to try rooting, installing roms and similars things in an old phone if you don't are confident / know what are you doing, you will learn a lot in a few days of tinkering.
Anyone know what I need? I can't finish the installation of a official xiaomi rom to unbrick my device
devedel said:
View attachment 5257349
Anyone know what I need? I can't finish the installation of a official xiaomi rom to unbrick my device
Click to expand...
Click to collapse
Hi,
Download the official stock rom
Dont use XiaoMiToolV2, instead use MiFlash (official tool). Works for me every time. Then connect your phone in fastboot and flash all, I use the clean all and lock option which relocks my bootloader but you could just clean all and leave the bootloader unlocked. Then you can start again
fizzy900 said:
Hi,
Download the official stock rom
Dont use XiaoMiToolV2, instead use MiFlash (official tool). Works for me every time. Then connect your phone in fastboot and flash all, I use the clean all and lock option which relocks my bootloader but you could just clean all and leave the bootloader unlocked. Then you can start again
Click to expand...
Click to collapse
Hi, thanks for your advice.
Do you think it can works if usb debugging is off? I'm afraid I've disabled it the night the phone bricked.
I did wrong too many things but was my first try, tomorrow I'll buy a new Mi 10t lite and I'll try again, using more precautions.
Thank you all anyway, good evening.
devedel said:
Hi, thanks for your advice.
Do you think it can works if usb debugging is off? I'm afraid I've disabled it the night the phone bricked.
I did wrong too many things but was my first try, tomorrow I'll buy a new Mi 10t lite and I'll try again, using more precautions.
Thank you all anyway, good evening.
Click to expand...
Click to collapse
Enabled debugging is needed for adb when the system is running. For fastboot it does not matter.
{
"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.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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 me for messing up your device, I will laugh at you.
Odin
- Odin3 v3.10.5
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 8.0
How to flash TWRP with Odin
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down and Home simultaneously. When the warning screen appears, release all buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP".
3. Disable auto reboot in Odin and press start.
4. You can then boot directly into TWRP by pressing the Power, Home and Volume Up simultaneously. Release all buttons as soon as you see the boot screen ("Samsung Galaxy Note 8.0").
How to flash TWRP within a previous version of TWRP
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all buttons when the boot screen appears ("Samsung Galaxy Note 8.0").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Bugs
- You tell me!
Credits
TWRP Team and all people who worked / are working on the exynos 4 devices.
Sources
- n5100 repository
- n5110 repository
- n5120 repository
- TWRP repository
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my spare time and every donation keeps me motivated.
donate
XDA: DevDB Information
TWRP 3.6.0_9-X, ROM for the Samsung Galaxy Note 8.0
Contributors
@html6405
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-03-14
Created 2021-02-21
Last Updated 2021-10-12
is the file corrupted? it's only 7KB instead of 7MB
begucu said:
is the file corrupted? it's only 7KB instead of 7MB
Click to expand...
Click to collapse
Hi, which file did you try?
They are all about 7.2MB, if you downloaded it with your device, check if it didn't downloaded the html page instead (I've seen this many times)
html6405 said:
Hi, which file did you try?
They are all about 7.2MB, if you downloaded it with your device, check if it didn't downloaded the html page instead (I've seen this many times)
Click to expand...
Click to collapse
I tried to download
Code:
https://dl.twrp.me/n5100/twrp-3.5.0_9-0-n5100.img
And as you said, I only got the html file
I'm using Google Chrome with Internet Download Manager.
It took a couple times to download the 7MB file
TWRP 3.5.1_9-0 is now ready to download , if you should find any bugs, let me know.
Does anyone know anyone who wants to sell his GT-N5120? Thanks
TWRP 3.5.2_9-0 builds are up, I've readded some file systems.
Can anyone access an encrypted data partition from TWRP?
I tested TWRP 3.3.1, 3.5.0_9, 3.5.1_9, 3.5.2_9-0 and 3.5.2_9-1 on my n5110, and no version asks me for the password, and the mounting process fails.
I encrypted the device shortly after @html6405 added support for it in his LineageOS 16 ROM. I selected "resize partition" in TWRP for the data partition, then the encryption succeeded in LineageOS. Since then, TWRP fails to access the data partition.
I attach recovery.log. This is from TWRP 3.5.2_9-1.
The most interesting line is probably
Code:
E:Unexpected value for crypto key location
Is my data partition messed up (although Lineage functions correctly), or has TWRP a problem with encryption, which @html6405 might be able to solve?
Mynacol said:
Is my data partition messed up (although Lineage functions correctly), or has TWRP a problem with encryption, which @html6405 might be able to solve?
Click to expand...
Click to collapse
Hi,
the encryption in TWRP was never supported for these devices, but I will take a look at it and try to find a solution.
Update 16.06.2021:
Brought support for GSI flash & reused old HIDDEN partition as vendor.
Brought support for encrypted /data partition.
Can i use this recovery img for my device gt-n5100 with build number KOT49H instead of KONA3G which is the only one available at twrp website?
sparks2012 said:
KOT49H
Click to expand...
Click to collapse
This code is only software related from samsung's side.
You can use the recovery.
html6405 said:
This code is only software related from samsung's side.
You can use the recovery.
Click to expand...
Click to collapse
Thanks
Hi,
After trying to revert my device to stock I lost twrp as well as the system..
Now my device is only showing start screen with samsung logo.
I want to reinstall TWRP so I followed procedure and with the device in download mode, from Linux I do:
Code:
heimdall flash --RECOVERY twrp-3.5.2_9-1-n5110.img
It seems to work (see logs below)
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
but when I restart the device and try to enter TWRP I get nothing but the same screen with Samsung logo.
I retried flashing several times but always same result.
Do you have an idea what could be wrong and how to solve it?
Thanks,
mutonic said:
Hi,
After trying to revert my device to stock I lost twrp as well as the system..
Now my device is only showing start screen with samsung logo.
I want to reinstall TWRP so I followed procedure and with the device in download mode, from Linux I do:
Code:
heimdall flash --RECOVERY twrp-3.5.2_9-1-n5110.img
It seems to work (see logs below)
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
but when I restart the device and try to enter TWRP I get nothing but the same screen with Samsung logo.
I retried flashing several times but always same result.
Do you have an idea what could be wrong and how to solve it?
Thanks,
Click to expand...
Click to collapse
If your device won't enter TWRP or the stock ROM (if you've flashe a full Firmware),
it could be that your eMMC is locked and need to get replaced.
html6405 said:
If your device won't enter TWRP or the stock ROM (if you've flashe a full Firmware),
it could be that your eMMC is locked and need to get replaced.
Click to expand...
Click to collapse
locked eMMC?? never heard of that before... what is it?
My device is in this state since I tried to flash the stock back ...
Could't it be related?
Edit:
Also I was surprised when I flashed the stock rom back to see the customized boot logo (with your nickname + xda developer) still displayed.
So it seems something went wrong or wasn't completely restored as I should see the original Samsung logo..
mutonic said:
locked eMMC?? never heard of that before... what is it?
Click to expand...
Click to collapse
The eMMC firmware lock's the storage if there are no blocks left.
Than it's read only.
mutonic said:
Also I was surprised when I flashed the stock rom back to see the customized boot logo (with your nickname + xda developer) still displayed.
So it seems something went wrong or wasn't completely restored as I should see the original Samsung logo..
Click to expand...
Click to collapse
This would be gone if the eMMC would store the flashed data.
html6405 said:
The eMMC firmware lock's the storage if there are no blocks left.
Than it's read only.
This would be gone if the eMMC would store the flashed data.
Click to expand...
Click to collapse
Very strange.. can it be fixed?
I wonder how something like this can happen.. I don't think I did anything wrong while flashing.
mutonic said:
Very strange.. can it be fixed?
Click to expand...
Click to collapse
Yes, your eMMC need to get replaced.
mutonic said:
I wonder how something like this can happen.. I don't think I did anything wrong while flashing.
Click to expand...
Click to collapse
Also a storage has it's physical end, the blocks are limited.
html6405 said:
Also a storage has it's physical end, the blocks are limited.
Click to expand...
Click to collapse
Thanks for precisions.
So this means it would be wearing issue? which would make sense given age of this device...
html6405 said:
Yes, your eMMC need to get replaced.
Click to expand...
Click to collapse
You mean hardware, how can it be?
Originally I wanted to restore device back to stock to benefit from trade in bonus offer from samsung.
I guess I'd rather getting it traded as it is than trying to repair it...
Twrp is not for galaxy tab a7 lite please i need a rom and twrp for this tablet. Thanks for watch this discussion.
It is a new device it will take some time to get someone to port it for Tab A7. Similar issues were happending with my galaxy A12 which had no custom recovery builds.
One ui core is phenomenal as it is, no offense to Samsung but I do believe that lineage OS or any other stock android OS would somehow increase the performance even more, battery life should may or may not change as it's great already!
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
R0GUEEE said:
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
Click to expand...
Click to collapse
Hey man that's great. I'm here for it I'll be the first one to try
Could anyone please kindly guide me how to unlock boot loader and root SM-T225.
Thanks in advance.
R0GUEEE said:
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
Click to expand...
Click to collapse
I too have a Tab A7 lite SM-T220 (rooted with Magisk) and cannot find any custom recovery anywhere ;( , if found would flashing say twrp on an already patched Magisk root cause unroot? Peace
vertab7 said:
I too have a Tab A7 lite SM-T220 (rooted with Magisk) and cannot find any custom recovery anywhere ;( , if found would flashing say twrp on an already patched Magisk root cause unroot? Peace
Click to expand...
Click to collapse
.
kzhtun said:
Could anyone please kindly guide me how to unlock boot loader and root SM-T225.
Thanks in advance.
Click to expand...
Click to collapse
.
ramz.pa said:
Hey man that's great. I'm here for it I'll be the first one to try
Click to expand...
Click to collapse
let me know if you find a solution. i want to root.
cewrik said:
.
I used
.https://forum.xda-developers.com/t/guide-sm-t500-t505-galaxy-tab-a7-10-4-unlock-bootloader-root-with-magisk.4185993/
Click to expand...
Click to collapse
method but with SM-T220 specific software NOT the
SM-T500/T505 software, it worked for me
cewrik said:
let me know if you find a solution. i want to root.
Click to expand...
Click to collapse
vertab7 said:
method but with SM-T220 specific software NOT the
SM-T500/T505 software, it worked for me
Click to expand...
Click to collapse
Can you help me, I sent you a private message.
R0GUEEE said:
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
Click to expand...
Click to collapse
Is there a procedure link for rooting by using the Magisk patched AP method and to unlock the bootloader? Thanks in advance!
I tried a lot but still like this
{
"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"
}
cewrik said:
I tried a lot but still like this
View attachment 5488719
Click to expand...
Click to collapse
What version of magisk are you on?
Did you try Universal SafetyNet Fix?
kzhtun said:
Could anyone please kindly guide me how to unlock boot loader and root SM-T225.
Thanks in advance.
Click to expand...
Click to collapse
Check out these guides out. The steps are mostly similar for recent Samsung tablets,
https://forum.xda-developers.com/t/guide-unlock-the-tab-s7-bootloader.4158841/
https://forum.xda-developers.com/t/how-to-root-galaxy-tab-s7-guide.4155897/page-5
xpdragon said:
What version of magisk are you on?
Did you try Universal SafetyNet Fix?
Click to expand...
Click to collapse
v23
what is this ?? Universal SafetyNet Fix
cewrik said:
v23
what is this ?? Universal SafetyNet Fix
Click to expand...
Click to collapse
It is another way to check SafetyNet. Can no longer check SafetyNet directly from latest version of Magisk Canary
xpdragon said:
It is another way to check SafetyNet. Can no longer check SafetyNet directly from latest version of Magisk Canary
Click to expand...
Click to collapse
I want to use xposed. I need full authorization.
R0GUEEE said:
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
Click to expand...
Click to collapse
Have you made any headway? I also spent a significant amount of time attempting to port TWRP. I was able to get TWRP to boot but touch did not work. Plugging in a mouse to a usb dongle, I was about to navigate TWRP but I was not able to do much. I had probelms mounting and editing the DATA partition. Im guessing it was an FSTAB config or an android 11 partitioning problem. I'm pretty fresh to this stuff but still made some progress. I gave up a bit ago but maybe I'll mess around with it a bit more.
tagcart said:
Have you made any headway? I also spent a significant amount of time attempting to port TWRP. I was able to get TWRP to boot but touch did not work. Plugging in a mouse to a usb dongle, I was about to navigate TWRP but I was not able to do much. I had probelms mounting and editing the DATA partition. Im guessing it was an FSTAB config or an android 11 partitioning problem. I'm pretty fresh to this stuff but still made some progress. I gave up a bit ago but maybe I'll mess around with it a bit more.
Click to expand...
Click to collapse
vbmeta or multidisabler flash is required ? . i tried porting twrp from xda guide for all devices. using stock recovery img ang google pixel twrp . all i got was bootloop .
Can i flash by dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery or odin method only works ?
AddictedA1 said:
vbmeta or multidisabler flash is required ? . i tried porting twrp from xda guide for all devices. using stock recovery img ang google pixel twrp . all i got was bootloop .
Can i flash by dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery or odin method only works ?
Click to expand...
Click to collapse
Once booted to twrp, I wasnt able to flash multidisabler because DATA wasnt mountable. In my case, flashing with Odin worked. Unfortunately the linux vm I did all this work on died so I lost all my progress.