Related
I flash my i780 with i780_DXHC_Rev12.img and now i have a big problem
EBOOT+PDA+PHONE
Help pls
Hi,
where did you find this ROM ?
http://forum.xda-developers.com/showthread.php?t=390932
this image contains the eboot+PDA+PHONE
tks
you should try another rom
I can't find a full rom eboot+PDA+PHONE
here the radio rom XIHA7
http://forum.xda-developers.com/showpost.php?p=2114173&postcount=13
here the pda rom SHC3
http://forum.xda-developers.com/showthread.php?t=388067
and a thread that can help you
http://forum.xda-developers.com/showthread.php?t=380723
I trust you tried what I suggested in the other thread ( http://forum.xda-developers.com/showthread.php?t=390996 )
In the flashing log form the mirage you posted there, I don't see that the phone part finished as it should.
Have you had the the modem drivers installed correctly? Did you trim the log?
Also, possibly the img file you flashed was corrupted.
Try downlowding the file and extracting it again before reflashing.
Make sure you don't have phone.bin etc. under C:\ in your PC before reflashing.
Let us know what results you achieved with any of your trials...
Good luck
I tried everything and nothing.
5 ROMs / 2 Full ROMs
Analyzing the Combined Image...Done!!
Calculating file parameters(DISKIMAGE)....
Calculating file parameters(DISKIMAGE) Done!!
-------------------------------------------------------------------------------------
PDA Device 1 ready to download!
-------------------------------------------------------------------------------------
PDA 1 starts downloading...
Don't plug it out until the label becomes blue!!!
-------------------------------------------------------------------------------------
EBOOT will be written.
Total 1 PDA region(s) will be written .
PHONE will be written.
-------------------------------------------------------------------------------------
Downloading EBOOT...
EBOOT finished!!
Downloading PDA region #1(DISKIMAGE)...
PDA Write count : 607
PDA finished!!
Downloading PHONE...
GetSize : 13674496
PDA 1 finished downloading!
I need a Full Orange Rom
It's may last tried,
tks
And the device works ?
If you had SH3 PDA ROM , you 've got HARD RESET shortcut in start/settings/system
yes, phone, GPS and all aplications.
HARD RESET don't change nothing
tks
I need a Orange eboot.
tks
help me please
Hi everyone
you know that a big problem of upgrading using multiloader is that all of applications and our data will be deleted due to a firmware upgrade
*This method is found by mylove90 so all credits goes to him
special thanks to mylove90, adfree, and everyone who have helped this developement
Upgrading using this method is by using "PFS" file like kies upgrades
1. first you should prepare two firmwares, one is the firmware which is installed on your phone and the second is the firmware you want to upgrade to
2. Then you need to extract files of the new and the old firmware so download Trix, Select input file (You can make PFS file from a mix between FFS , ShpApp , CSC (Not Rcrs compressed part)) but just FFS is enough
then go to "scripts" tab and select "fs_shell.trx" and add it then run the script and ...
3.then download Winmerge (google it!) its an open source application which compares two files or folders with one click
then compare the new firmware folder and old firmware folder
then in view tab choose the files we want for upgrading
4. the files which are needed are "Different files" and "Unique files" from new firmware, so copy them to a new folder
also the "unique files" from old firmware must be deleted so "copy path names" and change path names to the correct pattern ex:"/appex/sys/blabla"
5. we can delete these files during PFS upgrade by adding the file paths to "/debug/PfsDeleteList.txt" file which we'll include it in our PFS
5. every thing is done
now just download wave_remarker and in FW view select "open dump" and select the files which we put into a new folder!
make a new folder named "debug" and put a txt file named "PfsDeleteList.txt" which contains the path of files which should be deleted during pfs upgrade
then save file as PFS
6. open multiloader and first check "boot change" and flash the new firmware's boot files
then again flash other firmware files (which does not contain FFS, CSC, shpapp (just the files which you extracted)) and includes pfs file
*note that no checkboxes in this level should be checked in multiloader
Thanks I will test this method
I have some questions from who have made this method
when i try dumping just FFS and making pfs of that in flashing it says error: shpapp write
when i try dumping FFS and Shpapp it says error: csc wite
when i try dumping FFS and shpapp and csc it says error: pfs write
edit
for deleting extra files i try putting all file paths into pfsdeletelist.txt
should i use _CSC_FsDeletelist.ini for some of them?
Sorry
I got no clue what you did wrong
Never tested the update from bada 1.2 to 2.0
Best Regards
when i tried bada 2 to bada 2 upgrade
everything was ok but at the end it says CMD_USB_LOCK fail
i could successfully turn my phone on but after some seconds a blue screen appears and it says:
platform "so" checking is failed
Platform "so" modification is detected!!!
Then you didn't edit the file handling .so signatures to add in it new signatures
You can find such a file in the data folder with .so files
It is named : GeneralSoInfo.so.sig
Edit it with Notepad++ only
If you don't know WTH you are doing please just stop !
Best Regards
Its not ever easy.
Depend really exact on Firmwareversion and what you want or what you did...
NOT TRY if you need data on your handset.
At your own risk.
platform "so" checking is failed
Platform "so" modification is detected!!!
Click to expand...
Click to collapse
This is ""standard"" Error message...
I have seen this also during my database experiments...
DB2 folder...
Or some spxxfing thingies...
More infos possible. If you play with Debug Level MID or HIGH...
Then you got if luck Blue Screen with additional infos, what goes wrong...
Feel free to learn.
Your handset will not explode, BUT again.
Security since XXJL2 is improved... since bada 2.0 higher.
All mistakes or Errors made by oyu leads to Security fail...
So you can loss data.
Backup before all you can.
Good luck.
Best Regards
mylove90 said:
Then you didn't edit the file handling .so signatures to add in it new signatures
You can find such a file in the data folder with .so files
It is named : GeneralSoInfo.so.sig
Edit it with Notepad++ only
If you don't know WTH you are doing please just stop !
Best Regards
Click to expand...
Click to collapse
adfree said:
Its not ever easy.
Depend really exact on Firmwareversion and what you want or what you did...
NOT TRY if you need data on your handset.
At your own risk.
This is ""standard"" Error message...
I have seen this also during my database experiments...
DB2 folder...
Or some spxxfing thingies...
More infos possible. If you play with Debug Level MID or HIGH...
Then you got if luck Blue Screen with additional infos, what goes wrong...
Feel free to learn.
Your handset will not explode, BUT again.
Security since XXJL2 is improved... since bada 2.0 higher.
All mistakes or Errors made by oyu leads to Security fail...
So you can loss data.
Backup before all you can.
Good luck.
Best Regards
Click to expand...
Click to collapse
I havent touched .so files ever
but as this is a custom rum which i want to upgrade to maybe the problem is here
so i try upgrading to another fw
in learning these things nothing else is important for me
i have backup of my apps that are important for me
so i try everything with your help
I havent touched .so files ever
Click to expand...
Click to collapse
This Error message is for wide range of Security issues...
Only if you enable Debug Level to see Blue Screens for more details...
Example for Blue Screen is attached...
1.
Post your Blue Screen...
Maybe we can help you...
2.
Or upload your files.
MAYBE someone has time to check...
Maybe with password and password only via PM, to prevent noobs to kill their handsets...
3.
To add any other Apps is not good idea... also leads to fail...
Security HIGH
Best Regards
Now i have full flashed to another rom so i dont have that bluescreen to post it for you
but bluescreen is showing just that 2 lines i wrote
first of all i'll try another fw to upgrade to
maybe the problem was with this fw
if again i failed, i'll try to upload my files (cuz my internet speed is very low!!)
Oh WTF i think i've found the problem
when i make a pfs using wave remarker then i add it into multiloader, it writes s8500 in front of pfs
but my device is s8530
how can i solve this problem
i havent seen such settings in wave remarker
i myself found a solution for this and made a correct pfs
but again multiloader says CMD_USB_LOCK fail
I think the best way for me is to make a video of what i do yes?
and someone do me a favor and kindly check whats my fault
I'll make a video in the next days
but again multiloader says CMD_USB_LOCK fail
Click to expand...
Click to collapse
Depend what you did... you could ignore this from Multiloader...
I see this Info often if I play with my modified apps_compressed... or do other stuff. Then Autorestart not work with Multiloader...
Try to press ON OFF... (hold Button to force Restart)
At your own risk.
Not during Bootloader write.
Best Regards
I have encountered this error while using modified apps_compressed and rebooting was fine
but in this case when i try to reboot i see the blue screen or the handset stops on the first screen:
"WAVE 2 S8530"
"WAVE 2 S8530"
Click to expand...
Click to collapse
apps_compressed is PROTECTED by Bootloader...
It checks Integrity...
For easier handle unsecdload.fota...
This is only for S8500 available.
For S8530 you can't easy use modified apps_compressed... WITHOUT dataloss.
As you have to flash more then once ...
So all data is erased... before handset can start proper...
Best Regards
adfree said:
apps_compressed is PROTECTED by Bootloader...
It checks Integrity...
For easier handle unsecdload.fota...
This is only for S8500 available.
For S8530 you can't easy use modified apps_compressed... WITHOUT dataloss.
As you have to flash more then once ...
So all data is erased... before handset can start proper...
Best Regards
Click to expand...
Click to collapse
Thank you but you didnt understand what i mean !!
i said i see this error while editing apps_compressed too
but in this case i'm not doing that but again i see this error
this is the video of all i do:
http://dolphintest.co.cc/video.rar
i want to make a pfs for upgrading from JPKA1 to XXKL6
here i encounter error: pfs write
if you can't understand a part, mention here
Please check the video so we can solve my problem!!
video is just 10 mins so it doesnt take so much time
JPKA1
Click to expand...
Click to collapse
XXKL6
Click to expand...
Click to collapse
This is bada 2.0... I'm sure, I used often...
But is JPKA1 not bada 1.x
You can't mix bada 1 with bada 2...
Please correct me, if I'm wrong.
Best Regards
yes your right
but why we can't upgrade from bada 1.2 to bada 2?
by the way i've tried bada 1.2 to bada 1.2 upgrade and bada 2 to bada 2 upgrade but same problems
but why we can't upgrade from bada 1.2 to bada 2?
Click to expand...
Click to collapse
Samsung did some funny things...
"New" Bootloader, new Memory Map...
Compare adresses in Multiloader... so NOT same position...
So major changes... maybe not impossible for Samsung to convert some...
Anyway. Its Security reason and to have "clean new" OS.
Maybe also to clean all Spoofer...
I have not seen whole Video...
No idea yet.
Maybe someone else...
Best Regards
Hi every one !
I'm using the Belgian firmware with a Wave 2 TLBLB1 and I'm getting some strange errors after an upadte :
- The boot screen is reversed
- The boot animation is played in reverse
(just annoying)
- After doing the Samsung apps update it can't launch it says : " Impossible to launch (...) invalid app"
I tried several times to hard reset and recover a clean bada but after each samsung apps update the same error appear.
Does some know from where those errors come from ?
Thanks in advance.
Solution :
- Do a hard reset
- Don't recover your settings files and apps
- Do the update
Solution 2, thanks to mylove90 :
-Try removing it by deleting its folder with TK file explorer (edit ini file to make it work with bada 2.0)
-Copy Samsung Apps.oap file....i'll assume you know the path of that file
-Open it with 7z or any other program
-Edit manifest.xml file to give it higher version number
Click to expand...
Click to collapse
Are you updated your phone via OTA ?
Yes it was an OTA update. But apart from the bug I listed, everything works fine.
Exactly Don't know about samsung apps but Reversed also for me as this
http://forum.xda-developers.com/showpost.php?p=25923810&postcount=119
hahahahahahahahaha
These bugs are so funny
Thanks to Samsung we don't have OTA updates in Egypt
But i guess that you just got a bad Samsung Apps update
-Try removing it by deleting its folder with TK file explorer (edit ini file to make it work with bada 2.0)
-Copy Samsung Apps.oap file....i'll assume you know the path of that file
-Open it with 7z or any other program
-Edit manifest.xml file to give it higher version number
In Theory , This should prevent the update & make your Samsung Apps work
Best Regards
Yeah it's exactly the same... It should be normal for Samsung that the phone boot that way...
Could it be a general error from the OTA system update ?
For the samsung apps I expect the same bug since it was also with an OTA update.
Edit : yes I will try later this method I don't have time to do it right know I will report when I did it.
Edit 2 : So I hard reset and try again to update and it works even after the update. But after recovering my files it bugs. I will try to recover before updating.
Just a simple/noob question how do you express the files into a .oap file ?
Edit 3 : WTF it works. It should have been a setting error. Strange.
This is NO bug...
This is VISUAL teststuff...
Firmware like XXKKV... XXLAV, XXLBV
These are for internal testing... it is easier to see if success, instead wait and enter *#1234#
Read here:
http://forum.xda-developers.com/showthread.php?t=1363328
Remember... as V is highest "Character/Digit"... Kies nor OTA update again...
You have minimum to flash other apps_compressed.bin with Multiloader.
Best Regards
adfree said:
This is NO bug...
This is VISUAL teststuff...
Click to expand...
Click to collapse
Thanks I didn't know.
Anyway it works great. I'll wait untill next firmware.
Overview
Now, I have seen many people facing problems like lost IMEI or NVRAM warning in their wifi list! Well, these are normal errors when you often flash a custom and wiped system or update using SP Flash Tools. So fix isn't that hard! But still, many people suffer from this! Now, this guide is applicable for every device(MTK) but BPLGU modem file will vary from device to device. I have specially made this guide for Lenovo Vibe K4 Note users!:laugh:
WARNING !!! IMEI CHANGING IS ILLEGAL. THIS GUIDE ONLY HELPS YOU HOW TO RESTORE ORIGINAL IMEI OF YOUR DEVICE! I DONT TAKE ANY RESPONSIBILITY OF ANY ILLEGAL ACTION TAKEN AGAIN YOU! BE AWARE IF YOU ARE NOT SURE FOR WHAT IMEI IS USED FOR ALSO I DONT TAKE ANY RESPONSIBILITY OF DEAD DEVICES/ BRICKS! PLEASE DO SOME RESEARCH IF YOU ARE NOT AWARE OF ANYTHING. HOWEVER, THIS GUIDE WILL HELP YOU DEAL WITH THINGS, IF YOU READ CAREFULLY AND FOLLOW INSTRUCTIONS THEN YOU DONT NEED TO WORRY ABOUT ANYTHING!
Click to expand...
Click to collapse
So lets fix it up !
Required stuffs !
Windows PC (7/8/8.1/10)
Usb Cable
Few tools
Drivers
Your device, ofc !
Download Section !
1. Scatter files !
2. MauiMETA
3. Temoprary IMEI fix.zip
Now before we start doing anything make sure you download everything from the download section. Also, make sure your device is having TWRP installed.
Process !
Now most of you must have thought hey Max where is NVRAM fix? There was nothing about NVRAM in title Well chill down I will target NVRAM NOW !! So let us begin! Now as you have downloaded entire scatter files so NVRAM needs entire scatter files. "Woosh! Thank god it was useful somehow" most of you must have thought Hehehe Well one more thing if you are using permanent NVRAM fix then use it before you flash IMEI or else you lose it again if you fix NVRAM after IMEI. However, a temporary fix can be flashed later on.
* Now navigate to the firmware folder
* Look for scatter file open it in notepad or notepad ++
* There look for this line, "partition_name: NVRAM"
* There you will also notice, "s_download: false"
* Just change it to, "s_download: true"
* Save and exit!
* Open Sp flash tools and load scatter file(Remember a thing, you will have to use an older version of SP Flash Tools)
* You will see checkbox of NVRAM just choose it and keep rest options unchecked!
* Flash into your device and all set!
NVRAM IS FIXED PERMANENTLY :good:
But now for those who are lazy doing this, there is a temporary zip file which you can flash and NVRAM problem will be fixed for a limited time to do so just go to download section and download temporary fix zip file and flash it into TWRP (Yes, that's why we needed TWRP):angel:
Now before we start doing anything make sure you download everything from the download section. Also, make sure your device is having TWRP installed. (YES AGAIN MAKE SURE YOU HAVE EVERYTHING)
• After that, run Maui META 3G
• Use USB COM
• From Options menu, select “Connect smartphone in meta mode”.
• Press Reconnect and connect the phone in the switched off state.
• Wait for a minute. Your Device automatically boots into meta mode. The blinking led will become yellow and you can see "connected with target"
• Now from the drop-down menu select “IMEI download”. Click ok till you see IMEI download box.
• Click Change NVRAM Database FIle and browse to “MT6753 DB” folder and select the following file.
File\MT6753\
BPLGUInfoCustomAppSrcP_MT6753_S00_K5_ROW_LWG_V56_ 1_lwg_n (BPLGU modem file for mt6753, do a double check as the name might change with firmware versions).
[Well I have not extracted this file yet from stock ROM scatter files. However, I have given you the download link of entire stock ROM look the file there itself !]
• Click ok on any warning.
• Leave IMEI Increasemnt 0.
• Write first 14 digits of your IMEI in IMEI box and last 15th digits will go in checksum(should be entered automatically). Eg:- if IMEI is 123456789123456, write 12345678912345 in IMEI and 6 in the checksum. Do same for Sim_2
[Now most of you must be wondering where is my IMEI. I don't remember it and also it's not there in the list. Don't worry pull your back cover and you will see IMEI sticker there just type the same IMEI]
• Press Download To Flash. You will see Download IMEI flash successfully. Now close the box (or alt+f4 or close from task manager if stuck).
• Restart the phone
• Open Dialer and type *#06# and you will get your valid IMEI number.
* Well if you saw the same IMEI then you are done !!! :good:
Credits : Yaas !! Why not ?
meprakash_pyc
Sahil_Sonar
KM (One who made NVRAM fix for lazy people :silly
If this post was helpful to you just hit :good: below my posts !
Drivers ?
Hey Maxx where are our drivers? Well, come on relax as you have downloaded scatter files all the drivers are there you can additionally get extra drivers from my https://forum.xda-developers.com/k4-note/how-to/bootloader-unlock-t3846902 another post [/url] Yes the same one! TWRP one! I have added ADB Drivers there follow the same process also there is a manual how to install drivers same is applicable for these drivers!
after loading that modified scatter file, it says that it should not be treu value
yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.
royskeyz said:
yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.
Click to expand...
Click to collapse
Actually, I have tested this thing on my own device... No idea what's wrong with you. You can also try notepad c++
jaskoooo said:
after loading that modified scatter file, it says that it should not be treu value
Click to expand...
Click to collapse
royskeyz said:
yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.
Click to expand...
Click to collapse
Try older version of SPFT.
I've downloaded your drivers and tried many other drivers,None worked,Please help me.With the drivers i have im able to Flash stock through SP,Device gets detected too,But i dont know y its not working for this tool or SN writer..This is the error im getting..Communication through either RS232 or IPC error,Please reconnect..
JaSomTy said:
Try older version of SPFT.
Click to expand...
Click to collapse
Exactly!
where is nvrm file 's ?
where is nvrm file 's ?
Can anyone tell which version of sp tool worked for them? that would really really be helpful
Edit: Files are no longer available on google drive
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
link is restricted
Bro. Share file pls on your googledrive. We cantdownload it
Flar4eg said:
Bro. Share file pls on your googledrive. We cantdownload it
Click to expand...
Click to collapse
Excuse me, is that I uploaded the files to my google drive cloud and I detect a dll, or part of the flashtool as a virus, now I upload it again and put the link
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
multiuploader error: WinDNWApi.dll file could not be found.
Skyfall191299 said:
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Click to expand...
Click to collapse
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Skyfall191299 said:
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
Click to expand...
Click to collapse
getting error that el3mon_dram not found. can you help me?
Hello someone has the files ? The download link is inactive
The download link is inactive, please active or reupload please.
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
good jod
im follwed to this instruction but all links not woriking
pla give me ur telegram or whtas app
and upload files to the new link plz
eldon301 said:
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Click to expand...
Click to collapse
how to create with hex bro ?
links not woriking
link isn't working please fix
akbarshoxdedamirzayev said:
how to create with hex bro ?
Click to expand...
Click to collapse
Find the exact firmware that’s currently in the device, extract sboot from the firmware. You need to find correct location of bl1 bl2 el3 and others, names correspond to which is cut. You need 5 files from sboot. Am stuck on the forth file failing and I still don’t understand how to find them. What I did was follow others with exactly the same problem to see and understand how they got there’s and then tried it on my sboot. I am failing on part4 don’t even know how to make a cfg but from what I understand e for exynos and the number after so mine is e7885. Still not sure like I said
http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip/file download link
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
Can you check the addresses and lenghts of the partitions cut out of sboot?
I think you've made a mistake.
Can give me the precise partition details?
Are you 100% positive that this is valid at least for most devices of the same chipset?
I'd like to try to make an automated script or a tool of some sort.
Also when I was dividing my A515F U5 sboot I've spotted some long breaks in data which I assumed were empty blocks at the end of partitions.
What confused me about it is that I didn't find those where you said partitions are ending.
Can you demonstrate graphically your partitions in a linear projection?
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
eldon301 said:
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
Click to expand...
Click to collapse
I'd like to help
NonStickAtom785 said:
I'd like to help
Click to expand...
Click to collapse
Hello my friend I am try to get life back into a A750G, it’s completely hard bricked showing exynos usb in device manager. Can i direct message you or should I keep it in the forums. I was falling on part 4 off the files needed to create, I didn’t even know if my cfg file was correct but I tried my best at understanding the creation of the files. Plz help my brothers