Related
Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the last three days of late nights and no sleep plus full day of work!
Thanks to SDX !!
Requires:
Unlocked bootloader and root access!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into kernel /sbin, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone. No recovery or adb needed! Flash a custom kernel, boot logo (some devices) and custom recovery all from android w/o rebooting into recovery mode!
The application displays current kernel version information!
Current Device Support:
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: Sprint Galaxy S4, International HTC One, T-Mobile HTC One, Sprint HTC One, HTC EVO 4G LTE, HTC One S, HTC EVO 3D CDMA and GSM, HTC One XL, HTC Droid DNA, HTC Amaze, HTC Vivid/Holiday, HTC EVO 4G, HTC EVO Shift, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
The current phone support limitation is due to hardware manufacturer differences and their software implementations. This process can be very dangerous and I'm being very caution by thoroughly testing before releasing. I've started with the phones I am most familiar and hope to cover all those who request it!
I have a personal list of features I am going to be adding over the coming days and weeks in addition to support for other phones. Please feel free to leave feedback here and requests for phone support. If you have any information on flash_image or bmlwrite for your phone, that'll help get me started researching on your phone support request. Thanks!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release versions (free from my personal hosting): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
http://twitter.com/joeykrim
http://joeykrim.com
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
Users Guide for flashing ONLY a Kernel (zip file):
1) Ensure the bootloader is unlocked and root access is properly setup
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate the kernel zip file is contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
Im curious, why does this only work on certain phones? I need a way to flash a recovery to my Tmobile Comet (Huawei Ideos U8150). Thanks
jdyates said:
Im curious, why does this only work on certain phones? I need a way to flash a recovery to my Tmobile Comet (Huawei Ideos U8150). Thanks
Click to expand...
Click to collapse
great question. I've updated the OP to answer this better.
essentially each hardware manufacturer is able to use their own type of drivers in dealing with the phones internal memory and in formatting the phones internal file system.
this allows for many different variations. the specific phones I support are the ones I was able to obtain a flash_image binary for (hence the name flash_image) and was able to extensively test.
if you any information to the flash_image binary for your phone, i'd be more than happy to research it and adding support to the app!
i've worked day/night the last three days to put this app together and had a ton of testing. i do hope to continue to add support for more phones! thanks for the feedback and phone support suggestion! i will definitely look into it and any help you can provide would be great!
Here is the flash_image binary for Tattoo,
please add it to supported devices, thanks.
How soon before the Epic 4G gets some love?
Samsung galaxy spica gt-i5700 also use same s3c6410 chip. Will this work on it??
Sent from my GT-I5700 using Tapatalk
I have a viewsonic gtab and I HATE the splash screen - would love to see it supported. My 2c... great tool! Thanks!
joeykrim said:
great question. I've updated the OP to answer this better.
essentially each hardware manufacturer is able to use their own type of drivers in dealing with the phones internal memory and in formatting the phones internal file system.
this allows for many different variations. the specific phones I support are the ones I was able to obtain a flash_image binary for (hence the name flash_image) and was able to extensively test.
if you any information to the flash_image binary for your phone, i'd be more than happy to research it and adding support to the app!
i've worked day/night the last three days to put this app together and had a ton of testing. i do hope to continue to add support for more phones! thanks for the feedback and phone support suggestion! i will definitely look into it and any help you can provide would be great!
Click to expand...
Click to collapse
Thanks for the detailed reply, you dont see that alot from app devs these days.
Unfortunately, i have no idea what a flash binary is for my phone or how to get it. Oh well. Thanks again
dancer_69 said:
Here is the flash_image binary for Tattoo,
please add it to supported devices, thanks.
Click to expand...
Click to collapse
perfect! recovery image support should be simple.
kernel flashing methods seem to vary quite a bit between devices. could you post links up to two/three popular kernels so i can see the format they're using?
mattallica76 said:
How soon before the Epic 4G gets some love?
Click to expand...
Click to collapse
great question! i hope to get this supported within the next week as ill be on my honeymoon the next 5 days w/o internet...i know, tough but worth it
if you have the information handy, could you post links to two/three top kernels so I can examine their format?
lovleshgarg said:
Samsung galaxy spica gt-i5700 also use same s3c6410 chip. Will this work on it??
Sent from my GT-I5700 using Tapatalk
Click to expand...
Click to collapse
yes, i had thought about this but didn't know anybody with the phone. supporting this phone should be very simple as it uses that same chip set. could you post a link to a pastebin of this command:
adb shell ls -l /
to double check, flash_image on the spica also does zImage (kernel), logo.png (boot logo) and recovery.rfs (recovery) right?
thanks!
austontatious said:
I have a viewsonic gtab and I HATE the splash screen - would love to see it supported. My 2c... great tool! Thanks!
Click to expand...
Click to collapse
great, this seems to be popular. i have been looking into this and will keep you updated! i hope to get support added for this soon!
for you
hi joeykrim. you do good work man.
attatched is 3 things.
1.flash_image binary for the Epic 4g SPH-D700
2.redband_ua, the method we use to flash kernels
3.zImage, i compiled from source and use
we run on EXT4 mostly these days
I and a few other developers use a scripting process to flash kernels without recovery. if want these pm me.
joeykrim said:
perfect! recovery image support should be simple.
kernel flashing methods seem to vary quite a bit between devices. could you post links up to two/three popular kernels so i can see the format they're using?
great question! i hope to get this supported within the next week as ill be on my honeymoon the next 5 days w/o internet...i know, tough but worth it
if you have the information handy, could you post links to two/three top kernels so I can examine their format?
Click to expand...
Click to collapse
Here are some links to some popular kernels on the Epic-
http://forum.xda-developers.com/showthread.php?t=961614
http://forum.xda-developers.com/showthread.php?t=976197
Congrats and have fun on your Honeymoon.
can i use this with my samsung galaxy apollo????
yea joeykrim!!! i just saw the release! \o/
congrats, buddy!!
Looks like an awesome utility
Support for HTC Desire would be perfect, as i can't seem to get fastboot working, so i'm stuck with Clockworkmod 2.5.1.8 at the moment..
I'm not sure how to get the flash_image file, is it the one contained in /system/bin?
Kernel links:
AOSP - http://forum.xda-developers.com/showthread.php?t=782875&highlight=vork
AOSP - http://forum.xda-developers.com/showthread.php?t=1031909
Sense - http://forum.xda-developers.com/showthread.php?t=849002
Sense - http://forum.xda-developers.com/showthread.php?t=801915&highlight=vork
Stock ROM support
Will this work on galaxy S stock ROM...or do I need to have a third party ROM installed. Most of the other flashing softwares do not support the stock ROM and I hope this is not amongst them.
mattallica76 said:
Here are some links to some popular kernels on the Epic-
http://forum.xda-developers.com/showthread.php?t=961614
http://forum.xda-developers.com/showthread.php?t=976197
Congrats and have fun on your Honeymoon.
Click to expand...
Click to collapse
released an update - version 1.0.3 - supports kernel flashing on Samsung Epic!
tested recovery flashing on the Samsung Epic but it seems too unstable to support
thanks to DRockstar, skeeterslint and MeatMcBadass for testing and feedback!
links in OP updated with new version!
Released version 1.0.5 - Fixing a few minor bugs
** Updated boot logo flashing support on S3C6410 series devices (moment, transform, intercept and acclaim)
** Cleaned up code on the back end for efficiency
** Clarified wording in the prompts
Links in OP have updated versions! Thanks for all the support!
SU Access
Hey I could really use some help, I rooted my Samsung Moment yesterday using the Z4Root program yesterday, but when I try to use Flash Image_GUI I get the following error:
"Root Access Denied
This device has not granted root access to this application. Please root this device to allow this application root access. This application can not run without root access. Sorry!"
Can anyone please help me? I did root the phone accurately, I have the SU icon, but this app (flash image) won't open for me...
WDeamz said:
Hey I could really use some help, I rooted my Samsung Moment yesterday using the Z4Root program yesterday, but when I try to use Flash Image_GUI I get the following error:
"Root Access Denied
This device has not granted root access to this application. Please root this device to allow this application root access. This application can not run without root access. Sorry!"
Can anyone please help me? I did root the phone accurately, I have the SU icon, but this app (flash image) won't open for me...
Click to expand...
Click to collapse
After reading through the z4root thread,
http://forum.xda-developers.com/showthread.php?t=833953 , it appears they install the superuser.apk after rooting.
After you run z4root, and it is a permanent root, I would reboot the device to make sure the SuperUser apk appears in the app draw/tray.
After you can confirm z4root gave you permanent root and installed the superuser apk, then install my app. When you first open my app, the SuperUser app should ask whether or not you want to grant my app root access.
If you've already said no, you can open the SuperUser app from the app draw/tray and change your preference. My application will require root access to run properly.
If you don't see the superuser app in your app draw/tray it would seem z4root did not work properly.
Hope this helps!
Thanks for getting back to me
Hey I appreciate the fast reply, I uninstalled your app and re-installed it, but unfortunately I am still getting the same error. SU is on the tray, but I get no option to allow root for your app...any help you could give me is really, really, appreciated.
PLEASE READ THIS FULL POST BEFORE FLASHING
I continue to put a lot of effort into making this post to help YOU so please help YOURSELF by reading it all!
If this solves your problem please consider donating as I continue to put a lot of effort into keeping this current and up-to-date! Thank you!
These instructions should fix your semi-bricked or broken phone as long as you can get it into download mode. Make sure you have drivers already installed on your Windows computer before starting.
A NON-STOCK microUSB CABLE IS REQUIRED AS STOCK FAILS THE MAJORITY OF THE TIME
If you need drivers or the ones you have don't work you can use these:
32-bit drivers 64-bit drivers
Things you will need to restore your phone are below.
BY PERFORMING THESE STEPS ALL DATA ON YOUR PHONE WILL BE WIPED AND IT WILL BE RESTORED TO FACTORY STATE. I ASSUME NO RESPONSIBILITY IF THIS DAMAGES YOUR PHONE OR DOESN'T FIX IT. DO AT YOUR OWN RISK
A Windows Machine is required for using Odin. If you don't have a Windows machine see second post.
Download and use this version of Odin: Odin 1.85 and pit file Thanks to iNsAn|tY for hosting1
Download this tar: SPH-D700-EL30-8Gb-REL.tar.md5 Provided by K0nane
Mirror 2 Provided by iNsAn|tY
or
SPH-D700-FC09-8Gb-REL.tar hosted by kennyg123
MD5 sum:6426b89638df4e3dcf6e19b8f79cdcf0
Set up the software:
Extract the Odin3 v1.85.zip
Run odin3 v1.85.exe
Make sure the following boxes are checked (they should already be checked):
Re-Partiton, Auto-reboot, F. Reset Time
Click PIT and select the victory_8G_100528.pit that you extracted from the Odin zip.
Click PDA and select SPH-D700-EL30-8Gb-REL.tar.md5
Put your phone in Download Mode:
Make sure the USB cord is unplugged
Remove the battery and microSD card
Plug the phone into Computer (the phone may display a battery on the display this is normal just ignore it and go to the next step)
Hold down the "1" key and the power button.
The phone should now be displaying a Yellow Triangle with Downloading... (see end of post for image of download mode)
Under ID:COM, the box should turn yellow and contain the com port. If it doesn't see Troubleshooting at the end.
Odin should now look like this (screenshot shows EB13 but is the same for EL30):
{
"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"
}
Full-size Image
Now you should be able to click Start.
Your phone should try and auto-reboot when finished.
The phone can't boot normally without the battery but you can safely unplug it from the computer install the battery and turn it on.
You phone should be working 100%!
This has worked on numerous phone that have partition issues, intermittent booting issues, and many other file system issues. This also fixes the Samsung Logo disappearing from boot.
While some people claim that the re-partition and time reset should not be checked, this guide is designed to fix ALL problems. While using Odin on your phone has some inherent risk and is slightly less risky to not re-partition the phone some phones will not be fixed without this and that's why it is included. You can try following the above steps and only checking "reboot" but you may have to reflash and check the boxes in the instructions if you phone still has problems.
Troubleshooting:
Phone not getting in download mode
While holding down 1 and power insert the battery before trying to connect the USB cableOdin isn't detecting the phone?!
Try a different USB PORT on the computer.
Normally only the USB port the drivers were installed to and the phone was plugged into when they were installed will work (easily anyway)Try a different USB cable
If you are using the stock cable it is almost certainly NOT going to work. You can get a cheap BlackBerry USB cable off of Amazon for a couple bucks and works like a charm.Uninstall the drivers, reboot, and reinstall the driversTry Odin v1.61It seems frozen and hasn't made any progress for 15 minutes
factoryfs.rfs takes awhile but if it stays on that for longer than 15 minutes unplug the phone and start overIt started flashing but part way through the download mode screen went away and it just shows a color (can be different colors each time)
This means that it got disconnected during the transfer. Try again if that doesn't work try a different USB cable.You get a big red failed and tried the above steps.
Before you try to reflash make sure to copy the log that Odin makes in the bottom left hand portion of the screen so we can help you troubleshoot and then post in this thread.Still not working?
Try this tar SPH-D700-EC05-8Gb-REL.tar provided by K0nane
Here is a picture of Download Mode if you aren't sure what it looks like:
This has worked on all phones that were able to get into download mode. If this works for you or if you have issues let me know! You can message me on Irondust formerly Fossnet in #epic my nickname there is Cyc
Click here to chat with me in IRC
Special thanks to K0nane and iNsAn|tY hosting and providing the EL30 tar and Odin.
Even though there are other guides how to do this I wanted something that was a little more concise and easier to follow. If you prefer qbking77 made a How-To Video to restore your phone. He uses different files and such but the end result is hopefully the same so check that out if you prefer or if you are confused and want to see the steps.
Forum Post for other How-ToVideos by qbking77
May need this again but can't remember the URL NO PROBLEM http://tinyurl.com/epicfix directs here!
Heimdall Section for users having trouble with Odin or do not have Windows PC will be added shortly. Below is mordant23's post that I am putting here in the mean time. My post will feature the gui as the main interface and give options for all supported operating systems. Until then thank you mordant23 for allowing me to use this in the opener:
mordant23 said:
I had to flash back to stock after I switched to Linux. I couldn't find an easy guide. In case this helps someone else, below are the steps I took. If this is useful, could this be added to the original post or would it be better if I start a new thread?
The steps should be adaptable to OS X, but since I don't use OS X I can't really write instructions with confidence. Perhaps someone else can?
Note: Everyone's linux distributions are different. For the instructions I'll use generalized descriptions of steps. The only specific instructions I'll give is for using Heimdall. I am not a linux guru nor am I an Epic 4G expert. The only wisdom I have is 42 is the answer to life, the universe, and everything else.
The steps are pretty easy. I'll give more detailed explanation afterwards.
0. Download tar and pit files listed in the original post
1. Install Heimdall
2. Understand how Heimdall linux process differs from Odin windows process
3. Boot phone into download mode and connect to computer
4. Push files to phone with Heimdall
Step 0: Download tar and pit files
Pretty simple. Unpack those bad boys. Put them all into one folder nice and cozy neat like. That's right. The pit, modem, and completely unzipped files all in one folder.
Step 1: Heimdall is your friend
There is no Odin without Windows. We must turn to another Norse god, Heimdall to help us out. Heimdall is an open source project to replace Odin. There are ports to Windows and Mac OS X. The Epic 4G is not officially supported but many people have used it with no problem. I personally used linux mint 11 with an almost bricked phone with no problem. Use at your own risk.
Install Heimdall
The latest version at this time is a command line only version 1.2.0. The GUI for previous version 1.1.1 looks easy enough if you want to use them, although according to reports it may not work as well as command line. For the instructions I'll use the command line because I think it makes it easier to understand how to match files up to the different fields.
Since your linux distros are different, I will not go into any specifics on how to install.
Step 2: Understand how Heimdall differs from Odin
Difference 1: Don't need no stinkin' Samsung drivers (unless you're using Heimdall in Windows). "But what about those drivers..." Zip it! You don't need 'em.
Difference 2: Unpack the tarball and unzip the pit. The individual files in the tar, the pit file, and the modem.bin file should all be in one folder. The major difference with Heimdall and Odin is that with Heimdall, you specify how the files match the partitions. In some respects this is easier because if you don't need to repartition, or if you only need to push a particular file, e.g. the modem, you can do that. The trick with the command line is to know which files match the command line switches, e.g. --modem modem.bin, --factoryfs factoryfs.rfs, etc.
Step 3: Boot phone in download mode and connect to computer
Open up keyboard and hold 1 while hitting power.
Connect phone to computer.
Step 4: Push files to phone
Open terminal window in the directory with all the files. Use cd if necessary to get to the folder.
The general structure for the heimdall command is:
Specifically for the SPH-D700-EC05-8gb-REL.tar and victory_8G_100528.pit listed in the original post on this thread:
Capitalization is important. I don't know how many times I messed up because I didn't type Sbl.bin with a capital "S".
If you use the gui, just make sure you specify which files go in which fields. I don't have the gui front end so I have not tested it, but it looks simple enough.
If everything works, then you'll see the progress as heimdell copies everything. If something is not right, then you'll get an error message.
Heimdall reboots the phone when it's done.
Please let me know what you think. Suggestions always welcome.
Sources:
http://www.glassechidna.com.au/products/heimdall/
http://wmarkito.wordpress.com/2011/02/11/flashing-android-froyo-in-a-galaxy-s-with-ubuntu-and-heimdall/
Click to expand...
Click to collapse
Important to note this will take a very long time I've been sitting waiting for mine to finish for a while. Been about 30 minutes and still not done.
krisman said:
Important to note this will take a very long time I've been sitting waiting for mine to finish for a while. Been about 30 minutes and still not done.
Click to expand...
Click to collapse
What is it saying? It shouldn't take that long. Do you see the blue progress bar on your phone?
I was going to mention that it froze once when I was trying to do it and I just unplugged my phone and took out the battery and restarted and it went through.
You can chat with me on Fossnet
http://webirc.fossnet.info/?channels=epic
Just say my name "Cyc" in channel and I will respond.
dyehya said:
What is it saying? It shouldn't take that long. Do you see the blue progress bar on your phone?
I was going to mention that it froze once when I was trying to do it and I just unplugged my phone and took out the battery and restarted and it went through.
Click to expand...
Click to collapse
Yea still has the blue progress bar odin says factoryfs. I actually thought it might be frozen. But i started to ask how long it would take and it jumped forward some more. And now it just finished as I'm typing this. Which it won't boot stuck on the samsung boot screen just keeps vibrating gonna try again.
krisman said:
Yea still has the blue progress bar odin says factoryfs. I actually thought it might be frozen. But i started to ask how long it would take and it jumped forward some more. And now it just finished as I'm typing this. Which it won't boot stuck on the samsung boot screen just keeps vibrating gonna try again.
Click to expand...
Click to collapse
Yeah try again. It takes a few minutes of factoryfs due to it pushing 258MB to the phone but shouldn't have taken 30 minutes.
Now this can't fix your phone if it has hardware problems but should fix everything else. Let me know how it goes. My problem with it freezing was before it started push stuff to the phone.
The only other thing I could think of and didn't even question was your computer using a USB 2.0 port. That's the only reason I could see it taking so long to transfer data to the phone if it was Using usb 1.0 or 1.1
Finally gave up on eb13 after redownloading the tarball and still not getting anything. Tried a di18 tar and it worked first try. Trying to odin from there to eb13 seems to be slow flash and then not working right still.
krisman said:
Finally gave up on eb13 after redownloading the tarball and still not getting anything. Tried a di18 tar and it worked first try. Trying to odin from there to eb13 seems to be slow flash and then not working right still.
Click to expand...
Click to collapse
IF DI18 works you can let it OTA update to EC05 the same way EB13 would. I used EB13 because there is no OFFICIAL EC05 tar available presently but any of the full tars should work. Any reason you are trying to tar to EB13 in particular if you got DI18 working?
I don't remember where I downloaded EB13 from I just looked for a link when I was posting this How-To. You might want to try finding an EB13 tar from another source and see if that resolves the issue or redownload the EB13 tar. My EB13 tar has an md5 of b9b14611dcde5fbe586fdc242315b92b and I know it works on my Epic. You can use HashCalc or some other program to calculate the EB13 hash.
I updated the EB13 tar link in my original post. You may have to refresh your browser to see it http://www.multiupload.com/3YPCROH00T
You can try that.
No reason in particular for wanting to go to eb13 just thought it strange that it wouldn't work and wanted to keep trying.
Sent from my SPH-D700 using XDA App
krisman said:
No reason in particular for wanting to go to eb13 just thought it strange that it wouldn't work and wanted to keep trying.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I appreciate you trying. If you want you can try the new link of EB13 I posted and see if that works. I am downloading it now myself to see if the hash check matches what I have or not.
I made a video showing how to do this. You might want to link it in the OP:
http://www.youtube.com/watch?v=YQ2g6J1JgjU
Also, a link to my other how to video thread:
http://forum.xda-developers.com/showthread.php?t=1009997
Oh and just for future reference, a post like this doesn't belong in the development section. It goes in to the general section.
Yeah I am going ask impaler to move it for me b/c I didn't mean to post it in dev just had a few too many windows going when I was putting it together. Thanks for the video link I'll add to OP with credit of course
I verified the new link has the correct md5 so it should work.
Very good directions.... should be added to the Other thread we have about ODIN though...
This will also bring back your samsung logo if you repaired your epic after a visionkernel brick but lost the samsung logo..
Sent from my SPH-D700 using XDA App
This thread sponsored by k0nane.info.
@DYEHYA
IM having my first issue with my epic .. SEMI BRICK ... i see in ur picture of ODIN n description u have everything checked but from video n past ODIN tries ive only had reboot checked is this only for semi bricked or should i do what i know worked from previous odin use and that is only keep the auto reboot checked ....
djgallis said:
and that is only keep the auto reboot checked ....
Click to expand...
Click to collapse
I would suggest you continue as you have been - check ONLY 'auto reboot'.
k0nane said:
I would suggest you continue as you have been - check ONLY 'auto reboot'.
Click to expand...
Click to collapse
thank you will do ..
{
"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"
}
Okay, I'm tired of seeing people not be able to get on the GB ext4 bandwagon where apps don't disappear. This guide is for you if you want a smooth, surefire way to get on GB.
NOTES
* The KC1 and KJ6 files contain bootloaders for the SGH-T959V. By downloading and flashing the files you agree that you will not hold me or anyone in Team Acid responsible if your device gets bricked. There are always risks when flashing custom firmware and ROMs onto your phone.
* As always, make a full backup of your SD card and phone.
FEATURES
* Root
* CWM + drhonk's custom KJ1 kernel preinstalled.
* Gets rid of the disappearing apps problem
* Gets rid of the missing SD card once you're booted into GB
* Gets rid of your bootloops
* Get a working GB ROM with ext4 support (includes Official KJ6 with drhonk's custom KJ1 + cwm kernel)
* All the files you need are included in this post
* Wipes out all the gremlins you had on your phone by putting the KC1 bootloaders, then the KJ6 bootloaders on your phone.
PREREQUISITES
1) Download all the files from the links on this post, and extract both .7z files and Odin v1.85 using 7-zip or a compatible program
2) Leave the phone's back cover off since you're gonna have to do a few battery pulls and you need access to the sd card
3) Format your sd card by hooking it up to your computer with an sd adapter or through mass storage mode using your phone and a USB cable.
FORMATTING ERASES EVERYTHING ON YOUR SD CARD. MAKE SURE YOU BACK IT UP ONTO YOUR COMPUTER BEFORE YOU DO THIS.
Follow this guide to format your sd card on Windows (this is on XP but the same steps can be taken on Vista or 7).
This guide is meant for using your sd card on a Wii, but the process is the same to get it working on the phone.
WATCH THE VIDEO ALL THE WAY TROUGH BEFORE ATTEMPTING ANY OF THIS.
http://www.youtube.com/watch?v=l5fxOKdmmv8
Click on the link above if you wanna watch fullscreen, or you can watch here it here:
INSTRUCTIONS
1) After formatting the SD card with the steps above, put your favorite GB ROM, and install_busybox.zip onto the SD card
- 1a) You can restore any backup of your SD card you made at this point. Make sure you have at least 2GB free on the card though!
2) Put your phone into download mode
3) Open Odin on your computer
4) Load up Odin, and load the KC1 files, DON'T TOUCH ANY OTHER OPTIONS, leave them like they are even if Odin changes them!
- 4a) PIT: Sgs4g.pit
- 4b) PDA: pda.tar.md5
5) Flash and let the phone reboot. Once you see the T-Mo startup screen (the pink one), OR the CWM (red text) screen do a battery pull.
6) Put your phone back into download mode
7) Click reset in Odin, now load up the KJ6 files
- 7a) PDA: pda.tar.md5
- 7b) CSC: csc.tar.md5
8) Flash the files and let the phone reboot.
- 8a) The phone will go into standard recovery (blue and yellow letters, you might hear Linda) and then reboot itself once.
- 8b) The 2nd time you will see either the CWM red letter screen or the Galaxy S 4G white letters/pink splash screen and if you prefer you can let the phone boot all the way, do a battery pull.
9) Now unplug the USB cable, put the battery back in, hold vol + and -, then press power. You should boot into CWM (red letters, voodoo).
10) Go into the voodoo menu > enable lagfix and /system lagfix on
11) Flash the GB rom you put on your sd card
12) Flash the busybox_installer.zip
13) Reboot and hear Linda give her speech.
14) Welcome to GB with ext4!
CREDITS
For helping me expand my knowledge:
krylon360
whitehawkx
drhonk
chadster214
golmar88
Team Acid
raverx3x for the CSC flashing trick that fixes the missing apps problems and for the KC1 and KJ6 builds
dsexton702 for his countless guides which help me build mine.
The helpful members of this community
TESTIMONIALS
Lawful123 said:
It was all a blur. I followed your steps and all I remember was some cable and talking to the ruler of Asgard then their was a crazy battery pull then back to Asgard and then i had a one way conversation with some fembot named linda and it all ended with me having gingerbread.
Thanks for the help.
Click to expand...
Click to collapse
CHANGELOG
Nov 24, 2011
Updated the guide and files for the official KJ6 GB release. Now you get Raver's KJ6 ROM plus drhonk's KJ1 kernel + voodoo.
Sep 27, 2011
Changed the formatting and added a youtube video link on how to format your sd card from your computer instead of CWM.
Aug 18, 2011
Initial release
Click to expand...
Click to collapse
LINKS
7-zip
Odin3 v1.85.zip
install_busybox.zip
fb_kc1_bootloaders_cwm.7z
fb_kj6_official_kj1_kernel.7z
I can say this is pretty much what I followed and had only one other change. Many of us have had to create a 2048 partition on the SD card to make it work, 1024 just wouldn't work for some of us.
shotchacokov said:
I can say this is pretty much what I followed and had only one other change. Many of us have had to create a 2048 partition on the SD card to make it work, 1024 just wouldn't work for some of us.
Click to expand...
Click to collapse
Word
Sent from my SGH-T959V using XDA Premium App
Changed
Sent from my awesome SGS4G
I currently have:
Modem: T959VIKH2
Kernel: 2.6.35-T959VUVKG4-CL3585158
Rom:T959VUVKG4 odin
Linda will not speak. Will the above work for my Rom?
It might be overkill for you, but yes it'll work as long as you have a properly formatted sd card.
Just know that this will wipe everything on your phone so look for a CWM gingerbread rom. There's a few good ones right now. I'm using audiophile ftw
Sent from my awesome SGS4G
Your going to get a few questions for the people who were on the leaked first version of GB with the jacked bootloaders - So I was thinking you might want to add How to get back to a proper Froyo version like KD1 in your post.... .Kc1 for some reason didnt work for me - and I somewhat know what Im doing...lol....Im just saying tho.... happened to me...
FBis251 said:
It might be overkill for you, but yes it'll work as long as you have a properly formatted sd card.
Just know that this will wipe everything on your phone so look for a CWM gingerbread rom. There's a few good ones right now. I'm using audiophile ftw
Sent from my awesome SGS4G
Click to expand...
Click to collapse
Thank you!
I thought the partition was 1024
Sent from my SGH-T959V using XDA Premium App
Thnaks
Sent from my SGH-T959V using XDA Premium App
I use a process very similar to this when flashing a new GB ROM, excellent write up! Only difference is I use the old 8gb sdcard from my old MT3G with a 2gb partition on it, works every time! I just don't feel comfortable resizing my normal 16gb sdcard in case something goes wrong, or the card gets wiped.
Sent from my SGH-T959V using XDA Premium App
Cheffz said:
Your going to get a few questions for the people who were on the leaked first version of GB with the jacked bootloaders - So I was thinking you might want to add How to get back to a proper Froyo version like KD1 in your post.... .Kc1 for some reason didnt work for me - and I somewhat know what Im doing...lol....Im just saying tho.... happened to me...
Click to expand...
Click to collapse
This will actually revert you back to a full KC1 with bootloaders, wiping the GB bootloaders that were bad, then it puts you on the KH2 bootloaders which I haven't had any trouble with and haven't heard anyone complain about. That's why I wrote this guide, this is all working.
makavelicruz said:
I thought the partition was 1024
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
As crackpot and others have mentioned, 2048 might actually work best for you. If you formatted to 1024 and it worked, stick with it, the point is to get a method working for you that works every time.
FBis251 said:
This will actually revert you back to a full KC1 with bootloaders, wiping the GB bootloaders that were bad, then it puts you on the KH2 bootloaders which I haven't had any trouble with and haven't heard anyone complain about. That's why I wrote this guide, this is all working.
As crackpot and others have mentioned, 2048 might actually work best for you. If you formatted to 1024 and it worked, stick with it, the point is to get a method working for you that works every time.
Click to expand...
Click to collapse
very well, thank you sir
i done everything .... installed kh2 with crt but when i open voodoo there is no lagfix ....
I tried this thing for 5 hours and just gave up. Raver posted a new Redux v. Lol I am not sure where I got lost in the OP but after several tries I couldn't flash a GB. Bricked my phone very ugly. Will give it a try when a final GB is out. Anyway, thanks for the help. I know its just my noobness.
Sent from my SGH-T959V using XDA App
Well you can always send us PM's or try to contact us if you ever get stuck, you don't have to try to solve problems on your own. If you are willing to try it again, and I recommend you do because it'll get rid of a lot of problems, feel free to send me a message.
I've tried your guide twice, I end up with a stock recovery and no ext4. I heard Linda talk both times after ODIN, but no dice
I'm trying to use this ROM: [ROM-Leak][CWM] Gingerbread 2.3.4 T959VUVKH2 Deodexed + CRT On and Off Enabled! by chadster
Acctttuuuaaalllyyy I just tried flashing drhonk's GB kernel with voodoo via ODIN. Got it! Linda is converting now.
I got something I've never seen before.
At step 8 (not a or b), I let the phone reboot and I hear linda say "convert data partition", then I see the android + install package screen blip by, and now I'm at a screen that says "Confirm password" and a low res touch ui for entering a would be confirmed password... wtf?!?
I'll start over and try again, but in case I get back to this point, has anyone ever seen this?
You must've used a password instead of a pattern for your lockscreen. Try typing in anything and press enter.
Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have is, "Why did you release this - why wouldn't I just use <insert name here>'s stock rom?" It's simple: every other rom in this forum (at this time) has been modified from the original stock rom - whether they've added root, de-odexed it, debloated it, or otherwise. Because the Unadulterated rom is 100% stock (with stock kernel), it is possible for other developers to flash this rom and use it as a platform for attempting to find a root method for the MF3 users out there already. Plus, I like to make my own modifications from a stock base.
UPDATE (8-1-13): a root method has been found for MF3. See thread here. This ROM's purpose has been fulfilled, but your are still welcome to use it, of course!
UPDATE: The MF3 Odin files have been uploaded by @Shockndrop over in his thread here. Remember that the Odin files will flash your bootloader to MF3 (if you allow them), so be careful out there.
Rest assured, this rom will not update your bootloaders, it will not break your custom recovery, and it won't flash your modems. Like most roms, it will simply replace your /system and flash a Kernel. It's also scripted to wipe cache and dalvik for you. It will not wipe your /data partition - you might want to do so if you run into problems, especially when coming from other roms.
Next, you might ask, "How can you say this is 100% stock? How did you construct it?" I'll hide nothing from you - you can build it yourself if you'd like. Here's how I did it:
Rooted with motochopper
Installed TWRP 2.6.0.0
Wiped data & cache
Odin to MDL stock
Allow one full reboot:
Boot script runs (installs CSC - this is REQUIRED for the MF3 update to patch correctly)
Clears up any SysScope flags, etc. that may have persisted from previous rom or root.
"Temporary Root" using motochopper:
Code:
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
NOTE: Possible outcomes of temporary root:
Failure
Success, motochopper exploit hangs, device spontaneously reboots
Success, immediate return to prompt, but adb shell is still not root (indicated by $ prompt)
Success, immediate return to prompt, adb shell is root (indicated by # prompt)
Repeat as needed (usually only twice or so?)
NOTE: Don't both trying to run su. It isn't installed. We're just relying on motochopper to give us a temporary adb root shell.
From adb root shell, installed TWRP recovery:
Code:
dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
Rebooted, checked to be sure system status is still Official. Note that at this point, we've got a 100% stock MDL rom, without root, but with a custom recovery. Woot.
Rebooted into TWRP, installed custom-neutered OTA update (mf3-sys-only.zip), which only does the following:
Verifies all system files
Removes "unneeded" files (as determined by AT&T, not me)
Patches files
Copies new files
Sets permissions
Patches build.prop
Wiped data & cache for good measure
Booted phone, verified ROM works okay, system status = official. Rebooted, checked Odin Mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Booted back to TWRP to begin pulling dumps
... Now, on to the good stuff!
ROM Install Instructions:
Download mf3-stock-rom.zip and place it on your internal sdcard.
Make a nandroid backup of your existing system, data, cache, and anything else you deem important (everything!).
Flash/install the zip using your favorite custom recovery. This part should take several minutes - the file is huge!
Optionally, flash any additional Add-ons that you want (e.g. SuperSU for root)
Optionally, flash a custom kernel (use instructions from the kernel's author!). Note that some custom kernels will need you to flash Loki-Doki. The included kernel does not require Loki patching! It is 100% stock, and your system will accept it as-is.
Optionally, wipe /data. You can skip this, but if you get a ton of force-closes or extreme problems, this would be one of the first troubleshooting steps.
Reboot, and enjoy!
Click to expand...
Click to collapse
Important Recommendation:
You are advised to disable the OTA update applications! If AT&T/Samsung release a new OTA update (beyond MF3), it is theoretically possible to download and install it while using this rom! Accepting such an update could do just as much damage as the original MF3 update did. You can easily disable OTA updates from a root ADB shell using the following commands:
Code:
pm disable com.wssyncmldm
pm disable com.LocalFota
pm disable com.sec.android.fwupgrade
You could also use Titanium Backup Pro to accomplish the same thing. I will later look into the possibility of disabling these using a flashable Add-on zip that otherwise keeps your system as stock as possible.
Known Bugs:
If you do not flash a custom kernel, you will lose WiFi. The WiFi in the MF3 Kernel is expecting the MF3 bootloaders, which we aren't flashing. Therefore it breaks.
If you happen to have the MF3 modem/baseband installed, your WiFi might work, but your sound may stop working completely. This is also a result of not having MF3 bootloaders. A custom Kernel should fix this too.
If you use the "remove-SysScope" Add-on, be careful of any other mods that may poke around with SecSettings.apk - these are rare, but there's some risk of conflict here.
With the custom kernel I installed, I frequently received the "The device has detected an application attempting..." message. This can be pinpointed to the KNOX agent, and can be fixed a different ways (your choice!):
I found this post to be very helpful.
You can also try using the command pm disable com.sec.knox.seandroid from a root ADB shell. This just freezes the app. Personally, I used this method.
@jeboo also mentioned that the KNOXAgent.apk can be patched using smali/baksmali. Check out his post about it.
Also with the kernel I installed, there was a bug regarding updating the camera firmware. I was forced to restore the stock kernel temporarily, open the camera app to update the camera firmware, and then re-flash the custom kernel. The original MF3 kernel is included in the Add-ons.
Any other bugs are likely straight from AT&T/Samsung, otherwise they could be from your custom kernel, if you flashed one.
Be sure to make good backups of everything, and be prepared to use Odin back to stock. One member has reported that after flashing away from this rom to any other rom/kernel, their SIM card would not work until they used Odin to return to stock. After Odin, it worked fine.
It seems most custom kernels are expecting you to have an MDL baseband. Some people are reporting strange issues (such as problems with video streaming) when using MF3 modems and their choice of custom kernels. Check out File #11 for various modems, NON-HLOS modems, and kernels.
Custom Kernels:
Here's a list of custom kernels that are known-working with this rom. Please feel free to test and report other working kernels, and I will gladly add them to the list!
@jeboo's Kernel - built for @shoman94's SHOstock rom. Available in post #3 of their thread.
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me. It appears that the kernels in their thread require Loki-Doki to be flashed after flashing the kernels. However, the one that I downloaded came from here: http://d-h.st/WVs and it was pre-patched for the I337.
@Jamison904's Infamous Kernel works really well, it seems. It also has BusyBox v1.19.3. I'm currently using v4.0, but there are newer versions available on his Dev-Host folder. These are for the M919, so flash Loki-Doki afterwards if you're on I337!
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
File #1 - mf3-stock-rom.zip - CWM/TWRP-Flashable ROM .zip file - created by hand (you are welcome to dissect it if you'd like - take a look inside the updater-script)
Files #2-#7 (individual image files and odin-flashables):
File #2 - system.img.ext4 - EXT4 format copy of the System partition - pulled using make_ext4fs in TWRP:
Used fdisk to obtain partition size:
Code:
# fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
Dumped the partition:
Code:
# make_ext4fs -s -l 2894069760 -a system /sdcard/system.img.ext4 /system
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 3192/176704 inodes and 584765/706560 blocks
File #3 - system.img - Binary copy of the System Partition - pulled using dd:
This was much easier to create:
Code:
# dd if=/dev/block/mmcblk0p16 of=/sdcard/system.img bs=4096
File #4 - boot.img - Kernel - pulled from the OTA update file
File #5 - mf3-sys-boot.tar.md5 - "Odin-flashable" tarball - created without any modification:
Using a Linux PC or Cygwin, executed the following:
Code:
$ tar -H ustar -c system.img.ext4 boot.img > mf3-sys-boot.tar
$ md5sum -t mf3-sys-boot.tar >> mf3-sys-boot.tar
$ mv mf3-sys-boot.tar mf3-sys-boot.tar.md5
File #6 - mf3-sys-boot-sgs4ext4fs.tar.md5 - "Odin-flashable" tarball - "bloated" with Chainfire's sgs4ext4fs
Using a Linux PC (I used Ubuntu 13.04 64bit - couldn't get the win32 version to process the file entirely):
Code:
$ mv ./sgs4ext4fs.linux.amd64 ./sgs4ext4fs
$ sudo chmod 755 ./sgs4ext4fs
$ mv system.img.ext4 system.img.ext4.orig
$ ./sgs4ext4fs --bloat system.img.ext4.orig system.img.ext4
Optionally, you can use the "--list" option to view the file before and after the bloating. Once complete, pack it up in a tarball again.
File #7 - mf3-factoryfs.tar.md5 - "Odin-flashable" tarball - created using the system.img instead:
Using a Linux PC or Cygwin, executed the following:
Code:
$ mv system.img factoryfs.img
$ tar -H ustar -c factoryfs.img boot.img > mf3-factoryfs.tar
$ md5sum -t mf3-factoryfs.tar >> mf3-factoryfs.tar
$ mv mf3-factoryfs.tar mf3-factoryfs.tar.md5
Files #8-#11 (Add-ons!):
File #8 - UPDATE-SuperSU-v1.41.zip - ROOT! Flash this to root your new MF3 rom!
Original is found on Chainfire's website.
File #9 - remove-SysScope.zip - Want to stay "Official", even though you rooted? Flash this! It will remove SysScope and customize your SecSettings.apk to not check for SysScope anymore. Must be flashed before first boot, otherwise you'll just be stuck with a "custom" status until you remove it by some other means.
File #10 - mf3-kernel-only.zip - Want to quickly flash back to the MF3 stock Kernel again? Flash this. No need to use Loki-Doki after flashing this - the I337 will accept this just fine and boot.
File #11 - all-kernel-modem-apnhlos.zip - My personal collection of flashable .zip's of all available versions of the stock kernel, stock modem, and stock NON-HLOS modem for the I337 - including MDB, MDL, MF3. Unzip this file first, and flash individual partitions/versions in whatever combination you want.
Disclaimers, etc.:
I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other devices, I can't guarantee anything!
You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.
If you appreciate my work, please use the THANKS button below to let me know!
reserved...
First .. ..... Hey guess u got ur phone up and running huh ?
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
as expected...
Aou said:
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have
.......
[*]I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other device, I can't guarantee anything!
[*]You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
[*]I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.[/list]
If you appreciate my work, please use the THANKS button below to let me know!
Click to expand...
Click to collapse
The result was what was expected.
Keeping my fingers crossed for other solutions...
iB4STiD said:
First .. ..... Hey guess u got ur phone up and running huh ?
Click to expand...
Click to collapse
Nope! Ended up needing to replace it, unfortunately. The original is a 100% hard brick. It won't even take the MF3 firmware via JTAG.
jeboo said:
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
Click to expand...
Click to collapse
Awesome - thanks! I'll add that to the list of options. Also, thanks again for your awesome Kernel. v1.4 is exactly what I need for my phone.
SaltyFoam said:
The result was what was expected.
Keeping my fingers crossed for other solutions...
Click to expand...
Click to collapse
This is really unfortunate, but somewhat expected (as you've said). Have you tried the Odin-flooding again (even with the MDL or MF3 Recovery) yet? That was a very interesting accidental discovery you made. I'm going to have to try that myself too! It might have been a fluke, but still worth investigating.
As an update: The last file (mf3-factoryfs.tar.md5) has finished uploading, so I'm adding the link to the OP now.
FINALLY, someone else that respects untouched firmware. Glad to see this.
The odin flooding is not working at this point.
apparently one of the features of the new odin mode (aboot?) is that once it gets the 'failed auth' it stops responding to further pushes. It does not even allow the connection to be setup until a power down and restart.
As you can see in the other thread I submitted a warranty claim and they are replacing the device: as I have no backup device and a family that needs to get in touch with me (i.e. my wife and mother scolding me for not having a phone) I ran out of time...
I still have a few days with the old device before the replacement arrives...
I any case I am off to work.
If anyone wants to help create a flashable-zip that would disable the OTA updates without touching /system, I'm working on it here:
http://forum.xda-developers.com/showthread.php?t=2379517
I just need someone to write something up in a bash script that will make modifications to a file in /data. Should work without rooting the system.
Jah0n said:
FINALLY, someone else that respects untouched firmware. Glad to see this.
Click to expand...
Click to collapse
One thing I've seen in many "stock" roms is: "Completely stock, except for this.... and this.... and this mod I made here.... and this...."
-_-
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
mocsab said:
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
Click to expand...
Click to collapse
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Jah0n said:
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
Click to expand...
Click to collapse
Awesome! If the kernel turns out alright, we could add it to the list in the OP.
Aou said:
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Click to expand...
Click to collapse
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
mocsab said:
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
Click to expand...
Click to collapse
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Aou said:
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Click to expand...
Click to collapse
The kernel lies in a separate partition but twrp wipes it away by default so you'd have to unmount the boot partition
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Is boot.img a compressed file?
jortex said:
Is boot.img a compressed file?
Click to expand...
Click to collapse
I did not compress it at all. However it is not a full 10MB either. It's the exact file that came from the MF3 update package. The way that the OTA update .zip installs it is by doing this:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
If you need a full 10MB partition dump (i.e. using dd or a nandroid), I can upload those if you need them for any reason.
UPDATE: I just did a binary comparison of the boot.img that came from the OTA .zip (the one I uploaded), and a nandroid backup I made. It was 100% identical, except the nandroid was padded with zeros at the end (a couple megabytes of zeros...)
Added another kernel to the list:
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me.
Hi
Here is the way i used to flash the firmware, i advise to backup all your data before the flash.
All the files here are provided without any waranty.
Flash at your own risks.
Remember that go back to 4.3 is impossible after this procedure.
You may too void your knox counter when you attempt to root your device...
Click the pictures to open the root of the Mirror and find others goodies.
- Flash The Firmware :
First: Set the reactivation lock setting of your phone to OFF.
Be sure the battery of the phone is full.
- Uninstall Kies if you have it on your computer to avoid conflicts.
- Download PC Odin and Install / update the drivers from Samsung[/URL], that's all you need.
- Best and safe way is to use the original stock usb3 cable and make the job on a portable computer with his own power supply (battery connected).
1 - Download the latest repacked rom in this folder and extract it.
This is pure stock rom with only Multi-CSC OXXEND2 added.
Currently, this rom contain 19 Country Codes:
BGL, CYO, ERO, MSR, ORX, PHE, ROM, SEB, SEE, SIO, TEB, TOP, TPH, TRA, TSR, TWO, XEF, XEH, XSK
As it have a small sized hidden partition there is no need of any PIT File. More safe in my opinion.
If you need another CSC, maybe one of then is yours:
The Multi-CSC VFGENA4, 19 Country Codes:
ATL, CNX, CYV, MOB, MTL, OMN, PRO, SIM, SWC, TCL, TOP, VD2, VDC, VDF, VDH, VDI, VGR, VOD, XFV
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OLBEND1, 10 Country Codes:
GLB, MM1, SIN, SMA, STH, THL, XME, XSP, XTC, XTE (Asia)
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OXAEND1, 5 Country Codes:
BTU, DBT, ITV, XEF, XEO
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OJVENB2, 3 Country Codes:
KSA, XFM, XSI
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ITVEND1, 1 Country Code:
ITV (Italy)
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ZZHENE3, 1 Country Code:
TGY (Hong Kong) - The attached modem ZHUENE2 is here.
As it have a small sized hidden partition there is no need of any PIT File.
The CSC VNZDMJ4, 1 Country Code:
VNZ (New Zealand)
The csc parts are from 4.3 rom but are confirmed working fine.
As it have a small sized hidden partition there is no need of any PIT File.
Three others CSC for specifics operators in France.
As they have a small sized hidden partition there is no need of any PIT File.
Check at the bottom of this post for French thread.
Just grab the one you want and put it in CSC in PC ODIN during the same flash process and it first flash the CSC inclued in the firmware, and then overwrite the CSC with the one you added.
2 - Download CF Auto Root for KitKat from Chainfire ODIN version.
Extract the tar.md5 file inside the zip to use with pc odin.
3 - Download the custom recovery PhilZ Touch ODIN version.
I advise to apply this unlock procedure before anything to avoid flash errors:
-> You need Triangle Away from Chainfire with a root acces granted.
Free version is avaible but consider to support the dev for his great job...
a/ Install the app on your phone.
b/ Run Triangle Away and Reset Flash Counter - Follow exactly what the program ask.
At the time to choose the way to reboot after the reset is done in recovery, choose reboot in download mode and then start the flash process immediatly.
4 - In download mode flash the file that you had previously downloaded N9005-hlte_PDA-xxxxxxx_CSC-xxxxxxx_MODEMS-xxxxxxx_REPACK.tar.md5 with PC Odin in AP.
Do not forget to check/enable the Phone Bootloader Update option in pc odin. (seems working nevertheless without this option ticked)
Leave all others one by default.
Make sure re-partition is NOT ticked.
If you have an error (size error - Your phone may mismatch with this rom, another Samsung lock...) as odin fail at the end of the flash process.
- Shutdown the phone, disconnect the battery, disconnect the phone from your computer and wait a minute, return to download mode.
- Download and flash the file wich contain the CSC that you want.
5 - Auto self-reboot, let the stock recovery do his work completly (the green android man).
If you don't want to install root and a custom recovery, you can stop here.
6 - Go back download mode, flash the PhilZ Touch recovery with pc odin in AP.
7 - Again, in download flash, CF Auto Root with pc odin in AP, let the installation process terminate.
Note: If you were previously rooted, jump this step and download, If not yet done, SuperSu to update by flashing the file in custom recovery..
In this case, re-flash CF Auto Root will loose all your settings of SuperSu...
8 - Download the fix for the ExtSdCard issue and flash it in custom recovery.
This is a Google security restriction, unnecessary to wait for a fix from Google, just from developpers of apps. Quick way is to apply this fix.
9 - Don't forget BusyBox which should be usefull too.
- About Mobile Odin :
As Mobile Odin seems to be unable to update the bootloader, don't use this one to avoid brick issues when operate with a different rom version than you have.
If you are already on the same firmware, you can use Mobile Odin to re-flash the rom or any other single part:
- Copy the file on your phone.
- Open this file in Mobile Odin.
- Enable EverRoot and Inject Superuser (SuperSu) in case of a system flashing.
- Choose to reboot in Recovery when you flash System and Cache partitions. If not, you may have problems regarding the CSC.
- Start Flashing.
- Do not skip md5 check to gain a little time. (For the life of your phone...)
- Issues :
All theses solutions were tested by me and worked for me, but without any other warranty.
The CSC region code or version are invisibles, the CSC folder is missing in system/.
The stock samsung keyboard crash often once booted.
You need another CSC (warning, you wil loose all your datas and settings, change for another CSC perform a wipe of the phone)
- Check here for the file you need, download and extract it.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_CSC_xxxxxxx_RECOVERY-xxxxxxx_REPACK.tar.md5 with pc odin in CSC.
The Modem is not updated.
Download and extract the .tar.md5 modem file.
-> Apply the Unlock Procedure.
- Flash the file that you had previously downloaded N9005-hlte_MODEMS_xxxxxxx_REPACK.tar.md5 with pc odin in CP.
- Reboot normally.
The Bootloader is not updated.
You can check by using this app.
-> Download and extract the .tar.md5 bootloader file.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_BL_xxxxxxx_REPACK.tar.md5 with pc odin in BL and check/enable the Phone Bootloader Update option.
- Reboot normally.
Flash player doesn't work anymore.
-> Install Firefox last up to date version and the original latest apk from adobe, nothing else to do.
-> If you prefer Dolphin, download the special version of adobe flash player, more here.
Maybe someone make an xposed module later, it should be a dream...
This fix seems working with this rom (bootloop efs corrupted related).
Not personally affected, just tested the flash.
Download here too.
After all this procedure, you should be fine, upgraded and with all yours datas and settings...
At this state, i just made a wipe of the cache and dalvik cache with phil'z recovery.
- Tune :
- Enable Init.d Support.
- To simply restore the sound at the (de)connection of the charger, you can install this app.
- If you want an imaged battery, you can use RECOVERY - SystemUI N9005 xxxxxxx MOD tkari4-Version by tkari4 based on the guide from parkhyb.
Basically revert to the old 4.3 style for battery and network icons.
{
"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"
}
Just Flash the mod with any custom recovery.
To revert back to the original situation, just flash in custom recovery the file RECOVERY - SystemUI xxxxxxx ODEX STOCK. (STOCK ODEX version)
You can use my blue battery mod. (I reworked a little the graphics for a better scale.) Just extract the .rar archive and install normally the apk Inside, you need too a working Xposed Framework installed.
You can find other Xposed compatibles battery Mods here.
Just reboot once installed.
Many Thanks to tkari4 for keeping alive his mod. :good:
- The repacks i made still works fine.
The rom repacks are made by me with this tool.
Many thanks and credits to all the persons who made this possible.
Notes:
As i do not have the time to download/extract all the roms, if someone needs another CSC repack for him or just to share, please post here with a link for the extracted CSC files only (cache.img.ext4 - hidden.img.ext4) related and with all the details (region, full code name, original rom it come from ... )
To unpack a .tar.md5 file, simply rename it as .tar and extract the content with any good archive software.
I will centralize here.
All others requests in any another form will be ignored, thanks for understanding.
To keep as simply and clear as possible, i will maintain on the Mirror and on thread only the latest updated rom, so if you put elsewhere any link from here, it may be broken in the time, the only ones which would be permanent is the one of the folder and the one of this thread. If you Mirror any file, thanks to keep credits.
Keep a local copy of the downloaded files if you think you will need then later as the content should be updated here.
I maintain the updates only for multi-csc repacks and keep others ones in the mirror, if you need one of theses mono-csc wich is not updated with the latest recovery avaible, simply ask here...
French users, clone thread is here.
Just press thanks if i helped.
Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.
polish_pat said:
Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.
Click to expand...
Click to collapse
Yes, every day i do.
And i saw no thread that talk about merging two différents roms to make a new one for a specific country, centralize all the majors tools with direct download links for correct versions to avoid confusions between JB & KK, that i often saw, and attached xda threads, and too provide others files needed at the same place for my device (n9005)
Maybe i had read the forum more often than you think...
Sincerly.
Perhaps you should look again
http://forum.xda-developers.com/showthread.php?t=2617932
http://forum.xda-developers.com/showthread.php?t=2631395
http://forum.xda-developers.com/showthread.php?t=2614787
http://forum.xda-developers.com/showthread.php?t=2618633
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'
I made also my Rom N9005XXUENA7_OXXENA5_XXUENA2_ NoBootloader whit this TOOL from A.S._id Dev. Thanks @A.S._id
Only this files:
boot.img
cache.img.ext4 -->from NA6 (OXX)
hidden.img.ext4 -->from NA6 (OXX)
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4
Whitout Bootloader (5 files). Work well whit BL XXUENA6 and no Knox appl's.
At first boot, after enter whit my language, I have my csc TPH automatic, alright.
It's very good this [TOOL] TAR.MD5 PACKAGER and easy to make changes whit.
Anyway, thanks by Your work.
Best Regards
Valente
=======================================================================================
polish_pat said:
Did you search the forum before posting?
Click to expand...
Click to collapse
polish_pat said:
Perhaps you should look again
Click to expand...
Click to collapse
Hi Dear @polish_pat
Please, we have a MODERATION to see all Member's work. Not censure this Member. He have rights like You.
Thank You
polish_pat said:
Perhaps you should look again
....................
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'
Click to expand...
Click to collapse
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly
Le [email protected] said:
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly
Click to expand...
Click to collapse
i made a thread a month ago, when it was relevant and nobody else did it.
Le [email protected] said:
Hi,
Set the reactivation lock setting of your phone to OFF.:
Click to expand...
Click to collapse
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.
johnvicencio said:
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.
Click to expand...
Click to collapse
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn
Le [email protected] said:
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn
Click to expand...
Click to collapse
I see thank you. That doesn't exist on T-Mobile USA at least not on 4.3.
1 - Download the official Poland rom...
2 - Download any NA7 rom...
To this step's We have here a MIRROR on MEGA Host.
Updated the op with a link to the repacked rom and refreshed the guide.
So it is more easy and simple, i think.
Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today
Pierre118 said:
Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today
Click to expand...
Click to collapse
Op Updated
No need to repack the whole firmware as all which is needed is Inside.
I am currently upload the rom to mirror it ...
Just made a new repack for the multi-csc.
Just flashed over the NA7 rom by following my guide and all went fine.
No full wipes.
Just made a wipe in dalvik cache and cache in recovery once done.
Great and complete Guide. Useful this ALL IN ONE PLACE. Bookmarked.
Thanks
I QUOTE from my THREAD next useful posts by @letama and @Le [email protected]
After this question to a member that not managed to flash the Bootloader NB3:
ValenteL said:
What Rom have You installed? If You have flashed the XXUENB3 why You are in NA6 BL?
Click to expand...
Click to collapse
letama said:
There is a catch in going from NA6 to NB3, it seems bootloader flashing is ignored now in NA6 BL if your rom status is custom. Solution is triangle away, reflash na6 stock, then make sure that you status is official before flashing NB3.
Click to expand...
Click to collapse
Le [email protected] said:
I was on NA7 BL previously flashed over NA6 BL without any problem.
Followed your trick and flashed my own made NB3 flashable file.
I did not any reflash, just reseted with triangle away.
And it worked, i am now on NB3 BL.
Updated my thread too..
Thanks.
Click to expand...
Click to collapse
letama said:
Thanks, good to know that reflashing pure stock is not mandatory, so the bootloader checks custom status flag only and not the whole firmware. Great, will save time for next one .
Click to expand...
Click to collapse
Updated the OP with a new version of Flash Player i found on xda wich work with Firefox too now.
Hi @Le [email protected]
Only for this time: Do not forget to check/enable the Phone Bootloader Update option in pc odin.
I don't understand why, if we flash a complete Rom whit a new bootloader. We not update the bootloader installed. Why You have this opinion now?
Thank You
Hi ValenteL
I saw (here or on other frenchs forums, no links to provide, forgot then) twice posts of somes personnes who don't have checked the option and have updated their bootloader and others one who don't had bootloader update and got soft brick issues as the rest was updated (JellyBean to Kitkat essentially)
It is usually advised here to check this option.
I not personnally took the risk to bypass this option in pc odin and always used it, so i can not confirm if it is important, effective or not.
There is this option in pc odin, i think too this is not for nothing at all.
For all this reasons, i prefer advise to enable this option when flashing a new rom, and it cost nothing to do.
Personnaly, i think it is important to do when using multi-files roms as the first Poland Leaked KitKat, but the bootloader update must be done automatically when flashing a single file rom which contain Inside all the needed parts.
Of course we can have problems when the knox is trigerred or the status of the rom is to custom, then somes parts seems to be 'jumped' when flashing. I feel this fact is increasing in the time.
When i bought my note 3, Under JellyBean, in France, i updated the rom with the latest version of JellyBean avaible on sam mobile for my country (XEF) and had no issue after the flash.
I got problem when i starded to flashed KitKat from others countries as the XEF one is not yet avaible and as i am a little an impatient flash-addict.
I wonder sometimes if i could have all this problems if were more patient and waiting for an upated version for my country.
At this time i identified three parts wich seems locked (not a secret).
CSC -> Ok, Samsung do not want i flash from another country, new policy from Samsung to lock by geographics sectors.
Modem -> Ok, region lock again.
Bootloader -> Why ? Does samsung want to block customs rom such CM, roots and others sames things? And knox related certainly too.
Samsung want to control and limit me a lot, to make more money with me.
Me, i want to be able to do ALL what i want with the device i bought, this is mine, as i can do with my Note 1.
There is a lot of chances that samsung never see again my money...
Time to bed here.
Sincerly
@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
---------- Post added at 09:22 PM ---------- Previous post was at 08:36 PM ----------
Pierre118 said:
@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
Click to expand...
Click to collapse
Never mind, Mega had a problem. Download is ok now.