[Preroot deodexed]N7100XXDMG1_N7100ODDDMG1_INU_Prerooted_deodexed - Galaxy Note II General

[Preroot deodexed]N7100XXDMG1_N7100ODDDMG1_INU_Prerooted_deodexed
I have recieved too many request for deodexed prerooted for latest MG1 on thread as well PM, so i have consider it.
I have spare 1.5 hour right now and hopefully should be fine within time.
Once it will be ready will upload to my prerooted thread
Again this won't be for every ROM, as uploading 1Gb file is difficult for me with my unlimited net with cable. Using 3G is quiet costly here.
Anyway it will be same
No wipe,No flash counter raise + Prerooted ROM + Deodexed + Zipaligned
Thank you all

Ok it's done and will update soon after testing.

Ok Guys it's up now on my PreRooted thread
This is prerooted ROMN7100XXDMG1_N7100ODDDMG1_N7100DDDMG1_INU
+
Rooted (SuperSU 1.34)
+
busybox
+
Deodexed
+
Zipaligned
Non-Wipe, No Flash counter raise
Open Odin.exe (packed in odi3_v3.03 folder
select PDA tab and point to attached deodexed/prerooted ROM
For detail option picture attached here with
Flash
Reboot
Open SuperSU - update binary (If ask)
Done.
Zip also havingg Extra folder (Optional)
---------------------------------------------------------------------
Extra : folder contains
1.philz_touch_5.06.1-n7100.tar.md5 is philx recovery, if you wish to flash (Optional)
2.recovery.tar.md5 is stock recovery from same prerooted ROM, if you wish to revert to stock recovery any time (after flashing custom) you can use it.

Related

[ROM-Update (Dutch)] Stock 1.5 + Cyanogen Root + Pre OTA Update

To update your Stock HTC 1.5 rooted with Cyanogen Mod, just use the included zipfile and reboot into recovry mode. Select to update with any zip file and choose the included file...
WARNING!!!!!!! The attached file is for Dutch Users only tested. Damage to your device by using this patch is your own responsibility.
i think this go to development section ?

[Guide]ATT KitKat leak working with root

I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
I found a place to upload the rom: http://forum.xda-developers.com/showthread.php?p=47451659#post47451659
Hopefully the instructions there are clear...
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Ctrl-Freak said:
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
Click to expand...
Click to collapse
Glad to see locked BLs getting some love. Any chance of KK screenshots? No one seems to have uploaded them on any thread. How has your experience been with it so far?
freak4dell said:
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Click to expand...
Click to collapse
This took me a day to figure out. I used simg2img in ubuntu.
anirudh412 said:
... How has your experience been with it so far?
Click to expand...
Click to collapse
The only material problem I am having is battery life - it seems noticeably worse that the att .54 ota version.

[LB] Create ROOTED update package from stock FTF (Windows)

With the latest firmwares not directly rootable you need to download or create an update package with root and recovery and update your system via recovery. This won't delete your data and root will be there on 5.x.x. I made this complete tutorial so that everyone can make an update from an FTF file.
THIS IS FOR LOCKED BOOTLOADER and/or STOCK KERNEL ONLY !!!
MAKE SURE YOU HAVE A BACKUP !!!​
1.1 You need obviously an already rooted phone with [NUT]'s DualRecovery installed and working (this can be achieved on firmwares with Android 4.4 and 5.0.2)
If you don't have the recovery, you can install it from here: [Z2][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A see post #2 there for instructions. 2.8.12 and later should work on KitKat and Lollipop too!
1.2 You need Flashtool with working USB drivers (Make sure flashmode works - which means the drivers are properly installed on your system, especially on Windows 8/8.1/10 - before you start this tutorial).
2. Download the newest FTF update file for your phone/branding. Use the same customization version (xxxx-xxxx) that is on your phone now!
This you can do with Flashtool (Devices/Check Updates menu) or download it from the [FTF] STOCK FIRMWARES for Xperia Z2 thread.
(Alternative option for advanced users: XperiFirm -> you can create an FTF from the downloaded firmware files with Flashtool.)
3.1 Download PRFCreator v1.1.zip from [TOOL] PRFCreator - easily create pre-rooted firmwares.
3.2 Download latest stable SuperSU update package from here.
3.3 Download XZDualRecovery's latest - 2.8.23 - flashable version (Z2-lockeddualrecovery2.8.xx-RELEASE.combined.zip) from here (XZDualRecovery section).
You will have 5 files so far:
PRFCreator v0.5.zip
D650x_23.x.1.A.x.xxx.ftf (with different name and firmware version number)
UPDATE-SuperSU-v2.46.zip
Z2-lockeddualrecovery2.8.x-RELEASE.flashable.zip
Click to expand...
Click to collapse
4. Unzip PRFCreator and run it.
5. Load the FTF, SuperSU and Z2-lockeddualrecovery (flashable) zip files into the three section.
6. Uncheck all the Include options [ ], we don't need them, we will flash them with Flashtool after the update. I think it's still safer to flash kernel, baseband, boot and other system critical parts of the firmware from Flashtool.
(But if you want to include them anyway then you can skip part 11 and start your phone normally.)
There is a Legacy mode option in the latest version. Without it PRFCreator will use a direct sin flashing method for system update. If you check the legacy option it will use the older repack method for system. The direct sin flashing should work in most cases if not then use the legacy option.
7. Push Create. After it's finished (wait for the Create button to be available again), you'll find a flashable.zip in the folder of PRFCreator.
Check the contents of the zip file, it should look like this with PRFCreator v0.5:
Code:
data
META-INF
system
utils
partition-image.sin
system.sin
dualrecovery.zip
SuperSU.zip
If something is missing, redo the process from step #4 until all is there.
8. Copy flashable.zip to the internal/external SD card of your phone. If you want to go for 100% working root and recovery copy UPDATE-SuperSU-v2.46.zip and Z2-lockeddualrecovery2.8.x-RELEASE.flashable.zip there too.
9. Boot your phone into recovery (use TWRP!).
10. Install flashable.zip in recovery. After finished DO NOT REBOOT !!!
*Optional step: install SuperSU and Recovery again so if something went wrong during the system flashing you'll still have a working recovery.
Clear Cache/Dalvik only and go back to Home and choose Reboot/Power off.
11. Start Flashtool and with the Flash device icon flash the kernel and other baseband files from the FTF in Flashmode.
Use the following configuration (or similar):
Wipe:
Code:
[ ] APPSLOG
[ ] CACHE
[ ] DATA
Which means nothing is wiped, this is good for a system update only, that reserves your settings, applications and data. (If you want a clean system or run into errors after updating only the system, you can wipe all the three.)
Exclude:
Code:
[ ] BOOTBUNDLE
[x] PARTITION
[ ] KERNEL
[ ] FOTA
[ ] BASEBAND
[x] SYSTEM
[ ] ELABEL
Which means system, partition and ta options are unchanged and won't be wiped/overwritten. You can exclude fota, elabel and baseband too, but some phone functions may be limited. Always use your phone's original customization version when choosing FTFs. Never exclude = never check (x) kernel. It is the main reason we're flashing this.
TA -> not always present in the FTF file, but if you see it, then EXCLUDE it, just to be sure, you don't simlock your device
Code:
[x] No final verification
[ ] Reset customization
Connect the micro USB to your phone and get ready with the other end of the cable in your hand
Push Flash button.
Push the Volume down button and connect the USB cable to the computer's USB port. Wait until Flashtool begins with the flashing and you can release the Volume button now.
When finished, unplug the the phone, start it and wait until it completes the first boot. After it is fully working, check SuperSU and if you can mount system R/W too (in Root Explorer or in other root file manager).
ENJOY another rooted version of Android I can give support only for this process, for the tools you need to ask your questions in the appropriate threads above.
Thanks to @zxz0O0 for creating the PRFCreator and the Lollipop fixes, it makes things easier in this process (you don't need to mess with linux mounts, virtual machines and other scripts copying system images and recovery updates to a zip).
hi
I look forward to your work to install on my z2
:good:
Nice guide. Please let me know the bugs in PRFCreator v0.6 (you can drop me a pm as I don't have a lot of time for xda at the moment). Also, is step 12 really necessary? Dualrecovery should already be included in the flashable zip (same for step 11 if you include those files).
Will downgrading 4.4.4 to 4.4.2 without wiping data cause a bootloop?
ravdo said:
Will downgrading 4.4.4 to 4.4.2 without wiping data cause a bootloop?
Click to expand...
Click to collapse
Yes. At least that's what i'm getting. And i'm currently stuck because my last TiBu backup is months old :/ bummer...
zxz0O0 said:
Nice guide. Please let me know the bugs in PRFCreator v0.6 (you can drop me a pm as I don't have a lot of time for xda at the moment). Also, is step 12 really necessary? Dualrecovery should already be included in the flashable zip (same for step 11 if you include those files).
Click to expand...
Click to collapse
I didn't use the v0.6 because more people complained in the tool's thread about it. V0.5 is working, I can test v0.6 later (maybe tomorrow).
Dualrecovery is included with the flashable.zip but the RIC killer isn't working in that version, it needs to be installed again with the PC installer. Maybe someone (I mean @[NUT] ) could clean up the process
Thx! This is really useful for noobs like me!
Hi zxz0O0, the updater script is looking for 3 files in /utils but when the zip is created on 0.6 those files remain in the root of the zip so you get error when flashing. i think that's the problem with 0.6 but i can be wrong as i didn't test it
norti said:
I didn't use the v0.6 because more people complained in the tool' thread about it. V0.5 is working, I can test v0.6 later (maybe tomorrow).
Dualrecovery is included with the flashable.zip but the RIC killer isn't working in that version, it needs to be installed again with the PC installer. Maybe someone (I mean @[NUT] ) could clean up the process
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56542112&postcount=130
It may be an alternative for Step 12 to modify the flashable dualrecovery .zip file as the post of the link above, I think.
ptmaniac said:
Hi zxz0O0, the updater script is looking for 3 files in /utils but when the zip is created on 0.6 those files remain in the root of the zip so you get error when flashing. i think that's the problem with 0.6 but i can be wrong as i didn't test it
Click to expand...
Click to collapse
Please use his thread for error reporting, thanks!
Ningyou Higeki said:
http://forum.xda-developers.com/showpost.php?p=56542112&postcount=130
It may be an alternative for Step 12 to modify the flashable dualrecovery .zip file as the post of the link above, I think.
Click to expand...
Click to collapse
I don't want to change [NUT]'s recovery installers (everyone can edit scripts if wants), this may be a longer process but more user friendly.
Hi,
Stuck in a ****ing bootloop.. How do I recover?
Puffin617 said:
Hi,
What will happen if I tick RESET CUSTOMIZATION as well?
Click to expand...
Click to collapse
It will reset your phone to factory state after flashing the firmware. If you want a clean update (here we don't) only then you should use this option.
Puffin617 said:
Hi,
Stuck in a ****ing bootloop.. How do I recover?
Click to expand...
Click to collapse
Flash a previous ftf (not 4.4.4), root it, install recovery and restore your backup.
Did you got any errors during the process?
norti said:
Flash a previous ftf (not 4.4.4), root it, install recovery and restore your backup.
Did you got any errors during the process?
Click to expand...
Click to collapse
During the flashing of the ZIP (before FTF), there was something that failed (set_perm) but it still said SUCCESSFUL... But I want a clean update. Can I clean DATA at least?
Puffin617 said:
During the flashing of the ZIP (before FTF), there was something that failed (set_somethingorother) but it still said SUCCESSFUL... But I want a clean update. Can I clean DATA at least?
Click to expand...
Click to collapse
Of course, I'll put this in the OP as an option.
@norti, I tried EVERYTHING again. This does NOT work. Bootloop...
When flashing the Zip, I get an error with the set_perm:
Please link a pre-rooted ROM which has NOT been de-odexed or de-bloated...
PS: After selecting to turn off the phone, it tells me "the phone does not seem to be rooted. Do I want to root" Do I need to select to root it?
---------- Post added at 11:26 PM ---------- Previous post was at 11:18 PM ----------
I get the following when flashing the FTF as-is:
08/025/2014 23:25:54 - ERROR - Processing of system.sin finished with errors.
08/025/2014 23:25:54 - INFO - Ending flash session
08/025/2014 23:25:54 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="8009001C";
now where is that "Thanks" button located.....
Succeeded!!! But I can't make system R/W, though I do as Step 12... Any ideas?
Can someone please link me a good FTF?
Puffin617 said:
Can someone please link me a good FTF?
Click to expand...
Click to collapse
Where did your FTF on your computer NOW come from?

[Rooted OR Stock] Update Procedure For Lollipop 5.0 (OC1)

Build Number: N900AUCUEOC1/N900AATTEOC1/N900AUCUEOC1
Backup anything important you might have on your phone before proceeding any further
Look Here For 100% Stock Non-Rooted Lollipop (OC1):- http://forum.xda-developers.com/note-3-att/general/100-stock-lollipop-5-0-n900aucueoc1-t3069609
100% Stock Non-Rooted Procedure
[You HAVE to be on NL1 NOT NC2, NJ5 or anything else]
1. Make sure you are on 100% stock non-rooted NL1 currently (ie no ROOT, NO BUSYBOX, NO Xposed etc.)
2. If you are not sure then restore to complete stock using this NL1 files. : Here
3. Now download the following file and save it on the external SD card: Here
4. Reboot into recovery by pressing Volume UP + Power + Home
5. Once in recovery select "apply update from external sd"
6. Then select the above file you downloaded called "N900A_OC1_Stock(100%).zip"
7. Enjoy 100% Stock Lollipop 5.0 (OC1).
8. If you change your mind and want root... then you can! (Just follow the procedure below).
Look at Post #2 For Rooted Lollipop (OC1):- http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
100% Stock Rooted Original Procedure
1. Restore back to complete NC2 stock using this files: Here or Here
2. Root using Towelroot: Here
3. Install busybox: Here
4. Install SS: Here
5. Download the following files and save it on your external SD: Here and Here
6. Now follow steps 1 to 5 from this thread: Here
7. Once that is done go back to flash the above file you downloaded called "SM-N900A_NL1_Modem_Recover_Flashable.zip" and then after flash "N900A_OC1_Stock_Rooted.zip" using Safestrap.
8. Last, from the main menu press "Reboot," reboot into "Download" mode and flash the following files using Odin's AP slot: Here
100% Stock Rooted Alternate/Easier Procedure
1. Restore back to complete NC2 stock using this files: Here or Here
2. Root using Towelroot: Here
3. Install busybox: Here
4. Install SS: Here
5. Download the following files and save it on your external SD: Here
6. Extract the files from "stock-2015-03-24--23-26-50 LRX21V.N900AUCUEOC1" folder in .7z file you downloaded above into your Safestrap backups folder, i.e: ext-sdcard/TWRP/BACKUPS/xxxxxx (the name of your backups folder may vary. If a backups folder does not already exist you must first create a backup using Safestrap's "Backup" function before proceeding).
7. Use Safestrap's Backup Function to back-up User Data.
8. Perform an "Advanced Wipe" and wipe everything but your ext-sdcard.
9. From the main menu press "Restore" and restore the stock-2015-03-24--23-26-50 LRX21V.N900AUCUEOC1 backup.
10. Once complete press the back button twice to access your backups again and restore User Data.
11. Last, from the main menu press "Reboot," reboot into "Download" mode and flash the N900A_OC1_ALL_Other_Stock_Partitions.tar.md5 using Odin's PDA slot: Here
Download/Odin Mode Flash Counter after OC1 update: S2, T2, R2, A3, P2.....
GOOD NEWS..... Downgrade to NL1/NC2 still possible!!!!!​
OC1 Stock Rooted Very Easy Procedure
1. Download this .zip and save it on external sd:- Here
2. Reboot into Safestrap.
3. Wipe everything expect external-sd.
4. Flash the .zip you download above called, "SM-N900A_OC1_Lollipop_Rooted_Rom.zip"
5. Reboot.
6. Enjoy Rooted Lollipop
To access Safestrap (only works if you followed "Very Easy Procedure"
1. Bring up Power Menu.
2. And select "Safestrap Recovery" from the Reboot Menu.
3. Flash/Backup anything you need to do in SS.
4. Once you are done with that....
5. Flash the file called "SM-N900A_OC1_Kernel_Safestrap_Installer.zip" which is located under /sdcard/OC1_Kernel/
Odin: 3.10 http://forum.xda-developers.com/showthread.php?t=2711451​
Only try it if you know how to restore to NC2/NL1. I don't want everyone to jump in at the same time. Let some brave soul try first and report back.
NON-Root method success confirmation:- http://forum.xda-developers.com/showpost.php?p=59667605&postcount=27
Root method success confirmation:- http://forum.xda-developers.com/showpost.php?p=59668138&postcount=37
Here's a Mega mirror of the NC2 Odin files: https://mega.co.nz/#F!wg5wRQrQ!vR7a6pze9dgSWjbaRSyhWA
EDIT: Should be stock, so you will have to go about rooting with towelroot and installing busybox and Safestrap.
Awesome, downloading now!
Nice work
Cowboy from Hell on a twisted trail.
Koffed From my Big Ass Outlaw Phone.
Walter.White said:
Only try it if you know how to restore to NC2/NL1. I don't want everyone to jump in at the same time. Let some brave soul try first and report back.
Click to expand...
Click to collapse
Great work
here is safestrap recovery Lollipop installer
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip 9.1 MB
https://mega.co.nz/#!fAcA3JhL!-hK_TU6NamIJdvgwWdZ90VmOwBdRBxSL70VgC4sILwc
Walter can you run the Stock install on a NC2 non-rooted/stock device? Or does it have to be NL1?
kangi26 said:
Walter can you run the Stock install on a NC2 non-rooted/stock device? Or does it have to be NL1?
Click to expand...
Click to collapse
It has to be on NL1 or it will fail the file integrity check . OTA.zip for NC2 to OC1 is different one 1197.08 MB according to this.. https://www.att.com/esupport/article.jsp?sid=KB423151&cv=820
Just 2 questions!
I just have two questions!
1: can i apply this update from NJ5?
2:If i apply the update on Stock Recovery will it reset my phone?
Walter.White said:
It has to be on NL1 or it will fail the file integrity check . OTA.zip for NC2 to OC1 is different one 1197.08 MB according to this.. https://www.att.com/esupport/article.jsp?sid=KB423151&cv=820
Click to expand...
Click to collapse
Excellent, thanks! I'd hit the thanks button again, but I'm at quota
Javi22610 said:
I just have two questions!
1: can i apply this update from NJ5?
2:If i apply the update on Stock Recovery will it reset my phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=59667172
Cowboy from Hell on a twisted trail.
Koffed From my Big Ass Outlaw Phone.
Javi22610 said:
I just have two questions!
1: can i apply this update from NJ5?
2:If i apply the update on Stock Recovery will it reset my phone?
Click to expand...
Click to collapse
I can tell you that I just learned,
1. No you MUST be on NL1
2. I don't know...........
Yup, the zip contains a bunch of binary patch files.
You must be on NL1 to flash.
Javi22610 said:
I just have two questions!
1: can i apply this update from NJ5?
2:If i apply the update on Stock Recovery will it reset my phone?
Click to expand...
Click to collapse
1. Have to be on NL1.
2. I *think* it will but now 100% sure. So make sure you backup whatever that you need to.
Awesome! Will have to try it tomorrow
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
I know we must be on NL1 and all but I'm running evolution 3.0 which is based on NL1 so can I just flash the OC1 file in ss and Odin the kernel and call it a night?
@Walter.White, could you just load the OTA to the phone after ODIN'ing NC2?
majortaylor said:
I know we must be on NL1 and all but I'm running evolution 3.0 which is based on NL1 so can I just flash the OC1 file in ss and Odin the kernel and call it a night?
Click to expand...
Click to collapse
@majortaylor Nope. It wont work. Every step/warning of those steps is important.
@TeldenW Which procedure?
Keep in mind that the Rooted procedure will become bit easier once... someone provides me with the SS backup of Stock OC1 ROM.

[ROM] Odin + Custom ROMs + CF Root Recovery + SuperSU & CWM

Here are just some general files that some of you guys might want, had no hassle at all installing all of them onto my Samsung Galaxy S3 as I tested them all before posting. I put the ZIP file together after doing some customizations to my phone and just after having a mess around with them. I wanted to post this for you guys because I know the files really were pretty useful to me so might be useful to you all as well. Enjoy guys!
BEFORE YOU READ ON / DOWNLOAD PLEASE NOT THAT THESE FILES DO NOT BELONG TO ME AND I HAVE NOT CREATED THE FILES. I TAKE NO RIGHTS OVER THESE FILES.
The download includes the following files and their formats.
TAR Files:
CWM 6.0.4.4 I9300.tar,
CF Root SGS3 v6.2.tar.
ZIP Files:
SR4 SuperSU v2.78.zip,
SlimKat 4.4.4 Build.zip,
Odin 1.85.zip.
RAR Files:
I9300 International Stock Firmware.rar.
- DOWNLOAD HERE -
Forgot to include in the OP that you will need to install Gapps ( I did not include Gapps download for either ROMs )
Cwm is very outdated. For newer custom ROMs, twrp is required.
audit13 said:
Cwm is very outdated. For newer custom ROMs, twrp is required.
Click to expand...
Click to collapse
Thanks for letting me know

Categories

Resources