[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
Related
Okay guys - I've created a Heimdall only version of Gingerbread/KF1 for those who want to use Heimdall.
THIS WILL GIVE YOU ROOT!!!
[Edit] This is the ODEXED version. If you are looking for the DEODEXED version, I will be posting another thread regarding that one.
A few things before I begin.
Many thanks to dsexton702, DrHonk, Krylon360, penguin0609, whitehawkx, and others for their work. If I missed your names, it's not on purpose, I just have a bad memory.
This requires Heimdall. A link to Heimdall for Windows is here:
http://www.mediafire.com/file/az3ia99by9rgcdf/heimdall-suite-1.1.1-win32.zip
This is a Heimdall ONLY solution. You only need to unrar the link attached (yes, I use RAR. Sorry - but it's an all in one solution that allows me to manipulate RAR, ZIP, and TAR files.) into a directory. Get WinRAR (from rarlabs) to undo the file.
When unRAR'ing it, you will see 8 files and a folder. The folder contains the zimage_patch that is required to root the SGS4G.
This is a modification of what dsexton702 did. Steps are as follows:
1) Download the Heimdall suite file here:
http://www.mediafire.com/file/az3ia99by9rgcdf/heimdall-suite-1.1.1-win32.zip
Install Heimdall, including the drivers. Read the instructions included.
If you have Heimdall 1.1.1 installed already, skip step 1 and go to step 2
2) Download the ROM file here:
http://www.mediafire.com/?d920rdcm2mt20ie
3) Unzip the ROM file to a directory.
4) Open Heimdall
5) Match the filename to the PDA/Code location. In other words:
FactoryFS = factoryfs.rfs
Kernel = zimage
Param.lfs = param.lfs
Primary Bootloader = boot.bin
Secondary Bootloader = sbl.bin
cache = cache.rfs
Database = data.rfs
Modem = modem.bin
6) Put your SGS4G into download mode. Click Start. Wait until the green bar goes all the way across and it's done.
7) Reboot to Download mode again
8) Close and re-open Heimdall. Click and browse zImage to the directory "zimage_patch". Choose the zImage file there. Click Start.
9) Let the SGS4G go through the Fugu bootloop a couple of times. This is where your SGS4G gets Rooted.
10) Reboot to download mode once more
11) Close and re-open Heimdall. Click and browse the ORIGINAL zImage (NOT THE ZIMAGE_PATCH VERSION!!). Click start.
12) Let the unit flash, then reboot. Download busybox to verify Root.
I've done this a few times with my SGS4G. It works for mine, but I need a couple of guinea pigs to verify it.
Let me know!
sgyee said:
Okay guys - I've created a Heimdall only version of Gingerbread/KF1 for those who want to use Heimdall.
A few things before I begin.
Many thanks to dsexton702, DrHonk, Krylon360, penguin0609, whitehawkx, and others for their work. If I missed your names, it's not on purpose, I just have a bad memory.
This requires Heimdall. A link to Heimdall for Windows is here:
http://www.mediafire.com/file/az3ia99by9rgcdf/heimdall-suite-1.1.1-win32.zip
This is a Heimdall ONLY solution. You only need to unrar the link attached (yes, I use RAR. Sorry - but it's an all in one solution that allows me to manipulate RAR, ZIP, and TAR files.) into a directory. Get WinRAR (from rarlabs) to undo the file.
When unRAR'ing it, you will see 8 files and a folder. The folder contains the zimage_patch that is required to root the SGS4G.
This is a modification of what dsexton702 did. Steps are as follows:
1) Download the Heimdall suite file here:
http://www.mediafire.com/file/az3ia99by9rgcdf/heimdall-suite-1.1.1-win32.zip
Install Heimdall, including the drivers. Read the instructions included.
If you have Heimdall 1.1.1 installed already, skip step 1 and go to step 2
2) Download the ROM file here:
http://www.mediafire.com/?d920rdcm2mt20ie
3) Unzip the ROM file to a directory.
4) Open Heimdall
5) Match the filename to the PDA/Code location. In other words:
FactoryFS = factoryfs.rfs
Kernel = zimage
Param.lfs = param.lfs
Primary Bootloader = boot.bin
Secondary Bootloader = sbl.bin
cache = cache.rfs
Database = data.rfs
Modem = modem.bin
6) Put your SGS4G into download mode. Click Start. Wait until the green bar goes all the way across and it's done.
7) Reboot to Download mode again
8) Close and re-open Heimdall. Click and browse zImage to the directory "zimage_patch". Choose the zImage file there. Click Start.
9) Let the SGS4G go through the Fugu bootloop a couple of times.
10) Reboot to download mode once more
11) Close and re-open Heimdall. Click and browse the ORIGINAL zImage (NOT THE ZIMAGE_PATCH VERSION!!). Click start.
12) Let the unit flash, then reboot. Download busybox to verify Root.
I've done this a few times with my SGS4G. It works for mine, but I need a couple of guinea pigs to verify it.
Let me know!
Click to expand...
Click to collapse
good stuff sgyee it works great
A picture of the first file upload. Directories will be different from yours, but you should get the idea (if my post doesn't make sense) of where which file goes.
{
"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"
}
Plain KF1 gingerbread correct? No root or deodex implemented?
Figured it would be stated but just double checking.
Thanks as well!
heartspains88 said:
Plain KF1 gingerbread correct? No root or deodex implemented?
Figured it would be stated but just double checking.
Thanks as well!
Click to expand...
Click to collapse
Oops. I forgot to mention Root.
This will give you root. No deodex. Haven't gotten there yet nor will I have a chance to even try - I have a family reunion and other events this weekend, so I wanted to get the Heimdall only version out there.
I'll update the original post.
Never used Heimdall yet.
Will this do a data wipe of my device or will I retain all of my programs and program data if I do this?
This will wipe everything. If you use Titanium Backup, you will be able to do an app restore.
works great with no problems also root checker verify
what if u have cwm recovery from before does that stay too? plz and ty
dohandrew said:
what if u have cwm recovery from before does that stay too? plz and ty
Click to expand...
Click to collapse
Cwm will disappear. Krylon360 is working on that.
Sent from my HTC HD2 using Tapatalk
Can't get back to download mode
I went to install the Zimage patch, but now I am unable to get back into download mode, so I can't install it. Am I missing a step or something?
youngarty85 said:
I went to install the Zimage patch, but now I am unable to get back into download mode, so I can't install it. Am I missing a step or something?
Click to expand...
Click to collapse
Nope. You MAY have to do the alternate download mode "method", which involves volume down, home, power, then insert battery.
Sent from my HTC HD2 using Tapatalk
Thanks. I did the steps above, but now, it just goes to the bootscreen and goes back to charging the phone. Very frustrating.
Nevermind. I tried it again and I'm good! Thanks!!
Netflix
If this helps any guys, The Netflix app is OFFICIALLY working with this rom!!!!!!! Spread the word!
OT, but I cant get the netflix app to work. It installs, but says streaming is not available on my device. Is it still working? What version are you using? Do you have a link?
This rom works great. Lots of issues - particularly videos - with the deodexed version. THANK YOU!
Blade
Hey I followed all the steps above but I am stuck in the fugumod reboot thing..unless its supposed to be rebooting 40+ times
After Fugu mod bootloop, you reflash the original zImage back.
yea i figured it out...i was just having a hard time getting in to download mode again for some reason...worked perfectly!
Thx very much
This Rom has fix the null/null Imei problem and can't catch the signal that always happen to me.
Sorry if the question isnt clear, here is my delemma
So My N5 I had deleted the system partition (or folder) and I no longer had a rom, now my problem is that I cannot get a new rom installed.
I have TWRP as my recovery but no roms.
I also cant do adb sideboot, It always says: Error: Device not found
What Can I do about this?
Does adb Sideboot need usb debugging enabled?
Thanks!
Sounds like you may have to install the drivers for adb on your computer
Sent from my Nexus 5 using XDA Premium 4 mobile app
kevkid said:
Sorry if the question isnt clear, here is my delemma
So My N5 I had deleted the system partition (or folder) and I no longer had a rom, now my problem is that I cannot get a new rom installed.
I have TWRP as my recovery but no roms.
I also cant do adb sideboot, It always says: Error: Device not found
What Can I do about this?
Does adb Sideboot need usb debugging enabled?
Thanks!
Click to expand...
Click to collapse
Why not just flash the factory images from fastboot?
So I tried to using this: http://forum.xda-developers.com/showthread.php?t=2509428 one of mthe multi tools, and it seems to go through and it stays boot looping in the boot animation.
hrmm.... very weird
EDIT: Ok I was able to flash stock via the direct google link, Now a question about adb sideload, How does that function? Do I have to have usb debugging enabled?
kevkid said:
So I tried to using this: http://forum.xda-developers.com/showthread.php?t=2509428 one of mthe multi tools, and it seems to go through and it stays boot looping in the boot animation.
hrmm.... very weird
Click to expand...
Click to collapse
1. Go here: https://developers.google.com/android/nexus/images
2. Download the Nexus 5 Android 4.4 (KRT16M) image.
3. Unzip.
4. Run the .bat file while in fastboot.
That's it. It's going to wipe everything but atleast it will work.
bahnburner said:
1. Go here: https://developers.google.com/android/nexus/images
2. Download the Nexus 5 Android 4.4 (KRT16M) image.
3. Unzip.
4. Run the .bat file while in fastboot.
That's it. It's going to wipe everything but atleast it will work.
Click to expand...
Click to collapse
Thanks worked!!
bahnburner said:
1. Go here: https://developers.google.com/android/nexus/images
2. Download the Nexus 5 Android 4.4 (KRT16M) image.
3. Unzip.
4. Run the .bat file while in fastboot.
That's it. It's going to wipe everything but atleast it will work.
Click to expand...
Click to collapse
Having a little trouble I was hoping you could help clarify how to run the .bat file while in fastboot. I tried to flash the image and I am still stuck on a bootloop. Thanks
capathy21 said:
Having a little trouble I was hoping you could help clarify how to run the .bat file while in fastboot. I tried to flash the image and I am still stuck on a bootloop. Thanks
Click to expand...
Click to collapse
Open a new command prompt, drag and drop the bat file into the terminal window, press enter.
bahnburner said:
Open a new command prompt, drag and drop the bat file into the terminal window, press enter.
Click to expand...
Click to collapse
I am having trouble with what the bat file is. When I unzip the download I have
bootloader-hammerhead-HHZ11d(disc image file).
flash-all(windows batch file)
flash-all.sh(SH File)
flash-base.sh(SH File)
image-hammerhead-krt16m(WinRar zip archive)
radio-hammerhead-M8974A-1.0.25.0.17(Disc Image File)
I am not seeing anything that says .bat file.
Sorry for being so ignorant on this.
capathy21 said:
I am having trouble with what the bat file is. When I unzip the download I have
bootloader-hammerhead-HHZ11d(disc image file).
flash-all(windows batch file)
flash-all.sh(SH File)
flash-base.sh(SH File)
image-hammerhead-krt16m(WinRar zip archive)
radio-hammerhead-M8974A-1.0.25.0.17(Disc Image File)
I am not seeing anything that says .bat file.
Sorry for being so ignorant on this.
Click to expand...
Click to collapse
Windows batch file = .bat file. If you're going to screw with your phone, at the very least you should probably make sure explorer shows all file extensions...
{
"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"
}
bahnburner said:
Windows batch file = .bat file. If you're going to screw with your phone, at the very least you should probably make sure explorer shows all file extensions...
Click to expand...
Click to collapse
Thanks for the help! Sorry to annoy. I've been rooting and such for several years but was just a bit lost.
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....
Hi
I created root method for the last version of samsung J2 Prime G532G - G532GDXU1APL1.
It based on modified stock recovery with custom keys (mine), which allow to install a special zip that signed with those keys.
This method include's a patched boot.img (sepolicy), in order the root work properly. (this is normal system root - not systemless, and from Android 6.0 or samsung 5.1.1 and above need also pathed boot)
The phone must be with G532GDXU1APL1 version, or it wont work.
It can be downloaded from here
G532GDXU1APL1
Instructions:
Download this file, and extract it to some folder.
G532GDXU1APL1_root_by_avicohh
Open odin and flash the .tar file inside the folder (In AP).
This file contains the custom recovery, a patched boot, and an empty cache.img in order the phone will restart to recovery after flashing.
In recovery choose "Apply update from ADB".
Run the .bat script file from the "SuperSU sideload installer" folder.
Wait until it finish, the phone will restart automatically with SuperSU inside.
Good luck!
Credits:
@Chainfire for SuperSU
@osm0sis for AIK
P.S. (for devs)
This method can be modified to another build / device, by patching the sepolicy inside boot.img (see here), and replacing the res / keys file inside the recovery.img with my keys. (Attached)
You can unpack and repack boot and recovery images with this tool. (It recomanded to this on linux in order to keep the files permissions)
The stock recovery doesn't support the standart SuperSU installer bacause it bash script, so i wrote another one in Edify. (this zip should work on any device with android 5.11 - 6.0.1 and armv7)
I am waiting new method root for G532G (G532GDXU1APL1)
Now..
great work ,,thanks bro .......I 'm so happy .....
Manual instruction recovery_custom_keys.7z ??? thank
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
avicohh said:
Hi
I created root method for the last version of samsung J2 Prime G532G - G532GDXU1APL1.
It based on modified stock recovery with custom keys (mine), which allow to install a special zip that signed with those keys.
This method include's a patched boot.img (sepolicy), in order the root work properly. (this is normal system root - not systemless, and from Android 6.0 or samsung 5.1.1 and above need also pathed boot)
The phone must be with G532GDXU1APL1 version, or it wont work.
It can be downloaded from here
G532GDXU1APL1
Instructions:
Download this file, and extract it to some folder.
G532GDXU1APL1_root_by_avicohh
Open odin and flash the .tar file inside the folder (In AP).
This file contains the custom recovery, a patched boot, and an empty cache.img in order the phone will restart to recovery after flashing.
In recovery choose "Apply update from ADB".
Run the .bat script file from the "SuperSU sideload installer" folder.
Wait until it finish, the phone will restart automatically with SuperSU inside.
Good luck!
Credits:
@Chainfire for SuperSU
@osm0sis for AIK
P.S. (for devs)
This method can be modified to another build / device, by patching the sepolicy inside boot.img (see here), and replacing the res / keys file inside the recovery.img with my keys. (Attached)
You can unpack and repack boot and recovery images with this tool. (It recomanded to this on linux in order to keep the files permissions)
The stock recovery doesn't support the standart SuperSU installer bacause it bash script, so i wrote another one in Edify. (this zip should work on any device with android 5.11 - 6.0.1 and armv7)
Click to expand...
Click to collapse
recovery_custom_keys.7z hướng dẫn tay ??? cảm tạ
I don't understand, what instructions?
ask something
this root files include custom recovery?
Yes, but no TWRP. Modified stock recovery.
not only G532GDXU1APL1
Not only G532GDXU1APL1 is working but also G532GDXU1AQA4 is rooted smoothly i have tested on my device. So thanks a lot.:fingers-crossed:
Brother. Can you explain to me ste by step to root sm-g532g on aq4 firmware? Please
:fingers-crossed:
bolda.mia said:
Not only G532GDXU1APL1 is working but also G532GDXU1AQA4 is rooted smoothly i have tested on my device. So thanks a lot.:fingers-crossed:
Click to expand...
Click to collapse
Just do the instruction in the first post.
Hei avicoh
avicohh said:
just do the instruction in the first post.
Click to expand...
Click to collapse
sometimes i have an error when daemon start in cmd, maybe my pc's problem? I used win7 64 bit
Upload log
Log is here
avicohh said:
Upload log
Click to expand...
Click to collapse
{
"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"
}
HELP ME
I ALSO USE STOCK FIRMWARE THAT U GIVE ABOVE G532GDXU1APL1 ,
sometimes there is a messege in CMD that saying ADB out of date :/
I believe it something in your computer.
Try another one.
avicohh said:
Upload log
Click to expand...
Click to collapse
avicohh said:
I believe it something in your computer.
Try another one.
Click to expand...
Click to collapse
another one??????
alfanjawa8 said:
I ALSO USE STOCK FIRMWARE THAT U GIVE ABOVE G532GDXU1APL1 ,
sometimes there is a messege in CMD that saying ADB out of date :/
Click to expand...
Click to collapse
@avicohh WHY SUPERUSER CANNOT BE READ?
Try with another computer.
I my god it is now ask for password, and i have no z2x box to unlock it :/
So maybe @bolda.mia is wrong.
The reason the device ask for password is because the custom boot is based on G532GDXU1APL1 and you have a newer system version. (I think is something related to storage encryption, I don't know exactly)
That's why I said this method should work only on G532GDXU1APL1.
Anyway, flash the stock version back. I believe it will fix the problem even without wipe.
before root, I already flash to lower version brother
avicohh said:
so maybe @bolda.mia is wrong.
The reason the device ask for password is because the custom boot is based on g532gdxu1apl1 and you have a newer system version. (i think is something related to storage encryption, i don't know exactly)
that's why i said this method should work only on g532gdxu1apl1.
Anyway, flash the stock version back. I believe it will fix the problem even without wipe.
Click to expand...
Click to collapse
i know exactly, that i already flashing with the lower rom such as pl1 pk3 etc. And the result is same, ask for password my brother!
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