Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
What is TWRP?
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Click to expand...
Click to collapse
Everything should work.
Installation:
Code:
fastboot flash recovery recovery.img
Download (thanks to @dhacker29 for this build):
http://loki.rombitch.com/Devs/Dhacker29/MotoG/TWRP-2.6.3.3-falcon.img
Unable to access TWRP. Unsure if it has even installed. Existing stock Recovery remains. How to access from cold boot? Power and Vol UP?
C:\Android\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
OKAY [ 0.672s]
finished. total time: 1.109s
Click to expand...
Click to collapse
lost101 said:
Unable to access TWRP. Unsure if it has even installed. Existing stock Recovery remains. How to access from cold boot? Power and Vol UP?
Click to expand...
Click to collapse
Sorry, wrong instructions in OP. Of course you have to "fastboot flash recovery recovery.img"
I flashed it with fastboot flash recovery recovery.img and all works fine, many thanks
Edit// nvm op has just updated flashing instructions
Sent from my XT1032 using Tapatalk
I got the 'mismatched partition size error,' but TWRP installed and loads. Cannot get swipe to unlock to work however.
lost101 said:
I got the 'mismatched partition size error,' but TWRP installed and loads. Cannot get swipe to unlock to work however.
Click to expand...
Click to collapse
"mismatched partition size" is nothing wrong, it is basically just saying, that the TWRP image is smaller than the stock recovery one.
You have to boot into recovery and wait for ~60s until screen turns black. Then press the power button and the touchscreen should work.
lost101 said:
I got the 'mismatched partition size error,' but TWRP installed and loads. Cannot get swipe to unlock to work however.
Click to expand...
Click to collapse
Touch was a little but buggy at first but as op said works fine after you let the screen sleep
Sent from my XT1032 using Tapatalk
Nice I will try it as anyone backuped, flashed anything?
Sent from my XT1032 using Tapatalk
---------- Post added at 01:02 PM ---------- Previous post was at 12:56 PM ----------
The touch bug, happens every time you boot into recovery? If so maybe u can set screen of to the minimum 60s is long, lol
Sent from my XT1032 using Tapatalk
Backup fails.
E:Unable to locate local storage device.
Click to expand...
Click to collapse
Can '/data/media/0' be specifically mounted as storage?
ferreinf said:
Nice I will try it as anyone backuped, flashed anything?
Sent from my XT1032 using Tapatalk
---------- Post added at 01:02 PM ---------- Previous post was at 12:56 PM ----------
The touch bug, happens every time you boot into recovery? If so maybe u can set screen of to the minimum 60s is long, lol
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
I am working on a better fix for it.
lost101 said:
Backup fails.
Can '/data/media/0' be specifically mounted as storage?
Click to expand...
Click to collapse
Will upload a new build within a few minutes.
lost101 said:
Backup fails.
Can '/data/media/0' be specifically mounted as storage?
Click to expand...
Click to collapse
Updated OP with new version.
OK, i think i fixed touch bug, and properly setted the mount points, i'm going to make a build.
josalaito said:
OK, i think i fixed touch bug, and properly setted the mount points, i'm going to make a build.
Click to expand...
Click to collapse
Could you share the information, how you fixed the touch bug, please?
a1Pha said:
Could you share the information, how you fixed the touch bug, please?
Click to expand...
Click to collapse
I added misc partition to recovery.fstab, because in some devices it has a related stuff from touch, but not sure if that fix the problem
[BACKUP COMPLETED IN 99 SECONDS]
Click to expand...
Click to collapse
lost101 said:
Click to expand...
Click to collapse
Can you upload it?
System files from stock rom are partitioned in 3 and isn't readable.
josalaito said:
I added misc partition to recovery.fstab, because in some devices it has a related stuff from touch, but not sure if that fix the problem
Click to expand...
Click to collapse
Just tried it here, unfortunately it doesn't help Thanks for trying!
Will update image later, fixing /radio mountpoint.
a1Pha said:
Just tried it here, unfortunately it doesn't help Thanks for trying!
Will update image later, fixing /radio mountpoint.
Click to expand...
Click to collapse
Maybe some touch layers are deep-sleeping until screen turns on, so i think the bug is related with init.rc file.
josalaito said:
Can you upload it?
System files from stock rom are partitioned in 3 and isn't readable.
Click to expand...
Click to collapse
Ok, will upload shortly.
OP updated with new image, fixes /radio-partition mountpoint.
Related
Hi, I was using TWRP to flash a new rom... I wiped but it took ages and appeared to have hanged. I powered down, then back up.
It loaded to Android... then froze.
Now I cant even boot to TWRP.
I can use WUGS toolkit to boot to twrp but I cant mount anything as it asks for a password to decrypt! I didnt have encryption enabled on my phone.
How can I fix this... I cant boot to Android to change USB debugging, only fastboot commands,
I think the fix is to format data. But try formatting just the cache first if you don't want to lose data.
viperman78 said:
Hi, I was using TWRP to flash a new rom... I wiped but it took ages and appeared to have hanged. I powered down, then back up.
It loaded to Android... then froze.
Now I cant even boot to TWRP.
I can use WUGS toolkit to boot to twrp but I cant mount anything as it asks for a password to decrypt! I didnt have encryption enabled on my phone.
How can I fix this... I cant boot to Android to change USB debugging, only fastboot commands,
Click to expand...
Click to collapse
First try:
fastboot flash cache cache.img
Get the cache.img from the factory image
jd1639 said:
First try:
fastboot flash cache cache.img
Get the cache.img from the factory image
Click to expand...
Click to collapse
Thanks,
I tried that but I get "error cannot open 'cache.img"
meangreenie said:
I think the fix is to format data. But try formatting just the cache first if you don't want to lose data.
Click to expand...
Click to collapse
TWRP wont let me format, it just re-asks me for my password to decrypt
viperman78 said:
Thanks,
I tried that but I get "error cannot open 'cache.img"
Click to expand...
Click to collapse
You sure you got the path to cache.img correct. Fastboot isn't finding it
jd1639 said:
You sure you got the path to cache.img correct. Fastboot isn't finding it
Click to expand...
Click to collapse
My bad... I've only used Toolkits before (very lazy). I put the cache.img in the right folder... it now says its erasing cache. But its taking ages!
viperman78 said:
My bad... I've only used Toolkits before (very lazy). I put the cache.img in the right folder... it now says its erasing cache. But its taking ages!
Click to expand...
Click to collapse
Let it do it's thing
---------- Post added at 08:27 AM ---------- Previous post was at 08:16 AM ----------
jd1639 said:
Let it do it's thing
Click to expand...
Click to collapse
If it's still going, something is wrong. Your cache partition is probably borked
jd1639 said:
Let it do it's thing
---------- Post added at 08:27 AM ---------- Previous post was at 08:16 AM ----------
If it's still going, something is wrong. Your cache partition is probably borked
Click to expand...
Click to collapse
Ok, its still going. Is there a recovery from this or have I killed my phone?
viperman78 said:
Ok, its still going. Is there a recovery from this or have I killed my phone?
Click to expand...
Click to collapse
If you can get into fastboot there's recovery. The next step is to flash the factory image. You will lose all your data. In the factory image there is a flash-all batch file. Just plug your phone into the usb and run that. It should take about 5 Minutes to run it
jd1639 said:
If you can get into fastboot there's recovery. The next step is to flash the factory image. You will lose all your data. In the factory image there is a flash-all batch file. Just plug your phone into the usb and run that. It should take about 5 Minutes to run it
Click to expand...
Click to collapse
Thanks mate, I don't care about saving data... I just want the phone to work! I'll let you know how it goes
viperman78 said:
Thanks mate, I don't care about saving data... I just want the phone to work! I'll let you know how it goes
Click to expand...
Click to collapse
When you get it running again use trwp 2.6.3.4 from what started your problem it sounds like you were using an earlier version
jd1639 said:
When you get it running again use trwp 2.6.3.4 from what started your problem it sounds like you were using an earlier version
Click to expand...
Click to collapse
Thanks, I have flashed the bootloader and radio fine... but whenever I fastboot reboot-bootloader it just goes black and I have to power/volume down to get back to recovery. I'll do the other files now
@abaaaabbbb63 any ideas for this guy? I thinking bad emmc at this point
jd1639 said:
@abaaaabbbb63 any ideas for this guy? I thinking bad emmc at this point
Click to expand...
Click to collapse
Its not good... I'm flashing system.img but its just hanging on erasing 'system'.
is there a recovery from bad emmc?
viperman78 said:
Its not good... I'm flashing system.img but its just hanging on erasing 'system'.
is there a recovery from bad emmc?
Click to expand...
Click to collapse
There is but you're not going to like it. It's RMA the device
jd1639 said:
There is but you're not going to like it. It's RMA the device
Click to expand...
Click to collapse
Crap... its unlocked does that mean they wont honor a warranty? Is there nothing left to try?
viperman78 said:
Crap... its unlocked does that mean they wont honor a warranty? Is there nothing left to try?
Click to expand...
Click to collapse
You can probably still:
fastboot oem lock
But hold off on that for awhile maybe someone else had some ideas
jd1639 said:
@abaaaabbbb63 any ideas for this guy? I thinking bad emmc at this point
Click to expand...
Click to collapse
Yup. Definitely a bad emmc. Sorry mate.
abaaaabbbb63 said:
Yup. Definitely a bad emmc. Sorry mate.
Click to expand...
Click to collapse
Well bugger it! Thanks for the help guys. So, I'll try a relock and RMA. If the relock fails is it possible I can pay LG to fix it or is it just better to buy a new Nexus? Otherwise I imagine I'll be months without a phone.
Did I break the emmc or is it just a dodgy chip? Or maybe I didn't use the latest TWRP?
Q&A for [RECOVERY][GT-P51XX] TWRP | PhilZ Touch | CWM
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Thanks for your help
Great work! Thank you
can mobile odin (http://forum.xda-developers.com/showthread.php?t=2068667) flash ur latest cwm???
Hi, I am a newb.
I just rooted my Galaxy Tab 2(P5113) using Philz Recovery 6. I really don't know what I'm doing. I have spent hours reading and trying different things.
The device is now 'rooted'. I can get into Philz Touch 6. I don't think it installed correctly though. When I choose 'Install Zip' and 'Choose zip from /storage/sdcard1' and select a file like(philz_touch_6.57.8-p5110.zip) It says 'E:Can't open /storage/sdcard1/philz_touch_6.57.8.zip(bad)'. I have tried many files (5.00.5, 6.07.9, 6.57.8). Not sure which file I should be loading, I assumed the latest. All the files say p5100, mine is a p5113 but I think that's right.
Any help will be greatly appreciated.
Thanks,
Wiij
Make sure you are properly rooted and have the latest updated custom recovery of your choice. For your P5113 use P5110 zips not P5100. Good luck!
@wiij your file seems corrupt. Maybe try flashing from internal storage. Also make sure you are useing P5110 recovery!
Send from OnePlus One using Tapatalk
TWRP decrypt doesnt work
Hi there,
I need help because my encrypted tab doesnt decrypt in TWRP.
I am running my P5100 with CM11 (nightly from September) and TWRP 2.8.1.0. I've encrypted the tab a few weeks ago under CM11, but when I boot into recovery, I dont get a decrypt prompt (which differs to the behavior of my nexus7_2013 with the same rom and twrp recovery). A manual mount of /data does not work (still no prompt or something similar) or I am doing it wrong.
Because of this, I am unable to install a rom update.
Thanks in advance for any help.
drohhyn
TWRP on GT-P5113
I had the same experience (and frustration) on my GT-P5113
Once the device was rooted and CWM recovery installed, I downloaded Android-Andi's GT-P5110_TWRP_2.8.1.0.zip (saved to external storage), rebooted to recovery mode, then installed from zip.
I also (sucessfully) tested installing TWRP using Andi's GT-P5110_TWRP_2.8.1.0.tar.md5 image from Windows 8.1 using Odin3 v1.85.exe.
I was attempting to post this message (links to Andi's files on AFH removed) in reply to http://forum.xda-developers.com/showthread.php?p=57880315#post57880315 (this is where XDA dumped me).
Decryption isn't support because i don't use it and don't need it.
You can try official TWRP, maybe it supports it http://teamw.in/project/twrp2/147
Send from OnePlus One using Tapatalk
---------- Post added at 09:37 PM ---------- Previous post was at 09:32 PM ----------
Maybe someone can please create a recovery log @mentat2 or @drohhyn?
Send from OnePlus One using Tapatalk
Android-Andi said:
Decryption isn't support because i don't use it and don't need it.
You can try official TWRP, maybe it supports it [useful link removed]
Send from OnePlus One using Tapatalk
---------- Post added at 09:37 PM ---------- Previous post was at 09:32 PM ----------
Maybe someone can please create a recovery log @mentat2 or @drohhyn?
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Thanks Andi,
I will give that a try (it appears that I have to remove the links from your post, before XDA will let me reply)!
This reCAPTCHA business is killing me.
mentat2 said:
Thanks Andi, I will give that a try (it appears that I have to remove the links from your post, before XDA will let me reply)!
Click to expand...
Click to collapse
Can you first please create a recovery log in TWRP? I.mean before.switching?
Send from OnePlus One using Tapatalk
---------- Post added at 09:51 PM ---------- Previous post was at 09:47 PM ----------
Btw. Did you tried to format internal storage on advanced wipe?
Send from OnePlus One using Tapatalk
Android-Andi said:
Can you first please create a recovery log in TWRP? I.mean before.switching?
1.
Send from OnePlus One using Tapatalk
---------- Post added at 09:51 PM ---------- Previous post was at 09:47 PM ----------
Btw. Did you tried to format internal storage on advanced wipe?
2.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
1. Sure, I'll do that now.
2. No, I did not... I usually wipe/format everything, including internal storage with switching ROMS (CM11/SlimKat), but not when flashing a new recovery (CWM/TWRP).... Is this recommended?
BTW, are you planning on building TWRP 2.8.3.0 for the P5113/P5110?
Thanks.
@mentat2 i am in contact with Dees_Troy in hope to.solve the issue:
" Next step is to get a log of a failed decrypt
adb pull /tmp/recovery.log while still in TWRP"
Edit:
About 2.
No not needed while switching recovery.
It only would be interesting if this works because of decrypt. Our data is stored in /data/media Internal storage).
About 3.
Yes, sometimes later.
Send from OnePlus One using Tapatalk
@mentat2 what about the log? Without log we can't fix the issue.
Send from OnePlus One using Tapatalk
Android-Andi said:
@mentat2 what about the log? Without log we can't fix the issue.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Hi Andi,
It appears that I am having major issues with my laptop right now (I can't seem to make a connection to the tablet from any of the USB ports)...
Perhaps we can call on @drohhyn to provide you with a log of a failed decrypt?
@mentat2 i will upload a new recovery for you which might fix adb not working in recovery. Give me some minutes.
Send from OnePlus One using Tapatalk
Android-Andi said:
@drohhyn i am in contact with Dees_Troy in hope to.solve the issue:
" Next step is to get a log of a failed decrypt
adb pull /tmp/recovery.log while still in TWRP"
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
@drohhyn can you get this log for Andi regarding your post?
drohhyn said:
Hi there,
I need help because my encrypted tab doesnt decrypt in TWRP.
I am running my P5100 with CM11 (nightly from September) and TWRP 2.8.1.0. I've encrypted the tab a few weeks ago under CM11, but when I boot into recovery, I dont get a decrypt prompt (which differs to the behavior of my nexus7_2013 with the same rom and twrp recovery). A manual mount of /data does not work (still no prompt or something similar) or I am doing it wrong.
Because of this, I am unable to install a rom update.
Thanks in advance for any help.
drohhyn
Click to expand...
Click to collapse
mentat2 said:
Hi Andi,
It appears that I am having major issues with my laptop right now (I can't seem to make a connection to the tablet from any of the USB ports)...
Perhaps we can call on @drohhyn to provide you with a log of a failed decrypt?
Click to expand...
Click to collapse
Please try attached repacked TWRP. Sometimes for me Windows also does not detect my device in recovery...depends on the installed driver.
The repacked version might work for you to get a connection on ADB work.
Edit:
Re-uploaded, used wrong ZIP
Android-Andi said:
Please try attached repacked TWRP. Sometimes for me Windows also does not detect my device in recovery...depends on the installed driver.
The repacked version might work for you to get a connection on ADB work.
Edit:
Re-uploaded, used wrong ZIP
Click to expand...
Click to collapse
Andi, you know I trust you implicitly, but is safe to download and flash now?
I am currently running GT-P5110_TWRP_2.8.1.0.zip downloaded from your AFH site.
mentat2 said:
Andi, you know I trust you implicitly, but is safe to download and flash now?
I am currently running GT-P5110_TWRP_2.8.1.0.zip downloaded from your AFH site.
Click to expand...
Click to collapse
I see no reason why it shouldn't work. I flashed the p3110 TWRP 2.8.1.1 and repacked a ton of recoveries in the past. If something went wrong you can flash back using Odin. Maybe @tetakpatak can test the repack first if you feel more safe.
Send from OnePlus One using Tapatalk
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.
CHANGELOG for 3.2.3-0:
Fixed automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Flashing:
Note: this device has anti roll back
Code:
fastboot boot twrp-sakura.img
it'll boot to TWRP... now flash the recovery again with TWRP
Internal showing 0 mb ?
format data... including Internal storage to remove encryption
Downloads: for Redmi 6 pro
Credits:
~ TeamWin
~ CM/Lineage/Omni android
~ Tingyi Chen, sarthak malla
~ @CrazyBirdie1 our pro tester ;-;
Device tree: here
Kernel: prebuilt, from stock miui rom
XDA:DevDB Information
official twrp, Tool/Utility for the Xiaomi Redmi 6 Pro
Contributors
aragon12
Source Code: http://github.com/teamwin
Version Information
Status: Stable
Stable Release Date: 2018-10-09
Created 2018-10-09
Last Updated 2018-10-08
reserved
Thanks for this. I was beginning to regret buying sakura since there was no development other than those GSI's. This was a breath of fresh air. Is the full device tree up?
Sir very happy to see you here. I have seen your work for land, hope to see similar kind of development here. I hope more peoples will come here soon.
Procedures after booting into TWRP?
Hi Sir,
Thanks for the update with TWRP for Redmi6 Pro first, i am just confused about what do you mean by "flashing twrp after booting into TWRP.img", i know i can do that by install disk image in twrp, but it asks for file decryption password, otherwise twrp shows 0MB for every partition.
So there is nothing to flash.
What should i do about that? If you can provide some suggestions that would be great!
Anyone tried on mia2 lite?
Edit: Boots, but partition-scheme kills the fun... Data can be formatted, but all other partitions can´t be mounted. Flashing back stock recovery and wiping data with stock brings everything to normal...
You can always use memory card.
madhead2333 said:
Hi Sir,
Thanks for the update with TWRP for Redmi6 Pro first, i am just confused about what do you mean by "flashing twrp after booting into TWRP.img", i know i can do that by install disk image in twrp, but it asks for file decryption password, otherwise twrp shows 0MB for every partition.
So there is nothing to flash.
What should i do about that? If you can provide some suggestions that would be great!
Click to expand...
Click to collapse
Anyone here tried rooting via Magisk? Also, flashing the TWRP image after after booting into it will make it persistent, right?
coolek33 said:
You can always use memory card.
Click to expand...
Click to collapse
Sure, i will try it.
ty
DJBhardwaj said:
Anyone here tried rooting via Magisk? Also, flashing the TWRP image after after booting into it will make it persistent, right?
Click to expand...
Click to collapse
Magisk works well no problem..however i cant seem to boot into twrp, it always boots into mi recovery..only way i booted to twrp is by using pc.
loseyourself said:
Magisk works well no problem..however i cant seem to boot into twrp, it always boots into mi recovery..only way i booted to twrp is by using pc.
Click to expand...
Click to collapse
Not even after flashing the recovery image in TWRP itself?
DJBhardwaj said:
Anyone here tried rooting via Magisk? Also, flashing the TWRP image after after booting into it will make it persistent, right?
Click to expand...
Click to collapse
DJBhardwaj said:
Not even after flashing the recovery image in TWRP itself?
Click to expand...
Click to collapse
It didnt work for me..flashed the recovery partition with twrp from booted twrp many times.. no luck..vol up + pwr button same mi recovery 3
I've read somewhere that because i've been using miui it always boots up in mi recovery..
I cant seem to remember if i had working twrp with miui before in previous mi phones..
loseyourself said:
It didnt work for me..flashed the recovery partition with twrp from booted twrp many times.. no luck..vol up + pwr button same mi recovery 3
I've read somewhere that because i've been using miui it always boots up in mi recovery..
I cant seem to remember if i had working twrp with miui before in previous mi phones..
Click to expand...
Click to collapse
Try both vol up+down+power together
loseyourself said:
it always boots into mi recovery.
Click to expand...
Click to collapse
If mi recovery is present then it means you didn't flash twrp img after booting into it. Follow the instructions carefully.
So all of you folks have already unlocked the bootloader of your Redmi Note 6 Pro and are using TWRP?
I tried unlocking mine on the 10th and was given a 30-day waiting lockout before I could unlock my bootloader
IceBreakr said:
If mi recovery is present then it means you didn't flash twrp img after booting into it. Follow the instructions carefully.
Click to expand...
Click to collapse
Are you able to access twrp using keys? Because i flashed many times using booted twrp..i must be doing something wrong..
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
NaYaB786 said:
Try both vol up+down+power together
Click to expand...
Click to collapse
No luck man it just reboots
It's redmi 6 pro thread.
Enddo said:
So all of you folks have already unlocked the bootloader of your Redmi Note 6 Pro and are using TWRP?
I tried unlocking mine on the 10th and was given a 30-day waiting lockout before I could unlock my bootloader
Click to expand...
Click to collapse
i hope someone make a android 9 rom.
Hi i can this recovery in MiA2 lite?
secoes90 said:
Hi i can this recovery in MiA2 lite?
Click to expand...
Click to collapse
Nope you have different thread for that.
https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
Searching on internet about working twrp recovery for weekly developer 9.7.18 ROM, i find this TWRP who is working on this version of ROM. I have tested on chines weekly 9.7.18 and recovery install fine.
Code:
/*
*
* I am not responsible for bricked devices or components. Please
* do some research if you have any concerns about features included in this image
* before flashing it! YOU are choosing to make these modifications.
*
*/
After Install : Format data or wipe everything to decrypt storage
OriginalSource Thanks to Xiaomi-Miui.gr
DownloadFile
NEW WERSION DownloadFile
How to flash it if I'm already on 9.7.18 version and I can't boot into TWRP ?
Fikul said:
How to flash it if I'm already on 9.7.18 version and I can't boot into TWRP ?
Click to expand...
Click to collapse
Put your phone in fastboot mode, and flash by fastboot
fastboot flash recovery twrp.img
then start phone with buttons power on and vol+ to go back to twrp.
maybe you will have to do wipe data to clear encryption , i have to do that after flashing on chines 9.7.18
would be nice to tell as you have already install custom rom so maybe all will be ok.
Works like a charm with new developer 9.7.18 !
Fikul said:
Works like a charm with new developer 9.7.18 !
Click to expand...
Click to collapse
I am happy if it works
did you have to wipe/format data?
Flashed with the other TWRP, works perfectly, color is ugly af.
EDIT: OTG not working.
Schnedi said:
Flashed with the other TWRP, works perfectly, color is ugly af.
Click to expand...
Click to collapse
i agree color is ugly, but i dont know how to change color.
slavke1976 said:
I am happy if it works
did you have to wipe/format data?
Click to expand...
Click to collapse
Yes i had to format data because of encryption
Can somebody please do a noob tutorial on how to get this running on my phone please the last time I was in the flashing game Xiaomi phones came with unlocked bootloaders ?
Source down?
Any official recovery????
Shahkhalid zadran said:
Any official recovery????
Click to expand...
Click to collapse
None yet.
Koehlix said:
Source down?
Click to expand...
Click to collapse
Go to source page, and search in tab list k20/mi9t it will give you download link. https://xiaomi-miui.gr/community/index.php/Thread/25256-TWRP-3-3-X-X-για-συσκευές-XIAOMI/
but if you dont know just go here https://www.mediafire.com/file/0is4jdh0emuja4v/twrp_davinci_3.3.1_23-07-19_red_ss.img/file
Cant find my files in TWRP anymore. All is looking "crypted". Did a full wipe. Nothing helps.
FroZine said:
Cant find my files in TWRP anymore. All is looking "crypted". Did a full wipe. Nothing helps.
Click to expand...
Click to collapse
Same here.
Sent from my [device_name] using XDA-Developers Legacy app
Koehlix said:
Same here.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You need to wipe everything (ALL DATA GONE) - working for me now
When I flashed the 'official' TWRP recovery I'm asked to enter a password to decrypt data. But how can I get the password??? If I press 'cancel' my folders are all encrypted
the steve said:
When I flashed the 'official' TWRP recovery I'm asked to enter a password to decrypt data. But how can I get the password??? If I press 'cancel' my folders are all encrypted
Click to expand...
Click to collapse
You put a password in Android for unlock your phone, it's this.
the steve said:
When I flashed the 'official' TWRP recovery I'm asked to enter a password to decrypt data. But how can I get the password??? If I press 'cancel' my folders are all encrypted
Click to expand...
Click to collapse
you have to enter password you use to unlock your phone (screen)
AlexCmb said:
You put a password in Android for unlock your phone, it's this.
Click to expand...
Click to collapse
slavke1976 said:
you have to enter password you use to unlock your phone (screen)
Click to expand...
Click to collapse
Thank you so very much! I didn't expect it would be that simple.
Anyway I can't boot to system anymore, it always ends in the recovery.
Team Win Recovery Project for Galaxy A20e (A202F)
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.
*
*/
BUGS:
- ADB
This recovery is only for Android 9, if u updated A20E to Android 10 u can't flash this recovery.
According to some users it can work on Android 10 but I don't guarantee booting to your stock system but u can install straight GSI
1. Make sure u have rooted phone, if not check this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root or/also this https://forum.xda-developers.com/galaxy-a20/how-to/root-samsung-galaxy-a20-rooting-guide-t3954872
2. You gonna lose all of data.
3. Make sure u have checked OEM unlock in settings
4. Reboot phone to android/stock recovery (u can use: adb reboot recovery), wipe data/cache and straight after this select "Reboot to bootloader"
5. Plug telephone to computer, start Odin(use v. 3.13.x) add recovery.tar to AP slot, click start and immediately click and hold POWER and VOLUME UP until TWRP logo pop up.
6. Format Data (not just wipe) - don't restart (idk if needed but do it for safety)
7. Use MTP to put Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip and flash it, system should start normaly. (i didnt checked on stock, i straight installed GSI)
Now u can flash GSI ROM(use only A/B): https://forum.xda-developers.com/galaxy-a20/how-to/gsi-galaxy-a20-t3964546
Flash .img and after this flash GSI_Fix_boot.zip, wipe cache and restart to system.
AND NOW MOST IMPORTANT PART:
Find your build number in software information.
A202FXXU3ASL4 means U3
A202FXXU2ASJ3 means U2
IF U HAVE U3/S3 BOOTLOADER FLASH THIS TAR:
https://mega.nz/folder/LTZlUKyI#oxxVc5zj8tP4bNQBIo8AlA
IF U HAVE U2/S2 BOOTLOADER:
u need to compare alphabetically 3 last characters of build number(NOT CSC!) with A202FXXU2ASJ3
for example your build number is A202FXXS2ASI3 so last 3 characters are ASI and u need to compare it with ASJ -> first and second letter are the same, so go to third, letter I in alphabet is before J, so u have older firmware and u need flash this tar(eg. ASH, ASG, ASF):
https://mega.nz/folder/nDZUwS5A#_FQKWL_1QUHN8_wXgqdGBw
if u have at least A202FXXU2ASJ3 or newer(eg. ASK, ASL, ASM) or firmware flash this tar:
https://mega.nz/folder/7bZ20IAY#ewz5ZZzWxTJfAbcnEJgAZA
I DIDN'T TESTED NEWER U2 AND U3 BUT IT SHOULD WORK FOR 99%
Crashes on teamwin splash screen.
How did you compile? When I make one, it bootloops. Can you tell me how you did it?
ert69 said:
Crashes on teamwin splash screen.
Click to expand...
Click to collapse
If it stucks on splash screen it means that ur device have still data encryption, did u before flashing wiped data/cache in stock recovery?
Royna said:
How did you compile? When I make one, it bootloops. Can you tell me how you did it?
Click to expand...
Click to collapse
U need to do twrp device tree, u can use prebuilt kernel or straight from source, and u need dtbo image if ur bulding on android 9+. I too get bootloops but key is to use right version of kernel appropriate for ur bootloader version. There is massive difference beetween old U2 and new U2 and maybe that why ur twrp gets bootloop. Also u need fix for himax touchscreen to work in recovery mode. I make public sources of my work also with commits.
famouzkk said:
U need to do twrp device tree, u can use prebuilt kernel or straight from source, and u need dtbo image if ur bulding on android 9+. I too get bootloops but key is to use right version of kernel appropriate for ur bootloader version. There is massive difference beetween old U2 and new U2 and maybe that why ur twrp gets bootloop. Also u need fix for himax touchscreen to work in recovery mode. I make public sources of my work also with commits.
Click to expand...
Click to collapse
Thank you for answering. Are there no plans for developing for android 10 a20e? When I install ur u3 bootloader twrp, it shows twrp logo. And its stuck there. Can you make one using android 10 sources? Or you don't want to take risks not testing it, can you share ur files like ueventd.rc , boardconfig.mk? So I can make one. I am not so sure about my flags and ueventd.rc files...
Royna said:
Thank you for answering. Are there no plans for developing for android 10 a20e? When I install ur u3 bootloader twrp, it shows twrp logo. And its stuck there. Can you make one using android 10 sources? Or you don't want to take risks not testing it, can you share ur files like ueventd.rc , boardconfig.mk?
Click to expand...
Click to collapse
Samsung didin't for now make public any android 10 kernel sources for A20e, if they do it public i gonna try. Oh, if u get splash screen it means u have still data encryption, did u before flashing twrp wiped in stock recovery data/cache, if it boots to splash screen its really big chance it gonna work for you and also for others.
uevent.rc just pick up from any exynos7885 device tree, also BoardConfig.mk are really the same, as a10 or a30.
famouzkk said:
Samsung didin't for now make public any android 10 kernel sources for A20e, if they do it public i gonna try. Oh, if u get splash screen it means u have still data encryption, did u before flashing twrp wiped in stock recovery data/cache, if it boots to splash screen its really big chance it gonna work for you and also for others.
uevent.rc just pick up from any exynos7885 device tree, also BoardConfig.mk are really the same, as a10 or a30.
Click to expand...
Click to collapse
Wow. It worked. You can edit that it works for android 10 too. One question. Why the system partition is mounted read-only and can't be changed? I want to re-partition /system to install google r preview gsi
Edit: Search: On android Q, We can't mount /system rw.....
Royna said:
Wow. It worked. You can edit that it works for android 10 too. One question. Why the system partition is mounted read-only and can't be changed? I want to re-partition /system to install google r preview gsi
Edit: Search: On android Q, We can't mount /system rw.....
Click to expand...
Click to collapse
https://android.stackexchange.com/q...m-partition-locked-to-read-only-in-android-10
Android 10 is formatted with EXT4_FEATURE_RO_COMPAT_SHARED_BLOCKS which is blocking to mount system partition as rw.
Royna said:
Wow. It worked. You can edit that it works for android 10 too. One question. Why the system partition is mounted read-only and can't be changed? I want to re-partition /system to install google r preview gsi
Edit: Search: On android Q, We can't mount /system rw.....
Click to expand...
Click to collapse
Can u also give ur build number? I mean A202FXU3xxx?
famouzkk said:
can u also give ur build number? I mean a202fxu3xxx?
Click to expand...
Click to collapse
a202fxxu3btd1
---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------
Now trying to downgrade to android 9 gsi and re-partiton there
---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------
P.S. Does re-partition work?
famouzkk said:
Team Win Recovery Project for Galaxy A20e (A202F)
BUGS:
- ADB
This recovery is only for Android 9, if u updated A20E to Android 10 u can't flash this recovery.
According to some users it can work on Android 10 but I don't guarantee booting to your stock system but u can install straight GSI
1. Make sure u have rooted phone, if not check this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root or/also this https://forum.xda-developers.com/galaxy-a20/how-to/root-samsung-galaxy-a20-rooting-guide-t3954872
2. You gonna lose all of data.
3. Make sure u have checked OEM unlock in settings
4. Reboot phone to android/stock recovery (u can use: adb reboot recovery), wipe data/cache and straight after this select "Reboot to bootloader"
5. Plug telephone to computer, start Odin(use v. 3.13.x) add recovery.tar to AP slot, click start and immediately click and hold POWER and VOLUME UP until TWRP logo pop up.
6. Format Data (not just wipe) - don't restart (idk if needed but do it for safety)
7. Use MTP to put Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip and flash it, system should start normaly. (i didnt checked on stock, i straight installed GSI)
Now u can flash GSI ROM(use only A/B): https://forum.xda-developers.com/galaxy-a20/how-to/gsi-galaxy-a20-t3964546
Flash .img and after this flash GSI_Fix_boot.zip, wipe cache and restart to system.
AND NOW MOST IMPORTANT PART:
Find your build number in software information.
A202FXXU3ASL4 means U3
A202FXXU2ASJ3 means U2
IF U HAVE U3/S3 BOOTLOADER FLASH THIS TAR:
https://mega.nz/folder/LTZlUKyI#oxxVc5zj8tP4bNQBIo8AlA
IF U HAVE U2/S2 BOOTLOADER:
u need to compare alphabetically 3 last characters of build number(NOT CSC!) with A202FXXU2ASJ3
for example your build number is A202FXXS2ASI3 so last 3 characters are ASI and u need to compare it with ASJ -> first and second letter are the same, so go to third, letter I in alphabet is before J, so u have older firmware and u need flash this tar(eg. ASH, ASG, ASF):
https://mega.nz/folder/nDZUwS5A#_FQKWL_1QUHN8_wXgqdGBw
if u have at least A202FXXU2ASJ3 or newer(eg. ASK, ASL, ASM) or firmware flash this tar:
https://mega.nz/folder/7bZ20IAY#ewz5ZZzWxTJfAbcnEJgAZA
I DIDN'T TESTED NEWER U2 AND U3 BUT IT SHOULD WORK FOR 99%
Click to expand...
Click to collapse
Can you pls make a Recovery for android 10? Because I already have Android 10 ? Or can it also work with Android 10? I don't want to brick my phone ? that's the reason why I ask
famouzkk said:
Samsung didin't for now make public any android 10 kernel sources for A20e, if they do it public i gonna try. Oh, if u get splash screen it means u have still data encryption, did u before flashing twrp wiped in stock recovery data/cache, if it boots to splash screen its really big chance it gonna work for you and also for others.
uevent.rc just pick up from any exynos7885 device tree, also BoardConfig.mk are really the same, as a10 or a30.
Click to expand...
Click to collapse
for what do you actually need the device tree?
donut boyyyyyy said:
Can you pls make a Recovery for android 10? Because I already have Android 10 Or can it also work with Android 10? I don't want to brick my phone that's the reason why I ask
Click to expand...
Click to collapse
Can you please read post carefully? Ye it can work on android 10 but i dont guarantee booting to your stock system(but after flashing dm verfiy zip it should work) also u can just flash gsi
famouzkk said:
Can you please read post carefully? Ye it can work on android 10 but i dont guarantee booting to your stock system(but after flashing dm verfiy zip it should work) also u can just flash gsi
Click to expand...
Click to collapse
sry was so happy that finally a recovery for my device because the device is already 1 year and Before there was no Recovery I am so grateful that there is finally one
---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------
famouzkk said:
Can you please read post carefully? Ye it can work on android 10 but i dont guarantee booting to your stock system(but after flashing dm verfiy zip it should work) also u can just flash gsi
Click to expand...
Click to collapse
Should I downgrade and then flash recovery? ?What would you advise me as a developer?
donut boyyyyyy said:
sry was so happy that finally a recovery for my device because the device is already 1 year and Before there was no Recovery I am so grateful that there is finally one
---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------
Should I downgrade and then flash recovery? ?What would you advise me as a developer?
Click to expand...
Click to collapse
Do not downgrade it gonna brick ur telephone, just straight install twrp but CAREFULLY read instruction.
famouzkk said:
Do not downgrade it gonna brick ur telephone, just straight install twrp but CAREFULLY read instruction.
Click to expand...
Click to collapse
So should I do it in Android 10? And one thing what do you mean with step four...Do you have to do that in recovery or download mode or do you have to wipe the data and cache in stock recovery and then flash it in Odin Have the latest security update in German its 1.6.2020 Which file do I need?
donut boyyyyyy said:
So should I do it in Android 10? And one thing what do you mean with step four...Do you have to do that in recovery or download mode or do you have to wipe the data and cache in stock recovery and then flash it in Odin Have the latest security update in German its 1.6.2020 Which file do I need?
Click to expand...
Click to collapse
Yes you need to do this because of data encryption and if u dont do that u gonna get stuck at splash screen. Just pick up U3 recovery.
famouzkk said:
Yes you need to do this because of data encryption and if u dont do that u gonna get stuck at splash screen. Just pick up U3 recovery.
Click to expand...
Click to collapse
But in stock ? ? Have watched videos since they only formatted it in custom recovery
donut boyyyyyy said:
But in stock ? ? Have watched videos since they only formatted it in custom recovery
Click to expand...
Click to collapse
Ehh, enable debugging in programming options, then connect to computer and write in cmd: adb reboot recovery(if u dont have adb - install it), after wipe cache/data click reboot to bootloader and follow the instruction.