Related
This has been observed in at least one post, buried deep within another thread, but I thought it is important enough to have its own thread.
The latest JH7 OTA update seems to remove the file containing the unlock code for the Captivate. I unlocked my phone a couple of weeks ago, and after receiving the upgrade I verified that the phone is still unlocked. However, the SGS Unlock app no longer finds the code. Presumably, other PC/Mac-basede unlock techniques will be affected, as they look for the unlock code in the same file.
Anybody else can confirm this? In a word (two, really), what now? I was about to buy another Captivate for my wife, but the only reason she was willing to get it instead of the iPhone 4 was the possibility to unlock it (we travel to Europe twice a year).
If I manually peek at the bml3 or nv_data files, I still see my unlock code after JH7. I haven't used any apps to unlock, but it sounds like they just need an update if they are failing.
Well, if you bought the phone today, it wouldn't have the JH7 update, I would presume. So, you can run the unlocker to get the code. It sounds like, though I cannot confirm because the update failed on my phone, that it just deletes a file with a number in it. If that's the case, it shouldn't be able to undo any existing unlocks, and there's no time limit once you have the code.
Then you better buy one now and extract the unlock code before you upgrade. It typically takes AT&T a few months to sell phones with new firmware.
Even though new firm ware makes current unlock method useless, it won't chang your unlock code.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok, so maybe the SGS unlock app fails but could be fixed in the future, or perhaps one of the other methods still works...
Sent from my SAMSUNG-SGH-I897 using XDA App
One question: are you rooted? I tried copying the nv_... file to the sd card using adb, but got a "permission denied" error.
Sent from my SAMSUNG-SGH-I897 using XDA App
Yup. That may be what is breaking the apps... I don't remember it needing it before to access /efs/nv_data.bin. I can read it after su though.
edit: If you want to try and get it manually, the following grep works for me, but I'm not exactly sure if it work on others...
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
You should see 2 identical sets of numbers.
aloant said:
Yup. That may be what is breaking the apps... I don't remember it needing it before to access /efs/nv_data.bin. I can read it after su though.
edit: If you want to try and get it manually, the following grep works for me, but I'm not exactly sure if it work on others...
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
You should see 2 identical sets of numbers.
Click to expand...
Click to collapse
OK, so this is very good news.
To clarify (here's the noob asking...): rooting does *not* affect your ability to get the update, right? If all rooting does is install su & friends (and uninstall removes them), there should be no adverse consequences at all, especially if you unroot prior to getting the update. I'm just worried about the reports of updates failing (everything went smoothly for me, but I'm 100% stock and not rooted). Thanks!
MarcianoS said:
To clarify (here's the noob asking...): rooting does *not* affect your ability to get the update, right? If all rooting does is install su & friends (and uninstall removes them), there should be no adverse consequences at all, especially if you unroot prior to getting the update. I'm just worried about the reports of updates failing (everything went smoothly for me, but I'm 100% stock and not rooted). Thanks!
Click to expand...
Click to collapse
I am rooted and the install went fine for me. I had not done any of the lag fixes, overclocking, or flashing custom ROMs though.
Same. Rooted before the update. It even stayed rooted after the update.
If the grep above doesn't work btw, look here for how to manually copy the files to your computer, and view the code using a hex editor: http://forum.xda-developers.com/showthread.php?t=761045 . Just remember you need to use "su" first now. Or just wait... One of the devs will probably update their app soon enough.
Ok, thanks! This helps a lot.
Sent from my SAMSUNG-SGH-I897 using XDA App
WTF!!
I reflash back to stock rom JF6 from JH7.
it seems like flashing back to stock rom JF6 wont restore the unlock code!
aloant said:
If I manually peek at the bml3 or nv_data files, I still see my unlock code after JH7. I haven't used any apps to unlock, but it sounds like they just need an update if they are failing.
Click to expand...
Click to collapse
how do you manually peek at bml3 or nv_data file?
netnerd said:
how do you manually peek at bml3 or nv_data file?
Click to expand...
Click to collapse
Posted it in the previous page. The files are still there for me in JH7, it's just that nv_data requires root access now.
aloant said:
Posted it in the previous page. The files are still there for me in JH7, it's just that nv_data requires root access now.
Click to expand...
Click to collapse
thanks! manually peeked, unlock code still there!
aloant said:
Yup. That may be what is breaking the apps... I don't remember it needing it before to access /efs/nv_data.bin. I can read it after su though.
edit: If you want to try and get it manually, the following grep works for me, but I'm not exactly sure if it work on others...
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
You should see 2 identical sets of numbers.
Click to expand...
Click to collapse
Ok...total noob here...how and where do I actually do this(on the phone or in some program on the pc)? I too lost ability to retrieve code after JH7..... on a good note...I did get my 3 button recovery that was missing....
Hy, Can you explain to my how you did the Update? I have mine unlocked and I keep getting a mesage "can´t conect to at&t servers".
I had mine rooted but I unrooted it to intall the update
I had mine lag fixed but I unfiexed it to intall the update
I removed all at&t blowatware.
Please Help.
robertoaste said:
Hy, Can you explain to my how you did the Update? I have mine unlocked and I keep getting a mesage "can´t conect to at&t servers".
I had mine rooted but I unrooted it to intall the update
I had mine lag fixed but I unfiexed it to intall the update
I removed all at&t blowatware.
Please Help.
Click to expand...
Click to collapse
It could just that the servers are currently overloaded... take a look at the thread on successful updates; although there are still only a few reports, phones that did not have a lagfix at the time of the update did OK, and rooting does not seem to matter. In any case, it's not like your update failed: you haven't even downloaded it yet.
netnerd said:
WTF!!
I reflash back to stock rom JF6 from JH7.
it seems like flashing back to stock rom JF6 wont restore the unlock code!
Click to expand...
Click to collapse
That makes sense, because the JH7 update changed the *permissions* of the nv_data file. So, even if you reflash the stock ROM, the permissions on that file stay the same.
BTW, I suppose this means that one way to fix this would be to create a very simple update.zip that changes the permissions on that particular file. Although, if you go down that route, you might as well root your phone, I guess!
aloant said:
Yup. That may be what is breaking the apps... I don't remember it needing it before to access /efs/nv_data.bin. I can read it after su though.
edit: If you want to try and get it manually, the following grep works for me, but I'm not exactly sure if it work on others...
su
busybox grep -E "^[0-9]{8}$" /efs/nv_data.bin
You should see 2 identical sets of numbers.
Click to expand...
Click to collapse
Thank you, thank you, thank you aloant. My Captivate is now 'reunlocked'
.... or maybe download link from google?
Hello all,
Wondering if someone could try this since I already upgraded won't work but when i got the update on my phone I was able to go to the cache folder and extract from fumo file the following zip that is on mediafire.
Called OTApkg.zip like the mt3g update file.
Should be the current update.
Anyone on the original firmware should be able to flash this from recovery and be up and running with new firmware
Let us know if it worked.
Just rename update.zip and put to root of memory card
boot with vol down and power.
down and select recover
vol up and power to get options
select update from update.zip and should run.
Download:
http://www.mediafire.com/?jm90w7hr922bpd4
You didn't get a chance to test this at all? Can anyone test this and tell me if it works. Before even thinking about rooting I always like to have a set of file to recover with. G1, original mytouch, and slide i all have had way to undo before I rooted.
Didn't work for me. When I tried it I got an error that said
Code:
-- Invalid operation --
On a side note, when I reboot into recovery I get this
Code:
E:Can't open /cache/recovery/command
Anyone else? Is this correct?
Reviewing the code does look like the right file but may not be able to be flashed manually.
First line in update script is mount ( "MTD" , "system" , "/system" )
Looks like boots is a special "fota" mode that will allow modification and this update run like that won't initialize it.
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
travisjames said:
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
Click to expand...
Click to collapse
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Beast84 said:
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Click to expand...
Click to collapse
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
travisjames said:
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
Click to expand...
Click to collapse
Great that means theres no problem with my phone. I feel so much better now
Beast84 said:
Great that means theres no problem with my phone. I feel so much better now
Click to expand...
Click to collapse
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
travisjames said:
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
Click to expand...
Click to collapse
Very true. In the Vibrant section, those guys were able to make update.zip's that were flashable through the stock recovery. Maybe someone can do that for us with this update. I have no dev experience at all but I am willing to test whatever comes up.
It was weird because when I looked at it
It was in the cache directory but not directly
in the cache directory was a file fumo which on browsing just looked like a file on the phone using sufbs.
But when I copied it to the device using the app that is when fumo turned into a folder and opened and saw that file.
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
bobsbbq said:
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
Click to expand...
Click to collapse
No, there isn't a way for T-Mo to push the OTA to you.
Did the rep say anything about the other update?
If you bought the phone full price instead of on contract be sure to check online and change the phone Tmobile has for you to a Mytouch 4g I think that could have something to do with it. I had mine listed as a Mytouch 3G still and I went and changed it and hope it'll make a difference.
Pretty sure that just changing the phone on my tmo wont change. Only thing that i can think of minus something being changed since i got it off the device vs a direct download if someone can get the link or call tmo to check on thier plans if past thier time frame they may be able to do something
Just hopefully someone could get the google link for it instead.
Sent from my HTC Vision using XDA App
I called T-Mobile today about the OTA and they said that it did matter that my plan wasn't set a mytouch package. They told me the OTA should have gone out after my first phone call. Sounds like a bunch of bull**** to me, just figured I'd fill in anyone who was interested. They told me I should have it within 48 hours. *crosses fingers*
*edit* my friend works at T-mobile, she just received the phone herself and after your phone is set as a Mytouch4G, use *#*#checkin#*#* should help start the process, now were both waiting...
I've been waiting since Sunday. Hopefully has nothing to do with having debugging enabled.
Been leaving the phone connected most of the time running
Code:
adb logcat | findstr clients.google
to try and snag the link for the update.
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
johnowa636 said:
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
Click to expand...
Click to collapse
I've been messing with this. It seems you can put in a filter (I put clients.google) but it doesn't matter if you set it to save to your card periodically it saves the entire logs... but you can open those on a pc later and search them or if you're a linux type you can cat file | grep "clients.google"
I thought I might as well start this thread. The only root method I currently know of is http://www.androidpolice.com/2011/04/30/instructions-how-to-root-the-verizon-samsung-droid-charge/
I have read that z4root works as well, can anyone confirm this? I will be receiving my DROID Charge tomorrow and will try z4root.
jism31 said:
I thought I might as well start this thread. The only root method I currently know of is http://www.androidpolice.com/2011/04/30/instructions-how-to-root-the-verizon-samsung-droid-charge/
I have read that z4root works as well, can anyone confirm this? I will be receiving my DROID Charge tomorrow and will try z4root.
Click to expand...
Click to collapse
use adb...z4root is lame
I am not too familiar with adb, how would i go about using it?
jism31 said:
I am not too familiar with adb, how would i go about using it?
Click to expand...
Click to collapse
install the android sdk
jism31 said:
I am not too familiar with adb, how would i go about using it?
Click to expand...
Click to collapse
Try this
http://lmgtfy.com/?q=how+do+i+use+adb
nitsuj17 said:
use adb...z4root is lame
Click to expand...
Click to collapse
Root however you want to, keep us updated on how it works out.
The method in the first post works well. In step 5 after adb shell you will need to input chmod 755 /data/local/GingerBreak or you will get a permission denied error when trying to run gingerbreak.
Just got my Charge from work finally, will root today and keep you guys posted. I will try z4root first to see if it can be done easily.
jism31 said:
Just got my Charge from work finally, will root today and keep you guys posted. I will try z4root first to see if it can be done easily.
Click to expand...
Click to collapse
So what happened ?
Sent from my SCH-I500 using Tapatalk
jism31 said:
Just got my Charge from work finally, will root today and keep you guys posted. I will try z4root first to see if it can be done easily.
Click to expand...
Click to collapse
What does that mean "just got from work"? Were you able to purchase one? I backed down on getting one from Best Buy at the last minute on the Sunday after the missed launch (they were willing to sell it to me), but when I tried to get one the other day, no sale!
Sorry for the delay, z4root does not work nor does superoneclick method. You need to use adb and add in step 5 that was previously posted. Worked for me. Also to clarify i work for verizon and I was able to get one early, I will not be paying for it until I get back from vacation so we do not get flagged in our commission system.
The adb method using Gingerbreak is broken by the OTA update that just came out as some of us more overeager updaters have learned. Here's hoping for a revised method soon!
I figured that ota did more then something usless. I will not be taking it, my phone has been running great rooted for almost 2 weeks.
Anyone know what I have to do to get rid of the ota notification? I'm rooted but the constant asking me to update now or later is annoying.
Well i did the OTA update because I did what I needed with the root. I will try to get a way to re root and get back to you guys.
when will the ota updated charge get a root?
I was screwed from the start. the guy at verizon updated my phone afer he activated in the back.
I ended up taking the ota after I had frozen all the bloat. I'm guessing the OTA fixed some serious battery issues because this morning at work I went from 100% to 60% in one hour with light usage. I don't know if this was a software issue or because my office is fringe 4g... my phone constantly goes back and forth from 3 to 4.
The rest of the day though after I let the ota install, battery life was much much better.
Found this over Droidpolice forum
At step 5 after adb shell you will need to input chmod 755 /data/local/GingerBreak before doing /data/local/GingerBreak this enables the permissions
Has anyone tries this?
Poloasis said:
Found this over Droidpolice forum
At step 5 after adb shell you will need to input chmod 755 /data/local/GingerBreak before doing /data/local/GingerBreak this enables the permissions
Has anyone tries this?
Click to expand...
Click to collapse
Tried and failed with ED02. This was mentioned a few replies up.
Any chance we can get the OP edited?
If you are rooted then go to the build.prop and change all instances of E1 to E2 that should get rid of the notifications as you are tricking the updater into thinking its updated. If you already on E2 you are SOL until a new root method is posted. I got my charge yesterday and Verizon dude updated the phone before I had a chance to tell him not to. I figure I will wait. All I want is root for titanium backup. Ive been happy with this phone.
Would someone mind posting the original Droid Charge ED1 build.prop file? I attempted to modify mine to work with Netflix, but all I did was break my market. Aaaand of course I didn't keep a backup.
Here's mine:
filesonic.com/file/1039316854
I've already changed ED1 to ED2 to prevent the update.
Thanks very much! Worked perfectly.
Thank you so much, this helped me out after i changed the screen density with jrummy root tools. I had to find a build prop and it happened to be one with the software bypass. Kudos on the build prop. very awesome since recovery through nandroid isnt available yet i am just waiting on a rom if not i will try making one myself (thought i dont have time so itd be purely for personal use i guess till the pros get on it lol)
how do u change ed1 to ed2???i tried but it wont save.
brandonaspencer said:
how do u change ed1 to ed2???i tried but it wont save.
Click to expand...
Click to collapse
You need to mount /system as read-write. Also, why don't you just update to ED2, at this point, there is no reason not to.
Does anyone have a stock build.prop for the VZW LTE Galaxy Note 10.1?
I modified mine and didn't make a backup and then found out the OTA update won't work because my build.prop is modified. After looking at the updater script, I think either a build.prop from before the upgrade or after the upgrade will satisfy the requirements.
Alternatively if someone knows if factory reset will restore it, that will be fine too. I don't think it does since I have seen so many stories of people bricking their device by modifying the build.prop and then a factory reset doesn't fix it.
Confirmed factory reset does not restore it.
Here ya go.
Also, rename sdm.apk so ya dont get those ota's
*Madmoose* said:
Here ya go.
Also, rename sdm.apk so ya dont get those ota's
Click to expand...
Click to collapse
Unfortunately that didn't work. I wonder if even the last modified date has to match.
I am actually trying to get the OTA to work. I have OTA Root Keeper, so I am not worried about OTA taking away root.
I'm honestly not sure that I even care if I can't get root back. The only thing I use root for now is modifying DNS to use Fool DNS to block ads, but that interferes with Hulu sometimes. Such a bummer too. It's nice watching the screen blink a couple times and then voila, commercial break is over.
Samsung gave me instructions to flash with OEM firmware, so I am going to try that.
Thanks for posting that up so quick though!