Develop Bugs

[q] please help!!!bricked!!!

please help me someone i had the stock el29 system and tried to root it with this
http://forum.xda-developers.com/showthread.php?t=1433101&highlight=el29+root
but it froze at factoryfs.im so im waited 25 mins then tried doing the odin manually by putting the file in myself then it went all the way to rqt_close then nothing it stuck.
i need to get rooted cause i want this rom but i will take anything now rooted non rooted i just want my phone fixed.
http://forum.xda-developers.com/showthread.php?t=1512419&highlight=fd24
it (auto root) made my phone say "firmware upgrade encountered and issue. please select recovery mode in kies & try again.
my first device. i couldnt connect to odin and computer wouldnt recognize device so i took it to sprint and they gave me a replacement.
i figured it was a bad download or something so i downloaded it again today and it messed this phone up to only this phone connects to pc and is recognized but when i try to upload the rom on the regular odin and not the one click it stuck at rqt_close and im confused as to what to do now. i dont even have to be rooted anymore i just want a rom on this phone i was out of a phone for 5 days for that Rom and its messed me over again.
1st time it stuck at factoryfs.img then i got replacement and it stuck at modem and then i took out battery after it was froze for like 25 mins. please help me!!!

Have you tried a different USB cable and/or computer?

yes ive tried a different cable but i only have this one computer. its recognizable through odin and my computer im a little dissapointed though. ive been flashing roms for 2 yrs almost and this has never happened to me

TamiaSky said:
yes ive tried a different cable but i only have this one computer. its recognizable through odin and my computer im a little dissapointed though. ive been flashing roms for 2 yrs almost and this has never happened to me
Click to expand...
Click to collapse
Can you get into recovery mode?

no i cant get into recovery just that dreadful notice but i can get into download mode, so thats a good thing im guessing.
i get all the way to the end to rqt_close then it says my device has been removed like odin is kicking me out or something. i dont unplug my phone or anything but it gets all the way to the end then says removed then failed

You get that message whenever ODIN doesn't complete a download. It doesn't mean much, other than the previous download didn't complete.
Is ODIN flashing anything or does it just stop right away?
If you are using regular ODIN, can you double-check you are using the PDA slot and not the Phone slot?

sfhub knows WAY more about Odin then I do but did you also try to Odin a different stock build to see what happens?

sfhub said:
You get that message whenever ODIN doesn't complete a download. It doesn't mean much, other than the previous download didn't complete.
Is ODIN flashing anything or does it just stop right away?
If you are using regular ODIN, can you double-check you are using the PDA slot and not the Phone slot?
Click to expand...
Click to collapse
ive tried the auto packages and doing it manually and when i did it manually i made sure tat it was the pda slot and i unchecked the re-partition when it popped up as well then after looking around on the internet still i used one of the 7-zip packages and used the pit file with it and checked re-partition and still nothing. odin gets all the way to the end right after modem and then sticks on rqt_close then says removed now it just did this
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> recovery.bin
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006>
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
i really hope you guys can help me. im so serious if i get this fixed ill never try to root this phone again. i dont wanna have to get another replacement phone.

MeWarning said:
sfhub knows WAY more about Odin then I do but did you also try to Odin a different stock build to see what happens?
Click to expand...
Click to collapse
no ive only been trying the el29 one the rooted one, then i tried the el29 that was just stock and not rooted.

Is this the NoData or Full version you are flashing?
Try the NoData if you are using the Full.
I'm curious, you were on ICS before. Did you happen to do a wipe/factory restore or nandroid restore using ICS kernel and custom recovery?

TamiaSky said:
no ive only been trying the el29 one the rooted one, then i tried the el29 that was just stock and not rooted.
Click to expand...
Click to collapse
Well first if you look in the reference section B in the one you've been trying to Odin(http://forum.xda-developers.com/showthread.php?t=1433101&highlight=el29+root) there's separate tar files for the modem, kernel, and rom. Why don't you try doing each one one at a time to see if anything will succeed.
And if that doesn't work try to Odin one of the leaked stock ICS builds sfhub has also.

This is what happens when I do it manually without the auto package.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.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> recovery.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
then it freezes

sfhub said:
Is this the NoData or Full version you are flashing?
Try the NoData if you are using the Full.
I'm curious, you were on ICS before. Did you happen to do a wipe/factory restore or nandroid restore using ICS kernel and custom recovery?
Click to expand...
Click to collapse
its the full, and ive never been on ics
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.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> recovery.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
<ID:0/006> data.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
now i will try the no data and see what happens.

thanks guys for helping me with this. the no data is downloading right now and i looked on my computer i tried to flash the ek02 sorry, i forgot that one.

TamiaSky said:
thanks guys for helping me with this. the no data is downloading right now and i looked on my computer i tried to flash the ek02 sorry, i forgot that one.
Click to expand...
Click to collapse
No problem, just let us know how it goes.

Don't worry about flashing the NoData version, you don't have the issue I was thinking you might.
Why don't you just flash the modem by itself and see if that works. As the previous poster mentioned, it is in the 2nd post reference section.
If it doesn't work, then just flash the kernel by itself. It should work, and then your phone shouldn't complain about the last flash failing and theoretically should boot. Basically you have completed flashing everything but the modem.
If it still doesn't boot, then ODIN flash CWM only and then flash the modem from recovery. This will increment your ODIN flash count, but it is better than a phone not working.

sfhub said:
Don't worry about flashing the NoData version, you don't have the issue I was thinking you might.
Why don't you just flash the modem by itself and see if that works. As the previous poster mentioned, it is in the 2nd post reference section.
If it doesn't work, then just flash the kernel by itself. It should work, and then your phone shouldn't complain about the last flash failing and theoretically should boot. Basically you have completed flashing everything but the modem.
If it still doesn't boot, then ODIN flash CWM only and then flash the modem from recovery.
Click to expand...
Click to collapse
so once i flash the modem then how will i know if it worked or not am i jus supposed to try turning my phone on? or do i reflash the auto package after flashing the modem?

TamiaSky said:
so once i flash the modem then how will i know if it worked or not am i jus supposed to try turning my phone on? or do i reflash the auto package after flashing the modem?
Click to expand...
Click to collapse
Just flash the modem. The reboot option should be checked. When it is done flashing the modem, it should reboot. If it hangs like before, boot back into ODIN DL mode and flash just the kernel.
The individual components are 7zip self-extractors, so you double-click on them to get the .tar.md5 file. All the .tar.md5 files can go into the PDA slot (including the modem). No need to use the Phone slot.

sfhub said:
Just flash the modem. The reboot option should be checked. When it is done flashing the modem, it should reboot. If it hangs like before, boot back into ODIN DL mode and flash just the kernel.
The individual components are 7zip self-extractors, so you double-click on them to get the .tar.md5 file. All the .tar.md5 files can go into the PDA slot (including the modem). No need to use the Phone slot.
Click to expand...
Click to collapse
Sfhub,I noticed that a while ago in your directions about having the modem in the PDA slot. Why is it not done in the Phone spot anymore? Just curious is all.

MeWarning said:
Sfhub,I noticed that a while ago in your directions about having the modem in the PDA slot. Why is it not done in the Phone spot anymore? Just curious is all.
Click to expand...
Click to collapse
When you package a modem.bin inside of a .tar.md5 it can flash in both the PDA and Phone slot. It is simpler for the instructions to ask people to always use the PDA slot.
If you flash a modem.bin file itself, then it must go in the Phone slot. If you flash the wrong file in the Phone slot, your phone won't boot. That is why I package things so people always use the PDA slot.

error when flashing ROM via Odin

hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Mashari_F said:
hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
1) Have you tried to use an other usb port?
2) do you use the original usb cable?
3) do you have all the samsung drivers installed?
4) make eure that samsung kies is not running in the background
Hope it helps you
Gesendet von meinem SM-P600 mit Tapatalk

Got the same problem, so recovered it from kies
Skickat från min SM-P605 via Tapatalk

Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.

ronaldphl said:
Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.
Click to expand...
Click to collapse
Is it giving you a FAIL after flashing , or doesn`t show up after a successful flash.
If it doesn`t show up after flashing , re-flash but untick "Auto-Reboot" within odin before flashing & restart manually after flashing.

I have a "Fail after flashing" - complete (Write) - operation failed in Odin

Which odin
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck

FSkyman said:
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck
Click to expand...
Click to collapse
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well

Recovery Flashing
ronaldphl said:
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well
Click to expand...
Click to collapse
Now I am confused are you talking about recovery or rom ?
The only recovery I could get to work was the TWRP - this Zip file comes with a Odin that works.
Cwm philz are not working.
But keep in mind as soon you installed twrp your knox counter is tripped.
For rom flashing you have to wipe your tablet and then follow these instructions xxxx://www.droidgator.com/update-galaxy-note-101-sm-p605-android-43-xxubmj9-firmware/.
Before starting backup your tab then everything should be fine.

Thanks for your effort in helping me out...
Before I sent my tablet for servicing... I restored the tablet with Kies to the original factory setting and rom as I HAD rooted my P605 and flashed a custom rom before. [Although the Know count is 0*1 anyway.... but the service centre was kind enough to fix my tablet as it's a hardware failure instead of anything to do with the ROM ]
When I got my tablet back and tried to flash the TWRP into it, this problem surfaced. And I read from another post that some say flashing a Samsung original rom could help I tried but to no avail. Still I am waiting and looking for a solution.
I tried Odin 3.04 3.07 and 1.85 with the two versions of TWRP but still none of them work.

Cant flash Stock firmmware
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3

aelaan said:
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?
Click to expand...
Click to collapse
Although it failed, I was able to recover using kies and use tablet as normal without data loss. It might be because at that point I had not rooted my tab and system state was still original in odin.
By the way I was on MJ4 xsa(AUSTRALIA) trying to install NC2 TGY(HONG KONG).
Now I have rooted it and have I installed NC2. I am still not sure what the issue was. But the only thing I did different was, first was using a virtual machine, but now did in an actual windows machine.
Can you please try this? If you can, install back NC2 using odin. Boot it once, then try recovering using kies. Kies recover mode gets your latest firmware based on your serial number. Not what firmware you are running.
Please post back the result. Interested to know the outcome.
Sent from my SM-P605 using XDA Premium 4 mobile app
---------- Post added at 08:38 AM ---------- Previous post was at 08:33 AM ----------
Khazaad said:
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3
Click to expand...
Click to collapse
I don't think it is. Although the specs are the same, read somewhere that the internal partition structure for carrier branded firmware are different to generic. Don't remember where I read that. But can't confirm that either.
Sent from my SM-P605 using XDA Premium 4 mobile app

I think my phone is bricked

Hey all I'm not sure what happened but I reflashed to stock KitKat and while I did that I installed all the newest updates to receive Lolipop and after I finished that I downloaded CF-AutoRoot. I rooted it and got stuck with a bootloop so I went into the stock recovery and erased everything. So I repeated step one by reflashing KitKat and now Odin is giving me an error and it isn't working.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I'm about to pull my hair out

gfp11289 said:
Hey all I'm not sure what happened but I reflashed to stock KitKat and while I did that I installed all the newest updates to receive Lolipop and after I finished that I downloaded CF-AutoRoot. I rooted it and got stuck with a bootloop so I went into the stock recovery and erased everything. So I repeated step one by reflashing KitKat and now Odin is giving me an error and it isn't working.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I'm about to pull my hair out
Click to expand...
Click to collapse
You have a dev edition or retail?

Retail I believe
Could I just go into TWRP, go to my computer, put on a ROM, transfer it to my phone, and then install something from there?
I don't really care about stock at this point

gfp11289 said:
Retail I believe
Could I just go into TWRP, go to my computer, put on a ROM, transfer it to my phone, and then install something from there?
I don't really care about stock at this point
Click to expand...
Click to collapse
If you're able to get in TWRP you do not have retail version. Do you have any ROMs or TWRP backups on an SD card? The CF-autoroot part is confusing me I don't remember ever having to use that.

jcip17 said:
If you're able to get in TWRP you do not have retail version. Do you have any ROMs or TWRP backups on an SD card? The CF-autoroot part is confusing me I don't remember ever having to use that.
Click to expand...
Click to collapse
Nope none. I tried downloading about 4 different stock roms and they all give me the same error in Odin.
I'm able to get into TWRP and Custom OS but that's it. The phone just keeps restarting after the Note 4 logo

gfp11289 said:
Nope none. I tried downloading about 4 different stock roms and they all give me the same error in Odin.
I'm able to get into TWRP and Custom OS but that's it. The phone just keeps restarting after the Note 4 logo
Click to expand...
Click to collapse
You can't flash stock roms (.zip files)in ODIN. They need to be .tar files
First check under your battery it should say developer device. If not you have a retail version. If you do have developer edition try to go through these steps and hopefully you will be okay. .
http://forum.xda-developers.com/note-4-verizon/development/how-to-custom-recovery-root-t2923340
If you have a retail version try this.
http://forum.xda-developers.com/not...nt/verizon-note-4-firmware-odin-file-t2926827
You said you accepted the lollipop update when you were on Kit Kat?

I need the Sprint firmware but it doesn't say anything about Developer or Retail under the battery
Model: SM-N910P

gfp11289 said:
I need the Sprint firmware but it doesn't say anything about Developer or Retail under the battery
Model: SM-N910P
Click to expand...
Click to collapse
Woh don't do anything I said. You're in the wrong forum
Try to seek help here
http://forum.xda-developers.com/note-4-sprint​

Oh shoot I didn't even realize I was in the Verizon forum. Sorry

gfp11289 said:
Oh shoot I didn't even realize I was in the Verizon forum. Sorry
Click to expand...
Click to collapse
Hey on the bright side you're a senior member now :highfive:
Hope you get your phone working !

jcip17 said:
Hey on the bright side you're a senior member now :highfive:
Hope you get your phone working !
Click to expand...
Click to collapse
Me too
Do you have any ideas possibly? If I'm able to get into TWRP and I put a ROM on a micro sd card, couldn't I just install it from there?

gfp11289 said:
Me too
Do you have any ideas possibly? If I'm able to get into TWRP and I put a ROM on a micro sd card, couldn't I just install it from there?
Click to expand...
Click to collapse
Yes definitely just do an advance wipe and wipe data, system, cache, and dalvik cache before. But don't confuse TWRP with the stock recovery. TWRP is a custom recovery.

HELP! Galaxy S6 (SM-G920P) (SOLVED)

I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
UPDATE
Was able to flash stock 5.1.1. Even stock firmware, still rebooted every minute even in safe mode.
Ended up flashing stock 5.1.1 and run the same root and also flash twrp to the device. Nonetheless It still reboots every minute, even in safe mode. Below is the recovery.txt and also attached is a photo of where it's stuck because of rebooting. I swear it's something with the cellular...
recovery.txt
Where it stuck due to rebooting every minute
Update 2
The reboot does not occur in twrp or download mode
Update 3
Following Koops second method
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
Click to expand...
Click to collapse
After the stock flash, booting up hangs on the sprint loading screen, dims, then restarts (only first time star. then ting up after flash) goes through setup, but again reboots every minute. The bars at the top sometime show up and sometime don't show up.
Also every reboot, i turned on voice assistant and "system update" is said every time.
At this point im open to any suggestions. If it's not fixed today ill most likely have to go buy an s5 off of amazon.
UPDATE
Got the phone through setup. Baseband and software version is unknown and notification of "Checking device status" is constant. Even after flashing stock 5.1.1. After about a minute, the device status becomes official.
Might try this:
technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
UPDATE
forum.hovatek.com/thread-116.html
Tried using these methods to fix the baseband issue yet still havent fixed it.
UPDATE Finale
For some reason Koops stock firmware didn't work with my phone. I'e uploaded the firmware that did in case others run into the same issue.
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Thank you everyone who helped!
Pictures of device info added below for specific info
Also if it helps I had flashed twrp before anything. I forget specifically if I did anything in twrp that may have helped or not.
http://imgur.com/vUmjfbX
http://imgur.com/CXql8Li
http://imgur.com/2dUJ1om

x1xmadex1x said:
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
Click to expand...
Click to collapse
Flash back to stock via Odin and install twrp then flash THIS version of SuperSU. Unlike the normal version, this one will not install in the system thus lowering the risk of breaking your device(s)

Flash failed
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess

Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.

Still rebooting
I flashed the newest one, the one linked and yet it still reboots after about a minute...cant get past the "Optimizing app" part now...it reboots before it can finish.
It seems like it reboots when trying to get signal....my bars come up but no reception..then just reboots...

Helpful info?
If it helps, I used this to root it:
autoroot.chainfire.eu
samsung SM-G920P zerofltespr zerofltespr universal7420 exynos5 LMY47X.G920PVPU3BOJ7 5.1.1
Like i said i uninstalled super su, reinstalled, than ran that through odin again and it crashed.

x1xmadex1x said:
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Click to expand...
Click to collapse
What do you have ticked under options?

1619415 said:
What do you have ticked under options?
Click to expand...
Click to collapse
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked

x1xmadex1x said:
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
Click to expand...
Click to collapse
Try doing it this time without rooting

1619415 said:
Try doing it this time without rooting
Click to expand...
Click to collapse
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on

koop1955 said:
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Click to expand...
Click to collapse
Correct tar and successful, but doesnt solve my problem...still rebooting a minute to being turned on even in safe mode

Updated main

Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...

1619415 said:
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
Click to expand...
Click to collapse
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago

I am having a very similar issue, can't seem to figure out how to fix it.

x1xmadex1x said:
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
Click to expand...
Click to collapse
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.

1619415 said:
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
Click to expand...
Click to collapse
My knox counter is tripped and the galaxy s6 doesnt have a removeable battery...it says it has a charge..i dont think the battery is the issue...

x1xmadex1x said:
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on
Click to expand...
Click to collapse
After it flashes, boot to STOCK recovery and perform a data wipe/factory reset. My guesses are you have stale leftovers from previous ROM/build and the system can't find what it is looking for and terminates.

Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.

koop1955 said:
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
Click to expand...
Click to collapse
Thank you, will try that in a little.
What about a "PIT" file?

Verizon Note 4 Will not flash in Odin

Alright i did a major mess up on my phone , Alright so i was rooted and was on CM13 well i decided to go back to stock rom so i downloaded the lastest Firmware and use odin to flash it and while it was flashing it failed . So i pulled the battery and restarted the phone and now i am hit with the ( Your device didn't update succesfully. Use the Verizon Software repair assistant to repair your deivce ) So i did that and it fails at 84% So i tryed reflashing again via odin and i keep getting failed well when i tryed flashing CF-Auto root to just see if it did anything it failed but when i booted the phone up it went stright to the samsung logo and boot looped so i was ok so i went into recovery and tryed to wipe /factory reset but keep getting a error .
So my thing is idk what to do i have tryed flashing via odin and it keeps failing i get this
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
and that is the lastest firmware from sam mobile
if anyone can help me i really appericate it

pfcland said:
Alright i did a major mess up on my phone , Alright so i was rooted and was on CM13 well i decided to go back to stock rom so i downloaded the lastest Firmware and use odin to flash it and while it was flashing it failed . So i pulled the battery and restarted the phone and now i am hit with the ( Your device didn't update succesfully. Use the Verizon Software repair assistant to repair your deivce ) So i did that and it fails at 84% So i tryed reflashing again via odin and i keep getting failed well when i tryed flashing CF-Auto root to just see if it did anything it failed but when i booted the phone up it went stright to the samsung logo and boot looped so i was ok so i went into recovery and tryed to wipe /factory reset but keep getting a error .
So my thing is idk what to do i have tryed flashing via odin and it keeps failing i get this
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
and that is the lastest firmware from sam mobile
if anyone can help me i really appericate it
Click to expand...
Click to collapse
I don't know if you tried already, but perhaps you could simultaneously flash a PIT file (hsbadr has a post over this) and a stock firmware image in ODIN. This should fix any borked partitions, if there are any. If this doesn't work, then I'm afraid I can't help you further. You'd have to wait on someone more knowledgeable than me. Or, you can take it into a verizon store or best-buy and ask for help there?

SirLaughsalot said:
I don't know if you tried already, but perhaps you could simultaneously flash a PIT file (hsbadr has a post over this) and a stock firmware image in ODIN. This should fix any borked partitions, if there are any. If this doesn't work, then I'm afraid I can't help you further. You'd have to wait on someone more knowledgeable than me. Or, you can take it into a verizon store or best-buy and ask for help there?
Click to expand...
Click to collapse
Were can i find this post at

ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?

pfcland said:
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
Click to expand...
Click to collapse
Is this on first boot go through set up and when your on the home screen power off the phone then power it on and if you were on cm 13 and flashed it with TWRP you tripped Knox so if powering off doesn't work then you can't get rid of it without rooting

Bren123 said:
Is this on first boot go through set up and when your on the home screen power off the phone then power it on and if you were on cm 13 and flashed it with TWRP you tripped Knox so if powering off doesn't work then you can't get rid of it without rooting
Click to expand...
Click to collapse
Yea it shows it on first boot shows a lock that is unlocked

pfcland said:
Yea it shows it on first boot shows a lock that is unlocked
Click to expand...
Click to collapse
OK complete setup when it gets off verizon screen then power it off and power it back on
Sent from my SM-N910V using Tapatalk

Bren123 said:
OK complete setup when it gets off verizon screen then power it off and power it back on
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Ok it is gone thanks alot man

Download this app called Samsung phone info from Google play and look at Knox warranty void if it shows up with 0x1 your warranty is voided I'm not sure if there is a way to reset it back to 0x0.

Bren123 said:
Download this app called Samsung phone info from Google play and look at Knox warranty void if it shows up with 0x1 your warranty is voided I'm not sure if there is a way to reset it back to 0x0.
Click to expand...
Click to collapse
it shows Ox1 but i am not worried about it because my phone is paid off

pfcland said:
it shows Ox1 but i am not worried about it because my phone is paid off
Click to expand...
Click to collapse
Oh OK cool.
Sent from my SM-N910V using Tapatalk
---------- Post added at 04:38 AM ---------- Previous post was at 04:37 AM ----------
pfcland said:
Ok it is gone thanks alot man
Click to expand...
Click to collapse
Your Welcome. [emoji3]
Sent from my SM-N910V using Tapatalk

pfcland said:
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
Click to expand...
Click to collapse
I'm at the exact point as he was but I haven't been able to try verizon software update assistant yet. However, I'm not able to install the PIT and TAR he used. Here's what I get. Any ideas? Under options I have the first three checked (auto reboot, re partition, f reset time).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT 1: Unchecked auto reboot and switched COM PORTS and it worked! THANK YOU!!!

droiddude414 said:
I'm at the exact point as he was but I haven't been able to try verizon software update assistant yet. However, I'm not able to install the PIT and TAR he used. Here's what I get. Any ideas? Under options I have the first three checked (auto reboot, re partition, f reset time).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT 1: Unchecked auto reboot and switched COM PORTS and it worked! THANK YOU!!!
Click to expand...
Click to collapse
Do this
Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
1. Extract odin into a desktop folder
2. Extract the tar from the zip and place it in the odin folder .
3. Place the PIT file inside the odin folder
4. Open odin folder
5. Run odin
6. In the left you should see some menues click on the one that says PIT
7. Now browse for thr PIT file and select it
8. Now Click on the AP button and select the TAR file in the odin folder .
9. Wait for it to load
10. Now make sure the re partition is not check marked .
11. Now click start and it should flash succesfully.
It will reboot and show the lock screen but one you reboot again it should be gone
Hope this helps

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
Bren123 (or anyone who can help), I am having a same type of problem flashing in Odin. I would like to put my phone back to kitkat, back when it was smooth and fast. When I have tried to flash with Odin it failed everytime, however it was an older version of Odin v3.10.7. I have a stock kitkat rom from Sam mobile. Can I load it with the newer Odin and the Pit file you shared links for? Any help would be appreciated!

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
lugnuttz said:
Bren123 (or anyone who can help), I am having a same type of problem flashing in Odin. I would like to put my phone back to kitkat, back when it was smooth and fast. When I have tried to flash with Odin it failed everytime, however it was an older version of Odin v3.10.7. I have a stock kitkat rom from Sam mobile. Can I load it with the newer Odin and the Pit file you shared links for? Any help would be appreciated!
Click to expand...
Click to collapse
I tried again with the never version of odin and it still does not work for me. This is what I get:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help me get my phone back to kitkat???
I can only flash marshmallow, or now lollipop v5.11, after following the instructions above. I still can't get the kitkat firmware to work.
Please help!

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
thank you, this helped me out when my odin got stuck for 30+ minutes.

I use to have a Note 4 Verizon good cell, but I then change it to a T-Mobile N910T unlock easer to flash them no boot-loaders are blocked, but thats just my saying.

I went through the process ... i have root and i can only install a 5.1.1 rom for the life of me i am unable to flash any 6 or 7 roms ... ideas?

Get write failure
I know this has been a couple years but I am in the same boat . I went through the steps and I get a flash write failure?
It happens after about 40 seconds into
system.img.ext4
ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> FAIL! (Write)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)