[Q] Flashing 4.4.4 in N910V Odin FAIL - Verizon Galaxy Note 4 Q&A, Help & Troubleshooting

I don't think this has already been answered here but this is my problem.
So I bought the Samsung Galaxy Note 4 from Amazon brand new with Lollipop 5.0.1 already preinstalled. After using it for a while I've noticed lag in Google Maps and the Google App. I then watched and read some tutorials about how to downgrade to KitKat 4.4.4 and using Odin, I successfully rolled back with no problem.
However, I was facing OTA update notifications quite frequently and I knew there was a way to turn them off I just never bothered to do so. Eventually I hit update on accident and I was forced to wait for the update to finish knowing that I could easily rollback to 4.4.4 right after. Well, once Lollipop finished it's 5.0.1 update (same one I had before), I headed back onto Odin, wiped cache partition using plain recovery mode, then went into download mode to prepare to flash 4.4.4 like I've done previously. Unfortunately, Odin said FAIL and no matter what I've tried it would always say FAIL. I've tried different USB ports, different USB cables...nothing. I then tried to root my device using CF Auto Root through Odin hoping to get TWRP and install CM12.1 , to which I was greeted with another FAIL in Odon. I am not sure why this is happening since I have done this before and it worked no problem. I doubt that my bootloader is locked because its the same 5.0.1 update that I had previously. I will post the FAIL details of Odin later when I get computer access since I am typing this on my phone.
Please help.

densmenace said:
I don't think this has already been answered here but this is my problem.
So I bought the Samsung Galaxy Note 4 from Amazon brand new with Lollipop 5.0.1 already preinstalled. After using it for a while I've noticed lag in Google Maps and the Google App. I then watched and read some tutorials about how to downgrade to KitKat 4.4.4 and using Odin, I successfully rolled back with no problem.
However, I was facing OTA update notifications quite frequently and I knew there was a way to turn them off I just never bothered to do so. Eventually I hit update on accident and I was forced to wait for the update to finish knowing that I could easily rollback to 4.4.4 right after. Well, once Lollipop finished it's 5.0.1 update (same one I had before), I headed back onto Odin, wiped cache partition using plain recovery mode, then went into download mode to prepare to flash 4.4.4 like I've done previously. Unfortunately, Odin said FAIL and no matter what I've tried it would always say FAIL. I've tried different USB ports, different USB cables...nothing. I then tried to root my device using CF Auto Root through Odin hoping to get TWRP and install CM12.1 , to which I was greeted with another FAIL in Odon. I am not sure why this is happening since I have done this before and it worked no problem. I doubt that my bootloader is locked because its the same 5.0.1 update that I had previously. I will post the FAIL details of Odin later when I get computer access since I am typing this on my phone.
Please help.
Click to expand...
Click to collapse
My understanding is that if you are on 5.0.1 and take a newer update, you can no longer roll back to 4.4.4. This is why there is a debloat program to prevent the OTA updates. I was in the same boat - got a new GN4 which came preinstalled with 5.0.1. I decided not to install the SIMM card and set the phone up instead over wifi so Verizon wouldn't see it until I had protected myself against the forced updates. I hope I'm wrong in that there is still a way for you to roll back to 4.4.4. Good luck.

Happen to use on sprint they locked our bootloader kies don't even work no more

This is the detailed info I receive upon failure of flashing CF Auto Root.
Code:
<ID:0/003> Added!!
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also in the top left corner in red it says "SECURE CHECK FAIL : recovery
What does this mean? Is there a way I can flash anything on my Note 4?

The latest OTA from Verizon prevents users from being able to downgrade the Note 4. That's why it fails in odin. No going back now.
Sent from my SM-N910V using Tapatalk

outcasted2003 said:
The latest OTA from Verizon prevents users from being able to downgrade the Note 4. That's why it fails in odin. No going back now.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I got this failed message when I attempted to update, now I'm stuck with the phone only booting into Odin Mode where it says "Software Update Failed" How can I recover from here? Any help is very much appreciated.

I'm assuming you had stock verizon retail lp build ending in OF1 or OG5? If it was then you can NOT downgrade or flash the note 4. The only way to fix it that I know of is to run the Verizon Upgrade/Repair Assist Program.
Sent from my Galaxy Note 4 using Tapatalk

Related

[Q] Help Un-Soft-bricking SGH-i747M

I have soft-bricked my GS3 - SGH-i747M.
I can still get into the Galaxy S3 Download Mode screen (Pressing VOLUME Down + HOME + POWER button), and am running ODIN3 v3.07.
But I have not been able to restore my backed ROM, nor a couple of "stock" ROMs that I have downloaded.
I ran into trouble trying to get the proper ClockwordMod installed.
Any suggestions would be appreciated. Thanks
Start from scratch. Load a image using Odin and re do it all. Root etc
Sent from my Samsung Galaxy S3
when i soft bricked my phone i just followed this thread and reflashed the stock rooted rom. This method of rooting involves flashing a stock rom with root injected into it so in essence you are just flashing back to stock. No need to wipe data before doing this process (at least in my experience)
The thread also includes the steps to get clockworkmod
success
that got it Florad, thanks much
*HELP* Friend Soft Bricked my phone
Let my self proclaimed tech savy friend borrow my phone for a few days... He decides to root it for me in thanks.
Now, all it is able to do is access the Download Function. No Recovery, instead I get a message saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Kies will not recognize the phone and connect. On boot it shows the SAMSUNG logo and shuts off. Sometimes on boot it just shows an empty battery. LED no longer comes on...
It is a Samsung gs3 sgh-i747m from the MTS Allstream carrier.
I have searched forum after forum to find what to do. Downloaded every Firmware rom from a Canadian provider (except MTS 'cause there just isn't any out there with valid links), tried to flash with Odin3 v3.07 .... no luck. Everything fails.
Phones are not really my language. From what I get he was trying to root:
RecoveryGalaxyS3USCanada.tar
SuperUser.zip
which worked but SuperSU kept crashing so he tired:
Siyah-s3-v1.9.1.tar
which caused the crash. since then I can only imagine what other things he tried in attempts of recovery before giving it back to me to figure out.
As for the few Roms (This one being Telus) I have attempted in hopes to reverse it, this has always been the result in Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MVLALE8_I747MOYBALE8_20120523.225040_REV04_user_low_ship.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Any help would be greatly appreciated.
Did you install latest 4.3 firmware. Do you have a line that says Knox in download mode.?
SaHiLzZ said:
Did you install latest 4.3 firmware. Do you have a line that says Knox in download mode.?
Click to expand...
Click to collapse
There is nothing saying anything about Knox
Odin Mode
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: YES (15 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWERV: 1
SECURE CHECK FAIL: aboot
As for the latest firmware, Im not exactly sure what I am looking for or where to get it. Like I said, not my language.
Wow 15 counts.. awesome!
S it looks like it was on 4.3 at some point of time.
1. You will need to pick a carrier file from here, http://forum.xda-developers.com/showthread.php?t=2543854 , and download it (really slow downloads) and use ODIN to install it.
OR
2. Follow this thread here, it is for Note 2, but same idea applies to your S3 for Emergency firmware recovery: http://forum.xda-developers.com/showthread.php?t=2261153
Good luck and post back, I will suggest #2 as it is not your language..
help v.v
first, im new here and don't know much on how things work, so im sorry if ive caused problems posting this. i rooted my galaxy i747. didn't install clockwork like an idiot and tried to put siyah firmware on my phone. when Odin tried to reboot my phone my phone just shut off and Odin said <something> Removed! except with numbers where i put something. since then ive tried to put normal fiemwares back on and nothing has worked. i even tried the method here http://forum.xda-developers.com/showthread.php?t=1739426 and that just failed or froze every time. i don't know what to do. i can try to start my phone. the Samsung white letters pop up then vanish and nothing. sometimes it will get to the galaxy s 3 screen then blackness. im stressed and have been trying to fix this for two days and really need help :crying: :crying:
anyone who can help will be greatly appreciated!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
formulaF said:
first, im new here and don't know much on how things work, so im sorry if ive caused problems posting this. i rooted my galaxy i747. didn't install clockwork like an idiot and tried to put siyah firmware on my phone. when Odin tried to reboot my phone my phone just shut off and Odin said <something> Removed! except with numbers where i put something. since then ive tried to put normal fiemwares back on and nothing has worked. i even tried the method here http://forum.xda-developers.com/showthread.php?t=1739426 and that just failed or froze every time. i don't know what to do. i can try to start my phone. the Samsung white letters pop up then vanish and nothing. sometimes it will get to the galaxy s 3 screen then blackness. im stressed and have been trying to fix this for two days and really need help :crying: :crying:
anyone who can help will be greatly appreciated!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
What bootloader was on your phone before flashing? Can you get into download mode?

s3 shutting off on its own and rebooting =/

So this problem just started today and came out of no where without any precursors. Worse thing is away from home working in the middle of nowhere in New Mexico without any real Tmo stores in the 5 hour vicinity.
My phone pretty much vibrates and turns on when battery is put in. Sometimes it will boot up, sometimes it wont. And when it does boot up, it will easily shut off or stay on for 10 minutes at the most.Tried a few other batts, but same thing. i even reflashed frosty rom and same thing.
I called tmo and they're working on sending me a phone as it is apparent that its a hardware issue- however it won't help my dependence on this phone as it I rely on it for work and daily duties.
I'm rooted via samsung toolkit and running frosty JB. I completely forgot how to revert back to stock as I am also using custom recovery from toolkit. Any direction? Also, will Tmo care if I leave the flashcounter untouched?
Yes they care if the flash counter is touched . use the search button or Google how to revert back to stock with 0 flash counter ..
Sent from my SGH-T999 using xda premium
can i just triangle away -> reflash stock recover thru odin via toolkit -> flash stock boot image via toolkit ....and done?
liberalswine said:
can i just triangle away -> reflash stock recover thru odin via toolkit -> flash stock boot image via toolkit ....and done?
Click to expand...
Click to collapse
heres the tutorial http://forum.xda-developers.com/showthread.php?t=2136921
ok why not go back to nandroid? its not a hardware issue there must be some kind of bugs
re: step by step info.
liberalswine said:
So this problem just started today and came out of no where without any precursors. Worse thing is away from home working in the middle of nowhere in New Mexico without any real Tmo stores in the 5 hour vicinity.
My phone pretty much vibrates and turns on when battery is put in. Sometimes it will boot up, sometimes it wont. And when it does boot up, it will easily shut off or stay on for 10 minutes at the most.Tried a few other batts, but same thing. i even reflashed frosty rom and same thing.
I called tmo and they're working on sending me a phone as it is apparent that its a hardware issue- however it won't help my dependence on this phone as it I rely on it for work and daily duties.
I'm rooted via samsung toolkit and running frosty JB. I completely forgot how to revert back to stock as I am also using custom recovery from toolkit. Any direction? Also, will Tmo care if I leave the flashcounter untouched?
Click to expand...
Click to collapse
If you can get the phone into download mode here is a sure fix for it, if you have a windows computer handy you
will need to use that OR you can go to the play store and download "mobile odin" and flash the stock rooted T999
rom without the need for any computers at all.
This guide will get your phone back up and running properly, doing anything else will just prolong your problem.
Easy and sure way to fix error 7 and other issues or problems - Here is the step by step guide:
After doing this you will end up with a stock-pre-rooted T999 Tmobile Touchwiz 4.1.2 rom which works properly.
You will not loose any of your pictures, videos or music by doing this.
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
umm, well i was able to setup and root the new phone that came in.
However, i'm having issues loading the stock .tar file I downloaded through Odin and receive this message:
<OSM> All threads completed. (succeed 0 / failed 0)
I also was unable to flash stock recovery file via odin and received the same message. Any thoughts?
re: Odin flash
liberalswine said:
umm, well i was able to setup and root the new phone that came in.
However, i'm having issues loading the stock .tar file I downloaded through Odin and receive this message:
<OSM> All threads completed. (succeed 0 / failed 0)
I also was unable to flash stock recovery file via odin and received the same message. Any thoughts?
Click to expand...
Click to collapse
There are a lot of people who don't have a tmobile T999 phone but instead they have a I9300 I hope you are not one of those people.
Everything found here in this thread pertains to the T999 Tmobile S3 phones. (sorry about having to make this comment but I just had to)
Forget about flashing stock recovery file with ODIN that was not part of the step by step instructions.
Only follow the step by step or things may get more complicated.
Did the [COM:XX] light up green or yellow in Odin after you plugged it into the usb of the computer before you started the flash?
BE SURE YOUR PHONE IS A Galaxy S3 Tmobile T999 (or you might end up with a shiny brick).
Unplug the usb cable from the phone before anything else and do NOT change any of the default settings in Odin.
#1: Open Odin
#2: Put the TAR file into the PDA slot in Odin
#3: Put the phone into download mode
#4: Connect the usb cable from computer to the phone
#5: Be sure that the [COM:XX] lights up in Odin
#6: Start the flash and have patience it may take up to 10 minutes
Good luck!
I was able to get it connected after trying out several different USB ports as the main culprit. But now Odin has been stuck for an hour and a half...
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<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> boot.img
I'm not sure if I should let it sit longer. It has been exactly one hour, 32 minutes. What to do...?
re: try this.
liberalswine said:
I was able to get it connected after trying out several different USB ports as the main culprit. But now Odin has been stuck for an hour and a half...
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<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> boot.img
I'm not sure if I should let it sit longer. It has been exactly one hour, 32 minutes. What to do...?
Click to expand...
Click to collapse
It should not take any more than at most 10 minutes. No need to let it sit there not doing anything.
Perhaps the TAR file got corrupted during the extraction or perhaps for whatever reason the
actual download of the rom got corrupted during downloading.
If I were you I would re-download the T999 stock rooted rom again and start all over, be sure you delete the
download which you first downloaded as to not make a mistake and use the first download.
Be sure that your battery is charged, if the battery is too low it may not want to continue the Odin flash.
So turn off the phone and plug it into the WALL charger it will charge 20% faster than usb, let it charge
for at least 45 minutes before trying to flash again.
Good luck.
i'm trying once more. The download file seems legit. =/
You can also find the firmware and a lot of info in my thread. Link in sig.
Do you have kies installed? If so get rid of it. It screws with Odin.
Sent from my SGH-T999 using xda premium
Currently stuck in this process:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDLJC_T999TMBDLJC_T999UVDLJC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> aboot.mbn
its been about 12 minutes
It's been over 30 minutes again and this is beginning to frustrate me. Everything looks good, but Odin just seems unresponsive and doesn't get anywhere past the firmware installation. I've tried two different stock firmware downloads. One directly from the tutorial previously listed, and one updated through samsung toolkit. Not sure what's going on and I need to return this phone back to Tmo
That sounds like a problem a lot of people have when kies is installed. If you don't have it installed you may want to try reinstalling the latest usb drivers. Ill post the link in a few mins.
For now though, be patient and see if it fails out. Avoid interrupting the process unless absolutely necessary.
Sent from my SGH-T999 using xda premium
Just uninstalled kies though I'm not quite sure if it's culprit here. Re attempting, i hope this works otherwise I'm out of options to getting my phone back to stock in time.
Does any one know if tmo/samsung really checks the phone once my "defected" unit is sent back?
liberalswine said:
Just uninstalled kies though I'm not quite sure if it's culprit here. Re attempting, i hope this works otherwise I'm out of options to getting my phone back to stock in time.
Does any one know if tmo/samsung really checks the phone once my "defected" unit is sent back?
Click to expand...
Click to collapse
Kies also contains the USB drivers, so you will probably need to reload those.
Here is the link to my drivers folder. Latest version I have is 1.5.23.0.
http://androidfilehost.com/?a=show&w=files&flid=1368
re: Odin flash.
DocHoliday77 said:
Kies also contains the USB drivers, so you will probably need to reload those.
Here is the link to my drivers folder. Latest version I have is 1.5.23.0.
http://androidfilehost.com/?a=show&w=files&flid=1368
Click to expand...
Click to collapse
About 5-6 or so posts ago I told liberalswine to uninstall kies, reboot computer and I gave him the official samsung
link for the proper usb drivers, I am not sure if he already uninstalled kies and & installed the samsung usb drivers
and if he rebooted the computer one more time before trying to odin flash the stock-rooted T999 4.1.2 firmware.
It's really strange that he is having so much trouble flashing the firmware with Odin
unless the actual TAR file is corrupted in one way or another.
I already told him to re-download the firmware and try the odin flash again a couple hours ago.
Just thought to let you know.
re: don't understand the question
richadorsey4 said:
Do we need to uninstall the stock app to flash this
Click to expand...
Click to collapse
I would like to give you a informed answer, but your question lacks any specifics,
I just don't know exactly what you mean or are talking about, looking back at some
previous posts here I see nothing that pertains to uninstalling any apps.
Try to ask your questions with a lot more details so we can know what exactly are asking about.
Misterjunky said:
About 5-6 or so posts ago I told liberalswine to uninstall kies, reboot computer and I gave him the official samsung
link for the proper usb drivers, I am not sure if he already uninstalled kies and & installed the samsung usb drivers
and if he rebooted the computer one more time before trying to odin flash the stock-rooted T999 4.1.2 firmware.
It's really strange that he is having so much trouble flashing the firmware with Odin
unless the actual TAR file is corrupted in one way or another.
I already told him to re-download the firmware and try the odin flash again a couple hours ago.
Just thought to let you know.
Click to expand...
Click to collapse
Any official FW will have an md5sum that Odin will check. If using anything else its wise to always check the md5 on dev-host or AFH and make sure what you download matches.
As for drivers, Sammy doesnt release the usb drivers as a standalone install, only with kies. Never found them anyway. Also forgot to mention, that link you posted is bad, so you may want to recheck it.
Sent from my SGH-T999 using xda premium

[Help Me Please] Kernel not seandroid enforcing

Hello,
Let me start off by saying, I'm a complete newbie when it comes to rooting (Infact - It took me a few days to even convince myself to do this) and I did look around for several guilds on how to remove this error (Downloaded Odin - Got Stock TAR.MD5) But I still get this error on my phone when I start the phone, it wouldn't be much of a probelm, except it hangs for a while and then restarts.) It also gets stuck for a long time at the T-Mobile load screen. The Wifi Wont turn on either... Please Help.
Galaxy S4: SGH-M919
T-Mobile...
Ghhostt said:
Hello,
Let me start off by saying, I'm a complete newbie when it comes to rooting (Infact - It took me a few days to even convince myself to do this) and I did look around for several guilds on how to remove this error (Downloaded Odin - Got Stock TAR.MD5) But I still get this error on my phone when I start the phone, it wouldn't be much of a probelm, except it hangs for a while and then restarts.) It also gets stuck for a long time at the T-Mobile load screen. The Wifi Wont turn on either... Please Help.
Galaxy S4: SGH-M919
T-Mobile...
Click to expand...
Click to collapse
Do you remember if you were on 4.3 or 4.2.2 before flashing with Odin?
Vigz said:
Do you remember if you were on 4.3 or 4.2.2 before flashing with Odin?
Click to expand...
Click to collapse
I was 4.3.
Ghhostt said:
I was 4.3.
Click to expand...
Click to collapse
Alright.
Download this .zip file and extract the .tar.md5 file. Flash that with Odin. https://copy.com/1yJkfBBGa4VwTzl
You should boot back into your phone normally. If it never boots successfully (if the t-mobile boot screen never goes away), go into recovery mode. Press Volume Up + Power + Home to access Recovery Mode. Then, wipe data/factory reset and reboot (use volume keys to navigate and power to hit enter). The easiest way to root the phone is to use CF Auto-Root (http://forum.xda-developers.com/showpost.php?p=41797154&postcount=2). Rooting voids warranty. Before 4.3, it was very easy to get warranty back. Now, it's a different story.
Vigz said:
Do you remember if you were on 4.3 or 4.2.2 before flashing with Odin?
Click to expand...
Click to collapse
Vigz said:
Alright.
Download this .zip file and extract the .tar.md5 file. Flash that with Odin. https://copy.com/1yJkfBBGa4VwTzl
You should boot back into your phone normally. If it never boots successfully (if the t-mobile boot screen never goes away), go into recovery mode. Press Volume Up + Power + Home to access Recovery Mode. Then, wipe data/factory reset and reboot (use volume keys to navigate and power to hit enter). The easiest way to root the phone is to use CF Auto-Root (http://forum.xda-developers.com/showpost.php?p=41797154&postcount=2). Rooting voids warranty. Before 4.3, it was very easy to get warranty back. Now, it's a different story.
Click to expand...
Click to collapse
Thank for providing a link that won't take 2+ hours to download I'm downloading it now and might flash or keep for future use. I gave up yesterday and ended up flashing my phone to Wicked 9.1 and well... I have no complaints against it atm. I actually like it, that and Themer Beta. So I think i'll keep it for now. I know that the warranty is already gone so why try holding on to old stock image when there's other opportunities to explore.
THank you for your replies and +Thanks to all; I will keep reading forums here and keep trying to expand what i know so that I can get better at this :victory: .
Thanks again,
D.
PS: If a way becomes available where I can restore my phone and get official updates again, then i might restore it; but I don't think Knox is letting me anywhere near that for the time being.
Ghhostt said:
Thank for providing a link that won't take 2+ hours to download I'm downloading it now and might flash or keep for future use. I gave up yesterday and ended up flashing my phone to Wicked 9.1 and well... I have no complaints against it atm. I actually like it, that and Themer Beta. So I think i'll keep it for now. I know that the warranty is already gone so why try holding on to old stock image when there's other opportunities to explore.
THank you for your replies and +Thanks to all; I will keep reading forums here and keep trying to expand what i know so that I can get better at this :victory: .
Thanks again,
D.
PS: If a way becomes available where I can restore my phone and get official updates again, then i might restore it; but I don't think Knox is letting me anywhere near that for the time being.
Click to expand...
Click to collapse
We will have to wait for the next update and whether it will install if the counter is 0x1. Just recently, the 4.4.2 update was leaked out for international S4 users. Most have said that it updates even if their Knox Warranty Void counter is at 0x1.
Vigz said:
We will have to wait for the next update and whether it will install if the counter is 0x1. Just recently, the 4.4.2 update was leaked out for international S4 users. Most have said that it updates even if their Knox Warranty Void counter is at 0x1.
Click to expand...
Click to collapse
Sweet! that's great news! Maybe it'll actually work and I can restore my phone :laugh:
Vigz said:
We will have to wait for the next update and whether it will install if the counter is 0x1. Just recently, the 4.4.2 update was leaked out for international S4 users. Most have said that it updates even if their Knox Warranty Void counter is at 0x1.
Click to expand...
Click to collapse
Hey, so i tried restoring my phone to stock with the image you gave me and im sad to say that it still didn't work ... Odin still says failed. Anything you can do further to help?
This is what Odin says:
<ID:0/003> Added!!
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
Hmm, that's odd. The download link that I gave you normally flashes fine on my phone. Try redownloading it and flash it again. If that doesn't work, perhaps you may need to reset the flash counter before using Odin with an app called Triangle Away.
Kernel is not sea....(and won't boot up.. screen stays off with Blue light blinking
Kernel is not sea....(and won't boot up.. screen stays off with Blue light blinking)
pls help me... it happened when i try to unroot my phone using modified cf-autorroot... in 4.3 os...
pls help me what do i do.. i havent intalled any recovery.....

[Q] bricked samsung note pro 12.2

I tried rooting my note with ODIN following directions from this site and seem to have bricked it. I had rooted it several months ago but had a random rebooting problem so I un-rooted it then did a factory reset and my random rebooting went away so I wanted to try rooting again. Every thing seemed to go OK until the end. Towards the end I get
<ID:0/009> NAND Write Start!!
<ID:0/009> cache.img
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The tablet stays in the download position. It will not restart. If I try to restart it I get the following message
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I don't know how to get to Kies. The only thing I can get to is ODIN MODE - Downloading. I can not even turn the tablet off.
I have spent half a day searching this site for a solution because I don't like to have to ask for help but I am stuck. I have tried so many things I may have made it worse. Any help I can get will truly be appreciated.
The model number is SM-P900ZWVXAR
Thank You
Do a Google search for your stock firmware and flash with odin
Thank you tgamble160 for the quick response. I couldn't find the firmware for my phone by model number. Couldn't find firmware for the Galaxy Note Pro 12.2 (wifi) for the US or North America either. Could find it for just about any other country. I could find a Cellular south (XAR) firmware from SamMobile that I believe will work. It is a slow download. I tried to pay for a faster download but it did not go through so the slow download. In another hour I should have it and will let you know if it worked.
It worked. It is 2am here. I am going to bed and will try rooting it again when I get up.

Galaxy SGH-I747 on 4.2.2 ROOTED Softbricked after AT&T OTA

Had stock AT&T SGH-I747 at Android 4.2.2 rooted with chainfire working fine. Today an update installed automatically and now I'm dead.
At first, it would show the Samsung logo and maybe another, then just go black.
Now normal booting, or attempting to boot into recovery gives: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
If attempt to boot into download mode, it succeeds. But everything will end up with "FAIL!" in Odin and show "fused 3 > binary 0" on the phone. I've tried multiple Odins: v3.10.6, 3.09, 3.07 and multiple recoveries (Clockwork 6.0.4.7, etc.) and stock ROMS (UCALG1, UCDLK3).
Even Kies "Firmware Upgrade and Initialiasion" option, where you enter in SGH-I747 and the serial number will go through all the motions and then fail, with the same "fused" message showing on the phone.
Grendelin had the most similar situation (I can't post external links yet, but you can get to it at http:__androidforums.comthreads_at-t-gs3-at-t-issues-after-downloading-newest-update.860382_ by replacing _'s with /'s) as me but the difference is that he was able to flash a recovery image which led to further restoration.
Please help. If it's not possible to recover this, I would just like to get a couple years' worth of pictures from /sdcard/DCIM/*.
When you boot into download mode, do you see anything about warranty bit?
You could try and flash TWRP using Odin, then boot to TWRP and mount the data partition to see if you can copy the data from the phone to your computer.
audit13 said:
When you boot into download mode, do you see anything about warranty bit? You could try and flash TWRP using Odin, then boot to TWRP and mount the data partition to see if you can copy the data from the phone to your computer.
Click to expand...
Click to collapse
I tried TWRP (specifically twrp-2.8.7.0-d2att.img.tar) using Odin and it gave all the usual signals that it's working before the box turns red and it says "FAIL!" on it. Here's its log in case it's useful:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialization..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yes download mode does mention the waranty bit. Here's the full text:
Code:
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SWREV: 3
Are you using version 3.07 of Odin? Did you uncheck everythign except f.reset time before flashing?
What about flashing Philz Touch for the d2lte? I was suggesting TWRP because you may be able to re-flash a rooted nj1 system and boot img.
I asked about warranty bit to make sure that the phone was running a 4.3 or newer bootloader. As you may know, the 4.3 bootloader cannot be downgraded so you can't flash anything from sammobile.
Yes, 3.07, and there were only two things checked, "F. Reset Time" and "Auto Reboot". At your suggestion I unchecked the latter but it appeared to have no effect on the flashing success.
Can't get to philz's dev files at the moment since his page at goo.im is down.
I don't understand what is meant by 4.3 bootloader. Isn't 4.3 referring to the Android version? While Android lists the bootloader version in its properties, Android in principle shouldn't be concerned about what lower level, hardware specific bootloader brought it up, should it?
I really need my phone back
dreamluvr said:
Yes, 3.07, and there were only two things checked, "F. Reset Time" and "Auto Reboot". At your suggestion I unchecked the latter but it appeared to have no effect on the flashing success.
Can't get to philz's dev files at the moment since his page at goo.im is down.
I don't understand what is meant by 4.3 bootloader. Isn't 4.3 referring to the Android version? While Android lists the bootloader version in its properties, Android in principle shouldn't be concerned about what lower level, hardware specific bootloader brought it up, should it?
I really need my phone back
Click to expand...
Click to collapse
I really hate to tell you this but I don't think your going to get this fixed yourself. If Odin is failing like that your probably going to need a debricking service that can flash your emmc directly. If you can get a recovery back on then you'll be fine cause you can then flash firmware to repair the damage the OTA did. Keep trying I guess but ultimately you'll probably need the debricking service.
When bootloaders are refered to as 4.3 or 4.4.2 is just referring it to the OS version they came with in the OTA. And while on a pc this is true windows isn't dependent on the lower lever firmware, Android kinda is... least the OEM's have made it that way.
Most people say that if you can reach download mode then you're OK. I can't believe this ****ing phone is just going to sit here and reject everything that's sent to it. In some cases I'm sending it stock stuff.
It's bull**** that AT&T can just impose their updates like this. Yes I had modifications that probably interfered with their intended update, but they obviously exercised no caution, not checking that everything was in their expected state before overwriting.
I'm upset that I supported a gimped device, one that's cryptographically preventing user modifications when it's user paid for.
Is there no hope in simply making a disc image, mounting it, and recovering /sdcard/DCIM ?
I had a similar problem a week ago. I got this i747 and decided to wipe it using kies. I didn't know about the boot loader problem after the kitkat OTA upgrade. So I had a soft brick like you. I ran into the same problems using Odin to flash the twrp tar and various other images. What I decided to do was flash twrp multiple time using odin. But during one of the reboots I think I removed the cable and put it back (maybe even pulled the battery?) in time for odin to check and say it was successful. Then i had a semi-functional twrp to flash the rooted ucfnj1 image from the i747 dev forum. I still have root issues, but my phone works.
bump before I mail it off to unbrick service
looking for any ideas
short summary: canNOT boot into recovery, CAN boot into download, but Odin always fails and phone says "fused 3 > binary 0"
EDIT (Sept 8, 2015): I used mipick22's JTAG services on ebay and he fixed it. Good price, good communication, etc. Says he's a member on here but didn't give his username.

Categories

Resources