[Q] Unlock code does not work - T-Mobile Samsung Galaxy Note II

Hi,
This is for a Canadian T889V (note 2) from Wind Mobile.
A few weeks ago I tried to use the online form to get an unlock code from Wind (they let you have the code after 6 months for $10), and the code didn't work, I called their customer support multiple times, and all I got was, try the same code again (tried it rooted/unrooted/completely stock, etc, etc...), and I'm down to the last unlock attempt.
They also suggested I call Samsung, which I did, but the Samsung rep just told me to call Wind again.
So, in the end, my situation is that I have 1 unlock attempt left, I have a pure stock phone (running 4.1.1, Baseband T889VVLALJ4 (I used Odin to flash image from SamMobile)) that has the flash counter tripped to 4, but at the Odin screen, it says:
Product name: SGH-T889V_NA_VTR (I thought Wind was supposed to be GLW)
Custom Binary Download: yes (4 counts)
Current Binary: Samsung Official
System Status: Official
Click to expand...
Click to collapse
I have tried what was suggested in this thread: http://forum.xda-developers.com/showthread.php?t=2014982 at least 10 times, I got the PERSO_NV_INIT is SUCCESSFUL message at the end at least 7 times, and in all attempts, when I put in the rogers SIM card from my iPad (only other micro SIM I have), it asks for an unlock code.
So now, I think my only option left is to try a third party unlocking service, and hope that it works... does anyone have any suggestions for such service?
Also, is it possible to reset the unlock counter at all/if this fails horribly, am I stuck with Wind for good?
Thanks,

StackUnderflow said:
Hi,
This is for a Canadian T889V (note 2) from Wind Mobile.
A few weeks ago I tried to use the online form to get an unlock code from Wind (they let you have the code after 6 months for $10), and the code didn't work, I called their customer support multiple times, and all I got was, try the same code again (tried it rooted/unrooted/completely stock, etc, etc...), and I'm down to the last unlock attempt.
They also suggested I call Samsung, which I did, but the Samsung rep just told me to call Wind again.
So, in the end, my situation is that I have 1 unlock attempt left, I have a pure stock phone (running 4.1.1, Baseband T889VVLALJ4 (I used Odin to flash image from SamMobile)) that has the flash counter tripped to 4, but at the Odin screen, it says:
I have tried what was suggested in this thread: http://forum.xda-developers.com/showthread.php?t=2014982 at least 10 times, I got the PERSO_NV_INIT is SUCCESSFUL message at the end at least 7 times, and in all attempts, when I put in the rogers SIM card from my iPad (only other micro SIM I have), it asks for an unlock code.
So now, I think my only option left is to try a third party unlocking service, and hope that it works... does anyone have any suggestions for such service?
Also, is it possible to reset the unlock counter at all/if this fails horribly, am I stuck with Wind for good?
Thanks,
Click to expand...
Click to collapse
Hi
I am also with wind and recently obtained the code same way you did. I am rooted running jedix 16 at the time with twrp as my custom recovery. So i am on 4.1.2 and the code worked right away. I dont think you should be on 4.1.1 to do it.
Sent from SGH-T889v Canadian Wind Mobile

vseslija said:
Hi
I am also with wind and recently obtained the code same way you did. I am rooted running jedix 16 at the time with twrp as my custom recovery. So i am on 4.1.2 and the code worked right away. I dont think you should be on 4.1.1 to do it.
Sent from SGH-T889v Canadian Wind Mobile
Click to expand...
Click to collapse
The first time I tried it I used the code on Jedi Master 10 (which is based on 4.1.2 if I'm not mistaken), I also tried the code on 4.1.2 stock (**MA3 base band), and 4.1.1 (**LJ4 baseband).
Right now I think my main priority should be figuring out if its possible to reset the unlock attempts counter (and/or finding other unlocking procedures to bypass the code/counter completely).

I think I just screwed myself even more, I took it to a shady place to see if its possible to get it unlocked, they did some weird voodoo crap which I think bricked by modem. (any attempts to get it into service mode shows a blank screen)
I tried reflashing everything and restoring an old EFS from long ago, but the baseband version in settings->about phone says Unknown, and it kept saying no SIM card even if I use my original SIM....
Did anyone encounter this before? how to fix this? do I need to get the hardware fixed? is Samsung likely to help?
Edit: I'm fairly sure they used and NsPro

You could probably just flash a new baseband and all will be well... Also the RIL needs to match the baseband as well for it to work and come up in about phone, so try downloading get RIL from the play store and see if it detects a non matching RIL (it needs to match the baseband) also it requires root
Sent from my Nexus 4

stewi21 said:
You could probably just flash a new baseband and all will be well... Also the RIL needs to match the baseband as well for it to work and come up in about phone, so try downloading get RIL from the play store and see if it detects a non matching RIL (it needs to match the baseband) also it requires root
Sent from my Nexus 4
Click to expand...
Click to collapse
Hi, thanks for the response,
I downloaded getRIL and gave it superuser permission, and it said my device is unsupported.
Also, what do you mean flash a new baseband? I restored an nandroid backup all the way back from Janurary and that didn't store phone functionality.
Thanks,

Dang... That's a shame, It is probably because the nandroid doesn't backup the modem/baseband, by the fact that you made a nandroid I'm assuming you have a custom recovery?
Sent from my Nexus 4

stewi21 said:
Dang... That's a shame, It is probably because the nandroid doesn't backup the modem/baseband, by the fact that you made a nandroid I'm assuming you have a custom recovery?
Sent from my Nexus 4
Click to expand...
Click to collapse
I have TWRP, I've tried using Odin to flash the stock .tar.md5 file from sammobile, and that didn't work. So I've re-rooted after that and recovered an old backup.
Strangely, I have modem.emmc.win and modem.emmc.win.md5 in the backup directory, but no modem option in TWRP when trying to restore that backup...

well that makes everything a lot easier, dont worry about ODIN, its a pain in the a$$
grab a modem from here http://forum.xda-developers.com/showthread.php?t=2061031 (see if you can find one that matches your ROM, otherwise just try any)
flash it in recovery, clear cache and dalvik and reboot and you should be sweet

stewi21 said:
well that makes everything a lot easier, dont worry about ODIN, its a pain in the a$$
grab a modem from here http://forum.xda-developers.com/showthread.php?t=2061031 (see if you can find one that matches your ROM, otherwise just try any)
flash it in recovery, clear cache and dalvik and reboot and you should be sweet
Click to expand...
Click to collapse
I tried both modems (4.1.1 and 4.1.2) from Wind (GLW) to no avail, it still says Baseband unknown and it still wont recognize any SIM cards...
If I go to a store with an NsPro, will they be able to fix it?

What's an nspro? Also if you don't mind losing your data, flashing a whole stock rom package through Odin should get you going if all else fails
Sent from my Nexus 4
---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------
You should be able to grab a complete Odin package over on samfirmware
Sent from my Nexus 4

stewi21 said:
What's an nspro? Also if you don't mind losing your data, flashing a whole stock rom package through Odin should get you going if all else fails
Sent from my Nexus 4
---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------
You should be able to grab a complete Odin package over on samfirmware
Sent from my Nexus 4
Click to expand...
Click to collapse
It's a thing that came up in research that repairs IMEI damage (I think but I'm not sure), in any case I already tried flashing an entire stock ROM (multiple times, 4.1.2 and 4.1.1) through Odin, and it didn't work.

Have you tried different packages, from memory some don't include the baseband and bootloader and stuff like that (It's been a while since my Samsung captivate)
Sent from my Nexus 4

stewi21 said:
Have you tried different packages, from memory some don't include the baseband and bootloader and stuff like that (It's been a while since my Samsung captivate)
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, I've tried the stock from this post:
http://forum.xda-developers.com/showthread.php?t=2061031
And a rooted version from this post:
http://forum.xda-developers.com/showthread.php?t=1975560

StackUnderflow said:
Yes, I've tried the stock from this post:
http://forum.xda-developers.com/showthread.php?t=2061031
And a rooted version from this post:
http://forum.xda-developers.com/showthread.php?t=1975560
Click to expand...
Click to collapse
At this point if I bring it back to Wind (and by extension, Samsung) I think it's fairly obvious I voided my warranty, but if I pay (not sure how much though), would they be able to fix it?

I'm not sure sorry, because I bought my captivate off XDA and the time I bricked it I had to mail it to adam outler and get it made unbrickable
try downloading an ODIN package from samfirmware and flashing it, because the .zip packages you linked wouldnt flash the modem and RIL. Also GLW is Wind on samfirmware, so just search T889V and choose the newest GLW package, youll need to make an account to download it

stewi21 said:
I'm not sure sorry, because I bought my captivate off XDA and the time I bricked it I had to mail it to adam outler and get it made unbrickable
try downloading an ODIN package from samfirmware and flashing it, because the .zip packages you linked wouldnt flash the modem and RIL. Also GLW is Wind on samfirmware, so just search T889V and choose the newest GLW package, youll need to make an account to download it
Click to expand...
Click to collapse
I already tried that (if you mean http://www.sammobile.com/firmwares/), and I think it's the exact same one as the teshxx download (factory image, exact same size and file name inside the zip, I haven't done an md5sum due to being on Windows),
I reflashed rooted injected stock ROM, did triangle away, and unrooted, and I'll bring it to Wind and see if they will fix it for me tomorrow.
Thanks for your help!

I think I'm actually having the same problems as this guy:
http://forum.xda-developers.com/showthread.php?t=2195869
I also tried QPST, and got the same exception as him...
And by page 4 the 2nd post down, http://forum.xda-developers.com/showthread.php?t=2195869&page=4 he took it to Samsung, and they did some software voodoo to bring it back to life... Fortunately there's a Samsung repair center in my city, and hopefully I'll have the same luck as he did (they aren't open tomorrow though).

One last thing before you do that (lucky you've got a repair centre!) this post says the efs is backed up when you install Cyanogenmod http://forum.xda-developers.com/showthread.php?p=30716302
So you might be able to recover it
Sent from my Nexus 4

stewi21 said:
One last thing before you do that (lucky you've got a repair centre!) this post says the efs is backed up when you install Cyanogenmod http://forum.xda-developers.com/showthread.php?p=30716302
So you might be able to recover it
Sent from my Nexus 4
Click to expand...
Click to collapse
When I restored the old backup (didn't work), I had the efs check box checked in TWRP, and I assume that efs should be in the stock ROM (that's how the OP of that thread did it)

Related

[HELP] Bricked my S3 i747M.

Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.
Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse
I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.
I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks
You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....
Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.
Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] If I flashed GT-N7100 ROM, how can I get back?

First, I'm an idiot,,,got new to android,,had no idea about flashing,, so I just randomly picked a Rom, and turned out its a GT-N7100 ROM, now my phone has no signal at all,,, anyone know how to flash back ? or I have to wait a att ROM come out?
BTW, Im with Rogers.
Thanks:laugh:
your gonna have to wait till either someone makes a odin back with a stock rom or makes a stock rom you can flash via recovery.
EDIT: did you make a backup?
this reminds me of the following youtube video:
http://www.youtube.com/watch?v=wwleOote5M0
Can you give a link to the firmware you flashed? It'd be useful to know if it contained a modem and/or kernel (or not.)
If it contained a modem, you'll need another modem. If it contained a kernel, you'll need another kernel. We have those. Regardless, you'll need to talk someone into getting you a system image (someone that has the same phone as you and has already rooted.)
Also, do you have CWM recovery installed? Is the existing firmware (as trashed as it might be) rooted? Can you use adb?
im an idiot
garyd9 said:
this reminds me of the following youtube video:
http://www.youtube.com/watch?v=wwleOote5M0
Can you give a link to the firmware you flashed? It'd be useful to know if it contained a modem and/or kernel (or not.)
If it contained a modem, you'll need another modem. If it contained a kernel, you'll need another kernel. We have those. Regardless, you'll need to talk someone into getting you a system image (someone that has the same phone as you and has already rooted.)
Also, do you have CWM recovery installed? Is the existing firmware (as trashed as it might be) rooted? Can you use adb?
Click to expand...
Click to collapse
nope,, I didnt back up anything,,
heres the ROM link I used.
http://forum.xda-developers.com/showthread.php?t=1925402
...
I just opened the file you linked to.. it includes a modem, kernel, etc.
I know you won't be happy with this, but until an ODIN image shows up, you're kind of out of luck. If someone you know has the same phone, you could ask them to do a backup to an external memory card, and then you restore that backup to your device. Assuming the modem wasn't flashed when you installed, that would get you back into business. If a modem was flashed, you'll need to get someone to extract a modem (and I'm not sure how to go about doing that.)
garyd9 said:
Please answer ALL of these questions. I can't help you if you don't answer them all...
Does your phone work now, with the exception of connecting to the mobile network?
Are you familiar with adb? If so, are you able to get a shell via adb?
When you plug your phone into your computer, are you able to copy files to/from the phone?
Which custom recovery do you have installed? CWM recovery or TWRP?
Is your phone rooted? (it probably is with a custom firmware - assuming the phone works at all.)
Click to expand...
Click to collapse
sorry buddy,,,
right now, the phone has no signal, asking for a sim card, which Ive already inserted it.
noepe, I donno what adb is, I tried google it, but I think its too complicate for me.
I'm able to copy files into or from my phone( SD card)
i rooted my phone through this:
http://forum.xda-developers.com/showthread.php?t=1923956
donno if i successed,,, but it has a superSU on my screen after I done it,(guess it count as rooted?) and I may used the TWRP
thank you for your help....
now Im back to my old Iphone 4
I updated that post. Basically, I can't think of anything you can do right now.. until an ODIN dump is available - or if someone gets you a backup you can restore. However, a backup won't flash the proper modem (and it appears you also overwrote the modem.)
garyd9 said:
I updated that post. Basically, I can't think of anything you can do right now.. until an ODIN dump is available - or if someone gets you a backup you can restore. However, a backup won't flash the proper modem (and it appears you also overwrote the modem.)
Click to expand...
Click to collapse
so, if theres a ATT ROM avaiable in the future,,,I can use my phone again by flashing the ATT ROM?
callmejoe1 said:
so, if theres a ATT ROM avaiable in the future,,,I can use my phone again by flashing the ATT ROM?
Click to expand...
Click to collapse
Was the phone originally from AT&T or Rogers?
callmejoe1 said:
First, I'm an idiot,,,got new to android,,had no idea about flashing,, so I just randomly picked a Rom, and turned out its a GT-N7100 ROM, now my phone has no signal at all,,, anyone know how to flash back ? or I have to wait a att ROM come out?
BTW, Im with Rogers.
Thanks:laugh:
Click to expand...
Click to collapse
Welcome to club i've been here for 6 days... it's a crappy feeling especially when its your work phone :[
garyd9 said:
Was the phone originally from AT&T or Rogers?
Click to expand...
Click to collapse
with rogers,but I heard ppl say ATT AND ROGERS‘s ROM can be equivalent , are they ?
callmejoe1 said:
with rogers,but I heard ppl say ATT AND ROGERS‘s ROM can be equivalent , are they ?
Click to expand...
Click to collapse
Perhaps - perhaps not. Until one actually flashes from the other, we don't know. (Many will tell you that they've done it with a different phone model - my answer to that is simply that it was a different phone model. Until its tried with THIS one, we can only guess.)
I think the biggest stumbling block for you right now is the modem. We have a stock kernel and recovery. A "near" stock system partition image can also be made from another device with a simple command. I have to be honest, though, that I have no clue how to extract the modem from these LTE phones.
A recovery (and kernel) can easily be flashed with ODIN (or with dd from a rooted shell.) Same for the system partition (which is, basically, the OS.) Getting a system image might be annoying, as you'd need to find someone with a roger's phone to make it for you, upload it, etc.
The modem, however... I'm not sure how to go about getting that for you. I've never had to create a modem image...
If/when a ODIN package appears, you can use a program that will, basically, reflash your entire phone to stock. Modem, kernel, recovery, bootloader, etc. Everything. Normally, users wouldn't see those ODIN packages, but there are a couple of websites that have access to some samsung servers where they a put. Once they are put there, we can get it...
Take care
Gary
Mobiletechvideos. Have them Jtag it for you.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Just me happy you don't have the note 1 if you would have made that same mistake you could have bricked your phone
envision said:
Just me happy you don't have the note 1 if you would have made that same mistake you could have bricked your phone
Click to expand...
Click to collapse
Yup your very lucky
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
Looking forward to this remedy as this is the reason I am jumping from att Galaxy S 3 to the note2. Want my international dev community back!
Unfortunately so far down here in Southern Florida Miami beach there is no white Note 2 anywhere.
For those that have the ATT version of the Note 2, if you've mistakenly flashed the ROM, I highly suggest visiting your nearest AT&T Device Support Center. Since I've previously worked in those centers, they have a propietary Samsung flashing tool that allows them to flash to the stock ROM, even if it's rooted. Granted they'll be able to tell if you've rooted it or not (which may or may not void the warranty, depending on who you talk to), as long as the phone can turn on and go to firmware recovery mode, the flashing works almost 100% of the time and it's a free service.
However, as I got my Note 2 yesterday, I've contacted my nearest DSC and they said that they don't have the ability to flash the Note 2 yet and they may have that ability to do so in the next few weeks or possibly by the end of the year (if you can wait that long). Being that the associates are just corporate drones, if they can't fix it, they'll more than likely replace your phone under warranty (which I don't suggest since the replacements are refurbished, and besides you should be within the 14 day return period for a new phone).
Sorry if it doesn't help the ones who have the Rogers versions.
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
would you mind if you can post the link for the modem and kernel please?
thank you
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
Im having the same problem. I hope you can roll out a fix!

[Q] problems unlocking sim Galaxy note 2 LTE

I have the GT-n7105 but i am unable to find anyway to unlock it so i can use other sims in it, i even took it to a shop and they said they can not do it, can someone point me in the right direction ?
emmanneil said:
I have the GT-n7105 but i am unable to find anyway to unlock it so i can use other sims in it, i even took it to a shop and they said they can not do it, can someone point me in the right direction ?
Click to expand...
Click to collapse
Right, as long as JB 4.3 has not been flashed listen up.
You have to do some homework, I cannot tell you what to do exactly, its all here already.
You will need to do a full EFS backup ok, full using the only method that works, so you will need the tools and the usb driver,.
You will have to downgrade to 4.1.1 using Odin 3.07 or newer, that runs on windows and using a cable.
You then enter the code that is explained in the rom development thread that explains how to unlock for free, which works as I did it on my n7105.
Next once you confirm unlocked, immediately upgrade to 4.1.2 again using ODIN. If you wish to go to 4.3, use Lion Rom or DN3, or other rom that has Knox free bootloader.
Best of luck, please use the thanks button if helpful and merry Christmas.
Once you confirm unlock
(InsertNameHere) said:
Right, as long as JB 4.3 has not been flashed listen up.
You have to do some homework, I cannot tell you what to do exactly, its all here already.
You will need to do a full EFS backup ok, full using the only method that works, so you will need the tools and the usb driver,.
You will have to downgrade to 4.1.1 using Odin 3.07 or newer, that runs on windows and using a cable.
You then enter the code that is explained in the rom development thread that explains how to unlock for free, which works as I did it on my n7105.
Next once you confirm unlocked, immediately upgrade to 4.1.2 again using ODIN. If you wish to go to 4.3, use Lion Rom or DN3, or other rom that has Knox free bootloader.
Best of luck, please use the thanks button if helpful and merry Christmas.
Once you confirm unlock
Click to expand...
Click to collapse
thanks for the info,
I have done some homework and i dont want spoon feeding and maybe i didnt explain myself properly in the OP. I have done the EFS back up and a full NANDROID backup . i have odin but i am falling at the last fence of finding 4.1.1 rom. i find roms but they all seemed based on 4.1.2 or higher. i did try and put a differenet modem on to get the options i need but all the hotfil links are dead
So find a rom for your device from another country or network, no big deal, as long as its 4.1.1 and for your device, and you can set your language temporarily so you can read what you are doing, flash it, do a full factory reset in recovery wipe cache etc, then, when your running 4.1.1, get straight to unlocking, once done and confirmed, get updating to at least 4.1.2 as you don't want to stay on 4.1.1 in case of sudden death.
Best of luck, you can work it out, I flashed maybe 5 different networks roms before I realised I was flashing ones for the wrong network.
unlocking
emmanneil said:
I have the GT-n7105 but i am unable to find anyway to unlock it so i can use other sims in it, i even took it to a shop and they said they can not do it, can someone point me in the right direction ?
Click to expand...
Click to collapse
As members have mentioned, down grading works...i had up dated to 4.3 official and then rooted, paid the 16 dollars and had the code sent from Cellunlocker.com. May not of been free, but it was too easy.

[Q] IMEI says 0 on 4.4.1

Hey guys, I think I screwed up. I think that I lost my IMEI through flashing it and I didn't make a back up. It says 0 and only very few of the *# codes work, the *#7285# and #22745927 codes do absolutely nothing and the only one that I know of that works is *#*#4636#*#* which doesn't help me at all. Most programs that I use don't detect the phone correctly or my phones just downright wrecked. Example is DFS says CPS N/A in every section and Samsung MEID Repair says "Unhandled exception has occurred in your application" when I try to connect it to my phone.
I'm running CM11 4.4.1 and I had the problem when I was running a 4.3 ROM. Also I have data and I can make calls. Its just that I cant send MMS and I drop to edge over time and stay on edge until I restart.
Any help would be greatly appreciated. Everyone I call is saying it'll cost $65 - $75 IF they can even fix it.
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Note that if you reinject IMEI, it might screw up your network
audit13 said:
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
I wish I could, When I try to use it, it says "Failed.. phone does not answer". Keep in mind that *#7284# doesnt do anything at all.
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
pcshano said:
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
chasetacos said:
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
Click to expand...
Click to collapse
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
pcshano said:
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
Click to expand...
Click to collapse
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
chasetacos said:
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
Click to expand...
Click to collapse
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
Click to expand...
Click to collapse
Cool. I Will do this and I will keep you updated. Itll be just a few moments before I complete the process
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
Click to expand...
Click to collapse
So when I try to flash the stock I get an error status 7. Any advice?
chasetacos said:
So when I try to flash the stock I get an error status 7. Any advice?
Click to expand...
Click to collapse
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Cool. It may not be till tonight or tomorrow till I respond, I'm about to have a project m competition. I'll let you know how it goes as soon as I get a chance.
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So now that Ive restored to stock, I have a transparent window with yellow text in it. it reads a bunch of info on the phone. It also said that it was in factory mode?
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So despite being stuck in factory mode I was able to write the NV and luckily I dont have any new network problems as far as I know. However my IMEI now says / 00 and in the phone info it says "unknown"
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
chasetacos said:
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
Click to expand...
Click to collapse
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
pcshano said:
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
Click to expand...
Click to collapse
Still nothing, im getting the same result. This Nv data bin file is not in there. i mean, unless i dont know where to look, but ive checked the whole EFS folder and its not in there...
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
elcocolo50 said:
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately that did nothing . I might just have to cry about it

[Q] I am trying to unlock T-Mobile S4 from ebay

So, I recently bought a galaxy s4 from ebay, and it seems to work on the network, so I don't think the IMEI is blacklisted. However, when I tried the steps here http://forum.xda-developers.com/showthread.php?t=2282683 and here http://forum.xda-developers.com/showthread.php?t=2283068, I am unable to complete the process. When I do the latter, which seems more like what I did with my S3, I get the same message "unable to process request". I remember I was getting this message on my S3 when I had the SlimKat ROM on it. But when I look at my S4, it looks like it has the OEM ROM on it, so I am not sure what is happening. I looked at my boot loader/baseband, and this is what I have: m919uvufnh7. I know that with my S3 I had to make sure I used the correct ROM to flash my phone, so I could get it unlocked the free method. So, does anyone know what bootloader and ROM could help me accomplish these steps in the second thread?
I am thinking I should flash a different ROM on my phone.
mji2015 said:
So, I recently bought a galaxy s4 from ebay, and it seems to work on the network, so I don't think the IMEI is blacklisted. However, when I tried the steps here http://forum.xda-developers.com/showthread.php?t=2282683 and here http://forum.xda-developers.com/showthread.php?t=2283068, I am unable to complete the process. When I do the latter, which seems more like what I did with my S3, I get the same message "unable to process request". I remember I was getting this message on my S3 when I had the SlimKat ROM on it. But when I look at my S4, it looks like it has the OEM ROM on it, so I am not sure what is happening. I looked at my boot loader/baseband, and this is what I have: m919uvufnh7. I know that with my S3 I had to make sure I used the correct ROM to flash my phone, so I could get it unlocked the free method. So, does anyone know what bootloader and ROM could help me accomplish these steps in the second thread?
I am thinking I should flash a different ROM on my phone.
Click to expand...
Click to collapse
Have you tried contacting T-Mobile? If the phone is paid for in full, they are supposed to unlock it for free.
This worked for me:
http://forum.xda-developers.com/showthread.php?p=58645651
Sent from my SGH-M919 using XDA Free mobile app
rlichtefeld said:
Have you tried contacting T-Mobile? If the phone is paid for in full, they are supposed to unlock it for free.
Click to expand...
Click to collapse
Thanks for the response, but I have not tried it, because I don't think it is that easy. I also purchased AT&T tablets and tried unlocking them, but AT&T said they were 'active' under someone else. They were not not showing as stolen, but active. I am not sure what that entails, but I am guessing I have to register it under my account first, before I can request to unlock it. So before I try going through the long process of figuring out how T-Mobile can unlock my device, I thought I would give this a try. It seems simpler and since I plan on modding my phone after I unlock it, I see it as just part of the process. (At least I hope so.)
radoo7701 said:
This worked for me:
http://forum.xda-developers.com/showthread.php?p=58645651
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
I will try this. But I was trying to make sure that there was no problem with downgrading, as I am currently on 4.4.4. And I know that on my S3 there was a big warning about downgrading from 4.3 to 4.1. To avoid bricking my phone, I thought I would ask and make sure.
So thanks again to both of you for the responses!
I will try this. But I was trying to make sure that there was no problem with downgrading, as I am currently on 4.4.4. And I know that on my S3 there was a big warning about downgrading from 4.3 to 4.1. To avoid bricking my phone, I thought I would ask and make sure.
So thanks again to both of you for the responses![/QUOTE]
You only have to downgrade the modem. This should not brick your phone.
Sent from my SGH-M919 using XDA Free mobile app
Would you please posts step by step on what you did to successfully unlock 4.4.4 T-Mobile which I assume is version M919UVUFNK2.
How to Unlock Samsung Galaxy S4 M919 4.4.4
c627627 said:
Would you please posts step by step on what you did to successfully unlock 4.4.4 T-Mobile which I assume is version M919UVUFNK2.
Click to expand...
Click to collapse
Alright, I was able to get mine to work, so maybe I will list my steps. However, I must say that I had some failed attempts (in part due to not understanding the post referred to by radoo7701) and some issues with my phone. But those steps wont be included. Also, my version was m919uvufnh7, not NK2. I would think it does not make a difference, as long as you reflash back to NK2 at the end.
1. I locaed the modem for M919UVUAMDL and m919uvufnh7 modem (as I did not make a backup of mine before starting)
2. I used Odin 3.07 to flash the AMDL modem
3. I tried the steps here http://forum.xda-developers.com/showthread.php?t=2283068, but this would not work, I could not even get the menu to pull up, as it would say request unable to complete. So I tried this http://forum.xda-developers.com/showthread.php?t=2282683 and that actually worked, so I went through these steps successfully.
4. Use cf-auto-root to root your phone
5. Download regionlockaway and transfer it to phone, then install it on phone and run it.
6. flash m919uvufnh7 modem and booted up with my AT&T sim, and it did not ask for unlock code. It just worked!
NOTE: I did have to use a T-Mobile sim card to do the menu process, but radoo claims that he did not do the menu portion. I had already done the menu portion when I finally got to reading his comment. So I can't say that it will work or not. Either way, his suggestion worked for me and I am content with the result!
Thanks radoo7701!
Please post link to files in step 1 you specifically used. And also links for step 5 you used.

Categories

Resources