Related
Note:
This is not bootanimation, this is the splash screen (the 'LeEco' boot logo which is displayed when device is switched ON)
This is for LeEco Le Max2/Max1/Max Pro Only ..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted LeEco Le Max 2 / Max1 (X900) / Max Pro (X910) [any ROM]
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer.
3. You're proceeding at your own risk.
STEPS to create splash.img:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
It's not yet tested by anyone.
1. Download & Extract this: Le_Max_Splash_Logo_Maker.zip
2. Make sure you have 3 pictures (same or different) in 1440x2560 resolution in PNG format.
(It seems Le Max displays any 1 picture from the 3 pictures randomly while switching ON, so I think you'll have to use 3 pictures)
3. Now rename your 3 pictures as logo1.png, logo2.png, logo3.png & replace it inside "pics" folder of the extracted folder.
(Similarly you can replace other pictures in it carefully if you wish)
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. @GokulNC (myself ) who wrote this script.
2. Modified from my tool here: [GUIDE] How to Create Custom Splash Screen (Boot Logo) for Zuk Z2/Z2 Pro
3. Thanks to @pablo01 who provided stock splash.img of Le Max1 X900
Hit the Thanks :good: button if it worked for you
Don't forget to post here the custom splash screens that you made, since others may find it useful
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'LeEco' boot logo which is displayed when device is switched ON)
This is for LeEco Le Max 2 Only ..
Requirements:
1. Rooted LeEco Le Max 2 X820 (any ROM)
2. Terminal Emulator app installed.
STEPS to create splash.img:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
It's not yet tested by anyone.
1. Make sure you have 3 pictures (same or different) in EXACTLY 1440x2560 resolution in PNG format.
(Actually, it seems Le Max2 displays 3 pictures one by one while switching ON, so I think you'll have to use 3 pictures, but feel free to explore)
2. Download & Extract this: Le_Max_2_LeEco_Splash_Logo_Maker.zip
3. Now rename your 3 pictures as logo1.png, logo2.png, logo3.png & replace it inside "pics" folder of the extracted folder.
(Similarly you can replace other pictures in it carefully if you wish)
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
1. Transfer the splash.img to your device's Internal Storage.
2. Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
(You can also flash from fastboot as given below)
Note:
Incase something goes wrong or device doesn't bootup, download this: stock_splash.zip. Extract it & flash the splash.img from fastboot like:
Code:
fastboot flash splash splash.img
Credits:
1. @GokulNC (myself ) who wrote this script.
2. Modified from my tool here: [GUIDE] How to Create Custom Splash Screen (Boot Logo) for Zuk Z2/Z2 Pro
Hit the Thanks :good: button if it worked for you
Don't forget to post here the custom splash screens that you made, since others may find it useful
Click to expand...
Click to collapse
Any app on Play Store can apply an other boot animation?
Inviato dal mio Le X820 utilizzando Tapatalk
working good for me . thank you.
Q. how do you unpack the original splash.img?
M4nu3l1c4t4 said:
Any app on Play Store can apply an other boot animation?
Click to expand...
Click to collapse
This is not bootanimation bro...
This is the boot logo (the Le logo which is displayed when the device is switched ON)..
And BTW, please don't quote the entire thread
Dmxsir said:
working good for me . thank you.
Q. how do you unpack the original splash.img?
Click to expand...
Click to collapse
There's no automated tool for that, I did that manually..
It's a bit technical, so I'm not sure if I can make it understand to others who don't have an experience with this..
Anyway, here's what I did:
1. Your device's resolution is 1440x2560, and I saw using Hex Editor that the splash image is raw bgr24 format...
Which means there's 3 bytes per each pixel, so total no. of bytes for a picture=1440*2560*3, which is 11059200 (A8C000 in hex)
2. The first 512bytes is the header of a splash picture (it starts like "SPLASH!!" followed by resolution in little endian format; don't worry about those details). It doesn't contain any pixels data, so remove (or skip) that first 512Bytes and take the next 11059200 (A8C000 in hex) bytes and store it in a new file, say temp.img
3. Now you have to convert the temp.img to a picture file (preferably PNG), so I use the ffmpeg tool for that.
Code:
ffmpeg.exe -f rawvideo -vcodec rawvideo -pix_fmt bgr24 -s 1440x2560 -i temp.img -vframes 1 -y temp.png
4. Now you have first picture with you (temp.png)..
Similarly, after exactly 12MB (12582912bytes or C00000 in hex) of the picture in the splash.img, there's the header of picture of second pic, which is followed by its raw pixels data (as I've said from point 1), and similarly you can extract the picture2..
It seems there are 6 pictures, so you'll be doing this 6 times..
It may seem like it's a tedious process, but once you're good with using the Hex Editor with it, it'll just take a few minutes.. (You'll know the tricks of how to do this easily and fast with experience)
I have not explained everything in detail, as I don't have time now
And, I don't intend to make any automated tool for extracting it, since splash.img varies for devices, and I'll be wasting time for something that'll be useful to a single device only (or probably no one will use it, since who cares about extracting it really while there's a tool to create a new one?)
And also, by default, I have included the stock pics only in the /pics/ folder (So if you want to edit the stock pics, you may take a backup of those somewhere and do it)
BTW, you may post the splash.img that you created here, since others may find it useful..
(Just zip it to reduce the 72MB splash.img size to just 200kB or something before posting )
thank you for that explanation, i will look into it.
attach my israeli version .
:good:thank you very much man...
Creating a batch of splash screens for this device. Unfortunatly behind a work firewall so have to attach via XDA to make sure they work.
First up Samurai Champloo
Le max developer phone...
Thanks after flashing some custom rom it changed the splash logo and I wanted stock one.
pubg
pubg boot screen
Can someone make one with google logo like pixel phones?
download link is off
edit: Qr code is working
thanks very much
Sagit Logo Generator
notice:
someone reported(firmware version global 071019) getting random reboot after changed boot logo, and flash [china firmware 0908/0907] solved it. Use it at your own risk.
First download this File View attachment GenLogo.zip
How to use (Windows)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run GenLogo.exe and you get logo_new.img.
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to use (Linux&Unix)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run python genlogo.py and you get logo_new.img (python3).
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to restore
Just flash logo.img in official fastboot ROM View attachment logo.zip.
Source: https://github.com/moonheart/sagit-logo-gen
Thanks @huhu2207 for advice (binwalker).
Anyone tested it to confirm its working?
ermacwins said:
Anyone tested it to confirm its working?
Click to expand...
Click to collapse
Works Flawlessly.
Google Pixel 2 Boot Logo
---
You can install the same mod from kenzo to your bootanimation.
https://androidfilehost.com/?fid=673368273298932636
Enjoy
moonheartmoon said:
Sagit Logo Generator
notice:
someone reported(firmware version global 071019) getting random reboot after changed boot logo, and flash [china firmware 0908/0907] solved it. Use it at your own risk.
First download this File View attachment 4316668
How to use (Windows)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run GenLogo.exe and you get logo_new.img.
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to use (Linux&Unix)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run python genlogo.py and you get logo_new.img (python3).
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to restore
Just flash logo.img in official fastboot ROM View attachment 4316673.
Source: https://github.com/moonheart/sagit-logo-gen
Thanks @huhu2207 for advice (binwalker).
Click to expand...
Click to collapse
Hi,
in the instructions you indicate that i have to edit the 5 images that appear in the folder. I just want to create the logo on boot that by default mi.com appears. Have I to edit all the images with the same image I want to put in the boot or just one of them? Thanks in advance and soory for my bad english.
Guillemi said:
Hi,
in the instructions you indicate that i have to edit the 5 images that appear in the folder. I just want to create the logo on boot that by default mi.com appears. Have I to edit all the images with the same image I want to put in the boot or just one of them? Thanks in advance and soory for my bad english.
Click to expand...
Click to collapse
Yes, you can just edit one of them.
moonheartmoon said:
Yes, you can just edit one of them.
Click to expand...
Click to collapse
Thanks. i'll give a try.
Thank you!
It works wonderfully!
Can someone propose in which .bmp editor pictures should be edited. I was try with Photoshop, but without succes. I suppose Logo generator is working, because after I edited just one pic, main boot logo 4.bmp, I've got a change, but if I edit all images I got a black screen instead of boot logo.
Which tool you using and which settings for .bmp images saving?
Thanks.
EDIT: Guys, please ignore this post, not sure what I have screwed last time, this working as expected. .bmp pictures edited in Photoshop.
Up. Is this guide still working for MIUI 10 ? (8.6.21 .eu) ???
pi4a7a said:
Up. Is this guide still working for MIUI 10 ? (8.6.21 .eu) ???
Click to expand...
Click to collapse
Yes
Is it device dependent ? Or it can work on similar specs Mi Mix 2? If not, any changes I can do to make it work?
Thanks!
moonheartmoon said:
Sagit Logo Generator
Click to expand...
Click to collapse
Thank you for the mi6 logo. Could you make a logo for mi note 3?
offset0 = 0x4000
offset1 = 0x4200
offset2 = 0x2A200
offset3 = 0x1C0200
offset4 = 0x1EE000
offset5 = 0x7DCE00
sagit
UP
Is this guide still working for miui 11?
edit: yes it works
Hi,
So many of us are not happy with the oreo rom of Honor 8 Pro (C675). Those who looking forward to downgrade from Oreo to nougat just follow the steps. (This method is tested and is working. I just finished downgrading and is working perfectly fine. I just want to share this method with you guys. Also this i my first post in the forum. Some steps have been copied from a previous post by xfact)
Things you might need :-
>>A computer
>>At least 8GB memory card.
>>An unlocked bootloader. (you can relock it later)
>>Download the necessary files here :- [The Dload file was previously shared in this forum by xfact, but the link is not working now. Fortunately, I downloaded the file while it was available and I am providing the link to the google drive backup.]
REMOVE THE *** IN BETWEEN THE URL'S
(a) Dload File --- https***://***drive.google.com/open?id=1ZpOoPZ3dEn86lEh0PwlZP0W2LShM-BnT
(b) Recovery File --- https***://***drive.google.com/file/d/1qiP4k5HtJ3VR5l9ac8FnpxrwryIxu-pV/view?usp=sharing
(c) ADB platform tools --- https***://***drive.google.com/open?id=1vu-awRNjH3B9os5MuHGSlu-ca6zNv10V
>>Unzip the above-mentioned Dload file, then go to the folder, then software>dload folder and unzip the 'SDupdate_Package.tar.gz' with 7-Zip. It will extract another archived file called 'SDupdate_Package.tar'. Now unzip that too with 7-Zip and you will get a folder called 'dload' again.
>>Now take an SD card with at least 8 Gb of space, format it to exFAT. Paste the last 'dload' folder and all its contents at the root directory of that SD card. Put it into your phone.
>>To unlock the bootloader, just log into---- https***://***bit.ly/2uEEvdj
This is their chinese website, use translator in chrome to read in english.
Fill up the necessary details and you will get an unlock code for your device.
>>Follow the necessary steps to unlock your bootloader from here :- https***://***bit.ly/2uEM1F8
>>After unlocking the bootloader, your phone will be factory reset. When the phone boots up again, go to settings and enable USB Debugging from devoloper options.
>>Unzip the platform tools zip file and copy the Recovery file into that folder.( you have to unzip the platform tools file while unlocking the bootloader. Just copy the recovery image to that folder)
>>Holding the SHIFT key, right click any empty spaces in the folder and from the menu that appears, select "Open command window here"
>>Connect your handset. Ensure USB debugging prompt appeared as seen in the bootloader unlocking tutorial.
>>In the command window type the following commands :-
1. adb devices
(this is to make sure your device is connected properly)
2.adb reboot bootloader
(to put your device into fastboot mode)
3.fastboot flash recovery_ramdisk DUK-RECOVERY_RAMDISK_NoCheck.img
(to flash the recovery image)
4. fastboot reboot
>>When the device boots up, go to the dialer, type *#*#2846579#*#*
->Click on Software Upgrade -> SDcard upgrade->confirm.
Your phone will recognise the memory card with dload file in it. It will flash the rom. It will get stuck at 99% and shows error. Dont worry, just select reboot system option that appears on the screen.
You will be on the Nougat Rom
To relock the bootloader--
>>Again you have to enable USB debugging from devoloper options>>open command window from the platform tools folder>> execute the commands 1 and 2.
Then type the following command :-
fastboot oem relock *unlock key*
(replace *unlock key* with your unlock key used for bootloader unlock)
YOUR DEVICE WILL BE ON NOUGAT ROM WITH LOCKED BOOTLOADER
As this is my first post, kindly ignore the errors. Sorry if this lengthy post made any confusion. Hope this is helpful to all of you.
akhilbs94 said:
Hi,
So many of us are not happy with the oreo rom of Honor 8 Pro (C675). Those who looking forward to downgrade from Oreo to nougat just follow the steps. (This method is tested and is working. I just finished downgrading and is working perfectly fine. I just want to share this method with you guys. Also this i my first post in the forum. Some steps have been copied from a previous post by xfact)
Things you might need :-
>>A computer
>>At least 8GB memory card.
>>An unlocked bootloader. (you can relock it later)
>>Download the necessary files here :- [The Dload file was previously shared in this forum by xfact, but the link is not working now. Fortunately, I downloaded the file while it was available and I am providing the link to the google drive backup.]
REMOVE THE *** IN BETWEEN THE URL'S
(a) Dload File --- https***://***drive.google.com/open?id=1ZpOoPZ3dEn86lEh0PwlZP0W2LShM-BnT
(b) Recovery File --- https***://***drive.google.com/file/d/1qiP4k5HtJ3VR5l9ac8FnpxrwryIxu-pV/view?usp=sharing
(c) ADB platform tools --- https***://***drive.google.com/open?id=1vu-awRNjH3B9os5MuHGSlu-ca6zNv10V
>>Unzip the above-mentioned Dload file, then go to the folder, then software>dload folder and unzip the 'SDupdate_Package.tar.gz' with 7-Zip. It will extract another archived file called 'SDupdate_Package.tar'. Now unzip that too with 7-Zip and you will get a folder called 'dload' again.
>>Now take an SD card with at least 8 Gb of space, format it to exFAT. Paste the last 'dload' folder and all its contents at the root directory of that SD card. Put it into your phone.
>>To unlock the bootloader, just log into---- https***://***bit.ly/2uEEvdj
This is their chinese website, use translator in chrome to read in english.
Fill up the necessary details and you will get an unlock code for your device.
>>Follow the necessary steps to unlock your bootloader from here :- https***://***bit.ly/2uEM1F8
>>After unlocking the bootloader, your phone will be factory reset. When the phone boots up again, go to settings and enable USB Debugging from devoloper options.
>>Unzip the platform tools zip file and copy the Recovery file into that folder.( you have to unzip the platform tools file while unlocking the bootloader. Just copy the recovery image to that folder)
>>Holding the SHIFT key, right click any empty spaces in the folder and from the menu that appears, select "Open command window here"
>>Connect your handset. Ensure USB debugging prompt appeared as seen in the bootloader unlocking tutorial.
>>In the command window type the following commands :-
1. adb devices
(this is to make sure your device is connected properly)
2.adb reboot bootloader
(to put your device into fastboot mode)
3.fastboot flash recovery_ramdisk DUK-RECOVERY_RAMDISK_NoCheck.img
(to flash the recovery image)
4. fastboot reboot
>>When the device boots up, go to the dialer, type *#*#2846579#*#*
->Click on Software Upgrade -> SDcard upgrade->confirm.
Your phone will recognise the memory card with dload file in it. It will flash the rom. It will get stuck at 99% and shows error. Dont worry, just select reboot system option that appears on the screen.
You will be on the Nougat Rom
To relock the bootloader--
>>Again you have to enable USB debugging from devoloper options>>open command window from the platform tools folder>> execute the commands 1 and 2.
Then type the following command :-
fastboot oem relock *unlock key*
(replace *unlock key* with your unlock key used for bootloader unlock)
YOUR DEVICE WILL BE ON NOUGAT ROM WITH LOCKED BOOTLOADER
As this is my first post, kindly ignore the errors. Sorry if this lengthy post made any confusion. Hope this is helpful to all of you.
Click to expand...
Click to collapse
can I get recovery image file please
Hi mates, today i come with the unique guide for unbrick our Huanor GR5X phones
THIS GUIDE IS FOR FULLY BRICKED HUAWEI GR5/5X HONOR, ALL MODEL/VARIANT
ATENTION!!!
Files rawprogram0.xml and patch0.xml from my packcage its ONLY for the Huawei GR5 KII-L23 16GB VARIANT!!!
In order to continue with the tutorial, you must create your rawprogram and patch0 xml files
(mini tutorial bellow)
Ready? GO
1) Download my packcage (link MEGA)
2) Install QFIL Software. From my packcage, extract and move the folder 'Firmware' to C:\Program Files\Qualcomm\QPST\bin
3) Download and extract this .IMG files from ANY 5.1 full firmware UPDATE.APP for your model/variant
(Note: for KII-L23 is not necessary GPT.img)
GPT.img
BOOT.img
CUST.img
SYSTEM.img
TZ.img
MODEM.img
Place all img files in C:\Program Files\Qualcomm\QPST\bin\Firmware
4) Install Qualcomm drivers, Connect phone to pc, open Device Manager. If you see under com port Qualcomm USB loader or something along those lines. your good.
5) In QFIL software, if qualcomm driver are found it will say on top of QFIL software Qualcom USB loader 9008 (if say 9006,900E, you must put your phone into EDL mode with EDL Cable or EDL TEST POINT, google it)
6) Once you get the Qualcom USB loader 9008 on QFIL, you can continue
6) Select Build Type: click Flat Build
7) Select Programmer: browse to C:\Program Files\Qualcomm\QPST\bin\Firmware\prog_emmc_firehose_8939.mbn and select
8) Load XML: browse to C:\Program Files\Qualcomm\QPST\bin\Firmware and select "rawprogram0.xml" file, then select "patch0.xml" file.
9) Go to Tools and click Partition Manager
10) You will see a list with all files from partition table
11) To flash, you need select Boot.img in the list first, a mini windows will open, click on Load image and select the Boot.img placed on C:\Program Files\Qualcomm\QPST\bin\Firmware
Do the same with the rest of img files in THIS order
BOOT.img
CUST.img
SYSTEM.img
TZ.img
MODEM.img
12) Once you finish, close the partition manager. A message will appear and phone will reboot. If not, reboot manually
That's all enjoy!
FOR GR5 KII-L2X AND HONOR 5X KIW-L2X MODEL/VARIANT, FOLLOW THIS TUTORIAL
1) Download my packcage and exctract it
2) Open a cmd windows in 'Phyton + GPT Tools' folder
3) Type: GPTAnalyzer.py (drag and drop the GPT.img file previously downloaded from 5.1 firmware) and click Enter
4) Copy all results in cmd, paste on notepad and save as 'Partition0.xml' (start with <?xml version... and finish on </configuration>)
5) Type GPTParseTool.py -x (drag and drop the partition0.xml created) and click enter
6) Go to phyton folder and move all created files to C:\Program Files\Qualcomm\QPST\bin\Firmware
7) Now you can continue with the guide
Thats all my friends, hope you get a new life for your Huanor GR5X
PLEASE IF I HELP YOU, BUY ME A COFFE HERE
Reserved
GOOD guide！someone will need it！
my question：does it work on the locked phone?
wsdyleon said:
GOOD guide！someone will need it！
my question：does it work on the locked phone?
Click to expand...
Click to collapse
Thanks!
Locked and unlocked devices.
My dear friend, there is no python tools folder in your package. i can't unbrick my phone with your xml files, its a KLL-L21.
Best of regards.
faabricjs said:
Thanks!
Locked and unlocked devices.
Click to expand...
Click to collapse
I cant find python + GPT tools
faabricjs said:
Thanks!
Locked and unlocked devices.
Click to expand...
Click to collapse
my device is not showing up I have removed the battery and connected the usb but nothing happens only the device vibrates and huawei logo apears but nothing on my pc
Ibrahim Tariq said:
I cant find python + GPT tools
Click to expand...
Click to collapse
Here you will find all files needed and instructions
You have to open the phone and put it in EDL mode
Search Google for that
https://forum.hovatek.com/thread-31505.html
snazzyman89 said:
My dear friend, there is no python tools folder in your package. i can't unbrick my phone with your xml files, its a KLL-L21.
Best of regards.
Click to expand...
Click to collapse
Ibrahim Tariq said:
my device is not showing up I have removed the battery and connected the usb but nothing happens only the device vibrates and huawei logo apears but nothing on my pc
Click to expand...
Click to collapse
See my reply in previous post #8
---------- Post added at 02:15 AM ---------- Previous post was at 02:06 AM ----------
Can't we use Huiye Download Tool to flash all the images ?
what if i dont have system.img in my firmeware ? what should i do ? i have firehose from b321 can this be compatible with b330?
EDIT : i found the sys.img for b321
friends help me out i have KiW L21 superbricked unable to charge battery and he dont show up in device manager as qloader 9008
Ive made a terrible mistake of not installing DevInfo before wiping my UK unlocked Samsung J5 and now i dont know what model number it was or what cpu i had arm32/64 or x86 I have tryed 3 different Linageos 17 and i keep getting this error on all of them.
I cant get my J5 to work through USB PC (Adb) so have to use another samsung phone which has a SD card so that i can put the rom on that and then transfer that sd card to the j5, also i never backed up my OS so theres nothing on there apart from TWRP
Theres no way in TWRP to get any info on the make or model, is there a safe universal rom to install via TWRP so that i can just check my model number cpu hardware etc, so i can then install the right lineageos 17 afterwards
{
"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"
}
68EC000 said:
Ive made a terrible mistake of not installing DevInfo before wiping my UK unlocked Samsung J5 and now i dont know what model number it was or what cpu i had arm32/64 or x86 I have tryed 3 different Linageos 17 and i keep getting this error on all of them.
I cant get my J5 to work through USB PC (Adb) so have to use another samsung phone which has a SD card so that i can put the rom on that and then transfer that sd card to the j5, also i never backed up my OS so theres nothing on there apart from TWRP
Theres no way in TWRP to get any info on the make or model, is there a safe universal rom to install via TWRP so that i can just check my model number cpu hardware etc, so i can then install the right lineageos 17 afterwards
View attachment 5405063
Click to expand...
Click to collapse
Some sensitive info was overlapped, for this reason this ROM is not recognizing your device as a candidate. If you are totally sure that this ROM work for your device, just delete from the zip path /META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device... and try again.
Regard to know the exact model you could flash a stock recovery (converting it in tar) from any of the LTE models; G/F/FM and booting to it, you will see the build number and the exact model it is.
Many thanks for your help.... Ive managed to find out that its a J5 SM-J530F 2017 (16gb) and with the IMEI number it has a ARM Cortex A53, Samsung Exynos 7870.
I loaded up a stock rom J530FXWS7CTF1 in Odin3_v3.10.5 everything went ok but when its starts up it goes into a loop on restart
Loaded up the Rom and everything went ok
Everything looked good
looks like its failed....
68EC000 said:
Many thanks for your help.... Ive managed to find out that its a J5 SM-J530F 2017 (16gb) and with the IMEI number it has a ARM Cortex A53, Samsung Exynos 7870.
I loaded up a stock rom J530FXWS7CTF1 in Odin3_v3.10.5 everything went ok but when its starts up it goes into a loop on restart
View attachment 5405703
Loaded up the Rom and everything went ok
View attachment 5405705
Everything looked good
View attachment 5405709
View attachment 5405711
looks like its failed....
Click to expand...
Click to collapse
From what I understood, you flashed the official stock firmware through Odin, but then you did try to root it.
If this is the case after to flash the Samsung firmware you should to reboot to system and redo all the process to can flash something custom on it, I mean USB debugging, OEM unlock and this stuff, only starting from there you should go further with.
And one more thing, when you return completely to stock is always recommendable:
- Wiping all and formatting data through stock recovery
- Then go to bootloader (Odin mode)
- When flashing use the CSC_... different from the CSC_HOME this will wipe completely the preferences, and you can start freshly from there.
Why you don't use Magisk instead of SuperSu.
again thank you for your time, i feel a bit embarrassed as im digging my self into a deeper situation and dont know what to do.
Since i dont have a OS installed am either stuck with download mode or twrp and even using magisk i cant get anything to work it seems that the custom lineageOS keeps saying its the wrong version for any of them.
.
.
magisk
anything else i could try if its salvageable, thanks again.
68EC000 said:
again thank you for your time, i feel a bit embarrassed as im digging my self into a deeper situation and dont know what to do.
Since i dont have a OS installed am either stuck with download mode or twrp and even using magisk i cant get anything to work it seems that the custom lineageOS keeps saying its the wrong version for any of them.
View attachment 5408207
.
View attachment 5408209
.
magisk
View attachment 5408211
anything else i could try if its salvageable, thanks again.
Click to expand...
Click to collapse
Some insights about:
- Don't try to flash 3 files at once, flash one by one.
- did you do the right editing from the updater-script as indicated? Can you upload here just this file?
- Did you change the system partition through TWRP I mean did you do "repair file" ?
- It seems that TWRP is not finding the route to misc partition, have your ROM this file? Unpack the stock ROM and search for it in case you didn't do a backup from.
- And as a final resource the PIT repartitioning could work too but, we have to see other reasons why your device got this.
hi thanks again for your patient i cant seem to find the line
META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device...
this is from the rom lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb)
68EC000 said:
hi thanks again for your patient i cant seem to find the line
META-INF/com/google/android/updater-script something like assert failed: getprop("ro.product.device...
View attachment 5409557
this is from the rom lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb)
Click to expand...
Click to collapse
You have to delete all the lines above, edit it with Notepad++, and let it from "ui_print........" then save it, you don´t need to unpack the zip, just open it, edit it and save, WinRar or 7zip will update the zip with the changes.
I used 7zip to edit the \META-INF\com\google\android\updater-script and saving editied file without unzipping.
then i put the edited lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb) file back onto microSDcard and tried again.
68EC000 said:
I used 7zip to edit the \META-INF\com\google\android\updater-script and saving editied file without unzipping.
View attachment 5410597
then i put the edited lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip (569 Mb) file back onto microSDcard and tried again.
View attachment 5410601
Click to expand...
Click to collapse
You shortened too much the file, from your original updater-script uploaded some days ago you didn't leave the most important scripts.
I don't recommend using a simple Notepad to edit it, you should use Notepad++ or other tool like Sublime.
Can you upload the original-updater script? I will check it, and will upload it again, this way we can discard if this is the culprit or something is wrong with your file system.
yes i deleted too much from the script file... i installed Notepad++ and re-done the script.
redited script saved
starts off good.
i dont know if it failed or if something did work as it asks if you want install twrp again
68EC000 said:
yes i deleted too much from the script file... i installed Notepad++ and re-done the script.
View attachment 5411271
redited script saved
View attachment 5411273
View attachment 5411275
starts off good.
View attachment 5411277
View attachment 5411279
i dont know if it failed or if something did work as it asks if you want install twrp again
Click to expand...
Click to collapse
The ROM you are trying to flash is this? https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/ if not, provide a link.
@68EC000 you should use the latest orange fox recovery for your device, This error was also faced by mt j5, I flashed orange fox recovery and I didn't get any error, With the old version of TWRP I was unable to flash android 10 lineage os on it
I was also getting this same error 7 with old twrp
[OFFICIAL][TWRP][J530X] OrangeFox Recovery Project [R11.0]
DISCLAIMER I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com
flash this recovery and then try to flash lineage os
Hi
Thanks again for your input and help.....so i tryed the Rom from https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/
edited the updater script
Spoiler: Screen shots
error 7 again...
So i tryed hasangillani66 method installing OrangeFox and adb then copying recovery.img to the adb directory but im getting some error when typing device, also everytime a connect the j5 to the pc via usb i hear the usb connection sound but cant see anything in my computer.
Spoiler: Screen shots
68EC000 said:
Hi
Thanks again for your input and help.....so i tryed the Rom from https://forum.xda-developers.com/t/...or-the-galaxy-j5-pro-j530-02-02-2021.4227945/
edited the updater script
View attachment 5412179
View attachment 5412181
error 7 again...
So i tryed hasangillani66 method installing OrangeFox and adb then copying recovery.img to the adb directory but im getting some error when typing device, also everytime a connect the j5 to the pc via usb i hear the usb connection sound but cant see anything in my computer.
View attachment 5412187
View attachment 5412189
View attachment 5412197
View attachment 5412203
Click to expand...
Click to collapse
TBH, I don't understand what you are trying to do with ADB,
Odin works while the device is in download mode, you should power off the device and then either reboot via recovery to bootloader mode or directly by pressing the key combo to download mode.
Extract the image from Orange Fox recovery (usually it comes into a zip with add-ons), compress the recovery image into a tar using 7zip, uncheck in Odin "Auto reboot" option and after to flash it, reboot manually to the new recovery, transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
That's all regards Orange Fox recovery.
Thank you again for your helping a low tech savvy person like myself, well i managed to get somewhere this time as the photos will explan
turned zip to tar
flash passed
starts up with orangefox
now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
thanks again for being so patient.
68EC000 said:
Now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
Click to expand...
Click to collapse
Download Ofox zip from their website. Your device can be found here Orange Fox J5 2017
The XDA thread for orange fox for your device can be found here
68EC000 said:
Thank you again for your helping a low tech savvy person like myself, well i managed to get somewhere this time as the photos will explan
View attachment 5412943
turned zip to tar
View attachment 5412947
flash passed
View attachment 5412949
starts up with orangefox
now when you say
transfer the Orange zip file to your SDCard and flash the zip to have all the scripts and add-ons integrated.
does that mean turn these files in the photo below in one zip file and transfer to SD card & flash
View attachment 5412963
thanks again for being so patient.
Click to expand...
Click to collapse
Oh Man, I hope you didn't brick your device, the recovery image must be targeted to the AP slot, not to the BL.
If you encountered some issue with a normal boot flash back again the BL file supposed to be in the stock Samsung firmware, extract it from there and compress it as tar with 7zip.
The Orange Fox zip is the same from which you extract it the recovery image, as you could see it contains other files that can't be flashed through fastboot method (for other devices) or download mode (for Samsung) and the zip have to be flashed through Orange Fox to permanently have those files in your SD card in the Fox path directory. Again, is the same zip where you did get the recovery image from.