Hi guys.
I would like to flash, but currently it is too risky for me because i got a netlock. So i have to unlock my Samsung galaxy s.
First i tried to use the SGSUnlockTool but it said if i actually had a galaxy s.
Afterwards i used other methods like your windows unlock tool, but that didn't work too - it said that it doen't find the "nv_data.bin" file.
I read through several forums and i read that the nv_data.bin could be "damaged" because of flashing. The only problem is, i never flashed (at least i never flashed manually) I just flashed with Kies from Eclair -> Froyo and one time i used the kies reg hack to get Froyo on my galaxy s.
So what could I do?
Shall i even unlock my phone before flashing manually?
(SP and all other locks but the networklock are off!)
(btw. sorry for double post)
Thx in advance
Joker
can you please tell me what is netlock
Related
Hello. I'm just a newbie on android system. I get my sgs yesterday. My friend bought it for me from Austria(he lives there) and i will use it in Turkey. When i used my sim card in there is sim lock request so i need to unlock sim.
Firstly i tried to upgrade firmware. I thinked that may surpass simlock part but it didn't work. I installed 3br update before it but after the firmware change 3br didnt run because of 2.1 update file. I installed couple of programs to easy root but now my sgs is messed up and there is no android market now. Only thing i want an updated and working phone with some applications :/. I know that there are my answers in forum because there is lots of good information about sgs but my phone is now messed up and i need to fix it step by step with some help.
I really need some help. Thank you.
I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)
I am also on sasktel and am an impulsive flasher (1-5 times daily) Heres an easy, fast fix. GO here:
http://www.darkyrom.com/community/index.php?threads/guide-installing-rc5-easy.2382/
go to section enabled "For GT-I9000 users only" and follow step by step. You can stop at step 2 if you want to leave your rom stock samsung or do last few steps to have darkys on there. EIther way once done you'll also have to enable the 850 band *#2263# then enable wcdma 850 option. Also you will have to manually enter your APN under network options. I use inet.stm.sk.ca for sasktel. Note that the Ficeto_JVB.zip download there includes all needed to flash (.pit file, rom, odin). THis is always my fail safe method after boot loops ( I always screw something up playing around lol).
ps: also depending how desperate you are and how trusting you are, I work at sasktels head office in the cornwall and if you wish I am sure I could take 15 mins out of my day tomorrow to do this for you, although you will not be able to get through security so you will have to trust me taking off with your phone lol. email me at [email protected] if needed.
trouble is I can't put things on SD card because I can't get it to load android
You won't be able to load eclair through Odin because JL2 installed a new SBL (secondary boot loader). Go to samfirmware.com, download JL2, and use odin to flash that. Once that's flashed it should fix your issues. Then, if you want a custom ROM, try the romkitchen (romkitchen.org).
problem solved!! turns out darkyrom did fix my phone, I couldn't push the zip file to my phone but their tar file got my phone working! Thanks for all the help
Dougustine said:
I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)
Click to expand...
Click to collapse
I loled, I've been in the same boat, wife is always asking me why I always have to mess around with stuff. Shoulda seen her face after I soft bricked the phone the first time.
Just rooted my phone
I am new to this, I can do all kinda of things with my pc but with my phone a different story lol. I don't understand when you say "Eclair". Is that a different model or is that stock. I am too from sasktel.
Android 2.1 is Eclaire, 2.2 is Froyo and 2.3 is Gingerbread... Ice cream is next 4.0
hi guys, I know this is an old post but has anyone successfully unlocked their Sasktel i9000 vibrant without paying any unlock code service? has anyone tried anything like the SGS Unlock Pro that claimed to unlock all GSM galaxy S phones but did not list Sasktel? anyways, from the sound of it is Darky's rom currently the best for i9000's? I wanted to try CM9, so i did the super 1 click root and followed the CM wiki page to push clockwork recovery to the phone through Heimdall Suite but both times i tried failed and stuck in a boot loop so both times i ended up going through Odin to fix it. (super 1 click root didnt seem to stick b/c i lost superuser after fixing the phone w/ Odin, is that normal?)
anyways i had a very unique situation, originally had a Bell i9000m but died 1 week later tried to fix it numerous times for 7-8 months ( i live in U.S., and Sammy refuse to fix it b/c i dont have a canadian address they can send it back to b.s.) anyways finally landed myself a dead i9000m w/ broken screen, so i took both apart and put the working parts together. now 1 working phone with 3 problems: 1) so it seems that it's currently locked to Sasktel (it can be done but i'm curious if there is a cheaper way or even free) 2) CM wiki suggested Heimdall push CW recovery cause boot loop (some on xda suggested flashing the phone back to 2.2 (or 2.1??) first) 3) i was playing around and click on screen update and lose my touch keys ever since (ppl also suggest flashing it back to 2.1 and reupdate the keys, but will a bell i9000m 2.1 stock rom be compatible w/ the i9000m from Sasktel?)
anyways lots of questions there but if anyone can answer anyone of these would be greatly appreciated.
thanks in advance
Update: problem 1 is taken cared of. SGS Unlock Pro worked like a charm. tested, working. other 2 problem still unsolved.
Here is why I'm asking this. I have a SGS I9000b. After some wrong doing that almost bricked my phone, the screen started to show that I had and SGS I9000b and then the B would quickly vanish resting only the Samsung Galaxy S GT-I9000.
The fact is, after some effort I was able to install eclair on the phone and put it to run again, but now when I start it, it shows SGS GT-9000 to quickly be substituted by GT-9000b.
I was unable to upgrade my SGS to froyo again, and maybe this is one reason that I cant, every time I try, I get that /dev/ error.
So, What does it means when at the start screen the modle changes suddenly?
Hope I could express myself clear enough.
I came across a similar thread yesterday.
http://forum.xda-developers.com/showthread.php?p=13268587
I guess the first part of the boot screen is from the bootloader and the second part of the boot screen is from the ROM? (pls correct me if I am wrong)
So, have you tried flashing I9000B stock ROM with bootloader using Odin?
If you want to upgrade using samsung softwares, you need to have the stock rom of your phone or an official stock upgrade (can find on samfirmware or in various posts here), otherwise in order to change rom you can use odin
Since a few days it is impossible to use my Samsung Galaxy GT-I9000 as a phone. Whenever i try using it, it doesnt register on the network.
I am running DarkyROM JVH v10.1 baseband version I9000XXJVO Firmware 2.3.3
If i try to register on the network is searches and searches and searches... but doesnt find anything.
What "worries" me is the fact that when i start up the phoe is tells me its a Samsung Galaxy S II, which it surely isnt!
Please advice.
CheopsChefren said:
Since a few days it is impossible to use my Samsung Galaxy GT-I9000 as a phone. Whenever i try using it, it doesnt register on the network.
I am running DarkyROM JVH v10.1 baseband version I9000XXJVO Firmware 2.3.3
If i try to register on the network is searches and searches and searches... but doesnt find anything.
What "worries" me is the fact that when i start up the phoe is tells me its a Samsung Galaxy S II, which it surely isnt!
Please advice.
Click to expand...
Click to collapse
There is your problem..
Re-flash stock firmware with pit and re-partition, When complete, check you can register on the network.
If so then avoid the ROM which you are currently running.
EDIT: When you say the phone says Galaxy S II, Is this not a boot animation taken from the SGS II ? Or is it the actual boot screen which says its a SGS II ?
Call me stupid ;-) but i didnt save my stock-rom....
CheopsChefren said:
Call me stupid ;-) but i didnt save my stock-rom....
Click to expand...
Click to collapse
No problem.
Head over to www.samfirmware.com and grab one from there, flash it through odin, Instructions are on that site too.
Thanks AzzleDazzle, but now comes up another problem.... Probably very basic, but for me, its all abracadabra.
I have an European Samsung Galaxy S GTi9000, but if i look at the site there are many roms u can download. From Android 2.1 to Android 2.3.4 for "my" device. Which is the one i should use? My ID is I9000XWJVH, which is according to the site an unknown H version.
Please advice once more, thanks in advance!
No worries, Make sure you download a firmware specifically for the I9000
the last 3 letters eg JVH is the firmware version, JV.X. represents gingerbread 2.3.3 and above.
Gingerbread is the latest release, so i would go for one of them, The one at the bottom of the page on samfirmware will be the very latest, Which i think is JVR
So look for I9000XXJVR.
flash that in ODIN and job done you should be back up and running and with the latest release.
The rest is upto you . i.e going to a custom ROM / rooting ect...
i feel more and more like a noob....
I started Odin, and there u can choose for the pit file, or for the pda file (which is the one i should use i guess), but also u have the choices of re-partition auto reboot and f. reset time. Which of those 3 (or non at all) i should use?
I dont know what has happened. I choose for only reboot after flashing. Flashing went okay, but now it seems to be stuck in a loop. The Galaxy S screen gets followed up by a Swisscom screen in a seemingly endless loop.
Worse, with volume down - power on i can not come in the download menu anymore...
Any advice would be much appreciated now.....
Also when trying a re-partitioning via Odin it doesnt work?
Found the solution. Using Odin 1.8 did the trick. I used Odin 1.3 which probably couldnt flash the 2.3.4, while when i tried with Odin 1.8 it worked flawlesly.
Thanks for your help!
I F****** up..
i played with rooting and flashing before i found these forums with guides and stuff.
and now my samsung galaxy have no mobile network, no imei number and freezes when i activate bluetooth..
it was also bricked (logo loop) but i fixed that.
i have flashed stock firmware in it and it works fine beside the 3 problems above.
i've tried
http://forum.xda-developers.com/show....php?t=1801997
http://forum.xda-developers.com/show....php?t=1804123
neither did work since i cant usb connect i've tryed every option to get my pc to usb detect my mobile.
including kies and latest samsung drivers, reinstalling and with or with out kies.
someone please be my hero and give me some answers
you guys ****ing rock and i know we can fixx this!
Unfortunately the only simple way to fix things ...
Unfortunately the only simple way to fix things is to find a backup of your EFS partition - look after something called:
efs.img
efs.tar.gz
efsbackup.tar.gz
efsdev-mmcblk0p3.img.gz
(the img versions are probably the best, but either one should work to some extent).
EDIT:
OOPS, just now I noticed that you are speaking about a i9305 - you should look here:
http://forum.xda-developers.com/showthread.php?t=1946915