Related
[i8190][HOW-TO]-[param-mod]-[BOOTLOGO]
!!Disclaimer!!You will be responsible for your own work. Don't blame me for anything that might go wrong with your phone.
I've done this and it worked just fine, but then again...i'm not you
----------------------------------------------------------------------------------------------------------------------------------------------------------
Ref. and research:
What is param.lfs, and why do we have it?
Param.lfs is needed for the bootloader to go on with the boot. Inside your phone there's a /lfs-partition which works as a image cache for the bootloader. It contains the bootimages, charging, warning, etc etc.
If image is not there it will fail to boot.
After extracting all images in param.lfs with "param-tools" I noticed there was a difference from the param folder in the phone.
One picture was missing in param.lfs.
In "/mnt/.lfs" there is a "logo.jpg" which is nowhere to be found in param.lfs.
View attachment param-extracted.zip
As you see in the zip, all bootimages are very low-res (96X160) but that "logo.jpg" in device is 480X800 so I realized that it must be created inside device on first boot after flash, somehow rendered from the two low-res images inside param.lfs.
I asked a few friends with L/N-models about their logo.jpg and they confirmed that it was there, but of course with the bootimage for their L/N-model.
I copied the "logo.jpg" from device and dd'd the param-partition from device and started searching for that "logo.jpg"...
This is where my work start.
Ok so we all got it, but it's different for all models, right. What if I change the 640X480 "logo.jpg" from the dd'd param instead of edit the small 90X160 model-specific images that other how-to's and mods suggested, which would have to be done for all models.... A total of six images!
This way, edit one 640X480 "logo.jpg" should make it work on all models, and it did!
So, how do we look whats inside param, and what do we look for?
We have to use a hexeditor to be able to do anything. I used HxD. Other editors work as well, but they have different options for copy/paste etc.
A *.jpg in hex always starts with "FF D8" and ends with "FF D9" (Ref.)
How to do it..First you'll have to make a "logo.jpg". Choose your tools for that as it will not be covered in this how-to.
Save your created picture as logo.jpg, 480X800, NOT BIGGER THAN 64673bytes. (176241 in octal numbers)
This is only safe with this specific param.(Attached at the buttom of post) Other params may have the picture in different offset.
Open attached param.lfs in HxD.
{
"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"
}
We will work with octal values.
Choose edit/select block.
Start:02464000 --> End: 02662240 (The lenght should now be 176241)
Start of block
End of block
Go to File/new. A new empty tab will open.
With the new tab in front -->Edit/insert bytes.
Bytecount must be same as the lenght-value from the block we marked in original param.lfs (176241)
You'll get a notification, just klick yes.
Now we have an empty block in the same lenght as the picture we want to change.
Open your 480X800 logo.jpg in HxD. Right klick/select all, then copy.
Go back to the empty file we made, right klick/paste write. (make sure you runnung HxB in overwrite mode.)
Save it as logo.jpg.
We should now have a new logo.jpg with exact the same lenght as the one in param.lfs.
Copy it the same way we did before, but now you paste write it into the marked space in param.lfs.
Save it as param.lfs and make sure its not bigger than original param.lfs.
You're done!
Now you can open (not unzip) the attached cwm-zip and overwrite the param.lfs in there, and flash in your custom recovery.
The one inside is an inverted i8190 stock image. Black on white background.
Some of the params I've made so far. Here you'll also find odin flashable params if anything goes wrong. Download mode will still be accessable.
I believe this should work for other Samsung devices as well, with their specific param, and the right offsets for that param.
Thanks to @ketut.kumajaya for param-tools, @DemonWav for reference for where to start.
Same procedure, different values..
Samsung Galaxy Exhibit SGH-T599
Original logo.jpg (64673byte)
Original param.lfs View attachment sgh-t599-param.zip
Octal values in original param: 3274000-->3465472. Length: 171473
Tbh I am still lost lol .
Sent from my _______ . You fill in the blank
Unjustified Dev said:
Tbh I am still lost lol .
Sent from my _______ . You fill in the blank
Click to expand...
Click to collapse
Haha. I'm no hex guru either :silly: Still learning.
I'll see if I can make one with Bless Hex Editor in linux and make a how-to for that also
Glad to know, as a reference my script useful here. How about creating a param.lfs as a base for param-tools, so no need any hex editor for a different boot logo.
ketut.kumajaya said:
Glad to know, as a reference my script useful here. How about creating a param.lfs as a base for param-tools, so no need any hex editor for a different boot logo.
Click to expand...
Click to collapse
Yes, param-tools is really a great tool Thank you for that!
I do't know much about scripts but it's a good idea
Do you mean like put the param and new logo.jpg in a folder, run a command to insert it to param?
tys0n said:
Same procedure, different values..
Samsung Galaxy Exhibit SGH-T599
View attachment 2272892Original logo.jpg (64673byte)
Original param.lfs View attachment 2272887
Octal values in original param: 3274000-->3465472. Length: 171473
Click to expand...
Click to collapse
Hello tys0n, any chance I could get you to PM me an odin or cwm flashable param.lfs for the T599n? I am trying to get Cygwin / param tools to work but my system just isn't up to the task. Greatly appreciated and keep up the great work!
Hi. I think I only got a param for T-Mobile.
T599n is metro, right?
If yours is fine then maybe you can make a backup, zip it, and attach it here so I can take a look at it
Sent through time and space from my s3mini/CM10.2
tys0n said:
Hi. I think I only got a param for T-Mobile.
T599n is metro, right?
If yours is fine then maybe you can make a backup, zip it, and attach it here so I can take a look at it
Sent through time and space from my s3mini/CM10.2
Click to expand...
Click to collapse
Hey tyson, sorry for taking so long to follow-up...holidays were upon us and took my time away. Anyway...i was able to grab the param.lfs from your previous post in this thread and dd the file through terminal emulator. Worked, no more scrambled boot screen. thanks to everyone who posted the information somewhere in these convoluted threads.
Hi evry one
Tyson please i need param.ifs for I8190N. I flash I8190 param.ifs and boot jpg now is I8190. Please can you givme to flash back.
joker79 said:
Tyson please i need param.ifs for I8190N. I flash I8190 param.ifs and boot jpg now is I8190. Please can you givme to flash back.
Click to expand...
Click to collapse
It is available here http://get.maclaw.pl/?id=51
piskor said:
It is available here http://get.maclaw.pl/?id=51
Click to expand...
Click to collapse
Thanks a milion...
Hi
Thank you for this tutorial it is really good but i can't do it
Could anyone help me.
I tried to make bootlogo but it doesn't work.
so could you make it for me with the logo of google
thanks
Thanks can I make boot logo with my own photo ?
Yes you can but you also can share a request image and someone will do it for you
There is a thread where you can do it http://forum.xda-developers.com/showthread.php?t=2432783
best1905 said:
Thanks can I make boot logo with my own photo ?
Click to expand...
Click to collapse
Yes you can
macieek1235 said:
Yes you can but you also can share a request image and someone will do it for you
There is a thread where you can do it http://forum.xda-developers.com/showthread.php?t=2432783
Click to expand...
Click to collapse
That is true. You can make a request, or give me a pm if you want any help to make one, or if you don't want to share your image with the whole forum.
Sent through time and space from my s3mini/CM11
I will update this guide soon! I'm now using "010 Editor" which is both powerful and available for windows, osx and linux. I will add empty templates with correct fileize where you can just paste/overwrite with your new image. I will add values for all i8190-models and SGH-T599 models. If you got more ideas, please send me a pm and let me know.
@tys0n maybe you can adapt also this way to do the logo changes: http://forum.xda-developers.com/showthread.php?t=2529133
Thank you so much for this tutorial! :laugh:
now i'm able to put my own photo as bootlogo :victory:
Hi.
My head is spinning.
Q1) Anyone have a decent link that describes (or hypothesizes) the N3 chain of trust boot sequence ordering?
e.g. is it something like: (power up) -> dbi -> sbl1-> -> aboot -> boot -> tz, rpm, init...
tz & rpm seem to be ELF images suggesting they need kernel support - or at least ELF relocation during image loading as they are not pure arm code. (The above sequence is hypothetical, I have no idea how it really works, but I picked that order based on blob size and continuous presence of PKI Certs).
Code:
x1kB-
PART NAME SIZE COMMENT
3 sbl1 512 Arm Code. Samsung Certs. Many SPMI comments
4 dbi 32 Arm Code. Samsung Certs.
6 aboot 2048 "bootloader". Arm Code. Samsung Certs
7 rpm 512 ELF image. Samsung Certs. Clock/Power Management
8 tz 512 ELF image. Samsung Certs.
Q2) The device (mmcblk0) MBR and subsequent UFI/GPT primary partition layout match the PIT exactly (as expected), excepting that PIT partitions 70-73 (PGPT, PIT, MD5, SGPT) are not actually explicitly present as partitions the UFI/GPT - but their data is.
And thus my question:
Has anyone figured out what the MD5 sigs contained in the MD5 partition (LBA blocks 0x32 - 0x51) are computed against?
For example, the psuedo-partition "MD5" at blocks 0x32 - 0x51 has (apparently) a number of MD5 sigs in there. I am not sure how they get there, but it brings up question Q3 below
The first of them - the "MBR" md5 (5AC92E1775AED95BFA69B4ED91B95F44) indeed is the md5 hash of the (legacy) MBR of /dev/block/mmcblk0 (first 512 bytes). But I can't figure out the correspondence of the others - the signatures of the full partitions (those not likely to change during normal operation) match neither the full-partition md5 signatures, nor the md5s of the Odin images installed there.
I went and grabbed one of those "Odin" tar files for the MJ7 build (that's what is still on my N3 & I have not used Odin or Kies, nor accepted any OTA since it came from the store, btw); when I dump the same number of bytes (from the corresponding partitions) of the various .img, .bin, and .mbn files from the corresponding partitions on my device, the MD5 sums of those blobs (apnhlos, modem, sbl1, sdi, aboot, rpm, tz, boot, recov) match. This is also to be expected - and a bit of a relief that the blobs are not per-device encrypted (e.g. as the Tegra3 bootloaders are); but strangely, if I dump the full partition lengths (the partitions sizes are greater than their contents), I still can not match the MD5s found on my device (LBA block addresss 0x32-0x51).
FWIW, here are the MD5s from the MJ7 build. You can find the corresponding ones on your device with something like:
Code:
dd if=/dev/block/mmcblk0 bs=512 skip=50 count=32 | strings -n 3
(MJ7 device, MJE should be different excepting MBR, GPT)
Code:
MBR 5AC92E1775AED95BFA69B4ED91B95F44
GPT 93D5B5ED952432999E1A63FBFBE1CAC2
PIT 0901E2E26B272644E64FBBFA671F1614
NONE 2BF1AABDC459C22BDA8FFFF5089B1443
NONE CAFA19C07B19E1CB633C6FD4DF38F23B
NONE DC3EE00113409E5172842D3A2703C862
NONE 1895185C4B4069E3DE38CDD97BAAD935
NONE 83EBDE825292FC15E5305DD3B39D900C
NONE F9F18407DE277A3330960B8C0C284FE5
NONE E3D03F2C0FCF8000EA45F2DAA3F5F927
CEXT4 B82580F9234207CCC4E575EAD339C7C5
NONE 5B6DBA514E8F7096E242CC419E479C0F
NONE 8C777C6B80565A59348B50F612A20AB8
CEXT4 6568CFE33E298FC376236DF82AEEB43E
CEXT4 FE48E691E236CB981B54C139E259137C
CEXT4 945E351CEE0008B2C8111572A31DCBCD
CEXT4 00630CC10D62CD21BE1263583E901D50
CEXT4 4C9C5F931BC89E2B09A0E0C22E22688E
Q3) Origin of the various Note 3 "Odin tar.md5" files floating around. Were these munged together by a dev, or captured intact directly from a Samsung download (e.g. by intercepting Kies software update payloads)? Specifically, I note that the files "pgpt.img", "md5.img", and "sgpt.img" referenced in @beanstowns106 's partition/PIT analysis thread are not present in either of these.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
Whew. Well, if you've read this far you deserve a reward, whether or not you reply. Attached are a zip of the JPEGs stripped out of the MJ7 bootloader. ("aboot.mbn"). Enjoy. (I can't guarantee they don't have trailing junk beyond their ends based on the way I extracted them, but it should be harmless junk if any).
{
"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"
}
I have lots of information to share with you. Do you have gtalk?
That zips actually pretty cool thanks!
Sent from my SM-N900V using xda app-developers app
Hello, I have made dd command for almost all partitions and I have found boot.img. However, I did not found boot splash logo. Where I should look?
Cyanogen Mod 13
SM-A500FU
legitscoper said:
Hello, I have made dd command for almost all partitions and I have found boot.img. However, I did not found boot splash logo. Where I should look?
Cyanogen Mod 13
SM-A500FU
Click to expand...
Click to collapse
It's in param partition.
It is empty ;(
It is in dev/block/bootdevice/by-name/param
I have made dd if=/dev/block/bootdevice/by-name/param of=/sdcard/param
I opened it in hexview and it has almost only 00 everywhere
and has 10mb
It's because you have a raw image of that whole 10MB partition while maybe only 1MB is used.
It'll send you it
I can take a look at it when I get home in a few hours.
Yeah it was quite empty
Is this from A500? Check /dev/block/platform/7824900.sdhci/by-name/param
Edit
Sorry, it took me a while before I realised this was a qualcomm/snapdragon.
They're in bootloader. "aboot.mbn" so you probably won't be able to change it.
{
"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"
}
Maybe re-flash bootloader? It must be possible. Or is it releated to Knox?
legitscoper said:
Maybe re-flash bootloader? It must be possible. Or is it releated to Knox?
Click to expand...
Click to collapse
I guess Odin would never allow the modified bootloader to flash. May be possible with the modified version of odin, I don't know..
I assume by the pictures I found that the background will be black by defauld no matter what.
There's no whole bootlogo, only the "Samsung galaxy A5" and "Powered by android" logos as small images.
Here I have extracted the "powered by android" logo from aboot. Only problem is I don't know what the file is named inside aboot.
If I name the new image something else than it should be and overwrite the old one, it would probably become bricked.
At best there would still be download mode.
Even if I did know the filename I would have to be precise in everything. Same resolution(304x81), same dpi(96dpi), same bytesize(6157 b), etc. and insert/overwrite at the exact same place. One faulty byte anywhere and chances are that the phone may never boot again unless you can get a jtag and reflash it.
It feels a bit risky just to change those two small images, and still be limited to only black background with new text at the same places as the original.
00033.jpg? Or it is something more complicated?
From where you know that bytes you selected is the image?
And that limitations (dpi, size) cannot be changed? Or simpler way is to get source code of bootloader and compile one for my phone?
legitscoper said:
00033.jpg? Or it is something more complicated?
From where you know that bytes you selected is the image?
And that limitations (dpi, size) cannot be changed? Or simpler way is to get source code of bootloader and compile one for my phone?
Click to expand...
Click to collapse
I would not try to change size or dpi in bootloader. I've made mistakes before when I modded param partition on another phone and it ends in no boot to system or recovery, or loop, and only download mode available. Param is like an image cache for bootloader, but here the images are inside bootloader which means that if something goes wrong it probably won't boot at all.
I think 00033.jpg was just what the program i used named it when it extracted the images.
That image was the second I found by searching for ffd8 which always is the beginning of a .jpg in hex, then make a search downwards for ffd9, which is the end of a .jpg. The first I found was the 5. It's a bit of trial end error when working in hex without knowing which image is what
The aboot I used was extracted from firmware.
And I will be unable to go to download mode it that "faulty byte" will occur?
I think thread is to close, I don't want to have that level of risk and with that limitations
tys0n said:
Yeah it was quite empty
Is this from A500? Check /dev/block/platform/7824900.sdhci/by-name/param
Edit
Sorry, it took me a while before I realised this was a qualcomm/snapdragon.
They're in bootloader. "aboot.mbn" so you probably won't be able to change it.
View attachment 4094675
Click to expand...
Click to collapse
Program name?
After unlocking my 996, I'm met with the unlocked warning screen:
{
"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"
}
I've seen several other devices fix this with a flashable zip or img file to overwrite or mask the warning. I've yet to see anyone mention it in regard to the V20.
Any help?
Other devices being something besides LG...
That image is in aboot, and you can't modify aboot.
runningnak3d said:
Other devices being something besides LG...
That image is in aboot, and you can't modify aboot.
Click to expand...
Click to collapse
5X is an LG phone: https://forum.xda-developers.com/ne...gdata-tool-t3240052/post63826602#post63826602
It may have been BUILT by LG, but it is still very much a Google phone and they specify the software that goes on it. For the Nexus series Google used the reference implementation of the boot loader.
If you find an imgdata partition on the V20, please be sure and let me know
-- Brian
runningnak3d said:
It may have been BUILT by LG, but it is still very much a Google phone and they specify the software that goes on it. For the Nexus series Google used the reference implementation of the boot loader.
If you find an imgdata partition on the V20, please be sure and let me know
-- Brian
Click to expand...
Click to collapse
Fair point. Thanks for the insight.
Yes, I miss being able to replace this goofy screen as well, I replaced the same bootloader unlocked warning screen on my Moto G4 with this awesome Motorola Developer Edition screen - on that phone it was a simple fastboot command or alternatively a zip you could install via TWRP
I decided to take a look at this again. raw_resources on the V20 is the equivalent partition to imgdata on the Nexus 5X. However, the format is not compatible with the tool that was linked above.
On the 5X they used bitmap images, and on the V20 they decided to use RLE images.
If someone wants to spend some time with a hex editor to figure out the new format, this is doable.
-- Brian
runningnak3d said:
Other devices being something besides LG...
That image is in aboot, and you can't modify aboot.
Click to expand...
Click to collapse
unless you can decrypt the whole aboot which is unlikely.
aboot is not encrypted, it is signed. But as I stated above, I was wrong. The images aren't in aboot directly. They are in raw_resources which is read by aboot. raw_resources isn't signed.
runningnak3d said:
I decided to take a look at this again. raw_resources on the V20 is the equivalent partition to imgdata on the Nexus 5X. However, the format is not compatible with the tool that was linked above.
On the 5X they used bitmap images, and on the V20 they decided to use RLE images.
If someone wants to spend some time with a hex editor to figure out the new format, this is doable.
-- Brian
Click to expand...
Click to collapse
you are talking about this right ?
http://www.fileformat.info/mirror/egff/ch09_03.htm
That is correct. RLE has no header like BMP or JPEG, so you have to know where it starts and where it ends if you have several images contained in one file -- which is what raw_resources is.
There is an index, but since I don't mind the nasty warning, I am not going to waste my time figuring it out
I am sure that it is probably something like:
Name
Beginning offset in raw_resources
End offset in raw_resources
Animated
Frames
blah blah blah
If someone wants to take this on, I will be more than happy to give some input, but at the end of the day solving LAF is far more important to me...
-- Brian
runningnak3d said:
That is correct. RLE has no header like BMP or JPEG, so you have to know where it starts and where it ends if you have several images contained in one file -- which is what raw_resources is.
There is an index, but since I don't mind the nasty warning, I am not going to waste my time figuring it out
I am sure that it is probably something like:
Name
Beginning offset in raw_resources
End offset in raw_resources
Animated
Frames
blah blah blah
If someone wants to take this on, I will be more than happy to give some input, but at the end of the day solving LAF is far more important to me...
-- Brian
Click to expand...
Click to collapse
Thank you very much for checking into all of this. That's amazing feedback.
Hello there !
I have an issue where I want to go back to Windows from fastboot as explained in this post :https://forum.xda-developers.com/no...nt/restore-windows-phone-8-installed-t3608223 .
I have my TZ.bin and other necessary files, but when trying to flash them with the command "fastboot flash partition TZ.bin", I get this error message:
{
"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"
}
Is there someone here smarter than me who knows how to solve that ?
First, it's TZ.img don't use .bin
Second, if you want to flash, for example, TZ partition use this:
fastboot flash TZ dump\TZ.img
You have to replace partition with the partition name (in this case TZ).
TBM 13 said:
First, it's TZ.img don't use .bin
Second, if you want to flash, for example, TZ partition use this:
fastboot flash TZ dump\TZ.img
You have to replace partition with the partition name (in this case TZ).
Click to expand...
Click to collapse
Hey ! Thanks for the answer !
I manager to get past the error.
However, I don't think I have access to the .img files as my backup seems corrupted.
I've red that some users were able to go back to a thor2 working state with the .ffu, but I'm pretty confused about how...
r0mDU19 said:
Hey ! Thanks for the answer !
I manager to get past the error.
However, I don't think I have access to the .img files as my backup seems corrupted.
I've red that some users were able to go back to a thor2 working state with the .ffu, but I'm pretty confused about how...
Click to expand...
Click to collapse
I don't remember how to do it, but i did it like a year ago and it broke some things like Bluetooth (and i think that SIM Card too). That's why it's recommended to use your phone backup.
Why do you think that your backup is corrupted?
TBM 13 said:
I don't remember how to do it, but i did it like a year ago and it broke some things like Bluetooth (and i think that SIM Card too). That's why it's recommended to use your phone backup.
Why do you think that your backup is corrupted?
Click to expand...
Click to collapse
My file is only about 2Gb large instead of the 8Gb it should be, and imgman64 does not manage to extract anything from it.
That's why I downloaded the .ffu and extracted teh different partition files, but in a .bin format.
If you remember how you did it I'd be interested (I don't really mind about Bluetooth or calls) !
r0mDU19 said:
My file is only about 2Gb large instead of the 8Gb it should be, and imgman64 does not manage to extract anything from it.
That's why I downloaded the .ffu and extracted teh different partition files, but in a .bin format.
If you remember how you did it I'd be interested (I don't really mind about Bluetooth or calls) !
Click to expand...
Click to collapse
Sorry, but i don't remember.
TBM 13 said:
Sorry, but i don't remember.
Click to expand...
Click to collapse
No problem, thanks again for the advices ! :good:
Weirdly enough, my problem came back.
That prevents me from flashing anything at all.
r0mDU19 said:
Weirdly enough, my problem came back.
That prevents me from flashing anything at all.
Click to expand...
Click to collapse
Same problem than today, replace partition with the partition name (TZ in this case).