I TAKE NO CREDIT FOR CORE METHOD. I APPLIED IT FOR OUR DEVICE !
To make long story short, I've hard bricked my device while trying to patch/unlock the bootloader after successfully flashing a custom kernel (this tripped knox counter). After reading all guides that addresses the problem for other devices, I'm posting a 100% working solution for the most hated disaster in the Android rooting/flashing world. Moreover, this is very promising info for testing bootloader exploits.
What is Hard Brick?
Hard brick is the state of android device that occurs when your device won’t boot/respond/charge at all. This is mainly caused by flashing corrupted firmware, damaged bootloader, incomplete flashing in Odin/Download mode, or interrupted OTA upgrade. You can't recover from hard brick by traditional methods since your phone is ~dead & you can't enter any Recovery or Download Modes; You'll need to use JTAG (expensive service), USB JIG (cheap, but no gurantee), or this free guide/files to get it repaired.
What do you need?
- Hard Bricked Device: Samsung Galaxy Note 3 (N900V)
- Micro SD Card: 4/8/16/32 GB micro SD card
- Unbrick Image: working dump with the same bootloader/version
- Image Writer: native commands on Linux/MacOSx or Win32 Disk Imager on Windows
How to recover?
1- Download Unbrick Image for your bootloader (MJE, NC2 or NC4) from here
2- If you're using Windows, download Win32 Disk Imager
3- Backup all files in the micro SD card you 'll use
4- Write the Unbrick Image to your micro SD card using Win32 Disk Imager or Linux/MacOSX commands
5- Remove battery, Insert micro SD card & then the battery
6- Hold Power + Home + Volume Down to enter Download Mode by bootloader on SD card
7- Flash Stock firmware via Odin & Enjoy
YOU MAY NEED TO TEST MICRO SD CARDS WITH DIFFERENT TYPES/SIZES & FORMAT AS EXFAT BEFORE WRITING AN UNBRICK IMAGE ACCORDING TO YOUR BOOTLOADER!
This method should work for most Hard Brick cases, especially those with flashing failures. However, some cases might need a repair service or a hardware treatment to recover. One thing you may try if you can't get a replacement (warranty claim) is from Samsung guide for N900 device that includes disassembly & making short of R4075 resistance (which isn't tested & for another device + I don't recommend it) as described here.
Click to expand...
Click to collapse
For Developer Edition, you need to create your own Unbrick Image since I can't share it for the device-specific bootloader. Just run this Unbrick Image Creator in recovery & it'll create "/sdcard/Unbrick_Files" in your internal SD card.
For more details, read the guides provided bellow in the credits section.
Downloads:
All files you may need are available in this folder.
Credits:
- designgears - for this guide
- Shabbypenguin - for this guide
- theramsey3 - for this guide
- dstruct2k - for this guide
- -Mr. X- - for this guide
Thanks to:
- @soundrizm - for creating the MJE image from his device
- @jrbxx7 - for creating the NC2 image from his device
- @K03WL3R - for creating the NC4 image from his device
XDA:DevDB Information
How to recover from a HARD BRICK, Tool/Utility for the Verizon Samsung Galaxy Note 3
Contributors
hsbadr
Version Information
Status: Stable
Created 2014-08-01
Last Updated 2015-02-15
Nice work! Thanks
Tapped from an annihilated N10.1
This is amazing progress for our devices @hsbadr. I, for one, can't thank you enough for all you're doing to keep our beautiful albeit locked down Note 3's on the forefront! Donation coming asap!
Sent from my SM-G900V using Tapatalk
Wait, how can this help with unlocking bootloader? I have no developing background so this would be nice to know
This won't reset knox to 0 though, correct? So there's no way to reset to 0 yet?
I see there is a nc2 and nc4 unbrick image... If i am on the unified kk Jasmine rom firmware which image do i use... I thought i read on the Jasmine thread that it contained components of both...
Samsung Note 3 - VZW
Jasmine 2.0 v4
XDA Pro
ihavenewnike said:
Wait, how can this help with unlocking bootloader? I have no developing background so this would be nice to know
Click to expand...
Click to collapse
Testing bootloader exploits could easily HARD BRICK the device; now, we've a tested fully working fix for this disaster. So, devs can feel better with their tests.
kvnhmmd said:
This won't reset knox to 0 though, correct? So there's no way to reset to 0 yet?
Click to expand...
Click to collapse
This just enables booting the device from SD card so that you can enter Download Mode & revive it from HARD BRICK state. The knox counter won't change unless you've already tripped it while messing with your device at/before HARD BRICK.
Night_Watcher said:
I see there is a nc2 and nc4 unbrick image... If i am on the unified kk Jasmine rom firmware which image do i use... I thought i read on the Jasmine thread that it contained components of both...
Click to expand...
Click to collapse
It only depends on the bootloader version. The unified KK firmware doesn't include any bootloader; so, you'll need to use the Unbrick Image based on your bootloader (NC4 for OTA update or full NC4 tar via Odin & NC2 otherwise). You may try the NC2 image 1st which won't boot if you're on a newer NC4 bootlooder; if so, use the NC4 image.
hsbadr said:
Testing bootloader exploits could easily HARD BRICK the device; now, we've a tested fully working fix for this disaster. So, devs can feel better with their tests.
This just enables booting the device from SD card so that you can enter Download Mode & revive it from HARD BRICK state. The knox counter won't change unless you've already tripped it while messing with your device at/before HARD BRICK.
It only depends on the bootloader version. The unified KK firmware doesn't include any bootloader; so, you'll need to use the Unbrick Image based on your bootloader (NC4 for OTA update or full NC4 tar via Odin & NC2 otherwise). You may try the NC2 image 1st which won't boot if you're on a newer NC4 bootlooder; if so, use the NC4 image.
Click to expand...
Click to collapse
So now we can just randomly try bootloaders, like maybe the DE bootloader modified for a device?
ihavenewnike said:
So now we can just randomly try bootloaders, like maybe the DE bootloader modified for a device?
Click to expand...
Click to collapse
NO, don't! This is only for devs or users who know exactly what they're doing. If you flashed another device's bootloader, you may kill your device forever. However, you can use it to recover when you ACCIDENTALLY made your device hard bricked.
Ok. Thanks. Curious, how do you learn about these things. I would love to try some stuff. Hey I got the device for 50 off contract.
Thank you, Thank you, Thank you! Makes me feel better about trying different roms &mods.
had a Droid HD unlocked bootloader, bricked it many times.
Could the unbrick files be made flashable. The DE 4.4 bootloader is now on new devices and many DE guys (me too) are interested in upgrading from 4.3? I bow low to @hsbadr really great work!
ol`DXer said:
Thank you, Thank you, Thank you! Makes me feel better about trying different roms &mods.
had a Droid HD unlocked bootloader, bricked it many times.
Click to expand...
Click to collapse
You're welcome! Glad I could help.
LillieBennett said:
Could the unbrick files be made flashable. The DE 4.4 bootloader is now on new devices and many DE guys (me too) are interested in upgrading from 4.3? I bow low to @hsbadr really great work!
Click to expand...
Click to collapse
The purpose of Unbrick Image(s) is to revive a ~dead (hard bricked) device by booting from external SD card to enter Dwonload Mode & flash firmware to recover. You can pull all images from your device & on DevED, all of them can be flashable.
Is the process similiar for a phone that was on MJE?
Scenario:
Phone was stock MJE.
Rooted w/ TowelRoot, installed SS 3.7.1
Rebooted to DL mode, Odin'd "unified firmware" from Jasmine thread (*I think this is where things went sideways b/c no NC2/4 rom was installed to stock slot, just the leftover MJE+TR+SS install).
Phone shutdown at the end of that Odin, and now will not power up / vibrate / enter DL mode / nothing ...
I put the NC2 debrick image on a 32GB Class4 MicroSD - no joy.
I was wondering if it's because the MJE bootloader is still there? Wouldn't I then need an MJE unbrick microSD img?
I figured as much so I made one by Odin'ing another phone back to Stock MJE, and doing a "dd if=/dev/block/mmcblk0 of=/sdcard/unbrickMJE.img count=524288" and used that .img to make the MicroSD card (with Win32DiskImager)...
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
NetworkPIMP said:
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
Click to expand...
Click to collapse
Does your phone vibrate when you attempt to turn it on? With the battery or without the battery but plugged into the charger? In my experience with hard bricks, the phone should at least vibe when you go to power it up. Also, not sure if it will make a difference but, try a class 10 card with the same amount of memory as the phone.
Other than that everything you did sounds correct.
Sent from my SM-G900V using XDA Premium HD app
NetworkPIMP said:
Is the process similiar for a phone that was on MJE?
Scenario:
Phone was stock MJE.
Rooted w/ TowelRoot, installed SS 3.7.1
Rebooted to DL mode, Odin'd "unified firmware" from Jasmine thread (*I think this is where things went sideways b/c no NC2/4 rom was installed to stock slot, just the leftover MJE+TR+SS install).
Phone shutdown at the end of that Odin, and now will not power up / vibrate / enter DL mode / nothing ...
I put the NC2 debrick image on a 32GB Class4 MicroSD - no joy.
I was wondering if it's because the MJE bootloader is still there? Wouldn't I then need an MJE unbrick microSD img?
I figured as much so I made one by Odin'ing another phone back to Stock MJE, and doing a "dd if=/dev/block/mmcblk0 of=/sdcard/unbrickMJE.img count=524288" and used that .img to make the MicroSD card (with Win32DiskImager)...
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
Click to expand...
Click to collapse
1st: you should have flashed full firmware to upgrade from JB; the unified firmware is for KK only !!!
2nd: If you can enter Download Mode, flash the firmware linked above to recover.
3rd: You should use Unbrick Image for the same bootloader & device (N900V MJE in your case)
Update: you may also try a USB JIG to enter Download Mode & flash the required firmware; you can create one or order it from Amazon.com (it's very cheap).
Can someone do a video tutorial on this.
An unbrick image may only be viable on a 32GB+ MicroSD. It must be at least the size of the eMMC chip on-board.
Kudos to all the folks that are involved in this, a life saver for those in need for sure!:good:
Any luck with mj7 debrick.img
Related
I have a note 2 arriving this afternoon and I would like to unlock the bootloader and flash stock samsung experience. My understanding is that I download and run CASUAL (link in general forum) from linux using oracle java 7 and the system will be prepared for flashing (have bootloader unlocked, radio firmware updated and twrp installed).
-
I then download cleanrom (either cleanrom ace 4.2.5 or cleanrom vzw-se) put the binary on a microsd card; double check md5 hash. I then reboot the note 2 and hold volume up; home and power at same time while it boots and there will be an option to select a rom to boot?
-
Four questions:
1) Am I correct in the instructions (and will the radio be automagically updated by casual or is that a different process) ?
2) Which is 'better' or what is the difference between cleanrom ace 4.2.5 and cleanrom vzw-se ? Which is more likely to see updates as samsung make changes ?
3) When future radio updates occur how are they applied; do I rerun CASUAL?
4) Can the device be permanently bricked or can I always get into bootloader to load somethjing off sd card (I though the original hack - pre CASUAL - suggested that if you did not flash the radio first you could permantly brick the device which I did not understand is why you could not start over and then flash the radio?)
--
This will be my first time flashing an andriod device. My current (and first smart) phone is a verizon razr which is locked.
jake21 said:
I have a note 2 arriving this afternoon and I would like to unlock the bootloader and flash stock samsung experience. My understanding is that I download and run CASUAL (link in general forum) from linux using oracle java 7 and the system will be prepared for flashing (have bootloader unlocked, radio firmware updated and twrp installed).
-
I then download cleanrom (either cleanrom ace 4.2.5 or cleanrom vzw-se) put the binary on a microsd card; double check md5 hash. I then reboot the note 2 and hold volume up; home and power at same time while it boots and there will be an option to select a rom to boot?
-
Four questions:
1) Am I correct in the instructions (and will the radio be automagically updated by casual or is that a different process) ?
2) Which is 'better' or what is the difference between cleanrom ace 4.2.5 and cleanrom vzw-se ? Which is more likely to see updates as samsung make changes ?
3) When future radio updates occur how are they applied; do I rerun CASUAL?
4) Can the device be permanently bricked or can I always get into bootloader to load somethjing off sd card (I though the original hack - pre CASUAL - suggested that if you did not flash the radio first you could permantly brick the device which I did not understand is why you could not start over and then flash the radio?)
--
This will be my first time flashing an andriod device. My current (and first smart) phone is a verizon razr which is locked.
Click to expand...
Click to collapse
You can download any rom, and it doesn't matter if it is on the SD card or not. I just always make sure I have a nandroid on my sd and on my computer at all times.
I'm unsure how to answer 1.), because i'm unsure what you are asking exactly.
2.) neither is better than the other. if you use VZW apps, use the VZW cleanrom. If you don't and want the purest version possible, use cleanrom ace. I personally use cleanrom ace.
3.) do you mean OTA? they are international roms so you don't get asked for the VZW updates
4.) i think you can brick the device, but it is really hard and almost impossible to do as long as you are reading the instructions for hte mod/rom/etc... you are using. Most of the time you can use a nandroid to get back to a saved state.
With (1) I was asking if i listed the right sequence or if I missed some critical detail. If I use cleanrom ace (I'm leaning towards either cleanrom ace or jellybean) is there a way for me to install myverizion (which is the only verizon ap I used; polaris is also nice but both version include polaris).
kimdoocheol said:
You can download any rom, and it doesn't matter if it is on the SD card or not. I just always make sure I have a nandroid on my sd and on my computer at all times.
I'm unsure how to answer 1.), because i'm unsure what you are asking exactly.
2.) neither is better than the other. if you use VZW apps, use the VZW cleanrom. If you don't and want the purest version possible, use cleanrom ace. I personally use cleanrom ace.
3.) do you mean OTA? they are international roms so you don't get asked for the VZW updates
4.) i think you can brick the device, but it is really hard and almost impossible to do as long as you are reading the instructions for hte mod/rom/etc... you are using. Most of the time you can use a nandroid to get back to a saved state.
Click to expand...
Click to collapse
jake21 said:
With (1) I was asking if i listed the right sequence or if I missed some critical detail. If I use cleanrom ace (I'm leaning towards either cleanrom ace or jellybean) is there a way for me to install myverizion (which is the only verizon ap I used; polaris is also nice but both version include polaris).
Click to expand...
Click to collapse
I think you're missing a lot of steps. Also to get to recovery power off. Then do the button combo to power it on. Here is a great guide on how to flash a ROM. You are going to want section 2. Also if you want my Verizon you're gong to want the Verizon version of clean or beans or Eclipse. Then just download my Verizon from the play store
http://forum.xda-developers.com/showthread.php?p=34891181
Sent from the dark on a Note 2
Ok thanks. There is some side confusion on my part (perhaps with system layering) that I think contributes:
I understand what a bootloader is but I'm unsure what twrp is (is it a boot loader or does it act as a kernel that the bootloader runs and in itself allows for execing another kernel (the actual user layer). I also don't quite understand where the radio fits in this picture. I.e, how do you tell the system to flash the radio eprom indepdently of the kernel. My basic understanding of the system layer is:
rom -> exec bootloader from nvram -> bootloader has a configured option to exec the kernel -> kernel runs everything else
radio is in a different nvram that the chip knows how to read when radio is triggered by the kernel
(I used nvram above but I really don't know what sort of r/w chip they use these day; i.e, eeprom or something else)
-
My understanding is that if the flashing of hte bootloader fails then the phone is truely bricked and will require the nvram/eeprom be pulled and falshed exeternally as the rom bootloader has no method to recover.
-
Is this correct ?
kintwofan said:
I think you're missing a lot of steps. Also to get to recovery power off. Then do the button combo to power it on. Here is a great guide on how to flash a ROM. You are going to want section 2. Also if you want my Verizon you're gong to want the Verizon version of clean or beans or Eclipse. Then just download my Verizon from the play store
http://forum.xda-developers.com/showthread.php?p=34891181
Sent from the dark on a Note 2
Click to expand...
Click to collapse
jake21 said:
Ok thanks. There is some side confusion on my part (perhaps with system layering) that I think contributes:
I understand what a bootloader is but I'm unsure what twrp is (is it a boot loader or does it act as a kernel that the bootloader runs and in itself allows for execing another kernel (the actual user layer). I also don't quite understand where the radio fits in this picture. I.e, how do you tell the system to flash the radio eprom indepdently of the kernel. My basic understanding of the system layer is:
rom -> exec bootloader from nvram -> bootloader has a configured option to exec the kernel -> kernel runs everything else
radio is in a different nvram that the chip knows how to read when radio is triggered by the kernel
(I used nvram above but I really don't know what sort of r/w chip they use these day; i.e, eeprom or something else)
-
My understanding is that if the flashing of hte bootloader fails then the phone is truely bricked and will require the nvram/eeprom be pulled and falshed exeternally as the rom bootloader has no method to recover.
-
Is this correct ?
Click to expand...
Click to collapse
I think you are way over thinking this. So, TWRP is just your recovery. It replaces the stock Android recovery. To change your radio you would boot into TWRP and flash it like anything else.
As for the system layer break down. It's not really important for flashing except that kernels are included with whatever ROM you flash so unless you want to run a different one there's no need to worry about it. Also, radios are never included in a ROM flash so no need to worry about it.
To the if you can brick your phone. If course you can, but as stated is hard to do. Check the md5 before using Odin and don't unplug in the middle of a Odin flash. You can still recover most the time anyways, but why risk it.
Sent from the dark on a Note 2
JUST THOUGHT I WOULD TOSS THIS UP IF ANYONE NEEDS IT, THERE IS A COPY IN BLOATWARE LISTS !!!
First what version of KIKAT are you on ? If you are on 4.4.4 NH7 or NK4 the latest upgrade then you can root with Chainfires CF-autoroot or his SuperSu v 1.94, v2.02 or 2.40 this will trip KNOX warranty. Towel Root will not work yet for NH7 or NK4. If you are still on 4.4.2 NC5 then you can use Towel Root to root your device, this will NOT trip KNOX warranty. If you root with Chainfires CF-autoroot or his SuperSu v 1.94 or v2.40 this will trip KNOX warranty on NC5. If you want odin flash a fresh copy of 4.3 NAB, 4.4.2 NC5, or 4.4.4 NH7 here is micmars link http://forum.xda-developers.com/showthread.php?t=2712205 or rpenrod23 [ odin ] (mirrors )http://forum.xda-developers.com/showthread.php?t=2522638 for NK4 and OC5 you will need to go here http://www.sammobile.com/firmwares/ . Make sure you have USB drivers installed on your PC here is the link http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
How to flash a fresh copy of a stock OS
1. download the version of KitKat you want to the desktop of your PC.
2. extract zip file to the desktop of your PC it will turn it into a .tar file
3. you need to install Samsung drivers on your PC you can get them from here http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
4. download odin to your desktop here is the link ( version 1.85 ) https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo ( version 3.07 ) http://www.mediafire.com/download/2uxt5u83qxhz6xr/Odin_v307.zip
5. completely power down device, reboot into download mode (hold power button, home button, and volume down button at the same time, then push the volume up button)
6. open odin on desktop, connect device to PC via USB cable COM: will light up in upper left corner of odin doesn't matter what color it is just shows a connection.
7. click the PDA button a box will open click on desktop then on KitKat file to open
8. now don't touch anything else and click start
9. it will take several minutes, then say pass, and automatically reboot device with new OS/ROM ( this will take 3 to 4 min. after you see Samsung logo )
10. Important !!! If the device was rooted or you are trying to downgrade from NH7 or NK4 back to NC5 the device may bootloop on the startup. ( you will know this when the Samsung logo is still on the screen after 6 to 7 min. )
11. to fix bootloop pull battery then reinstall, boot into download mode and use odin to flash the OS/ROM again it will take the second time and boot up.
Let's root the phone, there is a couple of ways. First if you are running NC5 4.4.2 you can download Towel Root directly to the device here is the link http://towelroot.org/ The second way if you are running any version of KitKKat is to use odin to flash the cf-autoroot .tar, just download cf-autoroot here is the link http://autoroot.chainfire.eu/ to your PC desktop and follow the same instructions listed above just use the root file in place of the rom .tar file. Remember to choose the right root file for the version of KitKat you running so you don't trip KNOX !!!
Recoveries, the two popular ones are TWRP and Philz CWM. INSTALLING A RECOVERY WILL TRIP KNOX WARRANTY!!! You need a recovery to flash roms so you need to make choice at this point ? Here is the link to Philz CWM latest version 6.48.4.tar http://forum.xda-developers.com/showthread.php?t=2201860 and TWRP here http://teamw.in/project/twrp2/201 download to desktop or downloads.
I run a stock rooted 4.4.2 NC5 with Philz custom recovery version 6.12.9 hltespr https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ . The device was rooted and warranty tripped the second day I owned it. I was in a Sprint corporate Store a couple of wks ago. Showed the tech my rooted note 3. He said I can't touch that, I said what if I unrooted the phone. He said no problem, now I can warranty the phone. He didn't care that the KNOX flag was tripped at all 0x1. Just can't be rooted when you bring it in for service. Sprint doesn't care about KNOX only Samsung cares about KNOX. What is KNOX, KNOX is a program that creates secure encrypted containerization of DATA so it can be sent to another location. So, when Samsung paid millions to the NSA to design the KNOX security containerization system, which apparently they won't warranty will work after the device is rooted, than maybe they care. Can you say track and spy on me !!!
Ok lets install a recovery !!!
1. you need Odin on the desktop of your PC here is the link ( version 1.85 ) https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo ( version 3.07 ) http://www.mediafire.com/download/2uxt5u83qxhz6xr/Odin_v307.zip
2. you need to install Samsung drivers on your PC you can get them from here http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
3. completely power down your device, and boot into download mode (press and hold the power button, volume down button, and the home button at the same time) a new screen will popup then push the volume up button to get into download mode.
4. click on the Odin zip file and extract to desktop, right click and run as administrator
5. with your device in download mode connect it to your pc via usb cable, COM: will light up in the upper left hand corner of Odin doesn't matter what color or number just shows a connection has been made.
6. click PDA box in odin, a box will popup click where ever you have recovery file downloaded, once open it will show up in box next to PDA
7. click start wait till you see pass and success , then your custom recovery is installed.
After the recovery is installed, download a copy of SuperSu to your desktop here is the link http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip to version v2.40 and for SuperSU 2.46 go here http://forum.xda-developers.com/showthread.php?t=1538053 . Then copy and paste to sd card via USB cable. Now the next thing you are going to do is completely power down the device and boot into recovery. (press and hold the power button, volume up button, and home button at he same time) a menu will come up, click on Install Zip, then sd card to install zip and root device. Boot device and verify it is rooted, then power down, and boot into recovery. Click on backup, MAKE A BACKUP OF YOUR ROOTED ROM !!! Then make a backup of EFS file by its self it will show up in your backup file on the sd card or ext sd card depending on where you choose to put it. Copy and paste the efs file someplace safe.
With the Google Play Store download some type of root file manager like ES File Manager or Root Explorer (what I use). Then you can remove/freeze/delete some of the bloatware on your stock rooted rom. Check out this thread on Bloatware removal http://forum.xda-developers.com/showthread.php?t=2770729
OK lets flash a rom !!!
First, you CANNOT flash a rom that is based on an older version of rom you are currently running. EX: If you are on KK 4.4.2 NC5 you can flash a rom based on NAB or NC5 but you CANNOT use a rom based on mj4 or older read the OP thread carefully . You can run AOSP roms as long as they are based on 4.4+. If you are running a KK 4.4.4 based rom, you will need to odin flash a stock lollipop 5.1.1 OS. Then root the lollipop 5.1.1 OS, install a lollipop compatible recovery. Now you can flash a lollipop based rom.
1. install the new rom zip you want to flash on your sd card via usb cable from PC or download directly to device
2. power down phone completely and boot into recovery
3. from the menu find and wipe cache, delvik cache, and wipe system to install new rom, NOT FACTORY RESET !!!
4. go back to menu and click on install zip then click on where you have the zip ( i.e. sd card ) and install this will take a minute or two
5. back to main menu and reboot device this will take several minutes on the first boot of a new rom
6. enjoy your new rom !!!
Lets do a restore from a backup recovery file !!!
1. completely power down device and boot into recovery
2. go to main menu and click on wipe system to install new rom ( no need to mess with the caches on a restore )
3. back to the menu click on back up and restore, then click on the backup file location ( i.e. sd card )
4. now click on restore
5. when its completed reboot device this will install your original rooted stock rom you made a backup for
Eventually you will figure out that you can make several backups and they have really weird numbered time stamps to identify them.
If my instructions are hard to follow you can find root and recovery installation videos here http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Malware in linked odin site
That odin site is complete malware. Its not where you should get odin.
juts said:
That odin site is complete malware. Its not where you should get odin.
Click to expand...
Click to collapse
Thanks, that just happened. Looks like the site has been hacked !!!
jimzweb1 said:
Thanks, that just happened. Looks like the site has been hacked !!!
Click to expand...
Click to collapse
I have a Note 3 locked to Sprint which announce "Invalid SIM card" everytime I get the sim in and of course it doesn't have network. So I have a question 4u that after flashing this ROM am I possible to use the SIM (I'm from VN) ?
3597dxta said:
I have a Note 3 locked to Sprint which announce "Invalid SIM card" everytime I get the sim in and of course it doesn't have network. So I have a question 4u that after flashing this ROM am I possible to use the SIM (I'm from VN) ?
Click to expand...
Click to collapse
No, it's my understanding the device has to be unlocked by sprint. There is an access code to do that, I have seen it just can't remember where. I will do a little searching.
Should make a noob tutorial since people are still confused.
asim.sidz said:
Should make a noob tutorial since people are still confused.
Click to expand...
Click to collapse
I guess if people are still confused, there are a lot of youtube videos that have walk-throughs as to how to root, install recovery, and flash a ROM. Maybe some people might be visual learners?
asim.sidz said:
Should make a noob tutorial since people are still confused.
Click to expand...
Click to collapse
If my instructions are hard to follow you can watch these videos http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Great work Jimmy
Pretty lucid , these tutorials are
great stuff !!!
Cool!
jimzweb1 said:
If my instructions are hard to follow you can watch these videos http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Click to expand...
Click to collapse
Thank you very much! I cannot imagine the process to get any easier than the way demonstrated in the ways that you directed me. Really appreciate it! Thanks again! Keep up the good work and support! :highfive:
I am on 4.4.4 NH7, how can i downgrade to 4.4.2 NC5?
i am facing gps fix issues...so wanted to give it a try. any ideas?
swapyworld said:
I am on 4.4.4 NH7, how can i downgrade to 4.4.2 NC5?
i am facing gps fix issues...so wanted to give it a try. any ideas?
Click to expand...
Click to collapse
You can't and you shouldn't . Flashing nc5 might brick your phone that's why we all believe one should always wait for a few weeks before jumping on a new ota as downgrade is not possible
Sent from my NOTE 3 .. size does matter .......
lord dredd said:
You can't and you shouldn't . Flashing nc5 might brick your phone that's why we all believe one should always wait for a few weeks before jumping on a new ota as downgrade is not possible
Sent from my NOTE 3 .. size does matter .......
Click to expand...
Click to collapse
My phone came with 4.4.4, that's the problem.. I was told it is possible by odin one click method by r wilco?
Sent from my SM-N900P using Tapatalk
swapyworld said:
My phone came with 4.4.4, that's the problem.. I was told it is possible by odin one click method by r wilco?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
First, if your device came with 4.4.4 NH7 it should be possible to down grade to 4.4.2 NC5. However, is the phone new and under warranty ? If so odin flashing back to NC5 won't trip the knox e-fuse, that happens when you install a custom recovery. Here we go, first BACK UP ALL YOUR DATA TO AN EXT SD CARD OR PC !!! ( i.e. pics, music, videos etc.) From my post here is the link for odin https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo download to PC desktop. Then go to micmars and download a copy of NC5 here is the link http://forum.xda-developers.com/showthread.php?t=2712205. It is a zip file so just right click and extract it to your desktop, that will change to a .tar file in a folder. Next extract the odin zip to your PC desktop, and open the odin file as administrator. Now connect your device to your PC via a USB cable. A box will light up in the upper left hand corner COM: doesn't matter what color it is just shows a connection. Now click on the PDA box a new window will open up click on desktop then click on the NC5.tar file to open. Then the file show up next to the PDA box don't touch anything else just click start. Sit back go get a coffee it is going to take few minutes.
Now here is the fun part, if your phone boots up GREAT !!! If it doesn't, and bootloops no problem this common when going back to NC5 it happened to me. Just pull the battery, then reinsert battery, and boot into your stock recovery ( hold the power button, volume up button, and menu button at he same time) once there navigate to factory reset with the volume button and click on factory reset with power button. Finally the phone should boot into NC5, now go to settings/general/about phone and see what version you have.
If you are still on NH7 no problem, it didn't stick go through the process again. Others have had the same thing happen to them, and it took the second time, in the end it's worth it.
I had all kinds of problems on NH7 and so have many others, I went back to NC5 and have had no problems, I'm going to stay here and wait till android 5.0 (lollipop) comes out. Enjoy !!!
Jimzweb1
You sent me here for the thread "How to root Galaxy Note 3".
Thing is, I know how to use CF Auto Root, but I'm pretty green even at that. Maybe a total of 10 phones for my family.
I took root off a Note 3 (sm-n900p) by upgrading to the new firmware (NK4). It was having issues and he wanted to go back to a stock. Now he needs root again and chainfire doesn't list a file for the NK4.
Chainfire says he needs a image file from the update to add to his list, but I do not have it. He also states that in most cases, root will work on the new firmware. But if does not, that's where things go black, what to expect and how to recover?
And from what I read, I can't go back to an early firmware?
Your help would be greatly appreciated, thanks.
btb601 said:
Jimzweb1
You sent me here for the thread "How to root Galaxy Note 3".
Thing is, I know how to use CF Auto Root, but I'm pretty green even at that. Maybe a total of 10 phones for my family.
I took root off a Note 3 (sm-n900p) by upgrading to the new firmware (NK4). It was having issues and he wanted to go back to a stock. Now he needs root again and chainfire doesn't list a file for the NK4.
Chainfire says he needs a image file from the update to add to his list, but I do not have it. He also states that in most cases, root will work on the new firmware. But if does not, that's where things go black, what to expect and how to recover?
And from what I read, I can't go back to an early firmware?
Your help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
First you have a S5 not a note 3 but other than size they are basically the same. Read the post above yours, the same thing will probably happen to you don't panic !!! I have to go to work will be back tonite if you want to wait so I can help as you do it or you can try it yourself even you loop it (like what happened to me and most people ) don't panic just follow the instructions in post # 14. You need a clean copy of NE5 go here enter SM-G900P in search on right, you will have to register but its free , I don't see a XDA site for stock NE5 so here is the link http://www.sammobile.com/firmwares/ enjoy !!!
jimzweb1 said:
First you have a S5 not a note 3 but other than size they are basically the same. Read the post above yours, the same thing will probably happen to you don't panic !!! I have to go to work will be back tonite if you want to wait so I can help as you do it or you can try it yourself even you loop it (like what happened to me and most people ) don't panic just follow the instructions in post # 14. You need a clean copy of NE5 go here enter SM-G900P in search on right, you will have to register but its free , I don't see a XDA site for stock NE5 so here is the link http://www.sammobile.com/firmwares/ enjoy !!!
Click to expand...
Click to collapse
LOL, I know I'm getting old and senile. Been called all kind of mean names and all, but I do believe I know what phone I'm working on. And thanks for the help, maybe a rain check for now. It's not my phone and he's not here.
Have a happy new year, as for me, I'm old and tired and going to bed.
btb601 said:
LOL, I know I'm getting old and senile. Been called all kind of mean names and all, but I do believe I know what phone I'm working on. And thanks for the help, maybe a rain check for now. It's not my phone and he's not here.
Have a happy new year, as for me, I'm old and tired and going to bed.
Click to expand...
Click to collapse
Sorry about that, I'm no spring chicken either. I'm sure you know what phone you have, I only based my statement on the firmware name (NK4). If you want try in the future I would glad to try and help !!! You will find as I have that here on XDA there is always someone to lend a hand !!!
jimzweb1 said:
Sorry about that, I'm no spring chicken either. I'm sure you know what phone you have, I only based my statement on the firmware name (NK4). If you want try in the future I would glad to try and help !!! You will find as I have that here on XDA there is always someone to lend a hand !!!
Click to expand...
Click to collapse
Yeah, I kind of figured that, plus the the model number is one letter different too. I would only try it if you are sure I won't lock up his phone using CF Auto root. I've been at this since the 27th, even throw money at chainfire, although I doubted that would do anything. I needed to donate anyway to show some support for his work.
My other question, can I put it back to the firmware he was on? It's was 4.4.4 (NH7). Then I could root his phone if I can't do it as you said in post #14.
btb601 said:
Yeah, I kind of figured that, plus the the model number is one letter different too. I would only try it if you are sure I won't lock up his phone using CF Auto root. I've been at this since the 27th, even throw money at chainfire, although I doubted that would do anything. I needed to donate anyway to show some support for his work.
My other question, can I put it back to the firmware he was on? It's was 4.4.4 (NH7). Then I could root his phone if I can't do it as you said in post #14.
Click to expand...
Click to collapse
No guarantee it won't bootloop !!! I did on my note 3, you just have to take a step back and keep going. Let me give you an overview, but then you need to follow the individual steps in my first post for each part you need to do.
Ok, the first thing you are going to do is BACK UP ALL THE DATA ON THE DEVICE !!! I.E. music, pics, and videos. These are found on the internal sd card copy and paste them on the desktop of your PC.
Now download Odin to your desktop and extract it. (get the link in 1st post) Download a fresh copy of NH7 4.4.4 to your desktop (get the link in 1st post) and extract it. Now follow the instructions in the first post to flash a stock rom. Let it boot up, if it bootloops take off the back and pull the battery. Let it sit for two minutes, replace the battery and hold the power button, volume up button, and the menu button at the same time. It should boot into a stock recovery, if it DOES use the volume button to navigate to factory reset and push the power button. Let device reboot this will take a couple of minutes. Now go to settings/general/about device and see what version of KK you are running.
If it DOES NOT boot into a stock recovery, and goes back to your custom recovery or bootloops. No problem, pull the battery let it set for a couple of minutes reinstall battery then hold the power button, volume down button, and menu button at the same time and boot into download mode. Go to the first post and flash the rom again it will stick the second time.
Once you are back to bone stock 4.4.4 NH7 just follow the first post for rooting and recoveries. I know this is your friend's device and you don't want to mess it up. So before you try anything check here http://autoroot.chainfire.eu/ go to SM-G900P NK4 and try the CF-auto root for the s5. The s5 and note 3 are pretty much the same. You can try to flash the root through odin the worst that can happen is it will fail and not install. Then you are back to try and going back to 4.4.4 NH7.
I have been trying to switch from TWRP to CWM but every time it always ended up with "Secure Fail Kernel" message. So, after many hours of frustrations, I have tried EZ-Unlock to unlock my bootloader, which was a very bad idea.
So, phone is dead now. Power button does not do anything... So, my last hope, before paying for JTAG services, is to try to boot from a unbrick file from sdcard. So, if someone would kindly post/upload/PM the S4 unbrick file, I would appreciate it..
16GB Verizon SCH-I545 S4
ME7 with TWRP
ROM - 4.4.4 Dan&Ktoonsez CM (final) 09-18-2014
How to save your bootloader image (unbrick file) so that you could upload:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=131072
xdatufoz said:
I have been trying to switch from TWRP to CWM but every time it always ended up with "Secure Fail Kernel" message. So, after many hours of frustrations, I have tried EZ-Unlock to unlock my bootloader, which was a very bad idea.
So, phone is dead now. Power button does not do anything... So, my last hope, before paying for JTAG services, is to try to boot from a unbrick file from sdcard. So, if someone would kindly post/upload/PM the S4 unbrick file, I would appreciate it..
16GB Verizon SCH-I545 S4
ME7 with TWRP
ROM - 4.4.4 Dan&Ktoonsez CM (final) 09-18-2014
How to save your bootloader image (unbrick file) so that you could upload:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1024 count=131072
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2560961 be warned if you use the wrong bootloader you may trip the aboot counter and permanently lock it so you can't run custom kernels/recovery EVER AGAIN THERE IS NO GOING BACK IF YOU DO THIS~ tho I fear its to late for that now
trying to go from twrp to cmw is unpossible whatever possessed you to try and use a GS3 utility on a GS4 congrats you get the Darwin award
if you send it out to be jtagged you will lose custom recovery forever unless they flash the exact bootloader which I assume is MDK and you are running ME7 baseband on a loki'd MDK bootloader
I don't know what possessed me to do that. It was middle of the night and I was desperate...
Anyways, trying to move forward... So, I have already tried the debrick file in that URL. It didn't work because I suspect that's for MJ7.
You said "exact bootloader which I assume is MDK and you are running ME7 baseband on a loki'd MDK ". Does that mean I need MDK or ME7 debrick file - I thought I needed ME7.
Can anyone help out and dump their bootloader image please... I am without a phone!... Use the command below to dump bootloader:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=1024 count=131072
anyone? can someone post their MDK bootloader please...
Dump via the command below:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=1024 count=131072
xdatufoz said:
anyone? can someone post their MDK bootloader please...
Dump via the command below:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=1024 count=131072
Click to expand...
Click to collapse
did you try and boot into download mode with the bootloader image in that thread it can take several trys
I don't have a MDK phone available
Using a 32GB microSD card,I wrote the backup.bin to the SD card via Win32 Disk Iimager. Then I tried to power on using different combinations, vol up/down/home/power... Nothing... Unless, I misunderstood the instructions, that image is not working. Another issue might be that I need a 16GB card to match my internal storage.... I did use Partition Wizard to carve out 16384MB FAT32 to mimic a 16GB card but no luck...
Do you think I can extract and use the recovery images from the link below on my SDCard?
http://forum.xda-developers.com/showthread.php?t=2637686
Thanks again,
xdatufoz said:
Using a 32GB microSD card,I wrote the backup.bin to the SD card via Win32 Disk Iimager. Then I tried to power on using different combinations, vol up/down/home/power... Nothing... Unless, I misunderstood the instructions, that image is not working. Another issue might be that I need a 16GB card to match my internal storage.... I did use Partition Wizard to carve out 16384MB FAT32 to mimic a 16GB card but no luck...
Do you think I can extract and use the recovery images from the link below on my SDCard?
http://forum.xda-developers.com/showthread.php?t=2637686
Thanks again,
Click to expand...
Click to collapse
size of the card doesn't matter don't mess with the partitioning that will screw it up reformat the card as fat 32
the combonation is always as follows
insert sd card containing image
power button and volume down
retry until you get into download mode
honestly I don't know what the process is for recovering a loki'd phone via MDK when you have managed to toast the bootloader
I would assume you would flash a ODIN package containing the MDK bootloader with the ME7 baserom..
wait for somebody that knows what they are doing to post don't be tinkering with stuff without knowing what you are doing thats what got you here
if you where running a custom kernel it means you where using loki and your bootloader must have been MDK because there is no other option
and no you can't use developer edition stuff on a VZW phone
pokes @Surge1223
Those big red letters for Developer Edition only is tough to miss.. So, yeah, that's not for my phone..
" Do you think I can extract and use the recovery images from the link below on my SDCard? http://forum.xda-developers.com/show....php?t=2637686 "
I just installed Cygwin so that I could dd the img file to the sdcard instead of using the win32 disk imager. Still, no luck. I feel that the MJ7 image file on that thread is not what I need. I need a MDK bootloader image. Anyone?
I am going nuts. Probably tried to power on above 200 times or more... Yes, I am ok with TWRP or no recovery. If I get any vibration/light out of my phone, I ll take it...
btw, can I use any of these files in this URL to boot from the SD card?
http://forum.xda-developers.com/showthread.php?t=2720163
xdatufoz said:
btw, can I use any of these files in this URL to boot from the SD card?
http://forum.xda-developers.com/showthread.php?t=2720163
Click to expand...
Click to collapse
nope
you need a image of the mdk boot-loader from a Verizon i545
you also might need a different SD card
odds are you are gonna need to have it jtagged I am not even sure the Verizon version has the functionality needed to recover from a sdcard as far as I know only the GT-l9500/95004 have that functionality enabled
make sure you pull the battery between try's if the functionality does exist its only gonna try on a cold boot
IF YOU HAVE IT JTAGGED MAKE SURE YOU SPECIFY YOU WANT VRUAMDK FLASHED AND ONLY THAT ANYTHING ELSE WILL RESULT IN A PERMANENT LOSS OF ABILITY TO RUN CUSTOM NON TW ROMS
At this point, unless someone else that's an expert on this and fix it up, yeah, I would like to have it JTAG to be fixed but unfortunately the only place I know is MobileTechVideos which currently has a backlog of over 4 weeks. That's too long..
So, JTAG service would cost $50 from them but I don't want to wait that long... Anyone that could help me get the bootloader working, I would be ok donating them the money... Anyone?
I hard bricked my first S4 and found several JTAG services on eBay.
I picked the one that had the highest number of positive feedbacks and sent it off.
There was no guarantee that they would be able to restore it to MDM but they guaranteed they could unbrick it or a full refund.
They did unbrick it but unfortunately it was not MDK.
I had the phone back in less than a week.
sent from a Galaxy S4 far far away.
Well, I have sent my S4 to mobiletechvideos and also spoke with Josh about the backlog. It seems like he wants to be on top of his business and really wants to make his customers happy. I ll keep this thread posted.
I have received my S4 today from mobiletechvideos and it is alive now!! I have worked with Josh and he has JTAG my S4 to unbrick, updated my recovery to CWM, put back my baseband to MDK again. After he has fixed my phone in under 2 days, he has sent it back via priority to me. The only reason it took this long is because when I sent him the phone, USPS delayed my package.
So, I must say, I would recommend mobiletechvideos to anyone looking to get specialized work done on their phones.
I am very happy today to have my phone back!!! ok, lets see what are the latest ROMs...
xdatufoz said:
I have received my S4 today from mobiletechvideos and it is alive now!! I have worked with Josh and he has JTAG my S4 to unbrick, updated my recovery to CWM, put back my baseband to MDK again. After he has fixed my phone in under 2 days, he has sent it back via priority to me. The only reason it took this long is because when I sent him the phone, USPS delayed my package.
So, I must say, I would recommend mobiletechvideos to anyone looking to get specialized work done on their phones.
I am very happy today to have my phone back!!! ok, lets see what are the latest ROMs...
Click to expand...
Click to collapse
Good for you!
Wish my experience would have been so good, would have saved me the hassle of selling it on eBay and then finding another MDK 32gig Verizon S4.
I'll know who to send it to if it ever happens again
if you are indeed still on MDK should just be a matter of running the loki exploite and you should be good to go
next time don't go fiddling with stuff you don't fully understand
Legitsu said:
next time don't go fiddling with stuff you don't fully understand
Click to expand...
Click to collapse
The more I learn, the more I realize how little I know. I am pretty sure that applies to you as well.
Disclaimer:
I am not responsible for anything that happens to your device after following this guide. Also, I'm not entirely sure if this works 100% for OF1, although I can guarantee that this guide works for OB6 because I just successfully rooted, unlocked the bootloader, and flashed a custom recovery onto my Galaxy Note 3 running the OB6 update.
This guide was compiled for the sole purpose of convenience for other users here on XDA Forums. My reason for making this guide was to make it as easy as possible for Verizon Galaxy Note 3 owners to root, unlock the bootloader, and flash a custom recovery without jumping from thread to thread, searching for answers.
ONLY FOLLOW THIS GUIDE IF YOU KNOW WHAT IT MEANS TO BE ROOTED, HAVE AN UNLOCKED BOOTLOADER, AND WHAT A CUSTOM RECOVERY IS USED FOR
If you are the proud owner of a Verizon Galaxy Note 3 (SM-N900V) and would like to root, unlock the bootloader, and/or flash a custom recovery onto it, you've come to the right place. Included in this guide are methods of doing these exact things, which also happen to be generally easy to perform.
Before you begin, you'll need a few things:
a Verizon Galaxy Note 3 (running OB6 or OF1, obviously)
a computer of some sort (running Windows)
a micro SD card (make sure there isn't anything on it, because it WILL be erased)
Odin 3.09 *
TWRP 3.02-1 *
ArabicTool *
eMMC Brick Bug Checker app
unlock_n3 (for unlocking the bootloader, attached) *
* place these files in a location that you know the path of. e.x. C:\ or C:\Users\...\Desktop
Once you are 100% sure that you have all of these things, continue to the rest of the guide.
Root
Open ArabicTool
Make sure your phone is connected to your computer
In ArabicTool, click on the "Version" field and select your firmware version (OB6/OF1)
Click on "Read phone info" and wait for the information above to show your phone's status
Check the logs on the bottom right to make sure that everything is correct, then click on "Root" below the "Phone info" box (if there is an error about not being on 5.0, close the app, set the compatibility mode to W7, and run as admin)
Once your phone restarts, continue to the next part of the guide
Unlocking the Bootloader
Just follow this tutorial. The consequences of messing this part up can lead to bricking your phone, although the process itself is fairly simple. Just remember that you need to unzip samsung_unlock_n3.zip and rename the file in there to unlock_n3. Follow the instructions from there.
Flashing TWRP
Honestly, this part was the easiest for me.
Unzip and open Odin 3.09
Reboot your phone into download mode (with it plugged into the computer, obviously)
In Odin, click "AP" and find the flashable TWRP tar that you downloaded earlier
Start the flashing process by clicking "Start" in the bottom right hand corner
If, after this process, your phone reboots and shows an error about the recovery partition in the top left hand corner (in blue), then goes into a bootloop:
Download the stock recovery.tar from the attached files at the bottom of this post
Open Odin again
Click "AP", find the file you just downloaded, and start the flashing again
Follow the instructions to unlock your bootloader again, but only do the second set of code. The first set is irrelevant to us at this point.
Flash TWRP onto your phone again. This time, it should work if it didn't already.
To make sure, boot your phone into recovery mode. If TWRP boots up, success (obviously )!
If you have any issues whatsoever that I haven't covered in this guide, please either PM me or reply to this thread. Also, if I have made any mistakes in outlining the instructions in this guide, do the same.
Credit to:
@androidyemen and others for finding the root method,
@ryanbg for finding the bootloader unlock method,
@beaups for finding the eMMC backdoor,
and Team Win for creating TWRP
Source posts:
[Official] Note 3 Verizon Bootloader Unlock by ryanbg
OB6 & OF1 N900V Note 3 Verizon Oneclick SuperSU Rooted Successfully
If in any case you would like to donate to me for this post (which in no way am I asking you to), here is my PayPal email:
[email protected]
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Sent from my SM-N900V using XDA-Developers mobile app
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Click to expand...
Click to collapse
I'm not entirely sure if it will work on JasmineROM 6.1 specifically, but it won't hurt your device to try. Unless your CID doesn't start with 15 for some reason. If it does, the worst that can happen is the unlock file won't work.
I'll have to edit that part when I get home. I'm only going to be gone for about 20 minutes or so.
Sent from my LG-H634 using XDA Labs
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Click to expand...
Click to collapse
It really only needs root, although the spot it looks for the eMMC CID value changed from kernel release to kernel release, so there were some minor release dependencies.
[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.
The version which seems to be most compatible with M*, N*, and O* kernels is the build posted (along with source code) in post #218 of the bootloader unlock thread.
( The newly-rebuilt version in the OP of that thread is still incompatible with 4.3 and 4.4 (M*, N*) releases. )
Man up and use your browser if the XDA app is broken.
.
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes it will, I did it already months ago when all this first came out.
Sent from my SM-N900V using Tapatalk
@jamesalynch
I know you are trying to help and everything, but you've kind of screwed the pooch in a couple of different ways. First, the binary that you attached doesn't work on any 4.3.x (M*) or 4.4.x (N*) series ROMs, and I'm not sure it ever worked even on OB1 and OF1.
Second, you should not be re-attaching files that are available in other people's posts. Just provide a link to the original post; if there is an ambiguity as to what download is desired, then describe it in your post.
Third, you should not be taking other people's downloads, unpacking them, and then renaming the included files to match filenames used elsewhere - that is only going to increase people's confusion.
Fourth, in that OP (@ryanbg 's post) he mentions re-building the code and NOT USING the version that you provided as an attachment. Unfortunately, he was in a hurry when he rebuilt the code, and even the new version he built still does not work on 4.3.x and 4.4.x ROMs.
[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.
The version that will work for everyone is in @donc113's post #218 in that thread.
Code:
$ find . -type f \( \! -name '*.zip' -a \! -name '*.c' \) -exec md5sum {} \;
[b][color=green]ea856efcb7de0ca8ff428522dbdc0267 ./donc113-post218/unlock[/color][/b] [b]<<<==== Use this for NK1 and prior.[/b]
0bcb409af65e311ce4b67faf7ed3f0af ./ryanbg0804/unlock_n3 [b]<<<==== Use this for OB6 and OF1.[/b]
cba959357ed1d0207dbde56bb6b6a1b7 ./ryanbgORIG/samsung_unlock_n3
cba959357ed1d0207dbde56bb6b6a1b7 ./JAL/unlock_n3 [b]<<<==== Your version with name change from 'samsung_unlock_n3'.[/b]
Thanks to everyone who posted. I will be going back to the post mentioned in the comments.
Sent from my SM-N900V using XDA-Developers mobile app
This is kinda confusing, to be honest.
Once bootloader is unlocked you could just download FlashFire and download and flash TWRP from there rather than using Odin.
The root tool you linked didn't work for me, even on Windows 7, granted others said it worked for them. If they are on Windows 10, there is a different tool to use.
stock recovery?
I need the stock recovery file, that you said would be attached. My phone is not booting with the Recovery warning..
Tremo419 said:
I need the stock recovery file, that you said would be attached. My phone is not booting with the Recovery warning..
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/45906/N900VVRUEOB6_N900VVZWEOB6_VZW/
Open that file and extract the recovery image. Compress it in a TAR. Flash.
Sent from my LG-H634 using XDA Labs
I have the sm-900v on 5.0 and I rooted and unlocked bootloader and twrp and flash a rom but didn't go through so I Odin stock rom back to begin fresh and now it won't root...as soon as I do the root process and it restarts my phone into stock recovery...so I clean cache and reboot and goes right back to stock recovery...can anyone help
Sent from my SM-N900V using XDA-Developers mobile app
ozz200127 said:
I have the sm-900v on 5.0 and I rooted and unlocked bootloader and twrp and flash a rom but didn't go through so I Odin stock rom back to begin fresh and now it won't root...as soon as I do the root process and it restarts my phone into stock recovery...so I clean cache and reboot and goes right back to stock recovery...can anyone help
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Firstly, if you have an unlocked bootloader, you never have to flash STOCK again.
So - after you have gotten this problem fixed - learn how to avoid using Odin with STOCK firmware bundles.
Odin can flash a custom recovery when the bootloader is unlocked. That will save you trouble in the future. You need to learn how to build Odin ".tar.md5" files. In a nutshell, for doing what I just mentioned, you take a TWRP .img file, rename it to "recovery.img", put it in a "ustar" format tar file, and then compute the md5 signature of that and append it to the end of the file. Search for "Odin md5 ustar" in these forums.
For your current problem, I can't tell exactly what you are saying. If you are saying "I am stuck in a vicious cycle of nothing but recovery reboots (the stock recovery)", then
- pull the battery and wait ten seconds
- put the battery back in
- start in download mode with Vol_Down+Home+Power. When you get the pop-up screen, select cancel.
- if it still boots into the stock recovery, the do a full wipe (yes the whole phone, data+cache) and try booting. If the same trouble persists, go back and do the Odin STOCK flash again. (You can't flash a custom recovery with a locked bootloader).
If it still doesn't work, make sure your next problem report includes far more details than the one above, for instance:
- what version of firmware was on your phone before this mess started
- what version of firmware you were trying to flash with Odin
- what version of Odin you were using
- the name of the Odin file and it's MD5 signature.
that's a start.
VZW Note 3+Root+Jasmine Rom+Partial Firmware
CID starts with 15 (verified with EMMC)
Android Ver: 5.0
N900VVRUEOF1
Ive ran the unlock countless times I gets nothing no unlock of the bootloader at all
Omegastorm said:
VZW Note 3+Root+Jasmine Rom+Partial Firmware
CID starts with 15 (verified with EMMC)
Android Ver: 5.0
N900VVRUEOF1
Ive ran the unlock countless times I gets nothing no unlock of the bootloader at all
Click to expand...
Click to collapse
It produces error messages when it encounters a problem and exits without completing it's job.
Is there some reason why you believe we should be able to intuit what those countless error messages were? (It would be simpler if you just cut-n-paste that output into your post.)
You might also want to state which version of the tool you used - there are at least 3 in the original thread.
im thinking about getting a verizon note 3.. does this work for all variants to get root, twrp and custom roms?
thanks
Jaws4God said:
im thinking about getting a verizon note 3.. does this work for all variants to get root, twrp and custom roms?
thanks
Click to expand...
Click to collapse
No
You can root all variants but can not unlock all variants, thus can't use TWRP or use custom ROMS or kernel.
Must be model SM-N900V, must have a specific Samsung eMMC (cid must start with 15) and the external SD card slot must work along with the USB port.
Sent from my SM-N900V using Tapatalk
bftb0 said:
It produces error messages when it encounters a problem and exits without completing it's job.
Is there some reason why you believe we should be able to intuit what those countless error messages were? (It would be simpler if you just cut-n-paste that output into your post.)
You might also want to state which version of the tool you used - there are at least 3 in the original thread.
Click to expand...
Click to collapse
Oh wow didn't know there was three I'm gonna go back and check that out again thanks
This is awesome man, great thanks to you. I'm new on n3 verizon, i like unleashing the power of my phone, =D
THANK YOU!
Nice post! I hadn't looked at XDA/ note 3 development in awhile. Awesome to see an exploit found! BAM!
Has anyone made a STOCK deodex/? CM is cool, but I like the S-pen. I have the n900V.
Thanks again
1Xfan said:
Nice post! I hadn't looked at XDA/ note 3 development in awhile. Awesome to see an exploit found! BAM!
Has anyone made a STOCK deodex/? CM is cool, but I like the S-pen. I have the n900V.
Thanks again
Click to expand...
Click to collapse
There are some Stock out there:
[LP] [5.0] [RE/DE] [Xposed] [MultiSystem] JasmineROM v6.1
mostly stock N900VVRUEOF1[debloated/deodexed/wifi fixed]
So, I cobbled together a (custom-recovery) flashable NC4 stock ROM.
I'm interested to find out whether it is possible to boot it successfully from later bootloader firmware - e.g. NK1, OB6, or OF1
(I'm still on NC4 bl and not planning on upgrading near term. It boots on NC4 bl but that's pretty obvious lol)
[size=+2]Q: Why would this be useful?
A: to provide a means for upgrading bootloader firmware without starting from scratch.[/size]
For instance, there are folks on OB6 firmware that would like to use a custom ROM that will only work on OF1 firmware. They can certainly start from scratch (backup and unload the entire device); an alternative would be to:
- Make a backup of an existing rooted ROM (that more than likely has a custom or modified boot image so is not bootable when the bootloader gets re-locked) using the currently-installed custom recovery (which will also be non-bootable under re-lock).
- Restore a (debloated) pure stock ROM w/ Samsung kernel. Root it with Towelroot (does not touch boot image)
- Flash replacement bootloader only in Odin. Locked bootloader = no custom recovery... but with a rooted stock ROM already in place with an unmodified stock kernel it can be immediately unlocked.
NC4 is easily rooted with Towelroot-v3 "on device". No need for PC drivers, online rooting tools with a separate PC, etc (e.g. as with Yemen rooting methods on OB6, OF1)
This approach in principle saves the need to backup everything up in the /sdcard - but you have to know in advance that the NC4 stock kernel and ROM can successfully be booted with later bootloaders.
So anyway, that's what I'm asking for help testing with - folks that are: (a) unlocked and (b) on NK1, OB6 or OF1 bootloader willing to try flashing a debloated NC4 Stock ROM using their existing custom recovery, and see if it boots, roots, and if root survives a single boot cycle.
Contact me via this thread or PM; I'll provide the flashable NC4 and the Towelroot .apk
.
my n900v came with 5.0 Of1 but i rooted, unlocked BL. installed twrp and flashfired NC4 tar minus recovery
runs smooth.I hate lollipop.lol
only bug is wifi password resets everytime i reboot
im curious as to why i have trouble running certain nc2/nc4 roms..some want to bootloop/freeze
baja,biggins,and objective rom
kernel issue maybe? or BL version
btw. i am rooted via towelroot v3
hotrod85z said:
my n900v came with 5.0 Of1 but i rooted, unlocked BL. installed twrp and flashfired NC4 tar minus recovery
runs smooth.I hate lollipop.lol
Click to expand...
Click to collapse
Thank you for posting that, very useful/helpful information to know.
Does Flashfire understand the Samsung "sparse" image format of the system.img.ext4 file inside the Stock (Odin) .md5 tarfile blob? Or maybe somebody else packaged up a "flashable .zip" of NC4?
hotrod85z said:
only bug is wifi password resets everytime i reboot
Click to expand...
Click to collapse
in /system/build.prop, set ro.securestorage.support=false and reboot. You might also want to set ro.config.tima=0 as well.
I suspect that mixing and matching Samsung kernels with bootloader versions breaks something in the TrustZone, and so secure containers and other sort-of-obscure security functions no longer work as the TZ smells something fishy. I am using a rooted PL1 rom on NC4 bl and it would spontaneously reboot (infrequently) until I made the above changes - it's been rock stable for about 4 days now. Why this works I can't really say - it's a "generation skipping" bootloader and stock rom combination - N* bootloader and P* ROM *
hotrod85z said:
im curious as to why i have trouble running certain nc2/nc4 roms..some want to bootloop/freeze
baja,biggins,and objective rom
kernel issue maybe? or BL version
btw. i am rooted via towelroot v3
Click to expand...
Click to collapse
all of the above or none of the above LOL
There are definitely some mysteries here, and I don't claim to fully understand the interdependence of the TZ (== bootloader firmware), the TIMA and RTKP stuff in the kernel, and the cross-communication between kernel and TZ via the qseecom service daemon (which is in the ROM in /system/bin) much less how the APIs of all these interfaces might have changed between major releases.
You could check those two build.prop settings in those ROMs for starters though. I suspect that if the TZ smells something fishy (e.g. a kernel TIMA to TZ info mismatch), a variety of secure credential services in the TZ stop working. It is possible that "ro.securestorage.support" is a toggle that attempts to use TZ services when it is set to "true", and so anything in the ROM which builds on it breaks because the TZ is refusing to play on an otherwise "stock" ROM variant.
FWIW I got the AryaMod (S7Edge MM port) + phantom kernel running on NC4 bl + OF1 modem for a full 24 hours after I disabled the qseecom service daemon. It ran long enough that I had customized the whole thing as a daily driver with all my apps, verified that all sensors & radios worked, made test calls, etc. Rebooted it and the kernel started getting reset by a "Modem Reset". Even weirder was that despite the use of the OF1 "modem" firmware, the kernel was reporting a bunch of RIL "unknown ioctl's". Strikes me as odd that the whole thing could run that long with so many different things happening, and then the "modem" is unhappy - even though other folks are using the ROM with OF1 bl + OF1 radio/modem firmware. (As if the "modem" isn't really the source of the problem, even though that's what initiates the device reset).
.
i initially tried flashing NC4 full tar via ODIN. but even bl unlocked. i got FAIL. flashfire worked!
very curious as to whether a custom n900v kernel would boot my 4.4.2 custom roms..its either that or the BL isnt compatible with non-touchwiz roms....
most of the kernel/modem/firmware links on here are 404 error dead links.. would be nice to see an up to date sticky. ill flash anything as long as i dont end up in JTAG mode with a brick.lol
ive played with verizon s5 atnt s2,galaxy capitivate,atrix 4g and many other phones
the s2 is still by far the fastest Smoothest phone on cm7..the newer the phones..the newer the OS..the bigger the resourse hogs"ram" im a minimalist...
even after flashing NC4 official full tar..im still showing OF1 baseband under settings
@hotrod85z
FWIW I posted a bunch of recovery-flashable stock ROMs here.
There is also a link in that thread to a complete set of (Odin flashable) modems for NC4, NJ6, NK1, OB6, OF1, and PL1 if that is of interest to you.
Maybe I wasn't paying attention, but I could swear that on at least one occasion or two when I performed an Odin modem flash, it didn't "stick", despite no complaints on the handset screen or in Odin - the next boot showed the (prior) baseband version, not what I flashed. Its a bit of a mystery to me; but for now I've resolved to make sure that after the Odin session is complete, I wait 30 seconds or so, then remove the USB cable, and then pull the battery rather than try to restart the device by holding buttons down. It is possible that those events occurred when I soft-restarted the phone, but I'm not sure. For now I'm just trying to always flash and restart with exactly the same method to avoid different behaviors from creeping in.
PS I have no idea if those ROM flashables are compatible with Flashfire. They might be, but I've never tested it, and as they are not pre-rooted I'm not going to suggest it for fear that somebody with a rooted but locked (bootloader) phone will try using flashfire and then end up with a phone that needs a full Odin re-install. Appearances are that each version of the bootloader restricts the Samsung signing verification to only the matching kernel version - you can't even boot a Signed samsung kernel on a locked phone if it is a different version than the bootloader's version.
Hello all I have a emmc exploit note 3 I'm using here and I wanted to flash different radios for the us carrier note 3's and I first tried to use flash fire to try to update the modem, but even that didn't stick, cause I don't readily have a pc available, I wasn't ballsy enough to flash a different carrier modem, since I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode and I didn't want a brick, so overall my question is, do I need a unlocked bootloader to flash different modems and do I need odin tovdo it or will some sort of mobile odin or something do it? Thanks mates and happy flashing.
Dlind said:
Hello all I have a emmc exploit note 3 I'm using here and I wanted to flash different radios for the us carrier note 3's and I first tried to use flash fire to try to update the modem, but even that didn't stick, cause I don't readily have a pc available, I wasn't ballsy enough to flash a different carrier modem, since I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode and I didn't want a brick, so overall my question is, do I need a unlocked bootloader to flash different modems and do I need odin tovdo it or will some sort of mobile odin or something do it? Thanks mates and happy flashing.
Click to expand...
Click to collapse
Well, your question is way off topic for this thread.
But since nobody is in here anyways, I guess I'll answer the parts that I am able to.
The modems that I posted over in that other thread were meant to be flashed in Odin using a PC. You can use either the AP slot or CP slot. Note that the very first post says - in big bold blue letters "Odin-flashable Modems".
Not flashfire. It never said anything about flashfire.
Is there such a thing as MobileOdin? If there is, I know nothing about it and certainly have never tested anything with it. So I don't know and am not going to speculate.
You said something confusing here:
Dlind said:
I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode
Click to expand...
Click to collapse
If it says "MODE: Developer" you have an unlocked bootloader. Which is exactly the same thing as a Developer Edition phone.
If you were to use a PC with Odin and you flashed a FULL Stock firmware flash, yes it would overwrite the unlocked bootloader and indeed re-lock the phone. If you were able to re-root that (stock) ROM, you could perform the unlocking procedure again to unlock it.
On the other hand, those Odin-flashable modem packages do not contain the bootloader firmware, so if you were to use Odin on a PC to flash just those modem images, your bootloader would not get re-locked - the unlocked bootloader is still there, untouched.
When the carriers issue an OTA update, many times (perhaps most of the time) they contain a modem update (NON-HLOS.bin and modem.bin). So it is obvious that they are able to be flashed **somehow** right on the phone, without using Odin from the PC or an "Odin app" at all.
BUT that happens using a combination of the STOCK recovery and the bootloader itself during the reboot following the actions taken by the STOCK recovery. (My guess is that the recovery simply "stages" it into place, and sets some flags so that the bootloader knows that it is supposed to evaluate the crypto signatures of the file blobs that the recovery put into place and it is actually the bootloader that does the flashing. That's really not a whole lot different than what happens when you transfer files from Odin to the phone - the "Odin/Download" mode is just one of the personalities of the bootloader. (Odin is actually a rather dumb program - it's the bootloader on the phone that gets to decide whether a flash happens. It does that by carefully examining the file blob that gets transferred, e.g. crypto signature checks)
My guess is that you would be able to flash STOCK modem packages from Odin (using a PC) independent of whether the bootloader is locked or unlocked. But as I said: "guess".
I don't have a second phone to test with, so I would have to flash completely back to stock and lock my bootloader to be able to test that hypothesis. That's a big jobs because of all the crap I have to backup and restore to my phone.
Frankly, if you don't have access to a PC, and you really need your device to keep working, I would advise you to stop screwing around with it, simply because you don't have good tools available to fix it if a disaster occurs.
PS. I've never once noticed anything different between various radio firmwares on ANY device I've ever owned.
bftb0 said:
Well, your question is way off topic for this thread.
But since nobody is in here anyways, I guess I'll answer the parts that I am able to.
The modems that I posted over in that other thread were meant to be flashed in Odin using a PC. You can use either the AP slot or CP slot. Note that the very first post says - in big bold blue letters "Odin-flashable Modems".
Not flashfire. It never said anything about flashfire.
Is there such a thing as MobileOdin? If there is, I know nothing about it and certainly have never tested anything with it. So I don't know and am not going to speculate.
You said something confusing here:
If it says "MODE: Developer" you have an unlocked bootloader. Which is exactly the same thing as a Developer Edition phone.
If you were to use a PC with Odin and you flashed a FULL Stock firmware flash, yes it would overwrite the unlocked bootloader and indeed re-lock the phone. If you were able to re-root that (stock) ROM, you could perform the unlocking procedure again to unlock it.
On the other hand, those Odin-flashable modem packages do not contain the bootloader firmware, so if you were to use Odin on a PC to flash just those modem images, your bootloader would not get re-locked - the unlocked bootloader is still there, untouched.
When the carriers issue an OTA update, many times (perhaps most of the time) they contain a modem update (NON-HLOS.bin and modem.bin). So it is obvious that they are able to be flashed **somehow** right on the phone, without using Odin from the PC or an "Odin app" at all.
BUT that happens using a combination of the STOCK recovery and the bootloader itself during the reboot following the actions taken by the STOCK recovery. (My guess is that the recovery simply "stages" it into place, and sets some flags so that the bootloader knows that it is supposed to evaluate the crypto signatures of the file blobs that the recovery put into place and it is actually the bootloader that does the flashing. That's really not a whole lot different than what happens when you transfer files from Odin to the phone - the "Odin/Download" mode is just one of the personalities of the bootloader. (Odin is actually a rather dumb program - it's the bootloader on the phone that gets to decide whether a flash happens. It does that by carefully examining the file blob that gets transferred, e.g. crypto signature checks)
My guess is that you would be able to flash STOCK modem packages from Odin (using a PC) independent of whether the bootloader is locked or unlocked. But as I said: "guess".
I don't have a second phone to test with, so I would have to flash completely back to stock and lock my bootloader to be able to test that hypothesis. That's a big jobs because of all the crap I have to backup and restore to my phone.
Frankly, if you don't have access to a PC, and you really need your device to keep working, I would advise you to stop screwing around with it, simply because you don't have good tools available to fix it if a disaster occurs.
PS. I've never once noticed anything different between various radio firmwares on ANY device I've ever owned.
Click to expand...
Click to collapse
Thanks SOOOOOO MUCH for your input I kinda had a feeling that the idea was risky at first and I don't know a whole lot about odin and I wish Samsung could have created something much easier to use, but thanks for answering the wayyyyy off topic question, I'm gonna smash that thanks button, I'm also going to take the advise on not cross flashing different modems, its just to risky. You answered all my questions so thanks, Also I want to say thank you for your continued work on this phone is by normal terms "old" now but in reality its still an amazing phone with the right custom software, and happy flashing!