[N2E][1.0][1.0.1] TouchNooter 1.6.24

[ros87]

In your normal phone, and I may have this wrong, it responds to the servers that it's a phone and therefore can be assigned an Android ID. On your normal unhacked framework.jar within the Nook Simple Touch, this doesn't exist, so Android ID doesn't properly get generated.

There are three pieces of info that Market asks for:

Android ID (Auto generated on first boot, also on the NST)
Phone Type (NST surprisingly returns GSM when asked for this)
Device ID (this is where it goes ka-blam as this is null on the NST)

getDeviceId() would normally return the IMEI for a GSM unit, but as there are nothing in the other end of the Radio Interface Layer on the NST this function returns null, and it it this function that is patched in the framework.

I've actually been looking into writing a dummy-ril for the NST as to avoid having to use a modified framework.

 

[GabrialDestruir]

There are three pieces of info that Market asks for:

Android ID (Auto generated on first boot, also on the NST)
Phone Type (NST surprisingly returns GSM when asked for this)
Device ID (this is where it goes ka-blam as this is null on the NST)

getDeviceId() would normally return the IMEI for a GSM unit, but as there are nothing in the other end of the Radio Interface Layer on the NST this function returns null, and it it this function that is patched in the framework.

I've actually been looking into writing a dummy-ril for the NST as to avoid having to use a modified framework.

Ah well, my understanding was always that android id thing was broken. The device gets patched framework.jar using the method I linked to previously and it works... but if we could find a way to make it work without a modified framework.jar maybe we could build a version of TouchNooter that persists between version updates?

 

[ros87]

Ah well, my understanding was always that android id thing was broken. The device gets patched framework.jar using the method I linked to previously and it works... but if we could find a way to make it work without a modified framework.jar maybe we could build a version of TouchNooter that persists between version updates?

Looking at the updater-script for 1.0.1 doesn't leave much hope for a persistent TouchNooter

...
format("ext2", "/dev/block/mmcblk0p5");
mount("ext2", "/dev/block/mmcblk0p5", "/system");
...

And there's also the problem with uRamdisk being replaced by the update.

 

[GabrialDestruir]

I was unable to get TouchNooter to boot with the version of framework.jar posted earlier. I'm getting the black flashing screen boot loop. Not really sure what's causing this and have no way to adb in to find out. (My computer really doesn't like USB ADB) I may just release a Gapp-less version of touchnooter until I can figure it out.

Okay... maybe I'm just hitting some bad luck, but even after removing framework.jar from nooter I can't seem to get it to boot. Idk what's going on.

 

[GabrialDestruir]

Looking at the updater-script for 1.0.1 doesn't leave much hope for a persistent TouchNooter

...
format("ext2", "/dev/block/mmcblk0p5");
mount("ext2", "/dev/block/mmcblk0p5", "/system");
...

And there's also the problem with uRamdisk being replaced by the update.

Well, what I mean is persistent in the sense that one version could work across multiple versions of BN software.

 

[ros87]

Well, what I mean is persistent in the sense that one version could work across multiple versions of BN software.

Ah sorry, misunderstood you there

Yeah that should be possible.

 

[nickveldrin]

On your normal android device, you'll have something called an Android ID, this ID I think is connected to your Google account and allows you to access your services such as Gmail, and Market. In your normal phone, and I may have this wrong, it responds to the servers that it's a phone and therefore can be assigned an Android ID. On your normal unhacked framework.jar within the Nook Simple Touch, this doesn't exist, so Android ID doesn't properly get generated.

Without this Android ID, Gapps will not work, you won't be able to check Gmail, you won't be able to use market, etc. This framework.jar is only required if you want Gapps working. If you don't care about Gapps then you don't need it.

I see! That makes sense - thanks for explaining. I will wait patiently for a fix and will try again as more progress is made.

 

[GabrialDestruir]

Seems there's something else wrong with TouchNooter besides the framework, I'm going to have to rebuild it from the ground up for 1.1 It seems even without framework.jar somethings corrupting system so it won't boot.

Some bad news, it appears that there may be some sort of signature based protection on files in /system. I'm not sure how to confirm this, but it seems if I replace framework.jar it boot loops, if I modify build.prop without replacing framework.jar it also boot loops. If someone could verify this maybe with noogie? I can add files to /system/ but any modifications to an existing /system/ file causes a boot loop from what I can tell.

 

[apeine]

Dear Fellows,

Kralik, a XDA user, having few posts, and being unable to post in the development forum, posted the following on Mobileread forum:

Link

Maybe it can help us get to a solution faster.

 

[ros87]

If someone could verify this maybe with noogie? I can add files to /system/ but any modifications to an existing /system/ file causes a boot loop from what I can tell.

fwiw, I've also seen this behavior on 1.0.0 and 1.0.1 when replacing android system files on a fully running system. (dalvik cache?)

Just did a quick test on editing build.prop with noogie and then reboot.

#cat build.prop
...
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt

#Added by ros87
ro.dummy.test=hello
#

No problems with that.

Then I tried copying that patched framework.jar (again trough noogie) and rebooted.
As expected there were loads of complaints about incorrect dependency signatures by dalvik which would force it to rebuild cache.
In the end it booted just fine and on subsequent boots there's no complaints.
Unit works just fine with the patched framework, but I cannot confirm the patch itself working as I haven't tried installing gapps yet.

This is more or less the same behavior I've seen before which suggests to me there's nothing new and sinister added to 1.1

---------- Post added at 12:39 PM ---------- Previous post was at 12:33 PM ----------

Update:

I quickly wrote a small app that displays AndroidID, Phone Type and Device ID

With the patched framework getDeviceID() now returns a 15 digit number instead of null, so this confirms it working as intended.

I'll try to set up market next.

---------- Post added at 12:45 PM ---------- Previous post was at 12:39 PM ----------

Update #2:

It's also worth noting that Device ID (IMEI) is regenerated on every call, which could cause trouble with certain apps.

This has been discussed before, just wanted to emphasize that this problem is still there with this patch.

 

[niphoet]

I rooted my 1.1.0 with the new ramdisk and I was successfully able to remove some files from/system, specifically the 2 "how-to" books included. I don't know if this helps or not.

 

[GabrialDestruir]

Odd, anytime I modify build.prop or replace framework.jar it sticks in a boot loop. Specifically it sticks in the same boot loop mentioned earlier about running an unmodified TouchNooter. (Flashing black every 5 seconds) and it just repeats and repeats and repeats, doesn't progress beyond this point.

I suppose if the issue is with replacing the files in a fully running system it's time to rewrite the uRamdisk used by TouchNooter. Fun Fun -sarcasm-

 

[mali100]

Update:

I quickly wrote a small app that displays AndroidID, Phone Type and Device ID

With the patched framework getDeviceID() now returns a 15 digit number instead of null, so this confirms it working as intended.

I'll try to set up market next.

Could you please upload that app?

---------- Post added at 05:19 PM ---------- Previous post was at 04:56 PM ----------

I suppose if the issue is with replacing the files in a fully running system it's time to rewrite the uRamdisk used by TouchNooter. Fun Fun -sarcasm-

Hi,
I have absolutely no problems modifying the files in the running system. Just tried it another time, adb pulled the build.prop, edited the file, remounted /system as rw, pushed it back, rebooted without problems. Also when i did the same thing with the framework.jar, i got no problems.
Can you get an adb logcat from the bootloop?

 

[GabrialDestruir]

Could you please upload that app?

---------- Post added at 05:19 PM ---------- Previous post was at 04:56 PM ----------


Hi,
I have absolutely no problems modifying the files in the running system. Just tried it another time, adb pulled the build.prop, edited the file, remounted /system as rw, pushed it back, rebooted without problems. Also when i did the same thing with the framework.jar, i got no problems.
Can you get an adb logcat from the bootloop?

If I could.... this would be a LOT simpler.

 

[ros87]

Could you please upload that app?

Sure, I'll pm you the link a little later, dinner first

 

[chriscsh]

Odd, anytime I modify build.prop or replace framework.jar it sticks in a boot loop. Specifically it sticks in the same boot loop mentioned earlier about running an unmodified TouchNooter. (Flashing black every 5 seconds) and it just repeats and repeats and repeats, doesn't progress beyond this point.

I suppose if the issue is with replacing the files in a fully running system it's time to rewrite the uRamdisk used by TouchNooter. Fun Fun -sarcasm-

i have replace the patch framework.jar and uRamdisk (only inside the nooter/boot, cause when i replace both uRamdisk, it can boot to the root forever screen, then boot to normal nook home, seem nothing happen ) and it work fine for me
my problem is:
i can launch the youtube at first boot to add the google account, but after that when launch market and it show error "A server error has occurred. Retry, or cancel....." then youtube can't launch anymore

but other than that everything work fine

 

[nickveldrin]

i have replace the patch framework.jar and uRamdisk (only inside the nooter/boot, cause when i replace both uRamdisk, it can boot to the root forever screen, then boot to normal nook home, seem nothing happen ) and it work fine for me
my problem is:
i can launch the youtube at first boot to add the google account, but after that when launch market and it show error "A server error has occurred. Retry, or cancel....." then youtube can't launch anymore

but other than that everything work fine

Same with me. Gmail seems to work okay now that i have that fixed framework.jar, but market behaves the same way as before.

 

[GabrialDestruir]

Same with me. Gmail seems to work okay now that i have that fixed framework.jar, but market behaves the same way as before.

redo the packages.xml via adb and reboot again

 

[chriscsh]

Same with me. Gmail seems to work okay now that i have that fixed framework.jar, but market behaves the same way as before.

i just try delete the patch framework.jar and add back the ori 1.1 framework.jar (use root explorer)
my Market back to normal, search, update....

 

[GabrialDestruir]

It seems, I cannot find a method in which to inject framework.jar and modify build.prop automatically without causing a bootloop, until I can it looks like TouchNooter is dead in the water.