Changes

no edit summary
Line 258: Line 258:  
To modify the Device brand, you can make use search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, you can find the TWO files from route below:
 
To modify the Device brand, you can make use search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, you can find the TWO files from route below:
   −
First File:
+
'''First File:'''
    
  ~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin
 
  ~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin
Line 264: Line 264:  
[[File:SVG1.jpg|border|class=tlt-border]]
 
[[File:SVG1.jpg|border|class=tlt-border]]
   −
Second File:
+
'''Second File:'''
    
  ~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/ tlt-icons
 
  ~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/ tlt-icons
Line 274: Line 274:  
[[File:DubaiNetworks.png|border|class=tlt-border]]
 
[[File:DubaiNetworks.png|border|class=tlt-border]]
   −
Note: If you have a brand in a different format, you can convert it to SVG using any online converter, please keep in mind that online converters can cause scalability issues.
+
'''Note:''' If you have a brand in a different format, you can convert it to SVG using any online converter, please keep in mind that online converters can cause scalability issues.
    
and then compress it to .gz file as per screenshot below:
 
and then compress it to .gz file as per screenshot below:
Line 298: Line 298:     
==Changing Device Logo==
 
==Changing Device Logo==
 +
To modify the Device logo, you can make use search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, you can find the TWO files from route below:
 +
 +
'''First File:'''
 +
 +
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin
 +
 +
[[File:LOGO1.jpg|border|class=tlt-border]]
 +
 +
'''Second File:'''
 +
 +
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/assests
 +
 +
[[File:LOGO2.jpg|border|class=tlt-border]]
 +
 +
For example, I will use Burj Khalifa logo in order to perform the changes here.
 +
 +
'''Note:''' If you have a brand in a different format, you can convert it to ico using any online converter, please keep in mind that online converters can cause scalability issues.
 +
 +
After making changes and saving them to the directory, we may build compile using the following commands:
 +
 +
1- ./scripts/feeds update -a
 +
 +
2- make clean
 +
 +
3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
 +
 +
The firmware can then be found in the directory listed below *Depends on the target*:
 +
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
 +
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
 +
 +
 +
'''RESULTS:'''
 +
 +
[[File:LOGORESULT.jpg|border|class=tlt-border]]
 +
 +
==Disclamer==
 +
It may not be necessary to update scripts and make clean after making firmware changes; this will depend on the changes undertaken. In these cases, the commands were used to assure clean compilation and the removal of any potential artifacts from previous environments.