Develop Bugs

Help unbrick note 3

I am not new to the rooting scene, however I have a problem that I can't seem to figure out. I've been reading now for the past 2 days, tried several things and still can't get this resolved. I've never had any issues in the past with odin and rooting samsung phones before, including ones with locked bootloaders. However, I've met my match. I tried following the tutorial listed on this site for rooting the samsung note 3 from tmobile. I watched the video and followed along with the files listed here
http://forum.xda-developers.com/note-3-tmobile/#root
My problem is as follows: I tried rooting with odin, installed kies for the usb support but halfway through the root process I get the big RED FAILED! phone's progress bar stops and it hangs. I though this was strange and never encountered this before. I then tried repeating the same process and same results, however this time around I am only able to bring the phone into "odin" mode "download" and not the original stock rom.
At first I was getting the original "the firmware encountered an upgrade issue" and couldn't bypass this unless I opted for download mode. I've tried the same steps to "unbrick" via oden with stock tmobile firmware for this phone and yet it yields the same results, big exclamation failed on odin. I then tried the process with the .pit file to partition that I found online somewhere and that fails too. My note starts up now, but stuck at the samsung galaxy note 3 screen. I've tried several versions of odin, switching usb cables, usb ports and I am unable to root this phone or even get it unbricked! i've read extensively here and can't seem to find a solution to my problem. Can someone PLEASE point me in the right directions?? BTW, I am using a mac with VMWARE, i've never encountered any issues with vmware in the past while running windows 8.
Phone says the following:
Once in download mode my phone says the following:
ODIN MODE
PRODUCT NAME: SW-N900T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOM SECUREBOOT: ENAMBLE
RP SWREV: S2, T2, A2, A3 P2
WRITE PROTECTION: ENABLE
UOC START
and I get these results from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Try a new computer...
Sent from my SM-N900T using Tapatalk

dobbs3x said:
Try a new computer...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
You think a new computer might solve this?

Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1

xmatic said:
You think a new computer might solve this?
Click to expand...
Click to collapse
Actually, he might be right. But you may need to just try a different USB port instead of a new computer.
I had a problem with Odin failing when I tried to install a ROM. I remembered something about there being problems with certain USB ports, so I switched it to a port on the front of my PC and it worked. This was despite the fact that Odin recognized the device in the first port.
Hope that helps.
TL;DR: Just read through your post again and saw that you already tried that. Sorry.

dragonstalker said:
Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1
Click to expand...
Click to collapse
I use Odin all the time for rooting Samsung phones. Never used Heimdall, but love the idea of using it in my Mac.
Does this works with Note 3?

dragonstalker said:
Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1
Click to expand...
Click to collapse
Thanks for all the help, I was able to install the original rom back and restore the phone to it's original state through my mac side. I have downloaded Heimdall, but what are the steps necessary to root my phone? I only see an option to load package, flash or create package but it seems it's requiring a "PIT" file. Can anyone point me in the right direction of which particular file I need to root this note 3 with Heimdall? Thanks!

xmatic said:
Thanks for all the help, I was able to install the original rom back and restore the phone to it's original state through my mac side. I have downloaded Heimdall, but what are the steps necessary to root my phone? I only see an option to load package, flash or create package but it seems it's requiring a "PIT" file. Can anyone point me in the right direction of which particular file I need to root this note 3 with Heimdall? Thanks!
Click to expand...
Click to collapse
CF_Autoroot does not work with Heimdall? I have yet to use it eventhough i have a Ubuntu Box. So i'm curious to know also.

dragonstalker said:
CF_Autoroot does not work with Heimdall? I have yet to use it eventhough i have a Ubuntu Box. So i'm curious to know also.
Click to expand...
Click to collapse
The auto root is not working for me period! it bricked my phone 3 times already and I had to unbrick. It was a pain in the butt. All ulitmately due to odin failing with the flashes. I've tried different versions of Odin, different versions of windows within vmware and different usb slots/cables. All fail! Is there another way to root this phone guys! Please help? I am on a mac. Obviously Odin is now out of the question.

xmatic said:
The auto root is not working for me period! it bricked my phone 3 times already and I had to unbrick. It was a pain in the butt. All ulitmately due to odin failing with the flashes. I've tried different versions of Odin, different versions of windows within vmware and different usb slots/cables. All fail! Is there another way to root this phone guys! Please help? I am on a mac. Obviously Odin is now out of the question.
Click to expand...
Click to collapse
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip

dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
That is what I used but get on a PC. Go over a friends house and borrow his.
TWEAKED N3

dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
My apologies, I didn't think I was yelling, and I didn't mean to be ass. I am just a little frustrated because i've never had any issues before in the past rooting a phone, especially a samsung phone via Odin. I'll try this as I was using the n900t auto root. I'll advise how it goes.

xmatic said:
My apologies, I didn't think I was yelling, and I didn't mean to be ass. I am just a little frustrated because i've never had any issues before in the past rooting a phone, especially a samsung phone via Odin. I'll try this as I was using the n900t auto root. I'll advise how it goes.
Click to expand...
Click to collapse
OH no. i was saying don't yell at me for asking the question.
If you still have issues pm me. i'll give you my number and we'll walk thru it.

BACARDILIMON said:
That is what I used but get on a PC. Go over a friends house and borrow his.
TWEAKED N3
Click to expand...
Click to collapse
I failed again, can't get it to work. I wouldn't be surprised if it's a vmware thing. I just can't find anyone with a pc around.

xmatic said:
I failed again, can't get it to work. I wouldn't be surprised if it's a vmware thing. I just can't find anyone with a pc around.
Click to expand...
Click to collapse
Sorry bro I just don't know enuff about Mac products to point you in the right direction.
TWEAKED N3
---------- Post added at 11:05 AM ---------- Previous post was at 10:48 AM ----------
dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
https://plus.google.com/app/basic/stream/z12yzpirzqf4srxw204cjl1aoor5ezninhc
He just updated the apps like 50 min ago
TWEAKED N3

xmatic said:
You think a new computer might solve this?
Click to expand...
Click to collapse
This is the same exact problem I'm having. Also not new to rooting.
Guess what. I'm also trying on a mac with VMWARE. Makes me wonder. But I've rooted so many times this way. What makes this android any different. Tomorrow I'll try making a boot able window HD.
Sent from my SM-N900T using xda app-developers app

starscrean said:
This is the same exact problem I'm having. Also not new to rooting.
Guess what. I'm also trying on a mac with VMWARE. Makes me wonder. But I've rooted so many times this way. What makes this android any different. Tomorrow I'll try making a boot able window HD.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yeah, i've given up with rooting via VMWARE and Odin, it just doesn't work, period. I've tried to virtual machines, a win 8 and win 7 all with the same results. I have a feeling it's VMware, I am trying parallels now and I'll post updates afterwards. Thanks to everyone for contributing. BTW, does anyone know if it's even possible to root with Heimdall?

Update:
I was able to root fine without any issues, it seems the issue was ONLY because I used VMWARE! To all you mac users out there, I tried Parallels 9 and voila it worked!

xmatic said:
Update:
I was able to root fine without any issues, it seems the issue was ONLY because I used VMWARE! To all you mac users out there, I tried Parallels 9 and voila it worked!
Click to expand...
Click to collapse
This is good to hear. I'll give a try and update later. Thanks
Sent from my SM-N900T using xda app-developers app
---------- Post added at 05:21 AM ---------- Previous post was at 05:07 AM ----------
In the future another easy way to unbrick your Samsung just open Kies in tools drop down select the emergency firmware. A pop up will ask you to put in your phone model and S/N. Kies restores firmware via download mode. This is how I restored from 5 bricks.
Sent from my SM-N900T using xda app-developers app

xmatic said:
Yeah, i've given up with rooting via VMWARE and Odin, it just doesn't work, period. I've tried to virtual machines, a win 8 and win 7 all with the same results. I have a feeling it's VMware, I am trying parallels now and I'll post updates afterwards. Thanks to everyone for contributing. BTW, does anyone know if it's even possible to root with Heimdall?
Click to expand...
Click to collapse
MUCH THANKS !!! To you my friend. I must've bricked my phone 5x trying to gain root using vmware.
So I downloaded the parellel 9. And BOOMMMM. I was so glad to see a big green pass in Odin lol.
Sent from my SM-N900T using xda app-developers app

[Q] I747M Can't get 3G/LTE data after IMEI loss / restore

Hello to the experts on xda-developers.
I f***ed up! It was me, no need to point that out, yes, i should have backed up my radio settings, EFS and such, yes i should have been more careful, and no, i don't know why i am such an idiot.
Now, with that out of the way...
I have a Samsung Galaxy S3 (SGH-I747M) on Rogers that until recently, worked great. I was running Android KitKat 4.4.2 (CyanogenMod 11 nightlies) and happily so, upgrading to new versions of the ROM every few days or so. All was good in the world.
Then, tragedy..... I upgraded the CM a few weeks ago, and from that day forward, i noticed that i could not sustain a higher connection speed than EDGE save short bouts of LTE after reboot or flight mode disable. This would eventually (<5m) fail and i would be back on EDGE.
I found through troubleshooting, that the IMEI on the phone was all zeros, I could still make and receive calls, but data was capped at edge, except right after reboot, or flight mode, where LTE is available for up to 5 minutes before again dying back to EDGE Using instructions on another thread (can't remember which one) I restored the IMEI to the value on the sticker and did a factory reset. .... Still on Edge.
Next, using kies 3 I upgraded the firmware to the latest and greatest : (ro.bootloader = I747MVLUFNK2) followed by another Factory Reset. ..... Still on Edge.
And then most recently, i have been scrolling through, and performing instructions from tonnes of forum posts that suggest all sorts of combinations of : *#197328640# or *#2263# or others and fiddling with back-end settings, however I am still as yet unsuccessful.
Any assistance or pointers in the right direction would be appreciated.
thanks ,
./Darren

Thought to check my APN settings. Using the 6th post (from DaveM) on communityforums. rogers. com/ t5/ forums/ forumtopicpage/ board-id/ Other_mobile_device/ thread-id/ 3904 As a reference, it suggests the APN should be:
(remove spaces from above url to get full link.... i have too few posts to post links)
LTE Smartphone
APN: ltemobile.apn
Username: not required
Password: not required
APN Protocol/Type: IPv4/IPv6 (use IPv4 if IPv4/IPv6 option is not available or if no "APN roaming protocol" option)
APN Roaming Protocol: IPv4
LTE Tethering
APN: ltedata.apn
Username: not required
Password: not required
APN Protocol/Type: IPv4
APN Roaming Protocol: IPv4​
My APNs were the exact same as above, but with an APN protocol type of IPv4, greyed out with no option to change it.

Another suggestion was to check my USBSettings (*#0808#) and check what they were set to.
Upon arrival, I found it to be set to MTP, multiple threads suggest that it should be MTP + ADB. So i made that change and rebooted and it has had not effect.
./D

You used Kies while on CM11 to update the firmware?
Did you try flashing the stock ROM from sammobile.com using Odin? This should return the phone to completely stock.
If the imei has not been restored after flashing stock, try using nvwriter to inject the imei.

audit13 said:
You used Kies while on CM11 to update the firmware?
Did you try flashing the stock ROM from sammobile.com using Odin? This should return the phone to completely stock.
If the imei has not been restored after flashing stock, try using nvwriter to inject the imei.
Click to expand...
Click to collapse
Hello Audit 13, thank you for your reply... I believe I have done this already but for the sake of completeness, i did it again.
Steps to complete:
1) Downloaded ROM - I747MVLUFNF2_I747MOYAFNF2_RWC. zip from sammobile->firmwares
2) Fully charged phone and opened Odin 3.07
3) Plugged in phone, (Added in the status bar)
4) Clicked PDA button and browsed to the tar md5 file
5) Clicked start. ​Phone reset at the end and booted into a fresh stocky way.
The connection though? ---> EDGE
The IMEI is fine (i think), it reads the same number on the sticker under the battery, in Settings->About phone and also when *#06# is invoked.
Any other thoughts on steps to troubleshoot?
./d
Output from Odin below
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUFNF2_I747MOYAFNF2_I747MVLUFNF2_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
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> NON-HLOS.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)

Looks like you did everything I would have done, that's for sure.
Did you try non-LTE APN settings?

Well, i hadn't, but i have now.... no dice.
(and there is nothing worse than the dashing of hopes, when you first start up after trying a new thing and it goes straight to LTE and is lightning fast....for about 90 seconds...then crash....sputter..spurt........Edge.)
./D

Maybe ask the OP from this thread: http://forum.xda-developers.com/galaxy-s3-att/help/galaxy-s3-i747-stuck-edge-t3013978

So I read his instructions....
downloaded nv reader/writer
downloaded it from here
http://forum.xda-developers.com/show....php?t=2374063
then i made a backup of my imei just incase it didnt wrk...dont know how? watch this
http://www.youtube.com/watch?v=CQkUo...e_gdata_player
came across this in a forum and injected this nv item into my s3
http://forum.xda-developers.com/atta...9&d=1380728466
and then turned on mobile data and put my phone in and out of air plane mode and 4g poped up
im guessing that imei backup only works for i747.
this worked for me. my imei wasnt missing but this fixed it.​
Problem is that i have an i747m and not an i747... so if i understand what is suggested is to.....
backup my IMEI from nvbackup
source a full nv backup from another i747m .... which I don't have readily available....
restore it to my phone....thus making my phone an illegal clone of the source
remove the IMEI on the backup and replace with the IMEI that I backed up in the first step.​
Am i reading that correct? have i mistaken any of the steps?
ugh!
.d
...Still searching. Thanks for the help tho

You could also try using nvwriter to just re-inject the imei.

audit13 said:
You could also try using nvwriter to just re-inject the imei.
Click to expand...
Click to collapse
I tried that as well. The IMEI was set to a string of zeros (000000000000000) after a CM upgrade. I used nvwriter to inject the IMEI from under the battery.
I have also done a full export/import of the entire nv path, followed by a factory reset. Annnnd still no good.
.D

I assume you flashed the Rogers version of the firmware from sammobile. Maybe try firmware from Telus or Bell? I doubt it will make a difference.

my project for tonight.
wheeee!!!
.d

bodybuzz said:
my project for tonight.
wheeee!!!
.d
Click to expand...
Click to collapse
Did you fix it?

fausto412 said:
Did you fix it?
Click to expand...
Click to collapse
Hi Fausto412,
Alas...no.
I worked for about 2 weeks trying to get the POS to work. Tried endless restores, of Bell, Rogers, Telus, and even US carrier stock ROMS. I followed recommendations from threads on XDA and on gsmhosting.com and on SamMobile.com. I even offered to pay a local cell unlocking "guru" if he could finagle it (he couldn't). I never got full data capabilities back..
In the end gave up when my wife's contract renewal came up and her Note 3 was available after she procured a GS5.
Sorry i couldn't be more helpful.
bodybuzz (Darren)

bodybuzz said:
Hi Fausto412,
Alas...no.
I worked for about 2 weeks trying to get the POS to work. Tried endless restores, of Bell, Rogers, Telus, and even US carrier stock ROMS. I followed recommendations from threads on XDA and on gsmhosting.com and on SamMobile.com. I even offered to pay a local cell unlocking "guru" if he could finagle it (he couldn't). I never got full data capabilities back..
In the end gave up when my wife's contract renewal came up and her Note 3 was available after she procured a GS5.
Sorry i couldn't be more helpful.
bodybuzz (Darren)
Click to expand...
Click to collapse
Yeah, I'm starting to think this isn't fixable lol...how do you like that Note 3? I'm thinking of buying a refurbished model.

fausto412 said:
Yeah, I'm starting to think this isn't fixable lol...how do you like that Note 3? I'm thinking of buying a refurbished model.
Click to expand...
Click to collapse
Note 3 is a solid phone, big screen is great, battery life is **** (just like the GS3) but with a spare battery or two you are good to go.
I have been (understandably) gun shy about putting a custom ROM on this phone, both because of my previous blunders and because i have heard that custom ROMs do not perform very well with the s-pen, which i think is a killer feature of the Note series of phones. So stocky-stock-stock, for me (for now at least).
Good luck to you sir!!
./bodybuzz (Darren)

Error when trying to rollback from CM 12.1 to Stock on N910P

Hi!
First of all, thanks for reading this...
Yesterday I installed Cyanogen cm-12.1-20160208-NIGHTLY-trltespr on my SM-N910P but I noticed that I lost my 4G connectivity (I only receive H, I'm in Mexico, using Nextel network). Because of that, I'm trying to rollback to my stock firmware (5.1.1) but when trying to do it using Odin (I've tried several FW and Odin versions) every time I receive the following error log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, I receive this error:
UDC START
SW REV CHECK FAIL: [aboot] Fused 4 > Binary 1
[1] eMMC write fail: ABOOT
Any suggestion? I'll really appreciate your help
Thanks for your time!
Regards.

The bootloader has increased security that prevents older bootloaders from being installed even if the reactivation lock is not enabled. You cannot go back that far in Odin.
You've most likely found that you can still go back to CM with a backup or flash ROM. You should backup the things you want to keep that are on internal memory because you need to wipe that to restore stock.
You'll need a newer stock tar to restore stock. Galaxy Tools by iDone or this application in Google Play will tell you what your bootloader is to restore the same stock tar or newer.https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo But you can most likely install the latest stock tar found in the general forum if you go into recovery and wipe everything but extSdCard, power down and use latest Odin with Odin defaults to install it.
You need to go into Settings/System update and update PRL and data profile once your restored to stock.
Sent from my SM-N920P using Tapatalk

samep said:
The bootloader has increased security ....
Click to expand...
Click to collapse
Bro, you're my hero!!!! :good: my n910p is now as original!!! but now, I really don't know how to update the PRL for my network in Mexico...
Searching on Google I found how to update for Sprint Phones (My phone is a sprint one, but unlocked, so I can use it here in Mexico...) but I don't know if that could do the job...
Thanks!!!

lordkorhat said:
Bro, you're my hero!!!! :good: my n910p is now as original!!! but now, I really don't know how to update the PRL for my network in Mexico...
Searching on Google I found how to update for Sprint Phones (My phone is a sprint one, but unlocked, so I can use it here in Mexico...) but I don't know if that could do the job...
Thanks!!!
Click to expand...
Click to collapse
Your carrier should be able to help with the network connection issues. Tech support maybe?
Sent from my SM-N920P using Tapatalk

samep said:
Your carrier should be able to help with the network connection issues. Tech support maybe?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thanks my friend for your follow up!
I contacted Tech support today and after "several revisions" they told me that it is maybe the telephone, because when we tried to go to Settings > Data Usage > Mobile Networks, the option "Network Operatos" is disabled....
I was thinking to do the same that I did to run away from Cyanogen... Use the Phone info app, see the bootloader version and look for a firmware of that version (actually I have the N910PVPS4COK1) and apply it again to my phone... to see if that helps... what do you think?
Thanks!!!

lordkorhat said:
Thanks my friend for your follow up!
I contacted Tech support today and after "several revisions" they told me that it is maybe the telephone, because when we tried to go to Settings > Data Usage > Mobile Networks, the option "Network Operatos" is disabled....
I was thinking to do the same that I did to run away from Cyanogen... Use the Phone info app, see the bootloader version and look for a firmware of that version (actually I have the N910PVPS4COK1) and apply it again to my phone... to see if that helps... what do you think?
Thanks!!!
Click to expand...
Click to collapse
They can't provision it? I'm not sure if you have to be rooted to access it on an unlocked phone?
If they won't provision it, root or the XAS stock tar version of OK1 may open up the settings at more networks if you don't see them there. Be aware that going backwards in Odin may be blocked and cause those problems with flash again.
But you're rooted anyway, right? Try adding these lines to bottom of build.prop, leaving one blank line with no spaces at end and reboot.
ril.sales_code=XAS
ro.csc.sales_code=XAS
Sent from my SM-N920P using Tapatalk

samep said:
They can't provision it? I'm not sure if you have to be rooted to access it on an unlocked phone?
If they won't provision it, root or the XAS stock tar version of OK1 may open up the settings at more networks if you don't see them there. Be aware that going backwards in Odin may be blocked and cause those problems with flash again.
But you're rooted anyway, right? Try adding these lines to bottom of build.prop, leaving one blank line with no spaces at end and reboot.
ril.sales_code=XAS
ro.csc.sales_code=XAS
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I've no root on in (already, LOL). Let me root it and then, apply the couple of lines that you told me...
I'll keep you posted.
Thanks buddy!

lordkorhat said:
I've no root on in (already, LOL). Let me root it and then, apply the couple of lines that you told me...
I'll keep you posted.
Thanks buddy!
Click to expand...
Click to collapse
It didn't work my friend... :crying: take a look to my captures...
Thanks!

What about the Access Point Names. Aren't there edit symbols on those?
I'm not the expert but I at least thought it possible to edit for carrier with MSL as well.
Maybe this helps?
https://www.whistleout.com/CellPhon...y-verizon-sprint-phone-on-a-different-network
Sent from my SM-N920P using Tapatalk

Yes, I can see and edit the APN options, in fact I add them manually to try to force the 4G connectivity, but I only reach 3G..
Let me resume that I did and how I mess all up ... I bought this Note 4 unlocked with Android 5.1.1 installed on it. When I received everything worked perfectly, even my 4G network. Then, I wanted to test Cyanogenmod, so I installed it into my device... (why I did that!!!???). I saw that I lost a lot of functions of my Note 4 and I wanted to rollback my device... As long as I noticed that I couldn't do that so easily, I posted in here looking for help... Then you helped me out saying me this: "You'll need a newer stock tar to restore stock. Galaxy Tools by iDone or this application in Google Play will tell you what your bootloader is to restore the same stock tar or newer.https://play.google.com/store/apps/d...uyen.phoneinfo But you can most likely install the latest stock tar found in the general forum if you go into recovery and wipe everything but extSdCard, power down and use latest Odin with Odin defaults to install it."
I did that and I found a ROM (from Sprint, ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5) that helped me to have my stock Android again, but since then, I lost 4G. Everything works perfectly but that. Then, I saw that on my phone appeared a system update, I ran it and now I gave the version N910PVPS4COK1
The last thing that I applied to my device was the root option, to try the option that you told me... that's my little soap opera... hehehe...
No matter the result of this, please thanks for your support on this path of darkness, XD

First thing first. That kernel your non. Is known to cause issues.
Sent from my 0x1 Note 4...... I love tep

N910p unlocked without 4G, only 3G
samep said:
What about the Access Point Names. Aren't there edit symbols on those?
I'm not the expert but I at least thought it possible to edit for carrier with MSL as well.
Maybe this helps?
https://www.whistleout.com/CellPhon...y-verizon-sprint-phone-on-a-different-network
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Hi!
After being investigating, I have recovered a "parcial backup" that I did of the boot files of my phone after I changed the ROM using TWRP.
The name of the backup file of the ROM that my phone had was is 2016-02-08--17-06-42_LMY47X.N910PVPU4COG5-LTE1-ASFAHAN.
The only files that I have from that backup are:
-boot.emmc.win
-boot.emmc.win.md5
-recovery.log
Just to remember, I'm from Mexico and I receive my note 4 n910p without Sprint logos and working perfectly on 4G LTE on Nextel. After I installed CM 12 I lost 4G. Actually I have Botcatrom and all works perfect except for 4g LTE. (I only receive 3g).
I have read that if a sprint phone gets unlocked, I'll be able to use only 3g, but as I mentioned before, I receive the phone working on 4G! so there must be something for it!
As we can see in the name of the ROM, it says LTE, so that's the one! (I think) but looking for that ROM on google, I cannot find it
Do you know something about that ROM? or maybe I can do something with the Boot files that I found? I was thinking to upload that Boot files into my actual Bobcatrom, but I'm not sure if it will help or I'll brick my device.
Any help will be appreciated.
Thanks!!!

lordkorhat said:
Hi!
After being investigating, I have recovered a "parcial backup" that I did of the boot files of my phone after I changed the ROM using TWRP.
The name of the backup file of the ROM that my phone had was is 2016-02-08--17-06-42_LMY47X.N910PVPU4COG5-LTE1-ASFAHAN.
The only files that I have from that backup are:
-boot.emmc.win
-boot.emmc.win.md5
-recovery.log
Just to remember, I'm from Mexico and I receive my note 4 n910p without Sprint logos and working perfectly on 4G LTE on Nextel. After I installed CM 12 I lost 4G. Actually I have Botcatrom and all works perfect except for 4g LTE. (I only receive 3g).
I have read that if a sprint phone gets unlocked, I'll be able to use only 3g, but as I mentioned before, I receive the phone working on 4G! so there must be something for it!
As we can see in the name of the ROM, it says LTE, so that's the one! (I think) but looking for that ROM on google, I cannot find it
Do you know something about that ROM? or maybe I can do something with the Boot files that I found? I was thinking to upload that Boot files into my actual Bobcatrom, but I'm not sure if it will help or I'll brick my device.
Any help will be appreciated.
Thanks!!!
Click to expand...
Click to collapse
Only thing I can think of is get in touch with your cellular provider or the point of sale of your phone. It seems you cannot run custom ROMs on your device and you don't have a full backup to restore. Ask if the XAS stock tar with APN edits is all you need. They should be able to help with provisioning service.
Updates would most likely come from OTA only once you restore the ROM with 4G would be my guess.
You should still be able to root and modify but that would have you in need of an updated stock tar to flash as your provider updates the ROM. IDK if it works but you may get by the tar updates using OTA update if you don't modify system.
Or make a stock backup of system partition before modifying it. Then you would restore that backup and full un-root. You would have to use the latest the updated Chainfire Auto root for Note 4. And you may have to root again and immediately go with full un-root in order to get the stock recovery with dm-verity cleared for OTA update. IMO, you'd be better off with a download for stock tar site before rooting but have the backup next time just in case. It might work for OTA updates but no guarantees.
I don't claim to be the expert but that's the best advice I can give with what I know ATM. Check around and see if there's a support site that includes your phone and provider; but you might find some guides our tutorials for editing APN. And when you get your ROM restored, try to copy your APN data to manually re-enter if you choose to risk another custom ROM or just need to provision it for service. Again, I'd suggest having a backup stock tar to flash before pursuing any risks.
Sent from my SM-N920P using Tapatalk

//SM-N920A\\ - ODIN 100% stock ATT recovery firmware N920AUCS4EQH1

N920AUCS4EQH1 - Link up
Enjoy !!!

Thank you so much!!!
I have been a luker for a little while now, but have made an account to try and contribute to this forum and say a big thank you to you. I recently purchased a new unlocked Note 5 from AT&T and thought it was impossible to update, but you've really gone above and beyond.
Just a few questions though:
1. Is this recovery firmware the same as the latest Nougat update? (In other words can I update my Note from 5.1 straight to this? Or is this some type of recovery firmware only, not to be used as an official update?)
2. I have a vague idea how to use Odin, could you just correct me if i'm wrong here. Its a matter of downloading these files, extracting them, run odin, put the files in the correct place and press start and done?
3. Will I be okay to update straight from 5.1 to 7.0 without any problems? (Does all the security updates come included?)
Thanks for your time and contributions!

E123xOMEGAx said:
I have been a luker for a little while now, but have made an account to try and contribute to this forum and say a big thank you to you. I recently purchased a new unlocked Note 5 from AT&T and thought it was impossible to update, but you've really gone above and beyond.
Just a few questions though:
1. Is this recovery firmware the same as the latest Nougat update? (In other words can I update my Note from 5.1 straight to this? Or is this some type of recovery firmware only, not to be used as an official update?)
2. I have a vague idea how to use Odin, could you just correct me if i'm wrong here. Its a matter of downloading these files, extracting them, run odin, put the files in the correct place and press start and done?
3. Will I be okay to update straight from 5.1 to 7.0 without any problems? (Does all the security updates come included?)
Thanks for your time and contributions!
Click to expand...
Click to collapse
1. Yes
2. Unzip files all the way to md5 format. Open ODIN and place in correct slots. Put your phone in download mode, connect to PC and click start.
3. Yes, there will be no problem.
Writing from the Edge of Galaxy S8+

Also add a little note that you need to use Odin 3.12.3 ...if you dont, you will get stuck on fota.zip something.

So I have updated to the lastest firmware using the link in this thread, and it works absolutely perfectly. I haven't tried all the features on the phone yet, so will update in due time. (For example battery life, performance, device heating up, etc...)

Avoid the cloud recovery mode
First of all thx norbarb for your support and help in this forum and of course is a superb firmware version but I would recommend to avoid the cloud recovery mode by Google Play Store it take a lot of time and is not practical.

need a little help
i get stuck at sboot.bin any ideas? heres the ODIN log
<ID:0/008> Odin engine v(ID:3.1207)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
Thanks in advance for any help

norbarb said:
download N920AUCS4EQH1 - Link up
Enjoy !!!
Click to expand...
Click to collapse
Can i update my Note 5 At&t unlocked N920AUCS4CPK1 with these files? and still unlocked after update

mohamedwaly said:
Can i update my Note 5 At&t unlocked N920AUCS4CPK1 with these files? and still unlocked after update
Click to expand...
Click to collapse
yes

Hello
I don't see the link

yishay said:
Hello
I don't see the link
Click to expand...
Click to collapse
What you mean you don't see link? Link is in OP ( 1-st post )

Thanks
---------- Post added at 08:21 PM ---------- Previous post was at 08:19 PM ----------
Will this installation wipe the phone (all apps) ?

Big Thanks
First of all I would like to thank norbarb for his contributions to the forum, and I have some questions please,
Is this Nougat update of the At&t Note5? and if yes can I flash it on my device (N920AUCU2BPE6)?
*Just for the record I live outside the US, and sorry for my stupid questions

OussamaTouahria said:
First of all I would like to thank norbarb for his contributions to the forum, and I have some questions please,
Is this Nougat update of the At&t Note5? and if yes can I flash it on my device (N920AUCU2BPE6)?
*Just for the record I live outside the US, and sorry for my stupid questions
Click to expand...
Click to collapse
Yes and you can flash it.
On Edge of Note

Thanks a lot bro.!

download link is broken.. hello master pls fix this... tq
and can u tell me.. can i flash this firmw with my note 5 bootloop>??

Looks like a lot of your GDrive links are 404-ing, particularly this one. I've got a N920A outside the US stuck on 6.0 and would really like to update it! Any chance you can rehost the files?

I can't Download. Showing "Not Found Error 404"

Can I not flash the CSC, is it okay?

Link is down!

Can't flash new Verizon variant S20 5G UW model with stock firmware.

For some reason none of the stock firmware files I am trying are working to flash my phone to the unlocked stock version. I have tried the latest Odin, have the drivers installed, and have tried the patched versions of Odin as well. Each time I get the obvious SHA256 error on stock, but when I try the patched versions I get a "re-partition operation failed" error and it just fails after the "set PIT file" command. Am I wrong to assume this is just another S20 model? I am making sure to use the SM-G981u1 firmware that I have tried from two different sites. The third one I can try, being from sammobile won't be done for another 6 hours because I don't want to pay $7.50 a month for a file that I have to download once.
Is there something I am doing wrong? I am using a USB 3.0 port directly on the back of my motherboard, the original cable with an adapter that came with a WD hard drive, and all the latest drivers are installed. If anyone has any tips or was successful in flashing please let me know what you did and how you got it working.
The error I get through USB 2.0 with the adapter is
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8662 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Try using a normal 2.0 USB port. This could be the reason. Saw this issue before.

From0toHero said:
Try using a normal 2.0 USB port. This could be the reason. Saw this issue before.
Click to expand...
Click to collapse
Tried and no luck. I think the only thing to try is the firmware file from sammobile and see if that gives me any issues. I am also going to try and see if updating the phone helps at all before flashing, so that's going now. If it does work I will update the original post.

cadcamaro said:
Tried and no luck. I think the only thing to try is the firmware file from sammobile and see if that gives me any issues. I am also going to try and see if updating the phone helps at all before flashing, so that's going now. If it does work I will update the original post.
Click to expand...
Click to collapse
are u putting the pit file in pit tab? also try using patched odin.. if still fails try extracting firmware then putfing back into tar without the pit file.. u get the idea..
does it give any error on phone when u get that error in odin?

I'll give that a try tonight. I've been meaning to do a factory reset since my Bluetooth is iffy.

elliwigy said:
are u putting the pit file in pit tab? also try using patched odin.. if still fails try extracting firmware then putfing back into tar without the pit file.. u get the idea..
does it give any error on phone when u get that error in odin?
Click to expand...
Click to collapse
Stupid question, but are all csc files password protected? I have three that I tried all need a password to extract the contents.
Tried with the newest version, extracted the .pit file with 7zip and
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8662 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!
Same with G981U1UES1ATE4 version, error on the phone shows "SECURE CHECK FAIL : PIT"

Why are you trying to repartition and use a pit file?
Leave odin settings as default and load the 4 parts of the firmware into their relevant odin sections and hit start

*Detection* said:
Why are you trying to repartition and use a pit file?
Leave odin settings as default and load the 4 parts of the firmware into their relevant odin sections and hit start
Click to expand...
Click to collapse
Because that doesn't work. It flat out seems that the verizon model of the S20 is different.

cadcamaro said:
Because that doesn't work. It flat out seems that the verizon model of the S20 is different.
Click to expand...
Click to collapse
secure check fail means ur using the wrong firmware or the firmware was somehow modified..
whats your exact model and exactly what firmware are you trying to flash and where did you get it?
and no, stock firmware is not password protected.. only time ive seen password protected files is if u dl from some website that zips it and puts a password on it

elliwigy said:
secure check fail means ur using the wrong firmware or the firmware was somehow modified..
whats your exact model and exactly what firmware are you trying to flash and where did you get it?
and no, stock firmware is not password protected.. only time ive seen password protected files is if u dl from some website that zips it and puts a password on it
Click to expand...
Click to collapse
You're right, it's an SM-G981V which I thought was just a crappy way for verizon to rename their model considering they sell flashable s20+/ultra variants. It's just a totally new model though so it's not working. Also as far as the password protection, it was only on winrar and the files extracted fine in 7zip.
The fw files I've tried came from sammobile, and the download tool directly from the xda app. Multiple versions and no success.

cadcamaro said:
You're right, it's an SM-G981V which I thought was just a crappy way for verizon to rename their model considering they sell flashable s20+/ultra variants. It's just a totally new model though so it's not working. Also as far as the password protection, it was only on winrar and the files extracted fine in 7zip.
The fw files I've tried came from sammobile, and the download tool directly from the xda app. Multiple versions and no success.
Click to expand...
Click to collapse
considering u have a g981V then u are flashing wrong firmware.. u need to flash G981V firmware

elliwigy said:
considering u have a g981V then u are flashing wrong firmware.. u need to flash G981V firmware
Click to expand...
Click to collapse
The problem is I don't want the 981v firmware which is why I was trying to flash it to the carrier unlocked firmware. Either way I'm stuck with it so there's the answer for everyone else.

cadcamaro said:
The problem is I don't want the 981v firmware which is why I was trying to flash it to the carrier unlocked firmware. Either way I'm stuck with it so there's the answer for everyone else.
Click to expand...
Click to collapse
Everyone else already knew you have to flash the correct firmware for your device model....

Use frija (you can download it here on xda), punch in model SM-G981V / VZW and it should pull the firmware direct from Samsung.
If you don't want the vzw firmware, punch in XAA for the CSC. You'll need to flash it with patched Odin for it to work.

Da_G said:
Use frija (you can download it here on xda), punch in model SM-G981V / VZW and it should pull the firmware direct from Samsung.
If you don't want the vzw firmware, punch in XAA for the CSC. You'll need to flash it with patched Odin for it to work.
Click to expand...
Click to collapse
he wanted the U1 firmware lol.. the carrier specific models dont have multi csc.. he probably only has vzw csc and maybe gcf csc
he also can only flash g981v firmware since its a carrier specific model signed with different keys than U U1 W models hence his secure check fail error

Yeah, the VZW variant has physical hardware differences also, so getting a U1 firmware to flash would probably go badly as far as booting.
Looks like there are only two regions available, on SM-G981V, VZW and CCT (Comcast)
elliwigy said:
he wanted the U1 firmware lol.. the carrier specific models dont have multi csc.. he probably only has vzw csc and maybe gcf csc
he also can only flash g981v firmware since its a carrier specific model signed with different keys than U U1 W models hence his secure check fail error
Click to expand...
Click to collapse

*Detection* said:
Everyone else already knew you have to flash the correct firmware for your device model....
Click to expand...
Click to collapse
That's weird, because I routinely Flash U1 on to U, U onto XU, CZ onto literally anything I can so I can get past FRP locks... On older phones I used to flash carrier specific combination files onto the wrong devices so I had OEM unlocking in the developer options of AT&T devices. Maybe you just didn't know that it was actually a hardware limitation rather than a software limitation. I didn't. I that's why I'm here. And I know for a fact that it's possible to flash the wrong model/variant firmware onto a device, even if you don't. But hey that's XDA for you. Ask a question that requires a modicum of thought, and get a snarky answer from a "senior member" that doesn't know what they're talking about.
Anyway, to the OP, I'm also trying to flash the Xfinity splash screen off some unlocked G981V devices. It may be a lost cause because it's a hardware compatibility issue but I know a few people that might want to take a crack at it with me and I'll let you know how it goes. It was a good question. It just sucks that you always seem to get one headass in the replies.

Hi Cadcamero
In also trying to restore my S20 back to original flash.
I bought it rooted, but certain apps that I need do not work on rooted phones.
Could you by any chance share a link to the stop by step process that you follow. I've never done this before and a little overwhelmed....
I've downloaded odin ah the firmware off sammobile. Just need to now know what to do with them :silly:
Thanks a million
Lee

cadcamaro said:
The problem is I don't want the 981v firmware which is why I was trying to flash it to the carrier unlocked firmware. Either way I'm stuck with it so there's the answer for everyone else.
Click to expand...
Click to collapse
Did you ever find a solution? I am having the EXACT same problem on a Verizon S20 FE. I want to load the unlocked American XAA firmware onto it. I am getting the same error. I wonder what Verizon has come up with to stop this? I have ALWAYS done this with my Verizon phones until now.