PRFCreator: Bootloop nach Flashen einer Pre-Rooted Firmware (zip)

[Mordor]

Hallo,

ich habe ein kleines Problem.
Ich habe ein xperia z1.

Ich flashe mit dem Flashtool
Welche FTF ist mit Towel Root rootbar?
C6903_14.4.A.0.108_Generic_DE.ftf
Dann roote ich mit Dualrecovery.
Dann starte ich twrp und Update das image
Dann wipe ich alles außer external SD

Auf der SD ist die aktuelle Firmware von 5.1.1 (C6903_14.6.A.1.236_DE.ftf) die ich mit dem PRCreator (Version 1.3) erstellt habe.

Dabei ist super su und dualrecovery.

Allerdings nach dem Flashen komme ich immer nur ein Bootloop zu sehen. Bist zum "Android" Schriftzug und nochmal. Immer wieder.

Wo ist mein Fehler?
Ins TWRP komme ich auch nicht mehr, muss dann immer wieder erst C6903_14.4.A.0.108_Generic_DE.ftf flashen, und dann dualrecovery drauf spielen.

Ich habe noch eine "alte" vor gerootete 5.1.1 die funktioniert. Allerdings ist da default mäßig chinesisches Schriftzeichen installiert. Ich weiß nicht mehr, welche FW ich damals dafür genommen hatte.

Weiß einer wo das Problem liegt?

 

[Aaskereija]

Geh mal bitte diese Anleitungen durch.

[Anleitung][Win10] Wie Repariere/Downgrade/Update/Debrande ich mein SONY? - Flashtool
[Guide] Dualrecovery auf allen verfügbaren Sonys installieren

Dann wipe ich alles außer external SD

Du löscht dann alles. Auch dein System. Klar das dann nichts mehr funktioniert. Wenn man Wiped, dann ausschließlich nur "Cache, Dalvik/ART-Cache". Ausser du möchtest eine Custom-Rom flashen, dann wiped man ausschließlich "Data, System, Cache, Dalvik/ART-Cache". Niemals "internal sd" und "external sd"

 

[Mordor]

Danke für die Antwort, aber wenn ich sowieso eine neue fw flashe müsste doch alles wieder dabei sein, oder?

1. Flashe 4.4.4 (C6903_14.4.A.0.108_Generic_DE.ftf) ([Anleitung][Win10] Wie Repariere/Downgrade/Update/Debrande ich mein SONY? - Flashtool)
2. Aktiviere Entwicklermodus
3. DualNut (jetzt geht es plötzlich wieder :S) mit 3. ([Guide] Dualrecovery auf allen verfügbaren Sonys installieren)
4. Danach bootet er ins TWRP
5. Dann boote ich ins System
6. dann wieder in TWRP
7. Aktuelles TWRP
   1. Flash to kernel (einzige Auswahl)
8. Reboot to recovery
   1. "Swipe to allow modifications" aktivieren
9. Wipe
   1. Cache
   2. Dalvik/ART-Cache
10. Install prerootet Firmware (C6903_14.6.A.1.236_DE.ftf + super su + DualNut)
    1. Install läuft > Flashing System.sin to /dev/block/mmcblk0p23. Please Wait
    2. Danach kommt noch mehr text
    3. Dann ein "error" > Couldn't find partition with matching uuid
    4. Danach dann "Kernel flashed"
    5. Einiges an Text, dann "SuperSu installer
    6. Dann XZDualRecovery
    7. Updating partition details.....
    8. .....done
    9. Ich wähle direkt "Reboot System" - habe nicht "Wipe cache/dalvik" geklickt

11. > Bootloop
Sony Xperia - 2x Vibrieren
Display Schwarz, aber an
Kurze Pause
Sony Xperia - 2x Vibrieren
Display Schwarz, aber an
Sony Xperia - 2x Vibrieren
Display Schwarz, aber an
Kurze Pause
Sony Xperia - 2x Vibrieren
Display Schwarz, aber an

Das ganze habe ich jetzt an die 12 mal versucht.......keine Ahnung, was da schief läuft

 

[Aaskereija]

vor der installation der preRooted musst du natürlich auch system und data wipen. Daher der bootloop, ist ja schließlich eine viel höhere Android version.

 

[Mordor]

Von 4.4.4 KitKat auf 5.1.1

1. Flashe 4.4.4 (C6903_14.4.A.0.108_Generic_DE.ftf) ([Anleitung][Win10] Wie Repariere/Downgrade/Update/Debrande ich mein SONY? - Flashtool)
2. Aktiviere Entwicklermodus
3. DualNut (jetzt geht es plötzlich wieder :S) mit 3. ([Guide] Dualrecovery auf allen verfügbaren Sonys installieren)
4. Danach bootet er ins TWRP
5. Dann boote ich ins System
6. dann wieder in TWRP
7. Aktuelles TWRP
   1. Flash to kernel (einzige Auswahl)
8. Reboot to recovery
   1. "Swipe to allow modifications" aktivieren
9. Wipe
   1. Cache
   2. Dalvik/ART-Cache
   3. system
      
   4. Data
   5. NICHT AUSGEWÄHLT: Internal, sd OTG
10. Install prerootet Firmware (C6903_14.6.A.1.236_DE.ftf + super su + DualNut)
    1. Install läuft > Flashing System.sin to /dev/block/mmcblk0p23. Please Wait
    2. Danach kommt noch mehr text
    3. Dann Flashing FOTAKernel flashed
    4. Flashing to boot.sin to /dev/block/mmcblk0p14. Please Wait
    5. Finished
    6. Dann ein "error" > Couldn't find partition with matching uuid
    7. Danach dann "Kernel flashed"
    8. Einiges an Text, dann "SuperSu installer
    9. Dann XZDualRecovery
    10. Updating partition details.....
    11. .....done
    12. Ich wähle direkt "Reboot System" - habe nicht "Wipe cache/dalvik" geklickt

Mal noch ein Problem zwecks Dualrecovery:

Nach install von der o.g. KitKat Version kommt sehr häufig ein Reboot:

==============================================
=                                            =
=              XZDualRecovery                =
=           Maintained by [NUT]              =
=                                            =
=       For Many Sony Xperia Devices!        =
=                                            =
==============================================

1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia
4. Install ADB drivers to windows
5. Open an ADB shell
6. Exit

Please choose install action.
[1,2,3,4,5,6]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!

=============================================
Getting device and ROM info
=============================================
Device model is C6903
Firmware is 14.4.A.0.108
Android version is 4.4.4

=============================================
Step2 : Sending the recovery files.
=============================================
7 KB/s (31 bytes in 0.004s)
739 KB/s (18170 bytes in 0.024s)
81 KB/s (501 bytes in 0.006s)
735 KB/s (12812 bytes in 0.017s)
1571 KB/s (65965 bytes in 0.041s)
192 KB/s (3159 bytes in 0.016s)
1584 KB/s (29204 bytes in 0.018s)
48 KB/s (699 bytes in 0.014s)
1051 KB/s (34473 bytes in 0.032s)
97 KB/s (1202 bytes in 0.011s)
1932 KB/s (96956 bytes in 0.049s)
2214 KB/s (870760 bytes in 0.384s)
2010 KB/s (3415064 bytes in 1.659s)
2366 KB/s (2430930 bytes in 1.003s)
1077 KB/s (14346 bytes in 0.013s)

=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using rootkitXperia now.

NOTE: this only works on certain ROM/Kernel versions!

If it fails, please check the development thread (Post #2) on
XDA for more details.


******** REMEMBER THIS: ********


XZDualRecovery does NOT install any superuser app!!

You can use one of the recoveries to root your device.
=============================================
Drücken Sie eine beliebige Taste . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Sending files
=============================================
529 KB/s (13568 bytes in 0.025s)

=============================================
Installing using cubeundcube's rootkitXperia

Thanks to anyone involved in the development of this exploit:

Keen Team, cubeundcube, AndroPlus and zxz0O0
=============================================
ro.build.product=C6903
ro.build.id=14.4.A.0.108
ro.build.version.release=4.4.4
max_fds=4096
Creating target socket...OK.
3072 sockets created.
04000000 bytes allocated.
Done!
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxo

>>>>>> Jetzt startet das Handy einfach neu!

Ich mach das dann mit dem EasyRootTool v12.4, installiere SuperSu
Dann nochmal DuealRecovery aber mit Punk 1 (Rooted with Super su)

Die install von DualRecovery sieht dann so aus:

==============================================
=                                            =
=              XZDualRecovery                =
=           Maintained by [NUT]              =
=                                            =
=       For Many Sony Xperia Devices!        =
=                                            =
==============================================

1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia
4. Install ADB drivers to windows
5. Open an ADB shell
6. Exit

Please choose install action.
[1,2,3,4,5,6]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!

=============================================
Getting device and ROM info
=============================================
Device model is C6903
Firmware is 14.4.A.0.108
Android version is 4.4.4

=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
7 KB/s (31 bytes in 0.004s)
1774 KB/s (18170 bytes in 0.010s)
97 KB/s (501 bytes in 0.005s)
1137 KB/s (12812 bytes in 0.011s)
1840 KB/s (65965 bytes in 0.035s)
616 KB/s (3159 bytes in 0.005s)
1677 KB/s (29204 bytes in 0.017s)
113 KB/s (699 bytes in 0.006s)
1602 KB/s (34473 bytes in 0.021s)
293 KB/s (1202 bytes in 0.004s)
2014 KB/s (96956 bytes in 0.047s)
2395 KB/s (870760 bytes in 0.355s)
2619 KB/s (3415064 bytes in 1.273s)
2673 KB/s (2430930 bytes in 0.888s)
2001 KB/s (14346 bytes in 0.007s)

=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x    1 shell    shell       870760 Feb 22  2016 [1;32m/data/local/tmp/recovery/busybox[0m
Drücken Sie eine beliebige Taste . . .

##########################################################
#
# Installing XZDR version 2.8.26 RELEASE
#
#####

Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
This firmware does not require byeselinux, will not install it.
Creating /system/.XZDualRecovery and subfolders.
Copy recovery files to system.
Rename stock mr
Copy mr wrapper script to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Copy init's *.rc files in to /system/.XZDualRecovery.
Updating installed version in properties file.
dr.recovery.boot will be set to TWRP (default)
dr.initd.active will be set to false (default)
dr.ramdisk.boot will be set to false (default)
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up CWM backups.
Make sure firstboot goes to recovery.

=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================


=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================


=============================================
Installation finished. Enjoy the recoveries!
=============================================

Drücken Sie eine beliebige Taste . . .

Dann startet er ins


Nachtrag:

Hier nochmal der Flashprozess:

05/027/2017 12:27:21 - INFO  - Flashtool Version 0.9.22.3 built on 08-06-2016 22:30:00
05/027/2017 12:27:21 - INFO  - Executing search strategies to find proxy selector
05/027/2017 12:27:22 - INFO  - No proxy found for IE. Trying next one
05/027/2017 12:27:22 - INFO  - No proxy found for firefox. Trying next one
05/027/2017 12:27:22 - INFO  - No proxy found for java. Trying next one
05/027/2017 12:27:22 - INFO  - Syncing devices from github
05/027/2017 12:27:22 - INFO  - Opening devices repository.
05/027/2017 12:27:23 - INFO  - Scanning devices folder for changes.
05/027/2017 12:27:38 - INFO  - Pulling changes from github.
05/027/2017 12:27:39 - INFO  - Quietly closing devices repository.
05/027/2017 12:27:39 - INFO  - Devices sync finished.
05/027/2017 12:27:39 - INFO  - Loading devices database
05/027/2017 12:27:39 - INFO  - Loaded 94 devices
05/027/2017 12:27:39 - INFO  - Starting phone detection
05/027/2017 12:27:44 - INFO  - Device disconnected
05/028/2017 12:28:16 - INFO  - Selected Bundle for Sony Xperia Z1(C6903). FW release : Generic_DE. Customization : 14.4.A.0.108
05/028/2017 12:28:16 - INFO  - Preparing files for flashing
05/029/2017 12:29:27 - INFO  - Please connect your device into flashmode.
05/036/2017 12:36:31 - INFO  - Device connected in flash mode
05/036/2017 12:36:32 - INFO  - Opening device for R/W
05/036/2017 12:36:32 - INFO  - Reading device information
05/036/2017 12:36:32 - INFO  - Phone ready for flashmode operations.
05/036/2017 12:36:32 - INFO  - Opening TA partition 2
05/036/2017 12:36:32 - INFO  - Current device : C6903 - BH90194W13 - 1277-0154_R2D - 1274-8313_14.6.A.1.236 - EURO-LTE_14.6.A.1.236
05/036/2017 12:36:32 - INFO  - Closing TA partition
05/036/2017 12:36:32 - INFO  - Start Flashing
05/036/2017 12:36:32 - INFO  - Processing loader.sin
05/036/2017 12:36:32 - INFO  -     Checking header
05/036/2017 12:36:32 - INFO  -     Flashing data
05/036/2017 12:36:33 - INFO  - Loader : S1_Root_6732 - Version : LOADER_RELEASE_MSM8974_28_AID_4 / Boot version : S1_Boot_MSM8974_Rhine1.2_LA1.04_19 / Bootloader status : ROOTED
05/036/2017 12:36:33 - INFO  - Max packet size set to 512K
05/036/2017 12:36:33 - INFO  - USB buffer size set to 512K
05/036/2017 12:36:35 - INFO  - Parsing boot delivery
05/036/2017 12:36:38 - INFO  - Found a template session. Using it : C:\Users\userrname\.flashTool\devices\C69XX\default.fsc
05/036/2017 12:36:38 - INFO  - Opening TA partition 2
05/036/2017 12:36:38 - INFO  - Writing TA unit 00002774. Value : 01
05/036/2017 12:36:38 - INFO  - Closing TA partition
05/036/2017 12:36:38 - INFO  - Processing partition-image.sin
05/036/2017 12:36:38 - INFO  -     Checking header
05/036/2017 12:36:38 - INFO  -     Flashing data
05/036/2017 12:36:38 - INFO  - Opening TA partition 2
05/036/2017 12:36:39 - INFO  - Processing dbi_S1_Boot_MSM8974_Rhine1.2_19_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
05/036/2017 12:36:39 - INFO  -     Checking header
05/036/2017 12:36:39 - INFO  -     Flashing data
05/036/2017 12:36:39 - INFO  - Processing emmc_appsboot_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
05/036/2017 12:36:39 - INFO  -     Checking header
05/036/2017 12:36:39 - INFO  -     Flashing data
05/036/2017 12:36:39 - INFO  - Closing TA partition
05/036/2017 12:36:39 - INFO  - Opening TA partition 2
05/036/2017 12:36:39 - INFO  - Writing TA unit 0000084F. Value : 1A CE 1D 00 01 00 04 05 00 02 02 51 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 0A 00 02 00 A9 09 BE BA A9 09 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01
05/036/2017 12:36:39 - INFO  - Writing TA unit 000008FD. Value : 00
05/036/2017 12:36:39 - INFO  - Closing TA partition
05/036/2017 12:36:39 - INFO  - Opening TA partition 2
05/036/2017 12:36:39 - INFO  - Processing s1sbl_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
05/036/2017 12:36:39 - INFO  -     Checking header
05/036/2017 12:36:39 - INFO  -     Flashing data
05/036/2017 12:36:39 - INFO  - Processing sbl1_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
05/036/2017 12:36:39 - INFO  -     Checking header
05/036/2017 12:36:39 - INFO  -     Flashing data
05/036/2017 12:36:39 - INFO  - Processing tz_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
05/036/2017 12:36:39 - INFO  -     Checking header
05/036/2017 12:36:39 - INFO  -     Flashing data
05/036/2017 12:36:40 - INFO  - Closing TA partition
05/036/2017 12:36:40 - INFO  - Opening TA partition 2
05/036/2017 12:36:40 - INFO  - Processing cache.sin
05/036/2017 12:36:40 - INFO  -     Checking header
05/036/2017 12:36:40 - INFO  -     Flashing data
05/036/2017 12:36:41 - INFO  - Processing apps_log.sin
05/036/2017 12:36:41 - INFO  -     Checking header
05/036/2017 12:36:41 - INFO  -     Flashing data
05/036/2017 12:36:41 - INFO  - Processing kernel.sin
05/036/2017 12:36:41 - INFO  -     Checking header
05/036/2017 12:36:41 - INFO  -     Flashing data
05/036/2017 12:36:43 - INFO  - Processing fotakernel.sin
05/036/2017 12:36:43 - INFO  -     Checking header
05/036/2017 12:36:43 - INFO  -     Flashing data
05/036/2017 12:36:44 - INFO  - Processing rpm.sin
05/036/2017 12:36:44 - INFO  -     Checking header
05/036/2017 12:36:44 - INFO  -     Flashing data
05/036/2017 12:36:44 - INFO  - Closing TA partition
05/036/2017 12:36:44 - INFO  - Opening TA partition 2
05/036/2017 12:36:45 - INFO  - Processing userdata.sin
05/036/2017 12:36:45 - INFO  -     Checking header
05/036/2017 12:36:45 - INFO  -     Flashing data
05/037/2017 12:37:06 - INFO  - Processing system.sin
05/037/2017 12:37:06 - INFO  -     Checking header
05/037/2017 12:37:06 - INFO  -     Flashing data
05/041/2017 12:41:07 - INFO  - Processing amss_fs_1.sin
05/041/2017 12:41:07 - INFO  -     Checking header
05/041/2017 12:41:07 - INFO  -     Flashing data
05/041/2017 12:41:07 - INFO  - Processing amss_fs_2.sin
05/041/2017 12:41:07 - INFO  -     Checking header
05/041/2017 12:41:07 - INFO  -     Flashing data
05/041/2017 12:41:07 - INFO  - Processing amss_fsg.sin
05/041/2017 12:41:07 - INFO  -     Checking header
05/041/2017 12:41:07 - INFO  -     Flashing data
05/041/2017 12:41:07 - INFO  - Closing TA partition
05/041/2017 12:41:07 - INFO  - Opening TA partition 2
05/041/2017 12:41:07 - INFO  - Writing TA unit 00000964. Value : 00
05/041/2017 12:41:07 - INFO  - Writing TA unit 000008A4. Value : 00 00 00 00 00 00 00 00 00 00 00 00 00 00
05/041/2017 12:41:07 - INFO  - Closing TA partition
05/041/2017 12:41:07 - INFO  - Opening TA partition 2
05/041/2017 12:41:07 - INFO  - Closing TA partition
05/041/2017 12:41:07 - INFO  - Opening TA partition 2
05/041/2017 12:41:08 - INFO  - Processing elabel-C6903-row_201401221511.1_14.4.A.0.108.sin
05/041/2017 12:41:08 - INFO  -     Checking header
05/041/2017 12:41:08 - INFO  -     Flashing data
05/041/2017 12:41:10 - INFO  - Closing TA partition
05/041/2017 12:41:10 - INFO  - Opening TA partition 2
05/041/2017 12:41:10 - INFO  - Writing TA unit 00002725. Value : 32 30 31 37 2D 30 36 2D 30 35 20 31 32 3A 34 31 3A 31 30 00
05/041/2017 12:41:10 - INFO  - Writing TA unit 00002774. Value : 00
05/041/2017 12:41:10 - INFO  - Closing TA partition
05/041/2017 12:41:10 - INFO  - Ending flash session
05/041/2017 12:41:10 - INFO  - Flashing finished.
05/041/2017 12:41:10 - INFO  - Please unplug and start your phone
05/041/2017 12:41:10 - INFO  - For flashtool, Unknown Sources and Debugging must be checked in phone settings

 

[Aaskereija]

warum installierst du 2x die dualrecovery? das macht keinen Sinn. Und wenn du die SuperSU zip (SuperSU.zip 2.79! Die 2.82 macht Probleme bei Sony) über flashtool flashst, brauchst du auch kein easyroot mehr.

Ansonsten, wo genau fehlt es jetzt noch? Scheint ja trotzdem alles zu funktionieren

 

[Mordor]

Nein, funktioniert nicht, weil ich ja ein Bootloop bekomme.

Installiert das EasyRootTool denn auch DualRecovery? Das das es nur rootet.

 

[Aaskereija]

Nein, aber wenn du die dualrecovery schon über die towelroot methode installierst, brauchst du das nicht später mit root nochmal zu wiederholen.

Ansonsten, hol dir eine andere PreRooted. Entweder ist die fehlerhaft oder passt nicht.

 

[Mordor]

habe neu erstellt mit der niedrigeren Version super su!

Daran lag es! Danke!