Q&A for [GUIDE][HOWTO] ODIN to Stock Unrooted Firmware [NK4]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][HOWTO] ODIN to Stock Unrooted Firmware [NK4]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can I use this method to unroot if I'm on NK4 rooted?
After I've followed every step, my phone still gets stuck in the same boot loop as always. It never loads to recovery mood after flashing the stock ROM using Odin v3.09.
I used the NK4 rom. Am I doing anything incorrectly? I've tried loads of different things to get past this boot loop.
re: rooting and recovery
whatishappening said:
After I've followed every step, my phone still gets stuck in the same boot loop as always. It never loads to recovery mood after flashing the stock ROM using Odin v3.09.
I used the NK4 rom. Am I doing anything incorrectly? I've tried loads of different things to get past this boot loop.
Click to expand...
Click to collapse
Here are the steps you need to do to root and install custom recovery:
1: Download and Odin flash cf-autoroot which can be found here:
https://www.dropbox.com/s/jokv7avj6pphjkq/CF-Auto-Root-trltetmo-trltetmo-smn910t.tar?dl=0
2: Download and Odin flash twrp custom recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.1.1-trltetmo.tar
Once you have successfully odin flashed both the TAR files you should have root
and custom recovery too.
Good luck!
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.1.1-trltetmo.tar
Misterjunky said:
Here are the steps you need to do to root and install custom recovery:
1: Download and Odin flash cf-autoroot which can be found here:
link removed
2: Download and Odin flash twrp custom recovery which can be found here:
link removed
Once you have successfully odin flashed both the TAR files you should have root
and custom recovery too.
Good luck!
[/URL]
Click to expand...
Click to collapse
is it possible that my problem of being stuck in a boot loop and restarting is due to a fully drained battery?
I asked because my phone doesn't ever charge when plugged in, it instead immediately attempts to boot. Should I purchase a second battery and attempt to boot?
---------- Post added at 01:25 AM ---------- Previous post was at 01:18 AM ----------
I've attempted to flash that recovery image multiple times. It's an .img file. How am I supposed to attach it using ODIN PDA?
re: tar files
whatishappening said:
is it possible that my problem of being stuck in a boot loop and restarting is due to a fully drained battery?
I asked because my phone doesn't ever charge when plugged in, it instead immediately attempts to boot. Should I purchase a second battery and attempt to boot?
---------- Post added at 01:25 AM ---------- Previous post was at 01:18 AM ----------
I've attempted to flash that recovery image multiple times. It's an .img file. How am I supposed to attach it using ODIN PDA?
Click to expand...
Click to collapse
I don't know where you got the IMG file, but both of the links I posted
only contain TAR files which needs to be flashed in Odin's PDA slot.
My mistake was unzipping the recovery file when I should have not been doing that. I've done both of the things you suggested and now my phone auto boots with a battery icon and continuously boot loops, but instead of saying "Samsung Galaxy Note 4" for a second before boot looping, it shows the battery icon.
youtube.com/watch?v=Bj6Zssy3-ZQ&feature=youtu.be
I apologize for linking as a new member, but this is not spam and I had to modify the link to include a video demonstration of what I'm describing. Thank you.
---------- Post added at 02:02 AM ---------- Previous post was at 01:38 AM ----------
whatishappening said:
My mistake was unzipping the recovery file when I should have not been doing that. I've done both of the things you suggested and now my phone auto boots with a battery icon and continuously boot loops, but instead of saying "Samsung Galaxy Note 4" for a second before boot looping, it shows the battery icon.
youtube.com/watch?v=Bj6Zssy3-ZQ&feature=youtu.be
I apologize for linking as a new member, but this is not spam and I had to modify the link to include a video demonstration of what I'm describing. Thank you.
Click to expand...
Click to collapse
Just for fun, here is a video of what happens when I attempt to boot into recovery mode. Notice that I do not need to press the power button because my phone always attempts to auto-turn on when it is plugged in.
youtube.com/watch?v=zgbqQTuImcM&feature=youtu.be
My Note 4 is stuck in a boot loop after flashing. It gets to the T-Mobile logo, stays there for about 30 seconds and reboots. Any way around this?
Thanks in advance.
Foxhoundz said:
My Note 4 is stuck in a boot loop after flashing. It gets to the T-Mobile logo, stays there for about 30 seconds and reboots. Any way around this?
Thanks in advance.
Click to expand...
Click to collapse
Try redownloading the firmware and reflashing.
Sometimes downloads have hiccups.
Just used the exact same file and flashed today, worked fine as usual (usually flash stock about once a week).
Sent from my trltetmo using XDA Premium 4 mobile app
I was able to get it working.
For those facing the boot loops, simply go into the stock recovery mode during boot and clear your cache. That should fix any remaining issues.
Also, always make sure to factory reset before the first boot.
Perfect!
Perfect, flawless tutorial. Worked Great, ready for Lollipop OTA!
Baseband and Bootloader
For some reason I downloaded the baseband and bootloader for ANK4.
I Odin'd back to stock successfully and am wondering if I need to flash this too.
Still "custom" after unrooting
Unrooted my t-mobile note 4 using the guide, went to re-root using the same method I did before, chainfire/twrp, and get an error when hitting the start button in Odin. Every time. Even after unroot the device status still says custom. Could that be affecting re-root? Anyone else have this issue?
I've asked before in this thread:
http://forum.xda-developers.com/note-4-tmobile/help/root-unroot-kies-t3003971
Sorry for link but didn't want to copy/paste everything.
Have you tried a different version of Odin? I usually rock 3.0.4
Android_Monsters said:
Have you tried a different version of Odin? I usually rock 3.0.4
Click to expand...
Click to collapse
I've tried every version of Odin I can find... And multiple CF sources.
Razorfengraul said:
I've tried every version of Odin I can find... And multiple CF sources.
Click to expand...
Click to collapse
I've used this method multiple times to stock and re root, haven't had any problems.
Few things that may he the problem...
Are you using the factory cord that came with your device?
Are you putting your device in download mode?
Are you turning on debugging in the Developer Settings?
Do you have the correct drivers for your device?
Sent from my SM-N910T using XDA Premium 4 mobile app
devynbf said:
I've used this method multiple times to stock and re root, haven't had any problems.
Few things that may he the problem...
Are you using the factory cord that came with your device?
Are you putting your device in download mode?
Are you turning on debugging in the Developer Settings?
Do you have the correct drivers for your device?
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes to everything other than the Samsung cable... Would that really make a difference?
Alright, as stated, I've followed this guide flawlessly... Factory reset before first boot, wiped cache, everything. Device status still showed "custom" and i was unable to download OTA updates due to custom binary. (mundane, i know, but proves my point)
So i went to re-root.
This is my command line in Odin upon flashing CF Auto Root:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What am i missing... Every version of Odin out there and every available CF download i can find... Happens every time.
Razorfengraul said:
Yes to everything other than the Samsung cable... Would that really make a difference?
Click to expand...
Click to collapse
Yes, ODIN sometimes only works if you have the original Factory Cable.
I've run into MANY problems (like the one you're explaining) when not using the cord that came with it.
That's your problem. Use the factory cord.
Sent from my SM-N910T using XDA Premium 4 mobile app
Related
Hi, I have rooted my tab ,no problem. But I read all the posts about EXT4 and kernel flashing needed for flashing roms, but I cannot find a definitive guide on how to flash the kernel using odin or EXT4.
Can anyone help with a small , simple guide on how to do this please?
I've been looking for hours and darent try it without knowing fully how.
Thanks
Stu.
Galaxy Tab UK
Recovery mod installed and Rom backed up.
Havent looked yet but i quick guide would be great if it doesnt already exist.
Sent from my HTC HD2 using XDA App
You can follow the instructions from this thread
http://forum.xda-developers.com/showthread.php?t=925760
Stu308 said:
Hi, I have rooted my tab ,no problem. But I read all the posts about EXT4 and kernel flashing needed for flashing roms, but I cannot find a definitive guide on how to flash the kernel using odin or EXT4.
Can anyone help with a small , simple guide on how to do this please?
I've been looking for hours and darent try it without knowing fully how.
Thanks
Stu.
Galaxy Tab UK
Recovery mod installed and Rom backed up.
Click to expand...
Click to collapse
Sent from my GT-P1000 using Tapatalk
Seen that post , but it doesnt say what to do with odin? As in where to load the .tar file etc.
You flash the Modaco kernel via Odin, if your file system isn't ext4 (which it won't be then you may need to manually reboot your phone - My phone still rebooted automatically coming from a rfs file system)
Once your phone reboots it should enter recovery automatically and you just sit back and let CWM backup / covert your file system to ext4 / restore your rom back on to your coverted file system
(I believe there are instance also when you phone does not automatically enter recovery on reboot, in this situation you will need to manually enter recover after flashing the kernel in Odin - to do this you hold down the power button and volume up)
Another thing worth noting, i had encountered an issue during the conversion process where CWM was not able to restore my existing rom, when this happens you can download a ext4 rom (i.e. modaco rom or overcome 1.1.3) and flash the file via CWM - i.e. you can leave the kernel and try another Rom.
Hope this helps.
thanks bendjlee, but how do I use odin? (where to put .tar file which mode should tab be in etc..).
Stu308 said:
thanks bendjlee, but how do I use odin? (where to put .tar file which mode should tab be in etc..).
Click to expand...
Click to collapse
under pda
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
This is what I get, doesnt work. Should I be in recovery or the phone in normal mode?
I also had "fail" in red in the left had box of odin, my tab is rooted and clockwork mod installed. What is wrong?
You'll need to put your tab to download mode first before connecting to your computer to odin. Turn on the tab with "volume down" held
Stu308 said:
I also had "fail" in red in the left had box of odin, my tab is rooted and clockwork mod installed. What is wrong?
Click to expand...
Click to collapse
Sent from my GT-P1000 using Tapatalk
ahh, will try it that way , but Im sure I tried that. Do I put phone in debugging mode before I go into download mode?
Download mode is different than recovery and debug. It would display an image of an android with a shovel. That is the mode you need to be in.
Even though the question was asked by someone else, these attempts to answer the question helped solve a similar problem on my side. Thanks!
I've been trying to Flash V700XXUAMK7_V700OXAAMK7_HOME.tar.md5 (BTU) to my Galaxy gear, it got bricked and now I'm sitting in the "Firmware upgrade encountered an issue. Please select Recover mode in Kies & try again."
Well Kies isn't connecting to it and Odin results in a Fail no matter what I try. I've tried it on Odin 3.09, 3.07, 3.04. I've tried resetting but can't get to the download boot or any of that. I've tried different roms, I've tried Kies, and I can't find a way out.
Any help?
Try a different cable? Cheap cables can cause problems
Brendo said:
Try a different cable? Cheap cables can cause problems
Click to expand...
Click to collapse
I'm using the best cable I have.
Also try a different computer,,,
If it helps this is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> V700XXUAMK7_V700OXAAMK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
crutzulee said:
Also try a different computer,,,
Click to expand...
Click to collapse
I tried a different computer, both cords, version 3.09 and 3.07 with the same MK7 file and it throws out the same log I posted.
EDIT: 3.09 Starts to work, then it crashes.
CarbonWyre said:
I tried a different computer, both cords, version 3.09 and 3.07 with the same MK7 file and it throws out the same log I posted.
EDIT: 3.09 Starts to work, then it crashes.
Click to expand...
Click to collapse
sounds like you got a bad download on your MK7 check the file size i bet its wrong.
rob8178 said:
sounds like you got a bad download on your MK7 check the file size i bet its wrong.
Click to expand...
Click to collapse
Where do you recommend downloading it from?
rob8178 said:
sounds like you got a bad download on your MK7 check the file size i bet its wrong.
Click to expand...
Click to collapse
I redownloaded and re unzipped, same thing happened. Odin just crashed after clicking start
CarbonWyre said:
I redownloaded and re unzipped, same thing happened. Odin just crashed after clicking start
Click to expand...
Click to collapse
Has anyone gotten a solution here? I can't get Odin/Kies/Fastboot to bring this back to life. I was trying to flash Tizen and got here instead.
And minutes later Odin makes me a liar and flashes an stock android img onto the little bugger and I am back in business, thanks anyway!!
Same thing happened to me.. you will have to do one of two things. . Search for the tizen downgrade. Sorry don't have link handy. .. or flash the original tizen update not the newest nf1 then flash the nf1 after successful flash... the problem is you flashed the newest nf1 before having the tizen bootloader. .. and right now you are trying to flash android on a jacked up tizen bootloader. .. give me a min to search for you and I will post links
Sent from my SM-G900T using Tapatalk
---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------
Tizen downgrade. ...
http://forum.xda-developers.com/showthread.php?t=2776157
Oh yeah don't forget thanks
Sent from my SM-G900T using Tapatalk
---------- Post added at 01:30 AM ---------- Previous post was at 01:27 AM ----------
Flash this first... then flash NF1 ... and I hope it goes with out saying flash in oden
http://forum.xda-developers.com/showthread.php?t=2767465
Sent from my SM-G900T using Tapatalk
Very Thanks !
Thanks you !
Flash this version of Tizen is only way to back to Tizen after downgrade from Tizen to Android ( i know it isn't very clever )
I try flash many tizen firmwares but, ONLY this working.
Kies Updates doesn't work, only ODIN.
Think I've Bricked My Gear
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please
trisha3010 said:
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please
Click to expand...
Click to collapse
No need to get back to recovery or download mode. Use odin and follow instructions by @fireishott above. I have just restored my gear from the 'Firmware Upgrade Encountered a problem' screen. It should be recognised by odin 3.09. You can try another computer, and also press the power button as if you are rebooting the gear. The screen will go off then you get the 'firmware....' screen again. Ensure you have latest samsung drivers.
Good luck.
trisha3010 said:
So have encountered the same problems as above. Was trying to restore my gear back to original setting via odin but got the message - Firmware Upgrade Encountered A Problem - Now can't get it back into recovery mode or anything odin won't recognise it either so can't even try any of the solutions given.
Any ideas how to get it into recovery or download mode...please
Click to expand...
Click to collapse
I used Odin3.07 and 4.2.2 stock ROM to flash first - I used PHONE option because the others didn't work (no progress in the message window). This 'faulty' flash came up with a 'UI stopped working error' when the Gear rebooted but I was able to get it into download mode now. I then used Odin 3.09 and the flashed the 4.2.2 as a PIT which worked fine!
Got there after reading through a lot of XDA threads and trying many things. But in the end, the answers were here. Thanks.
PS how I got into the mess (the firmware error message with the yellow triangle)? I was on null 23 and wanted to go back to stock rom so that I could sell the Gear. Couldn't get into download mode for Odin 3.09; I can't exactly remember what I did but I disconnected the gear midway through a seemingly failed flash and it got me to the error. Googling says use Kies but nope, it wouldn't recognise the gear even for the 'emergency firmware'. I tried a lot of things, and wasted a lot of time!
Big Thanks
chobochobo said:
I used Odin3.07 and 4.2.2 stock ROM to flash first - I used PHONE option because the others didn't work (no progress in the message window). This 'faulty' flash came up with a 'UI stopped working error' when the Gear rebooted but I was able to get it into download mode now. I then used Odin 3.09 and the flashed the 4.2.2 as a PIT which worked fine!
Got there after reading through a lot of XDA threads and trying many things. But in the end, the answers were here. Thanks.
PS how I got into the mess (the firmware error message with the yellow triangle)? I was on null 23 and wanted to go back to stock rom so that I could sell the Gear. Couldn't get into download mode for Odin 3.09; I can't exactly remember what I did but I disconnected the gear midway through a seemingly failed flash and it got me to the error. Googling says use Kies but nope, it wouldn't recognise the gear even for the 'emergency firmware'. I tried a lot of things, and wasted a lot of time!
Click to expand...
Click to collapse
Hi Everyone HUGE thanks managed to follow instructions and gear is back up and working. Just wanted to check I only flashed the tizen downgrade (ie-image 1) and this automatically rebooted the galaxy back to original settings without having to reflash the NF1 is this ok or should i flash this anyway. Many thanks again for the replies as everyone here was telling me it was beyond repair.
i was in the same situation last week kept getting same errors,decided to try different computer and went here and downloaded (http://samsung-updates.com/device/?id=SM-V700) and picked 4.2.2 btu version and went through with no error and got it back up and going
Further Problems
trisha3010 said:
Hi Everyone HUGE thanks managed to follow instructions and gear is back up and working. Just wanted to check I only flashed the tizen downgrade (ie-image 1) and this automatically rebooted the galaxy back to original settings without having to reflash the NF1 is this ok or should i flash this anyway. Many thanks again for the replies as everyone here was telling me it was beyond repair.
Click to expand...
Click to collapse
Hi everyone can't believe this but hit the reset button in the settings app and the gear has now rebooted and stuck on the Samsung screen with nothing working - odin not recognising it and even when i try to reboot in recovery mode it just keeps reverting back to same Samsung screen ... any help or suggestions would be appreciated.
solved for me
shayind4 said:
No need to get back to recovery or download mode. Use odin and follow instructions by @fireishott above. I have just restored my gear from the 'Firmware Upgrade Encountered a problem' screen. It should be recognised by odin 3.09. You can try another computer, and also press the power button as if you are rebooting the gear. The screen will go off then you get the 'firmware....' screen again. Ensure you have latest samsung drivers.
Good luck.
Click to expand...
Click to collapse
solved for me.the problem was that i didnt press the POWER button.
I had same issue after getting stuck on zimage during flashing of Tizen over Null rom. I simple flashed null rom thru odin as a phone rom and it booted back into null rom. Gear is back up and fuctioning.
Sent from my SPH-L900 using XDA Premium 4 mobile app
[Q&A] [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/2
Q&A for [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/24
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL/UTILITY][TWRP][2.8][RECOVERY] TWRP 2.8.1.1 TeamWin Recovery Project 10/24. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Problem Flashing TWRP to T-Mobile Note 4 in ODIN...PLZ HELP
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.
Ttw626 said:
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.
Click to expand...
Click to collapse
Can you try verifying the md5 of the file from the place you downloaded TWRP from?
How do I verify it
re: odin flash issues
Ttw626 said:
I am trying to flash TWRP to my Note 4 for T-Mobile via ODIN 3.09 & 3.07 with no luck at all. I have downloaded many different files for TWRP for T-mobile's Note 4 but none of them work at all I keep getting the same error message from Odin. PLEASE some1 HELP me I have never had this issue before with Samsung phones until now and I am completly lost on what to do to get it to work. . Here is the message I get when I try to flash using Odin 3.09 or 3.07:
<ID:0/012> Initialzation...
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0/ failed 1)
I have Auto Reboot & F . Rest Time checked everything else is unchecked.
openrecovery-twrp-2.8.1.0-trltetmo.img.tar is the file I have to flash.
PLEASE PLEASE PLEASE some1 help me get this to work PLEASE.
Click to expand...
Click to collapse
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!
bigbiff said:
Can you try verifying the md5 of the file from the place you downloaded TWRP from?
Click to expand...
Click to collapse
How do I verify it?
---------- Post added at 02:25 PM ---------- Previous post was at 02:13 PM ----------
Misterjunky said:
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!
Click to expand...
Click to collapse
Misterjunky i think relock is on in the phone ill disable it and try again i didnt think of that before thanks.
Misterjunky said:
Be sure that the "Reactivation lock" in settings>security is Unchecked
and be sure that you have USB debugging enabled before odin flashing.
After doing that you should no longer have odin flashing errors or issues.
Good luck!
Click to expand...
Click to collapse
Great it took this time thanks alot sir :good:
@bigbiff...VZW Note 4 stock recovery image is here....
http://forum.xda-developers.com/showthread.php?p=56385923
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.4.13
nicee 5*
I accidentally wiped my sd card in twrp and now I'm having trouble downloading from a lot of apps. How can I fix this? Would I have to Odin back to a stock firmware to get it back to where it was? Titanium back up and other apps say I have insufficient space, but I know I have a good amount. I reflashed the ROM I've been on and started fresh, but I'm still having issues. Thanks in advanced.
re: titanium backup
paranoid android85 said:
I accidentally wiped my sd card in twrp and now I'm having trouble downloading from a lot of apps. How can I fix this? Would I have to Odin back to a stock firmware to get it back to where it was? Titanium back up and other apps say I have insufficient space, but I know I have a good amount. I reflashed the ROM I've been on and started fresh, but I'm still having issues. Thanks in advanced.
Click to expand...
Click to collapse
Uninstall titanium backup and re-download/install it from the play store then have titanium backup
detect backup location under preferences>backup location in settings then restart titanium backup.
Once you do that it will work fine.
Good luck!
TWRP 2.8.1.0 is not installing on my Tmo Galaxy Note 4
I don't know what's going on guys. I know I am doing everything the right way but for some reason whenever i get back to turning the phone off hitting Vol up/Home/ Power key it takes me to the android boot screen vs the twrp android boot screen.
I am using the img.tar file in odin under the pda option
I have odin set to auto re-boot
i turn the phone off and hit the command
nothing.
Using this twrp in odin
openrecovery-twrp-2.8.4.0-trltetmo.img.tar
if someone can please help me out greatly appreciated.
Is the phone rooted? With bootloader unlocked? Did u use CF auto root?
If so u can flash recovery with FLASHIFY [ https://play.google.com/store/apps/details?id=com.cgollner.flashify] from the play store. Just download the .IMG file for TWRP in the app and let it flash it.
Sent from my SM-N910T using XDA Free mobile app
Thanks for your help man I did end up figuring it out. For some reason the auto reboot was causing the issue. I had to turn that off and manually pull the battery out etc for it to work.
Worked great and I'm now running cm12
thanks for this
I'm guessing twrp 3.0.0 dosent work for the kindle fire (otter) right?
AlbGol said:
I gave you the correct file for what you need to do if you have the n910t, for more specifics look the post above me.
Here is the correct way of installing twrp 3.0 image file, straight from your existing recovery (twrp)
When you boot into your current Recovery 2.8.7.0 and click on Install - Bottom Right you'll see a Image Button - Click on this - The next Screen will show Boot and Recovery - You want to click on Recovery and Swipe to install.
Thats it. (All the phones that I did this were N910T, so was the image file for my device trltmo)
Here is the direct link for twrp 3.0 image file for 910t
https://www.androidfilehost.com/?fid=24407100847294047
Also if u have different model(carrier) just find it here and follow the steps:
http://forum.xda-developers.com/not...-utility-twrp-2-8-1-0-teamwin-t2915588/page44
Click to expand...
Click to collapse
Hey, HUGE problem here. I did this I may have totally bricked my phone. im freaking out.
Please help me
Stuck on recovery booting and cannot even get into download mode. Plugged into comp, I do get a chime .
Is it time to Jtag?
What are my options. Please help
Remove battery, install battery...use button combo to enter download mode and flash 2.87 with odin...
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw
manbat said:
Remove battery, install battery...use button combo to enter download mode and flash 2.87 with odin...
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw
Click to expand...
Click to collapse
Button combo does not work, goes to recovery booting loop. This is the problem. That's the first thing i did. I haven't seen a hard brick on any of my devices in 12 years.
A little back information to clear up how this started; a friend of mine has some very serious mental health issues and over factory reset his SM-G900A because he is paranoid someone will get his phone and steal his information. Its not stolen or found. The reactivation lock was triggered and hes so overly medicated he cant figure out what his Samsung account information is to recover it. He claims to have sent it back to Samsung and they couldn't recover it. I'm new to modding androids but have had a lot of success tweaking my SGH-I537.
I tried to reinstall the stock firmware to get around the reactivation lock. When i checked the properties of the phone on my pc it said it was running G900AUCU4BOF3 firmware. But a google search told me that the OF3 was a OTA to downgrade it to NCE. Several attempts with Odin "failed" every time and brought me rite back to the reactivation lock. Until the last attempt with my third different set of NCE files ended with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" warning on boot up. But Kies or Smart Switch wont connect to the device now.
Can someone help me please?
You can only flash OF3. I also sent you a private message with a link to lead you to help.
I'm brand new to this site and just opened the message. I have seen this bypass but my current problem is in stuck at the boot up warning "firmware upgrade encountered an issue. Please select recovery mode in keys and try again." kies and smart switch won't recognize the device. And when I run nce through Odin the operation falls
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
I have also tried several different versions of the fix you sent me. I don't think that particular one though. But at the moment I can't get any firmware to load
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
I've been working on this for about four days now. The closest I came to success was at one point when I restarted the phone while attached to my pc it restored to my sgh-i537 settings. I don't know how it happened but the phone was working. Thinking I had fixed it I did the factory reset to get rid of my information and let my friend put his in. When it rebooted it was back to the reactivation lock. If I could get the sm-g900a to reset to my sgh-i537 again I would just leave it but it's refusing to do anything for me.
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
It would seem that I need the g900aucu4bof3 update but there's no way to do an ota and I can't find it in a downloadable file
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Same problem here, I have received this error every time after trying to flash firmware from numerous sources and boot loaders as well.
"<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!"
Interested to see if anyone has a fix to offer
That's the exact message I get from Odin.
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
try this
retlawb42 said:
A little back information to clear up how this started; a friend of mine has some very serious mental health issues and over factory reset his SM-G900A because he is paranoid someone will get his phone and steal his information. Its not stolen or found. The reactivation lock was triggered and hes so overly medicated he cant figure out what his Samsung account information is to recover it. He claims to have sent it back to Samsung and they couldn't recover it. I'm new to modding androids but have had a lot of success tweaking my SGH-I537.
I tried to reinstall the stock firmware to get around the reactivation lock. When i checked the properties of the phone on my pc it said it was running G900AUCU4BOF3 firmware. But a google search told me that the OF3 was a OTA to downgrade it to NCE. Several attempts with Odin "failed" every time and brought me rite back to the reactivation lock. Until the last attempt with my third different set of NCE files ended with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" warning on boot up. But Kies or Smart Switch wont connect to the device now.
Can someone help me please?
Click to expand...
Click to collapse
hello,
Get the Lollipop 5.0 STOCK Offficial ROM for AT&T S5 SM-G900A.
https://
drive.google.com/file/d/0B2QQ1ShKpLTtYjU0aDJCLVFFSFk/view?usp=sharing
(this is a link to download)
This file is a odin one click, download, connect your phone s5 at&t and then start (sure that the drivers s5 is well in your pc)
What bootloader have you tried _OK?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
retlawb42 said:
What bootloader have you tried _OK?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
If your bug is on the bootloader , then you enter this web:
http://
www.droidviews.com/fix-invalid-ext4...while-installing-firmware-on-samsung-devices/
I had the same problem and solve it with this . download the pit files and follow the steps.
the pit file , you will fix the bootloader , the other link odin one click, contains the official firmware 5.0 , connect , start and done .
barbozaip said:
hello,
Get the Lollipop 5.0 STOCK Offficial ROM for AT&T S5 SM-G900A.
https://
drive.google.com/file/d/0B2QQ1ShKpLTtYjU0aDJCLVFFSFk/view?usp=sharing
(this is a link to download)
This file is a odin one click, download, connect your phone s5 at&t and then start (sure that the drivers s5 is well in your pc)
Click to expand...
Click to collapse
I have tried he BOC4 one click zip. It ends with the same operation fail message that _ok got. Are there AP files for Odin for lollipop? I didnt find any but im also getting frustrated at this point.
retlawb42 said:
I have tried he BOC4 one click zip. It ends with the same operation fail message that _ok got. Are there AP files for Odin for lollipop? I didnt find any but im also getting frustrated at this point.
Click to expand...
Click to collapse
You could post the picture of error?
try to connect the cel to the PC in another USB port and try again.
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
retlawb42 said:
I have tried he BOC4 one click zip. It ends with the same operation fail message that _ok got. Are there AP files for Odin for lollipop? I didnt find any but im also getting frustrated at this point.
Click to expand...
Click to collapse
remember unzip the zip file. connect the phone , run the unzipped file and then start . It is an executable file that contains the firmware of Odin and everything you need to restore your device .
The xtc4 didn't work. In the next page I tried the kies emergency recovery and got stuck at the recovery code part. I do have screen shots of everything. Give me a few minutes to get to my pc and backtrack to see if I missed anything
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
This is the error from the lollipop one click zip
Sorry if these arent in order or rite format. Let me know if they are unacceptable. These are the errors for the NCE
last ones
retlawb42 said:
last ones
Click to expand...
Click to collapse
I seem to be having the exact, same problem. I've tried every possible solution posted thus far, with no success
So now after flashing with the NCE pit and all AP files with just the auto reboot and re-partition checked I get this screen after the phone looks for an update. Not there yet but at least one step further. Any ideas?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
retlawb42 said:
This is the error from the lollipop one click zip
Click to expand...
Click to collapse
It is very strange that does not allow installing the software , I'll do some research about it and help you .
you tried to do it with another USB cable? placing it in another USB port ? even on another computer ? try to run the Odin clicking Administrator Mode also.
Hi, my N910T cannot be rooted. I tried reverting to NJ7 and flashed cf auto root (right file) and it would fail near the end of the process. I tried on COD6 (build number) and it still wouldn't work. I tried installing a custom recovery, and that failed near the end as well. I tried KingRoot on NJ7 (was slightly worried about KingRoot) and it worked (temporarily.) It said failed around 56% but I used root checker and it said I had root. From there I tried using an app like rom manager to try and install and flash a custom recovery. When I booted into recovery, it said something like "Custom Binary blocked by Reactivation lock," with a yellow triangle. I tried to do it multiple times with different apps, each time having to try to revert back to stock because it would be in a boot loop. I also tried NJ7 and NIH. I fixed the custom binary thing, just want to root/install custom recovery. Can anyone help? Sorry if it was kind of hard to follow, went back and forth from time to time. Anyways, thanks! :silly:
Is your device a T3 version? Did you send it in for repairs?
Sent from my SM-N910T using Tapatalk
cyanogen_patrick said:
Hi, my N910T cannot be rooted. I tried reverting to NJ7 and flashed cf auto root (right file) and it would fail near the end of the process. I tried on COD6 (build number) and it still wouldn't work. I tried installing a custom recovery, and that failed near the end as well. I tried KingRoot on NJ7 (was slightly worried about KingRoot) and it worked (temporarily.) It said failed around 56% but I used root checker and it said I had root. From there I tried using an app like rom manager to try and install and flash a custom recovery. When I booted into recovery, it said something like "Custom Binary blocked by Reactivation lock," with a yellow triangle. I tried to do it multiple times with different apps, each time having to try to revert back to stock because it would be in a boot loop. I also tried NJ7 and NIH. I fixed the custom binary thing, just want to root/install custom recovery. Can anyone help? Sorry if it was kind of hard to follow, went back and forth from time to time. Anyways, thanks! :silly:
Click to expand...
Click to collapse
do this, odin cog2, then odin twrp and do a complete flash by going into wipe, advanced wipe then check everything off except the last one which is external sd card, reboot into your system which may take a few minutes and then try to root afterwards using the cf auto root in teks thread
No I didn't, I did that a couple months ago because the finger scanner broke. I'm certain this is the original n910t not the T3, how would I tell?
Pick_A_Name said:
Is your device a T3 version? Did you send it in for repairs?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
No I didn't, I did that a couple months ago because the finger scanner broke. I'm certain this is the original n910t not the T3, how would I tell?
xnknown said:
do this, odin cog2, then odin twrp and do a complete flash by going into wipe, advanced wipe then check everything off except the last one which is external sd card, reboot into your system which may take a few minutes and then try to root afterwards using the cf auto root in teks thread
Click to expand...
Click to collapse
Flashing recovery doesn't work either, thanks for the input though!
cyanogen_patrick said:
No I didn't, I did that a couple months ago because the finger scanner broke. I'm certain this is the original n910t not the T3, how would I tell?
Click to expand...
Click to collapse
Settings> about device> model
Sent from my SM-N910T using Tapatalk
Pick_A_Name said:
Settings> about device> model
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Hahah okay I thought there was another way. I t is an n910t. So how do it root or install recovery on it?
cyanogen_patrick said:
Hahah okay I thought there was another way. I t is an n910t. So how do it root or install recovery on it?
Click to expand...
Click to collapse
Did you try what xnunknown suggested? When in doubt it's always smart to Odin back to stock and start over.
Sent from my SM-N910T using Tapatalk
Pick_A_Name said:
Did you try what xnunknown suggested? When in doubt it's always smart to Odin back to stock and start over.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I tried on NJ7, NIH, and COD6. I didn't flash recovery/cf right as I finished flashing the firmware, I set up the device first. Thanks for the reminder though!
cyanogen_patrick said:
I tried on NJ7, NIH, and COD6. I didn't flash recovery/cf right as I finished flashing the firmware, I set up the device first. Thanks for the reminder though!
Click to expand...
Click to collapse
I'm still saying try following his instructions, which seem to be different than what you're doing.
Sent from my SM-N910T using Tapatalk
Pick_A_Name said:
I'm still saying try following his instructions, which seem to be different than what you're doing.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Okay, I will be back soon.
cyanogen_patrick said:
I tried on NJ7, NIH, and COD6. I didn't flash recovery/cf right as I finished flashing the firmware, I set up the device first. Thanks for the reminder though!
Click to expand...
Click to collapse
odin and then try odining twrp directly afterwards, somethings probably corrupted and you need to wipe the device
Pick_A_Name said:
I'm still saying try following his instructions, which seem to be different than what you're doing.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Didn't work for me.
xnknown said:
do this, odin cog2, then odin twrp and do a complete flash by going into wipe, advanced wipe then check everything off except the last one which is external sd card, reboot into your system which may take a few minutes and then try to root afterwards using the cf auto root in teks thread
Click to expand...
Click to collapse
Sorry for the long wait, completely forgot. It didn't work, thanks! Are there any other ways?
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've figured out that the Complete(Write) operation keeps failing. Does anyone know how to fix this?
You have disabled the "Reactivation Lock" in Settings > Security??
anasmunir said:
You have disabled the "Reactivation Lock" in Settings > Security??
Click to expand...
Click to collapse
Reactivation lock effects it? I remember I factory resetted my phone and I had to bypass my reactivation lock. I tried to turn it off and it didn't work. I will try again after trying to turn reactivation lock off and I will tell you when I can. Thanks for your help!
anasmunir said:
You have disabled the "Reactivation Lock" in Settings > Security??
Click to expand...
Click to collapse
Reactivation. Lock will not shut off.