Database Users

[REF] Samsung Galaxy S - Froyo JP6 - SIM UNLOCK -

Hello,
I`ve made my "official" update to Froyo JP6 and I wanted to SIM unlock my phone. Since last unlock application did not worked (basically because SIM lock number was removed from nv_data.bin)
So this is how I did it.
My phone specs:
Model number: GT-I9000
Firmware version: 2.2
Baseband version: I9000XXJPM
Kernel version: 2.6.32.9
Build number: FROYO.XWJP6
Locked network: Orange Romania
Prerequisites:
- phone must be rooted
- adb application (you can find it in "Generate Unlock Windows.zip " from this /showthread.php?t=761045 post)
* first backup your /efs folder
change /efs permisions:
Code:
chmod 775 /efs && chmod 775 /efs/.*
get all files within /efs folder:
Code:
adb pull /efs bk2/
(where bk2 is a folder where adb resides)
* edit nv_data.bin with a hex editor
copy nv_data.bin from your backup folder and open it with a hex editor
move to Offset 18146E and change those 8 Fs(FFFFFFFF) to 00000000 (this should change your SIM unlock code to 00000000)
(I didn't do this step) move to Offset 188021 and change whatever is from that cursor (ex. GT-I9000HKDXEE) to XEF
save your binary file
* clean your /efs partition (you must have some free space for your phone to generate and work with your nv_data.bin file - If you don't have enough space it will write until it gets full and your phone will probably end up not seeing any SIM card (that's what happened to me, /efs was 100% used and I could not use any SIM. message: no sim card. or insert a sim card)
1. connect from your PC to phone's shell
Code:
adb shell
2. obtain root access
Code:
su -
3. list partition usage - it would be most of it used ~ 6Mb
Code:
df /efs
4. list the content of /efs/ filesystem
Code:
ls -l -a /efs/
5. remove most of the content
Code:
rm /efs/nv_data.bin.md5
rm /efs/nv_data.bin
rm /efs/.nv2.bak
rm /efs/.nv2.bak.md5
rm /efs/.nv_data.bak
rm /efs/.nv_data.bak.md5
6. check filesystem usage again. it should be ~ 3Mb
Code:
df /efs/
* copy your altered nv_data.bin file
from another prompt do:
Code:
adb push nv_data.bin /efs
(altered nv_data.bin which was edited in second step)
from your first shell where you connected earlier as root create the md5 file:
Code:
md5sum /efs/nv_data.bin | tr '\n' 'X' | sed 's/ .*//' > /efs/nv_data.bin.md5
change permissions/owner on nv_data files:
Code:
chmod 775 /efs/nv_data.bin && chmod 775 /efs/nv_data.bin.md5
chown radio.radio /efs/nv_data.bin && chown radio.radio /efs/nv_data.bin.md5
* now let`s unlock your phone
disconnect from your adb shell (exit, exit) and remove your USB cable
remove your phone's battery (without powering it off) and put another operator's SIM card
!!! When you'll be asked about unlock code enter: 00000000. It might say its unlocked or it might not. It may hang on searching network provider or it may not. After couple of minutes power off your phone and start it again with that SIM card in it. Pray that it will actually work ( For me it happened not to be able to "slide to unlock". It worked to power off the screen and power on, I could see animation but I could not do anything with my touchscreen)
!!! Your IMEI will be screwed (at least mine was), that's why it will be ok to keep your backup files on your PC so you can restore at any time if you need it
* restore
proceed like in previews mode but now you have to copy ALL your backed up files to your phone and you have to change ownership/rights to all copied files
Code:
adb push bkp_folder/ /efs/
(all files/folders within bkp_folder will be restored on /efs)
!!! pay attention on /efs rights (
Code:
ls -l -d /efs
you may change write permissions to all users
Code:
chmod 777 /efs
I`ve gathered all the info from other posts (mainly from this /showpost.php?p=8681529&postcount=806 one ), i haven't invented the wheel you know..
Please post if it`s working for you...

that's usful, thanks much!
Sent from my GT-I9000 using XDA App

...worked.
Had a friends SGS from 3 - Drei (Austria) here to unlock. Even unlockcode from Samsung did not work.
But now its unlocked.
thx

Dear users
I am in trouble
I am new to this forum, so please forgive me if i don't sound appropriate.
my samsung galaxy s (android) is un-unlockable
its working on the parent network but absolutely un-unlockable
did try to send to some geeks sitting in the market but they couldn't do it.
used also the self extracting code methods but it always says "no codes found"
don't know what to do... please if any one of you had this problem or you know about this problem please share any info you may have on this issue.
many many thanks
asim

Yes!
It worked for me too but now I have a wrong IMEI 004999010640000. I'm still like that because I don't think that a problem for my operator FR SFR
The first time I had boot, it told me no SIM no network.
I removed the battery for a couple of minute and the next time it works!
For your info, I also moved to Offset 188021 and changed whatever is from that cursor to XEF
When I did this tips few days ago, i used the same SIM card (from a other country CH Swisscom) but in a place where I can't connect to the original carrier of this SIM. And it did'nt work. Maybe that can explain...
I tried SGS Unlock many times but always code not found
GT-I9000/2.2/I9000XXJPM-Tayutama Edition v1.0.0-LagFix Voodoo 5 Pre6
Thx

Find this strange.
If you imei number is wrong then you have Some trouble.
And you could easy just deleted all files in the efs folder and you could use any simcard you want.
This would generate a new imei number. But it will be useless for you if you want to use it either keis or Samsung stuff. And you can't sent it for reparation before you will restoring the imei number.
Sent from GT-I9000 Jpm OS kernel with z4mod

For the moment I had no problems and my phone is unlocked. My Kies works perfectly.
IMEI number is good in efs folder but not when I check on the phone.
But it's clear that I must restore the files if I want to send it to Samsung.
With all tools and post at xda, I don't need Samsung support...
GT-I9000/2.2/I9000XXJPM-Tayutama Edition v1.0.0-LagFix Voodoo 5 Pre6

Worked for me aswell.. Great work

asim_121 said:
Dear users
I am in trouble
I am new to this forum, so please forgive me if i don't sound appropriate.
my samsung galaxy s (android) is un-unlockable
its working on the parent network but absolutely un-unlockable
did try to send to some geeks sitting in the market but they couldn't do it.
used also the self extracting code methods but it always says "no codes found"
don't know what to do... please if any one of you had this problem or you know about this problem please share any info you may have on this issue.
many many thanks
asim
Click to expand...
Click to collapse
Had the same problem on my friends phone (no codes found, Samsung unlockcode not working).
Phone is unlocked now and IMEI did not change.

Hello,
I followed this procedure and aftewards I have a different IMEI number.
Does anybody know which file is responsible the IMEI ?
I have all the original files saved to a backup folder on my pc.
I connected to kies mini after and it says my phone is not registered! My IMEI number is wrong.
Anyone know which file will restore my IMEI?

froyo sim unlock
Does anyone know if this method can work for captivate or it's only for i9000. And can i update to i9000 rom then do this method.
thank-you

will this solution work for android 2.1?

My EFS folder and the nv_data are deleted and I didn't made a back up.
what can i do to get them back??

md5sum /efs/nv_data.bin | tr '\n' 'X' | sed 's/ .*//' > /efs/nv_data.bin.md5
thats not working
it says
md5sum: not found
tr: not found
sed: not found
maybe this is why imei is corrupted (changed), cause md5 sum not match.
tried with md5summer and it's not working either

this line:
md5sum /efs/nv_data.bin | tr '\n' 'X' | sed 's/ .*//' > /efs/nv_data.bin.md5
Create a bad md5.
on my nv_data.bin:
Original md5: c5c3593b6e280a97d04205ae5b6043ba
Created md5 with this line: 449136859ae1319e2ee3cbef1c87f9eb
"Missmatch"
Only reboot create a good md5.
Modify your tutorial please.

That works!!!
Thanks so very much!!!
Only commends:
md5sum /efs/nv_data.bin | tr '\n' 'X' | sed 's/ .*//' > /efs/nv_data.bin.md5
I've made as:
md5sum.exe nv_data.bin | tr.exe '\n' 'X' | sed.exe 's/ .*//' > nv_data.bin.md5
in my Windows folder, runing it from cygwin shell and next I moved
nv_data.bin.md5
on the phone to /efs/ folder

When i double click adb.exe it just popup and closes!?!?! I am on windows 7, how to enter this?

Worked for me, but the weirdest thing happened, I put in a Cosmote RO sim card, after following the guide from this thread and it didn't even ask me for the unlock code, it accepted it and it worked perfectly fine, even tho the phone was blocked on Orange RO, I know this for sure cause few days ago I tried the sim card that is working now and it didnt work before... Thanks.

My data_nv.bin does not contain offset 18146E...
Docomo Galaxy
PDA: SC02BOMJJ1
Phone: SC02BOMJJ1
CSC: SC02BDCMJJ1
Bild Info 2010.10

Works perfect for me on Gingerbread 2.2.3 Darky ROM v10 RC3 All I did was hex edit the nv_data afrom phone memory and write back. Unlock code was 00000000. Thanks very much becuase before this my phone wouldnt detect network following SGS unlock

Weak Flipout mobile network signal

I've debranded a UK Orange Flipout and unlocked to use on Vodafone UK.
The mobile signal is terribly weak and spends more time with no bars that with. It makes the phone useless as a phone however great the design is.
Sitting next to another android phone on the same network the bars are almost full on the other phone - when showing nothing on the Flipout.
Does anyone else have this problem? Is there something I can do to re-configure the phone and make it work as a phone? I've had all the data settings from Vodafone reset for MMS and data etc.
If no answer it will have to go back to stock ROM and back to the shop.
Thanks.

Hey, I got the same problem. Had me temporarily switch back to Milestone 'cause Flipout wasn't able to even connect to the service..no signal at all. I noticed that Flipout has slow network acquiration compare to Milestone. But, I have to point out that I flashed it from stock to UK ROM without BLUR so it's more likely possible that something just went wrong. For now I blame the basebands and try to solve it that way..somehow. let me know if any news
Sent from my Milestone using XDA App

ok, it was the baseband.. i changed it from what it was to this (attachment) and everything's fine.
you have to be rooted, and remount system as r/w
the original baseband files are located in /system/etc/motorola/bp_nvm_default
basically you need to replace this folder with the new one and set the same permissions as the original files had. i don't know if you know how so just for sure, here's the how-to
i suggest you doing this:
0]if you are not rooted, install Universal Androot and press Go Root, then reboot your phone
1]unrar the attachment to your phone's sdcard
2]boot up the phone, switch to airplane mode
3a]if you have Root Explorer, navigate to /system/etc and push remount as r/w
3b]if you don't have that, install Root Toolbox go to Mount-System Mount Options-Mount System R/W
4]fire up Terminal Emulator
5]enter those commands: (enter after each line)
Code:
su
cd /system/etc/motorola
cp -R /sdcard/bp_nvm_default bp_nvm_default_nw
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
chmod 755 bp_nvm_default_nw
chown root.root bp_nvm_default_nw
cd bp_nvm_default_nw
chmod 644 *
chown root.root *
cd ..
rm -R bp_nvm_default
mv bp_nvm_default_nw bp_nvm_default
reboot
6]after the reboot, turn off flight mode, let the phone get registered to network and see what happens.. hope this will fix your problem.
it's a bit tricky, i actually had to reboot after mounting system to R/W and giving Superuser permissions and mount again because somehow it didn't work for the first time.. anyway, let me know if anything goes wrong

Thanks, that looks a bit technical but ill give it a go... thanks for info.
Sent from my Transformer TF101 using Tapatalk

Well I gave this a go - and I kept getting permission denied. sounds like problem you had with the system RW refusing to allow a copy.
Anyhow I am hoping I might have fixed it by using this link
http://dext3r.komodin.org/
And there is a radio file you can install under Quick FAQ with different country baseband radio files. Might help someone else ...

it didnt work
well, i did everything as written except i used ES File Manager to mount the /system as R/W and when it came to:
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
it said "cp: can't create symlink '/sdcard....': Operation not permitted" for every file so i just did it manually with ES File Manager... that is only a backup anyway and shouldnt affect anything.
it just doesnt work.
and why cant i just drop the baseband files in there with copy and paste? that didnt work either.
i need baseband files for T-Mobile on the US network for the Flipout. does anyone have any others i could try?
thanks!

[Solved] Is there an advantage with S-Off against mounting to rw and chmod 777?

Hi everybody!
Yesterday i came across S-OFF. From what i was able to find, S-OFF has two main advantages: 1.) Grant full NAND access, so you can write to /boot, /recovery and /system while in full booted mode. And secondly; allows unsigned fastboot flashing.
Now my question regards the first point; write access to all directories during full boot. Yesterday i was in need of write access to /system directory (actually just for creating a symlink). What i did - when got the "write-only permission" prompt at first try - i remounted system partition via terminal and then chmodded system directory:
Code:
/$ su
su
/# grep " /system " /proc/mounts | awk '{system("mount -o rw,remount -t "$3" "$1" "$2)}'
/# chmod -R 777 system
Afterwards i had write permissions to the system directory while i've been in full boot mode.
So my question is: If i'm not interested in unsigned fastboot flashing, nor in locking the bootloader etc, but only in having full access to all system directories - is my approach posted above giving me the same permissions, as S-OFF would do, or would S-OFF gimme any advantages?
My Phone:
*Nexus One on GRK39F Stock ROM,
*rooted (with "Superboot for Nexus One" by Madaco),
*su version 3 (by ChainsDD http://forum.xda-developers.com/showthread.php?t=682828)
Many thanks in advanced!
Cheers, Stephan
Update: @Mod/Admin: Sorry for posting to the wrong section. When i was looking at the section titles before posting this, i read Q&A as FAQ; donno why. I just realized the sticked thread at top of this section, thus recognized i posted to the wrong section. If you'd be so kind to move the thread to the approciated section, rather than closing it, i'd be thankful and promise to take more care about sticking to the board rules in the future. Thanks and kind regards!

I think you are mixing up a few things:
1) Nexus One's come with a partially unlockable bootloader. When you execute the "fastboot oem unlock" command, you are able to flash the /system, /boot, and /recovery partitions with unsigned images via the fastboot command. (So, essentially, you can give yourself root access once you are unlocked, and can write to the /system partition while booted normally.)
2) With S-OFF, you are able to flash ALL of the partitions of the N1 with unsigned images via fastboot, including radio, hboot, sp1custom and splash.
3) If you are rooted, you have write access to the system partition (the same as the above two).
So, to answer your question, having an unlocked bootloader, or S-OFF, or root: they all give you the same ability when it comes to the /system partition.
P.S. If you rooted with "Superboot for Nexus One" by Madaco, then you already unlocked your bootloader...

Hi Efrant!
Thanks for your answer, eventhough i'm even more confused now. ^^ You say
efrant said:
having an unlocked bootloader, or S-OFF, or root: they all give you the same ability when it comes to the /system partition.
Click to expand...
Click to collapse
But "Root" alone, on Android, does not necessarily gives you permissions to write to system directories. As long as a partition is mounted read only, you will - regardless you have userid 0 - get a "read-only file system" error prompt when trying to write to it. Or how comes
Code:
[U][B]whoami: unknown uid 10063 :[/B][/U]
issuing
[B]$ ls /data/app[/B]
returns
[B]opendir failed, Permission denied[/B]
issuing
[B]$ cp -s -P /system/xbin/busybox /system/bin/busybox[/B]
returns
[B]cp -s -P /system/xbin/busybox /system/bin/busybox: Read-only file system[/B]
Code:
[U][B]whoami: unknown uid 0 :[/B][/U]
issuing
[B]$ su
# ls /data/app[/B]
returns directory listing
[B]namespace.apk
...[/B]
issuing
[B]$ su
# cp -s -P /system/xbin/busybox /system/bin/busybox[/B]
returns
[B]cp -s -P /system/xbin/busybox /system/bin/busybox: Read-only file system[/B]
Code:
[U][B]whoami: unknown uid 0 :[/B][/U]
but issuing
[B]$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod -R 777
# cp -s -P /system/xbin/busybox /system/bin/busybox[/B]
will finally create the symlink
For me, that doesn't look like i'm having same access to system directories whether for reading, nor for writing and that - even when logging in as userid 0 ?!
PS: And yes, you're right; i unlocked the bootloader (the very first day i bought my Nexus).

Bexton said:
Hi Efrant!
Thanks for your answer, eventhough i'm even more confused now.
But "Root" alone, on Android, does not necessarily gives you permissions to write to system directories. As long as a partition is mounted read only, you will - regardless you have userid 0 - get a "read-only file system" error prompt when trying to write to it.
Click to expand...
Click to collapse
Yes, but once you have root access, you can mount the system partition as r/w, without any other permissions/etc. All I was saying was that when you have root, you can write to the system. Of course I didn't spell it out step by step, i.e., by mounting the system as r/w, changing directory to the system, etc.
P.S. If you use a root file explorer (like Root Explorer for example, it make the process much easier).

Okay, i got it! Thanks!
So the bottom line: @secuflag has no effect on read and write permissions for the file system.
PS: Sometimes i'm using "root apps" (such as sysroot file explorer eg). But some things can not be done by apps. Plus, i think for a lot of tasks - if you're familar with linux - the command line is also much more comfortable and faster. But thanks for your tip (and help) anyway.

Bexton said:
So the bottom line: @secuflag has no effect on read and write permissions for the file system.
Click to expand...
Click to collapse
Correct (on Nexus 1s)
Sent from my Nexus One using Tapatalk

Here is a new safe way to get S_OFF for your N1. For me the only real advantage was getting rid of the ugly padlock image during boot, and customizing the initial splash image.
http://forum.xda-developers.com/showthread.php?t=1270589

garrettc67 said:
Here is a new safe way to get S_OFF for your N1. For me the only real advantage was getting rid of the ugly padlock image during boot, and customizing the initial splash image.
http://forum.xda-developers.com/showthread.php?t=1270589
Click to expand...
Click to collapse
Keep in mind that what you are linking to is not "true" S-OFF (i.e., setting secu_flag=0, like what you get when using an XTC clip or something similar). The radio is still S-ON.

efrant said:
Keep in mind that what you are linking to is not "true" S-OFF (i.e., setting secu_flag=0, like what you get when using an XTC clip or something similar). The radio is still S-ON.
Click to expand...
Click to collapse
Yes, very true. But for what I wanted it's OK. I'm very lucky that this method turned up on the same day that my new XTC Clip arrived, since it fried itself when I plugged-in the battery and I was about as depressed as a geek could be

[Q] Good for Enterprise GFE hide root detect root 2012

3:36 PM 7/9/2012 None of that worked ... still searching .. I think GFE checks randomly so you have to make very sure you dont reboot before you hide all the apps ?
* disable persistent connections ?
* kill the app before you do anything ?
UPDATE: 12:49 PM 7/6/2012
* sync was ok for about a day then got blocked ...
* I am moving su superuser busybox ls and sqlite files ..will see
* found : http://www.mydroidworld.com/topic/7904-good-for-enterprise-work-around/ https://www.google.com/search?q="good+for+enterprise+"+rooted
plan on trying this:
Code:
# duh you need root ..
su
# remount /system to full read write yours may be different ... type mount|grep '\/system'
mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p15 /system
# finds and add BK to the end of stuff ...
find / -iname "*noshufou*" -exec echo rm '{}' \;
find / -name "su" -exec mv '{}' '{}'BK \;
find / -name "busybox" -exec mv '{}' '{}'BK \;
find / -name "sqlite3" -exec mv '{}' '{}'BK \;
# move xbin folder !
mv /system/xbin /system/xbinBK
# su on
/system/bin/mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p15 /system
/system/xbinBK/busyboxBK cp /system/bin/s /system/bin/su
# su off
/system/bin/mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p15 /system
/system/xbinBK/busyboxBK rm /system/bin/su
some kind of shanigans with registerign for the first time you kill good and then restore from backup ? I dont want to do this:
http://forum.xda-developers.com/showpost.php?p=14547408&postcount=3

Sweet Jesus...what are you asking? If you want to be able to boot multiple roms try boot manager by init2winit. If you want to keep root, use that root keeper app. Otherwise I have no clue what you're asking
Sent from my HTC Glacier using xda premium

any update on this. Cause i'm in the same trouble. My company use Good for Mobile but i need to keep my rotted device! Anybody have a solution?

johnelway said:
any update on this. Cause i'm in the same trouble. My company use Good for Mobile but i need to keep my rotted device! Anybody have a solution?
Click to expand...
Click to collapse
Did you try rootkeeper ? and renamkeing superuser.apk ? I plan to try it next time I wipe but just dont want to mess with it now.

Did not try anything since i dont bave good installed yet.

RootKeeper works. Just shutdown QFE and then re-root. Unroot before you start QFE again.

kevyli85 said:
RootKeeper works. Just shutdown QFE and then re-root. Unroot before you start QFE again.
Click to expand...
Click to collapse
This does not work. Good for Enterprise tries multiple checks to see if you have root. I specifically tried using voodoo ota rootkeeper to unroot then install Good for Enterprise and I still got the out of compliance error resulting in Good wiping the data and locking the app. The only solutions the google searches show to work are to unroot your phone and remove su, etc. At that point, you might as well reflash stock.
It sucks that so many corporate security feams seem to be jumping on the antiroot bandwagon. Also that they opt for Good over, say, Touchdown.
I refuse to change my personal phone back to stock, so I will end up using google calendar sync on my laptol, and my companies OWA access via broweser for email.

OLD

I would just get a cheap phone to use for work and use Google voice to forward all business calls to your primary phone. This seems like the easier softer way
Sent from my HTC Glacier using XDA

I am going to take a break but I updated the main post. I may have rebooted with su in /system/bin/ and I think GFE randomly checks and on boot it always runs ...

at work they took away my GFE because I was rooted so I cant test this, but here is an Idea...
Create a user on the system
make GFE startup with that user
deny that user access to all the binaries used for root
that could possibly work I think

same issue
. Any luck? I am having the same issue. I removed SU and Busy box, as well renamed su and busybox in /bin and /binx. I was able to get in for about 5 min then it booted. I have no idea what it checks for because I even checked myself.with Root Check Pro and it couldn't find a trace

im about to have the same issue here. any help would be greatly appreciated.
Well since im only signing up for corporate email so they will pay my cell phone bill, i dont ACTUALLY want email on my phone, im sure this will be of no use to anyone but heres what i did
nandroided my phone
Reinstalled my current rom
Removed Root
Installed and synced good
Nandroided the unrooted version with good installed
Nandroided back my rooted rom
Now once every 40 days ill nandroid my unrooted rom, sync goodlink to stay active (they disable you after 45 days of non use) then put back my rooted rom.

smgill said:
. Any luck? I am having the same issue. I removed SU and Busy box, as well renamed su and busybox in /bin and /binx. I was able to get in for about 5 min then it booted. I have no idea what it checks for because I even checked myself.with Root Check Pro and it couldn't find a trace
Click to expand...
Click to collapse
did you try :
Code:
find / -iname "*noshufou*" -exec echo rm '{}' \;
find / -name "su" -exec mv '{}' '{}'BK \;
find / -name "busybox" -exec mv '{}' '{}'BK \;
find / -name "sqlite3" -exec mv '{}' '{}'BK \;
I seen post on renameing sqlite3 and removing the noshufou stuff / the su apk I renamed my xbin or sbin folder and it got really pissed .. or it was because I copied a old ANDROID folder to SD card from a different phone

94tbird said:
im about to have the same issue here. any help would be greatly appreciated.
Well since im only signing up for corporate email so they will pay my cell phone bill, i dont ACTUALLY want email on my phone, im sure this will be of no use to anyone but heres what i did
nandroided my phone
Reinstalled my current rom
Removed Root
Installed and synced good
Nandroided the unrooted version with good installed
Nandroided back my rooted rom
Now once every 40 days ill nandroid my unrooted rom, sync goodlink to stay active (they disable you after 45 days of non use) then put back my rooted rom.
Click to expand...
Click to collapse
if you flash a rom then remove root will GOOD be able to detect the rom or unlocked bootloader? or does it work as long as you are not rooted?

debug
I plan to wait some time and resync/ run my script to hide sqlite3 busybox and su / the su folder and run this:
http://code.google.com/p/androguard/#Documentation
maybe I can tell what it is doing with this software.
offtopic but related to reversing :
http://rmccurdy.com/f_news.html#7/19/2012

agalvin13 said:
if you flash a rom then remove root will GOOD be able to detect the rom or unlocked bootloader? or does it work as long as you are not rooted?
Click to expand...
Click to collapse
worked for me. I have an unlocked bootloader, all i did was unisntall root in that rom, then nandrioded the rom. Restored my regular rom and all is well.

Huh, so this why my GOOD app quit working. I had a Nexus S 4G and I started to have problems with GOOD booting me. I got a new SGS3 and rooted it, stock rom, had GOOD device changed with my work and they sent me a new pin. Intalled GOOD from Play and I get the Account Disabled message.
Is there any work around for this yet?

i started a thread. This works for now...
http://forum.xda-developers.com/showpost.php?p=35263292

[Q] i337m Null imei and unknown baseband help

Hello
I have a Galaxy S4 i337m canadian model (firmware i337MVLUFNC1) that has unknown baseband and null imei.
WIfi and blutooth work. it does not recognize sim card.
I have been reading for two weeks about this problem and tried all the methods that i found on google.
I dont have efs backup.
I don't see the nv_data files in efs folder ( file manager =show hidden files enabled)
Any chance I can fix this phone without the original efs folder backup?
Thanks.

Twisteddd said:
Hello
I have a Galaxy S4 i337m canadian model (firmware i337MVLUFNC1) that has unknown baseband and null imei.
WIfi and blutooth work. it does not recognize sim card.
I have been reading for two weeks about this problem and tried all the methods that i found on google.
I dont have efs backup.
I don't see the nv_data files in efs folder ( file manager =show hidden files enabled)
Any chance I can fix this phone without the original efs folder backup?
Thanks.
Click to expand...
Click to collapse
Haven't done it on the gs4 but you'd have to be able to connect it to qpst
I've actually been looking around at this but haven't been able to find much most information is under backup gs3 imei.

Asadullah said:
Haven't done it on the gs4 but you'd have to be able to connect it to qpst
I've actually been looking around at this but haven't been able to find much most information is under backup gs3 imei.
Click to expand...
Click to collapse
Thanks for replay
But that is a way to explore the phone files?
I did a lot of research to find out if the efs file on this model s4 actually contains the .nv_data.bin at all? or it is somewhere else?
Do you know if these files are actually missing from efs folder on i337m? or they are stored somewhere else?
Thanks.

Tried the following method with no luck
http://forum.xda-developers.com/showthread.php?t=1852255

Twisteddd said:
Tried the following method with no luck
http://forum.xda-developers.com/showthread.php?t=1852255
Click to expand...
Click to collapse
Taking the device back to your carrier and letting them factory restore it your best option other then that you are limited without a backup.
You can try this method... if your rooted but there are no guarantees.
Do these commands from ADB from your PC.
adb shell
su
mke2fs -t ext4 /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
On your S4, download the Android Terminal Emulator from the Play Store and enter the following commands.
su
echo -n ON > /efs/FactoryApp/factorymode
sync
exit
exit
Reboot into Recovery, and preform a Factory Reset.

NighthawkXL said:
Taking the device back to your carrier and letting them factory restore it your best option other then that you are limited without a backup.
You can try this method... if your rooted but there are no guarantees.
Do these commands from ADB from your PC.
adb shell
su
mke2fs -t ext4 /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
On your S4, download the Android Terminal Emulator from the Play Store and enter the following commands.
su
echo -n ON > /efs/FactoryApp/factorymode
sync
exit
exit
Reboot into Recovery, and preform a Factory Reset.
Click to expand...
Click to collapse
Tried and gave me the following error in shell
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell
[email protected]:/ $ su
su
root[email protected]:/ # mke2fs -t ext4 /dev/block/mmcblk0p10
mke2fs -t ext4 /dev/block/mmcblk0p10
mke2fs: invalid option -- t
BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_
PERCENT] [-L LABEL] BLOCKDEV [KBYTES]
-b BLK_SIZE Block size, bytes
-F Force
-i RATIO Max number of files is filesystem_size / RATIO
-I BYTES Inode size (min 128)
-L LBL Volume label
-m PERCENT Percent of blocks to reserve for admin
-n Dry run
1|[email protected]:/ #

Twisteddd said:
Thanks for replay
But that is a way to explore the phone files?
Thanks.
Click to expand...
Click to collapse
Thats how people were re-writing / repairing their meids

Asadullah said:
Thats how people were re-writing / repairing their meids
Click to expand...
Click to collapse
I cant find anything for i337m
I don't have service menu either. it says service mode on top of the phone and nothing on the screen.
This phone has to be completely reformated even the system partition. There must be a way of rebuilding the whole phone software.

Twisteddd said:
I cant find anything for i337m
I don't have service menu either. it says service mode on top of the phone and nothing on the screen.
This phone has to be completely reformated even the system partition. There must be a way of rebuilding the whole phone software.
Click to expand...
Click to collapse
Yeah its a rough road ahead of you. I know it can be done because people advertise it on craigslist. But I don't know exactly how.
get on stock nb1 and dial *#0808# change usb settings to dm+modem+adb might get you on the right road.

Looks like they use service box like z3x
I am trying to find alternative ways to do this because where I live, nobody offers this sort of services

Twisteddd said:
Looks like they use service box like z3x
I am trying to find alternative ways to do this because where I live, nobody offers this sort of services
Click to expand...
Click to collapse
There's definitely a different way z3x is such a rip off. I don't know it but as I get time I'm looking around. I'm wondering if you can locate all of the spots that carry the imei if you can change them to something else.

Can some one tell me if the following z3x box sold on ebay enough for repairing baseband on my phone i337m? Or do I need to buy the smart card with it also?
http://m.ebay.ca/itm/151500466184?nav=SEARCH
I know i will need the uart micro usb.
Thanks.

Does null IMEI cause unknown baseband or unknown baseband causes null IMEI?
Which one should be fixed first?
Also the service mode (*#0011#) being blank is it because of the modem is not working?
Thatnks.

When I try qpst in windows 7 to connect to the phone in order to rewrite IMEI;
I can change usb setting to RMNET by dialling *#0808#, the device manager it installs two usb ports under ports. Com6 and com7
RMNET SAMSUNG network driver installs but cant be started. it shows a yellow caution sign on the driver. Restarting windows and phone does not fix it.
When I enter the com ports to qpst configuration, it says active but says no phone.
Any help is appreciated.