Database Info

[Q] my phone is restar after softwear

I install new software to my mobile when it finish the mobile restart after Galaxy S logo and don't boot to the home screen
Any one have idea what I do ???
I install the software with odin3 program
plz help i don't have any id to do

stevoo123oo said:
I install new software to my mobile when it finish the mobile restart after Galaxy S logo and don't boot to the home screen
Any one have idea what I do ???
I install the software with odin3 program
plz help i don't have any id to do
Click to expand...
Click to collapse
I would start by reading this post.
http://forum.xda-developers.com/showthread.php?t=1437548

psal217050 said:
I would start by reading this post.
http://forum.xda-developers.com/showthread.php?t=1437548
Click to expand...
Click to collapse
i read it and i do this step be step
i think the problem in boot file !
if i want to make completed format and software for mobile can any one help me ???

stevoo123oo said:
I install new software to my mobile when it finish the mobile restart after Galaxy S logo and don't boot to the home screen
Any one have idea what I do ???
I install the software with odin3 program
plz help i don't have any id to do
Click to expand...
Click to collapse
What ROM are you on? What ROM are you trying to flash? Which version of CWM do you have?
Give us as much info as possible.

thanx
psal217050 said:
What ROM are you on? What ROM are you trying to flash? Which version of CWM do you have?
Give us as much info as possible.
Click to expand...
Click to collapse
it was in 4.2 and want downlode the orginal kernal 2.3

stevoo123oo said:
it was in 4.2 and want downlode the orginal kernal 2.3
Click to expand...
Click to collapse
you need a return to stock package using either odin or heimdall. these are flashed in the phone's download mode.
look in here:
http://forum.xda-developers.com/showthread.php?t=1610374

qkster said:
you need a return to stock package using either odin or heimdall. these are flashed in the phone's download mode.
look in here:
http://forum.xda-developers.com/showthread.php?t=1610374
Click to expand...
Click to collapse
i try Odin3 v1.85 and Odin3 v3.04
plz can you send to me you MSN MESSENGER or any one to chat with you and ask you some question
thanx alot

stevoo123oo said:
i try Odin3 v1.85 and Odin3 v3.04
plz can you send to me you MSN MESSENGER or any one to chat with you and ask you some question
thanx alot
Click to expand...
Click to collapse
make this work:
http://forum.xda-developers.com/showthread.php?t=1524081
read the op. use of diff pc or usb cord or usb port

qkster said:
make this work:
http://forum.xda-developers.com/showthread.php?t=1524081
read the op. use of diff pc or usb cord or usb port
Click to expand...
Click to collapse
http://www12.0zz0.com/2013/03/22/18/6[IMG]
[url=http://www.0zz0.com][img]http://www12.0zz0.com/2013/03/22/18/656423228.png[/IMG]56423228.png[/img][/url]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url][/IMG]
this is pic for my Mobil and the program

I think you got it back to stock..which ever package you used.
You used Odin..not Heimdall. I haven't used Odin in a while
If you can use Odin, I recommend using option C via Odin
http://forum.xda-developers.com/showthread.php?t=1613523

qkster said:
I think you got it back to stock..which ever package you used.
You used Odin..not Heimdall. I haven't used Odin in a while
If you can use Odin, I recommend using option C via Odin
http://forum.xda-developers.com/showthread.php?t=1613523
Click to expand...
Click to collapse
ok i well try it now and told you what happened
thanx

qkster said:
I think you got it back to stock..which ever package you used.
You used Odin..not Heimdall. I haven't used Odin in a while
If you can use Odin, I recommend using option C via Odin
http://forum.xda-developers.com/showthread.php?t=1613523
Click to expand...
Click to collapse
this is video after i install the C OPTION and this is the mobile mad restart after restart
http://youtu.be/gWXBMtJ21Gc
THANX

stevoo123oo said:
this is video after i install the C OPTION and this is the mobile mad restart after restart
http://youtu.be/gWXBMtJ21Gc
THANX
Click to expand...
Click to collapse
do a 3 finger boot into recovery.
factory reset
pull battery
put it back into download mode
flash again

qkster said:
do a 3 finger boot into recovery.
factory reset
pull battery
put it back into download mode
flash again
Click to expand...
Click to collapse
i try this step and same problem
i don't know where is the problem is ???????:crying:

stevoo123oo said:
i try this step and same problem
i don't know where is the problem is ???????:crying:
Click to expand...
Click to collapse
What exactly did you put in the bootloader section?
Typically, you unzip the Odin files and drop each one in the corresponding section... Review jscott30's UCLB3 Odin OP for complete instructions...
Sent from my SAMSUNG-SGH-I997 using xda premium

ThANX
Zen Arcade said:
What exactly did you put in the bootloader section?
Typically, you unzip the Odin files and drop each one in the corresponding section... Review jscott30's UCLB3 Odin OP for complete instructions...
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
where can i find the UCLB3 and i unzip the file and have on file :fingers-crossed:
ODIN-UCLB3-GB-stock-zImage.tar
and i install it if u give me the link and i u give me any Email to chat withe you i can give you accesses to my computer and try tougher to see the problem

That file contains only the stock kernel file which needs to be extracted before it can be flashed. Note that for any of Odin packages you need to use 7zip or other archive program to extract the files needed to complete the task. If the files saved to disk don't end in "md5" you haven't extracted them yet.
Since it appears you got at least part of the way to JB-4.2, you will need to load a stock firmware package that includes a PIT (partition) file in order to get back to working stock config.
Visit this thread - http://forum.xda-developers.com/showthread.php?t=1705260
Choose whether you want rooted or stock firmware - either way you will have stock recovery and won't be able to flash other firmwares (ROMs, MUFs, etc). Follow the instructions exactly as shown in the OP. If successful you should be able to boot the phone with a brand new config.
If you later decide you want to flash custom firmware, you will need to flash a kernel with red CWM recovery. The Odin kernel packages are located here:
http://forum.xda-developers.com/showthread.php?t=1698367
For GB ROMs just follow the instructions in the associated OP.
For JB, andros11 published a good guide on how to get from GB with CWM(red) recover to JB - http://forum.xda-developers.com/showthread.php?t=1878458
-----
If you decide you don't like Odin anymore, there is another way, using Heimdall - http://forum.xda-developers.com/showthread.php?t=1524081
Kernels with red CWM recovery are in posts 2 & 3 of this thread.
Either way - read carefully, follow instructions exactly, and if necessary, repeat. Exercise care if flashing bootloaders - make sure you have a reliable USB cable, connection, and PC before starting. (This step only necessary if recovery mode looks like garbage, rainbows, unicorn farts, etc..)
Good luck and happy flashing!

Zen Arcade said:
That file contains only the stock kernel file which needs to be extracted before it can be flashed. Note that for any of Odin packages you need to use 7zip or other archive program to extract the files needed to complete the task. If the files saved to disk don't end in "md5" you haven't extracted them yet.
Since it appears you got at least part of the way to JB-4.2, you will need to load a stock firmware package that includes a PIT (partition) file in order to get back to working stock config.
Visit this thread - http://forum.xda-developers.com/showthread.php?t=1705260
Choose whether you want rooted or stock firmware - either way you will have stock recovery and won't be able to flash other firmwares (ROMs, MUFs, etc). Follow the instructions exactly as shown in the OP. If successful you should be able to boot the phone with a brand new config.
If you later decide you want to flash custom firmware, you will need to flash a kernel with red CWM recovery. The Odin kernel packages are located here:
http://forum.xda-developers.com/showthread.php?t=1698367
For GB ROMs just follow the instructions in the associated OP.
For JB, andros11 published a good guide on how to get from GB with CWM(red) recover to JB - http://forum.xda-developers.com/showthread.php?t=1878458
-----
If you decide you don't like Odin anymore, there is another way, using Heimdall - http://forum.xda-developers.com/showthread.php?t=1524081
Kernels with red CWM recovery are in posts 2 & 3 of this thread.
Either way - read carefully, follow instructions exactly, and if necessary, repeat. Exercise care if flashing bootloaders - make sure you have a reliable USB cable, connection, and PC before starting. (This step only necessary if recovery mode looks like garbage, rainbows, unicorn farts, etc..)
Good luck and happy flashing!
Click to expand...
Click to collapse
ok i well try in this moment to do i well do all the step in the link and used odin
when it finsh i well told you what happend
thannnnnnx alot

Zen Arcade said:
That file contains only the stock kernel file which needs to be extracted before it can be flashed. Note that for any of Odin packages you need to use 7zip or other archive program to extract the files needed to complete the task. If the files saved to disk don't end in "md5" you haven't extracted them yet.
Since it appears you got at least part of the way to JB-4.2, you will need to load a stock firmware package that includes a PIT (partition) file in order to get back to working stock config.
Visit this thread - http://forum.xda-developers.com/showthread.php?t=1705260
Choose whether you want rooted or stock firmware - either way you will have stock recovery and won't be able to flash other firmwares (ROMs, MUFs, etc). Follow the instructions exactly as shown in the OP. If successful you should be able to boot the phone with a brand new config.
If you later decide you want to flash custom firmware, you will need to flash a kernel with red CWM recovery. The Odin kernel packages are located here:
http://forum.xda-developers.com/showthread.php?t=1698367
For GB ROMs just follow the instructions in the associated OP.
For JB, andros11 published a good guide on how to get from GB with CWM(red) recover to JB - http://forum.xda-developers.com/showthread.php?t=1878458
-----
If you decide you don't like Odin anymore, there is another way, using Heimdall - http://forum.xda-developers.com/showthread.php?t=1524081
Kernels with red CWM recovery are in posts 2 & 3 of this thread.
Either way - read carefully, follow instructions exactly, and if necessary, repeat. Exercise care if flashing bootloaders - make sure you have a reliable USB cable, connection, and PC before starting. (This step only necessary if recovery mode looks like garbage, rainbows, unicorn farts, etc..)
Good luck and happy flashing!
Click to expand...
Click to collapse
thamx thanx it,s work :angel:
i have tow Question plz
1 the wireless is to poor and far i set near the router and network is far i am in Egypt is the any different in wireless or can do any thing for this problem
and the to and final the new software don,t have Arabic Language do u have any id to install the Language
and thanx thanx :good:

I'm glad it worked out for you.
I am not certain, but I think Aeon, Legend, and Emancipation support Arabic. These are all GB roms. There may be others.
I recommend you search the development forum to see what is available.
Sent from my SAMSUNG-SGH-I997

[GUIDE][N9005][TOUCHWIZ] From 4.3 to 4.4.2 NA6 Without any Data Lost!

HOW TO INSTALL A 4.4.2 TOUCHWIZ ROM OVER A 4.3 ONE WITHOUT DATA LOST​
REQUIREMENTS:
-Note 3 (N9005 model only!)
-Computer (with windows)
-Installed driver (install Kies, driver will be installed automatically)
-An USB cable
-This zip file: Download
-CWM Recovery: Download
-A 4.4.2 NA6 Touchwiz rom, choose and download it from Galaxy Note 3 Android Development section.
Click to expand...
Click to collapse
IMPORTANT:
1)You can follow this guide only as a N9005 user. Other Note 3 models will probably be destroyed.
2)I’m not responsible of what happends to your terminal. I updated my Note 3 doing these steps and it worked for me. If you follow my guide step by step, you will not fail. Do this update only if you know what are you doing.
3)Remember that updating bootloader to 4.4.2 will not allow to come back to 4.3 touchwiz roms or bootloader and will not allow to install 4.4.2 aosp-based roms.
Click to expand...
Click to collapse
LET’S START!
1) Extract the downloaded “Note3_Update_BootLoader.zip” file. I suggest to make a new folder and to drag and drop all the zip contnent into it. Copy downloaded “n9005-cwm-recovery-6.0.4.7-kk(0125).tar” file in the same folder.
2) Put you phone in download mode (turn it off and then hold down power button, volume – button and home button together until something shows on the phone screen. Now press volume up to confirm that you know what are you doing.
3)Open “Odin3 v3.09.exe” with Administrator privileges (right click on odin icon and click Run as Administrator)
4)Now “untick” Auto-Reboot. By doing that, your phone will not reboot after flashing bootloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5)Tap on BL button and open “BL_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar”
6)Now connect you phone via USB Cable, wait if you computer is installing drivers and then press Start Button. Wait till it finishes flashing
7)Now close Odin, take you phone (that still be in download mode) and hold down Power button + Volume down button + home button until it reboots in download mode, again. Press volume up to confirm.
8)Open Odin again, run it as Administrator. Now untick Auto-Reboot.
9)Tap on AP button and open “n9005-cwm-recovery-6.0.4.7-kk(0125).tar”. Now tap on Start Button.
10)Wait until it finishes flashing. Now close odin and take your phone. Hold down power button + volume up button + home button until it reboots in recovery mode.
11)Phone will show some texts and than it will reboot again. Hold down power button + volume up button + home button until it reboots again in recovery. Now you can install your 4.4.2 touchwiz rom. DON’T WIPE ANYTHING!
12)When rom is installed, reboot your phone… All Done! And you did not lost anything!
Click to expand...
Click to collapse
IF THIS GUIDE WAS HELPFULL FOR YOU, HIT THANKS BUTTON!​
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
​

First thing I don't understand is why we needs guide on development section.
Another thing is title. I didn't get you about data wipe. There are two method to update ROM either with CWM OR Odin (mobile odin/PC odin). If we directly flash stock ROM with odin that also doesn't wipe isn't ?
Problem only starts when we flash 4.4 on 4.3 (with any od said method) and device stuck at samsung logo. in that situation nothing but factory reset only works.
This guide can have better title how to flash bootloader and CWM recovery.

dr.ketan said:
First thing I don't understand is why we needs guide on development section.
Another thing is title. I didn't get you about data wipe. There are two method to update ROM either with CWM OR Odin (mobile odin/PC odin). If we directly flash stock ROM with odin that also doesn't wipe isn't ?
Problem only starts when we flash 4.4 on 4.3 (with any od said method) and device stuck at samsung logo. in that situation nothing but factory reset only works.
This guide can have better title how to flash bootloader and CWM recovery.
Click to expand...
Click to collapse
Thread moved by mods... my mistake. If you update to 4.4.2 from 4.3 using full firmware you need to wipe in order to boot to android.... This isn't needed if you update bootloader only... i wrote how to update from 4.4.2 without factory reset, installing bootloader only! If you follow this guide you will not have to wipe, so you keep root, recovery and data! It works, now i'm writing from a 4.4.2 rom, yesterday was 4.3 and i didn't lost nothing.
Inviato dal mio SM-N9005 utilizzando Tapatalk

OK, then when some users update 4.4 via OTA does their device gets stuck to boot? OTA also have new bootloader. Same way if someone flash 4.4 via Kies does their device gets wipe/stuck at samsung logo?
This thing is depends on data of device and may or may not stuck. In case it can't boot up, you needs wipe and nothing else will work in such situation.

dr.ketan said:
OK, then when some users update 4.4 via OTA does their device gets stuck to boot? OTA also have new bootloader. Same way if someone flash 4.4 via Kies does their device gets wipe/stuck at samsung logo?
This thing is depends on data of device and may or may not stuck. In case it can't boot up, you needs wipe and nothing else will work in such situation.
Click to expand...
Click to collapse
OTAs and Odin firmwares are totally different. OTAs are a lot lighter then odin firmwares and personally i've never seen a phone that enters in download mode while updating using OTA. If you flash a firmware using odin, you probabily need to wipe data. If you flash bootloader only, you don't need to wipe. Trust me. I didn't left anything using this method, so i thought to share what i did. You don't must to follow this steps. But maybe there's someone that wants to do that. I wrote this guide for this "someone".

AlbertoSONIC said:
OTAs and Odin firmwares are totally different. OTAs are a lot lighter then odin firmwares and personally i've never seen a phone that enters in download mode while updating using OTA. If you flash a firmware using odin, you probabily need to wipe data. If you flash bootloader only, you don't need to wipe. Trust me. I didn't left anything using this method, so i thought to share what i did. You don't must to follow this steps. But maybe there's someone that wants to do that. I wrote this guide for this "someone".
Click to expand...
Click to collapse
With your method though if you are on Knox 0x0 you get Knox 0x1 right? Because you flash custom recovery as I understand right? Because I am on 4.3 with Knox 0x0 and I would like to flash 4.4.2 without data loss but I am going to trip Knox If I use your method right? And if so, is there a method I can flash 4.4.2 without data loss and without tripping Knox?

I'm sorry, but there aren't any ways.... you'll trip knox if you follow this guide and if you update using full fimware, you will need to wipe data.... A question: why do you keep knox to 0x0? Warranty covers factory damages only, not user damages.... so if you had any factory damage, it should be already appeared!
Inviato dal mio SM-N9005 utilizzando Tapatalk

Well there are damages that aren't really user damages. If m/b gets fried or if screen gets damaged. For example on my S3 the volume buttons stopped working and it was covered by warranty. Am I wrong?
Sent from my GT-I9300 using Tapatalk

Ok finally rooted on 4.3 and used your method to flash XNOTE 8. Worked perfectly, no data loss

anpho said:
Well there are damages that aren't really user damages. If m/b gets fried or if screen gets damaged. For example on my S3 the volume buttons stopped working and it was covered by warranty. Am I wrong?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
You're right.... Samsung Warranty isn't clear... in some centers, they repair phones for free even if knox is 0x1, in other centers this doesn't happen. If you're lucky, you won't have any problem!
anpho said:
Ok finally rooted on 4.3 and used your method to flash XNOTE 8. Worked perfectly, no data loss
Click to expand...
Click to collapse
Good! Welcome to knox 0x1 world
Inviato dal mio SM-N9005 utilizzando Tapatalk

I asked other people from my country (Greece), and they say that Samsung is going to accept warranty claims even on Knox 0x1. That's why I did it hope it's true
Στάλθηκε από το SM-N9005 μου χρησιμοποιώντας Tapatalk

Great ..thank you..smooth update..:victory:

thanks really really man your the best i couldnt update from 4.3
AlbertoSONIC said:
HOW TO INSTALL A 4.4.2 TOUCHWIZ ROM OVER A 4.3 ONE WITHOUT DATA LOST​
[/CENTER]
Click to expand...
Click to collapse
exactly as you said i couldnt updatefrom 4.3 but after flashing bootloader am on 4.4.2 thnx man

[SOLVED] Stuck in DOWNLOAD mode after failed ODIN frimware update [SOLVED]

For those in need I have just received another confirmation that my solution works. Here are the details!
Sooo... let me explain before you begin recovery (and it will work, believe me!). 1) worry not!) 2).... the whole wrong comes from Odin. No matter what version of Odin you're using (and I used 3.10.6) and what firmware are you trying to flash (original, not so original, with MD5 or without) Odin will **** up your phone and get you stuck to the bloody "Downloading" screen. For me it happened after having a custom ROM installed and trying to revert to Vodafone UK original rom (namely "G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5"). DITTO! On some S6s ODIN will ruin your life and you can check that there are other similar horror stories around.
HOW DO I FIX THIS?
Well... pretty simple! Thank God! The idea is that once you reboot you phone and it shows as stuck in "Download" screen you have to flash the "recovery.img" that is actually inside the ".TAR" or ".TAR.MD5" file you have just flashed.
To do so you have to actually put the "recovery.img" you have just extracted from the ".TAR.MD5" (or just ".TAR) into a flashable file that ODIN understands. Yes, your'e right, in a blah-blah.tar.md5 or blah-blah.tar file.
To do so I have downloaded and installed 7Zip (since it's able to mangle .tar files as opposed to WinRAR) and also downloaded a "pristine" .tar file like the TWRP recovery (e.g. twrp-2.8.6.2-zeroflte.img.tar). The TWRP fil actually contains in it a modified "recovery.img" file.
Further on I have created a copy of the TWRP recovery file and named it "my-recovery.img.tar" (or call it whatever it fits you), opened it up in 7Zip and just dragged the "recovery.img" (you have extracted previously from the exact firmware ODIN has ruined at flashing last time) over the existing one in the archive. Click OK when 7Zip will prompt you that you are going to overwrite the existing "recovery.img" and you are done.
Now simply flash the "my-recovery.img.tar" via ODIN to you S6 and once done you'll have a functional phone with the latest firmware!
DON'T FORGET to go into the newly created recovery and factory reset! For your own safety the CSC has to be aligned from one old firmware to the new one.
Here is the recovery image for Italy (Vodafone) 5.0.2 G920FXXU1AODG to get you out of the trouble with the latest firmware (get it here):
my-recovery.img.tar
ATTENTION
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
The solution is, once you go through the procedure I have described, to open up Samsung Smart Switch (the new "KIES" for S6 and S6 Edge), go to "MORE" --> "Emergency software recovery and initialization" and perform that task! I will actually re-write the latest firmware you have flashed to your phone BUT will also solve the ODIN issues. On my phone, after doing so, I was able to flash this latest Vodafone Italy I have uploaded here.
The "Emergency software recovery and initialization" procedure has to be completed BEFORE you finish the setup procedure of your S6, you know the "WiFi" / Accounts / blah, blah (after flashing the firmware) and not afterwards. It least so I discover it to work.
Please let me know how this tutorial worked for you.

Will this prosedure trip KNOX?

It will not trip KNOX because it is a signed firmware that you're flashing with Odin.

Everything worked fine but not the Smart switch part. My device doesn't show up here in the list. How do I proceed?

Here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

h3llboy911 said:
Here. View attachment 3321069
Click to expand...
Click to collapse
Select the right tab and fill in there your phone's model after it confirms fill in your s/n number (phone's)... youll find the details on phonr box

This is what it says when I select the right tab. Looks like my device i snot supported. Any alternatives? I want to able to flash roms again.

Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!

AskinSavascisi said:
Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!
Click to expand...
Click to collapse
Why are we facing this flash fail error first of all? Is it because I had reactivation lock tuned on?

If u have it on, u wont be able to use odin... i had the same issue thats why i went with smart switch but it seems u have a problem with your device Model (not supported)... smart switch doesnt care if your reactivation lock is off or on

AskinSavascisi said:
If u have it on, u wont be able to use odin... i had the same issue thats why i went with smart switch but it seems u have a problem with your device Model (not supported)... smart switch doesnt care if your reactivation lock is off or on
Click to expand...
Click to collapse
I don't remember turning reactivation lock on before flashing with odin. I googled about the issue and it seems like it's a partition issue and we need to flash the correct .pit file to fix the issue. Till then every firmware that is flashed is going to fail at hidden.img.
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
and as the OP has stated, Smart Switch fixes this partition issue but sadly my device is not supported by it.
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
This what the OP has stated.
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
Click to expand...
Click to collapse

AskinSavascisi said:
Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!
Click to expand...
Click to collapse
Just to confirm, does flashing rom from sammobile using Odin will wipe phone? I know it will not trip knox, but is there any chance to flash official rom without wiping it?

Ollve said:
Just to confirm, does flashing rom from sammobile using Odin will wipe phone? I know it will not trip knox, but is there any chance to flash official rom without wiping it?
Click to expand...
Click to collapse
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.

h3llboy911 said:
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.
Click to expand...
Click to collapse
The point is I'm still on OCV rom (not branded) and I'd like to flash at least OE2-4 with ram fixes and possibly root right after update. Then wipe when we get official 5.1.1.
Waiting for OTA is so pointless in this case...

h3llboy911 said:
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.
Click to expand...
Click to collapse
If its the same pda not really needed

AskinSavascisi said:
If its the same pda not really needed
Click to expand...
Click to collapse
Different, from OCV to OE3/OE4. So probably worth to try without wipe and in case I get FC/bootloops - wipe.

ollve said:
different, from ocv to oe3/oe4. So probably worth to try without wipe and in case i get fc/bootloops - wipe.
Click to expand...
Click to collapse
???

Well, thanks for this

I was trying to install TWRP and my phone got soft bricked. I tried flashing the Trinidad and Tobago firmware that I had and got this "hidden.img fail!" error.The solution to recover the phone is well-explained by the OP and it works like charm.
A lot of people had faced the same issue over the S6 and S6 edge forums
-Some people told that the phones partitions are messed up and I needed to flash the correct PIT file to be able to flash any FW again. Otherwise it will fail every time.
-Some people told that I had "Reactivation lock"(Find my Samsung's feature) enabled and that's why I am facing the error. (In that case, we get a different error while flashing via ODIN or factory reseting, not hidden.img failed error.
The error is because of the FIRMWARE you are flashing is not supported. Yes! I recovered my phone by flashing the latest Indian firmware and it worked like charm. So the lesson here is, EVEN WHEN THE DEVICE MODEL IS SAME(925I), THE FIRMWARES FROM DIFFERENT COUNTRIES ARE NOT COMPATIBLE WHEN FLASHED VIA ODIN. (At least in my case and a few other who confirmed)
PS: The same firmware works if done by FLASHFIRE but ODIN fails.

dehnhaide said:
For those in need I have just received another confirmation that my solution works. Here are the details!
Sooo... let me explain before you begin recovery (and it will work, believe me!). 1) worry not!) 2).... the whole wrong comes from Odin. No matter what version of Odin you're using (and I used 3.10.6) and what firmware are you trying to flash (original, not so original, with MD5 or without) Odin will **** up your phone and get you stuck to the bloody "Downloading" screen. For me it happened after having a custom ROM installed and trying to revert to Vodafone UK original rom (namely "G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5"). DITTO! On some S6s ODIN will ruin your life and you can check that there are other similar horror stories around.
HOW DO I FIX THIS?
Well... pretty simple! Thank God! The idea is that once you reboot you phone and it shows as stuck in "Download" screen you have to flash the "recovery.img" that is actually inside the ".TAR" or ".TAR.MD5" file you have just flashed.
To do so you have to actually put the "recovery.img" you have just extracted from the ".TAR.MD5" (or just ".TAR) into a flashable file that ODIN understands. Yes, your'e right, in a blah-blah.tar.md5 or blah-blah.tar file.
To do so I have downloaded and installed 7Zip (since it's able to mangle .tar files as opposed to WinRAR) and also downloaded a "pristine" .tar file like the TWRP recovery (e.g. twrp-2.8.6.2-zeroflte.img.tar). The TWRP fil actually contains in it a modified "recovery.img" file.
Further on I have created a copy of the TWRP recovery file and named it "my-recovery.img.tar" (or call it whatever it fits you), opened it up in 7Zip and just dragged the "recovery.img" (you have extracted previously from the exact firmware ODIN has ruined at flashing last time) over the existing one in the archive. Click OK when 7Zip will prompt you that you are going to overwrite the existing "recovery.img" and you are done.
Now simply flash the "my-recovery.img.tar" via ODIN to you S6 and once done you'll have a functional phone with the latest firmware!
DON'T FORGET to go into the newly created recovery and factory reset! For your own safety the CSC has to be aligned from one old firmware to the new one.
Here is the recovery image for Italy (Vodafone) 5.0.2 G920FXXU1AODG to get you out of the trouble with the latest firmware (get it here):
my-recovery.img.tar
ATTENTION
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
The solution is, once you go through the procedure I have described, to open up Samsung Smart Switch (the new "KIES" for S6 and S6 Edge), go to "MORE" --> "Emergency software recovery and initialization" and perform that task! I will actually re-write the latest firmware you have flashed to your phone BUT will also solve the ODIN issues. On my phone, after doing so, I was able to flash this latest Vodafone Italy I have uploaded here.
The "Emergency software recovery and initialization" procedure has to be completed BEFORE you finish the setup procedure of your S6, you know the "WiFi" / Accounts / blah, blah (after flashing the firmware) and not afterwards. It least so I discover it to work.
Please let me know how this tutorial worked for you.
Click to expand...
Click to collapse
i simply cant work out this line.. after extracting the firmware file, i only get 1 xxxxxx.tar.md5
how do i actually change the recovery thing?

HOW TO ROOT OJ6/OI6/OGD ruturn to stock tar n920pvpu2aoi6

EDIT: 11/01/2015...This root method will work for OGD...OI6...OJ6... TRIED TESTED AND PROVEN ! ! !
WARNING: Once you USE THIS OI6 TAR OR take the OI6 OTA UPDATE . . . .
You will NOT be able to revert back down to OGD​
EDIT: 11/01/2015...If you take OJ6 OTA Update, YOU CAN USE OI6 TAR FILE TO REVERT BACK TO OI6 / STOCK
With this TAR, you will be able to ODIN back to 100% FULL SPRINT STOCK. in the event you develop bootloops or just want to unroot
ROOTING will trip knox and tripping knox WILL kill Samsung pay FOREVER...even if you flash back the stock tar
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOU PHONE. ... IT IS YOUR DECISION TO TAKE THE PLUNGE.
Anyone that tries this and gets bootloops and cannot recover here is a link to the OI6 stock tar file... flash in Odin AP slot from download mode you should recover very easily DOWNLOAD THE SPRINT N920P OI6 STOCK TARBALL HERE TO RECOVER AND/OR TO RETURN TO OI6 STOCK
WORD OF WARNING>>> AGAIN Once you take the update to OI6 or use the OI6 TAR (get OI6 HERE ) .. YOU CAN NOT GO BACK TO OGD.....
TO ROOT:
Download ODIN 3.10.7
Download FREEZA's BEASTMODE KERNEL HERE
Download TWRP-2.8.7.0-N920P.tar
Download BETA-SuperSU-v2.49.zip
PREP THE PHONE FIRST ...
go to settings>>>about device>>> scroll to bottom and build number 8 times
now press back button once and tap developer options...
make sure USB debugging is on AND OEM UNLOCK NEEDS TO BE ON ALSO .....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Place phone in ODIN / Download mode ( press and hold vol down+home+power for a few seconds...then release and press vol up)
plug the phone to the pc....Watch for ID:COM in top left corner to give an ID.......if none is given then check the data cable or try a different one.... NOTE: once you try a flash and "IF" it fails... you will need to disconnect and power off the phone ( to power off press and hold Vol down + power for 10 sec ) and go back into download mode again or you will get "Setup Connection" hangup error when re-trying to flash
Now Click the "AP" button and in the pop up window, migrate to the KERNEL and double click it. Wait for it to verify md5 checksum. If bad, re-download the file.
Now check in the OPTIONS TAB.... make sure ONLY Auto Reboot & F. Reset Time are checked...
uncheck Re-Partition ! ! !
Once these steps are followed, click start and wait till you see PASS in the ID:COM Field
After re-boot, follow same steps and flash TWRP
Then either install SuperSU in TWRP by going into recovery by powering off the phone then press and hold vol up+home+power until you see the TWRP splash .... or just install from the market( the market install "may" give update binaries issues... flash in TWRP )
I have a SPECIAL HANGOUTS thread for SPRINT NOTE 5 OWNERS.
I would like to add ALL of you to it.
PLEASE PM ME YOUR GMAIL EMAIL ADDRESS SO I CAN ADD YOU
So you have rooted, NOW WHAT? . . . You need to flash the best custom rom > > > >
Galaxy Note 5 OI6 & OGD Deodexed Rom
@tdunham has built the best deodexed rom.... CLICK HERE FOR HIS THREAD or CLICK this button
tdunham said:
Galaxy Note 5 OGD/OI6 Stock Deodexed Rom2
This build is based on the stock OGD & OI6 5.1.1 Lollipop builds.
This is a first release. Even though it has been tested, please report any issues.
Features:
- Rooted
- Busybox
- SQLite
- Hotspot enabled
- Knox Removed
- ItsOn Removed
Download Link ---> N920P_OGD.5.1.1.De-Odexed.Ver1.0.zip
Download Link ---> N920P_OI6.5.1.1.De-Odexed.Ver1.0.zip
Changelog:
OI6 Release
- OI6 brings some security enhancements and fixes nothing specific.
- Fixed access to hiddenment dialer codes
- stagefright vulnerability fully patched (for now)
- Beastmode v1.2 kernel already included.
Rom Installation
Preparing the stock rom
• In the stock rom, turn on developer mode, enable USB debugging and OEM Unlock
- Settings>>>about device>>> scroll to bottom and tap build number 8 times
now press back button once and tap developer options...
- Toggle on both USB debugging and OEM Unlock.
• Copy the downloaded rom.zip file to internal storage
Install Custom Recovery with Odin
• Download Odin & custom recovery tar
Odin3_v3.10.6.zip
TWRP-2.8.7.1-Alpha_N920P.tar.md5
or
philz_touch_6.59.0-820876114.tar.md5
• Extract Odin zip-file
• Power down the phone
• Open Odin on pc
• Boot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the recovery file to AP / PDA (depending on version of Odin)
• Make sure re-partition & Auto Reboot are NOT ticked
• Click the start button and let the Odin flash complete
• Unplug & Reboot phone directly into Recovery Mode (press and hold Home + Power + Volume Up buttons)
• BACKUP YOUR CURRENT SETUP WITH TWRP
• Do a FULL wipe but do not reboot yet
A full wipe includes:
Dalvik Cache
System
Data
Cache
• Flash rom and reboot.
Going back to the Stock Rom
• Use the same Odin instructions to flash TWRP above but using the stock tar
Credits to my beta testers: @Chaz187 @fsunoles101 @JoeyDuran @GAPO @rlmiller @sml2004
Special Credits to: @tx_dbs_tx
For help with development, the csc & personal mode fixes.
Click to expand...
Click to collapse
to read about it​.
.
.
.
.
.
.
.

reserved for later 1

reserved for later 2

reserved for later 3

nice bro, thanks. a lot of people have been waiting for this!

Is there by chance a flashable zip that doesn't affect the bootloader so you can go back to ogd if you want? I know in the past it has been done before, not sure what it takes to accomplish this. Thanks for all your hard work.

Thank you sooooo much, but this definitely should not be in the general section for sure. A mod needs to move this to its proper place, this is a lifesaver.

So I got a replacement Note 5. I updated to OJ6 and then followed this tutorial to root. I managed to get root and installed twrp. However, try to flash certain zips in twrp the phone just reboots. This only happens with certain zip files like xposed installer and the volume mod zip. The interesting thing is these zips flashed fine on my old Note 5.
Anyone have any ideas?
Edit: Nevermind, I reflashed stock via odin and went through update and root again. NOw it seems like it's working.

Can I flash twrp first and then flash the kernel zip? Because when I try to flash the kernel through Odin it gets stuck before it even starts.

melendez214 said:
Can I flash twrp first and then flash the kernel zip? Because when I try to flash the kernel through Odin it gets stuck before it even starts.
Click to expand...
Click to collapse
Yes, that shouldn't be a problem

rlmiller said:
Yes, that shouldn't be a problem
Click to expand...
Click to collapse
Ok thank you

DarkManX4lf said:
So I got a replacement Note 5. I updated to OJ6 and then followed this tutorial to root. I managed to get root and installed twrp. However, try to flash certain zips in twrp the phone just reboots. This only happens with certain zip files like xposed installer and the volume mod zip. The interesting thing is these zips flashed fine on my old Note 5.
Anyone have any ideas?
Edit: Nevermind, I reflashed stock via odin and went through update and root again. NOw it seems like it's working.
Click to expand...
Click to collapse
Can u get xposed working with OJ6? Stock rom?

drewiskee said:
Can u get xposed working with OJ6? Stock rom?
Click to expand...
Click to collapse
Yeah it works with stock rooted.

DarkManX4lf said:
Yeah it works with stock rooted.
Click to expand...
Click to collapse
I tried and got reboots and had to flash stock rom from lower build.
using twrp recovery

I have the edge + .....can I revert back to oi6 as well? Sorry I'm new at all this! Lol thank you

So, I was a master at rooting/manipulating my phone, but as it was a Note 2 until yesterday, I'm a bit rusty.
My son and I both got new Note 5s yesterday (a 32G and a 64G) and they've got OJ6 on them. I'm not completely sure I understand the instructions in post 1 - do I have to take the phone back to OI6 to be able to root using this method? Is there no root exploit for OJ6?
If I do have to revert, could you post clearly how to do it, please? Once I get past that I should be okay...
I have all these things I want to get done on the new one (getting rid of all the Sprint apps, backing up my messages, moving some program data over, more...) but realized everything I know about manipulating a cell phone is in Root, so I have to do it...
Thanks, in advance, for the help!!!

wackydroid said:
So, I was a master at rooting/manipulating my phone, but as it was a Note 2 until yesterday, I'm a bit rusty.
My son and I both got new Note 5s yesterday (a 32G and a 64G) and they've got OJ6 on them. I'm not completely sure I understand the instructions in post 1 - do I have to take the phone back to OI6 to be able to root using this method? Is there no root exploit for OJ6?
If I do have to revert, could you post clearly how to do it, please? Once I get past that I should be okay...
I have all these things I want to get done on the new one (getting rid of all the Sprint apps, backing up my messages, moving some program data over, more...) but realized everything I know about manipulating a cell phone is in Root, so I have to do it...
Thanks, in advance, for the help!!!
Click to expand...
Click to collapse
Yes, you can root OJ6 the same exact way as all the current builds.
I'm sure you're familiar with Odin by now so just download the OI6 factory tar (there isn't one available for OJ6 so far, its only available as an OTA update) and have that handy should you wish or need to go back to stock.
Also, if you see the OGD tar, don't bother with that one, you wont be able to flash that factory tar anyway as it will fail checks in odin when it recognizes you're on a newer build.
Additionally:
Since you're going to trip knox anyway by flashing TWRP custom recovery, you might want to keep in mind about wiping your internal storage too if you're having any issues along the way. It probably doesn't apply quite yet for you at this point but you know how it collects tons of extra stuff the longer you run android. There are a couple of deodexed stock builds and a custom rom too should you want additional features not available on stock.

All seemed to go well, BUT
When I boot, in tiny red type at top left, I get a "KERNEL IS NOT SEANDROID ENFORCING", or if booting into recovery "RECOVERY IS NOT SEANDROID ENFORCING".
What is that, and how do I fix it?
[EDIT] - I also just tried flashing the 1.2 version of the kernel and am still getting those messages...HELP...

wackydroid said:
All seemed to go well, BUT
When I boot, in tiny red type at top left, I get a "KERNEL IS NOT SEANDROID ENFORCING", or if booting into recovery "RECOVERY IS NOT SEANDROID ENFORCING".
What is that, and how do I fix it?
[EDIT] - I also just tried flashing the 1.2 version of the kernel and am still getting those messages...HELP...
Click to expand...
Click to collapse
That is normal you can't fix it!!!!!

SkyHigh auto-root kernel
OP.
Another auto root kernel. I've now added support for N920P
[KERNEL] [ROOT] [SM-N920P Exynos 7420] [02 Dec] SkyHigh TW 5.1.1 Kernel [v2.4]
I don't have the device, but I created it to share with users after receiving good feedback on Note5 :good:
Please make no direct download link, but add thread link to your OP (if your desire).
Also, loads of features with Synapse
Cheers,
UITA

[OutDated!] Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1]

THIS IS AN OUT DATED METHOD. A MUCH EASIER METHOD CAN BE FOUND
EMMC 15
EMMC 11
Scroll Down To This Post#3 For Instructions​
This is the main thread for rooting (and installing safestrap) on VERIZON Galaxy S5's running
OE1
OK3
OG5
PB1
If your firmware is NOT listed above, you MUST FIRST Follow the section that says "Flashing PB1", This will upgrade/downgrade depending on if you are on any other versions of Android. Yes it will downgrade from marshmallow, so don't ask.
Important Information​
One of the apps in this thread "Supersu-me" Is required to complete this process, otherwise you will be stuck with the Kingroot Superuser Manager(which blocks alot of actions we need). You can buy the App here. Supersu-me Pro The new version MAY NOT WORK ANYMORE!!! If you have issues, please message the developer of the app @gatesjunior, we cannot help.
If anyone wants to make a donation make a donation to @GeTex
[email protected]
A Special Thanks To @GeTex For Mods to the root.bat and updating the old instructions
A Special Thanks Also To @be free for the new simple method
WARNINGS​This Is Very Important!!! Once Your Rooted Do Not Flash Any Firmware Zips Found In My Other Threads Unless They Specify NO_BOOTLOADERS In The File Name!
Reactivation lock MUST BE TURNED OFF!!!
Before Doing Anything Please Install The Latest Samsung Drivers SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe
YOU MUST DO THIS
General Information​This is confirmed working on BOK3 Rom with BOK3 Bootloaders, BOG5 with BOG5 Bootloaders, BPB1 with BPB1 Bootloaders and BOE1 with BOE1 Bootloaders!, that were previously unrootable! Just make sure in bottom directions you flash the kernel that matches your firmware!
These files were provided to me by @voices! the files are by CDMA YEMEN TEAM.
I provided the method and editing of files and last but not least @alnazef34 he was the first to tell me about this.
Also would like to thank @gatesjunior for making the Supersu Me app. Please goto his thread and thank him donate to him and go buy his Super-Sume Pro at the playstore and keep a copy for future.
A Special Thanks To @GeTex For Mods to the root.bat and updating the old instructions
A Special Thanks Also To @be free for the new simple method
Understanding the process​
So alot of confusion has surfaced from this thread and how it works and I'd like to explain most of whats going on hopefully without error. When verizon updated the bootloader they made it impossible to downgrade the system back to Kitkat so we could abuse towelroot. Later it was found that while we cannot flash our Systems back we could flash the kernel, allowing us to run the same basic exploit via an ADB terminal remotely and install a root exploit. The end result is that we can then flash our kernel back to Lollipop and then use the exploit to allow kingroot to install it's root method, and then shortly after, we are able to use supersu me to remove kingroot and install SuperSu. Your original kernel is important but for the most part you should all do this on PB1 anyways. NI2 or NK2 are both kitkat kernels and can be used(one is included in the zip)to accomplish this process. because you clearly are not on a Kitkat system it will FREEZE while booting because it's not supposed to boot a lollipop system. So In order for root.bat to work(or root2.bat) you MUST flash a kitkat kernel(NI2 or NK2) and once it succeeds you must flash your original kernel(probably PB1)
Installing PB1​
(You will lose all of your app data and apps installed, your internal storage will be fine, backup is recommended anyways
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
2. Reboot to recovery (Power+Volume Up+Home Button) and wipe data from recovery, reboot to bootloader
3. Plug In your phone and open Odin located in the OK3_ROOT folder
3a. Make sure your phone is recognized (In the Odin Screen Under ID:COM the box under will be blue with your com port id #)
4. Click the AP button in the Odin Screen and locate and click on the G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 this is the file that was unziped from the G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip(Everything you do will be flashed via AP!!!!)
4a. This will take a few minutes for odin to load and verify MD5. When done in the odin message box it will say
Code:
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS.
5. Under options DO NOT CHANGE ANYTHING (Previously I had you check NandErase but this was part of the problem with root not finishing)
6. Now click on Start
7. When finished you will get a green box that says PASS!
8. Phone will reboot automatically to recovery and finish updating then it will restart
9. When Phone has finished loading and has booted up go through setup and do not add any google accounts or samsung accounts or anything
Rooting Instructions​Please read EVERYTHING ABOVE BEFORE CONTINUING
This is the BlackCat Update, Hopefully it's better
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
2. Unzip folder.(You need a unzip application like 7z or Winrar)
3. Open The Folder and click Bat file #1, Install APKs, plug in your phone and follow directions
All the Steps for the main rooting process are done ON THE BAT FILES, READ THEM!!!!
If the root process hangs Close the bat, unplug phone pull battery and reboot phone to recovery (VolUp+Pwr+Home). In recovery wipe cache only and reboot. If phone reboots back to recovery instead, pull battery and manually reboot. Now plug phone back in and Launch Bat #3.
IF you get into android and cannot get root, Open bat file #2 and start from there again
If your phone wont reboot, use Bat #4 and try and enter download mode manually(VolDown+Pwr+Home)
4. Open KingRoot.apk Click The Up Arrows a couple of time until you get to Try It and click Try It and that's it don click nothing else just close Kingroot. You should now have root. If It says Root not available and the bat said your were rooted Reboot Phone and open KingRoot You should now be rooted(otherwise reboot phone and check again)
5. Optional: If you Dont want to use SuperSu Me Skip To 6 and try but if it doesnt work then you will have to use SuperSume . Now open SuperSU-Me app (This app is now a paid app so setup Google Play and buy and it will remove kinguser and replace it with SuperSu. If you can't get the Paid version to work. The SuperSu Me 6.7 version worked. So you may have to hunt that one down by asking the Dev of the app) After this process SuperSu will ask to update binary click update normal
6. Copy this G900V_Fix Safestrap.zip (It may come in handy later on) to your SD Card and Internal Storage Copy Safestrap_Flashable_Kernels and Safestrap_Flashable_Firmware and anything else you want to install like the below rom
7. Now open Busybox Installer Allow KingRoot permission click on install
8. Click on Safstrap Allow KingRoot permission then click Install Safestrap after it installs reopen Safestrap and click on install again
9. Reboot phone open Safestrap app and Click Reboot To Recovery. If during this process you every get stuck on samsung screen.
Pull battery reboot phone to bootloader (VolDwn+Pwr+Home) Plug phone into computer open Odin In the AP Slot Flash VZW_BPB1_KERNEL_ONLY.tar.md5 Located in the LOLLIROOT Folder
10. Install This zip Knox_Removal_SU_BB_INIT.D.zip If you dont want a custom rom your done!
11. If you want to flash a custom rom make a backup In safestrap. Then in safestrap Click Wipe then Click Advanced Wipe Then Wipe System,Wipe Data,Wipe Cache Then Install any rom of your choosing as long as it is a Verizon S5 TocuchWiz Based Rom CM builds will not work! If you want you can try this it is stable. If for some reason you get an error flashing zips install this zip G900V_Fix Safestrap.zip in safestrap then you will be able to install roms. That zip wipes system and formats it so you will need to install a rom or backup before leaving safestrap
VZW_BPB1_ODEX_DEODEX_V8.zip This is a fully stock rom just like you had except it is Pre Rooted Knox free Deodexed with Tethering Fix, SDWrite Fix. Other than that all the bloat is still there but now your rooted you can remove it or flash different rom whatever
12. After flashing any rom I would head over to my Safestrap Thread and flash the latest version of Safestrap
Extra Information​Extra Information
If you soft brick your device and you made a backup in safe strap, flashing the NK2 kernel will get you back into safestrap, allowing you to restore your backup
THIS DOES NOT UNLOCK YOUR BOOT LOADER!!! To Unlock the bootloader look at the Sticky in the Development Forum. You cannot flash anything through the stock recovery. Do not try to, you will softbrick!
If you try and flash a rom or anything else, make a backup first, it saves many headaches.
If you cannot flash roms with the error "set_metadata_recursive failed" or something, you likely need to start from scratch BUT with the S5 PIT file(matching your size, there's a 16GB pitfile floating somewhere)
Realize your phone warranty is likely gone after doing this, should anything arise, you can try and get to download mode and flash the stock image again and it may go back to normal status but we cannot encourage fraudulent warranties, no matter how pathetic Samsung's policies are.

If something goes wrong! Here is the Factory Tar BPB1 Full Restore Image.
G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip
Here are the new safestrap flashable firmware zips with no bootloaders these are safe to flash on all versions of bootloaders
BOC4_Firmware_No_Bootloaders.zip
BOD5_Firmware_No_Bootloaders.zip
BOE1_Firmware_No_Bootloaders.zip
BOG5_Firmware_No_Bootloaders.zip
BOK3_Firmware_No_Bootloaders.zip
BPB1_Firmware_No_Bootloaders.zip
Here are the new safestrap flashable kernel zips these are safe to flash on all versions of bootloaders
G900V_OC4_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OD5_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OE1_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OG5_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OK3_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip

Wow ...

Chopstix9 said:
Wow ...
Click to expand...
Click to collapse
Edit: Its confirmed Working!!
Need some testers to confirm!

jrkruse said:
Need some testers to confirm!
Click to expand...
Click to collapse
No disrespect intended but I am not going to flash up to stock locked from where I am to test it !! Come on people !!! If you have a locked phone and want root, here's your chance to contribute to a potential major break through on our phones ...

Chopstix9 said:
No disrespect intended but I am not going to flash up to stock locked from where I am to test it !! Come on people !!! If you have a locked phone and want root, here's your chance to contribute to a potential major break through on our phones ...
Click to expand...
Click to collapse
Edit: Confirmed Working!!
Notice I didn't either, but it should work since all you have to do is flash the NI2 kernel which you can still do on the oe1.og5 and ok3 firmwares. They just wouldn't let you flash the ncg system.img

Edit: Confirmed Working!!

Yes it works. However my unknown mistake after achieving root with my bok phone was that I immediately installed titanium backup and a message came up saying something about an unauthorized action. My phone rebooted and now says start up failed . Use the verizon softwair repair assistant on a computer to repair your device. Of course this is impossible. I suppose if I had installed busybox and safestap first and placed a rom on the phone I would have been ok. Fortunately the phone was a spare but I'm still not happy.

rnh said:
Yes it works. However my unknown mistake after achieving root with bok was that I immediately installed titanium backup and a message came up saying something about an unauthorized action. My phone rebooted and now says start up failed . Use the verizon softwair repair assistant on a computer to repair your device. Of course this is impossible. I suppose if I had installed busybox and safestap first and placed a rom on the phone I would have been ok. Fortunately the phone was a spare but I'm still not happy.
Click to expand...
Click to collapse
Flash the BOK3 kernel it should boot
If it doesnt, Here is the Odin Factory tar image just flash in odin G900VVRU2BOK3_G900VVZW2BOK3_VZW.zip. This does not have the BOD5 bootloaders so it will flash fine for you

Thank you JK. How you stay up with all of these threads impresses me. Flashing the bok3 kernel worked. Now to continue I should install the bb and ss because apparently using the phone just rooted with rooted apps won't work?
Also, in the process of rooting as advice to anyone who wants to do it; when using the bat program, I found if it doesn't work right away close it then reopen it and it starts right away.
With titanium backup still installed the unauthorized app messge remained so I uninstalled tb and rebooted the phone with no problem

rnh said:
Thank you JK. How you stay up with all of these threads impresses me. Flashing the bok3 kernel worked. Now to continue I should install the bb and ss because apparently using the phone just rooted with rooted apps won't work?
Also, in the process of rooting as advice to anyone who wants to do it; when using the bat program, I found if it doesn't work right away close it then reopen it and it starts right away.
With titanium backup still installed the unauthorized app messge remained so I uninstalled tb and rebooted the phone with no problem
Click to expand...
Click to collapse
I added the apk above that will work with lollipop

So it seems this works!. The only thing you will want to do is make sure the kernel you flash after you root matches your firmware so you dont get the unauthorized actions message!. And I would get a custom rom flash asap because the stock verizon rom still has knox. I posted in the OP the files you should need to get busybox and lollipop safestrap installed
Edit Root_OG5_V2.zip contained a folder called SafeStrap Flashable Firmwares please dont use these as they contain older bootloaders and may brick your phone. So if you downloaded Root_OG5_V2.zip before i pulled it please dont use those zips
Edit Root_OG5_V3.zip Contains all the files you will need

Tried it, and got stuck after the NI2 kernel update. The batch file would never recognize the device again... ended up having to wipe and recover... more than happy to try again though
***my bad, tried the old method... didn't realize it was updated.
---------- Post added at 07:20 AM ---------- Previous post was at 06:29 AM ----------
confirmed working! You guys rock!

We have a winner! I followed the steps exactly and poof ROOT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks millions

Mine does not reboot after the .bat file fails the first time. I continue on, and when I get to the samsung screen, and I run the .bat once more it gets stuck at 'installing root now' and does not proceed. Help would be appreciated!

Awesome job @jrkruse.
I don't personally need this because I never updated my bootloader but for all of the people out there who updated via OTA or bought a phone that was already updated, you are a life saver.
As always, great work.
---------- Post added at 07:43 AM ---------- Previous post was at 07:27 AM ----------
Actually, I'm quite curious if I may just want to do a full stock Odin flash of OK3 (bootloader and all) since I never plan on going back to kitkat and I can just gain root and deodex the ROM myself for Xposed afterwards.
I've noticed that using the old bootloader with new updates causes my phone's screen to do weird things when I try to charge it while it's off. Using the correct bootloader may fix that.

so once more, I have installed every package for the SDK. Modded my paths correctly so that adb is usable.
flashed phone back to the OK3 .tar provided.
I run the .bat, it sees the phone and attempts to install root.
I now get 1 of two results.
first, it will hang at 'installing root now' and never proceed, or it will error out "error; device not found" and fail. Neither of these options promp a reboot.
as I mentioned earlier, if I proceed to install the kernal provided, the screen gets stuck at samsung, and the .bat once again hangs at 'installing root now'

Aireos said:
so once more, I have installed every package for the SDK. Modded my paths correctly so that adb is usable.
flashed phone back to the OK3 .tar provided.
I run the .bat, it sees the phone and attempts to install root.
I now get 1 of two results.
first, it will hang at 'installing root now' and never proceed, or it will error out "error; device not found" and fail. Neither of these options promp a reboot.
as I mentioned earlier, if I proceed to install the kernal provided, the screen gets stuck at samsung, and the .bat once again hangs at 'installing root now'
Click to expand...
Click to collapse
Maybe try using a different port on your computer. Did you goto developer options and enable usb debugging? After that did you accept the Allow USB debugging dialog
View attachment 3606452

jrkruse said:
Maybe try using a different port on your computer. Did you goto developer options and enable usb debugging? After that did you accept the Allow USB debugging dialog
View attachment 3606452
Click to expand...
Click to collapse
I have enabled debugging, and have tried different ports. Must've gone over every detail about 6 times total. For now, I just flashed back to factory. Will try again in a few hours if I get some decent replies..

Juust brought my spare to work. Seeems I was on boe1. Is there a kernel for that? I don't think it will do a software update to bok while rooted.