Database Info

adb and fastboot for PowerPC Macs

I managed to successfully compile the adb and fastboot binaries for PowerPC by hacking the Android SDK a little bit. If you use a PowerPC Mac and would like to use it for debugging/etc Android device, you may find these interesting. (The apps were compiled under Leopard, I have no clue if they will also run on Tiger or not)
Word of warning: I don't take any responsibility if any of these apps kill your phone or the neighbors. You have been warned.
Known bugs: serial numbers are shown incorrectly in both apps, also you should run them from iTerm as they messed up the standard Terminal.app for me once.
Tested and working features (on a PowerBook 12" 1.5Ghz and an iBook G4):
adb:
shell
logcat
reboot
bugreport
push
pull
fastboot:
reboot
reboot-bootloader
flash (radio|hboot)
erase (system|boot)
acp:
Didn't test this one, I never used it, but seems like working.
Since I don't have any other machine ATM, I couldn't test the flash function yet, I'm planning to do that soon. Anybody curious enough to test, please reply with your results, so I can update the list. As always, donations are welcome

Just tested on my ibook g4!
It works fine! Thank You very much!
EDIT:
I used it to flash the new bootloader (1.33.013d) and the new radio (2.22.28.25_S) via fastboot.
Commands tested:
fastboot flash radio RADIO-2.22.28.25.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
fastboot erase system -w
fastboot erase boot
fastboot reboot

Glad to hear that, I'll update the first post in a few minutes. Can you confirm the bug with the serial numbers or was it working for you?

Z0l said:
Glad to hear that, I'll update the first post in a few minutes. Can you confirm the bug with the serial numbers or was it working for you?
Click to expand...
Click to collapse
The serial number isn't shown but appear "####"
iBook:android_ppc michele$ ./adb devices
List of devices attached
#### device
iBook:android_ppc michele$
Click to expand...
Click to collapse

@Z0l, could you post a patch for the source?
I tried briefly to do exactly what you've managed to do, but no point in reinventing the wheel

Actually there is no patch What you should do is to checkout the froyo sdk with repo (this is important, because gingerbread requires java6, which is a bit problematic on ppc), copy the build/core/combo/HOST_darwin-x86.mk to HOST_darwin-ppc.mk, then issue the "make adb" and "make fastboot" from the top of the source. I think I received some warnings, but at the end the binaries were at out/host/darwin-ppc/bin. So, the actual commands are:
repo init -u git://git.android-x86.org/manifest.git -b froyo
repo sync
cp build/core/combo/HOST_darwin-x86.mk build/core/combo/HOST_darwin-ppc.mk
make adb
make fastboot
Click to expand...
Click to collapse
Hope that helps. Also, make sure you do the compile on a case-sensitive filesystem (I created a case-sensitive dmg for that)

Does this still work with Gingerbread and ICS devices like the Nexus S and the Galaxy Nexus?
Thanks for answering in advance.
land.apfel

I'd say yes because I see no reason for them not to work. Although both adb and fastboot received updates, the fundamentals are the same.

OK, so I'll try them but I won't be able to use the backup feature, will I?
Sent from my Galaxy Nexus using XDA

land.apfel said:
OK, so I'll try them but I won't be able to use the backup feature, will I?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Could you elaborate a bit what you mean under backup? All the adb and fastboot commands worked when I tested them.

With backup I mean "$ ./adb backup".
Sent from my Galaxy Nexus using XDA

These binaries were compiled long before ICS existed (adb backup is available since ICS), so I don't think it'll work. You can try compiling a new version yourself, unfortunately I no longer have access to a PPC dev environment.

That's why I've asked.
Unfortunately I'm too dumb to compile it by myself
Sent from my Galaxy Nexus using XDA

iBook G3
Hi there,
Sorry to bump such an old topic! But I think I have a (very?????) special case. Is it possible to compile the newer ICS Binaries..... for iBook G3 on 10.4.11?
I tried running these and I got the dreaded "Incompatible CPU subtype" so I assume they're for G4 and up. Is there a way this could be changed?

blackthund3r said:
Hi there,
Sorry to bump such an old topic! But I think I have a (very?????) special case. Is it possible to compile the newer ICS Binaries..... for iBook G3 on 10.4.11?
I tried running these and I got the dreaded "Incompatible CPU subtype" so I assume they're for G4 and up. Is there a way this could be changed?
Click to expand...
Click to collapse
Sorry for the late reply, you cannot compile anything newer than GB on powerpc. Even GB needed the above trick, but since ICS requires a Java that never existed for powerpc, I think its impossible.
Sent from my Galaxy Nexus using xda app-developers app

Z0l said:
Sorry for the late reply, you cannot compile anything newer than GB on powerpc. Even GB needed the above trick, but since ICS requires a Java that never existed for powerpc, I think its impossible.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Haha ok fair enough the hardware is kinda old anyway. ;p
It's because when parents remove the Windows laptop I only have my iBook or athlon server left xD

[DEV] Native Ubuntu !!

Please go to Lilsteffy's threat !!! ,DEV here has stopt !!!
Admin close threat please

Working
Touchscreen
USB Host
Audio Out (Speakers not working)
Wifi - Requires Terminal / Script
Code:
For WPA2 edit /etc/wpa_supplicant/wpa_supplicant.conf
then run
sudo chmod +x /etc/init.d/start-networking
sudo update-rc.d start-networking defaults 99 05
Known Issues
Wifi GUI not working
Bluetooth not working
Speakers not working(Output Works)
Touchpad not working
Standby issues with Lid CLosed - Investigating
Resize Loop File <--
Keep in mind 4G fat32 limit for FAT32 !!
To Do
Boot To android -> looking into kexec.
trying to mod touchpad driver.
Sources
Kernal Source
Mega Source
Tweakers and Testers
HTC Linux

Change log.
0.2 Added WPA2 script , user just have to edit and enable it.
0.1 Added boot from loop or second partition.
0.0b first release

There is already a thread for this...

Here is what I would do:
1)Rebuild your kernel without virtual terminal,
2)use/boot this kernel with android.
3) use es file explorer to find the write /dev/block/mmcblkXXX???
use this in the init script of the initrd
4) use terminal emulator and ls -la to find out the MAJOR and MINOR number
of the right /dev/block/mmcblkXXX
use/change this in the bin/MKNODE script in the initrd
-> Done

bergfex said:
Here is what I would do:
1)Rebuild your kernel without virtual terminal,
2)use/boot this kernel with android.
3) use es file explorer to find the write /dev/block/mmcblkXXX???
use this in the init script of the initrd
4) use terminal emulator and ls -la to find out the MAJOR and MINOR number
of the right /dev/block/mmcblkXXX
use/change this in the bin/MKNODE script in the initrd
-> Done
Click to expand...
Click to collapse
always a great help bergfex thnx

You can try step 3 and 4 also with the default android system. It is likley that it shows the same behavior.
Yea, but where is my motivation to buy a transformer, when you already have done the fun part.

bergfex said:
You can try step 3 and 4 also with the default android system. It is likley that it shows the same behavior.
Yea, but where is my motivation to buy a transformer, when you already have done the fun part.
Click to expand...
Click to collapse
i thing makedev is not even running as i dont even see the intro .( make is after intro )
think i have to dd the image to sdcard and that the kernels calls directly to init on root dev
you remember that sdcard is not mounted because of makedev , here its already working i think

Gary13579 said:
There is already a thread for this...
Click to expand...
Click to collapse
and have you seen any progress at the thread? cmon the thread title says: coming soon (i assume)

dd the image to sdcard (or even better to the internal nand sometime in the future) should end up in an better performance anyway.
If the intro doesn't show up there may be a problem with the arguments of mkbootimg.
It was the following if someone else want to give it a try:
./mkbootimg --cmdline 'init=/init rw consoleblank=0 fbcon=rotate:1' --kernel zImage --ramdisk ramdisk-new.gz -o boot-new.img
Maybe you can add a the link to your zImage and to your ramdisk in the first post if someone else want to try/help.
Otherwise the link can be found in the coming soon (i assume) thread.

jazux said:
and have you seen any progress at the thread? cmon the thread title says: coming soon (i assume)
Click to expand...
Click to collapse
it was meant for people to brainstorm for solutions, pretty much like this thread, and yes there has been progress in that thread.

jazux said:
and have you seen any progress at the thread? cmon the thread title says: coming soon (i assume)
Click to expand...
Click to collapse
And needlessly fragmenting information/work across numerous threads does nothing but exactly that: segment information and clutter the forum.

almost there

Wow!
Thats really good news!
But tell us more! Whats left to crack before you are ready to release something?
Thanks for making this happen!
Sent from my Transformer TF101 using XDA Premium App

Jhinta said:
almost there
Click to expand...
Click to collapse
If you can pull this off, you sir, will be my hero

Jhinta said:
almost there
Click to expand...
Click to collapse
Getting my paypal account ready for some donating

yes ? yes ? yes ??

Will this help?
http://www.nvnews.net/vbulletin/showthread.php?t=163916
Sent from my Transformer TF101 using XDA Premium App

Little tip, Add root=/dev/ram0 to get it to load the initrd and drop you to a shell

david279 said:
Will this help?
http://www.nvnews.net/vbulletin/showthread.php?t=163916
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
very limited amounts of that are useful, probably the sound stuff, GPU acceleration isn't going to work from that package as it is for the harmony SOC only, and we have the ventana SOC

[APP] QuickRemote IR Blaster for AOSP roms

Hi everybody! I've switched over to CM 10.2 M1 as my daily driver, but I missed being able to change the volume on my tv with my phone. So, I've managed to get the QuickRemote app from the stock ROM working on Cyanogenmod (and hopefully other AOSP roms). There is nothing carrier-specific in this, so it should work on all variants.
Luckily there is no kernel module involved in driving the IR hardware. Instead the IR chip is a black box that is controlled via an internal serial port interface. The QuicksetSDK.apk package includes the code to control the IR chip. It creates a Service that the LGQRemote.apk app binds to to send commands to the IR hardware.
Installation
This will only work on rooted devices.
To get this working you'll need to install two APKs:
QuicksetSDK.apk
LGQRemote.apk
You'll also need to add a script that runs on device boot.
You can download mine here: 10QuickRemote
Or just make one yourself, containing this code:
Code:
#!/system/bin/sh
chmod 666 /dev/ttyHSL1
setprop persist.sys.lge.eula_agreement true
This makes the serial port accessible to non-system processes. On the LG stock rom the QuicksetSDK package runs as the system user, but here we're running it as a normal unprivileged user, so we need to make the serial port world-readable and writable. We also use the 'setprop' command to tell the QuickRemote app that we've agreed to LG's EULA, otherwise it will attempt to launch a non-existent EULA activity and crash.
I'm not 100% sure how the init.d system works on other AOSP roms, but on Cyanogenmod, you can place this script in the /data/local/userinit.d directory (creating the userinit.d directory if necessary). The script should not have an extension, and should be executable.
A quick method that works on CM, assuming you've downloaded my 10QuickRemote script to your current directory:
Code:
adb root
adb shell "mkdir -p /data/local/userinit.d"
adb push 10QuickRemote /data/local/userinit.d
adb shell "chmod 755 /data/local/userinit.d/10QuickRemote
For the above to work, you'll need to enable root for adb in Settings > Developer Options > Root Access
After a reboot, you should be able to use the QuickRemote app just like on the stock ROM!
If the app crashes right away, or if it launches but won't send any IR commands or learn new ones, your start-up script probably isn't being executed properly. Try running it manually and see if things work:
Code:
adb shell
--- inside adb, as root:
# sh /data/local/userinit.d/10QuickRemote
# ls -l /dev/ttyHSL1
-- result should be:
crw-rw-rw- system system 245, 1 2013-11-06 08:20 ttyHSL1
# getprop persist.sys.lge.eula_agreement
-- result should be:
true
If running it manually works, make sure the script is executable or it won't be called automatically on boot:
Code:
-- inside a root shell
# chmod 755 /data/local/userinit.d/10QuickRemote
If it is executable and still doesn't work after a reboot, and you're running a non-Cyanogen ROM, they probably do init scripts differently. Hopefully you can google up how to make it work
If everything looks correct and it still won't work, send me a logcat and I'll try to figure it out.
Enjoy!

sefnap said:
Hi everybody! I've switched over to CM 10.2 M1 as my daily driver, but I missed being able to change the volume on my tv with my phone. So, I've managed to get the QuickRemote app from the stock ROM working on Cyanogenmod (and hopefully other AOSP roms). There is nothing carrier-specific in this, so it should work on all variants.
Luckily there is no kernel module involved in driving the IR hardware. Instead the IR chip is a black box that is controlled via an internal serial port interface. The QuicksetSDK.apk package includes the code to control the IR chip. It creates a Service that the LGQRemote.apk app binds to to send commands to the IR hardware.
Enjoy!
Click to expand...
Click to collapse
thanks so much!!
would it be possible to make this into a flashable zip?

just a quick question am i suppose to see the list of make and models? if so i dont see it... the remote is installed though
nvm... some how the list came out.. not sure what i did. thx for the mod

blkghost22 said:
just a quick question am i suppose to see the list of make and models? if so i dont see it... the remote is installed though
nvm... some how the list came out.. not sure what i did. thx for the mod
Click to expand...
Click to collapse
I have the same issue. You just keep playing around with it?
Sent from my LG-VS980 using Tapatalk

steveo17 said:
I have the same issue. You just keep playing around with it?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.

blkghost22 said:
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
Click to expand...
Click to collapse
Right i installed it by clicking the apk and installed it like normal. And now it works
Sent from my LG-VS980 using Tapatalk

steveo17 said:
Right i installed it by clicking the apk and installed it like normal. And now it works
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
for some reason tho... once i reboot my phone. i need to install that again.

awesome job!
I've been leery of flashing a custom rom for the lack of IR and other features. Plus I'm really digging the stock rom.
But with AOKP coming soon, I am might be tempted. Good to know that the application works with directly with the IR blaster.
I thought AOSP 4.4 was suppose to have support for IR blasters, but it seems noone has them working on CM yet.

blkghost22 said:
for some reason tho... once i reboot my phone. i need to install that again.
Click to expand...
Click to collapse
Same here
Sent from my LG-VS980 using Tapatalk

blkghost22 said:
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
Click to expand...
Click to collapse
The list is actually downloaded by the QuicksetSDK app at runtime. I guess they did it that way so they could add models after shipping the phone.

I hope make flash.zip it is easy

Set this up on my D801, works great! It's a little difficult to navigate sometimes because some of the coloring of menus is designed for the stock rom. It seems to be missing the Comcast cable box settings though, it could be possible the app is different on different phones. Either way I just made it "learn" buttons over my TV remote which works way better than the short while I had it on the stock rom. This is the only feature I miss at all from stock, now my phone has every feature I want!
It's really not difficult to use a little terminal/command prompt, people are scared of putting in commands for some silly reason. If you've used ioroot, you already have adb to use too.

nice job!
i made a quick flashable zip package:
http://www43.zippyshare.com/v/86147127/file.html (new slim mod)
-> http://forum.xda-developers.com/showpost.php?p=47500016&postcount=94
(installs in data partition so it should survive a rom update)

RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
I get this
Sent from my LG-G2 using XDA Premium 4 mobile app

RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
I tried flashing this zip and working fine on mine thank you!
Sent from my LG-D802 using xda app-developers app

RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
Flashable works gr8 here as well.... have not rebooted to make sure everything sticks though... tnx guys!

zplit said:
I get this
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
which recovery?
which rom?
did you do a manual installation before flashing the zip?

thank you SO MUCH sefnap! and thank you RieGo for the flashable zip. just flashed on PA 4.3 for D801 and everything is working beautifully.
and as mentioned above- if there's any way you could get the lg camera to work, too, you would be the king. it looks like some sort of progress has been made over in this thread. the AOSP camera works well, but i'd love to have the manual focus option, and so on.
thanks again for adding this great functionality back for us! :good:

Thanks. Flashable zip works perfectly with slimbean on D801. This was the only thing I was missing with AOSP. Thanks again
LG D801 on Slimbean

A camera port with official firmware LG can not? If you can, do it please.
And that zip up to 160 MB? Driver? Replacing the files?

Carrier Unlocking Sprints Photon Q

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

AdBlocking on Rooted Z5

Hi,
A while back I rooted my phone because I had had enough of missing out on xposed modules and had had enough with all the Ads!! When did Android become so riddled with adverts. (i know its not android itself before you say anything)
Anyway I managed to root my phone using the methods highlighted in the forum. I've got xposed working perfectly but I am still seeing averts in apps and on web pages. Correct me if I'm wrong but I should be able to hide these now. I've come from Galaxy S4 which I had rooted from day 1 so I never saw a single advert (in app or webpage) but now on my rooted Z5 I am still seeing a lot. Many apps (baconreader for example) have had the ads in there hidden but many still persist.
I've tried all the options I can see to be available to me
In no particular order and never installed at the same time incase they conflict.
- Adaway (this errors when applying the host file saying the copy failed)
- Adblock plus (app not browser)
- Adfree (this is what I used on my S4)
- MinMinGuard (tried different modes on this one and still no luck and no errors to speak of)
None of them error apart from AdAway.
Have any of you guys got a totally adfree experience on the Z5? If so how have you managed this?

I am using Adguard, it costs 8$ a year. That's almost free I think.

I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk

Funkmasterchilla said:
I am using Adguard, it costs 8$ a year. That's almost free I think.
Click to expand...
Click to collapse
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?

TimDawg said:
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?
Click to expand...
Click to collapse
AdAway is working for me.
Like I said ensure you can remount /system as r/w.
Sent from my E6683 using Tapatalk

_Dennis_ said:
I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers

TimDawg said:
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers
Click to expand...
Click to collapse
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk

See MOAAB (mother of all ad block) in Android Development and Hacking. Costs 0 bucks and blocks hosts. That's the best if you are rooted bro

_Dennis_ said:
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I get an error saying no such directory. if i try to create it manually it fails...

TimDawg said:
I get an error saying no such directory. if i try to create it manually it fails...
Click to expand...
Click to collapse
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk

_Dennis_ said:
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.

TimDawg said:
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.
Click to expand...
Click to collapse
What super user app do you use? How was it installed?

_Dennis_ said:
What super user app do you use? How was it installed?
Click to expand...
Click to collapse
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.

TimDawg said:
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.
Click to expand...
Click to collapse
Probably your best bet. Sorry I couldn't be of any help.
Sent from my E6683 using Tapatalk

How did you rooted your z5?

luisfillipe said:
How did you rooted your z5?
Click to expand...
Click to collapse
I used the method for Z5 dual SIM posted in the dirty root thread in development section. There are other simpler methods for the regular Z5, again in development section. It requires bootloader unlocks for all of them and that causes you to lose some Sony DRM keys.
Sent from my SM-T710 using Tapatalk

I tried Adblock since i'm not rooted, but it occasionally drain battery in sleep mode so I removed it..

I've always used Lucky Patcher for that. It has hosts blocking as well as disabling google ad modules inside apps, making everything clean and bull$hit free.

Gotta say I was starting it get a be pissed off with how much more complicated it is to do root this phone than any other android phone I've tried to do in the past...
so I came to the assumption that I'm supposed to be booting into recovery and installing the zip through there like I used to do to install ROMs on my older android phones.
I've flashed a few AndroPlus kernels and no luck. One of them left me stuck in bootloop which I let go around roughly 10 times until I decided it was getting nowhere. I did eventually manage to get one installed without a bootloop.
I wanted to know what Kernel I was running so I installed 'Kernel Adiutor' which required BusyBox to be installed alongside it. I found I was unable to install BusyBox which I guess was caused by the same thing causing all my other issues.
I've tried going through this whole over complicated process again and I hit a problem was trying to execute these two lines:
Code:
adb shell mount /dev/block/platform/soc.0/by-name/system /system
adb shell mount /dev/block/platform/soc.0/by-name/userdata /data
I read through everything I could find again to see if I could work out what was going on. While looking for this I can across this line of code:
Code:
fastboot flash boot boot.img
which is to be run if you want to flash the kernel via adb. (you need to extract the zip provided by AndroPlus)
Once this line had been executed I booted up again and was able to install BusyBox which let me see which kernel I had which showed AndroPlus (v3 incase you're interested) so I then tried AdAway again.
BINGO
Only thing is on some websites, particularly xda there is still a gap showing where the Advert would be displayed if not blocked. This I can live with.
I can't beleive how much more complicated this phone is to root compared to my HTC Desire, Galaxy S2 & S4. All of them were plug phone in. Click a few times and the jobs done. Is there a reason this hasn't been done for the Z5?
Just want to say thanks to all that have tried to help.
Thanks to AndroPlus for his kernel which has sorted me out.
Not so much thanks to Sony as this whole process has put me off ever getting another Sony phone. Mainly the fact I've lost some functionality what with having to unlock the bootloader. Overall I'm happy though.
Cheers