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

Having issues with i747, need assistance.

Just picked up a new-ish i747 from my brother because he grabbed the latest note. He did a factory reset on it and it kept getting stuck at the white ATT screen. I figured no big deal I'll just take it home and root/rom it.
Well following this guide...
http://forum.xda-developers.com/showthread.php?t=1739426
...I get the following error when trying to use odin.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Why is this thing not flashing, and why did a factory reset cause this thing to get stuck at the white ATT screen?
FWIW I plan to root/unlock this thing so I can use my tmobile straight talk sim in it. Just can't get it to cooperate for some reason.

Hi.
Make sure you're using an official Samsung cable.
Go back into recovery and be sure to format /cache and /data too.
Sent from my SGH-I747 using Tapatalk

RJantu said:
Hi.
Make sure you're using an official Samsung cable.
Go back into recovery and be sure to format /cache and /data too.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I was using the OEM cable and that didn't help.
Eventually I was able to get the phone to boot normally. I then rebooted in to download mode and tried the CF auto root method here...
http://forum.xda-developers.com/showthread.php?t=1963790
...which appears to have worked.
Now since I want to use my straighttalk tmobile sim in this device I'm guessing I have to unlock it. How do I go about doing that on 4.3?

You will have to get an unlock code for your phone. With the 4.3 bootloader, you cannot downgrade to the stock 4.1.1 ROM that's required to use the free unlock method.

You can't do it the same way you would in 4.1.1 with the dialpad. If you can downgrade to that you can unlock it for free.
Sent from my SGH-I747 using Tapatalk

RJantu said:
You can't do it the same way you would in 4.1.1 with the dialpad. If you can downgrade to that you can unlock it for free.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Is there an easy/safe way to downgrade? I'm going to be throwing a rom on here when I'm done anyway.

johnnyrichter said:
Is there an easy/safe way to downgrade? I'm going to be throwing a rom on here when I'm done anyway.
Click to expand...
Click to collapse
DO NOT attempt to downgrade to an earlier version of stock ROM with ODIN or you will brick. See if your brother can work with you to get the unlock code from AT&T. This will be the safest way to SIM unlock. Do not install any custom ROM until this is done
Sent from my awesome phone.

aybarrap1 said:
DO NOT attempt to downgrade to an earlier version of stock ROM with ODIN or you will brick. See if your brother can work with you to get the unlock code from AT&T. This will be the safest way to SIM unlock. Do not install any custom ROM until this is done
Sent from my awesome phone.
Click to expand...
Click to collapse
He is on his way over with a microSIM so I can cut my straighttalk tmobile sim down. I'll have him call ATT while he's here.
Will report back once done.

johnnyrichter said:
He is on his way over with a microSIM so I can cut my straighttalk tmobile sim down. I'll have him call ATT while he's here.
Will report back once done.
Click to expand...
Click to collapse
ATT is refusing to give him the unlock code. They're telling him to submit an online request which takes an unknown amount of time to complete IF it's approved. They said giving him the code over the phone is against some new policy.

johnnyrichter said:
ATT is refusing to give him the unlock code. They're telling him to submit an online request which takes an unknown amount of time to complete IF it's approved. They said giving him the code over the phone is against some new policy.
Click to expand...
Click to collapse
If the phone out of contract already, your brother can submit request for unlock, I did twice for (2)iphone and withing week or two get unlock.

4b3ck said:
If the phone out of contract already, your brother can submit request for unlock, I did twice for (2)iphone and withing week or two get unlock.
Click to expand...
Click to collapse
I'm trying to get this done tonight. I have work at 530am and already cut up my sim card which I now wish I wouldn't have done until I found out how retarded ATT is about unlock codes.

Went ahead and gave cellunlocker a try, fully convinced that I was about to lose 30 bucks, and it actually worked. Using rom manager to flash the latest CWM so I can flash AoCP kitkat.

johnnyrichter said:
I'm trying to get this done tonight. I have work at 530am and already cut up my sim card which I now wish I wouldn't have done until I found out how retarded ATT is about unlock codes.
Click to expand...
Click to collapse
The straight talk sim should work without an unlock code. Provided you have an AT&T compatible sim card that they recently started using again. My phone is an AT&T locked s3 using a Net10 sim. Put it in and then go to the APN Settings, insert your settings, reboot and enjoy. Tracfone, straight talk and Net10 are all 3 one in the same company, I assume since that's how it works on Net10 it will work that way for you.
Although I don't know for a fact that you shouldn't have to be unlocked someone else who does run straight talk could maybe post up.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth

It's the tmobile sim from straight talk so I needed the unlock which is done already.
Now I'm trying to get stuff to install. I installed rom manager but it won't flash CWM, it just sits on "flashing." I also can't get supersu or superuser to work. I think it has something to do with knox, and/or the method I used to root this thing last night.

Used this method(#2) to flash cwm/remove knox...
http://forum.xda-developers.com/showthread.php?t=2538991
...and it worked. Was able to then flash 4.4 aocp and the latest gapps. Everything seems to be working and I'm not getting those stupid security warnings anymore.

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)

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.