Database Info

[ROM][ODIN] Stock ODEXED T839UVKD1 (Sidekick 4G) Firmware [6/12/11]

Hello Everyone, This is Now an Instructional Odin ROM to flash Back to Factory Stock and/or Recover your Broken System.
This is 100% STOCK Odexed T839UVKD1 firmware For the Sidekick 4G and needs to be flashed through Odin. Odin is attached below along with the Sidekick 4G pit.
How to Install/Flash.
Code:
0. Download the KD1OdinSTOCK.tar.md5 File (Find link Below)
1. Remove the .md5 tail
2. Open odin with phone not connected yet
3. Boot in to download mode using Trackpad+Vol down then power
4. Connect phone to pc
5. KD1OdinSTOCK.tar in pda slot, Use SK4G pit file from below in Pit Slot
6. Double check that only auto-reboot is checked (if it doesnt work the first time, click re-partition)
7. Click flash
First boot may take around 3-5 mins. Wait it out and then you should be good to go.
KD1OdinSTOCK.tar.md5 >> DOWNLOAD
UPDATE: FOOL PROOF WAY TO GET INTO DOWNLOAD MODE
ayoteddy said:
Try this, take the battery sim and sd card out of your phone.
Open odin, put the tar in pda and pit into pit.
Plug your phone into the usb.
Now bare with me, this part is a bit akward but you can do it.. hold the vol down key and trackball *with one hand* and put the battery in while holding them. You will be in download mode and Odin will detect your phone. Then flash
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Thanks to Xda Members Datlilboricua and tweeklulz for testing these files for me.
Use the Thanks button if this was helpful ; post below if you have feedback/questions ect, Thank you and please enjoy!

Nice one! Keep at it. There are a bunch of us waiting for this!
Sent from my SGH-T839 using XDA Premium App

downloading now, i'll package them
thanks for pulling these man
edit: just got back from the bar and I work in 6 hours i'll upload it later

Can anyone teach me how to install it in sidekick
Sent from my SGH-T839 using XDA App

Mirrors:
Part 1: http://gititbit.ch/skgi
Part 2: http://gititbit.ch/skgi2

Is this still being packaged Blu? I could really use a working odin tar right now... accidentally soft bricked trying to use a recovery.tar to get rid of ClockworkMod and get back to a stock recovery.

sduvick said:
Is this still being packaged Blu? I could really use a working odin tar right now... accidentally soft bricked trying to use a recovery.tar to get rid of ClockworkMod and get back to a stock recovery.
Click to expand...
Click to collapse
Just packed now sorry. You flashed the one from the restoring stock recovery thread? What was your method of flashing it? Does it boot up at all or stick at the samsung boot screen? (i packaged that one and am curious as I heard reports of it working)
Download link: still uploading
Pit file attached in case you need it (unrar it first)
I do not guarantee that this will work, all I did was tar the files and upload them (and edit the pit). I did not trim the datafs.rfs file due to lack of ability to test it. Flash AT YOUR OWN RISK! so If this fails you now own a fancy brick!
edit:Not posting the tar yet for privacy of ayoteddy and potentially his logins to websites. The data wasn't wiped and has all his info, waiting for a clean one.

damn those files shouldnt contain any data since i had factory wiped just before pulling those images. *shrug* there might be a more in-depth way to clear all data
anyways im sure we can have a functional odin image with only the following files included
zImage
modem.bin
factoryfs.rfs
Recovery.bin
Param.lfs
i doubt anybody will be messing with anything else in their file sys but that should be able to recovery anybody from a soft brick.
Edit: Also dis-include the sbl and boot.bin as it could be very dangerous overwriting those files.. not really necessary anyhow.

I'm actually stuck at the black screen with a phone and a computer with a yellow triangle in the middle. Yeah, I was trying to flash a stock recovery from the stock recovery thread. Got a little desperate and tried to flash the recovery tarred for Odin, and that sent me to where I am now. I appreciate all your hard work guys, and have learned my lesson not to flash unless there's a lot of backups handy ;]
I'll try the pit, not sure if I may need more or not, you guys probably know better than me.
EDIT: as I am not skilled in using Odin and do not wish to cause further damage to my phone, I will await instructions from you guys/ayoteddy's image.

sduvick said:
I'm actually stuck at the black screen with a phone and a computer with a yellow triangle in the middle. Yeah, I was trying to flash a stock recovery from the stock recovery thread. Got a little desperate and tried to flash the recovery tarred for Odin, and that sent me to where I am now. I appreciate all your hard work guys, and have learned my lesson not to flash unless there's a lot of backups handy ;]
I'll try the pit, not sure if I may need more or not, you guys probably know better than me.
EDIT: as I am not skilled in using Odin and do not wish to cause further damage to my phone, I will await instructions from you guys/ayoteddy's image.
Click to expand...
Click to collapse
What did you do while flashing it? What boxes did you tick? Where did you put the tar, etc
@ ayoteddy alright i'll just make one from those, only reason i was including cache before is I heard its where permissions were stored though as you said I'm sure those files work fine

Here it is:
Odin + pit: attached
sk4g_stock.tar.md5.rar: Click here
UNRAR the tar first (i didn't want to trim factoryfs.rfs due to unability to test so I compressed it instead)
Put the extracted sk4g.tar.md5 in the pda slot
make sure ONLY AUTO-REBOOT is checked (unless you are re-partitioning, then use re-partition and the pit file)
1. open odin with phone not connected yet
2. boot in to download mode using Trackpad+Vol down then power (thanks sduvick)
3. connect phone to pc
4. sk4g_stock.tar.md5 in pda slot
5. double check that only auto-reboot is checked (and the pda you selected of course)
6. Click flash
Disclaimer: Flash at your own risk, if you get bricked I am not liable.
The odin tar includes
factoryfs.rfs
modem.bin
param.lfs
recovery.bin
zImage

Thanks blu, @sduvick would prolly be the first to test cause he was waitng for this.. hope everything works out for em
He also figured out how to get into downlode mode ..
Trackpad+Vol down then power
Sent from my SGH-T839 using XDA App

I'm not entirely sure what I did. I think I put the recovery.tar.md5 in the wrong place. anyways, I'm back out of bricked, and now just waiting for a working stock restore tar to get back to stock.
EDIT: just saw the tar, downloading now, will test in around 10 min when the file is downloaded.

sduvick said:
I'm not entirely sure what I did. I think I put the recovery.tar.md5 in the wrong place. anyways, I'm back out of bricked, and now just waiting for a working stock restore tar to get back to stock.
Click to expand...
Click to collapse
Did you try my one click stock in the same post?

Yeah, I didn't have the same root method, so that didn't get rid of Clockwork for me.

First try at flashing failed almost at the end, at recovery.bin if I'm not mistaken. I'm trying to run it again.
EDIT: Failed again, at recovery.bin

sduvick said:
First try at flashing failed almost at the end, at recovery.bin if I'm not mistaken. I'm trying to run it again.
EDIT: Failed again, at recovery.bin
Click to expand...
Click to collapse
Got it working through pm with him.
attach the pit and re-partition. then flash the tar
sduvick wanna post the steps you used?

I can actually give steps based on what you have for symptoms (too much experimenting for me haha)
If you have the "soft brick," that is the small phone and computer icons, just connect to Odin and flash the full image.
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
logo only
1. Download mode
2. Flash full package
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work

sduvick said:
i can actually give steps based on what you have for symptoms (too much experimenting for me haha)
if you have the "soft brick," that is the small phone and computer icons, just connect to odin and flash the full image.
Black screen, no logo.
1. Get into download mode by using voldown+touchpad+power
2. Flash full sk4g.tar.md5 as posted.
Logo only
1. Download mode
2. Flash full package
can't flash recovery/boot/sbl
1. Download mode
2. Use pit only, run with repartition checked
3. Reboot/redownload mode
4. Run the full image in odin.
Anything else
1. Download mode
2. Full tar.md5 flash in odin
3. Ask if it doesn't work
Click to expand...
Click to collapse
sticky this **** mothafuckas!!!

The Pope of Dope said:
sticky this **** mothafuckas!!!
Click to expand...
Click to collapse
good thing some incredibly sexy blu guy made that pit file. I hear he has the face of brad pitt with abs like jesus.

[Q] [HELP THE NOOB] A weird case of softbrick.

Dear XDA,
Such a warm heartening welcome I felt after watching the Noob video. I am noob.
I've been a lurker for quite a long while, but only this harrowing case of a softbrick that has hit my N8000 that has encouraged me to register and actually post.
Here's how it went:
I took a nap on Monday afternoon, my Note was left charging, it was working just fine. I get up, I look around for it, It was stuck on "Samsung Galaxy Note 10.1", the bootscreen.
I've been trying a lot of stuff for the past three days, here it goes:
Good news:
I can boot into download mode. I can get into recovery mode (High On Android's CWM)
Bad news:
I can't flash anything through ODIN, it gives me a "Complete(Write) operation failed."
Recovery mode always displays "E:can't mount cache/recovery/log" "E:Can't open /cache/recovery/last_log"
I can only mount /cache and /system in "Mounts and Storage", the rest give me a mounting error.
I tried getting into it through adb, but it says "unauthorized" next to my device.
Is there hope? I read this might be a corrupt NAND because of the NAND fail on ODIN. But I can get into both download mode AND recovery, so there is hope, right? RIGHT?
I also have tried a couple USB cables, both ODIN 1.85 and ODIN 3.07, I wanted to try Heimdall; I tried 1.1, it doesn't detect my device. Heimdall 1.4 on the other hand detects my device, but I can't flash recovery through it (It only acceps Heimdall Firmware? Packages?)
Also on Good news, I ran an emmc scanner, and it gave me OK on every singe line from start to end. (0 to 15750 *or something round that number*)
HELP THE NOOB. HELP THE NOOB. HELP THE NOOB. :fingers-crossed:

try to do a factory reset from recovery

Sounds like a corrupt .pit file.
What's your tablet model?

@jaspreet: I tried Factory recovery, but it's useless.
@kalashiencof: It's a 16gbs N8000.
I'm wondering if there's any way to get it to boot from an external sdcard? Until I can fix the internal sdcard? Nuke it and rebuild it or something?
ANY HOPE?

The tablet appers to be useless as of now, I would recommend you to flash a new .pit with Odin, then flash the original firmware.
You can find the .pit file for your model here in the forum.
Note: flashing a new .pit file is very dangerous. It could brick your tablet even more. Make sure you only flash the correct one!
Just a personal opinion: High On Android CMW is now pretty out dated, I recommend you to install TWRP, or Philz Recovery (this one is based on CMW)
Sent from my GT-I9000 using XDA Premium 4 mobile app
---------- Post added at 01:12 PM ---------- Previous post was at 12:51 PM ----------
I found a thread with a N8000 .pit file.
http://forum.xda-developers.com/showthread.php?t=2363703
When you go to download the firmware for the tablet make sure you choose the correct firmware, that .pit file is for android 4.0.4 (ICS).
To download the correct firmware go to http://www.sammobile.com/firmwares/2/, make sure you have an account (it´s free) and choose the correct firmware for your tablet.
PS: Any (4.0.4) firmware should work but just to make sure, you should choose the one that came with your tablet.
Best of luck in restoring your tablet.

@kalashenicof : I'd like to thank you for trying to help. I tried what you posted again and again and again, but not luck. Still getting problems flashing from Odin.
There must be any other way, it can't be dead, can it? Like, I still can access both Recovery and Download mode, any hope?

@ayeladawy
What appened when you try to flash the .pit file?
---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------
Have you tried to flash another rom via recovery?

kalashenicof said:
@ayeladawy
What appened when you try to flash the .pit file?
---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------
Have you tried to flash another rom via recovery?
Click to expand...
Click to collapse
@kalashenicof Flashing a pit file gives me a "Re-partition operation failed." message, almost everything else says Complete(Write) operation failed.
I've tried to flash another cyanogenmod rom via recovery, didn't make a difference, but I haven't tried flashing a different rom, any suggestions?

ayeladawy said:
@kalashenicof Flashing a pit file gives me a "Re-partition operation failed." message, almost everything else says Complete(Write) operation failed.
I've tried to flash another cyanogenmod rom via recovery, didn't make a difference, but I haven't tried flashing a different rom, any suggestions?
Click to expand...
Click to collapse
Take a look here -> http://forum.xda-developers.com/showthread.php?t=804695
It seens that some times the problem is with odin it self. Try to flash a stock firmware several times without closing odin, see if that helps.
And try diferent versions of odin, i think there's a new version 3.09??

bump!!?

Anyone willing to try OG5 Root?

I was looking into the S5 OG5 root a while ago and I sold the device I had because there didn't seem to be a way to root it. I do have a rooted S4 and there was recently a new root method found for the 5.0.1 S4 rom that was released after the OG5 rom for the S5. The MobileGo website says it also supports the S5 so if anyone with OG5 unrooted wants to give this a try and let others know whether it works or not, I'm sure everyone would appreciate it. You guys are probably going to want to flash an older S5 kernel just like the S4 users flashed an older kernel before running the MobileGo program. Link: http://forum.xda-developers.com/showthread.php?t=3254434

Where do I find kernels to flash? I am willing to try this.

MySonsDad said:
Where do I find kernels to flash? I am willing to try this.
Click to expand...
Click to collapse
What you can do for now is try running MobileGo using the kernel you have now. If you're lucky, it'll root. If not, you can read on:
So what I would do first is download the latest version of Odin: http://odindownloadxda.com/Odin3_v3.10.7.zip
Then you'd want to go to this thread for the Odin flashable stock kernels for older versions:
http://forum.xda-developers.com/ver...t/safestrap-odin-safestrap-flashable-t3161043
BEFORE YOU TRY THESE NEXT STEPS: I was unable to find the stock OG5 Odin flashable kernel in these forums. If someone could kindly extract it from the stock OG5 rom and post on here you can begin the next steps. Don't try this before you have the stock OG5 kernel on hand because the older kernels may not let your phone boot up into the rom and the only way to fix it is to either reflash the entire OG5 rom in Odin or to flash the OG5 kernel in Odin. I think you can make the kernel yourself if you have the stock OG5 Odin tar, just extract the boot.img and pack it into a tar.md5 using http://forum.xda-developers.com/showthread.php?t=2446269 Here is a stock OG5 odin flashable kernel I was able to create for you: https://mega.nz/#!SEhzyKaL!ymd4vJ2Jd6ytbZoBIPp4fYh6fCRz0tELRMNAYVmIrqU
Once you have the OG5 kernel as a backup, try flashing VZW_BOD5_RETAIL_KERNEL_ONLY.tar.md5 and run MobileGo, if that doesn't work move on to VZW_BOC4_RETAIL_KERNEL_ONLY.tar.md5 then trying the MobileGo and then if that fails try NI2_stock_kernel.tar.md5 since that's the 4.4 kernel that was rootable. However, there's a strong chance that your phone will refuse to boot into the Lollipop rom using a KitKat kernel. All you have to do is flash back the OG5 kernel in Odin 3.10. Once you go through the different kernels from OG5 -> OE1 -> OC4 -> NI2 and the MobileGo program fails to root on any of them, you'll know that this is not a viable root method for the S5.

I couldn't get MobileGo to connect to my phone on OG5. I flashed the OE1 kernel, connected to MobileGo, then used Mobilego's backup feature. After that I noticed that there's a notification reading SECURITY NOTICE Unauthorized actions have been detected. Restart the device to correct them. I tried the MobileGo root and after about 5 minutes it gave me a failure message. Then I tried to proceed to BOC4 but I kept getting failures from Odin. I cannot get back to OG5 kernel either. After a few tries, I now cannot even get into download mode.
The good news is my phone is working. What do I do now? Is this "tripping Knox?"

Pull the battery. Press the buttons for download mode. There should be no case in such you can't access download mode unless you hard bricked your phone which you didn't since the phone is working. Mobilego doesn't specify if their root method trips Knox. Probably should assume it does but if the root failed then it should've left Knox alone. After a clean battery pull try flashing the OG5 kernel back to your phone.

aznjosh said:
I was looking into the S5 OG5 root a while ago and I sold the device I had because there didn't seem to be a way to root it. I do have a rooted S4 and there was recently a new root method found for the 5.0.1 S4 rom that was released after the OG5 rom for the S5. The MobileGo website says it also supports the S5 so if anyone with OG5 unrooted wants to give this a try and let others know whether it works or not, I'm sure everyone would appreciate it. You guys are probably going to want to flash an older S5 kernel just like the S4 users flashed an older kernel before running the MobileGo program. Link: http://forum.xda-developers.com/showthread.php?t=3254434
Click to expand...
Click to collapse
Where on the mobilego website does it say it supports the s5? I will try this when I get home tonight and post results.

fates13 said:
Pull the battery. Press the buttons for download mode. There should be no case in such you can't access download mode unless you hard bricked your phone which you didn't since the phone is working. Mobilego doesn't specify if their root method trips Knox. Probably should assume it does but if the root failed then it should've left Knox alone. After a clean battery pull try flashing the OG5 kernel back to your phone.
Click to expand...
Click to collapse
I can now get into download mode. If I try the older kernels I get a status bar that goes about 1cm then stops. If I try the kernel you gave me for OG5 ODIN says the binary is corrupt before even letting me flash it.

MySonsDad said:
I can now get into download mode. If I try the older kernels I get a status bar that goes about 1cm then stops. If I try the kernel you gave me for OG5 ODIN says the binary is corrupt before even letting me flash it.
Click to expand...
Click to collapse
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
Click to expand...
Click to collapse
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?

MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?
Click to expand...
Click to collapse
Hey, I might have created the flashable kernel incorrectly. Sorry, this is my first time creating flashable odin images. Try this one: https://mega.nz/#!SEhzyKaL!ymd4vJ2Jd6ytbZoBIPp4fYh6fCRz0tELRMNAYVmIrqU
You can try flashing that over your OG5 rom right now since it's the OG5 kernel and it won't change anything on your phone even if it does flash.
---------- Post added at 10:03 PM ---------- Previous post was at 09:56 PM ----------
Hariiiii said:
Where on the mobilego website does it say it supports the s5? I will try this when I get home tonight and post results.
Click to expand...
Click to collapse
wondershare(dot)(com)/mobile-phone/root-samsung-galaxy-s5(dot)(html)
That guide is from before the OG5 update though. However, my basis for trying this is because it was able to root an S4 5.0.1 rom that was released well after the S5 OG5 rom was released. I was thinking that they would've implemented the same root-fixes into the S4 as the S5 so if the mobilego method worked on the patched S4 rom then it should have a good chance of working on the S5. I would test all this myself but I sold my brother's S5 a couple days ago.

I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install Heimdall For S5
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method

jrkruse said:
I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install Heimdall For S5
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method
Click to expand...
Click to collapse
Thanks for your input jrkruse! I read here http://mobile.tumblrvip.com/2015/09/23/successfully-downgrade-from-bog5-kernel-to-any-kernel-solved/ that Odin 3.10 should allow S5 users to downgrade OG5 to any older kernel supposedly.

jrkruse said:
I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method
Click to expand...
Click to collapse
Thanks for the detailed instructions. Somebody may want to keep trying this. I got an error on step 9 relating to libusb, is that the drivers?
---------- Post added at 06:11 AM ---------- Previous post was at 06:01 AM ----------
MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?
Click to expand...
Click to collapse
Okay. Here's my assessment of the ODIN method.
OG5 on OG5 Kernel - MobileGo Cannot Root this
OG5 on OE1 Kernel - MobileGo Cannot Root This
OG5 on OC4 Kernel - MobileGo Cannot Root This
OG5 on NI2 Kernel - Bad idea. I was stuck in a boot loop for like an hour before I got back to Download mode to reflash the whole stock image.
You can flash any of these kernels from ODIN, and you can flash everything back to rescue yourself. If you leave one of the older kernels on your phone too long, it will soft brick. If somebody figures out a root method that works, ODIN will be able to help use move between Kernels. This has been a fun first foray into Android Hacking. I still hate my phone.
Thank you fates13 and jrkruse, you guys rock.

MySonsDad said:
Thanks for the detailed instructions. Somebody may want to keep trying this. I got an error on step 9 relating to libusb, is that the drivers?
---------- Post added at 06:11 AM ---------- Previous post was at 06:01 AM ----------
Okay. Here's my assessment of the ODIN method.
OG5 on OG5 Kernel - MobileGo Cannot Root this
OG5 on OE1 Kernel - MobileGo Cannot Root This
OG5 on OC4 Kernel - MobileGo Cannot Root This
OG5 on NI2 Kernel - Bad idea. I was stuck in a boot loop for like an hour before I got back to Download mode to reflash the whole stock image.
You can flash any of these kernels from ODIN, and you can flash everything back to rescue yourself. If you leave one of the older kernels on your phone too long, it will soft brick. If somebody figures out a root method that works, ODIN will be able to help use move between Kernels. This has been a fun first foray into Android Hacking. I still hate my phone.
Thank you fates13 and jrkruse, you guys rock.
Click to expand...
Click to collapse
Thanks for testing!

All those people complaining that their updated device can't be rooted, not willing to try this out?

Can confirm that the root does not work and that the NI2 kernel will not successfully boot lollipop. Root might be theoretically possible if NI2 could boot....any thoughts on how to get into lollipop with the NI2 kernel in place?

ldeveraux said:
All those people complaining that their updated device can't be rooted, not willing to try this out?
Click to expand...
Click to collapse
I have an unrooted VZW S5 with OG5 and would like to give it a shot, but download mode hasn't worked for me since OE1. Holding power+vol down+home just boots the device normally. I've tried holding them all the way through the boot, which causes the phone to repeatedly reboot. Am I missing something?
Edit: Nevermind, guess I was pressing power first. I've got download mode now. Will report back if I make any progress...

Verizon
This is unfortunate.
So we are back to square one?
But if I understand, MySonsDad confirmed we have no reason to not update to OK3 since we can jump between the locked kernels?

So no root for 5.0? I've got to start researching these things before I buy a phone.

brd912 said:
So no root for 5.0? I've got to start researching these things before I buy a phone.
Click to expand...
Click to collapse
Same here, I figured it would be a similar process as rooting my Nexus 5 when I was on AT&T. The Verizon and Samsung bloatware is painful when it can't be removed.

Is there no update on this? I'm willing to anything at this point.

[7.0/8.0][WW] ZE520KL FOTA Update Links

Moving forward, let's add OTA Update links here for users who cannot receive OTA notifications.
Flash via stock recovery. If your system has been modified, you may need to flash stock system image or the stock firmware.
IMPORTANT: Do not boot to system immediately!! Flash the no-verity file via TWRP first, then reboot:
No-verity file
[7.0] ZE520KL OTA (for WW SKU only)
WW_14.2015.1701.13
WW_14.2020.1703.28
WW_14.2020.1704.38
WW_14.2020.1706.53
WW_14.2020.1708.56
WW_14.2020.1709.68
WW_14.2020.1711.75
WW_14.2020.1711.80
WW_14.2020.1711.81
WW_14.2020.1712.85
[8.0] ZE520KL OTA (for WW SKU only)
WW_15.0410.1712.31 (Initial release. Expect some bugs. Must be on latest Nougat build.)
WW_15.0410.1801.40
WW_15.0410.1802.44
WW_15.0410.1803.53
WW_15.0410.1803.55
WW_15.0410.1804.61
WW_15.0410.1804.62
WW_15.0410.1806.65
WW_15.0410.1806.68
credits:
@gkillershots for the WW_14.2015.1701.13 link
@spica1234 for the WW_14.2020.1703.28 and .38 links
@Eng.Raman for the WW_14.2020.1706.53, .56, .68, .75, .80, .81 and WW_15.0410.1712.31, .40, .44, .53, .61, .65, -68 links
@vaidhy2007 for the WW_14.2020.1712.85 link
@AL_IRAQI for the WW_15.0410.1803.55 link
@pop4xda for the WW_15.0410.1804.62 link
(Still looking for anyone who wish to provide FOTA links for ZE552KL.)

How about link for ZE552KL (Z012D)?

cdanthien said:
How about link for ZE552KL (Z012D)?
Click to expand...
Click to collapse
I tried to get it too, but since my phone is the z017, it can only see ota's for itself.
but the ota only patches system, boot and radio, so if someone is couraged to port, it may be not that hard.
for z017 ota links, mention me everytime a new one appears and i'll give the link for it.
if someone unlocked a z012 with unofficial method, contact me so I help you get the link to post here and help the community.

gkillershots said:
I tried to get it too, but since my phone is the z017, it can only see ota's for itself.
but the ota only patches system, boot and radio, so if someone is couraged to port, it may be not that hard.
for z017 ota links, mention me everytime a new one appears and i'll give the link for it.
if someone unlocked a z012 with unofficial method, contact me so I help you get the link to post here and help the community.
Click to expand...
Click to collapse
Give me guide for Z012D, i will guide again to my friend. Thanks

cdanthien said:
Give me guide for Z012D, i will guide again to my friend. Thanks
Click to expand...
Click to collapse
hit the update button, It'll give you the update notification, then open the folder /data/data/com.asus.dm/files/
If you don't want to continue from here, just pass me the tree.xml
If you want, open it on an editor like notepad++
then look into the <value> that has a link inside.
example: <value>http://fota.asus.com/delta_package/phone/WW_Phone/formal/14.2015.1701.8-user-WW_Phone-14.2015.1701.13-user-WW_Phone-QWWSSS/WW_ZE520KL-14.2015.1701.8-14.2015.1701.13-fota-user.zip.dd_20170317_151859.dd</value>
copy ONLY the link, put into the browser and It'll download you an dd file
ex: http://fota.asus.com/delta_package/...5.1701.13-fota-user.zip.dd_20170317_151859.dd
open this dd file on notepad ++
the <objectURI> is the link for the ota

gkillershots said:
hit the update button, It'll give you the update notification, then open the folder /data/data/com.asus.dm/files/
If you don't want to continue from here, just pass me the tree.xml
If you want, open it on an editor like notepad++
then look into the <value> that has a link inside.
example: <value>http://fota.asus.com/delta_package/phone/WW_Phone/formal/14.2015.1701.8-user-WW_Phone-14.2015.1701.13-user-WW_Phone-QWWSSS/WW_ZE520KL-14.2015.1701.8-14.2015.1701.13-fota-user.zip.dd_20170317_151859.dd</value>
copy ONLY the link, put into the browser and It'll download you an dd file
ex: http://fota.asus.com/delta_package/...5.1701.13-fota-user.zip.dd_20170317_151859.dd
open this dd file on notepad ++
the <objectURI> is the link for the ota
Click to expand...
Click to collapse
I edited ZE520KL to ZE552KL, but i received "File not found"

cdanthien said:
I edited ZE520KL to ZE552KL, but i received "File not found"
Click to expand...
Click to collapse
I tought you would do it on a ze552kl
if it were that simple, I would've done it myself

any guide how to install this? using twrp or stock recovery?

updated Tizen V2.1 here : https://forum.xda-developers.com/zenfone-3/development/rom-tizen-rom-nougat-1701-8-ze552kl-t3573231

gkillershots said:
i tried to get it too, but since my phone is the z017, it can only see ota's for itself.
But the ota only patches system, boot and radio, so if someone is couraged to port, it may be not that hard.
For z017 ota links, mention me everytime a new one appears and i'll give the link for it.
If someone unlocked a z012 with unofficial method, contact me so i help you get the link to post here and help the community.
Click to expand...
Click to collapse
thank you so much!!

Z520KL : 14.2020.1703.28
14.2020.1703.28

Thanks for uploading the new update, we are appreciate it :good:

can I update? I am rooted, no changes made except flashing TWRP

mecoromeo said:
can I update? I am rooted, no changes made except flashing TWRP
Click to expand...
Click to collapse
Make a backup first, flash stock recovery, then flash the OTA updates. Remember to flash no verity file before first boot

animaanimus said:
Make a backup first, flash stock recovery, then flash the OTA updates. Remember to flash no verity file before first boot
Click to expand...
Click to collapse
Is the flashfire app effective? I tried it and updated to the latest ze520kl update. Everything went smoothly, but, I am not sure why but my wifi was disabled. I tried clearing cache and did not work. Not sure if the app did not work correctly or if it was an issue with the latest update. That said i downgraded using the same tool and got everything working again.
I think there is an issue with the new update. What do you guys think? Did any of you guys also had an issue with the new update?
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
spica1234 said:
Z520KL : 14.2020.1703.28
14.2020.1703.28
Click to expand...
Click to collapse
I had an issue with the update wherein my wifi was disabled and i couldn't figure out how to fix it. I rebooted, clearing cache, i even tried flashing it again and resetting everything. None worled.
I went back to the previous version and now my phone is working fine.
Did anyone else encounter this issue with this update? If so, please help me to avoid it from happening, i want to try this update

mecoromeo said:
Is the flashfire app effective? I tried it and updated to the latest ze520kl update. Everything went smoothly, but, I am not sure why but my wifi was disabled. I tried clearing cache and did not work. Not sure if the app did not work correctly or if it was an issue with the latest update. That said i downgraded using the same tool and got everything working again.
I think there is an issue with the new update. What do you guys think? Did any of you guys also had an issue with the new update?
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
I had an issue with the update wherein my wifi was disabled and i couldn't figure out how to fix it. I rebooted, clearing cache, i even tried flashing it again and resetting everything. None worled.
I went back to the previous version and now my phone is working fine.
Did anyone else encounter this issue with this update? If so, please help me to avoid it from happening, i want to try this update
Click to expand...
Click to collapse
This is what I do follow while applying Delta OTA.
No need to flash back stock boot/recoveries and no need as well to reinstall twrp back.
Steps using FlashFire, Flash as zip/ota option:
1. Load 'UL-ASUS_Z017D_1-WW-14.2015.1701.8-user'
2. Load 'WW_ZE520KL-14.2015.1701.8-14.2015.1701.13-fota-user'
3. Load 'WW_ZE520KL-14.2015.1701.13-14.2020.1703.28-fota-user'
4. Remove tickmark from 'Inject SuperSU'
5. Add SuperSU zip, Which I've modded according to asus ramdisk of ours. Which is attached in here under my post.
Flash!
Note: FlashFire will take a minute or two to load flash, have patience.
* Reason I've to edit standard SuperSU package was for 'init.asus.rc' file in our ramdisk, which unset PATH during 'on init' event. So i added those params back in supersu's zip to append '/su/bin' in PATH

spica1234 said:
This is what I do follow while applying Delta OTA.
No need to flash back stock boot/recoveries and no need as well to reinstall twrp back.
Steps using FlashFire, Flash as zip/ota option:
1. Load 'UL-ASUS_Z017D_1-WW-14.2015.1701.8-user'
2. Load 'WW_ZE520KL-14.2015.1701.8-14.2015.1701.13-fota-user'
3. Load 'WW_ZE520KL-14.2015.1701.13-14.2020.1703.28-fota-user'
4. Remove tickmark from 'Inject SuperSU'
5. Add SuperSU zip, Which I've modded according to asus ramdisk of ours. Which is attached in here under my post.
Flash!
Note: FlashFire will take a minute or two to load flash, have patience.
* Reason I've to edit standard SuperSU package was for 'init.asus.rc' file in our ramdisk, which unset PATH during 'on init' event. So i added those params back in supersu's zip to append '/su/bin' in PATH
Click to expand...
Click to collapse
Thanks. Haven't tried it yet, but i will though.
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"

mecoromeo said:
Thanks. Haven't tried it yet, but i will though.
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"
Click to expand...
Click to collapse
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"

mecoromeo said:
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"
Click to expand...
Click to collapse
I'm facing the same issue after OTA update!
My fone is rooted too!

mecoromeo said:
Hi. I tried it again using the steps mentioned above and I still get the issue "wifi disabled"
Click to expand...
Click to collapse
Hello,
Sorry for that I got it now why it's happened.
Follow an extra step.
Extract ".28" firmware replace META-INF folder with attached below.
Zip the '.28' firmware back and rename it as 28_dummy.zip
Now follow above flashfire load 1-4 steps and as a 5th step add '28_dummy.zip' and as a 6th step as above supersu step and it'd definately work.

Any ODIN flashable Rom Request

hi all, I've managed to brick my SM-P900.
Could someone point me to where I can get an Odin flashable rom please, with all the individual bits such as PDA / Phone / CSC.
I can't flash normal roms, it's not working with just the md5. Ideally stock, but happy with any rom as I can flash something else with TWRP.
I can't use any of the normal samsung sites as they're paid, and I'm broke =(
I would really appreciate it if you could help me fix this.
Many thanks

Google
SM-P900 - Samsung Firmware | Samsung Updated
---------- Post added at 03:14 AM ---------- Previous post was at 03:09 AM ----------
https://forum.xda-developers.com/galaxy-note-pro-12/general/firmware-firmware-t3038178

Where you able to solve your problem?

bmwdroid said:
Where you able to solve your problem?
Click to expand...
Click to collapse
x2 for me also

sp000n said:
x2 for me also
Click to expand...
Click to collapse
Sorry, don't understand.
Problems or just interested as well?

Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!

Zophixan said:
Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!
Click to expand...
Click to collapse
Did you get the multiple part ROM using samfirm_reborn tool?

bmwdroid said:
Did you get the multiple part ROM using samfirm_reborn tool?
Click to expand...
Click to collapse
Just tried downloading it and I get .tar.md5 file, not sure how i did it but from a previous attempt at fixing it, I have the same thing but in seperate files, with boot, cache, hidden, recovery s boot and system. Do i need to put them into odin? where do they go? I get stuck on initialising, tried pulling out cable and putting it back in, then it says it can't find a pit partition... tried flashing a pit file but still stuck on initiailising so pit doesn't flash.

@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?

bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
I've tried odin 3.07 and 1.85. I downloaded samfirm_reborn and upon use it downloaded just one file "SM-P900_1_20170222195126_gly008r5gf.zip" and inside it is the tar md5. Where can I get the separate items?
Even if I am not using the seperated one, shouldn't odin flash? It's always stuck on intiailising, I don't know if this matters but it says knox warranty 0500 on the download screen, and custom kernal / binary.
I remember having a similiar problem years ago on the same tablet but no idea how I fixed it, vaguely remember downloading seperate files to flash in each of the odin sections.
thanks.
EDIT, found the binary option nature option, will download now and try flashing each bit and report back...

bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
Still stuck on initializing, tried samsung drivers, even tried heimdall (and installed it's drivers), is there anything else I can try?
It says AP SWREV A1 and know warranty voide 0500, and current binary / system status as custom on the tablet.

Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.

bmwdroid said:
Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.
Click to expand...
Click to collapse
I tried both 3.10 and 3.09 but still stuck on initialisation... (do i need to do anything with CP or UMS field?),
does the current binary/ system status as custom ,or AP SWREV A1, or knox warranty mean anything?
Do you have any other suggestions, I can't think of anything else! =(

Knox was triggered when flashing other than stock.
Forget about it.
Other is shown on mine as well.
CP stays empty at WiFi models.
UMS I've never did anything with.
Try to use other cables and USB ports.