[GUIDE]Porting TWRP without source

Search This thread

ulissesemuman

Member
Jan 1, 2022
7
0

@Augustoandro, I managed to port TWRP successfully on Aidan's ROM, thank you very much!​

But but the letters are all scrambled and the colors are strange, please see my video:​

I can still use the mouse and enter the options, but when I try to restore a backup, an error occurs in the partitions, but I can't see which partitions are in error because I can't read the text.​

Can you please help me to fix the text display? So I could see the errors and change the fstab correctly.​

 
Last edited:

Augustoandro

Senior Member
Jun 20, 2017
567
253
Pune
Micromax IN Note 1

@Augustoandro, I managed to port TWRP successfully on Aidan's ROM, thank you very much!​

But but the letters are all scrambled and the colors are strange, please see my video:​

I can still use the mouse and enter the options, but when I try to restore a backup, an error occurs in the partitions, but I can't see which partitions are in error because I can't read the text.​

Can you please help me to fix the text display? So I could see the errors and change the fstab correctly.​

There seems to be some incompatibility issue among the files you imported in the TWRP and the rest of the recovery.
Try porting with some other recovery, preferably one that has the closest or the same chipset as your target device.
 

Augustoandro

Senior Member
Jun 20, 2017
567
253
Pune
Micromax IN Note 1
I have a ZTE phone but unpacked image had ramdisk folder empty. i found recovery.img.ramdisk.cpio.gz file in split_img and some other files that as i know, aren't the right ones. i remember i also found a recovery.img-origsize file and some other weird files that include names like ramdisk and recovery. what to do now @Augustoandro?
Your img seems to have some issues, the ramdisk can never be empty.
Find a new img.
And about the files like ramdisk.cpio.gz which are part of split_img. DO NOT TOUCH THEM, EVER.
 

Cruel5anity

Member
Mar 15, 2020
20
4
There is no fstab.devicename or chipset... Any ideas if I can fabricate an fstab?
Skipped the fstab.device/chipset it booted to system but bootlooped when trying to boot to recovery... Might just send a copy of my recovery.img to your request thread...
 
Last edited:

ravijol1

Member
Oct 22, 2021
14
1
@Augustoandro now the problem is with default.prop. it contains this: 㰡祳汭湩㹫prop.default this is on both stock and twrp recovery. why is this and what to do?
 

Augustoandro

Senior Member
Jun 20, 2017
567
253
Pune
Micromax IN Note 1
There is no fstab.devicename or chipset... Any ideas if I can fabricate an fstab?
Skipped the fstab.device/chipset it booted to system but bootlooped when trying to boot to recovery... Might just send a copy of my recovery.img to your request thread...

There is no fstab.devicename or chipset... Any ideas if I can fabricate an fstab?
Skipped the fstab.device/chipset it booted to system but bootlooped when trying to boot to recovery... Might just send a copy of my recovery.img to your request thread...
There must be a recovery.fstab in your recovery. You can rename a copy of it as fstab.devicename.
 

blaze2051

Senior Member
Jul 26, 2010
372
37
LG G7 ThinQ
LG V40
@Augustoandro

Is it possible to use a ported twrp.recovery.img from a different unisoc device and use it to modify the oem boot.img AB dynamic on different unisoc device,? so ported iplay40 twrp recovery to stock boot.img on T803 ?

iplay40 has a recovery partition but the T803 does not have recovery partition only has boot partition. I trying to inject or patch the boot.img I cant used the fastboot boot twrp.img command on the unisoc it wont boot. so I have to patch the boot.img some how.

If i could use the fastboot method i could then use the feature install to ramdisk once i temporarily booted to twrp but that doesnt seems like its possbile i read somewhere unisoc and mediatek devices have this issue of termoprarily booting twrp.img from fastboot. google devices like ex. pixel 4 do not seem to have this issue.

i have managed to patch boot.img with magisk 23, but thats all iv done with the stock boot.img
 

Attachments

  • explorer_2022-01-31_14-02-43.png
    explorer_2022-01-31_14-02-43.png
    291.2 KB · Views: 21
  • cmd_2022-01-31_13-50-45.png
    cmd_2022-01-31_13-50-45.png
    35.2 KB · Views: 20
Last edited:

gentle_giant

Senior Member
Aug 1, 2011
131
111
So-Por
HTC 10
HTC U11+
@Augustoandro
what exactly do you mean with: "19. Edit the twrp.fstab file according to the newly pasted recovery.fstab.
Simply delete all the lines in the twrp.fstab and replace them with all the lines from recovery.fstab?

Also, would the official TWRP for the HTC U12+ be a good starting point? I got hold of a very newish HTC U11+ for a very good price.
They both started with Oreo and got an upgrade to Pie and they have the same screen resolution (1440x2880)

Sorry for the noob questions..

Edit: spelling and added a question.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    Yes, I know XDA is filled with such guides.
    But you can only port a TWRP if you implement parts of all the guides.
    This guide is a summation of all those guides.

    NOTE:
    I would be using AIK-Linux in this tutorial, since I don't recommend Windows for all this, who knows what problems you will get into.

    REQUIREMENTS:
    1.Download these TWRP recoveries in accordance with your screen resolution.
    A. If your screen resolution is 480x850, 480x854; download
    https://twrp.me/lg/lgnexus4.html
    B. If your screen resolution is 720x1280, 800x1280 or 720xsomething; download
    https://twrp.me/asus/asusnexus720123g.html
    C. If your screen resolution is 1080x1920, download
    https://twrp.me/motorola/motorolanexus6.html
    2. Download Android Image Kitchen-Linux from this thread:
    https://forum.xda-developers.com/showthread.php?t=2073775

    LET'S BEGIN:
    1. Unzip Android Image Kitchen zip file.
    3. Now, navigate to the unzipped folder of AIK (Android Image Kitchen).
    4. Just Right Click and select "Open Terminal here".
    5. Copy and paste your stock recovery.img and paste it in AIK folder.
    6. In the terminal, type the command
    Code:
    su
    Enter your root password, then type
    Code:
    ./unpackimg.sh
    7. This will unpack your stock recovery.img. Do not close the terminal.
    8. Cut the new folders, ramdisk and split_img, and paste them somewhere outside of AIK folder.
    9. Remove the stock recovery.img in AIK folder.
    10. Now, copy and paste the twrp_recovery.img according to your screen resolution in the AIK folder.
    11. Now, revert back to the terminal and type
    Code:
    ./unpackimg.sh
    12. This will unpack your twrp_recovery.img
    13. Delete all the files in the new split_img folder we got by unpackimg twrp_recovery.img
    14. Copy and paste all the files in stock split_img folder to the new split_img folder.
    15. Delete following files from new ramdisk folder.
    A. default.prop
    B. fstab.devicename_or_chipsetname
    C. ueventd.rc
    D. Any other file like ueventd.devicename.rc
    16. Copy and paste these files from stock ramdisk folder to new ramdisk folder.
    Code:
    default.prop
    fstab.devicename
    ueventd.rc
    17. Now go into stock ramdisk/etc folder and copy recovery.fstab
    18. Paste the recovery.fstab file in new ramdisk/etc folder.
    19. Edit the twrp.fstab file according to the newly pasted recovery.fstab
    20. You will have to replace"/sdcard" with "/external_sd" and "/usb" with "/usb-otg".
    21. If the partitions stated above are not available in your fstab files then add these lines. Order may change on the format in which the files are written.
    Code:
    /external_sd          vfat         /dev/block/mmcblk1p1  flags=removable;storage;display="SDCARD"
    /usb-otg                auto         /dev/block/sda1    flags=removable;storage;display="USB-OTG"
    22. Edit the following lines as shown in default.prop
    Code:
    ro.secure=0
    ro.adb.secure=0
    security.perf_harden=0
    ro.debuggable=1
    persist.sys.usb.config=adb,mtp
    23. Now, come out of the ramdisk folder and open the terminal.
    24. Type
    Code:
    ./repackimg.sh
    25. Your new TWRP img would be generated and named as image-new.img by default. You may change the name later.

    When you have successfully built the TWRP, or if you want to request one instead of creating yourself, contact me on this thread:
    https://forum.xda-developers.com/android/general/unofficial-twrps-devices-source-code-t3833338


    SPECIAL INSTRUCTIONS FOR MEDIATEK DEVICES:
    1. The recovery.fstab you will get after unpacking your stock recovery.img would be flawed in most cases. I believe OEMs do this deliberately.
    2. In order to know which partition is mounted at which location and at which device, you'll need DiskInfo (Install it from Play Store) and a root explorer.
    3. Enable the following Diskinfo settings:
    Code:
    Show mount path
    Show partition name
    Show file system
    Expert mode
    Unmounted partitions
    Device Mapper partitions
    Temporary filesystems

    4. Use the root explorer to find the path of your partitions. They would be located under /dev (mtk devices have bootimg and recovery here generally) and some other partitions like /system, /cache would be deeper inside.
    5. You can trace their exact locations by navigating within the /dev directory for partition names like mmcblk0p5.


    SPECIAL INSTRUCTIONS FOR DEVICES THAT DON'T HAVE RECOVERY.FSTAB WITHIN STOCK RECOVERY.IMG
    1. In the ramdisk/etc folder, there might be a dummy recovery.fstab file with the symbol of link on it.
    2. Right click on the file and select "Show Target". You'll get to know the path of original recovery.fstab file. It might be within the unpacked recovery or inside some other partition on your phone.
    For example: Honor 7C devices have their recovery.fstab in /vendor/etc folder.

    TROUBLESHOOTING INSTRUCTIONS:
    1. If you get a dm-verity error or facing an encryption problem, go to this thread and flash the "dm-verity and forceencrypt disabler zip".
    https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
    2. If you encounter a bootloop while booting into your new TWRP, please consult post #20 of this thread.
    3. At times, the path of partitions during recovery boot is not the same as those during normal boot. That's why you may get errors like
    Code:
    Updating partitions details...
    Failed to mount '/cache' (Invalid argument)
    Failed to mount '/system' (Invalid argument)
    Failed to mount '/data' (Invalid argument)
    Failed to mount '/metadata' (Invalid argument)
    ...done
    Unable to mount storage
    Failed to mount '/data' (Invalid argument)
    To resolve this, in your TWRP terminal type the following command
    Code:
    find /dev/block -name by-name
    Replace the paths of the partitions in your fstab files with the ones you get as output using the command above (only the partitions which failed to mount).

    If there are some bugs or you need some assistance in porting TWRP, contact me by mentioning in your post, for example @Augustoandro, we'll work on it to make it bug-free.

    Special thanks to @aIecxs for his troubleshooting instructions of bootloop, "Failed to mount /partition_name (invalid argument)" error and also @inguna for guiding me on how to fix the "SDCARD not detected by the TWRP" problem and also fixing the MTP, ADB not working issue.
    Another thanks to @seanybiker and @avirus for their troubleshooting instructions on "DM-Verity and forceencrypt" errors.

    CREDITS:
    @HostZero for his porting guide.
    @osm0sis for his awesome Android Image Kitchen
    @Zackptg5 for his "DM-Verity and Forceencrypt disabler zip".
    3
    Can't find fstab.devicename in stock ramdisk folder. btw phone is samsung a41 (sm-a415f) @Augustoandro
    This happens sometimes. Some devices directly reference the recovery.fstab file instead of fstab.devicename.
    Edit the rest of the files and proceed further.

    HIT THANKS IF FOUND USEFUL
    2
    SuperSU or Magisk won't install into system but into boot and data

    in TWRP you have a terminal. type
    Code:
    ls -ld $(find /dev/block -name by-name)/*
    you can manually mount, all you need is a folder as mount point
    Code:
    mkdir /system_root
    mount /dev/block/bootdevice/by-name/system /system_root
    mount
    2
    Pls brother help me port twrp for my device. Here is my stock recovery image link : https://drive.google.com/file/d/1dqBU4f0ZXK8Ot0V9t-4Tw6f_60UHg7ca/view?usp=drivesdk.
    My phone's resolution : 720 x 1280 pixel.
    This is not a TWRP request thread. I have included a link in the guide which takes you to a TWRP request thread. Post your request over there.

    HIT THANKS IF FOUND USEFUL
    2
    Hi I tried to Port a Recovery for my H96 Max RK3399 TV Box .
    I used TWRP From My RK3328 TVBox.
    I can Boot in Recovery, but its not Mounting any Partition (everywhere 0MB)
    I Think the problem is in .Fstab File but I am Not sure.
    I would appreciate help

    Sorry for my poor English
    Partitions not being recognized means the problem is in fstab files. Both recovery.fstab and twrp.fstab need to be edited.
    I am sure of it.

    HIT THANKS IF FOUND USEFUL