Here is a detailed guide on how to remove the bootloader warnings that appear at boot after oem unlocking your bootloader
please be sure to go over to here and give juda iskariotsky a like
if you want to remove them your self you will need
(only tested on Exynos)
Modded 7zip = Gdrive - Mega - Dropbox
Odin 3.14.1.3b = Gdrive - Mega - Dropbox
your firmware extracted
to just remove them without doing it your self
flash the up_param.tar file in odin under the BL tab
get it here = Gdrive - Mega - Dropbox
to remove them yourself you will need to follow these steps
(there is a video below too)
1st - download and install 7zip standard , and download and unzip odin
2nd - navigate to the extracted firmware and right click on "BL_S908BXXS2AVDB_S908BXXS2AVDB_MQB51326408_REV01_user_low_ship_MULTI_CERT.tar.md5" {your firmware may be different}
{
"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"
}
3rd - select open archive with 7zip standard, once its open drag "up_param.bin.lz4" into the firmware folder window and drop
4th - right click "up_param.bin.lz4" and select "extract to "up_param.bin/"" using 7zip standard
5th - navigate into "up_param.bin" folder and right click "up_param.bin" and select open archive using 7zip standard
6th - select the two files "svb_orange.jpg" and "booting_warning.jpg" keeping your finger pressed on "ctrl"
7th - press the "red x" delete icon in the top bar to delete them
8th - close that window, and in windows explorer right click the "up_param.bin" inside the "up_param.bin" folder and select add to archive using 7zip standard
9th - in the archive format tab select "tar" and click ok, that file is now ready to be flashed in odin
10th - open odin, clicking "ok" to dismiss the warning, the press "bl" and navigate to "up_param.tar" inside the "up_param.bin" folder
done......
thanks to
juda iskariotsky for making it common knowledge
Kangi26 for patched odin
Do you recommend to keep the created up_param.tar to be used after each update?
i would like to say yes, but its possible samsung changes something and flashing the up_param conflicts with a change they make and causes an error, its unlikely, but never say never
Well detailed Guide, Thanks!
Wish there was something for Snapdragon users.
Nice
Does it work in snapdragon? Is it risky to test? Don't want to reflash and go through all the hassle of getting the phone exactly as it is now, since we don't have TWRP backups yet...
ffp. said:
Does it work in snapdragon? Is it risky to test? Don't want to reflash and go through all the hassle of getting the phone exactly as it is now, since we don't have TWRP backups yet...
Click to expand...
Click to collapse
i wouldnt flash the file, but if you follow the guide, you can look in your directories for the same/similar files, its untested on sd variant
gav83collins said:
i wouldnt flash the file, but if you follow the guide, you can look in your directories for the same/similar files, its untested on sd variant
Click to expand...
Click to collapse
I have tried on snapdragon but there aren't such files there.
mrjoy said:
I have tried on snapdragon but there aren't such files there.
Click to expand...
Click to collapse
can you screenshot that folder for me ? up_param.bin/
gav83collins said:
can you screenshot that folder for me ? up_param.bin/
Click to expand...
Click to collapse
im going to download your firmware and some exploration, bare with me
gav83collins said:
im going to download your firmware and some exploration, bare with me
Click to expand...
Click to collapse
Its great. Thank you for your support.
gav83collins said:
im going to download your firmware and some exploration, bare with me
Click to expand...
Click to collapse
Exynos has the param bin file, Snapdragon possibly has it somewhere else.
Firmware code is S908E.. Give it a try, and its lovely if you succeed !
Cheers!
JazonX said:
Exynos has the param bin file, Snapdragon possibly has it somewhere else.
Firmware code is S908E.. Give it a try, and its lovely if you succeed !
Cheers!
Click to expand...
Click to collapse
mrjoy said:
Its great. Thank you for your support.
Click to expand...
Click to collapse
ive had a prelimenary look around but, the file types are a lot different to mine, so im gonna have to get more software to be able to open and explore further
gav83collins said:
ive had a prelimenary look around but, the file types are a lot different to mine, so im gonna have to get more software to be able to open and explore further
Click to expand...
Click to collapse
Yes sure. You are the person that can make it possible. Good luck.
gav83collins said:
ive had a prelimenary look around but, the file types are a lot different to mine, so im gonna have to get more software to be able to open and explore further
Click to expand...
Click to collapse
I was going to post my print, but mrjoy posted before. Digging around, it seems that this is not possible for snapdragons, at least for previous devices. It seems that the boot file is mounted during the boot and images are loaded, there is no way to extract and replace the images there without Samsung's signature.
I'm just writting what I found in other threads, though.
If you want to dig, it seems it is part of abl.elf file. See if you can get this to work.
Maybe if we could do that by another mean?
Any updates for S908E?
mrjoy said:
Any updates for S908E?
Click to expand...
Click to collapse
I wish for the same too. Guess no luck so far
I have followed your steps but it failed with my S22 Ultra Exynos :-(
Could it be because of "Universal Samsung PARAM Changer" Magisk's module?
Or "WETAmod" Magisk's module?
then there is no way to remove the bootloader warning in the snap version
Related
[TUT]Extract kernel "zimage" From boot.img and Convert to .tar and Flash using Odin
[Extremely Noob GUIDE]Since there is no explained and easy Guide to Extract Kernel [zimage] and Ramdisk [Ramdisk] from Boot.img, Then Convert it to zimage.tar and Flash it using Odin
Well here it is step by step:
Note: This Method is used to Extract Kernels form Stock Rom's Boot.img
First you need to install Python, which is round about 17MBs software freely available on python website.
Step 1:Download the attached Python script named "split_boot_img" from attachments down Below, Extract it and copy to the folder created in Step 2.
Step 2:Create a folder with any name you like. I recommend "boot.img extraction".
Step 3: Copy the boot.img, you want to extract, to the folder you created in Step 2.
Step 4: Run the script named "split_boot_img"by double-clicking and see the magic.
Congratulations!!! Here you go. the "zimage" and "ramdisk" files are extracted.
Now the Conversion Part:
Step 1: Download this IZARC software and install it from Here:http://www.izarc.org/download.html
Step 2: Open the folder created in First-Step 2.
Step 3: Right Click the ziamge File Extracted from boot.img. as in Image 1 in attachments.
Step 4: Select add to archive file from IzArc right click options as in Image 1 in attachments.
Step 5: Now scroll the Archiving type to ".tar" as in Image 2 in attachments.
Step 6: Click the Add button as in Image 3 in attachments.
Last Step: Now flash the "zimage" file created in Step 6 Using Odin.
View attachment split_boot_img.zip
Image 1:
{
"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"
}
Image 2:
Image 3:
Not Working
extraction doesn't work for me :/
shivasharmaarya said:
extraction doesn't work for me :/
Click to expand...
Click to collapse
Did you follow till last step. What message did you get?
yes
exceptionalkhan said:
Did you follow till last step. What message did you get?
Click to expand...
Click to collapse
Python script of yours is not working.Its giving error which flashes for microsecond and i am unable to see it
shivasharmaarya said:
Python script of yours is not working.Its giving error which flashes for microsecond and i am unable to see it
Click to expand...
Click to collapse
Maybe he should have put in that you need to use Python 2.7.9 not 3.x ... Had the same problem.
All steps worked after, but didn't flash it yet, I'll do it today or tomorrow.
Also you should mention IZArc is full of crapware, it open one install and even if I chose to not install stuff, it installed iStart and Search Enginer extensions to my browsers. After, surprise, another install showed up to actually install IZArc ... not I need to de-crap my system
dotuletz said:
Maybe he should have put in that you need to use Python 2.7.9 not 3.x ... Had the same problem.
All steps worked after, but didn't flash it yet, I'll do it today or tomorrow.
Also you should mention IZArc is full of crapware, it open one install and even if I chose to not install stuff, it installed iStart and Search Enginer extensions to my browsers. After, surprise, another install showed up to actually install IZArc ... not I need to de-crap my system
Click to expand...
Click to collapse
Did the kernel.img actually work for you? I tried this same process as well. It took me 4 hours to clean all the maleware from my laptop. I mad the .Tar file and tried to flash it. it failed completely. I think this OP needs to be removed. More than likely the OP is getting paid for all the downloads he is tricking people into.
Chillyz12 said:
Did the kernel.img actually work for you? I tried this same process as well. It took me 4 hours to clean all the maleware from my laptop. I mad the .Tar file and tried to flash it. it failed completely. I think this OP needs to be removed. More than likely the OP is getting paid for all the downloads he is tricking people into.
Click to expand...
Click to collapse
No, it failed also. Yes, it should be removed.
Ended up using http://forum.xda-developers.com/showthread.php?t=2446269 but for a strage reason Odin would not like it when I moved the .tar archive from a folder to an other from that method (I keep my pc organized), had to create the tar, flash it from that folder, then... deleted it because after I couldn't use it anymore.
dotuletz said:
No, it failed also. Yes, it should be removed.
Ended up using http://forum.xda-developers.com/showthread.php?t=2446269 but for a strage reason Odin would not like it when I moved the .tar archive from a folder to an other from that method (I keep my pc organized), had to create the tar, flash it from that folder, then... deleted it because after I couldn't use it anymore.
Click to expand...
Click to collapse
It won't trip knox, right?
Joker87 said:
It won't trip knox, right?
Click to expand...
Click to collapse
Flashing any modified boot / kernel / recovery trips Knox, doesn't matter what method you use. Sometimes even stock trips Knox as some users said.
What i did was take a stock rom from SamMobile that was 'hackable' through TowelRoot, extracted the kernel with WinRar, made the kernel flashable in Odin using that tool, flashed it via Odin, rooted device with TR, then used same steps to download,extract,make kernel bootable to restore my original kernel. Knox stayed 0x0 on i9195.
You can try reading about Heimdall. Supose you can flash without Odin and without converting. It would make your life easier, but for me it didn't work (didn't start on Win 64bit, i think i needed another MS visual c++ , a dependency of Heimdall).
ps.: the tool to create flashable archives would't work for me just by double-clicking, so I had to open an command prompt - CMD with admin rights, go to the directory where i had the tool and type ImgToTar.MD5.bat . Just put everything in C:\tool including recovery.img / boot.img or kernel.img then go start-> type in search box CMD -> right-click on the result and Run as admin -> in the black box type the next text followed by Enter key:
cd /
cd tool
ImgToTar.MD5.bat
I hope it works, i need it for the same reason of you, flashing an older kernel to root with towelroot keeping knox 0x0 at the end of this process
please download Root to Samsung Galaxy Note Pro 12 3g sm-p901
1 ..
{
"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"
}
2..
3..
Means no one will have the same hardware and the Root .. Please solution of the problem
alhgan2014 said:
I hope I Want Root attention to two Ergonomics I have tried before and failed periods transferred
Waza possible, please download Root to fit his two Samsung Galaxy Note Pro 12 3g sm-p901
Click to expand...
Click to collapse
um...
Thanks
Did you try towelroot?
Towelroot is only for Qualcomm devices, the P901 is an Exynos device.
Read this: http://androidxda.com/root-samsung-galaxy-note-pro-12-2-sm-p901
And the original autoroot file is in this list: http://autoroot.chainfire.eu/#odin
dodo99x said:
Towelroot is only for Qualcomm devices, the P901 is an Exynos device.
Read this: http://androidxda.com/root-samsung-galaxy-note-pro-12-2-sm-p901
And the original autoroot file is in this list: http://autoroot.chainfire.eu/#odin
Click to expand...
Click to collapse
Yeah I think the only option is cf autoroot and tripping knox
Sent from my Fired-up Kitty
Ok, now that he's fixed his comment so it makes a tiny bit of sense. I had this problem with the p900 as well. This was how I fixed the hang on cache issue very quickly.
Get 7zip.
1. Open the zip file you got for cf-autoroot with 7zip. Extract the CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar.md5 file.
2. Remove .md5 extension and rename the file CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar
3. Open this file with 7zip, extract recovery.img from it. Set this aside, you'll need it in a few more steps.
3. Download Caboomi's Recovery img2tar odin maker tool from here http://forum.xda-developers.com/showthread.php?t=2281287
4. Unzip the tool into a folder. Delete the recovery.tar.md5 it comes with. You will also see a Runme.bat file.
5. Edit the bat file with something like Notepad ++. The second line will be
Code:
bin\tar -H ustar -c recovery.img > recovery.tar
Change this to
Code:
bin\tar -cf recovery.tar recovery.img
Save the file.
6.Remember the recovery.img file you took from the CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar in step #3? Throw that file into the same folder where the Runme.bat file is located.
7. Run the .bat file. It will produce a new recovery.tar.md5
8. Flash this new recovery file in Odin. HAVE AUTOREBOOT TURNED OFF.
9. Flash the original CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar.md5 file after that.
10. Hopefully success?
Got everything but the result is still the same problem
Gatsrom said:
Ok, now that he's fixed his comment so it makes a tiny bit of sense. I had this problem with the p900 as well. This was how I fixed the hang on cache issue very quickly.
Get 7zip.
1. Open the zip file you got for cf-autoroot with 7zip. Extract the CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar.md5 file.
2. Remove .md5 extension and rename the file CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar
3. Open this file with 7zip, extract recovery.img from it. Set this aside, you'll need it in a few more steps.
3. Download Caboomi's Recovery img2tar odin maker tool from here http://forum.xda-developers.com/showthread.php?t=2281287
4. Unzip the tool into a folder. Delete the recovery.tar.md5 it comes with. You will also see a Runme.bat file.
5. Edit the bat file with something like Notepad ++. The second line will be
Code:
bin\tar -H ustar -c recovery.img > recovery.tar
Change this to
Code:
bin\tar -cf recovery.tar recovery.img
Save the file.
6.Remember the recovery.img file you took from the CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar in step #3? Throw that file into the same folder where the Runme.bat file is located.
7. Run the .bat file. It will produce a new recovery.tar.md5
8. Flash this new recovery file in Odin. HAVE AUTOREBOOT TURNED OFF.
9. Flash the original CF-Auto-Root-v1a3g-v1a3gxx-smp901.tar.md5 file after that.
10. Hopefully success?
Click to expand...
Click to collapse
Got everything but the result is still the same problem
alhgan2014 said:
Got everything but the result is still the same problem
Click to expand...
Click to collapse
Here I made one for you, try this one in Odin click me I didn't zip it since it's just the tar.md5 file not all the extra odin stuff. Don't modify this file's extensions, put it straight into odin.
After downloading, you should check the md5 matches: 44d09a57009cfdbb322f0c9ca13bd4fe
Let me know if it works. Otherwise we have to look for another problem cause/solution.
Please solution of the problem
Means no one will have the same hardware and the Root ؟
Please solution of the problem
Pleaseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
Salvation is no hope for me is not reasonable Root site developers not to be in the Real Root device
Samsung Galaxy Note Pro 12 3g sm-p901
Thank god! Solution of the problem
Thank god! Solution of the problem by means of friend gatsrom
alhgan2014 said:
Salvation is no hope for me is not reasonable Root site developers not to be in the Real Root device
Samsung Galaxy Note Pro 12 3g sm-p901
Click to expand...
Click to collapse
From the message I got from you this morning, we seem to have got it going. Device is still rooted and okay right?
Gatsrom said:
Here I made one for you, try this one in Odin click me I didn't zip it since it's just the tar.md5 file not all the extra odin stuff. Don't modify this file's extensions, put it straight into odin.
After downloading, you should check the md5 matches: 44d09a57009cfdbb322f0c9ca13bd4fe
Let me know if it works. Otherwise we have to look for another problem cause/solution.
Click to expand...
Click to collapse
can u please re-upload the file, i got the same exact problem. ill be just flashing the file using odin right?
thx in advance
Please re up the file
Gatsrom said:
From the message I got from you this morning, we seem to have got it going. Device is still rooted and okay right?
Click to expand...
Click to collapse
Hi Gatsrom,
I have the same problem with my P901, tried already the steps you mentioned but didn´t work.
Can you please re up the file so I can try this.
Thanks
posting error
21667 said:
can u please re-upload the file, i got the same exact problem. ill be just flashing the file using odin right?
thx in advance
Click to expand...
Click to collapse
HNevenEG said:
Hi Gatsrom,
I have the same problem with my P901, tried already the steps you mentioned but didn´t work.
Can you please re up the file so I can try this.
Thanks
Click to expand...
Click to collapse
Let me go through the emails and files, see if I still have it.
Please help me to solve th eProblem
alhgan2014 said:
Thank god! Solution of the problem by means of friend gatsrom
Click to expand...
Click to collapse
Dear alhgan,
do you still have the files you got from Gatsrom?
I have the same problem then you had.
Thanks!
Finally rooted my P901
After hundred times stucked at cache.img I found the reason and got my p901 finally rooted!
Two things which I made wrong, so remember the following two points:
1. You have to switch on USB debugging in “development options” under Settings on your P901!
2. You have to start Odin as Admin!
Go on with the normal flashing procedure:
Start P901 in flashing mode
Start Odin as Admin (use only the Odin version which comes in the package from CF!)
Load tar.md5 File in AP
Connect the P901 to PC
Start
That´s all!
please rebuild the file to root
Gatsrom said:
Let me go through the emails and files, see if I still have it.
Click to expand...
Click to collapse
Tired of all the meathods... nothing works .... even enabling debugging or running odin in admin.... its a request bro.... please please remake the file to root p901... its stuck at the cache.img....
INTRODUCTION
{
"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"
}
Code:
*/WARNING
This tool is in [B]BETA[/B] phase and is not for noobs. If you use this, you are choosing to play with your device on your own.
I will not be responsible for any damage to your device or your belongings in your home.
If you blame me for anything that goes wrong I'll die laughing at you/*
Hello all!
Today I present you F2I converter. This tool can convert system folder back to ext4 image format suitable for flashtools without cygwin.
Basically, this tool was made in keeping mind the format used by lollipop structure where dat files were converted to ext4 format and then unpacked, repacking them was kind of hard (or lazy to do so in my case) as it required linux or Cygwin [Based on Xpirt's Guide. Now I've always preferred a way to avoid linux and cygwin
I managed to put together a set of tools that can easily convert the extracted system folder back to img for flashing and in lollipop can be converted back to dat format on windows.
So this is what this tool is capable of! If you on lollipop and want @xpirt guide to do so then here it is - [HOW TO] Lollipop DAT files | Compression and Decompression
FEATURES
• Supports all Android Versions
• Works without Linux or cygwin
• Generates Log that help to troubleshoot the issues
• No extra software required (Except Git for Windows)
• Supports both way conversion
• Suggest more features
• Much more to come!
HOW TO USE
You need GIT for windows to run this tool. Kindly download and install GIT from HERE
Now install GIT and when you're done download F2I converter and extract it in core C: directory. There will be a folder names as "IMG_WIN" kindly make sure it is extracted in C:
Recommended GIT is v 1.9.4 or newer.
Mostly everything is self-explanatory in the tool but when you will convert "SYSTEM" folder back to "EXT4 img" format you will be asked to enter size in bytes.
Here is what you are asked to do..
1) Open the system.img inside the respective folder you're working on and then right click on it and click Properties
2) In General tab you'll see something like this
Now copy the highlighted part and paste in the box shown below in image
Now you can continue. Ahead
DOWNLOADS
MAJOR LINK
MIRROR
BUGS
This tool is in BETA phase so you are likely to face some bugs. Though I have paid a lot of attention while creating this tool but you may encounter some small code errors (like path not found etc) I request you to kindly see for yourself and correct it.
You are likely to face this error mostly though
Code:
error in bla bla bla ..... failed to allocate block [NUMBERS] out of space?
If you encounter something like this then it will not work with your files. This will occur mostly in Android 2.3.x-4.4.x and in some cases with 5.0 and 5.1
I am trying to fix this issue. Please co-operate
Rest no major bug.
CREDITS
@xpirt for his awesome guide on lollipop compression and decompression of dat files
Google for being so hepful :angel:
XDA for it's awesomeness
XDA:DevDB Information
[F2I Converter] Convert System folder into EXT4 Image without cygwin on Windows!, Tool/Utility for all devices (see above for details)
Contributors
Tech N You
Version Information
Status: Beta
Current Beta Version: v1.0
Beta Release Date: 2015-05-03
Created 2015-05-03
Last Updated 2015-05-03
Reserved.
Reserved Again.
Nice Dude ! extracted xolo one files using this ... hoping to port it for q700s
Great tool mate!
Enviado desde mi OnePlus One
Tech N You said:
.....This tool is in BETA phase so you are likely to face some bugs.....I request you to kindly see for yourself and correct it......
Click to expand...
Click to collapse
i've tried this. see the screenshot. i find only 2 files to copy back to my rom zip.
what about "file_contexts"? can/should the original be retained?
large size difference between original "system.transfer.list" and modified one ok?
Doesn't work for me. I'm unable to find system.img. So I downloaded "sda2img.exe" and I made system.img with it. Then, when I try to recompress system folder in DAT format, there is this problem ( see the screenshot ).
Then I noted that after using it, in "Working_Do_Not_Touch", system.transfer.list and system.new.dat get losts.
m0han said:
i've tried this. see the screenshot. i find only 2 files to copy back to my rom zip.
what about "file_contexts"? can/should the original be retained?
large size difference between original "system.transfer.list" and modified one ok?
Click to expand...
Click to collapse
AlessandroXCV said:
Doesn't work for me. I'm unable to find system.img. So I downloaded "sda2img.exe" and I made system.img with it. Then, when I try to recompress system folder in DAT format, there is this problem ( see the screenshot ).
Then I noted that after using it, in "Working_Do_Not_Touch", system.transfer.list and system.new.dat get losts.
Click to expand...
Click to collapse
Thanks for trying out the tool. You must use same file_contexts
As per your issue sir thing is the output is cleaned up and no file is left back. I request you to try the size from xpirts post on this. Kindly check that and reply back.
[system_new.img?]
Any ideas on how to fix this:
When I try repacking [system folder] back to [system.new.dat] the program throws an error : File not found -- system_new.img
MeTaL-01 said:
Any ideas on how to fix this:
When I try repacking [system folder] back to [system.new.dat] the program throws an error : File not found -- system_new.img
Click to expand...
Click to collapse
Option 4 is the correct one for Lollipop i see u chose option 3
Tech N You said:
....You must use same file_contexts.....
Click to expand...
Click to collapse
did so. upon trying to flash rom zip file, "error executing binary in zip....."
Tech N You said:
Option 4 is the correct one for Lollipop i see u chose option 3
Click to expand...
Click to collapse
I've tried both, none work
MeTaL-01 said:
I've tried both, none work
Click to expand...
Click to collapse
Okay then let me recheck whole thing and I'll revert back to you
ahh boy, you never cease to amaze me. Thanks for this
kirito9 said:
ahh boy, you never cease to amaze me. Thanks for this
Click to expand...
Click to collapse
Glad to know you liked this tool :good:
I keep getting a Permission denied error when using option 4. Any ideas why??
LupusGrande said:
I keep getting a Permission denied error when using option 4. Any ideas why??
Click to expand...
Click to collapse
Tool is not getting administrative privilege.
Kindly make your Windows user prompt to lowest
Tech N You said:
Tool is not getting administrative privilege.
Kindly make your Windows user prompt to lowest
Click to expand...
Click to collapse
after conversion there is nothing in system folder
well done bro ......................though small glitches bt overall grt tool (Y)
I can't convert the system folder back to dat files.
I use option 4 but nothing works.
Where I have to put the system.transfer.list and the system.new.dat?
What I have to do?
Hi all
I hereby present to you a cool addition for our beloved Note3 (SM-N9005 model).
Photos
Thanks to my junior @Kill-Switch
Please read the steps properly before you start flashing.
Don't hold me responsible for any damages you might end up doing to your device if you choose to flash either of the 4 files that I'm providing to you! :cyclops:
1. Go to Download mode.
2. Flash the BL file using Odin (remove Auto-Reboot tick).
3. After its been flashed completely, remove the data cable & pull out the battery.
4. Go to the Download Mode again.
5. This time, flash the CP file using Odin (don't remove Auto-Reboot tick).
These are links to 2 sets:
GPS works fine for me in the newer set, it might work for you with the older set.
1. Old
&
2. New
Tbh, the way I did it was, I flashed the Old set initially (photographs from that time) then I flashed the Newer set (hoping GPS would be better) & I still have the "Powered by Android" text in my phone.
Skip typing - hit
{
"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"
}
instead..
tried the new one, and it works! looks really great, thank you! =)
im testing later gps if it is working properly
Gps working perfect ?
If I'm not wrong, this is the boot splash that you've modified. If so, then let me make one small request . Can you please make another one That says Note 7 instead of Note 3
Edit: I know this basic fact that boot splash (param.bin) has nothing to do with CP (modem) so I only flashed the new BL file with auto reboot ticked in Odin and it was success for me without the need to change my modem or follow the steps in OP. I've got the new boot splash now. Good job mate, hop you will make one that I've requested :good:
immi said:
If I'm not wrong, this is the boot splash that you've modified. If so, then let me make one small request . Can you please make another one That says Note 7 instead of Note 3
Click to expand...
Click to collapse
searching years for that.tried also by my self to made it but no matter how i search never find some good guide to make it done.
so...i also want it
@TheTAMAS man, you are awesome. Haven't tried it yet, but the fact that you've shared for all to experience is awesome.
What I dont get is how this would effect your GPS?
ryuisnod said:
What I dont get is how this would effect your GPS?
Click to expand...
Click to collapse
They are bootloader & modem files.. Modem file affects all the radios on the phone.. Including the ones that relate to GPS..
Skip typing - hit
instead..
Yeah but I thought you just edited the image from the bootloader. Is this a custom bootloader then? Not a lot of info on the OP but I'm still a bit of noob with boot loaders and modems
immi said:
If I'm not wrong, this is the boot splash that you've modified. If so, then let me make one small request . Can you please make another one That says Note 7 instead of Note 3
Edit: I know this basic fact that boot splash (param.bin) has nothing to do with CP (modem) so I only flashed the new BL file with auto reboot ticked in Odin and it was success for me without the need to change my modem or follow the steps in OP. I've got the new boot splash now. Good job mate, hop you will make one that I've requested :good:
Click to expand...
Click to collapse
I didn't do it Myself but this might be what You want..
Edit:the guide(in the link I just shared) is supposed to work only on Exynos based phones..
Skip typing - hit
instead..
TheTAMAS said:
I didn't do it Myself but this might be what You want..
Skip typing - hit
instead..
Click to expand...
Click to collapse
you mean you use this guide and add the Powered by Android?
edit:tried but not work.."dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096" i think this path is wrong..
vagenrider said:
you mean you use this guide and add the Powered by Android?
edit:tried but not work.."dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096" i think this path is wrong..
Click to expand...
Click to collapse
I didn't do anything bro..
Skip typing - hit
instead..
vagenrider said:
you mean you use this guide and add the Powered by Android?
edit:tried but not work.."dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096" i think this path is wrong..
Click to expand...
Click to collapse
because its not sda4 on note 3 its mmcblk0p10
Delete
meawww said:
because its not sda4 on note 3 its mmcblk0p10
Click to expand...
Click to collapse
tried this path..seems ok but when i finish,i go check if param bin is ok extracted in the param folder and the folder is empty..
Do not work on my sm-n900w8
Why?
Thanks
vagenrider said:
tried this path..seems ok but when i finish,i go check if param bin is ok extracted in the param folder and the folder is empty..
Click to expand...
Click to collapse
@Kill-Switch can maybe explain us how to change it correctly on the note 3 with the right commands
MarkusOSx said:
@Kill-Switch can maybe explain us how to change it correctly on the note 3 with the right commands
Click to expand...
Click to collapse
agree mate..hope he help
Just an opinion, but for those who like the hassles, can just grab the latest stock Note 3 firmware on sammobile and flash it using Odin. I did that and saw the Powered by Android text when I rebooted my phone. Its a good thing to update your bootloader and baseband as well, but if you like the simple way then go ahead with this one.
P.S Nice guide by the way
This didn't work for me though. I tried installing both new and old, untick auto-reboot, retick auto-reboot, all the tricks in the book, restarted the phone, after each method, no Powered by Android
Sent from my SM-N930F using Tapatalk
mdfpido said:
This didn't work for me though. I tried installing both new and old, untick auto-reboot, retick auto-reboot, all the tricks in the book, restarted the phone, after each method, no Powered by Android
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
reseat the battery then flash via odin
Few weeks ago i got a LG G7 “UNLOCKED” on ebay, the phone had a sticker where it said model “LGG710PM”, the bad news i was stuck with a FIRMWARE LM-G710ULM (V10b-LAO-COM) MAY 2018. I tried updating the phone via OTA or LGBridge and i had no luck. So i looked online for the correct KDZ file for the LGG710PM and also no luck, So what i did is look for a G710ULM KDZ, but the only one the i could find was the G710ULM10G_00 (https://www.mylgphones.com/lg-g7-thinq-project-fi-stock-firmware-g710ulm10g.html) . So after searching online and watching some videos on youtube if this could work, i found a youtuber video (MAXLEE) he change a FIRMWARE of sprint to a Canadian FIRMWARE and it work he did it on a LG G6. So what i did is try it on MY G7 model LGG710PM“ the only thing is that on the G7 there's a few more steps to do:
1) Download G710ULM10G_00 KDZ file
https://www.mylgphones.com/lg-g7-thinq-project-fi-stock-firmware-g710ulm10g.html
2) Download LGUP and install (make sure to use this link for download and follow instructions, like this you don't get an error when
you insert the KDZ file and hit START).
https://mega.nz/#!kCpHBaia!xZmico6MYL1T07ffuc8z6cCbs5oU4pKEz5VG-AwfvV0
A) Make sure you don't have LGBrige installed, if so UNINSTALL and delete any folder of LGBridge after you have uninstalled
(C:\Program Files (x86)\LG Electronics)
B) Download the LGUP zip file and unzip, if you don't have the drivers install lgdrives(The file is inside the folder LGUP-LG G7 ThinQ).
After that install “LGUP_Install_Ver_1_14_3 (1).msi “ file.
{
"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"
}
C) After installing LGUP you must go to C:\Program Files (x86)\LG Electronics\LGUP and copy the first three files(CODEFIRE, LOG,
model) from the UNZIPED FILE from step B.
D) Go to file “model” (C:\Program Files (x86)\LG Electronics\LGUP\model) then go to file “common”....go to step “E” don't close the
window….
E) Go to the UNZIP FOLDER, go to file WindowsLGFirmwareExtract-1.2.6.1-Release. Run “WindowsLGFirmwareExtract.exe” and select
the KDZ file you downloaded, then make sure you
check on “LGUPc.dll. EXTRACT KDZ.
F) A file “LGUPc.dll” will be created, Copy that file into the folder “common”...... you should had left that window open from step “D”. Rename the actual “LGUP_Common.dll” to
“LGUP_CommonDDD.dll” and “LGUPc.dll” to “LGUP_Common.dll” and then deltate the “LGUP_CommonDDD.dll”.
Open LGUP...put your phone in download mode... select the KDZ file you downloaded from step “1” and in PROCESS select REFURBISH…. Then click START.
Thanks for posting the guide but I don't see any links to download the files on step 2
hytl said:
Thanks for posting the guide but I don't see any links to download the files on step 2
Click to expand...
Click to collapse
True, already put the link, thanks.
Radha09 said:
True, already put the link, thanks.
Click to expand...
Click to collapse
Thank you. I wonder after we upgrade to this firmware, will we be able to get OTA update?
hytl said:
Thank you. I wonder after we upgrade to this firmware, will we be able to get OTA update?
Click to expand...
Click to collapse
i hope so....
I got SPC Code does not match error.
hytl said:
I got SPC Code does not match error.
Click to expand...
Click to collapse
Where did you get that error?
After I click start in LGUP
hytl said:
After I click start in LGUP
Click to expand...
Click to collapse
Did you see the video from Victor Hernandez i know its in Spanish but just to make sure you made the steps.... and one more thing i forgot to mention is that before putting start you need to have you phone in download mode here's a link ....... https://www.youtube.com/watch?v=EkKfPPBzJ1c
Radha09 said:
Where did you get that error?
Click to expand...
Click to collapse
Radha09 said:
Did you see the video from Victor Hernandez i know its in Spanish but just to make sure you made the steps.... and one more thing i forgot to mention is that before putting start you need to have you phone in download mode here's a link ....... https://www.youtube.com/watch?v=EkKfPPBzJ1c
Click to expand...
Click to collapse
Thanks. It's flashing now. I didn't put the phone into download mode.
hytl said:
Thanks. It's flashing now. I didn't put the phone into download mode.
Click to expand...
Click to collapse
:good:
hytl said:
Thanks. It's flashing now. I didn't put the phone into download mode.
Click to expand...
Click to collapse
Cool, sorry that i forgot to mention that step.....hope it works for you too.
Could you please post screenshot of your phone software info? Is your SN under Hardware info blank?
hytl said:
Could you please post screenshot of your phone software info? Is your SN under Hardware info blank?
Click to expand...
Click to collapse
SN under Hardware is BLANK that has always been that way.... cant fix that.
I just checked with LGBridge. It still says "Cannot check software version. Please try again". I don't think we will be able to do OTA update in the future.
hytl said:
I just checked with LGBridge. It still says "Cannot check software version. Please try again". I don't think we will be able to do OTA update in the future.
Click to expand...
Click to collapse
Yeah, i think its because the firmware is from another hardware and not the sprint.... at least we are not stuck on MAY......
Radha09 said:
Where did you get that error?
Click to expand...
Click to collapse
Radha09 said:
Yeah, i think its because the firmware is from another hardware and not the sprint.... at least we are not stuck on MAY......
Click to expand...
Click to collapse
Yeah. I'm glad that we aren't stuck on May patch anymore. I don't remember but I don't think I had wifi calling before I flash this. Now I got wifi calling, so great. Thanks for the great guide.
Great! So is safe to flash then . Besides S/N still blank, any other side effect after flash? I assume storage 64gb still same, imie # still same, phone still unlocked, lte signal better? Good to see wifi calling is enabled.
Sent from my LM-G710 using Tapatalk
jonahy said:
Great! So is safe to flash then . Besides S/N still blank, any other side effect after flash? I assume storage 64gb still same, imie # still same, phone still unlocked, lte signal better? Good to see wifi calling is enabled.
Click to expand...
Click to collapse
Yes I guess it's safe it worked for me and also for member hytl. Everything is working fine, the phone is still unlocked, and everything else is the same nothing changes. You get battery improvement and camera. LTE signal it's the same for me.
Thanks Im gonna try later.. Do I need to do factory rest before flash and after?