Unable to emulate on boot

[GoogleCodeExporter]

What steps will reproduce the problem?
1. By setting a new SIM-numeric, the number is saved, but reset for some 
unknown reason upon boot.. However, it does say something about "emulating 
310260" (T-mobile US) in the statusbar after each reboot, but nothing happens. 

What is the expected output? What do you see instead?

Standard SIM-numeric "24002" (Swedish provider called Three) is shown when 
opening app, then I can either open "providers" and fake provider, or use 
"Restore value" and the app change from "24002" to "310260".. I believe it 
should rather ask for the complete opposit, to change from "310260" to "24002" 
when restoring..

What version of the product are you using? On what ROM?

I am currently running a Nexus One with Cyanogenmod 6RC1 and MarketAccess 
version 1.0.5.. I have also tried older versions of Cyanogenmod (5.0.6/7/8 and 
6.0 alpha 1) but same issue there.. 

Please provide any additional information below.

Have tried to reinstall, use different ROMs, remove/add superuser settings but 
it still won't work.

Original issue reported on code.google.com by Swedownh...@gmail.com on 14 Jul 2010 at 2:02

[GoogleCodeExporter]

Most likely the problem is caused by the new superuser 2.2.2. You must reset 
the database of the superuser application and ensure that it asks to add 
MarketAccess to list when you manually apply the new sim numeric. New Superuser 
comes with the script which resets the database, read the docs.

I've failed to reproduce the problem with MoDaCo r21 ROM for Nexus One and 
Superuser 2.2.2 after resetting the database. Phone boots and MarketAccess sets 
the provider.

If the issue remains, provide logcat recorded during boot.

Original comment by sbara...@gmail.com on 14 Jul 2010 at 2:30

[GoogleCodeExporter]

Hi! 

I opened applications -> All -> Superuser v2.2.2 and hit "Clear data", then 
opened MarketAccess and set "310260" as a custom value, SU asked for permission 
and I hit the "Yes"-box.. Tried to reboot and see if it was working, but it's 
just like before. 

I also made a logcat for you to read, it's my first one so I hopefully did it 
right! Commandprompt said "waiting for device" when I entered "adb logcat" and 
when my phone started to boot, it also started logging.. 

Thanks for your quick reply, I hope that I have done everything right so far, 
tell me otherwise! // Martin  

Original comment by Swedownh...@gmail.com on 14 Jul 2010 at 4:03

Attachments:

• logcat.txt

[GoogleCodeExporter]

The provided log has nothing related to MarketAccess or Superuser. Are you sure 
that emulation on boot is enabled? Maybe you have some application which 
disables automatic start (like Autostarts)?

Probably the log is not complete, try recording it again with redirecting the 
output to the file: 
http://developer.android.com/guide/developing/tools/adb.html#logcatoptions

You need to run it as

adb logcat -f log.txt

Reboot the phone and attach log.txt.

Original comment by sbara...@gmail.com on 14 Jul 2010 at 4:20

[GoogleCodeExporter]

Hmmm.. I tried to follow your instructions and it said "Waiting for device" 
again but then a new line came up and said "couldn't open output file: 
Read-only file system"..

I also tried to create a "log.txt"-textdocument in the AndroidSDK -> 
Tools-folder, but that didn't work either.. Any ideas why it doesn't work? 

Original comment by Swedownh...@gmail.com on 14 Jul 2010 at 4:30

[GoogleCodeExporter]

Looks like it's trying to write the log to the phone, try:

adb logcat -f /sdcard/log.txt

Then get log.txt from the phone SD card:

adb pull /sdcard/log.txt log.txt

Original comment by sbara...@gmail.com on 14 Jul 2010 at 4:35

[GoogleCodeExporter]

An easier way:

adb logcat > c:\log.txt

Original comment by sbara...@gmail.com on 14 Jul 2010 at 4:37

[GoogleCodeExporter]

Wow, thanks for incredibly fast answers... Same errormessage again though =/.

Is it possible to write to my computer directly, for example to my 
Tools-folder? 

Original comment by Swedownh...@gmail.com on 14 Jul 2010 at 4:40

[GoogleCodeExporter]

See comment #6.

Original comment by sbara...@gmail.com on 14 Jul 2010 at 4:41

[GoogleCodeExporter]

Yepp, I was just a bit too slow.. 

Finally a log.txt was created! After the phone was up and running, I opened 
MarketAccess and emulated 310260, since it didn't do it on it's own during 
boot.. 

Thanks for your help! I really want to take fully advantage of MarketAccess and 
appreciate your cooperation!   

Original comment by Swedownh...@gmail.com on 14 Jul 2010 at 4:49

Attachments:

• log.txt

[GoogleCodeExporter]

It seems to be Superuser 2.2.2 issue:

E/su      (  573): select failed with 2: No such file or directory
W/su      (  573): request rejected (10063->0 /system/bin/sh)

Superuser is not giving MarketAccess root and therefore it can't emulate on 
boot.

Try to wipe the Superuser settings:

adb shell rm -rf /data/data/com.noshufou.android.su

Then reinstall Superuser application, I do it from the command line with 
Superuser.apk and su binary in the current directory:

adb remount
adb push su /system/xbin/su
adb shell chmod 4775 /system/xbin/su
adb push Superuser.apk /system/app

Then run MarketAccess and Allow root. Run Superuser, ensure that MarketAccess 
is in the list. Reboot, see if it helps.

Original comment by sbara...@gmail.com on 14 Jul 2010 at 4:58

[GoogleCodeExporter]

Excuse me, but Im a bit lost.. I did wipe the superuser settings using "adb 
shell rm -rf....", then did an "adb remount".. But when I try to push su it 
says "cannot stat ´su´ no such file or directory. 

My guess is that it's because I need to download the superuser application 
somewhere, add it into the tools folder and then push it over to phone -> 
system.. Am I right? I tried to google superuser but without any good results.. 
=/ 

Original comment by Swedownh...@gmail.com on 14 Jul 2010 at 5:07

[GoogleCodeExporter]

Download and unpack from http://bit.ly/su222ef .
Make sure that su and Superuser.apk are present in the same folder.

Original comment by sbara...@gmail.com on 14 Jul 2010 at 5:14

[GoogleCodeExporter]

Awesome, it finally works! Thanks alot for your help... I followed your steps 
and rebooted, without success, then I realised that I didn't fake the provider 
before rebooting, and when I did, it started to work like it should! 

Thanks again =) // Martin

Original comment by Swedownh...@gmail.com on 14 Jul 2010 at 5:26

[GoogleCodeExporter]

Thanks for the info, closing as not MarketAccess problem.

Original comment by sbara...@gmail.com on 14 Jul 2010 at 5:27

• Changed state: Invalid

[GoogleCodeExporter]

Actually, it didn't work! It worked after first reboot (when I posted comment 
#13, but then it's back to "24002" like it was before... I can't understand 
why, I didn't do anything except reboot the phone. 

Original comment by Swedownh...@gmail.com on 14 Jul 2010 at 5:40

[GoogleCodeExporter]

Please try to get more help at 
http://forum.xda-developers.com/showthread.php?t=682828

Original comment by sbara...@gmail.com on 14 Jul 2010 at 5:41