Related
I just got a message saying there is an update available. I told it not to do it. I do not want RC30 because it gets rid of root.
However, the other side of me is tempted to see if telnetd and all the other goodies are still there.
I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.
Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?
Woobins said:
I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.
Click to expand...
Click to collapse
If you ever do say yes can you tell us what your software version is?
JesusFreke said:
Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?
Click to expand...
Click to collapse
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
The only file of interest in the /cache directory is named, signed-RC30-from-RC29-fat.1582cace.zip. From this I'm assuming it's going to update my phone to RC30. I've made the file available here in case anyone is curious.
Ah, ok. It looks like that's the same file I just posted a link to then. Thanks
boo
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
It did it.
just as I get home to catch up on the "jailbreak" and start doing it I get an
error while connecting to server, "connection refused"
error while receiving from server null
So I figured I'd check (I neglect my phone when I'm at work, and no, I don't recall accepting the update)
lo and behold:
Build description: kila-user 1.0 TC4-RC30 116143
ota-rel-keys, release-keysBuild ID: TC4-RC30
Build Date: Fri Oct 31 19:00:53 PDT 2008
Build type: user
Phone type: dream
Product brand: tmobile
Build user: android-build
Build host: undroid11.corp.google.com
Linux kernel version: 2.6.25-01843-gfea26b0
[email protected] #6Mon Oct 6 14:13:36 PDT 2008Baseband version: 62.33.20.08H_1.22.12.29
RIL Impl version: HTC-RIL 1.0 (Aug 19 2008,21:32:33)
Default keyboard device: trout-keypad-v3
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
MMTest97 said:
error while connecting to server, "connection refused" error while receiving from server null
Click to expand...
Click to collapse
After starting telentd via pTerminal?
quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
It has more than just that fix. It patches quite a few other packages on the phone... for what purpose? I don't know.
quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
yes
tried pterminal and terminal emulator
netstat shows the ip
but telnet from pc fails to connect failed on port 23 and the port shown on netstat
I also tried the steps koush put up but still fail
granted I'm no linux/unix pro and I just installed cygwin a couple days after the connect bot app came out; so I may be doing something wrong
Does google check in the new change into the source tree before they push a update?
In addition to jailbreak fix there is a battery fix as well and a few others according to androidcommunity.com.
Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.
Woobins said:
Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.
Click to expand...
Click to collapse
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.
JesusFreke said:
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.
Click to expand...
Click to collapse
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows. I guess I'll call tmobile and see what can be done.
edit: I should mention that pressing alt-w to wipe the phone does not work either. It still returns to the error screen. I'm talking to tmobile tech support now and the original tech said that 'they were informed that a small number of users might experience this problem with the update'. I'm on hold waiting to talk to an android tech now. My advice to everyone who's played around with adding any extra files to /etc to hold off on upgrading for now. I'll report back with the results of my call with the android tech.
Now they're saying they would like to exchange the phone. Problem is the g1 isn't in their replacement program yet.
Aaaand they're out of stock so it's going to be at least 2 weeks.
I wish I'd have just kept hitting no.
Disturbing news, especially as I'm wanting to install a modified rc30. What exactly did you change?
I was playing around with trying to get dropbear to work and in the process I created some files in /etc (passwd, shadow, groups, etc). As well as creating a new regular user, I also added a password to the root account and carelessly forgot to remove it before applying the update. I'm only guessing here but I wouldn't be surprised if the new root password is what did it. The system does not have one by default and I wonder if that caused it to hang, waiting for a password to be entered while booting.
On a brighter note, I persisted and was able to get them to send me out a new phone immediatly. This has the added benefit of possibly fixing the loose-screen/creaking problem that I, like many others, am experiencing with the phone.
I'm wondering if I should try manually applying the update from the SD card while I wait for the new phone to see if that solves the problem. I probably should have tried that before calling. I'm hesitant to do that now, however, since if it does fix it, I'm not sure how tmobile would react to me returning a perfectly working phone.
Woobins said:
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows.
Click to expand...
Click to collapse
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...
Dimath said:
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...
Click to expand...
Click to collapse
Unlike the RC29 update, the RC30 update doesn't actually do a complete wipe and restore of the /system folder. It patches a number of files (which will fail if any of them have been modified), and does a recursive chmod on the entire /system directory to clear any suid bits.
I updated to cupcake a little bit ago, and i was using open home as my default home screen. now that im updated i cant go to the home screen because open home force closes no matter what. Is there a way to get into the settings or clear the defaults without first going to the home screen?
Start the phone in safe mode (hold menu upon bootup)
thanks, but now i cant apply updates i think i can figure that one out though, any help would still be appreciated though. error message is e: /sd or whatever cant find update.zip ive followed the same procedures i have for the 50 million other times ive applied themes, but now it isnt working
bizckitmeat said:
thanks, but now i cant apply updates i think i can figure that one out though, any help would still be appreciated though. error message is e: /sd or whatever cant find update.zip ive followed the same procedures i have for the 50 million other times ive applied themes, but now it isnt working
Click to expand...
Click to collapse
make sure the usb cable is not connected to pc
Ok, It was disconnected but still won't work. Same error message.
u can adb uninstall open home, or if u have jf recovery,
home + power
alt + x
mount data
rm -r /data/app/com.betterandroid.openhome.apk
if you have adb setup(which you should if you are modding the phone) type this command
Code:
adb shell am start -a androic.action.intent.MAIN -n com.android.settings.Settings
type it exactly as that and settings will start up for you. had to do this myself when dxtop wouuldn't load
thanks all, i havnt tried most of these because seanos fix worked, but im definetly going to keep the command lines for next time or whatever problem may come up. anyway, now i am just having trouble installing the glossuite theme, keeps saying that the file or directory isnt found. like i said before, i used the same steps i did with jf1.42 and 1.43, but ever since i came up to 1.5 i keep getting that error. (yes, i am using johnowa's glossuite port for jf1.5). any ideas? i couldnt find anything on it in the themes forum
bizckitmeat said:
thanks all, i havnt tried most of these because seanos fix worked, but im definetly going to keep the command lines for next time or whatever problem may come up. anyway, now i am just having trouble installing the glossuite theme, keeps saying that the file or directory isnt found. like i said before, i used the same steps i did with jf1.42 and 1.43, but ever since i came up to 1.5 i keep getting that error. (yes, i am using johnowa's glossuite port for jf1.5). any ideas? i couldnt find anything on it in the themes forum
Click to expand...
Click to collapse
you failed to unmount the card from your computer properly and the file was never written to the card. plug it back in, copy and paste, wait a minute, unmount card, run update
that wasnt it, i redownloaded the file, and tried it again and it worked. earlier when i originally downloaded it, my computer crashed halfway thru the download, and it continued after i started back up, so im assuming something was corrupted in that whole thing. works now tho, i shoulda thought of redownloading it sooner
I have a WiFi only Xoom and it is unlocked/rooted.
I decided to use the hack on the stock browser which enables fulltime desktop mode. I downloaded the apk, renamed it to framework-res.apk and dropped in system/framework and overwrote the existing file. I dl the file from http://forum.androidcentral.com/xoom-rooting-roms-hacks/75616-full-browser.html
I've since discovered that had I read further into the thread, I would have known not to use the file on a WiFi Xoom.
The gist of my problem is I have managed to finally get the Xoom to boot to the homescreen but It's force close city. As soon as I force close one app, others come up (FC) too. The one FC that will not go away is Launcher. it will FC loop forever. The Google/Mic in the top left corner is missing but the bottom bar has the normal icons, but I can't use them because I am stuck in a FC loop. I also get stuck/locked up while rebooting using the power button and volume down and have to use the power/volume up to restart.
I'm wondering if I use the the same one click root file (with kernel) that I still have and root again if this may fix the issue?
Perhaps their may be an easier method if I am only missing the one (framework-res.apk) file I overwrote?
Any help would be most appreciated.
You wanted a new theme right?
http://forum.xda-developers.com/showthread.php?t=1015434
This theme has the framework you are looking for.
Or.. this is the original Wifi Xoom system dump. It may be in there. (I'm at work so i cant check myself)
http://forum.xda-developers.com/showthread.php?t=1011484
Just got home and read your post and do appreciate it.
I was going to begin but just discovered that my Xoom will no longer mount on my pc. Not sure what to do....
yooper said:
I have a WiFi only Xoom and it is unlocked/rooted.
I decided to use the hack on the stock browser which enables fulltime desktop mode. I downloaded the apk, renamed it to framework-res.apk and dropped in system/framework and overwrote the existing file. I dl the file from
I've since discovered that had I read further into the thread, I would have known not to use the file on a WiFi Xoom.
The gist of my problem is I have managed to finally get the Xoom to boot to the homescreen but It's force close city. As soon as I force close one app, others come up (FC) too. The one FC that will not go away is Launcher. it will FC loop forever. The Google/Mic in the top left corner is missing but the bottom bar has the normal icons, but I can't use them because I am stuck in a FC loop. I also get stuck/locked up while rebooting using the power button and volume down and have to use the power/volume up to restart.
I'm wondering if I use the the same one click root file (with kernel) that I still have and root again if this may fix the issue?
Perhaps their may be an easier method if I am only missing the one (framework-res.apk) file I overwrote?
Any help would be most appreciated.
Click to expand...
Click to collapse
I did the same thing my friend, twice in fact. Actually it was likely my post you are referencing above Second time around I still had USB debugging turned on so I didn't have to reload the images.
Do you have the original .apk backed up? If not, i'm attaching it. What I did to fix this was using the adb shell, I remounted the file system as rw and adb pushed the original .apk. You're good to go after that. Hope you have your USB Debugging still turned on
Hope this helps.
yooper said:
Just got home and read your post and do appreciate it.
I was going to begin but just discovered that my Xoom will no longer mount on my pc. Not sure what to do....
Click to expand...
Click to collapse
Are you stuck at the dual core screen? If so can you get into fastboot? You would have to flash the system and boot .img I believe. This is what I had to do when i bricked my wifi without having the USB Debugging turned on. Don't lose hope, you likely do not have a $600 paperweight on your hands.
joen1ce,
I cant thank you enough for your help and time as well as uploading the file for me. Thank you.
I do have dubugging turned on and can boot to the home screen. Actually I have gotten a bit further. I found that if I hit "ok" and force close and quickly continued to hit the time on the lower right corner, I could eventually get into the setting menu. Takes a lot of "tapping" to get it to work, but it did. I am able to get into the reset option but it simply wont work. I push the button and nothing happens. I even tried using bluetooth via my Fascinate and Xoom to see what I could do with the apk you uploaded within the xoom since I could get into the bluetooth downloads, but no worky.
Upon startup, I find that I can get into "Starting fastboot protocol support" as well as well as RSD - Fastboot and NvFlash. Although, I still cant get the Xoom to talk with the computer. I have a Mac with Windows installed and have neither will communicate with the Xoom.
I'm not overly savy with ADB and am not sure if I would know what to do with a boot.img nor where to put it let alone the commands needed to make it work with no communication between devices.
I do have SDK/ADB and the Fastboot (.exe) both on the Mac and Windows side.
I can do an exchange on the Xoom but would rather fix it myself and consider it a valuable learning experience, but I'm at my wit's end.
yooper said:
joen1ce,
I cant thank you enough for your help and time as well as uploading the file for me. Thank you.
I do have dubugging turned on and can boot to the home screen. Actually I have gotten a bit further. I found that if I hit "ok" and force close and quickly continued to hit the time on the lower right corner, I could eventually get into the setting menu. Takes a lot of "tapping" to get it to work, but it did. I am able to get into the reset option but it simply wont work. I push the button and nothing happens. I even tried using bluetooth via my Fascinate and Xoom to see what I could do with the apk you uploaded within the xoom since I could get into the bluetooth downloads, but no worky.
Upon startup, I find that I can get into "Starting fastboot protocol support" as well as well as RSD - Fastboot and NvFlash. Although, I still cant get the Xoom to talk with the computer. I have a Mac with Windows installed and have neither will communicate with the Xoom.
I'm not overly savy with ADB and am not sure if I would know what to do with a boot.img nor where to put it let alone the commands needed to make it work with no communication between devices.
I do have SDK/ADB and the Fastboot (.exe) both on the Mac and Windows side.
I can do an exchange on the Xoom but would rather fix it myself and consider it a valuable learning experience, but I'm at my wit's end.
Click to expand...
Click to collapse
Copy the apk file I uploaded to the directory where you have the adb files. Go to the command line and switch to that same directory.
Let the device reboot to the point where you get those damn force close messages.
at the command line type:
adb devices
you should see your device listed there. If so, do the following:
adb shell
mount
You should see all the mounts on your device listed. Copy the path for system you will need it for this next part. It may be exactly like mine. So next you will type in:
mount -o rw,remount /dev/block/platform/sdhci-tegra.3/by-name/system /system
the "/dev/block/platform/sdhci-tegra.3/by-name/system" above is the true path
to my /system mount. Use whatever the path yours is mounted to from the previous command.
Next hit ctrl + c to exit out of the shell and at the command line type this:
adb push framework-res.apk /system/framework/framework-res.apk
If the above was successful you should be able to reboot the device and be back in business.
You fixed it!!
joen1ce, I can't begin to thank you enough for your help Took me a couple tries as well as rebooting the Xoom for it to take but by god it worked!!!
I'm sure your post will help others out out in future too. As the WiFi Xoom becomes more popular, I'm sure this will happen again to more people looking to modify their Xoom stock browser to desktop mode.
I'm thinking their should be a sticky on bricking with possible fixes and your post should be noted for sure.
People like you really help make this site the cat's a**.
Thanks again,
Mark
yooper said:
joen1ce, I can't begin to thank you enough for your help Took me a couple tries as well as rebooting the Xoom for it to take but by god it worked!!!
I'm sure your post will help others out out in future too. As the WiFi Xoom becomes more popular, I'm sure this will happen again to more people looking to modify their Xoom stock browser to desktop mode.
I'm thinking their should be a sticky on bricking with possible fixes and your post should be noted for sure.
People like you really help make this site the cat's a**.
Thanks again,
Mark
Click to expand...
Click to collapse
No problem, glad I could help. I bricked my Xoom basically within an hour of buying it and I know how it feels, especially when trying to be moral and not return it! Had it about a week now and it's my first Android device so I'm new to these forums. But the helpfulness of the community is very impressive indeed.
Regards,
Joe
joen1ce said:
Are you stuck at the dual core screen? If so can you get into fastboot? You would have to flash the system and boot .img I believe. This is what I had to do when i bricked my wifi without having the USB Debugging turned on. Don't lose hope, you likely do not have a $600 paperweight on your hands.
Click to expand...
Click to collapse
joen1ce. Could you please help? I am stuck at the Dual Core Screen and cannot get my computer to recognize my device in adb. I am trying to return to stock 3.2.1.
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Morecrabs said:
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Click to expand...
Click to collapse
1. No
2. Yes
You need to be on stock ics firmware for the NV edit to succeed and stick.
Use Android 4.0.4 Blur_Version.77.8.14.XT897.Sprint.en.US - http://sbf.droid-developers.org/phone.php?device=3
If you're downgrading from jellybean, you have to remove the line with flash gpt_main0.bin from the xml file, otherwise the flashing via rsdlite will fail.
Code:
[STRIKE]<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="6C05E70F1DCC59AD92B0BBEC4E6100ED" />[/STRIKE]
The firmware thread is here: http://forum.xda-developers.com/showthread.php?t=2095536
Then you can follow this (RadioComm):
http://forum.xda-developers.com/showthread.php?t=2166542
or this (CDMA WS) guide:
http://forum.xda-developers.com/showthread.php?t=2386871
After it's done, you should flash the stock Android 4.1.2 via rsdlite, then install CM10.2 (or any other custom ROM) again.
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Morecrabs said:
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Click to expand...
Click to collapse
That development ID is simply for identifying your device under debugging circumstances like ADB, every device has them. Also, flashing another ROM changes this value.
Sent from Google Nexus 4 @ CM11
ok so that was a dumb decision to come to, but its not something id ever seen on any of my other android devices, Droid 1,2,4 samsung captivate glide, so i figured it was related to the developer Models
Do I need to run my copy of radio Comm on a 32 bit machine to accomplish this hacking?
my 64 bit machines seem to have driver related issues with the software
was wondering if anyone could help me setup the drivers, I keep getting errors with Radio comm and cdma workshop, and it all boils down to driver issues, with cdma workshop i cant get the QC port setup because IM missing a driver, and with radio comm, I cant get it to communicate properly with the phone once i boot into fastboot any help suggestions? ive installed the moto drivers and setup on a PC with a 32 bit version of win7 starter to allow radio comm to setup properly
In radio comm it will ID the phone as xt897 and i can get software version if its booted into OS, but it will do nothing else
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http://bork.cs.fau.de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
Code:
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https://github.com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
EDIT2: This is now included as "unlock-us-gsm" in CM12.0 and up on XT897, XT907 and XT926. To use it run "unlock-us-gsm" in a root shell:
Code:
[email protected]_c:/ # unlock-us-gsm
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Reading value of NV-item 8322...
GSM locked in the US: 1
Setting value of NV-item 8322 to 0...
Reading value of NV-item 8322...
GSM locked in the US: 0
Setting logging_mode to usb...
Regards,
Michael
stargo said:
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer
Click to expand...
Click to collapse
Excellent! I picked a good day to try to figure out how to do this, I was making notes of all the various steps (install ics on phone, use radiocomm on pc, install jb on phone, then cm on phone) when I got to this post and realized I won't need to do any of that, thanks much!
Terminal Emulator Question
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http //bork cs fau de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
[CODE
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
[/CODE]
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https //github com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
Regards,
Michael
Click to expand...
Click to collapse
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
DroidRazrMv said:
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
Click to expand...
Click to collapse
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
arrrghhh said:
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
Click to expand...
Click to collapse
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
DroidRazrMv said:
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
Click to expand...
Click to collapse
Still confused as to where you're having issues - we are both talking about the same post. If you look, kabaldan's post redirects to the one I am referencing....
So once these steps are used to unlock the phone, which carriers can be used and how does flashing of carrier info occur?
Just want to say thanks again Michael. I just got my new Photon Q back from having sim card slot installed, ran your program and it worked perfectly on 21OCT2014 CM nightly.
I did also change a couple settings in the phone menu too, cuz I put an AT&T sim card in it, but sprint kept calling me to activate. Seems to be working well now, but not sure I understand everything, does this seem right - in regular CM11 settings menu under Mobile network settings, I set Preferred network type to "GSM/WCDMA Auto".
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
Click to expand...
Click to collapse
I've recently started having problems after changing ROMs a couple of times.
I tried installing a new Rom (CM12.1) but it is still happening and I've installed a new GAPPS each time too so I guess the problem runs deeper than that.
The ROM runs fine for a bit but then all of a sudden I get a force close which constantly keeps coming up no matter how many times I press 'Ok'.
I've had a few different processes stop but the last two that spring to mind are 'process.android.phone', 'Swiftkey' and 'Google Play'.
I have to reboot but then end up stuck at the splash screen at boot. I then have to Power+Vol Down to go into recovery and then reboot system from there. It then runs through the App optimisation screen brfore restarting.
I've never touched kernels since I've been changing ROMs so whether thats the issue.
Any help with this would be great as otherwise this is the best Rom Ive used.
Thanks in advance
A logcat showing traces of these force closes would help
Aquous said:
A logcat showing traces of these force closes would help
Click to expand...
Click to collapse
I didnt do one on account of me not having a clue what the hell one was
Luckily my friend Google does know what the hell one was.
I've attached a couple of log files created around the time of the unpleasantries which hopefully might shed some light.
This one attached might be better, this was taken after I sorted out my Root Access again so might have more info.
Regards
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Aquous said:
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Click to expand...
Click to collapse
Hi, thanks for your reply. I havent been near any other custom themes. I've had this problem over a couple of Roms too.
I've tried to generate a catlog to get some error messages around the time its happening but I keep getting constant force close boxes which stop me doing anything (for a couple of different processes). The only way to stop them is to reboot but then the logs stop and reset when it boots so I cant get the info.
I've had to reboot about three times today and each time it has had to optimize the apps for some reason.
I've tried to get a catlog through ADB but I cant run the Android SDK as I need to install the JDK which keeps giving me 'Error 1500' on the install (even though I am most definately not already trying to install it).
Thanks for your help so far though and taking the time to read through the previous log.
Every solution I try just seems to create more problems
I've managed to attach a text file of all the error files its had since it started up (they are all in the space of about 10mins)
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Aquous said:
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Click to expand...
Click to collapse
Well I'm assuming their force closes. I get a white box popping up that says 'unfortunately XXXXX has closed' and when I click 'ok' the box goes away but either comes straight back or another similar one pops up. Its Trebuchet quite a lot.
I can't do anything then, if I try to get to LogCat that closes too and I can't really do anything until I reboot.
Its happened over 3 different Roms so dont think theres much the Rom compiler (is that what they're called, lol) can do.
I'm am probably going to have to see if I can get a Log through ADB, if I can remember how to use it, when I have time.
Cheers
I've managed to connect the tablet through ADB and managed to get some errors taken at the time I started getting all the 'Unfortunately XXXXX has closed [ok]' boxes kept coming up.
All the error messages attached came up in the space of a few seconds.
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Aquous said:
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Click to expand...
Click to collapse
Hi,
Thanks for looking through them errors.
To be honest I haven't heard of fsck. Is it something I can pick up fairly simply or am I more likely to do more damage? I've done a few searches and it looks a bit difficult and couldn't really find any threads that sounded similar to what I might need.
Thanks again
Update : I've gone into recovery and found files in /system/bin called fsck.exfat and fsck.f2fs is it a case of running a command through terminal command in recovery from this directory?
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Aquous said:
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Click to expand...
Click to collapse
Hi,
No worries mate, I wasn't sure if what I said didn't make sense thats why there were no replies
The problem seems to be a lot better now but I've still had it a couple of times over the last two days.
I've tried to run the command above but with no joy. I'm still only learning the basics of ADB so still having some trouble.
I wasn't sure exactly where to run the commands from through the SDK so just went to the Terminal Command in Recovery and after navigating to the system/bin folder tried that command but it came up with the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS is in use
esfsck: cannot continue, aborting
I apologise if some of what I am doing seems nonsense but I am trying to pick up what I can by myself from various sketchy threads to avoid being a 'tell me what to do cos I can't be bothered looking myself' person. I dont know if this is doing more harm then good
Thanks again in advance for your help.
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Aquous said:
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Click to expand...
Click to collapse
For some reason I cannot get my PC to pickup the tablet in a command window when in TWRP so I was unable to run through ADB. 'ADB Devices just did not show anything.
In the end I did it all on my tablet in TWRP through the 'Command Terminal'. I navigated to the necessary folder (the one with fsck.exfat and fsck.f2fs in - /system/bin) through the Command Terminal and after typing the command in I got the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS clean, 9086/791520 files, 694414/3160055 blocks
Is that good?
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Aquous said:
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Click to expand...
Click to collapse
Hi, yea sure. I could use a bit of guidance with exactly how to do that though. I take it that is something I would have to run through ADB from my PC before I reset my tablet? Step by step instructions would be appreciated a lot (as has your extensive help already, creep creep ).
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Aquous said:
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Click to expand...
Click to collapse
Right, first thing this morning I had some errors, so I've managed to paste the results of a dmesg into the log file attached.
Cheers!
Hmmmm, now this is interesting. It looks like random services are failing to load - they are immediately exiting after being restarted. This is basically the same problem as with your apps force closing - something at the lower layers is causing everything to crash immediately upon launch.
Yet you're able to run basic programs (e.g. adb, dmesg) just fine, meaning that it's not likely to be a hardware issue.
What happens if in adb shell you run su and then 'stop' followed by 'start'? What should happen: when you run 'stop', the whole system freezes, and when you run 'start', you see your boot logo and android starts booting up again. Is this indeed what happens in this case, or do you get a bootloop? If so, post another logcat when you're stuck in the loop; you can get out of it by simply entering 'reboot' in your still-open adb shell.