This recovery is compile from the latest TWRP source available for Android 4.4 and repack with Android Image Kitchen (the kernel and dtb.img are extracted from D620r10d stock recovery.img).
You can flash the recovery file (TWRP 2.8.1.0 D620.img) with Rashr app.
The backup and restore functions are tested and are working OK.
Thanks to:
Vagelis1608 for his help
all developers involved with development for our phone
TeamWin for their amazing recovery.
osm0sis for Android Image Kitchen
MD5:96be90212dae9f57ed0927089960187e
New TWRP 2.8.5.0 here.
Why is the theme orange and not the standard blue?
Also, why does it look like normal in this screenshot:
{
"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"
}
The log for the error mentioned in screenshot is attached.
Sent from my D620r [CM12]
I recompiled the recovery and I fixed the theme color. Now is standard blue.
I attached the new compiled recovery in my first post.
I retested full backup and restore and its working without errors.
The error you mentioned was from loading of the theme (Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)). Now with recompiled recovery that error does not appear.
powermetza said:
I recompiled the recovery and I fixed the theme color. Now is standard blue.
I attached the new compiled recovery in my first post.
I retested full backup and restore and its working without errors.
The error you mentioned was from loading of the theme (Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)). Now with recompiled recovery that error does not appear.
Click to expand...
Click to collapse
The theme is fixed, but the error still appears.
Sent from my D620r [CM12]
On my phone the error appears only when I reload theme (from Advanced settings), and I don't see any reason to reload the theme.
In recovery.log the error appear:
I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)
E:Failed to load package.
I:Attempting to reload stock theme...
I:Loading package: TWRP (/res/ui.xml)
And from this error I understand that the recovery try to load ui.zip from internal storage. The ui.zip does not exist, so it is normal that there is an error. The problem is why the recovery try to load ui.zip, because it does not need it (I think so, because the recovery works without it). If I have time, I will try to fix this problem. Now I am trying to compile TWRP 2.8.3.0 (without success until now) and I have only a few days off before I have to go to work (job).
If you have any idea to solve this problem please let me know. And thanks for your help.
powermetza said:
On my phone the error appears only when I reload theme (from Advanced settings), and I don't see any reason to reload the theme.
In recovery.log the error appear:
I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)
E:Failed to load package.
I:Attempting to reload stock theme...
I:Loading package: TWRP (/res/ui.xml)
And from this error I understand that the recovery try to load ui.zip from internal storage. The ui.zip does not exist, so it is normal that there is an error. The problem is why the recovery try to load ui.zip, because it does not need it (I think so, because the recovery works without it). If I have time, I will try to fix this problem. Now I am trying to compile TWRP 2.8.3.0 (without success until now) and I have only a few days off before I have to go to work (job).
If you have any idea to solve this problem please let me know. And thanks for your help.
Click to expand...
Click to collapse
This error isn't important. Don't even bother to fix it.
What problems are you having with TWRP 2.8.3.0?
Sent from my D620r [CM12]
Vagelis1608 said:
What problems are you having with TWRP 2.8.3.0?
Click to expand...
Click to collapse
I am trying to compile TWRP 2.8.3.0 with the source from here.
For the source code I used CM12.
For device I tried invaderjohn source, then Zaaap72 source, and then I created my on device with the next command:
Code:
.build/tools/device/mkvendor.sh lge d620 ~/recovery.img
In every situation, the compilation finished with the next error:
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat ‘/home/amd/android/system/out/target/product/d620r/root/init.recovery.*.rc’: No such file or directory
build/core/Makefile:909: recipe for target '/home/amd/android/system/out/target/product/d620r/ramdisk-recovery.img' failed
make: [/home/amd/android/system/out/target/product/d620r/ramdisk-recovery.img] Error 1 (ignored)
Made recovery image: /home/amd/android/system/out/target/product/d620r/recovery.img
I ask for help on IRC channel #twrp (official channel of TeamWin) and someone from there said that in BoardConfig.mk is a mention of recovery.rc.
The problem is that I search all the files from my device folders and there is no mention of recovery.rc.
I tried to use source code from Omnirom 5.0 instead of CM12, but the device source from invaderjohn or Zaaap72 are not working (after "source build/envsetup.sh" command, I used "lunch" command and then select the d620 device) and "build/tools/device/mkvendor.sh" file is missing so I can not create my on device. I tried to manually edit the files, but without success.
Now I have two virtual machine, one with CM12 source code and one with Omnirom 5.0 source code.
powermetza said:
I am trying to compile TWRP 2.8.3.0 with the source from here.
For the source code I used CM12.
For device I tried invaderjohn source, then Zaaap72 source, and then I created my on device with the next command:
Code:
.build/tools/device/mkvendor.sh lge d620 ~/recovery.img
In every situation, the compilation finished with the next error:
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat ‘/home/amd/android/system/out/target/product/d620r/root/init.recovery.*.rc’: No such file or directory
build/core/Makefile:909: recipe for target '/home/amd/android/system/out/target/product/d620r/ramdisk-recovery.img' failed
make: [/home/amd/android/system/out/target/product/d620r/ramdisk-recovery.img] Error 1 (ignored)
Made recovery image: /home/amd/android/system/out/target/product/d620r/recovery.img
I ask for help on IRC channel #twrp (official channel of TeamWin) and someone from there said that in BoardConfig.mk is a mention of recovery.rc.
The problem is that I search all the files from my device folders and there is no mention of recovery.rc.
I tried to use for source code from Omnirom 5.0 instead of CM12, but the device source from invaderjohn or Zaaap72 are not working (after "source build/envsetup.sh" command, I used "lunch" command and then select the d620 device) and "build/tools/device/mkvendor.sh" file is missing so I can not create my on device. I tried to manually edit the files, but without success.
Now I have two virtual machine, one with CM12 source code and one with Omnirom 5.0 source code.
Click to expand...
Click to collapse
In the error it mentions recovery.*.img so try searching that as well.
(Not sure if it matters, but who knows, maybe you will get lucky )
Sent from my D620r [CM12]
Hi
Hi my name in Claudiu and i have a Lg g2 mini LTE d620 europe version. I root my phone and now i want to install an custom recovery like twrp . But i don t know if your recovery will work on my phone . It is for lg g2 mini d620 R or 620 ?
FarfaraClau said:
Hi my name in Claudiu and i have a Lg g2 mini LTE d620 europe version. I root my phone and now i want to install an custom recovery like twrp . But i don t know if your recovery will work on my phone . It is for lg g2 mini d620 R or 620 ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=57864611
Also, here is TWRP 2.8.3.0: http://forum.xda-developers.com/showthread.php?t=2990196
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Hi
Vagelis1608 said:
http://forum.xda-developers.com/showthread.php?p=57864611
Also, here is TWRP 2.8.3.0: http://forum.xda-developers.com/showthread.php?t=2990196
Happy new year to everyone on the forums!
Sent from my D620r [CM12]
Click to expand...
Click to collapse
Thank you for your answear . Now i must ask you i can know if my bootloader it s lock or unlock ?My phone it have an unlock gsm carrier but the rom it s branded by vodafone And if it s lock how can i unlocked ? Or should to flash the recovery.img and if it work`s it s unlocked . If it dont work it lock and flash the back-up of stock recovery back
FarfaraClau said:
Now i must ask you i can know if my bootloader it s lock or unlock ?
Click to expand...
Click to collapse
Your bootloader is locked and if you want to flash custom recovery first you have to unlock the bootloader.
Sent from my SM-T310 using XDA Free mobile app
Hi
Do you know how to unlock my bootloader ? I do that before a Htc one mini but this lg it s wird i dont know how to do that
powermetza said:
On my phone the error appears only when I reload theme (from Advanced settings), and I don't see any reason to reload the theme.
In recovery.log the error appear:
I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)
E:Failed to load package.
I:Attempting to reload stock theme...
I:Loading package: TWRP (/res/ui.xml)
And from this error I understand that the recovery try to load ui.zip from internal storage. The ui.zip does not exist, so it is normal that there is an error. The problem is why the recovery try to load ui.zip, because it does not need it (I think so, because the recovery works without it). If I have time, I will try to fix this problem. Now I am trying to compile TWRP 2.8.3.0 (without success until now) and I have only a few days off before I have to go to work (job).
If you have any idea to solve this problem please let me know. And thanks for your help.
Click to expand...
Click to collapse
Hi, i have the same issue on twrp 2.8.7.0 from mobile Uncle Tools. The phone is a xiaomi redmi note prime 2. The recovery is working. Has anyone knows how to fix it?
Related
TWRP for Transformer Pad TF201T
{
"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"
}
MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1
Changelog 2.7.8.2
- All Upstream changes
- Small changes to the 'new theme' (thx z31s1g)
- Added flash to staging partition, via flash image feature.
Changelog 2.8.7.1
- Removed ability to flash raw .img files....
- gui: keyboard: support longpress label offset, code cleanup ( Thx @_that)
- Added flashable zip
- merged upstream changes
Changelog- 2.8.7.0
- Fully merged 2.8.7.0 source from upstream
- Removed SU from twrp ( Its useless & only takes up extra room)
Changelog- 2.8.6.5
- New theme fully implemented ( Huge thx to @z31s1g ) Still a WIP
- Fix mount -o bind error on recreating /data/media/0 (Huge thx to @xiaolu ) & ( @_that )
- All upstream merges by Team Win
Changelog 2.8.6.1
- GUI: Prevent duplicate page overlays. Thx Matt & _that
- Replace legacy DEVICE_RESOLUTION with the new TW_THEME
- Using new common repo to build recovery.
- Build with grimlocks-5.1 kernel from zombi
- All upstream changes. Thx TeamWin
Changelog- 2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Changelog- 2.8.5.1
- Added dock sd card support to twrp
Changelog- 2.8.5.0
- Added formatting of ext sdcard for ROM2SD & DATA2SD
- Added ability to backup ext sdcard partitions
- Added reboot to recovery & reboot to bootloader from with TWRP
- Fixed error formatting /data to f2fs <- Thx Dees Troy for this fix
- A few upstream changes
Click to expand...
Click to collapse
UPGRADE INSTRUCTIONS----------------------------------------------------------------------------------------------------------------------------------------
- Flashing recovery with fastboot
- Boot tablet into fastboot.
Code:
fastboot -i 0x0B05 flash recovery foo.img
- Replace foo with the file name.
- Once flashed reboot into bootloader.
Code:
fastboot reboot-bootloader
- Enter recovery.
----------------------------------------------------------------------------------------------------------------------------------------
- - Flashabale zip
- Boot into current recovery .....
- Flash the zip it is signed so turn that on ......
- Reboot in to android, fully
- Boot into bootloader, enter newly flashed RCK ....
----------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
TWRP for TF201T [KANG], Tool/Utility for the Asus Eee Pad Transformer Prime
Contributors
lj50036, hardslog
Source Code: https://github.com/zombi-x-lp
Version Information
Status: Testing
Created 2015-03-06
Last Updated 2015-03-06
DOWNLOADS
OLDER VERSIONS
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] WILL UPLOAD
The more you know
JOIN US ON IRC !!!https://webchat.frt/
Channel: #zombi-x
HOW TO TAKE A RECOVERY LOGYou will be taking this log cause of some kind of error message .....
Once you get and error message, here is how to retrieve a recovery log ....
Using a PC with adb/fastboot installed on it, and if windows the correct drivers. ....
Code:
adb pull /tmp/recovery.log
This log will be in the same directory as the terminal/cmd window is cd'd into ....
Now you have the log, upload it to a pasting site or for download, and give us a link....
lj50036 said:
it may appear to hang on the twrp curtain, let it boot there is nothing wrong here
Click to expand...
Click to collapse
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
flumpster said:
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
Click to expand...
Click to collapse
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
lj50036 said:
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
Click to expand...
Click to collapse
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
https://www.androidfilehost.com/?fid=95916177934537081
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
Got it if you would like to pull the download your call ....
Yes I will go back to stock bootloader then upgrade .....
Will let you know how I get on ....
Thx Josh
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Lavrentsii said:
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Click to expand...
Click to collapse
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
lj50036 said:
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
Click to expand...
Click to collapse
Cheers mate. I am in bed at the moment but I will make you another test tomorrow with your recovery added into it for you to try.
lj50036 said:
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
Click to expand...
Click to collapse
I'm testing DATA2SD on a non-supported ROM (Katkiss LP with Grimlock 300t/201 kernel) and so far with this recovery and the DATA2SD zip it seems to be working fine. This looks pretty promising
lj50036 said:
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
Click to expand...
Click to collapse
I can confirm that this works thanks to Josh's help/instruction on doing it. He is an awesome & great teacher as I learned so much from him. GREAT RECOVERY! Thanks again Josh! :good:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
elchevi said:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
Click to expand...
Click to collapse
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
lj50036 said:
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
Click to expand...
Click to collapse
Maybe choosing among some predefined templates would do the trick for most users. But yes, it can be potentially problematic hehe
Thanks!
Img vs. blob
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
JuraP said:
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
Click to expand...
Click to collapse
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
lj50036 said:
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
Click to expand...
Click to collapse
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
JuraP said:
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
Click to expand...
Click to collapse
It does not matter you can leave it .img or rename it .blob will not matter ....
Thx Josh
Helloo.. what's up guys...
I'm so sorry. Long time no post.. hehe
Today i'm gonna share custom recovery (again) for Samsung Galaxy V SM-G313HZ aka vivalto3gnvdx. This custom recovery called TWRP 3.0.
Quoted from official website :
Screenshots :
{
"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"
}
What’s new in 3.0.2-0:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
Link : Since our device officially supported by teamwin, then all updates can be downloaded directly to the official website TWRP on the vivalto section here
Old build :
What’s new in 3.0.0-0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
Link :
Odin version
Flashable version
Changelog :
Fix MTP
Thanks to Allah SWT
Credits :
Team win
Cleverior
corphish (for his clue to fix MTP)
And you...
DO WITH YOUR OWN RISK !!!
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
PLEASE PUT THIS POST AS SOURCE. THANKS
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
doesntexits said:
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
Click to expand...
Click to collapse
Ok.. thanks for correction.
MTP is detected but can not mount. In adb, device is in recovery status. not in device status. is this same with you ?
screenshot of adb is attached.
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
doesntexits said:
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
Click to expand...
Click to collapse
There is no custom lun in my boardconfig. Maybe i can try to add it later. And the correct lun file location is in /sys/devices/virtual/android_usb/android0/f_mass_storage/lun .
I'm using TWRP source from omni source.
adb shell is working bro. Now your problem is MTP only.
doesntexits said:
adb shell is working bro. Now your problem is MTP only.
Click to expand...
Click to collapse
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
cleverior.ipul said:
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
Click to expand...
Click to collapse
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
doesntexits said:
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
Click to expand...
Click to collapse
Ya, even using custom lun but still not working.
Update with fix MTP
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
which version of firmware do u use ? have u try to install twrp using odin ?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
If you install TWRP from Odin, make sure you've choose .tar file as PDA, if not the recovery won't be installed
There's no way to install it through stock recovery, since it always gives "E: Signature verification failed".......
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Kazryu said:
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Click to expand...
Click to collapse
When install custom recovery using Odin, don't tick auto reboot. After install successfully, pull your battery out, seriously!
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
doesntexits said:
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
Click to expand...
Click to collapse
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
cleverior.ipul said:
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
Click to expand...
Click to collapse
It adds f2fs support for TWRP recovery, so we can flash other ROMs with f2fs partition support
I cannot use `adb shell`, can you use it?
---------- Post added at 14:33 ---------- Previous post was at 13:57 ----------
In TWRP 2, I remove all adbd control scripts in init.rc, just leave adbd service def, then in init.recovery.scx15.rc:
Code:
on init
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct D002
write /sys/class/android_usb/android0/functions [B]mtp,mass_storage,adb[/B]
# adb won't work in OSX without this
write /sys/class/android_usb/android0/bDeviceClass EF
write /sys/class/android_usb/android0/bDeviceSubClass 02
write /sys/class/android_usb/android0/bDeviceProtocol 01
[B] export PATH /sbin:/system/bin
export LD_LIBRARY_PATH .:/sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /external_sd
write /sys/class/android_usb/android0/enable 1
start adbd[/B]
So now I can use adb shell and MTP in TWRP 2.
Dude, on the TWRP Official Site I see it is in version 3.0.2-0, so it is safe to install that version and you will update this thread to the new version ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bismillahi Alrahmani Alraheem
(in the name of God the most gracious, the most merciful)
Finally Unoffoicial TWRP 3.0.2 is here for Dual sim version of XPERIA Z3 (D6633)!!
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
And much more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
Notes About Sony Devices:
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here:
https://github.com/Dees-Troy/extract_elf_ramdisk
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
DOWNLOAD:
Please notice that it won't work in stock based roms, only custom roms will run it
20160907 (img)
20160907 (zip)
Installation methods
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/recovery-twrp-302-z3dual.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Fastboot method:
you should have fastboot in your pc (either downloaded separately or with android SDK)
fire up Terminal (Linux and OS X) or CMD window (MS Windows) in the folder you have the image on it and it is preferred to copy the image to the folder of fastboot so the following command work then type:
Code:
fastboot flash FOTAKernel recovery-twrp-302-z3dual.img
don't forget to put ./ before 'fastboot' if you are using OS X or linux (./fastboot)
ZIP method:
flash the zip using any recovery
Themes and colors:
HERE
(Read Post #2 in the link if you want to customize, I'll be making pre-made themes later on inshaaAllah (God willing) )
NOTE: You are free to repack it and even sharing it without taking my permission
Please Donate If you want me to support Z3 dual more and more, it is back to you
XDA:DevDB Information
TWRP 3.0.2 for Z3 Dual D6633, Tool/Utility for the Sony Xperia Z3
Contributors
Muhammad Ashraf
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Testing
Created 2016-06-25
Last Updated 2016-09-07
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
sorry for the late reply, I am not sure why does it act like that
i'll try to make a zip file for that issue
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Oh, I am SOOOOOOOO Sorry, You have noticed me, By mistake I have uploaded Cyanogenmod Recovery instead of twrp
figuring that out now
I am sorry all of you
thanks man
EDIT: DONE
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Unlocked or Locked bootloader?
(Does this require an unlocked bootloader?)
I cannot get to recovery mode using DD or fastboot
Command will go through but adb reboot or h/w combos wont get me recovery. How do I install recovery ? . I have a ROM that can only be installed via recovery pl help
I cannot get to recovery mode using DD or fastboot
FAILED (remote: Command not allowed)
it always says "FAILED (remote: Command not allowed)"
should the bootloader be unlocked ?!
what is the problem here?!
Hi, i flashed the .img using my twrp, the only option on "select partition" was kernel, i know i shouldn't have done it, but i did. Now the phone doesn't boot, it keeps on a black screen. I think i need to flash a new kernel, can someone help me? Thanks
edit
Locked bl
Excellent WORK +++++
Bismillahi Alrahmani Alraheem YOU are my god!
Well done. You are the man. Exellent work with this TWRP for my D6633 (z3 dual)
it saved my life!
bryantshurley said:
I cannot get to recovery mode using DD or fastboot
Click to expand...
Click to collapse
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
"fastboot flash boot recovery-twrp-302-z3dual.img" got me to a new recovery screen and can no longer boot the system.
rzepek2pl said:
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
Click to expand...
Click to collapse
That was a bad advice. Now I only have TWRP on my phone. Only boots into this!
Can it be saved? How?
Your 20160907.zip based on TWRP 3.0.2 was put into root & flashed with TWRP v2.8.7.0 which did not update, when re-launching recovery I was still on v2.8.7.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
Unlocked Honor 7x : See this [But don't flash twrp from anywhere else before backing up your device. Use twrpimgmount_ramdisk for backing it up first.]
Download:
TWRP Complete Backup
TWRP Img mount not tested yet
Instructions:
Flash twrpimgmount_ramdisk.img through fastboot
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
Press and hole both volume + power on to boot to erecovery OR volume up + power on to boot to twrp (i don't know which combination is of which one) i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Backup/restore and flash image functions are tested for system/vendor/product/version/cust/oeminfo/recovery/recovery2/boot rest of them are not tested by me but should work.
Note: It is suggested to make a complete backup in memory card before rooting your Honor 7x.
After backing up, flash TWRP Complete Backup Ramdisk
Join Telegram group if you are willing to test latest stuff
Credits:
Ported form Honor 6x : OP
Follow next:
1. Flash Magisk 16.0+ to root
XDA:DevDB Information
[OREO]TWRP COMPLETE BACKUP, Tool/Utility for the Honor 7X
Contributors
Sudeep Duhoon, Pretoriano80, zxz0O0
Version Information
Status: Testing
Created 2018-03-17
Last Updated 2018-04-07
For Nougat : Go Here
Reserved
TWRP on my OREO Beta Not Detecting My Phone on Pc no Response Please Check Ur Recovery
Can I do this with the Bnd-L24 model that has the bootloader unlocked with TWRP installed?
Great bhai
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Sudeep Duhoon said:
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Click to expand...
Click to collapse
one further note, using the "complete_twrp_ramdisk.img" TWRP was able to see the installed OS, and offered to install the TWRP app.
Sudeep Duhoon said:
i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Click to expand...
Click to collapse
What does this mean?
---------- Post added at 10:08 AM ---------- Previous post was at 09:36 AM ----------
I couldn't get it to backup. It always fails at data or system (If I don't select data).
Tried both images.
how can i flash the stock recovery? i was able to brick my device
Edit: nvm i fixed it
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Hi, I'm glad to report that although the first recovery that is twrpimgmount_ramdisk.img failed to backup system as I got the same error message as above but I was able to flash some other partitions like kernel, recovery etc... I actually selected a bunch of them.
Anyway most importantly after flashing the complete_twrp_ramdisk.img, I was able to backup system successfully. I'm using the Indian variant BND AL10 MODEL. I hope this helps some one out there.
I have a dumb question: Now, that the system is backed up with twrp, if I mess up my phone ever, can I simply restore this system img and be able to boot back into the os? Do I need to install any other partitions? I don't care about data. Please let me know.
Hi, I flashed this complete_twrp_ramdisk.img and now I want to go back to stock recovery of oreo which is bnd_recovery_nocheck.img from the other post. I tried using adb and it fails. I tried using the this twrp but it shows a lot of partitions to choose from and I'm confused example: ramdisk recovery, recovery_vendor, recovery_ramdisk etc... there are sooooooo many. I tried recovery_vendor and also ramdisk but it doesn't work. Can you please tell me how to install the stock recovery?
Does anybody have a BND-L21 backup of the system partition?
Edit: nvm i found it
Can someone tell me how to install stock recovery after installing the above complete_twrp_ramdisk.img as I'm unable to flash using adb. I tried "fastboot flash recovery recovery.img" and also "fastboot flash recovery_ramdisk recovery.img" I tried flashing the BND_recovery_nocheck.img from the other post which is a stock one.
I also tried flashing it using this twrp to the partition recovery_ramdisk and gives the error saying "the size is larger than the device" Please someone help.
I have tried couple times to install new release
twrp_ramdisk_oreo_7-4-18.img
Click to expand...
Click to collapse
But I can only get to twrp splash screen.
OP change-log has no information about this new release, so maybe is still not ready.
telegram group has mention of this , but did not help Yet.
**EDIT**
It was suggested by DEV in telegram to just be patient and try again. This third time installed 4-7-2018 released version it loaded right into recovery, without any delay.
Don't know if it is coincidence or not but before I was on RRos ROM. and now I am back on EMUI 8
Well, the mess here you have gentlemen, nichrome you do not understand where the root for 7ku, where to 8ku, what tvrp to put for 8ki for everyday needs.
---------- Post added at 03:56 PM ---------- Previous post was at 03:52 PM ----------
Which TWRP can I put in order to flush the root on the 8th oreo?
What TWRP should I be using on RROS Room? In order to install Magisk?
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
darkmage1991 said:
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
Click to expand...
Click to collapse
Afaik they are test builds (ports) of data decryption enabled twrp.
I had them working when on the Oreo beta but cannot get to work on RR or the new official Oreo.
Source: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/ The author wrote this: all issues fixed!
Thanks to the developer for the energy and time. Developer: wzsx150.
This is a working unofficial TWRP recovery for Redmi 9 for Miui 11. Tested on android 10, Miui Global 11.0.6 rom.
Miui 12 is work? I do not know. Everyone doesn't know. It probably won't work.
Original file: https://www.mediafire.com/file/auj2wh2lh8lzp47/3.4.2+Redmi+9+CN+EN.rar/file I modified this a bit.
What is required for installation:
Twrp img (blue) (recovery.img): Download
vbmeta_redmi9.img Download
1: Unlock bootloader
2: installed adb & fastboot drivers Download
3: Optional: Mtk usb driver Download
3a: Let the phone battery be charged to more than 50% !!!
(4: Everyone is at their own risk)
(5: Backup all data, recommended. Save idea 1, Save idea 2
6: Turn off the phone
7: Then press the volume down button + power on button to enter fastboot succes fastboot screen
8: Now connect your phone to your computer (windows emits a connection sound)
9: Open one a cmd/command line, where you downloaded the files cmd
10: Issue the two commands one after the other
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta_redmi9.img
11: You ready. Restart the phone in recovery mode
fastboot reboot recovery
12: If you did everything right, this picture will welcome you
12.a: If recovery asks you for a security pattern, enter what you use on your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12: If you messed up something, don't worry. Someone here will help. (It can usually be restored with Adb or fastboot, which is broken)
13: A few pictures of the program
14: Four colors are available: blue, red, brown, purple.
Blue TWRP Recovery: Download
Red TWRP Recovery: Download
Braun TWRP Recovery: Download
Purple TWRP Recovery: Download
For now, only Chinese and English language are available! The other languages are being prepared. Soon. As there will be time for it.
It doesn't hurt to have these:
Qualcomm HS-USB QDLoader 9008 Driver 64-bit [Windows] Qualcomm driver
MediaTek MT65xx Preloader VCOM USB Driver [32-bit & 64-bit] Mediatek Vcom driver
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 Adb & fastboot drivers
MTK usb driver Download
SDK Platform tools Download
Google usb driver Download
Thanks for watching. If you liked my job, you can invite me for a beer.
Paypal: [email protected]
Crypto: 3FJuZGaw98oefj45AiypytaJzyATuRn7dE
Reserved
I saw this at telegram yesterday
Is this updated version?
SunuWijaya said:
I saw this at telegram yesterday
Is this updated version?
Click to expand...
Click to collapse
Where did you see that? (I don't understand) Two versions of this have been made. This is the second.
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
-CALIBAN666- said:
short question,what have you modified and how did you testet which things,we have no custom rom,what about backup and restore,did you testet,what about flashing zips in general and are all partitions rw?Thanx!!!!
Click to expand...
Click to collapse
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Other. For everyone. It also became a fifth skin. Orange / black. Download
------------------------------------------------------------------------------------------------------------------------------------------------------------------------It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Can dis twrp flash kernel?
Meggyi said:
Hello. Well ... there weren't many tests available yet.
What I modified:
1: Skins / colors
2: Spelling mistakes
3: Syntax errors 2-3 pieces
What I was able to test in recovery:
1: Install zip / img: works
2: Backup and restore partition / data: works
3: Mount partitions: works
4: Wipe / advanced wipe: works
5: Reboot "all: works
6: Terminal: works
7: ADB Sideload: works
8: File manager: works
9: Settings "all works, except multilanguage.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Other. For everyone. It also became a fifth skin. Orange / black. Download
View attachment 5164259
------------------------------------------------------------------------------------------------------------------------------------------------------------------------It's different again. For everyone. I noticed a mistake yet. I haven’t used recovery in a long time, so I didn’t notice the error. After a while, twrp recovery disappears. And the original recovery will be again. I don't understand why .... If you twrp recovery in flash fastboot mode again, you have twrp again. For a while.
Click to expand...
Click to collapse
Ok,big thanx for info.Cheers!!!
SunuWijaya said:
Can dis twrp flash kernel?
Click to expand...
Click to collapse
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Just try to flash stock kernel
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Meggyi said:
Does it have a custom kernel? Modified kernel? Has anyone tried kernel flash? I don't think so. (Zip and img flash, it knows) Do you know of a modified kernel?
Click to expand...
Click to collapse
Yes it is have custom kernel named Minati-Xenodrome
How to use twrp to flash GSI ?
-CALIBAN666- said:
Afaik the issue with the missing twrp recovery is normal and only on miui based rom,on custom roms there is no issue like that.Most Xiaomi/Redmi devices do that.
Click to expand...
Click to collapse
Yeah, I get it. I didn’t have many phones that miui had. That makes sense. Stupid miui
Good job....I flash custom kernal...and it successful...but can this twrp able to go fastbootd as you mentioned and flash gsi like stock recovery?
Have you flashed a rom?
The solution for the issue that twrp is gone after some times is to flash the no-verity-opt-encrypt file for the device directly after flash of recovery,after this twrp is permanent,for the file check source link in first post.Cheers!!!!
Thank you very much, but my Redmi 9 China version cannot boot after flashing into twrp.
On Redmi 9 China version, I sorted out this version to be available.It seems that it can only be used for MIUI11
zhihuiyuze channel
论坛附件,Redmi9 twrp且可以在中国版使用
t.me
Google Drive Education Edition cannot share files (so use Telegram
There is another problem. It seems that if I use your modified version, /cust fails.
What we can do with this TWRP on lancelot?
I have the Redmi 9 (lancelot) with MIUI 11 installed. My bootloader is unlocked, I've the adb & fastboot drivers installed. I would really like to install that TWRP. While I'm flashing both files, cmd gives no errors, everything is fine. But at the end, I can not boot into recovery with "fastboot reboot recovery" from the cmd, it gives me an error. If I leave fastboot mode and try to enter TWRP manually by holding the volume and power key, it doesn't work. My device will get stuck inside a bootloop.
I'm able to fix the bootloop with disabling DAA & SLA protection in the MTK mode and flashing back the stock firmware with SP Flashtool. I tried it 3 times, every time the same issue and having to flash back the stock firmware. Do you have any tips to fix that? Or is there another or updated version I could try?
Edit: Nvm, got it working