This is a quick guide for anyone who needs instructions on how to return to stock or unbrick using a Mac (OSX) as I know I've seen a lot of people ask how. Since I just got rid of my Windows machine permanently, I figure I'd share my methods with others.
THIS GUIDE CAN GLADLY BE ADDED TO OTHER "HOW-TO" GUIDES, AND I WILL DELETE THIS ONE AFTER THAT, IF NEED BE.
This is actually much much simpler than I originally thought it would be.
RETAIL EDITION INSTRUCTIONS
Downloads:
Heimdall: http://glassechidna.com.au/heimdall/ Credit Benjamin Dobell
Factory Images for VZW Note 3: http://www.androidfilehost.com/?fid=23269279319196106 Credit Beanstown106
Unarchiver (or equivalent): Search your Mac App Store or google search - Its free - https://itunes.apple.com/us/app/the-unarchiver/id425424353?mt=12
Pre-install and unpack stuff:
Double click and install Heimdall. Self explanatory instructions, nothing special. Reboot if requested.
Double click and install The Unarchiver. Also self explanatory instructions. Reboot if requested.
Double click the ALL_N900.....7z file from beans to extract the files out of it. It will become .tar.md5 file. (select open with -> Unarchiver if nec.)
Double click the .tar.md5 file you just created to extract its contents as well. This will become a desktop folder with the actual images inside it.
Move those factory images you just unpackaged to your root user folder (or wherever you choose for this magic to happen).
Open Terminal (comes pre-installed in OSX)
Ready to Rock-N-Roll:
DO NOT FLASH THESE YET, this is just to show you the commands you are performing.
Code:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --MODEM modem.bin
heimdall flash --SBL1 sbl1.mbn
heimdall flash --DBI sdi.mbn
heimdall flash --ABOOT aboot.mbn
heimdall flash --RPM rpm.mbn
heimdall flash --TZ tz.mbn
heimdall flash --BOOT boot.img
heimdall flash --RECOVERY recovery.img
heimdall flash --PERSIST persist.img.ext4
heimdall flash --SYSTEM system.img.ext4
heimdall flash --CACHE cache.img.ext4
The reason you do not want to flash ^^^those yet is that Heimdall will reboot the phone between each flash, so why not just do it all in one command, right?
Here (make sure you get the whole thing, it scrolls to the right):
Code:
heimdall flash --APNHLOS NON-HLOS.bin --MODEM modem.bin --SBL1 sbl1.mbn --DBI sdi.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --BOOT boot.img --RECOVERY recovery.img --PERSIST persist.img.ext4 --SYSTEM system.img.ext4 --CACHE cache.img.ext4
I have not done this with retail version yet, only dev edition (instructions below).
All done. Make sure to boot to recovery and wipe data / factory reset before usage.
Enjoy.
DEV EDITION INSTRUCTIONS
Downloads:
Heimdall: http://glassechidna.com.au/heimdall/ Credit Benjamin Dobell
"Factory" Images for VZW Dev Edition Note 3: http://www.androidfilehost.com/?fid=23269279319196402 Credit Beanstown106 - created package
Unarchiver (or equivalent): Search your Mac App Store or google search - Its free - https://itunes.apple.com/us/app/the-unarchiver/id425424353?mt=12
Pre-install and unpack stuff:
Double click and install Heimdall. Self explanatory instructions, nothing special. Reboot if requested.
Double click and install The Unarchiver. Also self explanatory instructions. Reboot if requested.
Double click the DevEdition.7z file from beans to extract the files out of it. It will become .tar.md5 file. (select open with -> Unarchiver if nec.)
Double click the .tar.md5 file you just created to extract its contents as well. This will become a desktop folder with the actual images inside it.
Move those factory images you just unpackaged to your root user folder (or wherever you choose for this magic to happen).
Open Terminal (comes pre-installed in OSX)
Ready to Rock-N-Roll:
DO NOT FLASH THESE YET, this is just to show you the commands you are performing.
Code:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --BOOT boot.img
heimdall flash --MODEM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --SYSTEM system.img.ext4
heimdall flash --CACHE cache.img.ext4
The reason you do not want to flash ^^^those yet is that Heimdall will reboot the phone between each flash, so why not just do it all in one command, right?
Here (make sure you get the whole thing, it scrolls to the right):
Code:
heimdall flash --APNHLOS NON-HLOS.bin --BOOT boot.img --MODEM modem.bin --RECOVERY recovery.img --SYSTEM system.img.ext4 --CACHE cache.img.ext4
All done. Make sure to boot to recovery and wipe data / factory reset before usage.
Enjoy.
That was a really good post
Thank you for awesome guide. I have been struggling with mac for a really long time, I had to bootcamp for all of my Android needs. This definitely starts to break that barrier.
jmichaels1982 said:
Thank you for awesome guide. I have been struggling with mac for a really long time, I had to bootcamp for all of my Android needs. This definitely starts to break that barrier.
Click to expand...
Click to collapse
No problem. Same for me, this was my way of finally getting rid of my bootcamp partition :good:
Sent from my Galaxy Note 3 Developer Edition
Good Job!! Mac users needed some Luv
droidstyle said:
Good Job!! Mac users needed some Luv
Click to expand...
Click to collapse
Speaking of which....didn't I read somewhere that fastboot commands actually work on Dev Edition devices? I'd just try it but I'm at work right now...
EDIT: Nope, they don't work.
Sent from my Galaxy Note 3 Developer Edition
OP modified to add full retail instructions as well.
Hi, was wondering if this would work for my Sprint Note 3?
My phone is currently soft bricked.
Thank you so much to anyone who can answer this. Needless to say, it's been frustration so far with my limited knowledge.
???
does anyone have the boot.img from
ro.build.id=KOT49H
ro.build.display.id=ATT_11.10.8.7
ro.build.version.incremental=ATT_PadFone-11.10.8.7-20140527
i can't extract it from nand in pc
Hi,
How to extract modem.bin ? I extract rom but i don't see the modem.bin...
Just :
boot.img
cm.bin
recovery.img
sboot.bin
system.img
thx
Edit : i use izarc and is bad, with 7zip i can see all files and folders, and modem.bin, sorry.
Now i can extract the modem and bootloader from french providers.
A very warm Hi! to the XDA community
My phone, the Sony Xperia E4, does not have a recovery - so I am slowly learning how to develop one. It has an MT6582 chip.
In the process I have obtained the stock boot.img (via boot.sin) from the phone's stock .ftf firmaware file.
I wish to use MTK droid tools to create the recovery, however it first gave me the error that the boot.img file is not split. After some research I came to learn that such boot.img files need to be split into the kernal (Zimage i believe) and ramdisk.
After some further research I came across this seemingly helpful guide and tool on how to split the boot.img file on Windows (unfortunately I do not have Linux at my disposal atm).
Now to my issue: (referring to the aforementioned guide & tool) When running the command
Code:
bootimg.exe --unpack-bootimg boot.img
I get this error:
Code:
AssertionError: invald bootimg
Which leads me to believe the boot.img file I have extracted may be corrupt or extracted from the wrong .sin file.
If you are still with me, how can i confirm that the boot.img file from the stock rom is indeed "working" and contains ramdisk and kernal?
Some extra information:
This is the guide I used to initially extract the boot.img file from my phones stock firmware. They highlight that boot.img is extracted from the kernal.sin file. My firmware has no such file. Later in the comments it mentions that newer Sony phones have the boot.img file in the appropriately named "boot.sin" file. This is the file i used to extract my boot.img. Thus from here I cannot see why the boot.img file cannot be split.
The full command line and response is:
Code:
C:\Users\\Downloads\Cofface>bootimg.exe --unpack-bootimg boot.img
arguments: [bootimg file]
bootimg file: boot.img
output: kernel[.gz] ramdisk[.gz] second[.gz]
Traceback (most recent call last):
File "<string>", line 2213, in <module>
File "<string>", line 1424, in unpack_bootimg
File "<string>", line 151, in parse_bootimg
AssertionError: invald bootimg
Thanks very much in advance!
Hi xda, this is my algorithm about best thing that you can to bypass frp (that acutally i follow) in order to flash system.img also questionning to resolve my problem, thanks for reading.
PART1 - Download the stock firmware full factory including, BL | AP | CP | CSC.
PART2 - Using ImgExtractor and editing file as needed means remove bloatware[...]
[Q] If you modify content of system.img, do you must absolutely repack to same bytes plus 100M, in order to flash it?
PART3 - Using make_ext4fs to repack system.img
[Q]Do i need pit file for ext4 partition cause odin3 throw me the following :
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> system.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
PART4 - MAKING THE FLASHABLE TAR FILE
[Q]What type of odin3 accept ?
1. So now you should have the image file you want to flash but you need to get it in to a .tar format that can be flashed by Odin. Copy the .img file to the INPUT folder in the Toolkit (v1.2.7 or later) and start the Toolkit. Type option ’99’ to load up the Basic Toolkit. In the Main Menu of the Basic Toolkit select option ‘8’ (Create an Odin flashable tar). In the next menu choose option 2 to make a single tar file from multiple images (it doesn’t matter that you only have 1 image).
2. Make sure that ONLY the image you need to flash is displayed in the list (.img or .img.ext4) and type yes to start. If the file is a system image then it will take a while to convert but eventually it should say completed and you will have a .tar file in the OUTPUT folder. This is your flashable file.
PART5 - – FLASHING THE TAR FILE
1. Once you are back in the Main Menu of the Basic Toolkit select the ‘Device Reboot Options’ section and ‘Reboot to Download Mode and Start Odin’. If you can not boot your device in to Android with adb debug enabled (needed for this option) then just unplug your usb cable, hold Volume Down, Home and Power buttons until you get a warning screen and press Volume Down to get in to Download Mode. Then you can run Odin3_v3.09.exe from Toolkit folder. Now connect your usb cable and the box under ID:COM should be blue.
2. Make sure ‘Auto Reboot’ and ‘F. Reset Time’ is ticked.
3. Click on ‘PDA’ / ‘AP’ and browse to the Toolkit, OUTPUT folder. Click on the tar file (it will start with CREATED-TAR) and then click on Open. When you are ready hit the “Start” button and the flash process should start. This may take a while depending on the image you are flashing. A progress bar will be displayed on the device and on Odin to let you know how it’s going.
4. After the flash finishes your device will reboot and if everything went fine the new image will be flashed and your device should boot without any problems.
-PART6 - Deal with XDA (lol) when odin3 throws FAIL(<ID:0/004> Complete(Write) operation failed.)
Well as extra, there a pit file for hidden img that fix FAIL(<ID:0/004> Complete(Write) operation failed.)
WHAT CAN I DO FOR SYSTEM.IMG ? :fingers-crossed: