Develop Bugs

NTT Docomo Galaxy Note II SC-02E Root Japan

Status on Ntt Docomo Note SC-02E
Q&A
Q:How can I unlock the SC-02E?
A:Through Docomo around 3500 yen or The free unlock works!!!! (Tested by octa_amide ) Thanks Look below in Useful links
Q:Where can I find original SC-02E firmware if I need to return the handset for service?
A:In my signature Xda share drive :Stock Docomo 4.1.1 JB
Q: What is the current version firmware?
A:SC-02E Japan- 2013 November- 4.1.1- SC02EOMAMK1- SC02EDCMAMK1 Root still works!!
Q:Will I lose NFC TYPE payment example edy, Felicia,suica?
A:Yes and No: Yes you will lose if you stay on a custom recovery like CWM.No if you place your stock recovery back to the original.
Q: Does 1 seg digital mobile TV work?
A:Yes on stock docomo or Rob's Detoxed Rom(links coming soon)
Q:Is there a ROOT ?
A:Yes ROOTED
Root Kit Files
Q:Can i install CWMR or TWRP ?
A: Yes if you flash using odin or download TWPR from the website TWRP will work I tested it
Q:Will the CF Yellow triangle reset work?
A: Yes! Use just for Resetting binary count only !! Reset binary count Kit
Q: Can you do a wireless charge mod on this phone ?
A: "No" there is no easy way I could think of Look at these pictures I took when I took apart my device.
Q:Can I silent the Camera Shutter sounds?
A:Yes look here warning this may be illegal in some countries
Q Will the multi hack mod work?
A:Yes Tested by Robobob1221 Link here
Robobob1221 :Useful Link
Credit to g.lewarne for the ramdisk scripts/setup from his note2core kernel Robobob1221 for the zimage swap and Vipsavior walking on the darkside 55+counts trial and error HaHa .
Mskips Note 2 Tool kit,ChainFire's Triangle app & SuperSU.99, and the people that been with us from the start.

How to root the sc02E Docomo
IN 720P !!!!! also
Its not a Hollywood video but it should work

Thanks for the progress report.
I've just got it yesterday as well, and can't wait for a way to root it properly!
I will probably do some tests in the next days as well.
vipsavior said:
Well I dove in and installed CWMR and backed my stock rom by using this method below.
This method is for OSX mac, but there is a odin version also
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-on-mac-osx/
So i achieved CWMR and backed up my rom than I tried the root but its a no go. SU is installed but i receive a message "There is no SU binary installed and SuperSu cannot install it"
Now i don't know if this same method is needed below for the note 2 as it was needed for the Docomo S3 version
http://forum.xda-developers.com/showthread.php?t=1895737
If you read on the bottom of the post It states that the orginal recovery needs to be installed in order to use
beware this will raise your binary count
CWM recovery installed instead of the stock_recovery, then many of the SC-06D's functions will not work. The stock_recovery MUST be flashed/installed everytime before booting into Android
Click to expand...
Click to collapse

Still no luck,but getting there
Well I been looking all day for a root or progress of a root in japanese forums ,but i still had no luck .I restored my phone back to the stock binary and now i am able to receive updates via OTA and use NFC payments.While i was doing that i went and did a little digging and looked at busy box on my phone and it said it was rooted .I also looked up the message in SU "There is no SU binary installed " From looking at a few threads it seems that a little fix or patch is needed so hopefully it will not be long before we get a root.I also sent Chainfire a post for a CF-Auto root support.I know the man is busy ,but hopefully he will come through we just need to be patient. If you would like the stock JB 4.1.1 (1.57 GB)File its is being upload now in my shared xda drive below .I extracted the modem and recovery also .We might need this later for rom flashing .

`NOTE: If you want your carrier added to the Toolkit then download and install, flash CWM Recovery and make a NAND Backup (changing the backup format to 'tar' first). Send me the boot.img file and I will root and add it.'
If you've made a NAND Backup...
If you send (link) the NAND Backup (changing the backup format to `tar' first), to mskip then hopefully he will add NttDocomo to the Toolkit (as above).

Tried ,but no dice counter on 9 flashes lol
Yes i did the same way as in the video but i think japanese SGS 3+ phones do not auto recovery .It is very similar to the JP Gs3 awaiting chain fire to respond or tweak the CF auto root.

Nice to hear from fellowuser of note 2 in japan.
Me too, trying hard to root but no luck.
Only manage to odin an insecure boot into my phone. Made it myself based on information from the net.
So far no problem yet.
Asking expert for help now.
Let's keep each other updated.
Sent from my SC-02E using xda app-developers app

Also wait for way to root my note 2 as well.:highfive:

Well i just made a new Nand back last night after i got off work .I will send it to Mskip today .
Sent from my SC-02E using xda app-developers app

Yeah. I'm keeping an eye on the threads. I prefer to risk it at weekends, when I have more time. Good job for trying so far..

$Donation$ in exchange Root Docomo note 2 SC-02E
Well after long hours of trying different ways to get the root I was unsuccessful.So I am going to sweeten the deal with the first person to root a NTT Docomo SC-02E Note 2 a donation of $50 via Paypal from me for your hard work.If you need the boot.img ,NAND back up or stock Rom please let me know .I have gone as far as clockwork mod recovery installed on the device and installed SU but super user cannot find the binary.
Hope someone can answer the call because i am itching like a drug attic trapped in a cube with no doors.

vipsavior said:
Well after long hours of trying different ways to get the root I was unsuccessful.So I am going to sweeten the deal with the first person to root a NTT Docomo SC-02E Note 2 a donation of $25 via Paypal from me for your hard work and for a added bonus I will throw another $25 on top if its done in the next 3 days from this post so $50 total.If you need the boot.img ,NAND back up or stock Rom please let me know .I have gone as far as clockwork mod recovery installed on the device and installed SU but super user cannot find the binary.
Hope someone can answer the call because i am itching like a drug attic trapped in a cube with no doors.
Click to expand...
Click to collapse
Hi VipSavior,
I had already send the stock ROM to one of the experts for help to pre-root it.
Just got them back.
2GB file just finished downloading.
Took me one whole day to download. (in office)
Will updated you when I am free to Flash.(maybe tonight)
Just wait for a while.........

I sent chain fire it he had a quick turn around in 2 days but the cf auto root did not work .It looked like it was missing the recovery .I also sent mskip a post ,but i have not got a reply yet.

Thanks for pushing the cause vipsavior.
I'm sure the experts will get it sorted, or give us more to test - hopefully this weekend.

No go for me either. Using Odin 3.07 and CF-Auto-Root-sc02e-sc02e.zip.
(Odin says Pass, but SU doesn't show up in apps.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-sc02e-sc02e.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

The best way to make a NAND back up is CWM you can get CWM by Flashing it in Odin.It will work trust me i did it plenty of times this week .Follow the directions it should take 5 sec to flash leave auto reboot checked .Use this file on there site International Galaxy Note 2 GT-N7100
CWM install directions

I am thinking of 1 more option flash the Rom with a custom one I know some stuff might not work like edy payment camera, gps and the 4G signal may be not as strong as the original. I am still looking on which rom to use. It's a risk but I will give it more thought.
I saw in the Japanese forms they are flashing using 7015 but some functions are lost. I hope CM mod comes to the note 2 soon.
Sent from my SC-02E using xda app-developers app

vipsavior, I noticed that your recovery is 8,388,608 bytes in size. The recovery from the original firmware (which Chainfire got from SamFirmware) is 6,273,280 bytes in size.
I hate to sound like a total noob, but could they be different? Are you sure that your recovery is stock from your device?
I'm hoping that it's just a question of getting the correct recovery.img to Chainfire.

Grant Barker said:
vipsavior, I noticed that your recovery is 8,388,608 bytes in size. The recovery from the original firmware (which Chainfire got from SamFirmware) is 6,273,280 bytes in size.
I hate to sound like a total noob, but could they be different? Are you sure that your recovery is stock from your device?
Click to expand...
Click to collapse
the recovery may be different because i used cwm.

I was also thinking if i do send my phone to get rooted can i extract the rom and upload it for others to download with SU installed

[Q] Am I Soft AND Hard Bricked At The Same Time?

Hello there people. I'd not new to this website.... I've just been a ghost that was finally forced to register for this site.
I have a
Tmobile Galaxy S3 (SGH T-999)
Now, I rooted my phone with CWM a while back.
So then after a couple of days, I decided that I wanted a Custom Rom. Turns out that it wasn't compatible for my phone.
So I got put in a bootloop.
I was able to Access Recovery and Download mode.
I factory reset my phone from there, formatted dalvik, all of that.
I downloaded a stock bootloader and stock Rom from here for my phone
I tried to use odin to flash the stock bootloader onto my phone. From what i can remember i saw, boot.img, Compete(Write) operation failed.
Now when i booted my phone all i see is
it just...... Activates
Firmware upgrade encountered an issue. Please select recovery mode in kies and try again.
Therefore i cannot access recovery mode anymore but i can still access Download Mode. I cannot see it boot at all.
Some Info while in download mode:
ODIN MODE
Product Name: SGH-T999
Custom Binary Download: Yes(1Count)
Current Binary:Samsung Official
System Status:Custom
Qualcom Secureboot:Enable
Warranty Bit:0
Bootloader Ap swaev:1
Here's how it looks when i try to flash stock rom or virtually anything onto my phone.
Code:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've given up on trying to do this myself and I now have to suck up my pride and ask for help.
Is there still hope, or do i have a $500 Paper Weight? Please Help.

What file did you download and flash? You posted in the sprint section sph710. If you flashed something for this model instead of your model that could be the problem.

metalfan78 said:
What file did you download and flash? You posted in the sprint section sph710. If you flashed something for this model instead of your model that could be the problem.
Click to expand...
Click to collapse
Sorry about that. I was rushing lol. I forgot what rom i downloaded. It was off an rooted app. I think it was ROM Manager.

That doesn't help. If you have a T-Mobile phone and you flashed something for a sprint phone then you need to download a T-Mobile ROM and flash. Or use a stock T-Mobile tar file and use Odin.

metalfan78 said:
That doesn't help. If you have a T-Mobile phone and you flashed something for a sprint phone then you need to download a T-Mobile ROM and flash. Or use a stock T-Mobile tar file and use Odin.
Click to expand...
Click to collapse
I remember now. I downloaded a CyanogenMod Rom. I did rebooted without deleting everything on my phone. Then i got soft brick. And I'm pretty sure, It will say Get pit file....... Complete(Write) Fail. As usual.

Great news. I tried to flash root66 on my phone. Which almost installed but failed. Now when i boot up my phone, I get put in the boot loop BUT I can access the recovery mode from there now. Now what? Do I install CMW or something or just stock?

Sir, just download a ROM for your phone model. But as I can see (and I think others members too) the safest is going back to stock until you understand the difference between your phone model and others.
Sent from my SPH-L710

Do you realize you keep posting in the sprint section? Thats going to make a huge difference. I keep asking because I don't think you realize you are in the sprint section and I'm assuming you keep downloading and flashing Sprint roms.

metalfan78 said:
Do you realize you keep posting in the sprint section? Thats going to make a huge difference. I keep asking because I don't think you realize you are in the sprint section and I'm assuming you keep downloading and flashing Sprint roms.
Click to expand...
Click to collapse
I know I'm posting in the sprint model, I didn't know when I first made this thread because I was in panic mode and I was about to be late for my mid term while making this thread. Can you give me a break? I really don't have time to make another one in the proper section.. + I didn't flash any sprint roms. I have a T mobile galaxy s3. And the Root66 Rom i attempted to flash was for SGH T-999. It failed but I was able to actually get into recovery mode again but it's stock recovery.

I wasn't trying to be a jerk, just trying to clarify. You'll get more help in the correct forum. Just because it's the same phone doesn't mean everything works the same. There are differences from one model to the next.

metalfan78 said:
I wasn't trying to be a jerk, just trying to clarify. You'll get more help in the correct forum. Just because it's the same phone doesn't mean everything works the same. There are differences from one model to the next.
Click to expand...
Click to collapse
ok, I will. And I know that. Look at the first post of the thread, I know the different model. I just posted in the wrong section due to rushing and stress.

Understandable, I've just seen quite a few confused people here

metalfan78 said:
Understandable, I've just seen quite a few confused people here
Click to expand...
Click to collapse
This thread can be closed now. I've made a new one in the proper section and more understanding.

It always comes in as 'I had time to mess with it but don't have time to fix it.' Sheez.

Kevets said:
It always comes in as 'I had time to mess with it but don't have time to fix it.' Sheez.
Click to expand...
Click to collapse
No. I had time at 5PM at home after returning from school. 3AM it got bricked. Went to sleep, Woke up at 7:40AM, Had to rush to get ready for school to take Midterms at 8:15AM + Make this thread. And there's no where in any of my posts where you see me say I don't have time to FIX it. I said I didn't have time to POST IN THE RIGHT SECTION.
Moral of this reply: You don't know me.
If you're not here to help, You can find your way out of my thread with your useless post. Sheesh.

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

Unable to receive OTA updates on AT&T S9

So here's some background to the situation: Back in January 2019, I was impatient for waiting for the new One UI update for my phone. My solution was flashing the update (CSA7) to my device using my SD card. Everything was functioning as normal, but since that day, I am unable to receive any updates, thus stuck on the January 1st Security Patch. I have searched everywhere and have had no luck. I can provide more information if necessary, and thank you in advance!

SierraTheWuffy said:
So here's some background to the situation: Back in January 2019, I was impatient for waiting for the new One UI update for my phone. My solution was flashing the update (CSA7) to my device using my SD card. Everything was functioning as normal, but since that day, I am unable to receive any updates, thus stuck on the January 1st Security Patch. I have searched everywhere and have had no luck. I can provide more information if necessary, and thank you in advance!
Click to expand...
Click to collapse
unfortunately, this is common for at&t users. the updates are PAINFULLY late and most folks just consign themselves to manually flashing the stuff they want. cheers

Youdoofus said:
unfortunately, this is common for at&t users. the updates are PAINFULLY late and most folks just consign themselves to manually flashing the stuff they want. cheers
Click to expand...
Click to collapse
Yeah I get that, but is there any way I could fix this?

SierraTheWuffy said:
Yeah I get that, but is there any way I could fix this?
Click to expand...
Click to collapse
not unless you want to become a main shareholder in at&t mobile

Youdoofus said:
not unless you want to become a main shareholder in at&t mobile
Click to expand...
Click to collapse
Nononono I mean how do I fix my device.

SierraTheWuffy said:
Nononono I mean how do I fix my device.
Click to expand...
Click to collapse
oh, sorry, i misunderstood. what is your phone doing? does it boot? bootloop? does it give an error saying that you must connect it to Keis to repair the operating system? (btw, never connect it Keis)

Youdoofus said:
oh, sorry, i misunderstood. what is your phone doing? does it boot? bootloop? does it give an error saying that you must connect it to Keis to repair the operating system? (btw, never connect it Keis)
Click to expand...
Click to collapse
My phone is functioning normally, but I cannot update it.

SierraTheWuffy said:
My phone is functioning normally, but I cannot update it.
Click to expand...
Click to collapse
have you tried with the firmware available on sammobile.com/firmwares?

Youdoofus said:
have you tried with the firmware available on sammobile.com/firmwares?
Click to expand...
Click to collapse
Yes, I have but odin just brings up a connection error

SierraTheWuffy said:
Yes, I have but odin just brings up a connection error
Click to expand...
Click to collapse
can you copy and paste the entire error log in a reply here? screenshots also work. Did you install what is referred to as "system wide ADB"?

Youdoofus said:
can you copy and paste the entire error log in a reply here? screenshots also work. Did you install what is referred to as "system wide ADB"?
Click to expand...
Click to collapse
Hello! I just installed it and heres the error
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1303)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 7755 M
<ID:0/009> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I am using an official Samsung Cable Connected directly to my Motherboard

SierraTheWuffy said:
Hello! I just installed it and heres the error
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1303)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 7755 M
<ID:0/009> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I am using an official Samsung Cable Connected directly to my Motherboard
Click to expand...
Click to collapse
thats the entire log?
what does it show on the phone when this happens?

Youdoofus said:
thats the entire log?
what does it show on the phone when this happens?
Click to expand...
Click to collapse
That is the entire log, and it just says
RPMB fuse blown
RPMB PROVISIONED, CURRENT BINARY: Samsung Official FRP LOCK: ON, WARRANTY VOID: 0x0, QUALCOMM SECUREBOOT: ENABLE, RP SWREV : B3(2,2,2,3,2) K3 S3, SECURE DOWNLOAD: ENABLE, DID : 20208B6DA5696611
on the download screen.

SierraTheWuffy said:
That is the entire log, and it just says
RPMB fuse blown
RPMB PROVISIONED, CURRENT BINARY: Samsung Official FRP LOCK: ON, WARRANTY VOID: 0x0, QUALCOMM SECUREBOOT: ENABLE, RP SWREV : B3(2,2,2,3,2) K3 S3, SECURE DOWNLOAD: ENABLE, DID : 20208B6DA5696611
on the download screen.
Click to expand...
Click to collapse
sounds like youre flashing the wrong firmware TBH
please list the entire firmware version too. Thanks!

sounds like youre flashing the wrong firmware TBH
please list the entire firmware version too. Thanks!
Click to expand...
Click to collapse
Hello! The Version my device shipped with was G960USQU3BRJ5 (Android 8.0.0) and my current firmware is G960USQU3CSA7 (Android 9.0.0). The Version that I was attempting to flash was G960USQU3BRJ5_G960UOYN3BRJ5_USC.

SierraTheWuffy said:
Hello! The Version my device shipped with was G960USQU3BRJ5 (Android 8.0.0) and my current firmware is G960USQU3CSA7 (Android 9.0.0). The Version that I was attempting to flash was G960USQU3BRJ5_G960UOYN3BRJ5_USC.
Click to expand...
Click to collapse
have you ever been able to successfully flash firmware before or is this your first time? When its your first time, i recommend putting the usb cable in gently and carefully. If youve done this 100 times before, just slap that puppy in there any way you want!!
ignore the italicized part, its my Mr. Hyde who thinks he is hilarious

Youdoofus said:
have you ever been able to successfully flash firmware before or is this your first time? When its your first time, i recommend putting the usb cable in gently and carefully. If youve done this 100 times before, just slap that puppy in there any way you want!!
ignore the italicized part, its my Mr. Hyde who thinks he is hilarious
Click to expand...
Click to collapse
Hello! This is indeed the first time I'm flashing firmware using odin. The other way I did it was by using my SD card and putting the update file on there, and then flashing it that way.

SierraTheWuffy said:
Hello! This is indeed the first time I'm flashing firmware using odin. The other way I did it was by using my SD card and putting the update file on there, and then flashing it that way.
Click to expand...
Click to collapse
putting it on your sd card and flashing it via TWRP?
Anyways, if you did the flashing on the SD card, it had to have been a TWRP flash, and thats not what youre aiming for here, from what it seems.
Are you using the stock cable? do you have ADB installed systemwide?
Using Odin isnt terribly hard, theres just a few things you have to do prior to attempting the flash for it to work. Also, when Odin is running and you have the phone connected, does Odin show a number in the com port?

Youdoofus said:
putting it on your sd card and flashing it via TWRP?
Anyways, if you did the flashing on the SD card, it had to have been a TWRP flash, and thats not what youre aiming for here, from what it seems.
Are you using the stock cable? do you have ADB installed systemwide?
Using Odin isnt terribly hard, theres just a few things you have to do prior to attempting the flash for it to work. Also, when Odin is running and you have the phone connected, does Odin show a number in the com port?
Click to expand...
Click to collapse
I am not using my stock cable but it is an official Samsung one. And i have installed ADB. When Odin is running, it does show a number in the COM port, It just has that error that I previously mentioned.

SierraTheWuffy said:
I am not using my stock cable but it is an official Samsung one. And i have installed ADB. When Odin is running, it does show a number in the COM port, It just has that error that I previously mentioned.
Click to expand...
Click to collapse
gotcha. sorry about the flood of questions. I a: am VERY forgetful and b: i wanted to make sure the silly mistakes were all off the table, which it seems like they are.
Where did you download your firmware from and have you tried the firmware you currently have with the "patched Odin" i suggested?

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.