Database Users

[RECOVERY][21.Feb.12] ClockworkMod Recovery v5.5.0.4

Hey Everyone! So long story short, I ended up picking up a 8.9 tab and now we have a 100% confirmed working ClockworkMod Recovery!
So, quick and dirty instructions for users WITHOUT any form of CWM recovery on their device:
1) Download the attached ClockworkMod_Recovery_v5.5.0.4.tar
2) Reboot the tab into download mode
3) Fire up Odin 1.85 and put the ClockworkMod_Recovery_v5.5.0.4.tar in the PDA field.
4) Flash!
5) Reboot into ClockworkMod Recovery
Quick and dirty instructions for users WITH some form of CWM recovery on their device:
1) Download the attached ClockworkMod_Recovery_v5.5.0.4.zip to your device
2) Reboot the tab into recovery
3) Install the zip
5) Reboot
If, for any reason, you want to return to the stock recovery, simply download the P73xx_Stock_Recovery.tar and follow the instructions above (with odin)!
DISCLAIMER: THIS WILL NOT WORK WITH LTE TABS!

I kinda "bricked" my tab yesterday trying to create a recovery.
Now it just continually boots to the splash screen then restarts.
I can not get into recovery.
I can get into download.
I tried the ClockworkMod Recovery v5.0.2.6 but odin just hangs after setup connection.
Trying to download the stock recovery:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
Thanks,
-dana

Thankfully Samsung devices are notoriously hard to brick
So is the tab still booting into the OS? Or are you ONLY able to get to download mode?
Also, what did you do to try and create a recovery and what did you flash? If I can understand what has been done I can help you get up and running again
As for Odin hanging at "Setup Connection" when you tried to flash my recovery, it is likely just coincidence more than anything. Odin isn't the most dependable application...well, it is and it isn't...but getting stuck at Setup Connection is a common issue.
First tell me what you did yesterday so we can figure out how to proceed. Then we'll go from there!

I kinda want to volunteer as I am familiar with ODIN coming from a Vibrant but what's stopping me is 3 questions with all due respect. What's the related thread you were talking about at the OP? Are you sure that is the right 8.9 Stock Recovery? How did you find it as there is (at least) no American ODIN image as of today (checked Samfirmware as of this post)?

nirogu325 said:
I kinda want to volunteer as I am familiar with ODIN coming from a Vibrant but what's stopping me is 3 questions with all due respect. What's the related thread you were talking about at the OP? Are you sure that is the right 8.9 Stock Recovery? How did you find it as there is (at least) no American ODIN image as of today (checked Samfirmware as of this post)?
Click to expand...
Click to collapse
Excellent -
This is the thread I was talking about in 10.1 section:
http://forum.xda-developers.com/showthread.php?t=1307242
The recovery is standard, regardless of region. In fact, with the exception of precompiled binary modules, the recovery is even identical to that of the 10.1 tab
What I have done here is repacked the recovery image with a vanilla build of clockworkmod. This should work on both the P7300 and the P7310.
Give it a shot and let me know how it goes!

Neither got flashed via ODIN, but I too tried to install CWM yesterday via the market app so my recovery is messed up to start with.
After trying to flash the two the tab wouldn't boot and I got an error about a failed update.
Flashed the bootloader file below with ODIN to get it to boot.
Code:
ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Hmm ok...
So yesterday you tried the market CWM, which caused the tab not to boot at all? Then, you had to flash the bootloader to make it boot again?
I'm assuming you had a booting tab prior to trying to flash these files, but still had the borked recovery yes?

That is correct, but the recovery was fine when i got the device, I used it to root.
I know I should do a full flash but I don't want to lose all my stuff.
Also flahing the bootloader somehow removed the cwm ?script? That was forcing the tab to try and boot into the borked recovery on each boot.

Damn that app does a number on the poor tab...unfortunately the best course of action is really to completely restock the thing - flash an entire rom through Odin with a repartition.
Since you are able to boot, you can back up all your data with Titanium backup, then move the data off your internal storage and onto your computer in case it gets wiped by the Odin flash.
Now i really wish I had an 8.9 because I'm curious if someone who hasn't got the messed up recovery tries to flash my file if it will go through or fail like yours and the Geologist.
Any takers?

alterbridge86 said:
Now i really wish I had an 8.9 because I'm curious if someone who hasn't got the messed up recovery tries to flash my file if it will go through or fail like yours and the Geologist.
Any takers?
Click to expand...
Click to collapse
That'd be me. Once I backup my apps, I will (give me some minutes and I will post the result as an EDIT post). If it fails, worst case scenario would be flashing the Asian ODIN image since it is the only one available. That one displays everything in Chinese but I can change the language. Sidenote: Damn I wonder what is taking so long to bring an American ODIN image of the 7310 live???

nirogu325 said:
That'd be me. Once I backup my apps, I will (give me some minutes and I will post the result as an EDIT post). If it fails, worst case scenario would be flashing the Asian ODIN image since it is the only one available. That one displays everything in Chinese but I can change the language. Sidenote: Damn I wonder what is taking so long to bring an American ODIN image of the 7310 live???
Click to expand...
Click to collapse
Excellent! Let me know how it goes!

alterbridge86 said:
Excellent! Let me know how it goes!
Click to expand...
Click to collapse
It does not flash. This is what ODIN shows after following instructions:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
EDIT: Oh well...it's been a while since I last saw a "device-!-PC" screen.
EDIT 2: The "device-!-PC" screen vanished after one or two restarts as if nothing ever happened.

That's really weird, because I can even flash the p73xx stock recovery on my 10.1 tab and it at least goes through...it won't boot into recovery, as expected, but it at least FLASHES...
Maybe next question - are you guys using Odin 1.85? Also, are you using the driver from Kies or did you install a standalone driver? Try installing this driver:
http://www.multiupload.com/ISBTL9TADO
And then flashing after. It also may be worthwhile to switch USB ports after installing the new driver. Don't mind the p7510 in the file name, it works with multiple devices.

alterbridge86 said:
That's really weird, because I can even flash the p73xx stock recovery on my 10.1 tab and it at least goes through...it won't boot into recovery, as expected, but it at least FLASHES...
Maybe next question - are you guys using Odin 1.85? Also, are you using the driver from Kies or did you install a standalone driver? Try installing this driver:
http://www.multiupload.com/ISBTL9TADO
And then flashing after. It also may be worthwhile to switch USB ports after installing the new driver. Don't mind the p7510 in the file name, it works with multiple devices.
Click to expand...
Click to collapse
Yes, ODIN 1.85. Will install that driver and see how it goes.
EDIT: Same result as pointed earlier, even after installing the quoted driver and changing USB ports.
EDIT 2: Wait a second. I think I might have figured it out. This does not work on an encrypted system, right? I think I'll unencrypt and then try doing this.
EDIT 3: Nope, unencrypted or not, it does not flash. Same result.
Sent from my GT-P7310

Well, I have good news and bad news...lol
I was strolling through best buy this evening after dinner and made an impulse purchase...i'm now the new owner of a Galaxy Tab 8.9
EDIT (10/22/11): We're back open! Confirmed working STOCK recovery is in first post...confirmed working CWM recovery coming momentarily
EDIT 2 (10/22/11): And we're official. ClockworkMod is 100% working Enjoy guys!
Now on to my next project...making this thing FASTER

Confirmed working CWM-Recovery . Doing a NANDROID backup as of this post.

Working great, thanks.
Sent from my GT-P7310 using Tapatalk

Works perfectly on my gtab P7300 and ki1 rom.
Thanks for your job !
Now, wait noTW rom !

work perfectly on my gtab P7300 asia
AWeSOME

Thanks, working perfectly on my gtab 7300 as well. So glad you are one of us now, looking forward for your overcome roms

FAIL Flashing stock 4.2.2

Ive been desperately trying to return to stock to unroot my phone for 2 days to no avail.
Holding the power button takes me to the Samsung bootloop.
I used Odin 1.85 to flash a HOME.tar.md5 file getting this message:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it says the following:
ODIN MODE
Product Name:GT-i19505
Current binary: Custom
System status: Custom
Knox Kernel lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30 (have no idea what this is)
Write protection: Enable
eMMC Burst mode: enabled
START [224, 1440]
Any ideas?

poninaine said:
Ive been desperately trying to return to stock to unroot my phone for 2 days to no avail.
Holding the power button takes me to the Samsung bootloop.
I used Odin 1.85 to flash a HOME.tar.md5 file getting this message:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it says the following:
ODIN MODE
Product Name:GT-i19505
Current binary: Custom
System status: Custom
Knox Kernel lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30 (have no idea what this is)
Write protection: Enable
eMMC Burst mode: enabled
START [224, 1440]
Any ideas?
Click to expand...
Click to collapse
are you putting it in download mode
http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/

jaythenut said:
are you putting it in download mode
http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
Click to expand...
Click to collapse
Yes, I specifically wrote down what it said on the top left side in download mode,too.

poninaine said:
Yes, I specifically wrote down what it said on the top left side in download mode,too.
Click to expand...
Click to collapse
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.

jd1639 said:
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
Click to expand...
Click to collapse
I also found certain versions of Odin didn't work with some ROMS. When I tried using a 3.1x version of Odin to root my I9505G, it didn't setup properly, but using the 3.07 version did.

jd1639 said:
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
Click to expand...
Click to collapse
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?

poninaine said:
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
Click to expand...
Click to collapse
In the last fail the box on the bottom left side said "Leave CS" what does this mean?

poninaine said:
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
Click to expand...
Click to collapse
Do you know what firmware you were on? And what country and carrier are you.

jd1639 said:
Do you know what firmware you were on? And what country and carrier are you.
Click to expand...
Click to collapse
You mean now or before the root? And my country is Estonia which has no stock .tar file anywhere on the internet. I read somewhere that you can just use a random countrys one and change the csc later so I decided to do that.

poninaine said:
You mean now or before the root? And my country is Estonia which has no stock .tar file anywhere on the internet. I read somewhere that you can just use a random countrys one and change the csc later so I decided to do that.
Click to expand...
Click to collapse
Yes, before root.

I even tried re-partition. Still failed instantly.

jd1639 said:
Yes, before root.
Click to expand...
Click to collapse
Before root I was on the stock Android 4.2.2. The first time I flashed anything it was the new leaked 4.3 which worked just fine.
Then I flashed CM 10.1 and it worked but the problems started when I wanted to get back to stock.

poninaine said:
I even tried re-partition. Still failed instantly.
Click to expand...
Click to collapse
I'm pretty sure it's the firmware version you're flashing that's the problem. If you know what it was before you rooted I'd look for the same version.

I have a similar problem
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate

LimitedStreak said:
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
Click to expand...
Click to collapse
If Odin is successful but you get stuck at boot, do a factory reset in the stock recovery and it'll get you past the boot loop.

Would that delete my internal sd card folders etc?
---------- Post added at 10:12 PM ---------- Previous post was at 10:04 PM ----------
jd1639 said:
If Odin is successful but you get stuck at boot, do a factory reset in the stock recovery and it'll get you past the boot loop.
Click to expand...
Click to collapse
Would that delete my internal sd cards folders, prictures etc?
What if I flash another recovery then try wiping?

LimitedStreak said:
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
Click to expand...
Click to collapse
What do you mean I have Samsung Knox? I dont know how to find the same stock firmware as I dont know what I exactly need. As in if I need the exact same as it was when I bought it then I probably wont have no luck because my countrys csc firmware is nowhere for download.

I just realised - Im probably a huge idiot - I just checked the store site from where I bought my phone and it says the OS version is 4.2 not 4.2.2. Im going to try that but does every site only has 4.2.2!

[CANADIAN] Odin 5.1.1 Bootloader & TWRP Flashable Modem - SM-G920W8 BOI6 *UPDATED*

[CANADIAN] Odin 5.1.1 Bootloader & TWRP Flashable Modem - SM-G920W8 BOI6 *UPDATED*
Rogers is the only carrier who pushed this update, it was pulled shortly after, due to corruption. I had to spend literally ALL day downloading this. I downloaded it 7 times before i got a OTA zip that passes a CRC check and extracted properly. What a pain in the butt it is i had to convert my Telus device to Rogers fully down to modding the EFS to get this done.
Prerequisit: You must be on a 5.1.1 compatible TWRP as well as a 5.1.1 rom when flashing these packages or your going to get stuck in a binary miss match. While there is a fix for this with out the W8 5.1.1 odin packages, it takes a lot of musical flashing. So be sure to be on a compatible 5.1.1 rom, Kernel and TWRP first.
As always, you flash at YOUR OWN RISK. I will of course try to provide support if I am online, If you appreciate how much the pain in my butt was, and you didn't have to do this your self. Click Donate.
The Bootloader MUST be flashed via ODIN 3.10.X or higher. in the BL slot. Hence why its a tar. Sorry no flashables, Samsung locks the boot loader areas to everything but their own signed recovery, from their own signed update.zip
BO8H BL
BOI1 BL
BOI6 BL *LATEST*
The modem is TWRP flashable
BO8H Modem
BOI1 Modem
BOI6 Modem *LATEST*
You can get ODIN 3.10.6 HERE
Samsung USB Drivers HERE
Fingerprint confirmed working by my self. on custom 5.1.1 roms and stock.

You're my hero, lets have sex together

virulentt said:
You're my hero, lets have sex together
Click to expand...
Click to collapse
LOL the new "FIRST!"

-Mr. X- said:
LOL the new "FIRST!"
Click to expand...
Click to collapse
It works thanks a lot haha. No homo btw <3

Hi first of all thousands thanks to you for your work..
i have just quick question.
currently i am on xtrestolite v2.3 how do i flash this latest bootloader ? i tried flashing via odin v 3.10.7 and it failed. would you mind guide me here?

anuben said:
Hi first of all thousands thanks to you for your work..
i have just quick question.
currently i am on xtrestolite v2.3 how do i flash this latest bootloader ? i tried flashing via odin v 3.10.7 and it failed. would you mind guide me here?
Click to expand...
Click to collapse
You must reboot to download mode, and ensure you have the samsung drivers installed. IF you have already done this. paste your odin log.
failing that
please try attached odin instead. If it works i will edit the OP link. .7 worked for me. But either or.

-Mr. X- said:
You must reboot to download mode, and ensure you have the samsung drivers installed. IF you have already done this. paste your odin log.
failing that
please try attached odin instead. If it works i will edit the OP link. .7 worked for me. But either or.
Click to expand...
Click to collapse
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

anuben said:
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
redownload the Bootloader, your .tar could be corrupted.

anuben said:
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
Yes i flashed it via BL. Whats your actual device.

Worked perfectly for me. So glad to have a working fingerprint scanner on a 5.1.1 custom rom. Thanks
Sent from my SM-G920W8

Easiest way to do it is just make sure the Bootloader is loaded on Odin first on your PC then reboot to recovery and flash the modem package, select reboot and choose Download so it reboots to download mode, plug the phone to usb and flash in Odin and you're done!
Sent from my SM-G925F

I'm now getting some new "not enforcing" red text during boot. Is that expected?

BlackRabbits said:
I'm now getting some new "not enforcing" red text during boot. Is that expected?
Click to expand...
Click to collapse
Yep that's normal.
Sent from my SM-G925F

-Mr. X- said:
Yes i flashed it via BL. Whats your actual device.
Click to expand...
Click to collapse
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3

I've been using Arter97's back-to-n0t3 v3 with his 3.5 kernel, SO SMOOTH I lose around 5 to 7% overnight. You guys should give it a try!
http://forum.xda-developers.com/galaxy-s6/development/to-n0t3-bring-larger-fun-to-flagship-t3179857
http://forum.xda-developers.com/gal...development/arter97-kernel-galaxy-s6-t3171246
*** Download links are on his website (careful, the 3.6 version of his kernel isn't for our device, use the 3.5 g920tw8 one ***
http://arter97.com/browse/S6/
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
anuben said:
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3
Click to expand...
Click to collapse
that's not for the edge... you could brick your device flashing a non-edge bootloader to an edge one.

anuben said:
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3
Click to expand...
Click to collapse
This is why, odin is protecting you from your mistake. This is a G920W8 boot loader. It would brick your device if you convinced it to flash some how.
I do not have a G925W8 so i was un able to play musical CSC and FLash to get that OTA before rogers pulled it.
Just as a note guys, the fact that rogers pulled this update. expect all of the Canadian carrier updates to be delayed for weeks now.

-Mr. X- said:
This is why, odin is protecting you from your mistake. This is a G920W8 boot loader. It would brick your device if you convinced it to flash some how.
I do not have a G925W8 so i was un able to play musical CSC and FLash to get that OTA before rogers pulled it.
Just as a note guys, the fact that rogers pulled this update. expect all of the Canadian carrier updates to be delayed for weeks now.
Click to expand...
Click to collapse
holy fuk i shouldn't be doing drinking and flashing :silly: thank you though. appreciate your help...:good:

Thanks Mr. X....Confirmation number: 14Y69764AE724154S a little appreciation of your time. Can I re root and then flash this on my Bell device over 5.0.2? Or should I wait till I get the Bell`s 5.1.1. It has been awhile since I had a Sammy phone. I had a whale of time to get back to stock using Smart Switch and Odin always failed for me. Just want to be able to flash 5.1.1 roms with most stuff working. Thanks again!! My device is the SM-G920W8 Bell S6.

caanda45 said:
Thanks Mr. X....Confirmation number: 14Y69764AE724154S a little appreciation of your time. Can I re root and then flash this on my Bell device over 5.0.2? Or should I wait till I get the Bell`s 5.1.1. It has been awhile since I had a Sammy phone. I had a whale of time to get back to stock using Smart Switch and Odin always failed for me. Just want to be able to flash 5.1.1 roms with most stuff working. Thanks again!! My device is the SM-G920W8 Bell S6.
Click to expand...
Click to collapse
As this is a 5.1.1 boot loader it will require you to be on a 5.1.1 rom. good news is there are many roms to choose from that all work perfect due to my audio patches, and now this boot loader
I would flash TWRP on your 5.0.2 device as it sits, then i would choose your 5.1.1 rom of your liking. Put it all on your storage on the phone except the bootloader tar. Flash the rom, modem and what ever else in TWRP. then in the TWRP reboot options reboot directly to download/bootloader. and odin the bootloader. boot the device normally and you're good!
I do have the rogers ota update zip but i hesitate to distribute it since they pulled it due to bugs, and is uspect corruption ans i had to re-download it several times before it wasn't corrupt from their ota server.
PS: Thanks for the donation!
I am personally running this http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968, with the new boot loader and modem. it runs beautifully.
Any international rom with a kernel for our device and my audio patch will work. the rom i link packs it all up in a bow for you no extra work. finger print will also work since this boot loader

-Mr. X- said:
As this is a 5.1.1 boot loader it will require you to be on a 5.1.1 rom. good news is there are many roms to choose from that all work perfect due to my audio patches, and now this boot loader
I do have the rogers ota update zip but i hesitate to distribute it since they pulled it due to bugs, and is uspect corruption ans i had to re-download it several times before it wasn't corrupt from their ota server.
PS: Thanks for the donation!
I am personally running this http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968, with the new boot loader and modem. it runs beautifully.
Any international rom with a kernel for our device and my audio patch will work. the rom i link packs it all up in a bow for you no extra work. finger print will also work since this boot loader
Click to expand...
Click to collapse
Perfect, I was on that rom for awhile with 5.0.2 and some stuff missing..So the best plan is
1. Re Root and Flash TWRP
2. Back up
3. Flash 5.1.1 Rom
4. Flash Bootloader with Odin
5. Flash Modem with TWRP
And then I should be good to go? Where does the Audio patch come in?
Any other suggestions or order to my plan?
Thanks again for your time and hard work!!!

Phone won't boot, even into recovery mode

Hi all, im desperate for help here!!
I flashed Dr Ketans Rom to my Note 4 a couple of days ago but decided to try to go back to stock today due to a bug with my email. Anyway, a long story short, my phone failed the flashing process with odin whilst trying to flas the latest stock firmware from sammobile and then my phone refused to start up again.
I now get a screen telling me the firmware up grade process went wrong but I cant even reboot into recovery to install anything else.
I have tried flashing both TWRP and Philz recovery but both just flash the title screen on and off but never load up.
I have tried 2 firmware versions from sammobile and both end in fail, it seems like I cant flash any firmwares with odin which is a right pain because I cant get to recovery to install a zip file....
Please help, Im sooooo stuck!
Edit - this is the log from Odin if it helps anyone... Ive now tried software 4.4.4 also but nothing works.
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.

0-0-0 said:
I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.
Click to expand...
Click to collapse
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.

sudburys said:
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.
Click to expand...
Click to collapse
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.

0-0-0 said:
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.
Click to expand...
Click to collapse
No probs...
Thanks for the try anyway

Tried to install TWRP, messed up bootloader - Not sure what to do next

I pulled out my old Verizon Galaxy S4 with the intention of getting a ROM on it that had XPosed. After some Googling, saw KingRoot supported it, so I used that app to root it. Then I tried to get TWRP installed. Their website said you could do it from their TWRP Manager app, so I tried that. It *said* it succeeded, but after that, my phone couldn't even boot at all.
So then I read up on using Odin to fix it. I tried to flash TWRP recovery from Odin (even finding a .tar version was a PITA), but I got this:
Code:
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Now, it boots normally, but I can't get into Recovery any more.
All I really want to do is get some custom recovery on there. Or even back to normal at this point. But I don't know how. I also tried flashing Clockwork Mod, but that didn't improve anything. What should I be doing now? Go back to stock and start over? Or am I installing the wrong recoveries from Odin (the TWRP one wasn't on their official download page, they only have .img files there, not tars). Or what?

Your first mistake was that you used Kingoroot. CF-Autoroot should be supported on your S4. As to the recovery, you want the latest version of TWRP, here. Download the 3.0.2-0 tarball (.tar), open Odin, select the PDA slot and point Odin to the tarball, then flash. That should resolve your recovery woes.

Make sure your TWRP is for that phone model. Verizon phones have locked bootloaders which make modifications harder.

Since the OP installed Clockworkmod, I have to assume his bootloader is one of the ones that can be exploited. But a good point, and I edited the link in my last post accordingly.

Strephon Alkhalikoi said:
Your first mistake was that you used Kingoroot. CF-Autoroot should be supported on your S4. As to the recovery, you want the latest version of TWRP, here. Download the 3.0.2-0 tarball (.tar), open Odin, select the PDA slot and point Odin to the tarball, then flash. That should resolve your recovery woes.
Click to expand...
Click to collapse
That link doesn't have any tarballs. Only image files. I couldn't find the tars on their site at all, and the only one I could find was one someone had as an attachment in a thread. No clue if it's the right one, though.
Strephon Alkhalikoi said:
Since the OP installed Clockworkmod, I have to assume his bootloader is one of the ones that can be exploited. But a good point, and I edited the link in my last post accordingly.
Click to expand...
Click to collapse
I tried to install Clockwork Mod, but it didn't work. I got the fail message above when trying to install the tar via Odin, and when I tried to use their app, it did the same thing the TWRP Management app did - it said it succeeded, but now I can't boot into recovery.

Do not install Clockworkmod. It's no longer maintained and has problems with more current ROMs. Install TWRP using that tarball you found on the forums. I believe TWRP on Verizon has no tarballs as it's expected to be installed using the TWRP Manager or a similar app in the Play Store.
If this does not work, you may have to start from scratch. Hopefully you kept a copy of the ROM with the exploitable bootloader so you can reinstall if necessary.