EVO-MINI-ufs910-e2-3p1-1749_GoForIt

Status
Not open for further replies.

juli13

Staff member
Administrator
Messages
10,198
Code:
3p1 FLASH IMAGE FOR UFS 1749-MINI-910! 


Windoze USER FOR THE NO FLASH IN THE MINI-SUBMARINE HAVE ONLY flashable WITH THE FLASH SUITE 1.2.8 
(possibly also with older Flash ner Suite version, but without guarantee!) 

WHAT IS EVO-MINI: 
THEREIN IS THE SO-CALLED BY MINIUBOOT "solala (FAT THX AGAIN) INCLUDED! 
SO IT IS POSSIBLE VIA RC BOAT ON HIS IMG CHOOSE WHAT IS STARTING TO, WHETHER FLASH, USB OR NFS! 

THIS SHOULD BE MADE ONLY IN THE bootargs FLASHUITE IN 3P1MINI.TXT ADJUST AND THE EVO *. IMG DEPOSITED IN FLASH SUITE FOLDER. 
THERE ARE POSSIBLE ENTRIES FROM 0-9! (GO TO CONFORM. TXT FILE) 

THEREIN BEFORE BOOTARGSÜBERTRAG AND ONLY VERY UP YOUR IP, GW, ServerIP, NETMASK 
ADAPTED FROM YOU ARE ALREADY CAN Flash and ARGS TRANSFERRED, AND EVEN THEN it boots DIRECTLY FROM WHERE TO FLASH VIA JICH RC CHOOSES WHAT ELSE! Bootargs EXTENSIONS FOR EITHER THE EVO IMG FW_SETENV STOP THE USE OR TXT MODIFY AND AGAIN TRANSFERRED. 
OBIS INSTRUCTIONS FOR VARIOUS WAYS TO FIND UNDER "INSTRUCTIONS" HERE AT THE BOARD! 

new in mini1.2-final: 
emerg is back, it can now flash if the mini is back to normal from usb flash stick. 
give you more information in the download thread to the mini-1.2-final here and here 

who is already a mini-evo-img in flash can also have the mini-1.2-final preliminary "flash" to flash then the evo-mini-1730.img as in the mini-thread explains via usb-stick to then! 
it simply an old evo-mini can (eg boot 1501) and the copy miniUPDATE.img by means of ftp / tmp ufs, but kill only after: 
telnet: Quote: 
killall -9 rcS 
killall -9 enigma2 




Now after mini tmp directory via ftp and then: 

at evo images: Quote: 
dd if = / tmp / miniUPDATE.img of = / dev/mtdblock5 




aaf in images: Quote: 
dd if = / tmp / miniUPDATE.img of = / dev/mtdblock6 




HOW IS THE ONLY IF YOU ALREADY TOLD DE EVO IMG WITH MINI IN reflashing Did! 

then after that is also this: quote: 
direct flashing with mini: 
if one of nem on an internal SATA or USB stick or on TFTPserver nem a full-image 
by name: 
miniFLASH.img 
( 
evo_mini_1749_ufs910_flash.img unpack it and rename *. img Going!) 
test (size 15.8 MB) and the Boxstart the REC button is pressed holds approximately 3 seconds (until "FLASH mini search" in the display) appears, then the miniFLASH.img searched in the media. Once it is found, it is loaded and flashed. FAT32 or ext2 does not matter on the stick ... miniFLASH.img has only the root of the partition are FIRST, then 0:1 to USB or IDE 0:1.
 

juli13

Staff member
Administrator
Messages
10,198
evo_mini_1749_RC2_ufs910_flash_3

Code:
3p1 FLASH IMAGE FOR UFS 1749-MINI-910! 


Windoze USER FOR THE NO FLASH IN THE MINI-SUBMARINE HAVE ONLY flashable WITH THE FLASH SUITE 1.2.8 
(possibly also with older Flash ner Suite version, but without guarantee!) 

WHAT IS EVO-MINI: 
THEREIN IS THE SO-CALLED BY MINIUBOOT "solala (FAT THX AGAIN) INCLUDED! 
SO IT IS POSSIBLE VIA RC BOAT ON HIS IMG CHOOSE WHAT IS STARTING TO, WHETHER FLASH, USB OR NFS! 

THIS SHOULD BE MADE ONLY IN THE bootargs FLASHUITE IN 3P1MINI.TXT ADJUST AND THE EVO *. IMG DEPOSITED IN FLASH SUITE FOLDER. 
THERE ARE POSSIBLE ENTRIES FROM 0-9! (GO TO CONFORM. TXT FILE) 

THEREIN BEFORE BOOTARGSÜBERTRAG AND ONLY VERY UP YOUR IP, GW, ServerIP, NETMASK 
ADAPTED FROM YOU ARE ALREADY CAN Flash and ARGS TRANSFERRED, AND EVEN THEN it boots DIRECTLY FROM WHERE TO FLASH VIA JICH RC CHOOSES WHAT ELSE! Bootargs EXTENSIONS FOR EITHER THE EVO IMG FW_SETENV STOP THE USE OR TXT MODIFY AND AGAIN TRANSFERRED. 
OBIS INSTRUCTIONS FOR VARIOUS WAYS TO FIND UNDER "INSTRUCTIONS" HERE AT THE BOARD! 

new in mini1.2-final: 
emerg is back, it can now flash if the mini is back to normal from usb flash stick. 
give you more information in the download thread to the mini-1.2-final here and here 

who is already a mini-evo-img in flash can also have the mini-1.2-final preliminary "flash" to flash then the evo-mini-1730.img as in the mini-thread explains via usb-stick to then! 
it simply an old evo-mini can (eg boot 1501) and the copy miniUPDATE.img by means of ftp / tmp ufs, but kill only after: 
telnet: Quote: 
killall -9 rcS 
killall -9 enigma2 




Now after mini tmp directory via ftp and then: 

at evo images: Quote: 
dd if = / tmp / miniUPDATE.img of = / dev/mtdblock5 




aaf in images: Quote: 
dd if = / tmp / miniUPDATE.img of = / dev/mtdblock6 




HOW IS THE ONLY IF YOU ALREADY TOLD DE EVO IMG WITH MINI IN reflashing Did! 

then after that is also this: quote: 
direct flashing with mini: 
if one of nem on an internal SATA or USB stick or on TFTPserver nem a full-image 
by name: 
miniFLASH.img 
( 
evo_mini_1749_ufs910_flash.img unpack it and rename *. img Going!) 
test (size 15.8 MB) and the Boxstart the REC button is pressed holds approximately 3 seconds (until "FLASH mini search" in the display) appears, then the miniFLASH.img searched in the media. Once it is found, it is loaded and flashed. FAT32 or ext2 does not matter on the stick ... miniFLASH.img has only the root of the partition are FIRST, then 0:1 to USB or IDE 0:1.
 
Status
Not open for further replies.
Top