[NST/NSTG][ROM] 1337 ROM [Apr. 9]

[tge101]

I'm at the point where I've flashed Nooter 1, and I'm trying to sign into youtube. Is there any way to make this work with MFA? I keep getting a message that my account isn't valid.

 

[nmyshkin]

I'm at the point where I've flashed Nooter 1, and I'm trying to sign into youtube. Is there any way to make this work with MFA? I keep getting a message that my account isn't valid.

MFA?

AFAIK there are no longer any versions of YouTube for the NST/G which will successfully sign in. Google simply shut out sign-ins from Android 2.1. So if that was supposed to be your way into a device Google account, you may be SOL.

When I researched an update of NTGAppsAttack, my experience was that the only way to a quasi-Google account sign-in was through GMail, but only after going through the initial Google device set-up and declining to add any accounts.

With the unusual 3-part installation of the 1337 ROM, I'm not sure you can duplicate that, although you might try proceeding without the YouTube sign-in, then when the ROM is up and running, try using NookManager to run the updated NTGappsAttack. It could be your only way in at this point. It might also mess up the 1337 ROM. Make a backup before trying.

 

[thejaredhuang]

Hi,

As you all know B&N has pushed update 1.2.2 ... I recently upgraded ... i used Glownooter and turns out it can be rooted and unlocked for access as an android device.

I was wondering if somebody would be willing to recook @yattaro 's 1337 ROM using the latest official 1.2.2 firmware ?

thanks

I'm also interested in this. Or is there a way to update TLS without going to 1.2.2?

 

[aiamuzz]

I'm also interested in this. Or is there a way to update TLS without going to 1.2.2?

hmmmmm ... i tried upgrading to 1.2.2 ... used glownooter 1.2.x to root and convert the device into a full fledged android device but there just isn't any space to sideload any apps (it gives no space error) ... I reverted back to my backed up 1337 which has so many apps ... and there is still space for installing more ...

I really hope somebody here could find time to recook 1337 using the latest 1.2.2 firmware ...

 

[Pragd]

Install mod apps on nst 1.2.2

Hi is there a way I can root and install apps on my book simple touch with 1.2.2?

 

[nmyshkin]

Hi is there a way I can root and install apps on my book simple touch with 1.2.2?

The short answer is yes, start here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048

The 1337 ROM was put together in such a way that it cannot be readily updated and even if you stayed on 1.2.1 so you could use it, the whole Google apps part is broken. I have not looked at this closely before, but I now suspect that you could start with a rooted 1.2.2 device and then add nearly all of the 1337 features piecemeal since most of them are scattered around the forum in other places.

Maybe I'll look into this in a few days.

 

[nmyshkin]

hmmmmm ... i tried upgrading to 1.2.2 ... used glownooter 1.2.x to root and convert the device into a full fledged android device but there just isn't any space to sideload any apps (it gives no space error) ... I reverted back to my backed up 1337 which has so many apps ... and there is still space for installing more ...

I really hope somebody here could find time to recook 1337 using the latest 1.2.2 firmware ...

I've finally gotten around to taking a look at this and I have to say they made this as difficult as possible. I started comparing files with the 1.2.1 update zip. Most appear to be identical but others like the kernal (no surprise there) and recovery.img (again, no surprise) are different. I thought originally I could just swap the files from the 1.2.2 update zip into the various parts of the original install package and that would do it, but there are a great many files to check and I'm not sure I will live that long I'm also very reluctant to try this out because it replaces the internal recovery with CWM. Once the internal recovery is gone, there is no going back unless the various backup schemes (I use NookManager) actually backup EVERYTHING and can replace the recovery with the factory version.

So..., if you have your heart set on this ROM, here is what I would do:

1. BACKUP YOUR CURRENT CONFIGURATION.
2. Factory reset your device and do a manual update to 1.2.2. You can use NookManager for the factory reset and you'll need to make a NookManager card for step 4 below, so might as well do it now (follow link in step 4 for updating NookManager). If you cannot do a factory reset because the internal recovery image has been replaced by CWM, then you are SOL and I don't know where to go from there.
3. Register or not, as you like, but be aware that skipping OOBE will result in poorer battery life unless you remove the B&N stuff properly (see: https://forum.xda-developers.com/nook-touch/general/nst-g-removing-bn-apps-t3972941), but you can't do that until you are done with all this.
4. Root using the updated NookManager. See: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
5. If you want what's left of GApps, do that next. See: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-ntgappsattack-t3875957
6. Now....go back to the first post and follow the links to the various components and install each in turn (the kernal, the status bar mod, the Settings app, etc.). Some of these can be done with a CWM sdcard, others by ADB (which will be functional if you root with NookManager). Relaunch, the Cupcake/Donut Launcher and Rotation Control are user apps which you can find within the original zips. See next step.
7. Download the 1337 ROM zip from the first post "Download" tab. Unzip and you have three more zip files, each containing various parts of the original 1.2.1 installation. You'll want to unzip those to recover any of the user apps which you want from the original package. The user apps are found in /data/apps and they are spread over at least two of the zips, so look around. You can side-load anything you want and leave what you don't. There may be some system apps which have been added (/system/app), but I'd be careful there. Some are useless GApps files that don't function any longer. Unless you are missing some behavior you remember from the original 1.2.1 version, I'd stay away from adding system apps (which are not side loaded, but rather just copied into the /system/app folder on your device).

This procedure should get you very close to the original 1337 ROM but now running 1.2.2. If, as the developers claim, there were other various "tweaks", then you may be missing those. And you may not notice. It will not give you internal CWM as the recovery. There is a post in the forum somewhere for doing that, though, if you must have it. I just use an sdcard version when I need it. Again, I want to be really sure I can go back to stock if something awful happens.

I may try this myself to see what all the fuss is about, although I am pretty happy with the current evolution of my devices.

 

[pmforlife]

I may try this myself to see what all the fuss is about, although I am pretty happy with the current evolution of my devices.

Hi
I am wandering in NST development to find a way to finally could install, run, and sync the ankidroid app. Version 2.4.3 was working and had no problem in syncing in my rooted NST until recently which stopped working. It does not even login to my account.

When restoring and rooting again did not work, I tried to test other ways like installing 1337 ROM. However, after installing it (like the steps mentioned in the first post except that I used a CWM on my sd card and skipping the youtube step), I can not install any app (even apps I definitely know working on android 2.1). For any app, I got the message: For security, your phone is set to block the installation of apps not secured in Android market.

Could you tell me if there is a solution to this problem of running ankidroid + syncing or because of google limitations on android 2.1 it has stopped working?

Thanks

 

[nmyshkin]

Hi
I am wandering in NST development to find a way to finally could install, run, and sync the ankidroid app. Version 2.4.3 was working and had no problem in syncing in my rooted NST until recently which stopped working. It does not even login to my account.

When restoring and rooting again did not work, I tried to test other ways like installing 1337 ROM. However, after installing it (like the steps mentioned in the first post except that I used a CWM on my sd card and skipping the youtube step), I can not install any app (even apps I definitely know working on android 2.1). For any app, I got the message: For security, your phone is set to block the installation of apps not secured in Android market.

Could you tell me if there is a solution to this problem of running ankidroid + syncing or because of google limitations on android 2.1 it has stopped working?

Thanks

I'm not familiar with the app you refer to but there are two likely causes for sync failure. One might be fixed, the other not. It's possible the security certificate which enabled access to the sync server has expired. This is a slowly creeping problem with our outdated cacerts.bks file. The possible good news is that if you can determine that this is the case and correctly identify and download an updated certificate, it can be updated. I did this recently when FBReader stopped syncing.

The other possibility is that you are getting a general SSL handshake failure because two-step authentication or some other method the NST can't negotiate has been implemented. AFAIK there is no fix for this.

You can maybe see what the problem is by following a logcat during the attempted sync process. With FBReader the certificate was mentioned and returned an error.

Shifting to the questionable 1337 ROM is not going to help. It uses the same cacerts.bks file and SSL. I hope you made a backup.

 

[pmforlife]

I'm not familiar with the app you refer to but there are two likely causes for sync failure. One might be fixed, the other not. It's possible the security certificate which enabled access to the sync server has expired. This is a slowly creeping problem with our outdated cacerts.bks file. The possible good news is that if you can determine that this is the case and correctly identify and download an updated certificate, it can be updated. I did this recently when FBReader stopped syncing.

The other possibility is that you are getting a general SSL handshake failure because two-step authentication or some other method the NST can't negotiate has been implemented. AFAIK there is no fix for this.

You can maybe see what the problem is by following a logcat during the attempted sync process. With FBReader the certificate was mentioned and returned an error.

Shifting to the questionable 1337 ROM is not going to help. It uses the same cacerts.bks file and SSL. I hope you made a backup.

Many thanks for your quick reply. It would save me a lot of time if either I could fix the problem or I know that I have no choice except saving money to buy an android book reader.

I have back up of my unrooted nook. However, there is a way that not having a backup is solvable. I mention it here. Maybe it would be useful:
First go to CWM and clear system/data/cash.
Then use this method:
1. Power off the nook.
2. Power on it.
3. When seeing read forever, after 1 second hit the power button and hold it for 10 seconds.
4. Release the power button and immediately hit and hold it again, this time until the nook reboots. Release the button.
5. When you see read forever ... >>> continue from 3.
Do this cycle 8 times. It will go the restore and then you have your nook as it was on the first day.

Anyway, I restored my nook. Then rooted in the way I rooted it for the first time. (At least I can install applications! not like 1337 ROM which I could not). Then I tried to log in to my account in Ankidroid which is the top flashcard app for reading anything from learning another language to learning physics formulas.
However, I do not know how to use a logcat to see what is the issue. I have a "superuser" in my apps list but even after trying to log in to my ankidroid account and failing, it shows: no log information.

Any other app that could help me with this?

 

[nmyshkin]

Many thanks for your quick reply. It would save me a lot of time if either I could fix the problem or I know that I have no choice except saving money to buy an android book reader.

I have back up of my unrooted nook. However, there is a way that not having a backup is solvable. I mention it here. Maybe it would be useful:
First go to CWM and clear system/data/cash.
Then use this method:
1. Power off the nook.
2. Power on it.
3. When seeing read forever, after 1 second hit the power button and hold it for 10 seconds.
4. Release the power button and immediately hit and hold it again, this time until the nook reboots. Release the button.
5. When you see read forever ... >>> continue from 3.
Do this cycle 8 times. It will go the restore and then you have your nook as it was on the first day.

Anyway, I restored my nook. Then rooted in the way I rooted it for the first time. (At least I can install applications! not like 1337 ROM which I could not). Then I tried to log in to my account in Ankidroid which is the top flashcard app for reading anything from learning another language to learning physics formulas.
However, I do not know how to use a logcat to see what is the issue. I have a "superuser" in my apps list but even after trying to log in to my ankidroid account and failing, it shows: no log information.

Any other app that could help me with this?

No, logcat is a ADB function. It has nothing to do with Superuser.

I have another idea. Is there a Ankidroid website? If so, I could compare the certificate used there (which might be the same as used for the login server) and see if it has expired in our cacerts.bks. That would be simpler than me trying to establish an account, etc.

 

[pmforlife]

No, logcat is a ADB function. It has nothing to do with Superuser.

I have another idea. Is there a Ankidroid website? If so, I could compare the certificate used there (which might be the same as used for the login server) and see if it has expired in our cacerts.bks. That would be simpler than me trying to establish an account, etc.

Right. So I need to read and learn about ADB / Logcat.

Yes, Ankidroid is accesible here: https://ankiweb.net/decks/

The android app and desktop software of ankidroid are synced with that.

I have also created a new account with these details:
User ID: [email protected]
Password: 12345678

The ankidroid for android 2.1 is downloadable here:
https://ankidroid.en.uptodown.com/android/download/435651

So if you can not find the needed information on the website, you can install its apk and log in with the above user/id to see if it would work.

Sorry to bother you...

 

[nmyshkin]

Right. So I need to read and learn about ADB / Logcat.

Someday perhaps, but not today.

The website uses Cloudflare and Baltimore Trust certificates. Since the stock cacerts.bks file never contained a Cloudflare certificate we can eliminate that as you were once able to sync. The Baltimore Trust certificate has expired. That's probably the problem.

To test I installed the app on my NST running FW 1.2.2. I am using the cacerts.bks file that I recently updated to address FBReader sync. It also is fixed for the Kindle app and the Baltimore Trust certificate is still valid. Although it took me awhile to find how to log in, I sailed through the process with the credentials you provided.

So, you need to update cacerts.bks. To do so you require a file manager with root priveleges. ADB would also work but you are likely to have some kind of file manager?

Here is the direct download link for the file: https://forum.xda-developers.com/attachment.php?attachmentid=5033607&d=1591306898

This file needs to be copied into /system/etc/security. You can either overwrite the existing file or first rename the existing file to something like cacerts.bks.bak first. The permissions on the cacerts.bks file should be set to rw-r--r--

Then reboot. That should solve the problem.

 

[pmforlife]

Someday perhaps, but not today.

The website uses Cloudflare and Baltimore Trust certificates. Since the stock cacerts.bks file never contained a Cloudflare certificate we can eliminate that as you were once able to sync. The Baltimore Trust certificate has expired. That's probably the problem.

To test I installed the app on my NST running FW 1.2.2. I am using the cacerts.bks file that I recently updated to address FBReader sync. It also is fixed for the Kindle app and the Baltimore Trust certificate is still valid. Although it took me awhile to find how to log in, I sailed through the process with the credentials you provided.

So, you need to update cacerts.bks. To do so you require a file manager with root priveleges. ADB would also work but you are likely to have some kind of file manager?

Here is the direct download link for the file: https://forum.xda-developers.com/attachment.php?attachmentid=5033607&d=1591306898

This file needs to be copied into /system/etc/security. You can either overwrite the existing file or first rename the existing file to something like cacerts.bks.bak first. The permissions on the cacerts.bks file should be set to rw-r--r--

Then reboot. That should solve the problem.

Thanks for your time.
My default manager does not allow me to change system files. So I installed Root Browser 2.2.3.
I renamed cacerts.bks and paste the one you provided its download link. Set it to rw-r--r-- then Reboot. Unfortunately, the error remained the same. Deleting the old file from my NST did not change anything.

I attached the photos of the cacerts.bks and the ankidroid error. The ankidroid does not even check that the entered email/pass is not valid. It just says A network error occurred for every entered user pass. I tried other versions of this app, all were the same.

You said that you could successfully log in and sync your Anki in your NST, right? If yes, I am happy that it means this issue would be solvable. If it is the only choice, I will set up my NST just as you set it up to overcome this annoying error.

 

[nmyshkin]

Thanks for your time.
My default manager does not allow me to change system files. So I installed Root Browser 2.2.3.
I renamed cacerts.bks and paste the one you provided its download link. Set it to rw-r--r-- then Reboot. Unfortunately, the error remained the same. Deleting the old file from my NST did not change anything.

You said that you could successfully log in and sync your Anki in your NST, right? If yes, I am happy that it means this issue would be solvable. If it is the only choice, I will set up my NST just as you set it up to overcome this annoying error.

You did not say if you were running FW 1.2.2. I one thought that the TLS changes were only for the B&N purchases but I have changed my mind about that because of other behaviors I have observed in one device still running 1.2.1 and the other with 1.2.2. I may be the problem if you are still on 1.2.1

Otherwise, I don't know

 

[pmforlife]

You did not say if you were running FW 1.2.2. I one thought that the TLS changes were only for the B&N purchases but I have changed my mind about that because of other behaviors I have observed in one device still running 1.2.1 and the other with 1.2.2. I may be the problem if you are still on 1.2.1

Otherwise, I don't know

I rooted my device using a way described in another forum (It is not in English). It was said that your FW should be 1.1.2 then use this .img file to root and ... your device.
So if I should unroot my device, update it to FW 1.2.2, I will. Then could you please address me the topic I should root my device with the help of its instruction?
thanks

 

[nmyshkin]

I rooted my device using a way described in another forum (It is not in English). It was said that your FW should be 1.1.2 then use this .img file to root and ... your device.
So if I should unroot my device, update it to FW 1.2.2, I will. Then could you please address me the topic I should root my device with the help of its instruction?
thanks

Omigosh, no wonder! I'm surprised it will do anything at all without constantly complaining.

The easiest and surest way to root the NST is probably via NookManager. I have produced a set of updates for the utility. You will need to prepare an sdcard to use with it. If you don't want to hang on to it, you can erase the card later.

In brief, here is a summary of what you will do:
0. Is this a US firmware device? If not, there are additional preliminary steps. If it is a US device, continue to step 1.
1. Prepare and update a NookManager card (https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048). Be sure to make at least the update for 1.2.2. The rest are up to you. Also, in the second post is a method for updating cacerts.bks during the rooting process. You can substitute the file you already downloaded for any ones mentioned there. Or you can just do it manually after rooting it done as you did before.
2. On your PC download the FW 1.2.2 update from B&N (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
3. Power down your device and insert the NookManager card. Power up and it will boot from the card into NookManager.
4. Skip Wi-Fi turn on
5. Choose "Rescue" (top left) and after that "Restore factory.zip" (bottom right). Follow the directions.
6. At the Welcome screen, attach your device via USB to your PC. You should be able to see the "NOOK" drive. Copy the FW 1.2.2 update zip you downloaded earlier to this drive and let the device sleep (you can leave it attached to your PC or remove it, as you please--if you leave it attached you will be able to verify later if the update has been done).
7. After awhile check on your NST. It may say on the screen (or in the notifications) that the Firmware has been updated. Or not. If you look at the contents of the "NOOK" drive on your PC you should not see the update zip any longer if it was installed. If it seems like everything has been done, try to proceed through registration. If the update was successful you should have no issues.
8. Power down. Reinsert the NookManager card. Skip WiFi turn on. This time select "Root" (upper right). When it's done (no errors?), back out to the first screen where you will find "Exit" (bottom left). Follow the directions.

Now you are good to go with the latest security updates and a rooted device. After that (and with the updated cacerts.bks file), your app should work again.

 

[pmforlife]

Now you are good to go with the latest security updates and a rooted device. After that (and with the updated cacerts.bks file), your app should work again.

I finally finished the steps you provided and the result:
WOOOW! It worked! :laugh::fingers-crossed::laugh:
I can't believe it is syncing now! You made my night, no! my week! I do not know how to thank you! except say thank you for a million times...

 

[nmyshkin]

I finally finished the steps you provided and the result:
WOOOW! It worked! :laugh::fingers-crossed::laugh:
I can't believe it is syncing now! You made my night, no! my week! I do not know how to thank you! except say thank you for a million times...

Give yourself a pat. That was a lot to wade through! I'm glad it worked out.

 

[xisini]

I am on 1.2.2 now is it possible for me to downgrade to 1.2.1 ? I really need a rom like this but i don't know how to do it :/