Pre Rooted Stock ROM
Here is complete stock Pre rooted ROM
( MUST READ THIS before flashing DMF2/ME6 or any newer )
July13
N7100XXDMG1_N7100ODDDMG1_N7100DDDMG1- Deodexed - India - Download - Detail here
N7100XXDMG1_N7100ODDDMG1_N7100DDDMG1- Odexed - India - Download
June13
N7100XXDMF2_N7100OLBDMD2_XME - Malaysia - Download - - - Mirror
SuperSu updated to latest 1.34
Package have addition mod zip file which is optional, If you want to install that mod, instead using packed one use this
April 2013
N7100XXDMC3_N7100ODDDMD1_N7100DDDLK6 (INU) -India - Download
March 2013
N7100XXDMC3_N7100OXXDMC2_N7100XXDLK7 (XEO) - Poland - Download
Installation Instruction
- Download ROM and extract to ***.tar.md5 (unzip tool)
- Make sure you have installed Kies OR Samsung USB driver
- Open up the S/W Installation Program by executing the Odin3 v3.04.exe
1. Enable the check mark by click on the following options(default Option)
- Auto Reboot, and F. Reset Time
- Check PDA, and point to ROM file you have extracted
{
"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"
}
File name shown in above image is for demo purpose, you have to select according ROM you have download
2. Now switch off device and Enter into Download Mode
- Enter into Download Mode by pressing Volume Down button, Home Key and
Power Button simultaneously. And then, press Volume UP button in Warning Page to enter the Download Mode.
3. Connect the device to PC via Data Cable.
Make sure that the one of communication port [ID:COM] box is highlighted in
light blue. The device is now connected with the PC and ready to download the
binary file into the device.
4. Start downloading binary file into the device by clicking Start Button on the screen.
the green colored "PASS!" sign will appear on the upper-left box if the binary file has been successfully downloaded into the device.
5. Disconnect the device from the Data cable.
6. Once the device boots up, you can check the version of the binary file or name
by pressing the following code in sequence;
*#1234#
After flashing your device will have SuperSU in application drawer. If you want to unroot it, open SuperSu - settings - Full unroot.
First thing I do recommend after rooting device is
EFS Backup
Why so?
EFS folder contains some important and some basic info related to our device identity like Wi-Fi address, Bluetooth MAC address and the very main IMEI address (nv_data.bin).
Now if this EFS partition accidently corrupted then your phone’s IMEI no. will erased and you can not make voice call further. This kind of damage is often not accepted by the service center of your respected handset’s company.
Here your backup can only be savior for you.
-This is pure samsung stock ROM as it is + Root
-Non wipe
-Won't raise flash counter.
- Non Hotfile link
Again to make it clear, there is no any additional changes except pushing superSU (busybox added to April 2013 and onward), so there won't be have any difference from stock ROM, but you will not need to Root / reset counter. Just note that, flashing prerooted ROM doesn't reset counter, If your flash counter already raised flashing this ROM doesn't reset it, but you can use triangle away to reset counter after flashing this ROM. later you can uninstall triangle away.
Rooting is not difficult but still many users scare from it, this will come handy to them.
There is no plan to make every release Pre rooted, when there will be major update and myself update device that time will make that ROM pre rooted.
There is already thread in dev section by as i9000, which also have deodexed version and many other ROMs with multi CSC and regularly updating too. This thread will update only ROMs which i am using, as well basic aim is to write tutorial abiut how to make pre rooted ROM.
There are two other MB6 and DMB2 India are ready but really finding difficulty to upload. still i will try my best to upload it.
- Password to unzip - when there is any password to unzip, file name itself will have it.
- difference in file size from sammobile stock rom size is just due to different compression method, once you extract it will be same.
How to make prerooted stock ROM.
Requirements :
Ubuntu and login as Root user.
Ext4_utils - extract to home directory
Root files (su and Superuser.apk) - copy to home directory
busybox - copy to home directory (optional)
Procedure :
1.Download ROM you need to preroot and rename stock.tar.md5 (just to make command line input easy)
2.Extract ROM
Code:
tar xvf stock.tar.md5
3.convert system.img to ext4 so we can mount it.
Code:
./simg2img system.img newsys.img
4.delete system.img
Code:
rm -f system.img
5.Create temp folder and mount it
Code:
mkdir temp
mount -o loop newsys.img temp
6.Push root and busybox file to system and change permission
Code:
cp su temp/xbin/su
chmod 06755 temp/xbin/su
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
Code:
cp busybox temp/xbin/busybox
chmod 04755 temp/xbin/busybox
7.Conver newsys img to samsung system.img format
Code:
./mkuserimg.sh -s temp system.img ext4 tempdir 2048M
8.unmount and delete temp folder
Code:
umount temp
rmdir temp
9.create odin flashable tar file (here file names depends on files you have got by extracting ROM)
Code:
tar cvf prerooted.tar boot.img cache.img hidden.img modem.bin recovery.img sboot.bin system.img tz.img
10. add md5 checksum
Code:
md5sum -t prerooted.tar >> prerooted.tar
mv prerooted.tar prerooted.tar.md5
Now Flash prerooted.tar.md5 with odin.
Delete following files from home directory to make it clean
stock.tar.md5
newsys.img
and all files extracted while unpacking tar in step 1.
Credits :
Chainfire for his SuperSu
Phil3759
Credits to following user for referring their works on different forum
jazzor, rizdroid, das7982, faria
Where is it sir?
Sent from my GT-N7100 using xda premium
As I have said
What's your opinion?
Do I update rom
Or
You want guide, how to make it yourself.
Sent from my GT-N7100 using xda premium
My choice is 2
Please provide complete guide
Sent from my GT-N7100 using Tapatalk 2
Make a guide. That way, people learn more.
Sent from my GT-N7100 using xda premium
i thought it was just about placing su in xbin and supersu.apk in app -.-
yeah unpacking repacking and all can be a damn headache
No offense, leave the dev part to those who deserve this denomination and stick with the Guide Guru image that you have built for yourself and for which you get lots of credits and praise. I'd choose option 2.
Thanks for your excellent work of guiding noobs like me and troubleshoot their problems.
P_
))))))
That's the same there! And for a long time!
http://forum.xda-developers.com/showpost.php?p=32260125&postcount=1
:laugh:
2 with noobie detailed please
Sent from my GT-N7100 using xda app-developers app
UBUNTU needed for this)
alexyuh said:
UBUNTU needed for this)
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using xda app-developers app
alexyuh said:
UBUNTU needed for this)
Click to expand...
Click to collapse
Not with cygwin.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Not with cygwin.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
There are some limitations in cygwin. Ubuntu is best for this.
Sent from my GT-N7100 using xda premium
Please post guide so that we'd learn ourselves
Sent from my GT-N7100 using xda premium
---------- Post added at 09:22 PM ---------- Previous post was at 09:15 PM ----------
sharjackmission said:
2 with noobie detailed please
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using xda premium
Ok,
So will make complete Guide with link to all needed utilities. But may take some time.
Meanwhile try to upload pre rooted rom too, and will add link in op. (I have made two roms mb6 and mc3)
But really difficult to upload every rom, or to make specific on request.
Whenever there is major update and if I will update my device, that time will make that rom pre rooted.
Thanks for patience.
Sent from my GT-N7100 using xda premium
dr.ketan said:
Ok,
So will make complete Guide with link to all needed utilities. But may take some time.
Meanwhile try to upload pre rooted rom too, and will add link in op. (I have made two roms mb6 and mc3)
But really difficult to upload every rom, or to make specific on request.
Whenever there is major update and if I will update my device, that time will make that rom pre rooted.
Thanks for patience.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I can help
How?
Sent from my GT-N7100 using xda premium
Option 1
madhuranand007 said:
Option 1
Click to expand...
Click to collapse
Sure
Within 5 min updating OP
dr.ketan said:
How?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Advice to you ladies
http://forum.xda-developers.com/showthread.php?p=39848357#post39848357
http://forum.xda-developers.com/showthread.php?p=39286842#post39286842
You have incorrectly assembled system img.The composition of the image.
No busybox.No su in bin)))
resolution:
Code:
cd app
chmod 0644 Superuser.apk
My version:
https://hotfile.com/dl/202764580/bcb9aa2/system.img.zip.html
Related
hello.i open this thread to show you how to solve a2sd not working on custom roms so you people can use your favorite rom with all the features and rom developers can continue developing of their rom and make them more and more better.
First of all the reason why a2sd dont work and ext partition doesnt mount:
for these feautures and others that dev gives as with his rom,the kernel ramdisk is modified (by xda kitchen or "by hand").so if this boot.img is not flashed into your phone,those feautures wont work.every custom rom have her boot.img into the flashable rom.zip.the thing that our rom creators and devs dont know(cause all phones are not the same) is that the boot.img in the zip doesn flash!.our phone cant flash boot.img from recovery and the reason is because in this phone kernel and recovery are in the same partition and not separately partition like most phones.
The solution:
REMEMBER THAT YOU DO IT WITH YOUR OWN RISK!
its just very simple:the only thing you have to do is to flash the boot.img that comes with your rom and the only way to do that succesfull is with Odin.(this ofcourse will give the custom bin counter 1 up because its a modified and not stock kernel).also have in mind that you have to flash it once.if for any reason you want to reflash your rom,you just do wipe data etc and reflashing the rom.zip.its not necesary to reflash the kernel(boot.img) again.its still there and will only change if you flash another boot.img or stock firmware with Odin.
So i will give two options.
1.download my PDA_S5360_kernel.tar from TermaRomGR threadhttp://forum.xda-developers.com/showthread.php?t=1520167(the mods in all of these kernel are about the same).flash it with Odin in pda field (first try without wipe anything or reflashing stock firmware first.just boot in download mode,flash with odin and reboot,it should work ok.DONT FORGET TO BACKUP YOUR ROM FIRST!JUST IN CASE!).reboot may take more time dont worry.when phone is on your ext partition should be mounted.you can try with terminal simulator:
su
a2sd check
if everything is ok you can remove your dalvik cache to your sd if you want for more internal memory free space:
su
a2sd cachesd
the phone will reboot.it will late to reopen just be patient and then your internal memory will be almost empty.but have in mind that this partition is not as fast asthe internal memory so some apps or games maybe slow a bit.
2.the other option is to flash the kernel(boot.img) that come with your custom rom.how to do that (thanks to Doky):
copy the boot.img that is inside the zip of the rom you are using.
download my PDA_S5360_kernel.tar
find in web the program total commander for windows
open t commander and in left window navigate to my PDA_S5360_kernel.tar file and get into it.in the right window find the boot.img of your rom.drag it and drop it to the left window so it replace the boot.img into the .tar file with yours.its ready.just flash it with Odin.
Some important things too that i notice from my experiments:
with busybox 1.18 your rom will not boot after nove dalvik cache to sd
it will work nice with 1.17 but its not suitable for people who want to run v6 script.for those who want to run v6 you must download busybox instaler from market and install v1.19.2.if after that you have problems with wifi try another version (1.19.3 or 1.19.4).and report back what works ok and what not so all people together can find the best setup.
Please tell to the devs of your roms to read this thread so they learn about the solution to this problem so they can create even better and better roms
I love you. I'll try this tomorrow.
Sent from my GT-S5360 using xda premium
Why do i have SD Card Remove Problem then when i boot back i was in the Welcome Screen where my info of google account is being ask. I skipped it then check the settings, my account was just there still. Also having this Turning off by itself problems. This was just started when i begin using a2sd supported ROMS. But when i'm just on stock or non-a2sd roms it work fine. Maybe its the boot.img?
eyjay1991 said:
Why do i have SD Card Remove Problem then when i boot back i was in the Welcome Screen where my info of google account is being ask. I skipped it then check the settings, my account was just there still. Also having this Turning off by itself problems. This was just started when i begin using a2sd supported ROMS. But when i'm just on stock or non-a2sd roms it work fine. Maybe its the boot.img?
Click to expand...
Click to collapse
which boot.img you instal?mine?i dont think that this is the problem.for me and for others works ok.try wipe cache and if the same try wipe data/reset.
Thank you for the info bro!
Sent from my GT-S5360 using xda premium
bumslayer said:
I am interested to know what is so special about your boot.img and how you customized it. I am guessing you decompiled a stock boot.img to come up with your own
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
with xda kitchen.it doesnt has something xterme only a2sd, init.d support and ext mount on boot.
So this will happen?
before flashing ur 5360kernel.tar
{
"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"
}
after flashing
is this correct?
ronnieryan said:
So this will happen?
before flashing ur 5360kernel.tar
after flashing
View attachment 926853
is this correct?
Click to expand...
Click to collapse
yes its succesfuly flashed and should working right
termagazis said:
with xda kitchen.it doesnt has something xterme only a2sd, init.d support and ext mount on boot.
Click to expand...
Click to collapse
Oh, so I can take a stock firmware from Doky73's thread and modify it thru xda kitchen and change the kernel to include just init.d support (I kind of hate a2sd at the moment)? What about ext4 file system support? Is this possible?
By xda kitchen you mean the one by dsixda, right?
just like to ask if a2sd's low memory setting would conflict with [email protected] scripts?
coz after installing a2sd in my phone with [email protected] script, i sometimes notice that memory usage would reach 240+?
bumslayer said:
Oh, so I can take a stock firmware from Doky73's thread and modify it thru xda kitchen and change the kernel to include just init.d support (I kind of hate a2sd at the moment)? What about ext4 file system support? Is this possible?
By xda kitchen you mean the one by dsixda, right?
Click to expand...
Click to collapse
dont know.just try it if you want.for ext4 suport we need a custom kernel that will suport that
ronnieryan said:
just like to ask if a2sd's low memory setting would conflict with [email protected] scripts?
coz after installing a2sd in my phone with [email protected] script, i sometimes notice that memory usage would reach 240+?
Click to expand...
Click to collapse
maybe they conflict.use one of them
I'm using hybrid2.1 ,
Qus 1: is it necessary to partition SD card if I wanna enable a2SD? If yes then when&how?
Qus 2: is the1St option stated above mint to flash only the tar file by Odin and other fields of Odin remain empty?
And please give a link to download Odin & a link for step by step tutorial on connecting to Odin(with phone preparation ).
Sent from my GT-S5360
a.m.muammar said:
I'm using hybrid2.1 ,
Qus 1: is it necessary to partition SD card if I wanna enable a2SD? If yes then when&how?
Qus 2: is the1St option stated above mint to flash only the tar file by Odin and other fields of Odin remain empty?
And please give a link to download Odin & a link for step by step tutorial on connecting to Odin(with phone preparation ).
Sent from my GT-S5360
Click to expand...
Click to collapse
1.yes its necesary to have an ext2 or ext3 partition.you can create it with skin1980 CWM recovery in advance/partition sdcard.a partition 500Mb is enough.(before do it backup everything from your sdcard to your pc because this procedure will erase everything in your sdcard.)
2.for Odin google it Odin3-v1.85.Here is how to do it:
1. you put my tar in pda field and the other remain empty(check only "Auto reboot" and "F.reset time")
2. Now turn off your Samsung Galaxy Y (just for make sure is completely off, remove the battery for a few sec and put that back)
3. Press Volume[-] + Home + Power to boot in Download Mode
4. Hold the buttons until a warning screen with choise show up.
5. Select Continue (Volume[+]), then it`s go to download mode
6. Connect the cellphone (via USB cable) to PC, wait until ODIN detect the device.
7. Click Start
8. Wait until ODIN give feedback respon PASS
it`s mean the flashing proccess is complete. Samsung Galaxy Y will auto reboot.
9. unplug the USB cable from PC/Laptop
Thanks bro, I have 2 questions more,
before flash your PDA is it necessary to go back to stock rom?
Currently I'm using V6 with busy box v1.18 on hybrid2.1, should I change it to v1.19.2?
Your link for v1.19.2 in terma rom thread is not working.
Sent from my GT-S5360
a.m.muammar said:
Thanks bro, I have 2 questions more,
before flash your PDA is it necessary to go back to stock rom?
Currently I'm using V6 with busy box v1.18 on hybrid2.1, should I change it to v1.19.2?
Your link for v1.19.2 in terma rom thread is not working.
Sent from my GT-S5360
Click to expand...
Click to collapse
its not necesary.flash it as it is.just dont forget wipe data and wipe cache.for busybox 1.19.2 just download from market
termagazis said:
its not necesary.flash it as it is.just dont forget wipe data and wipe cache.for busybox 1.19.2 just download from market
Click to expand...
Click to collapse
After which step I should wipe data and cache bro?
Sent from my GT-S5360
a.m.muammar said:
After which step I should wipe data and cache bro?
Sent from my GT-S5360
Click to expand...
Click to collapse
before flashing the rom zip
termagazis said:
before flashing the rom zip
Click to expand...
Click to collapse
You mint after flashing .tar file I have to reflash my hybrid rom?
Sent from my GT-S5360
a.m.muammar said:
You mint after flashing .tar file I have to reflash my hybrid rom?
Sent from my GT-S5360
Click to expand...
Click to collapse
**** i messed up!sorry.you just flashing pda file and reboot and install busybox.no wipe
How to mod a stock kernel Tutorial (with Windows)
by: broodplank1337
In this tutorial I will explain how to unsecure a kernel and how to add init.d / custom bootanimation support to a stock kernel, in this tutorial we will be using Cygwin as shell, with Dsixda's Android Kitchen.
Requirements:
- Cygwin with Packages and Dsixda's Android Kitchen
- JRE or JDK
- Winrar
- A stock Kernel
- Some common sense
Chapters:
1. Getting the kernel
2. Setting up Cygwin
3. Setting up the Kitchen
4. Modifying the Kernel
5. Testing results
Chapter 1. Getting the Kernel
Since the kernel that you are going to use is a stock kernel, it can be found within the latest stock firmware. for example for the i9001, I have this Odin flashable: "I9001XXKQE_I9001ATOKP3_I9001XXKPL_HOME.tar.md5". Open this file with Winrar and you will see the boot.img in there, just extract it and your currently done. It may also be a zImage!
{
"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"
}
Chapter 2. Setting up Cygwin
The Cygwin package you downloaded needs to be extracted, the default folder of a Cygwin installation is: "C:\cygwin". This is recommended in most cases. Once unpacked navigate to the "home" folder. In this home folder you need to create a folder that has the same username as your current windows username. Once you made that folder you have to extract the contents of "kitchen.rar" to that folder. So you will get a folder structure like this: C:\cygwin\home\username\kitchen
Chapter 3. Setting up Kitchen
Go to the original_update folder (located in: C:\cygwin\home\username\kitchen) and open dummyrom.zip with Winrar, now move your own boot.img inside the zip and choose "Store" as compression, Press ok to update the archive. If you have an zImage instead, please remove the boot.img from the archive first. Now browse to the system folder inside the archive and replace the build.prop with a build.prop from your phone. Also choose "Store" as compression and update the archive.
Starting the Kitchen:
1. Open Cygwin (X:\Cygwin\Cygwin.bat)
2. Once loaded, enter: "cd kitchen" > Enter
3. now type "sh menu" The kitchen menu will now start...
Setting up a working folder:
1. Press 1 > Enter
2. Press Enter and wait...
3. Choose (1) dummyrom.zip > Enter
4. Choose "y" > Enter > Enter a new name (I chose WORKING_KERNEL) > Enter
(now wait until the zip is extracted)
5. Choose 2 > Enter
6. Enter to return to main menu
Chapter 4. Modifying the Kernel
Unsecuring the kernel (to use properly with ADB)
1. Press 2 > Enter (to add root permissions)
2. Press "s" > Enter (now wait until the process is done)
3. Press Enter to return to main menu
Adding init.d support (for using startup scripts in /system/etc/init.d)
1. Press 0 > Enter
2. Press 17 > Enter (to add init.d support)
3. Enter "y" > Enter (now wait until the process is done)
4. Press Enter to return to main menu
Adding custom bootanimation support
Since the bootanimation support is already inside the dummyrom.zip file, you don't need to add it again.
Chapter 5. Testing the results
Now you will find a working boot.img / zImage under: C:\cygwin\home\username\kitchen\WORKING_KERNEL\
You can copy this file directly to your phone but it won't have bootanimation support.
That's why you need to enter in the Kitchen menu:
1. Press 99 > Enter
2. Press 1 > Enter
3. Press "n" > Enter
4. Press "y" > Enter
5. Press "y" > Enter > "EnterANewZipName" > Enter
6. Now your cwm zip will be located at: C:\cygwin\home\username\kitchen\OUTPUT_ZIP
The zip that can be found in the directory above can be flashable in CWM. Ejoy your own stock kernel with init.d/bootanimation support!
Great tutorial! Btw, this works also with cm9 kernels?
Sent from my GT-I9001 using xda premium
Third post reserved for further use.
Just joking.You should make a tutorial to teach.us how to make an overclocked kernel and so on.
Btw nice tutorial from a great dev.
RyanJWZ said:
Great tutorial! Btw, this works also with cm9 kernels?
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
Thank you
And honestly I have no idea if it's working on CM9 kernels, I think it does work actually, you should give it a try
Costinutz32 said:
Third post reserved for further use.
Just joking.You should make a tutorial to teach.us how to make an overclocked kernel and so on.
Btw nice tutorial from a great dev.
Click to expand...
Click to collapse
lol hehe, I wish I knew how to do that, If I knew that I would have posted a tutorial for sure . I'm totally inexperienced with coding kernels unfortunately
and thanks btw ^^
edit: added screenshots
how to check init.d work?
kingsonwongs said:
how to check init.d work?
Click to expand...
Click to collapse
for example:
/system/etc/init.d/00test
Code:
#!/system/bin/sh
su -c "echo "pass" > /sdcard/pass"
If a file called "pass" will appear on your sdcard it's working
this is more a tutorial for how to make a rom flashable for cwm with kitchen
bootanimation with kitchen is not working for me, had to modify the init.rc manually in boot.img. but you can use the kitchen for extract the boot.img.
however, the headline of this thread is a bit confusing, the tutorial is ok.
i guess, it is not complete.
for set up working folder, you will need
system.ext4.tar
cache.ext4.tar
boot.img
from a nandroid backup of your rom
texten said:
this is more a tutorial for how to make a rom flashable for cwm with kitchen
bootanimation with kitchen is not working for me, had to modify the init.rc manually in boot.img. but you can use the kitchen for extract the boot.img.
however, the headline of this thread is a bit confusing, the tutorial is ok.
i guess, it is not complete.
for set up working folder, you will need
system.ext4.tar
cache.ext4.tar
boot.img
from a nandroid backup of your rom
Click to expand...
Click to collapse
Well actually, I've kept the dummyrom.zip so minimalistic that boot.img is fully compatible with the kitchen (it needed app/bin folder and build.prop), but all other things are basically removed.
And you don't need all those files, we are not trying to create a working rom here, and the bootanimation is idd not working correctly, that's why I added the AOSP bootanimation library to the dummyrom.zip
broodplank1337 said:
Well actually, I've kept the dummyrom.zip so minimalistic that boot.img is fully compatible with the kitchen (it needed app/bin folder and build.prop), but all other things are basically removed.
And you don't need all those files, we are not trying to create a working rom here, and the bootanimation is idd not working correctly, that's why I added the AOSP bootanimation library to the dummyrom.zip
Click to expand...
Click to collapse
ah, ok i didn't know about the dummyrom.zip
but only for extract boot.img and make the small changesfor init.d and bootanimation, you can use other methods, not the kitchen.
the setup for kitchen is much more work as needed for this.
you can also use the tool "disk internals linux reader" and change everything you want manually.
just my 2 cents.
maybe with alle that what you have done for this tutorial, you can change/expand it to "how to make a rom with kitchen"...
well whatever. do it as you want. good luck.
texten said:
ah, ok i didn't know about the dummyrom.zip
but only for extract boot.img and make the small changesfor init.d and bootanimation, you can use other methods, not the kitchen.
the setup for kitchen is much more work as needed for this.
you can also use the tool "disk internals linux reader" and change everything you want manually.
just my 2 cents.
maybe with alle that what you have done for this tutorial, you can change/expand it to "how to make a rom with kitchen"...
well whatever. do it as you want. good luck.
Click to expand...
Click to collapse
about that, you're right, it can be done allot easier, but the thing is, I never got any working kernel when I manually packed them (or with some scripts), so I'm very thankful to the kitchen, which allows me to make an actual working boot.img
Hey brood i tried this tutorial with my stock XXKG3 kernel and did it step by step
Then i flashed the output.zip and added the folder init.d in system/etc/ and the pass script you posted above but there isnt any pass file on my sdcard ):
what went wrong?
//edit: tried pushing a bootanimation (sanim.zip) to /system/media/ but after the reboot it shows the old galaxy s plus bootanimation );
EternalFame said:
Hey brood i tried this tutorial with my stock XXKG3 kernel and did it step by step
Then i flashed the output.zip and added the folder init.d in system/etc/ and the pass script you posted above but there isnt any pass file on my sdcard ):
what went wrong?
//edit: tried pushing a bootanimation (sanim.zip) to /system/media/ but after the reboot it shows the old galaxy s plus bootanimation );
Click to expand...
Click to collapse
hmm the init.d part should work. try it without "su -c" this time
the name of the bootanimation has to be "bootanimation.zip" instead of "sanim.zip"
broodplank1337 said:
hmm the init.d part should work. try it without "su -c" this time
the name of the bootanimation has to be "bootanimation.zip" instead of "sanim.zip"
Click to expand...
Click to collapse
also doesnt work without su -c and renamed to bootanimation.zip but theres still stock bootanim ):
isnt this tut working with 2.3.3 kernel?
BTW: here is my kernel:
www.hengelmueller.bplaced.net/OUTPUT_ZIP.zip
Sent from my GT-I9001 using XDA
EternalFame said:
also doesnt work without su -c and renamed to bootanimation.zip but theres still stock bootanim ):
isnt this tut working with 2.3.3 kernel?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
Hmm then I don't know atm what the problem, but about the bootanimation, did you build a zip from the working folder? Or did you just copy boot.img? Since it needs the bootanimation library which is included in dummyrom.zip
broodplank1337 said:
Hmm then I don't know atm what the problem, but about the bootanimation, did you build a zip from the working folder? Or did you just copy boot.img? Since it needs the bootanimation library which is included in dummyrom.zip
Click to expand...
Click to collapse
i have the bootanimation file in system/bin so that shouldnt be the problem ):
could you pls try with my kernel from the link i posted above?
it drives me nuts that i am not able to do such "easy" things ): ^^
btw: do i need something in init.rc or something which tells the system when it should execute the scripts?
Sent from my GT-I9001 using XDA
Search in the init.rc for system/bin/samsungani and replace it with system/bin/bootanimation.
This should work I guess. AT least this is what i did with my Stock Kernels.
Sent from my GT-I9001 using XDA
Does not work either ):
could you pls try with my kernel above?
Sent from my GT-I9001 using XDA
Tried also with skyhigh and feacore and init.d also doesnt work
could it be that they dont work with 2.3.3 ?
Sent from my GT-I9001 using XDA
EternalFame said:
Tried also with skyhigh and feacore and init.d also doesnt work
could it be that they dont work with 2.3.3 ?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
does your init.d folder and the scripts inside have the right permissions?
broodplank1337 said:
does your init.d folder and the scripts inside have the right permissions?
Click to expand...
Click to collapse
Which permissions do i need?
Sent from my GT-I9001 using XDA
Please note, this software is no longer maintained. Due to my hectic work life sadly, I no longer have time for programming. I have attached a copy of the last version to this post.
[ ABOUT ]
Tar To Flashable Zip is a multi-platform utility designed to build flashable Android recoveries from various input formats. The supported input formats are .img from your local filesystem as well as compressed .tar or .tar.md5 archives.
Tar To Flashable Zip runs on Windows XP and newer, Linux/Ubuntu, and on OSX ( supposedly, not tested )
I'll also be putting this utility on my web site within the next couple of days
[ REQUIREMENTS ]
Tar To Flashable Zip is written in Python, so it needs Python to be installed on your machine as well.
Windows users will need to install either of the software pairs listed below from their prospective developers or drop down to the "REQUIRED SOFTWARE" section and download the zip archive I'm hosting which contains the first required software pair listed below.
Linux/Ubuntu users should use their update mechanism to update Python and install wxPython to the equivalent of either of the software pairs listed below.
Mac users will need to do what ever they need to do, sorry for the lack of information, to install/update Python to their equivalent of either of the software pairs listed below.
Python 2.7.5 + wxPython 2.8
OR
Python 3.3 + wxPython 2.9 Phoenix ( Snapshot nightly builds )
NOTE::
I feel I must explain why the above softwares are required. For those of you who already know me, I've written a couple tools for Android that run on Windows only as I am a Windows programmer. In any case, I've had several requests to make Linux versions of the same utility apps. Since I'm not a Linux programmer, I was unable to grant those requests.
I'm here to help everyone that I can help. That's just me... That being said, after some reasearch I found Python to be the easiest way for me to be able to help more people with the utilities that I develop. Python will enable me to develop more and more useful utilities for the Android community while requiring less of my time to develop them. So in the end, installing Python is a win - win situation
[ REQUIRED SOFTWARE ]
Tar To Flashable Zip was written in Python. Therefore the Python interpreter is required. Tar To Flashable Zip's GUI uses wxPython. The archive linked below for Windows users has both Python 2.7.5 and wxPython 2.8. Obviously after extracting the archives contents you need to run Python's installer msi to install Python first. Then install wxPython. The installers will install 32-bit versions of Python and wxPython. This is fine even if you are using a 64-bit machine.
Windows XP and newer users -> python-2.7.5_win32+wxPython-2.8_win32.zip
Linux/Ubuntu users -> Please use your update tool to update Python to 2.7.5 and wxPython 2.8 or update Python to 3.3 and wxPython to 2.9 Phoenix
Mac users -> Please see the "REQUIREMENTS" section above
[ DOWNLOADS ]
See belowhttp://d-h.st/QFr
[ THANKS ]
@CodyF86 - For his Python expertise and beta testing
Works great! Everyone should learn Python btw, it's amazing!
Working on P3110 =) Good work
Waiting for tar.md5 to zip
Thanks @Android-Andi.
Support for .tar.md5 as well as .IMG files coming soon
Update available. Check the OP
Support for extracting from .tar.md5 archives had been added however there is no checksum verification provided at this time.
View "CHANGELOG.txt" for complete details;
What about 64bit Windows 7 users
Sent from my GT-I9152 using XDA Premium 4 mobile app
BalaN83 said:
What about 64bit Windows 7 users
Sent from my GT-I9152 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Install the 32 bit versions of python and wxpython. I develop on a windows 7 64 bit PC. 32 bit works on 64 bit too
Sent from my LG-P509
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
I found my mountable according to the files I have as a zip, it shows as /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6.
I've tried putting both those in the recovery mount space and hit convert, but nothing happens.
The file name I am useing is E4GT-EL29-directbootCWM-v3.tar.md5 from rwilco site here http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Not sure if that helps or not
easyrider77 said:
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
I found my mountable according to the files I have as a zip, it shows as /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6.
I've tried putting both those in the recovery mount space and hit convert, but nothing happens.
The file name I am useing is E4GT-EL29-directbootCWM-v3.tar.md5 from rwilco site here http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Not sure if that helps or not
Click to expand...
Click to collapse
Sorry, currently this tool does not support zImage format. Does your device support fastboot? If so and my memory serves me correctly, fastboot can flash zImage formatted images.
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Sent from my GT-N7100 using XDA Premium 4 mobile app
Well this is good!
I tested it successfully... on my Windows XP SP3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think there is a misunderstanding about this tool. Most of the users think that this tool can convert the whole tar/tar.md5 file to a ROM zip file. Actually it does with recovery.img only.... It's already specified in the thread... but not in the thread title....
zaharakis said:
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Click to expand...
Click to collapse
zaharakis said:
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not sure what exactly the problem is. This tool is only supposed to extract "recovery.img" from a .tar.md5 archive and then create a flashable zip. I've never seen a recovery of any kind that is 2+ GB in size. Most recoveries average around 10 MB, give or take a few MB.
Thread title has been update to reflect that this tool is for recoveries only.
shinobisoft said:
I'm not sure what exactly the problem is. This tool is only supposed to extract "recovery.img" from a .tar.md5 archive and then create a flashable zip. I've never seen a recovery of any kind that is 2+ GB in size. Most recoveries average around 10 MB, give or take a few MB.
Thread title has been update to reflect that this tool is for recoveries only.
Click to expand...
Click to collapse
No recovery,I tried to make a full rom.tar.md5 file to zip..
Sent from my GT-N7100 using XDA Premium 4 mobile app
zaharakis said:
No recovery,I tried to make a full rom.tar.md5 file to zip..
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry, you'll need to use ODIN to flash a ROM from .tar.md5 archive.
shinobisoft said:
Sorry, you'll need to use ODIN to flash a ROM from .tar.md5 archive.
Click to expand...
Click to collapse
Thank u mate ☺ I know it. I just wanted to make a flashable .zip file of rom to have it in my sdcard .
Sent from my GT-N7100 using XDA Premium 4 mobile app
Reverse?
is it possible to make a flashible zip into a tar? Just curious
majicmazo said:
is it possible to make a flashible zip into a tar? Just curious
Click to expand...
Click to collapse
Yes, but not with this utility.
Sent from my LG-P769 using Tapatalk
How to use on Mac
For those who wanna use this on a Mac OS X here is what you do.
Go to:
https://www.python.org/downloads/
Download the 2.7.7 python .dmg.
Mount the .dmg and run the Python.mpkg
Once the installer is done go to your applications folder. There will be a new folder there called Python 2.7.
Open that folder. Inside will be a Python Launcher.app (Looks like a Rocket Ship). The Python preferences window will come up.
Under Settings for file Type, change it from Python Script to Python GUI Script. Close out the preferences.
In the menu bar it should still say Python Launcher. Go to File / Open. Search for the TarToFlashableZip_1.0.0.1 folder you get from the zip you download in the original post. Find the TarToFlashableZip.pyw.
The tool will open. Load in your recovery.img or .tar file. Make sure you have chosen the right recovery partition and hit convert.
Thanks to the op for this tool. Very handy.
No way to use it on windows 7?
shinobisoft said:
[ ABOUT ]
Tar To Flashable Zip runs on Windows XP and newer, Linux/Ubuntu, and on OSX ( supposedly, not tested )
Click to expand...
Click to collapse
Hello
Thanks for this tool.
Is there no way to use this tool on windows 7?
Regards
Dr.Ghobar
Dr.Ghobar said:
Hello
Thanks for this tool.
Is there no way to use this tool on windows 7?
Regards
Dr.Ghobar
Click to expand...
Click to collapse
It requires Python to be installed on your system. I believe I stated such in the OP. This was developed on a computer running Windows 7 Professional...
Sent from my SM-G360P using Tapatalk
A lot of people were having issues with designgear's instructions on rooted their official roms.
Please read this guide (link below) first if you have no experience with this URDLV rooting method (a root method that avoids triggering KNOX counter).
http://www.theandroidsoul.com/universal-root-de-la-vega-script/
Here's a set of steps that worked
------------------------------------------------------------------
To URDLV your offical ROM (worked on MF4)
Some Assumptions:
1.) Snapdragon Processor
2.) Current Bootloader on your phone, MJ1 or lower. If higher, you'll likely trip KNOX
3.) Reactivation Lock = Disabled
Procedure:
Applying URDLV to Official ROM:
- Install Cygwin (64bit or 32 bit depending on your OS)
- Started the Cygwin terminal
- cd'ed to proper drive and URDLV folder
-----ie: cd urdl
- chmod +x URDLV.bat
- ./URDLV.bat full c:/URDLV/blahblah....tar.md5 (drag-n-dropped the path to the file)
-----this will take a while on regular HD
The following steps are folked into two alternate methods.
Method 1 can work for MF4, because it seems to work with the MF1 files, so not uploading the accompanying files from the official MF4 rom neglected by URDLV's process can work.
Method 2 is more complete, and includes the uploading of all files EXCEPT the bootloader, this should minimize any mismatches of files causing issues.
Method 1: Upload only System and Cache First, other files individually
-Use ODIN to send the file over to Phone (follow designgear's OP instructions)(or PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/ )
-Put the root files on the phone
Extra Reading (optional):
- follow designgear's OP instructions
- PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/
-----extract root_de_la_vega_sdcard.zip
-------- root_de_la_vega.sh (file)
-------- root_files (folder)
-----put into the directory: \sdcard
-Reboot
-Delete the Root files
-Reboot
-Extract the Modem.bin and NON-HLOS.bin file from the Official ROM (optional for MF4) (some later roms REQUIRE matching NON-HLOS.bin and MODEM.bin files)
-----these files were excluded by URDLV's output ROM (for reasons unknown with other ROM version, but the NON-HLOS.bin and modem files from MF4 seem to integrate fine)
-Use ODIN to send Modem.bin and NON-HLOS.bin to the phone via CP slot
If for some reason your WiFi passwords keep getting forgotten:
http://forum.xda-developers.com/showthread.php?t=2522629
-Done
Method 2 (which includes all files except the bootloader):
1.) Extract the System.img and Cache file FROM the URDLV tar.md5 TO [Folder]
--------You could use 7Zip
2.) Extract all files EXCEPT ABOOT and Cache file FROM the Official ROM TO [Folder]
3.) Now [Folder] should contain 10 files
4.) Tar up those files in [Folder].
----In Cygwin:
Change directory to the [Folder]
Enter the following commands to tar up your files into a TAR.MD5 file:
tar -H ustar -c *.* > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
How your TAR.MD5 should look like:
{
"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"
}
5.) Send your your_odin_package.tar.md5 package via ODIN (AP Slot) to your phone
6.) -Put the root files on the phone (follow designgear's OP instructions) (or PART 2 in HERE: http://www.theandroidsoul.com/universal-root-de-la-vega-script/ )
-----the directory: \sdcard
-Reboot
-Delete the Root files
-Reboot
If for some reason your WiFi passwords keep getting forgotten:
http://forum.xda-developers.com/showthread.php?t=2522629
-Done
------------------------------------------------------------------------------
For future rom updates (applicable to rooted users):
Reports claim that Mobile Odin works: http://forum.xda-developers.com/showthread.php?t=2522729
-------------------------------------------------------------------------------
Download Links in case if needed:
Working link:
https://mega.co.nz/#!co1jRKYY!p94iENAmHkqd9wD3c0T1qC_dz03o7n8xmmkuIiVxCLQ
OLD DELETED:
Universal RDLV script (v0.2)
https://mega.co.nz/#!ugJFUTCL!NrME135Mia6-x4e0E-21uQXmh8wMbhrksHG0HjTtg4g
Root de la Vega sdcard files
https://mega.co.nz/#!qoQnmAQD!U_dQMRsZ7UFMpEicnnGIFAtvn7V6Ti_gbyPDt9TDmmY
Odin v3.09
http://filecloud.io/cp43ua5j
Sammobile Firmwares
http://www.sammobile.com/firmwares/
Good guide m8 if I may tell you something to put in top of everything and This is that URDLV works only in mj1 bootloader and below, if with any way you have updated with OTA/KIES/SERVICECENTER or bought with mj3 and above you cannot use any of Vega ways.
Sent from my SM-N9005 using Tapatalk
You should write that old bootloader is needed and you should modify the process : boot, hidden and recovery images should be added to the tar
geek78 said:
You should write that old bootloader is needed and you should modify the process : boot, hidden and recovery images should be added to the tar
Click to expand...
Click to collapse
Are there any risks to triggering KNOX by integrating those files ?
I thought we don't want the boot file beyond mf1 since it makes it impossible to root without triggering KNOX later?
Figure there are reasons why designgears neglected to include those files.....
klau1 said:
Are there any risks to triggering KNOX by integrating those files ?
I thought we don't want the boot file beyond mf1 since it makes it impossible to root without triggering KNOX later?
Figure there are reasons why designgears neglected to include those files.....
Click to expand...
Click to collapse
No it won't as those are not the bootloader. I made a URDLV system image of MJ7 and added all the other files from the original rom (MINUS aboot --> bootloader) and flashed with odin. Got root and knox counter not tripped. :good:
Nice, I dont feel like uploading the system image again (and reroot), just to get the other files in.
Can I just tar.md5 up the left over files and Odin them in?
If so, which Odin slot?
klau1 said:
Nice, I dont feel like uploading the system image again (and reroot), just to get the other files in.
Can I just tar.md5 up the left over files and Odin them in?
If so, which Odin slot?
Click to expand...
Click to collapse
Yes you can just tar.md5 the rest and flash it. Not really sure where to place it but you can try ap or wait for others to reply.
Yes, I tar.md5 them up and ODIN them up from the AP slot.
It works
Was this thread moved over the General?
If not, could a MOD please move it over to Original Development where the URDLV thread also resides?
Thanks,
klau1 said:
Was this thread moved over the General?
If not, could a MOD please move it over to Original Development where the URDLV thread also resides?
Thanks,
Click to expand...
Click to collapse
Guides don't go in Development threads.
@klau1
Can you remove the download links please and link to the thread. I am going to be updating soon and don't want you to have dead links or links to older versions up. Thanks.
This guide will NOT work and brick your camera and wifi (did for me)
Real solution: http://forum.xda-developers.com/showthread.php?p=47390175
@klau1 u are allowed to copy my guide if you put my name on the op
My guide is 100% working for me 0x0 root camera wifi dmj7
Sent from my SM-N9005 using XDA Premium 4 mobile app
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
In the case of mj7, the other files designgears urdlv neglected to include are required.
@designgears Let me know once you've updated your guide so I can update and reflect the changes here thanks.
Hi all!
I own SGN 3 with exynos octa processor.
Versions of installed firmware:
AP: N900XXUBMJ1
CP: N900XXUMI2
CSC: N900OJVBMI5
Can I root this device with URDLV method without any problem with KNOX and warranty?
Can I update firmware in the future with KNOX trigger = 0x0 and so on?
Thanks.
No, UDRLV only works with Snap Dragon version.
klau1 said:
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
I thought it didn't work on any bootloader under MJ1?
If it does work on MJ4, I'm on N900W8OYABMJ4 (Rogers Canada), which method would work best for rooting it.
Thanks! Sorry for being a noob:crying:
Click to expand...
Click to collapse
SimerToor said:
klau1 said:
It didn't work for you, I suspect because your mj7 rom requires the matching modem and nos file. Where as the MJ4 can work without it.
Click to expand...
Click to collapse
I thought it didn't work on any bootloader under MJ1?
If it does work on MJ4, I'm on N900W8OYABMJ4 (Rogers Canada), which method would work best for rooting it.
Thanks! Sorry for being a noob:crying:
Click to expand...
Click to collapse
If the phone is ALREADY on MJ4 it's impossible to root with the current URDLV.
This method requires you to START OFF with MJ1 ROM because once your phone already has been upgraded beyond MJ1, the newer bootloader can detect changes in the URDLV rom and trigger KNOX.
Whereas the bootloader in MJ1 can be exploited.
You can't factory reset the bootloader back to MJ1 after you've upgraded AFAIK.
efs safe?
Hi,
Is the efs partition safe when flashing all those files ?
Could it be overwritten ?
Thx.
Masterz said:
Hi,
Is the efs partition safe when flashing all those files ?
Could it be overwritten ?
Thx.
Click to expand...
Click to collapse
100% safe
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app
Frickin amazing. Worked perfectly on my T-Mobile Note 3. No flag tripped, have root, will party. Had to use Cygwin to do it BTW.
Xposed has been achieved with some long testing back and forth for Galaxy S5 Neo. Without the need of custom build recovery :victory:
Code:
method public Disclaimer();
You're allowed to take my work and create your own rom, or do anything with it.
I (Laststandingdroid) provide these files as/is by no EULA or anything else.
I share this with the community and you [I][B]don't[/B][/I] need to ask for permission.
Your cat, dog, horse or even your baby is allowed to take these files and put it in your phone without questioning me.
All i do ask is that you put correct credits. however if you don't want to it isn't a must i won't die, nor get a heart attack. I know how the internet works. people will always copy and being willing to take credits for others work ;)
.end method
Note this recovery is experimental, it was used for my personal testing but it is now released here.
Requirements:
Rooted Device (or not mandatory i guess)
Busybox
PC with odin
Custom Modified Stock Recovery with insecure adb
stock recovery here: (Odin tar) https://mega.nz/#!DgomiZAQ!1m7aU5ojoU7PCw4L7E8hmk7mCFo2z0f_sYafJHzN7XE (NEE)
Modified recovery (Odin tar)
https://mega.nz/#!jogHWBTC!jozQXYAdnfzblZNiUmei4RLnzgoFzQg3WAdsi-LDMPA
Flash with Odin
Stock deodex-xposed Download:
https://mega.nz/#!r8BzXQKD!YCJsATrxuXRg7-tiHFtJWRKc6Mt3fTQAYElzPR01uSo
DIY (Do It yourself) Method
1/ First you need to go to sammobile to download last available generic firmware OR download the one related to your carrier.
2/ You need to decompress twice (first is the zip from sam, 2nd the tar.md5 file) with Universal Extractor.
3/ you will see many file (boot, recovery....and system the one which is necessary).
4/ now we need to decompress system.img but you can't currently. We need to convert this file to ext4 format. So time to download some necessary extra files. (https://1fichier.com/?bz9rmuuap4)
5/ Decompress this zip file in c:\deodex and put inside the system.img
6/ run 1MODEXT4.bat. This will create a temp.ext4 file in this folder.
7/ Now you can open the temp.ext4 file with ext2explore.exe which is in the folder.
8/ Create a folder on your PC named "system". Go on ext2explore, select "app", framework", "priv-app" folder and right click and make "save". Choose the folder system, you created.
9/ Now you have all the odexed files we need to deodex
10/ Run "SVADeodexerForArt.exe" and precise the system folder you created. Tick all boxes. Wait until it deodex. See if there is no errors in window
11/ Watch inside the "deodex" folder. you will see app, priv-app & framework folder. Here are the deodexed files.
Optional step:
12/ If you want before pushing the files you can debloat the rom. Or include xposed files too as LastStandingDroid
Pre Built Files
1.Download the zip and extract it on your pc.
2. Flash modified recovery trough Odin
Reboot to system
adb shell
mount - remount,rw /system
rm -rf /data/dalvik-cache
4. Reboot into recovery (don't be fooled by the stock recovery, it is modified to get system mounted as r/w trough adb
5. Plug your phone to PC, and wait for adb to initialize (this can take up to 20 seconds)
6. Type: adb remount
7. type: skip this for now now to 8.
8. Type adb push *drag and drop the extracted system folder to cmd/terminal window. /system/
In the terminal you should now have adb push /path/to/system /system/
8. Wait until all files has been pushed
9. Reboot the device, it will take time to boot since it will rebuild dalvik-cache
Optional is to recover stock recovery
Thanks @wanam for his modified xposed version which makes it compatible with Samsung variants for 5 1+ @Chainfire for his insecure adbd which is used to mount the system as read/write in recovery. Without this this wouldn't be possible
Special thanks @WILMANS2M for testing and reporting back. @bolme123 for testing and reporting back. @Dennziil testing and reporting @kaodd for being funny and being happy that we work on this
Sent from my SM-G903F using Tapatalk
Bugs: your original /sdcard path might be replaced this will not remove your files it will rather just kill the path.
You can access the internal sd files using /storage/emulated/0/
Settings might force close sometimes, this only seems to happen if you go to app info from recent. Not sure what gives
At least it might takes longer to load
Sent from my SM-G903F using Tapatalk
{
"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"
}
Sent from my SM-G903F using Tapatalk
Think im missing something, but don't know what.
C:\Users\Dennis>adb shell
[email protected]:/ $ dd if=/dev/block/platform/13540000.dwmmc0/by-name/RECOVERY of=/sdcard/stockrecovery.img
000.dwmmc0/by-name/RECOVERY of=/sdcard/stockrecovery.img <
dd: /dev/block/platform/13540000.dwmmc0/by-name/RECOVERY: Permission denied
So laststandingdroid, no need of a permissive kernel to do this right ?
Envoyé de mon K00F en utilisant Tapatalk
If you follow this will it trigger Knox or other bits and does it require root for it to work?
Thank you very much for your work
Dennziil said:
Think im missing something, but don't know what.
C:\Users\Dennis>adb shell
[email protected]:/ $ dd if=/dev/block/platform/13540000.dwmmc0/by-name/RECOVERY of=/sdcard/stockrecovery.img
000.dwmmc0/by-name/RECOVERY of=/sdcard/stockrecovery.img <
dd: /dev/block/platform/13540000.dwmmc0/by-name/RECOVERY: Permission denied
Click to expand...
Click to collapse
You need to write su first sorry
WILMANS2M said:
So laststandingdroid, no need of a permissive kernel to do this right ?
Envoyé de mon K00F en utilisant Tapatalk
Click to expand...
Click to collapse
Not quite sure I used permissive kernel might work. But I use permissive one to be able to use viper4android
Tepes4 said:
If you follow this will it trigger Knox or other bits and does it require root for it to work?
Thank you very much for your work
Click to expand...
Click to collapse
Yes know will be triggered and it requires root ofc [emoji14]
Sent from my SM-G903F using Tapatalk
So maybe first install permissive kernel, 2nd flash cfautoroot and 3rd your method
Envoyé de mon SM-G903F en utilisant Tapatalk
WILMANS2M said:
So maybe first install permissive kernel, 2nd flash cfautoroot and 3rd your method
Envoyé de mon SM-G903F en utilisant Tapatalk
Click to expand...
Click to collapse
No idea on permissive kernel
Root shouldn't be needed as recovery can remount as r/w but it's recommended since some apps requires root
Sorry I posted this tutorial in a rush.
Will clear it later.
Other galaxy s5 neo users if you want deodex send me your system framework and apps in order to get deodexed system
Sent from my SM-G903F using Tapatalk
I finally succeed deodexed last sgs5 neo rom file G903FXXU1AOI5_G903FXEF1AOI1_G903FXXU1AOI7.
64-bit Deodexer for Android Runtime (Version 3.5 ?? 20/07/2015) © Valery Studenikin, 2015
Path to stock /system directory: D:\Deodex\5.1.1\system
Android 5.1.1: SM-G903F, LMY47X.G903FXXU1AOI5, changelist 5560999, Tue Sep 15 19:31:20 KST 2015
Processor architecture: \arm\
Files deodexed succesfully: 355, with errors: 0. CPU time: 00:23:46 (1426,132 sec.)
List of originally deodexed (within stock firmware) files, are left as they were originally:
/system/framework/com.google.android.maps.jar
/system/framework/com.google.android.media.effects.jar
/system/framework/com.samsung.device.jar
/system/app/Bridge.apk
/system/app/minimode-res.apk
/system/app/RCPComponents.apk
/system/app/SecurityLogAgent.apk
/system/priv-app/ContextProvider.apk
/system/priv-app/HealthService.apk
/system/priv-app/intelligenceservice.apk
/system/priv-app/SPDClient.apk
LastStandingDroid i see in your zip file that some app were not deodexed as GMScore...Normal ?
I will try to push mine and try your method and will make a factory reset to see what's happening.
WILMANS2M said:
I finally succeed deodexed last sgs5 neo rom file G903FXXU1AOI5_G903FXEF1AOI1_G903FXXU1AOI7.
LastStandingDroid i see in your zip file that some app were not deodexed as GMScore...Normal ?
I will try to push mine and try your method and will make a factory reset to see what's happening.
Click to expand...
Click to collapse
Yes gms core failed I don't care about it since it isn't needed.
Edit shealth is broken download an update trough Samsung apps or download: https://mega.nz/#!3lwmEaKQ!f3iG_WQrK4hTXumHZbo0Jvs5DT9O0UC1TDlLRr4kH4s
Install as an update.
Sent from my SM-G903F using Tapatalk
Just 3 questions :
1/ Do we need to keep folders of apk. Can we put only apk in folder app or priv-app like xposed apk ?
2/ What do you add to the deodexed rom apart xposed file ?
3/ About xposed file :
in app : XposedInstaller.apk
in lib : all files
in framework : XposedBridge.jar
That's all we need ?
I really thank you.
Next step : The dirty flash
WILMANS2M said:
Just 3 questions :
1/ Do we need to keep folders of apk. Can we put only apk in folder app or priv-app like xposed apk ?
2/ What do you add to the deodexed rom apart xposed file ?
3/ About xposed file :
in app : XposedInstaller.apk
in lib : all files
in framework : XposedBridge.jar
That's all we need ?
I really thank you.
Click to expand...
Click to collapse
Depends on what you mean to keep folders?
There's only xposed added and needed files.
There's also files in system/bin app_process oat2dex patchoat and two more check the zip file xposed containing
Now it's ice fishing
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
Depends on what you mean to keep folders?
There's only xposed added and needed files.
There's also files in system/bin app_process oat2dex patchoat and two more check the zip file xposed containing
Now it's ice fishing
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
For ex, for the folder "AccuweatherPhone2015" we have inside "AccuweatherPhone2015.apk"
I just wonder if we can just put "AccuweatherPhone2015.apk" inside "app" folder without the folder "AccuweatherPhone2015"
Feel like a noob now, but when i type (adb shell su) in cmd, it gets locked. :S
WILMANS2M said:
For ex, for the folder "AccuweatherPhone2015" we have inside "AccuweatherPhone2015.apk"
I just wonder if we can just put "AccuweatherPhone2015.apk" inside "app" folder without the folder "AccuweatherPhone2015"
Click to expand...
Click to collapse
No since apps requires lib folders and stuff in arm/lib
Dennziil said:
Feel like a noob now, but when i type (adb shell su) in cmd, it gets locked. :S
Click to expand...
Click to collapse
Where do you type it? While phone is on?
Anyway I'll upload a stock recovery and modified as Odin tar file
Modified recovery flash able trough Odin comes soon
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
No since apps requires lib folders and stuff in arm/lib
Where do you type it? While phone is on?
Anyway I'll upload a stock recovery and modified as Odin tar file
Modified recovery flash able trough Odin comes soon
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
I hope! because I'm a little bit lost :crying::crying:
noob I am, noob I stay
LastStandingDroid said:
Anyway I'll upload a stock recovery and modified as Odin tar file
Modified recovery flash able trough Odin comes soon
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Great, then i'll just waint for the tar file insted Great work btw :good:
mmh i will try to delete all apk folder which does not have other file/folder inside than the apk one. In fact, only some folder have lib...folder inside. Most have only apk.
Will try.
As i said, will make a few test
androidissime said:
I hope! because I'm a little bit lost :crying::crying:
noob I am, noob I stay
Click to expand...
Click to collapse
Don't worry it comes in some minutes
Dennziil said:
Great, then i'll just waint for the tar file insted Great work btw :good:
Click to expand...
Click to collapse
Yeah I forgot about that
WILMANS2M said:
mmh i will try to delete all apk folder which does not have other file/folder inside than the apk one. In fact, only some folder have lib...folder inside. Most have only apk.
Will try.
As i said, will make a few test
Click to expand...
Click to collapse
Sure I don't recommend it since I see no reason to use it that way [emoji14]
Hopefully sooner or later I'll get a modified system.Img working there's no eta for that though. Since it yet doesn't flash in Odin.
Sent from my SM-G903F using Tapatalk