Related
Who is affected? All devices pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Flash this with ClockWorkMod.... this is for any Pre Gingerbread ROM.... ie TNT anything, VEGAn 5.1.1 and below, Zpad anything, GAdam anything.
This is not necessary for any ROMS based off Gingerbread AOSP or CM7. Including VEGAn-TAB Experimentals.
Be Safe.
Even More Details here: http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
I checked out the zip and it just adds a blank text file (0 bytes) called profile to the /system/bin folder. So I am not sure what the fix is?
**EDIT** Nevermind it is a dummy file meant to prevent the virus. Thanks to the OP for providing this.
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Nasty stuff. I would say this patch is high priority and I'm already going through my own ROMs to add it in.
http://forum.xda-developers.com/showthread.php?t=977154
Link above has info on creating the file manually.
Jim
fyi -
http://www.pcworld.com/article/221213/keep_malware_off_your_android_phone_5_quick_tips.html
Lookout mobile security . In case you cannot find it via the market.
http://www.getjar.com/Lookout-Mobile-Security-with-Antivirus
Edit. I just installed the lookout app to scan my tab, everything was fine and then, i un-installed it since it was running on the background and taking 10% of the cpu..
Anyways, a nice app that can be used to do a quick scan..
I don't have a stock gtab but I'll ask anyways... how can our stock rom users be protected? Is there an alternate method?
Edit just saw the manual process. Im guess that's the way to go.
xmr405o said:
I don't have a stock gtab but I'll ask anyways... how can our stock rom users be protected? Is there an alternate method?
Edit just saw the manual process. Im guess that's the way to go.
Click to expand...
Click to collapse
I'd curious to see what all the vendors are going to do about this. Granted, they could just say that the Market is not there, but regardless the security hole is still there and needs to be plugged up.
Hi,
I hope that this isn't too offtopic, but I was trying to create /system/bin/profile using a term and su, and when i went into root explorer to make /system/bin R/W, root explorer showed the dir as R/W already, and as mounted on /dev/loop9.
Is that normal?
I haven't installed dataloop, at least intentionally, so it seems strange that /system/bin would be mounted there, plus it being R/W by default?
FYI, I use z4root to get temp root. Could that be why /system/bin is R/W?
Then again, that wouldn't explain the /dev/loop9 mount ...
Jim
jimcpl said:
Hi,
I hope that this isn't too offtopic, but I was trying to create /system/bin/profile using a term and su, and when i went into root explorer to make /system/bin R/W, root explorer showed the dir as R/W already, and as mounted on /dev/loop9.
Is that normal?
I haven't installed dataloop, at least intentionally, so it seems strange that /system/bin would be mounted there, plus it being R/W by default?
FYI, I use z4root to get temp root. Could that be why /system/bin is R/W?
Then again, that wouldn't explain the /dev/loop9 mount ...
Jim
Click to expand...
Click to collapse
Hi,
Creating the profile file manually, it wouldn't persist,i.e., it was gone after rebooting, so I installed gojimi's zip usung CWM, and that worked.
I also did a mount w/o getting temp root, and /system/bin is not on /dev/loop9, so I'm guessing that when z4root sets temp root, it might be remounting /system/bin on /dev/loop9 itself.
Jim
You would have to download one of those sketchy apps to really be affected anyways, right? Who would do that?!
Appreciate the patch. This highlights the two problems with android though, google fixed this security issue in 2.2.2, but most carriers still haven't released that update. And the market needs some oversight, not authoritarian apple like, but some.
Sent from my T-Mobile G2 using XDA App
Is it possible to sticky this thread
Mods is it possible to sticky this thread so that it is easily visible.
Thanks
Hello guys. Is there a way to find out if our tablet is infected or not?
I mean if we have installed any of the apps in the list that automatically means that we are infected or not?
If infected what is preferred to do wipe the tablet or go back to stock rom??
Is there any manual for windows 7 noobies users?
Thanks.
Doctor LeVa said:
Hello guys. Is there a way to find out if our tablet is infected or not?
I mean if we have installed any of the apps in the list that automatically means that we are infected or not?
If infected what is preferred to do wipe the tablet or go back to stock rom??
Is there any manual for windows 7 noobies users?
Thanks.
Click to expand...
Click to collapse
Please read the thread completely, it is stated you can download lookout security to run a scan to see if you are infected.
downloading.....see what happens
There is a DroidDreamKiller app that allows you to check to see if you are already infected and install the patch. There is also a beta test app that gives you other information. Just search the market for DroidDreamKiller.
To devs: Thank You
TO Everyone else DO THIS ASAP
How do I flash the zip file after downloading it?
Thanks
Start cwm using volume up while powering on.
Once menu comes up select install zip using vol buttons
Use home to select.
Navigate to where you saved zip file
Select it with home button
Once install complete reboot from cwmod
MODs Please make this a sticky . It is being overlooked.
THIS METHOD IS NO LONGER WORKS as of update version 2.0.5 and higher.
Please visit this thread instead for the current rooting method.
Posting in this thread will get you nowhere, let it RIP.
ANNOUNCEMENT:
If you have a new Nook HD/HD+ and want to root and get the GAPPS running, you should follow the guide at the All-in-One thread instead. That said, I won't copy all the information here to there, so you should continue to read on.
Let me start by saying that I didn't come up with the working root method. The original root instruction came from verygreen in this thread. And I am not a developer, I merely have a few linux background and even less so in the Android. I worked on this on my spare time by myself.
I merely take what was working, but unusable to make it usable. I found something that he is missed. This may actually be working on Nook HD (non-plus) also, but since I don't own one I can't say that it will.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Background:
When I found out the root doesn't actually work past a reboot, I start looking what actually cause the Nook to be pissed and factory reset itself. Well, it seem that the /system and anything in there is basically coming from a /dev/block/mmcblk0p8 And if something got change, Nook get pissed and do a FULL FACTORY RESET(I'll explain in a moment). Well, at least I start investigated under that idea.
What I found:
What I found, or at least what I think I found is that, probably just adding file, or increase in the size(maybe there is a threshold for this), will cause it to do a full factory reset. What I also found is that there is a $PATH for /system/sbin but not pointing to anywhere. So I come up with the idea of making another ext4 file system in a file and loop mount it to /system/sbin I guess that work(very well). What I also found is that, there are two kind of factory resets. The one that you perform yourself, which is actually not a full factory reset and the one that Nook get pissed and do the full one.
A factory reset that you perform yourself, whether from the GUI or button combination will basically clean the partition /data while a full blown one will basically restore other partition such as /system
What is included:
basically a zip file, inside that zip file are 6 files.
boot_complete_hook.sh.bak this is basically a modified version of verygreen's
busybox & su are basically from his thread
superuser.apk well I found this one floating around and seem like a good idea to stick it in there (not even sure if it gonna work w/ Nook)
makeroot.bat this is basically what do most of the work. It's base on verygreen original rooting instruction.
sbin_mount This is basically an ext4 file system which have su and another version of busybox all setup nice and tidy for you all. This version of busybox is 1.20.2r2 which I grabbed from here.
Prerequisite:
ADB, it's your responsibility to have adb up and running, meaning not just have it install, but it can see your nook also.
leapinlar wrote a post to help you getting ADB to work here.
Now to get root:
all you have to do is unzip it and run makeroot.bat (obviously you run this in windows command prompt). Yub that's all. The batch file will do the rest, including reboot the nook and wait for it to reboot and stuff. Won't make a coffee for you though.
The manual and hard way:
well, I will only explain this in a summarize way. Basically this start with verygreen rooting method. It basically take advantage of the exploit and run /data/boot_complete_hook.sh which you adb push yourself(with correct permission) with root privilege. What you can run in there is basically up to your creativity. So obviously in this case, you mount the sbin_mount as an ext4 filesystem in the /system/sbin You can make this file yourself if you want to, in linux using dd and mkfs command. Basically using dd to create a file volume to the size you want and mkfs to format it to ext4. Mount it and start uploading stuff you want in there. You will have to correct all the file permission as well. Since all of this will be mounted to /system/sbin you should be aware what you gonna put in there. I guess I could make this thing 100MB, but for this specific purpose 10MB is enough. I my case, just the su and busybox and the symbolic links for the busybox. I'm doing this for the long term. I'm too lazy to point to busybox everytime I wanna do something.
What to do afterward:
Now that you have root, you can Enable Unknown Source to allow you to install app from within the device and install GAPPS. Follow the two guides below if you interested.
Enable Unknown Source: Again, I make an easy little tool for you here.
GAPPS: here.
Did I missed something:
Well, as I said I'm no coder so if I didn't do a clean job, you can refine it. If I didn't document or give proper credit, then I guess I missed that. Sorry about that, again I'm no coder and never done this. And finally:
If this thing work for you, feel free to hit that "THANKS" button. I spent many hours trying to come up with this solution.
FAQ:
Q: My so and so application when attempting to have root access get freeze up, or superuser doesn't work?
A: Well, I'm not sure if this is dued to how the Nook side-loading work or not, but it seem for some reason superuser won't start by itself. So you have to start it manually the first time.
Q: I type in "adb root" and I can't get in as root, it doesn't work?
A: yes it does, it's just not working with adb root. You can get in via "adb shell" once you get in, type in "su" and you can see that you now should have root access.
Thank you so much! This works perfectly. Survives reboot.
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
This sounds like a good idea initially.
It is true that the B&N does not just check for /system/xbin/su directly like they did in the past.
This time they check for something else and I just had no time to look into it more deeply to find out what is it they are actually checking for. I plan to figure this out on Friday when I am back home.
Also wanted to tell you that having Linux background is a great thing when tinkering with Android (at a low level, anyway). I don't have much Android background to speak of as well.
This works really well, and thanks to Someone (and mad props too) for getting persistent root working on this.
I may be being very naive, but my suspicion on the reboot is around the manifest file that's present at root.
It seems to be generated by the boot process and it might provide a quick and dirty list of what's permitted on the device to check. With persistent root, lots of investigation becomes a lot less painful. I expect that by end of day we'll have install unsigned running.
Early in my experimenting with the HD+, I noted:
- some versions of the Google Services Framework can be installed via adb
- when I launched the native calendar app after installing gsf, it wanted to sync to a google account, and was able to add the google account
- one version of the Play store installed and launched as far as throwing the 'you must accept the terms of service' before crashing
What BN most likely does is calculating the hash value (or digest, if you prefer) of certain system files that they think shouldn't be tampered with, then during reboot, the values of these files must match, or they will do a factory reset.
The key point is to find out where they do these checks and fool the check.
This sound simple but it depends on how they implement it. If they use binary decisions (like if the hash_value == calculated), then it is easy to get around. If not (e.g. using white box algorithm to hide keys), then it get more complicated.
excellent and very elegant solution. Kudos!
I'm heading out to work, and if you think your theory is right, try poking around with it. Now that your have root, you can try to dd those bootloading partitions out to user area and upload them out to PC and inspect them.
looking at the vold.fstab
Code:
xloader -> /dev/block/mmcblk0p1
bootloader -> /dev/block/mmcblk0p2
recovery -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p4
rom -> /dev/block/mmcblk0p5
bootdata -> /dev/block/mmcblk0p6
factory -> /dev/block/mmcblk0p7
system -> /dev/block/mmcblk0p8
cache -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p10
Be extra careful when touching those partition if you not sure, don't touch them. But making a block copy of them and taking them out should be relatively easy and safe. Obviously you gonna need a Linux box to do this. I setup a VM on one of my PC last night because I need to get a ext4 partition and put all the goodies in there.
krylon360 said:
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
Click to expand...
Click to collapse
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
someone0 said:
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
Click to expand...
Click to collapse
works just fine.
I chmod a+x'd the script before putting it into the zip.
heh, yeah, it works. Forgot I had my touchpad pluged in and it rebooted it....
whoops.
thanks for posting the location of the /recovery partition. I want to put a copy of htat on ice to prevent BN from undoing any of my work in a future update - I may want some of the fixes they have, but I want to be able to roll them back if needed.
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder and was able to see it in my sideloaded launcher, was able to uncheck/check install non market apps which sets the setting for US to be able to install .apk files from the nook itself, ONLY ISSUE is since I put that file in the system/app folder and the nook didnt like it I got stuck in a bootloop and get to start this process all over again! (nook resetted to ground zero)
maybe we temporary can leave it there get us the permission to install non market apps then remove the file and we will be ok or maybe stuck in another bootloop.
---------- Post added at 09:20 PM ---------- Previous post was at 08:52 PM ----------
GOT IT WORKING NOW:
1. Once rooted, get a file manager with root support and enable read/write permission to /system
2. temporary copy nook tools ver .02 .apk to the system/app folder
3. have a sideloaded launcher and check the app drawer youll see nook tools, run it, first screen uncheck and check the install non market apps box couple of times make sure its checked afterwards
4. have a test .apk to run the BN installer on and see you can now install .apks from the NOOK HD and HD+
5. remove the nook tools.apk file from the system/app folder and quit your file explorer which should reset everything for the system folder back to the way it orginally is!
6. reboot, if you reboot successfully with no boot loop 8 times, your GOLDEN FOR NOW! once again load up a file manager go select an .apk file and see you can now install it! Next step is trying to get amazon market working! then google somehow, but for google you need files in system/app folder permanently!
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
someone0 said:
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
Click to expand...
Click to collapse
when you sidelaod it OR install or have it installed to another folder or ran from another folder it cant modify the setting to allow non market apps to install!!
has to be in the /system/app folder THEN RAN from app drawer then you can set the setting uncheck and check box quit program and for now YOU HAVE to remove the .apk from the system/app folder and then you can reboot and the setting sticks! I GOT AMAZON MARKET INSTALLED right now installing apps! NOW WE GOT A KINDLE ladys and gentleman!
Amazon apk installs in internal memory. Apps downloaded from Amazon get installed in internal memory. You can then move them to SD card or leave them in internal memory. System apps are provided in the ROMs by the developers or vendors. ALWAYS back up before making system changes.. Now rooted - use Titanium Backup. System/app should be static throughout ROM lifecycle unless modified by user.
skyhawk21 said:
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Click to expand...
Click to collapse
This is why I put the /system back to ro, at least that is what I think I did.
Amazon Store working on ROOTED Nook HD
Proof of Concept:
http://youtu.be/wCyd730L74Y
skyhawk21 said:
Proof of Concept:
http://youtu.be/wCyd730L74Y
Click to expand...
Click to collapse
LOL, your internet is slow. Could have cut the video time by 1/2 if not 2/3 if you switch to faster ISP.
skyhawk21 said:
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder
Click to expand...
Click to collapse
What exactly did you install? I cannot find "nook color tools" in Google Play or on APKTOP. Thanks for your hard work!
NEVERMIND! I found the thread that has the link for the app: http://forum.xda-developers.com/showthread.php?t=868366 Thanks again.
does this root method work on Nook HD+2.0.2?
if not how I can downgrade to 2.0.0?
My Nook Simple Touch is on firmware 1.2 and has been rooted with NookManager. I downloaded the 1.2.1 update zip from the B&N website & copied it to the root directory of my Nook and have been patiently waiting for it to install for a week. Is there a way to force the upgrade or use CWM or NookManager to do it?
Did you try powering down/up your Nook?
CWM Recovery can install it too.
If you are using the original file, you might have to "toggle signatures".
I just strip off the first 0x1a3, 419 (dec) bytes off the file.
A standard zip file has "PK" as the first two bytes.
Something in the rooting process prevents the update from getting applied. The update will wipe out your root and system mods anyway so it might be easiest to recover back to stock, apply the update and reroot. If you back up your apps with Titanium Backup you can restore them afterward and its a pretty painless process.
straygecko said:
Something in the rooting process prevents the update from getting applied. The update will wipe out your root and system mods anyway so it might be easiest to recover back to stock, apply the update and reroot. If you back up your apps with Titanium Backup you can restore them afterward and its a pretty painless process.
Click to expand...
Click to collapse
Thanks, all sorted now
Op: just wondering why would you want to apply the update. What are the benefits? My nook is rooted w nookmanager and I'm quite happy the update fails ever time it tries.
Sent from my SGH-T959 using Tapatalk 2
sLiKK said:
Op: just wondering why would you want to apply the update. What are the benefits? My nook is rooted w nookmanager and I'm quite happy the update fails ever time it tries.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
it's happen with me too .... but it affect on system files and stability .....anyway ther's an option for stop update from nook manager appz ..... also i will reroot my device and turn off updates
best regards
Renate NST said:
Did you try powering down/up your Nook?
CWM Recovery can install it too.
If you are using the original file, you might have to "toggle signatures".
I just strip off the first 0x1a3, 419 (dec) bytes off the file.
A standard zip file has "PK" as the first two bytes.
Click to expand...
Click to collapse
Thanks! This worked, although stripping off the first few bytes was a bit too complicated for me.. I just unzipped and then re-zipped the files and then flashed that.
I would need a little help how exactly it worked. I'm in the same situation. I rooted with 1.2 with Nookmanager. Multitouch, Fastmode and NoRefresh and ezPDF are working fine, and I want to keep it that way.
How can I upgrade to 1.2.1. without going through the whole process again ? I have a Nookmanager SD with my backup and a separate CWM 2GB SD that I used to install the OC kernel for 174 and 166 earlier on. Also, of course I have the 1.2.1 update from B&N.
I guess I can install that zip with CWM, but how exactly ? I don't want to break my root if possible. I have already tried to go back to factory.zip with Nookmanager, then update to 1.2.1, but after restoring my Nookmanager backup I was back to 1.2
Thanks for help !
Renate NST said:
I just strip off the first 0x1a3, 419 (dec) bytes off the file.
A standard zip file has "PK" as the first two bytes.
Click to expand...
Click to collapse
That actually worked..!
419 bytes stripped from the front, leaving the firmware zip file starting with "PK".
(I was wondering why I couldn't open it using the Windows explorer - it was because of the 419 bytes of the signature).
Thank you very much.
If you're in UK, the USA version download won't flash if you're rooted.
USA:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/
UK:
http://www.nook.com/gb/support/nook-simple-touch-glowlight-software-updates
other countries should goto support for their country at:
http://www.nook.com/support
If you're rooted take out the bytes (roughly about a paragraph) as Renate said before PK and save using a hex editor. Or unzip and zip as mentioned.
frhed free hex editor:
http://frhed.sourceforge.net/en/
If you're rooted , flash with CWM as just copying to your nook root might just get deleted, CWM:
http://forum.xda-developers.com/showthread.php?t=1360994
In case anyone is struggling to apply the update, make sure you've put it in the *root* of the *NOOK* 'drive' when connected by USB I didn't read the instructions properly and put it in the root of the SD! Obviously, nothing happened for a fair while until I realised my error...
I've never tried to root my Nook Simple Touch so far. Yesterday I updated my NST to Software Version 1.2.1 and found that it could no longer display some ebooks correctly, so I decided to downgrade it to v1.1.*, following the instructions from this link: ｈｔｔｐ://bookclubs.barnesandnoble.com/t5/NOOK-E-Ink-Support/NST-1-2-0-update-Why-no-page-numbers-in-Contents/m-p/1416722#M3643.
Shortly, what I did is:
Inserted a uSD card burned with "noogie.img" into my (unrooted) NST, and then connected it to the computer via USB;
In Linux, replaced the original "factory.zip" (v1.2.1) with the new one (v1.1.5, link: ｈｔｔｐ://web.mailpen.com/_download/bnFirmware/touch/factory-v1.1.5.zip);
Did a factory reset via the "8-reboot" technique.
After that, my NST could work properly. However, to my surprise, when I checked the Setting menu, I found there is a "*Development" item I've never seen before. It contains "Manage Applications", "Running services", "USB debugging", "Stay awake", "Auto Mount", "Android launcher" and "Widget Test" subitems. When I select "Android launcher" I see something similar to an Android home screen.
To my limited knowledge about Android, to root the device you should at least change the uRamdisk file. Could anyone explain to me what happened? Is my NST rooted?
Yes, your Nook is rooted.
Your "factory.zip" did not come out of any B&N factory.
Update zips contain uImage and uRamdisk.
Thanks for your reply, but I can't find any file named "uRamdisk" or "uImage" in factory.zip. Moreover, it's said that a rooted NST has battery drain problem because of the "cell standby" and "phone idle" processes. However my (possibly rooted) NST only consumes 1% power per day (wifi turned off). So I still can't figure it out.
P.S. The v1.1.5 factory.zip is the one shipped with NST w/ GlowLight, and I'm wondering is there a *Development menu in NSTG...
Factory.zip
Renate NST said:
Yes, your Nook is rooted.
Your "factory.zip" did not come out of any B&N factory.
Update zips contain uImage and uRamdisk.
Click to expand...
Click to collapse
All the downloadable files on that site (www.mailpen.com and web.mailpen.com are my sites) came from:
1. Those that have the word "update" in them, came directly from the B&N site, and when used, should be applied as you normally would for an update.
2. Those that have the word "factory" in them, were directly extracted from partition #3 (the hidden factory restore partition) on the Nook Touch.
In all cases, there are no modifications from me.
What the prior poster did, should have worked. Note that a factory restore (the 8-reset method) does not clear the data partition.
@DeanGibson
Thank you very much for sharing these files! I am OK with the strange '*Development' menu now, since my NST works pretty well so far.
i need to downgrade from 1.2.1 to 1.1.5
excuse me but how did you replace the factory.zip, because my NSTG came with 1.2.1 ver and i want to downgrade to 1.1.5 . can i replace it through partition wizard. i tried to flash the zip file of 1.1.5 from mailpen through cwm , but did not work, i need help
max hd said:
excuse me but how did you replace the factory.zip, because my NSTG came with 1.2.1 ver and i want to downgrade to 1.1.5 . can i replace it through partition wizard. i tried to flash the zip file of 1.1.5 from mailpen through cwm , but did not work, i need help
Click to expand...
Click to collapse
iirc, simply replacing the factory.zip file is enough. All you need is an OS capable of reading NST's file system (if you use a Windows, a Ubuntu running in a VirtualBox is ok) and a "noogie.img" uSD card to boot your NST with. Find the original factory.zip and make a backup. Start nautilus as root (ｈｔｔｐ://askubuntu.com/questions/98489/how-can-i-elevate-nautilus-privileges-to-move-or-copy-a-folder-as-root) and replace factory.zip with the new (old actually) copy. Do an 8-rebooting.
You'd better back up your NST first (use Roadkil's Disk Image or whatever) , especially the directory containing files `SerialNumber`, `DeviceID` and `HashOfPrivateKey`. The device might be bricked.
(I did it months ago so some details given above may be incorrect. do it at ur own risk. )
Stupident said:
iirc, simply replacing the factory.zip file is enough. All you need is an OS capable of reading NST's file system (if you use a Windows, a Ubuntu running in a VirtualBox is ok) and a "noogie.img" uSD card to boot your NST with. Find the original factory.zip and make a backup. Start nautilus as root (ｈｔｔｐ://askubuntu.com/questions/98489/how-can-i-elevate-nautilus-privileges-to-move-or-copy-a-folder-as-root) and replace factory.zip with the new (old actually) copy. Do an 8-rebooting.
You'd better back up your NST first (use Roadkil's Disk Image or whatever) , especially the directory containing files `SerialNumber`, `DeviceID` and `HashOfPrivateKey`. The device might be bricked.
(I did it months ago so some details given above may be incorrect. do it at ur own risk. )
Click to expand...
Click to collapse
thank you for your replay, i alredy backed up my NSTG on ver 1.2.1 and i downgraded to 1.1.5 replace the factory.zip by "gksudo nautilus" then make a back up also, but cant find this development section . another thing how to apply "8 reboot method". thank you
max hd said:
thank you for your replay, i alredy backed up my NSTG on ver 1.2.1 and i downgraded to 1.1.5 replace the factory.zip by "gksudo nautilus" then make a back up also, but cant find this development section . another thing how to apply "8 reboot method". thank you
Click to expand...
Click to collapse
Follow the method #2 on this page: ｈｔｔｐ://nookdevs.com/Nook_Simple_Touch_restore_to_stock
A video on Youtube showing how to do a factory reset for Nook Color: ｈｔｔｐ://youtu.be/_atl79ZcB_I
It's similar for NST.
where did you get the rooted factory.zip? i need one a rooted 1.2 factory.zip
---------- Post added at 07:45 AM ---------- Previous post was at 07:42 AM ----------
DeanGibson said:
All the downloadable files on that site (www.mailpen.com and web.mailpen.com are my sites) came from:
1. Those that have the word "update" in them, came directly from the B&N site, and when used, should be applied as you normally would for an update.
2. Those that have the word "factory" in them, were directly extracted from partition #3 (the hidden factory restore partition) on the Nook Touch.
In all cases, there are no modifications from me.
What the prior poster did, should have worked. Note that a factory restore (the 8-reset method) does not clear the data partition.
Click to expand...
Click to collapse
how to i clear the data partition before doing a factory restore?
CWM has a selection for formatting partitions.
You could just delete everything using ADB under CWM.
Code:
cd /data
rm -R *
Forgive me if I have a gross misunderstanding about the hardware in the NST, but in my eyes it should be possible for the Nook to sleep but retain the screen, perhaps with a small banner indicating it's in sleep state and you need to press the 'n' to wake. It just seems silly having the benefit of an e-ink display only for the screensaver to kick it when it sleeps. If it didn't do this, I could (for example) leave a map open in OsmAnd and refer to it still while the Nook is sleeping. The only 'solutions' to this I've found involved plain and simply keeping the Nook awake! A hack I can think of would be to somehow bodge something together to take a screenshot just before the nook sleeps and set it as the screensaver image. Seems silly though... I've had a search around and can't find anything related to this specifically, more either people wanting to keep the nook awake or disable the slide to unlock.
Any thoughts welcome!
I had the exact same thought,
so I'm making an app that takes a screenshot every 1:50 minutes and saves it at a screensaver,
to be displayed when the nook goes to sleep.
hopefully it will be ready this weekend so stay tuned
It should be be simple enough.
Modify /system/framework/android.policy.jar
The class is com.android.internal.policy.impl.LockScreen
What puts up the "screensaver" is updateBackgroundImage()
The layout is in /system/framework/framework-res.apk,
res/layout/keyguard_screen_gossamer_unlock.xml
I'm not sure if changing the layout to transparent and not updating the image should be enough.
Renate NST said:
It should be be simple enough.
Modify /system/framework/android.policy.jar
The class is com.android.internal.policy.impl.LockScreen
What puts up the "screensaver" is updateBackgroundImage()
The layout is in /system/framework/framework-res.apk,
res/layout/keyguard_screen_gossamer_unlock.xml
I'm not sure if changing the layout to transparent and not updating the image should be enough.
Click to expand...
Click to collapse
Oh I wish you would have said that two days ago...
It seems a far better solution than my app, maybe I'll try playing with that later.
I tried replacing updateBackgroundImage()
with a stub, but the screensaver still comes up as usual,
Only difference is the "slide to unlock" screen now has black background, so that's what this function is doing.
Time for plan B (or C, really):
If I were to modify framework-res.apk as you suggest, Will I need to resign the whole system, as here?
Update -
The function that sets the screensaver is createScreensaver(), in class com.android.server.PowerManagerService, found in /system/framework/services.jar
I modified it to make the screensaver invisible, but unfortunately it also means there's no indication that the nook sleeps.
Anyway, it's better than constantly taking screenshots, so I'll stick with that.
nivieru said:
Update -
The function that sets the screensaver is createScreensaver(), in class com.android.server.PowerManagerService, found in /system/framework/services.jar
I modified it to make the screensaver invisible, but unfortunately it also means there's no indication that the nook sleeps.
Anyway, it's better than constantly taking screenshots, so I'll stick with that.
Click to expand...
Click to collapse
How did you do that? I'm using the screenshot sreensaver app for that and I find it very useful. But the above mentioned way seems to be less power consuming. Could you explain it for somebody with very little knowledge about manipulating apk, though I know how to manipulate apk with xdaAutotool.
I don't know xdaAutotool, I use apktool but you can probably use whatever tool you like.
First you need a patched /system/framework/services.jar
the one I attached here is for firmware 1.2.1 rooted with NookManager, so it also includes the NookManager patches.
if this is your setup as well, skip to 4
if you run a different firmware or don't want the NookManager patches you will need to patch it yourself
patching /system/framework/services.jar - some vauge instructions:
you will need apktool (or XdaAutotool or whatever) and the android-sdk.
1) use apktool to decompile services.jar
2) modify createScreensaver() in file smali/com/android/server/PowerManagerService.smali according to the attached patch-services.txt
notice - this patch is for firmware 1.2.1 with NookManager patches, it might not be ready for use with other versions - not only the line numbers, also the register v6 might not be a good choice if it is used later in the code without being assigned a new value first.
3) recompile with apktool.
replacing services.jar with patched version - complete instructions:
4) making a full backup before messing with the system is good practice, although the nook is notoriously hard to brick.
you could use NookManager to do the backup.
5) connect to your device with adb
6) apply these commands:
Code:
adb push pathced-services.jar /media
adb shell stop
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell cp /system/framework/services.jar /system/framework/services.jar.backup
adb shell cp /media/pathced-services.jar /system/framework/services.jar
adb shell chmod 644 /system/framework/services.jar
adb shell reboot
7) relax, first boot takes a few minutes, this is normal.
with this patch the screensaver is invisible, so there is no indication at all that the device is asleep.
also, there's no magic button to change behavior - if you want to the screensaver back you need to replace services.jar with original version
Thanks for that extensive description. I'll try the next days to implement it in my system which differs from yours, since I'm using the custom rom from pinguy1982.
Got it.
I compared your PowerManagerService.smali with the one in my services.jar and made the changes.
Recompiled the services.jar.
Exchanged the original classes.dex with the new compiled classes.dex in 7zip.
Signed the jar file.
Had a lot of problems with adb, which didn't recognize my device.
Lost my temper, packed it into a ZIP-file and replaced it via CWM.
Everything is working now. Thanks!
nhedgehog said:
Got it.
I compared your PowerManagerService.smali with the one in my services.jar and made the changes.
Recompiled the services.jar.
Exchanged the original classes.dex with the new compiled classes.dex in 7zip.
Signed the jar file.
Had a lot of problems with adb, which didn't recognize my device.
Lost my temper, packed it into a ZIP-file and replaced it via CWM.
Everything is working now. Thanks!
Click to expand...
Click to collapse
Hi @nhedgehog
I also use the custom rom from pinguy1982.
Can you share your zip file to flash with CWM
Thanks
tebra said:
Hi @nhedgehog
I also use the custom rom from pinguy1982.
Can you share your zip file to flash with CWM
Click to expand...
Click to collapse
Here you are:
Patch (nivieru's method) via ZIP, tested only with modded ROM from pinguy1982 and installed Nooter-Part1.zip. Install via CWM, to be safe make a backup before you do the patch.
Services-org.zip=original services.jar
Services-patch.zip=patched services.jar
Hi everyone!
I've patched the jar and now enjoy the last image in sleep mode. But, I'd like to wake app the Nook every few hours, update the page in dolphin and go back sleep. Page in dolphin has a meta refresh. But I can't wake up the Nook on interval. Is it impossible or I missing smth very important on this topic?
If anybody has some experience on topic, please comment.
Update, my solution:
Re-signed the system with personal cert and implemented an app instead of dolphin+web page.
App wakes up every few hours, updates view and throws device to deep sleep. Hope to get an uptime up to 10-15 days.
nivieru said:
I
replacing services.jar with patched version - complete instructions:
4) making a full backup before messing with the system is good practice, although the nook is notoriously hard to brick.
you could use NookManager to do the backup.
5) connect to your device with adb
6) apply these commands:
Code:
adb push pathced-services.jar /media
adb shell stop
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell cp /system/framework/services.jar /system/framework/services.jar.backup
adb shell cp /media/pathced-services.jar /system/framework/services.jar
adb shell chmod 644 /system/framework/services.jar
adb shell reboot
7) relax, first boot takes a few minutes, this is normal.
with this patch the screensaver is invisible, so there is no indication at all that the device is asleep.
also, there's no magic button to change behavior - if you want to the screensaver back you need to replace services.jar with original version
Click to expand...
Click to collapse
I've done exactly as described in points 4-7 on NST firmware 1.2.1 , rooted with Nook Manager.
I used Root explorer for replacement and rename of patched-services.jar.
After rebooting of NST, it works as intended - the screensaver is unseen, but it appears other problem.
When i click at random .apk, nothing happens, only the screen is flickering once and that's all.
I cannot install apk-s, nor uninstall them....? WTF ?
Someone with explanation...?
gsms said:
I've done exactly as described in points 4-7 on NST firmware 1.2.1 , rooted with Nook Manager.
I used Root explorer for replacement and rename of patched-services.jar.
After rebooting of NST, it works as intended - the screensaver is unseen, but it appears other problem.
When i click at random .apk, nothing happens, only the screen is flickering once and that's all.
I cannot install apk-s, nor uninstall them....? WTF ?
Someone with explanation...?
Click to expand...
Click to collapse
Replacing services.jar while the android system is running can cause problems, that's why I suggest doing it through adb after issuing the "stop" command, which stops android while leaving the underlying linux (with adb) running.
You should try that and see if it helps.
I will try, but before that another question from me.
Is there a chance the file "patched-services.jar" to be remade as .zip file and installed thru CWM.
If this can be done, i will be glad somebody to share the .zip file, because i think it is more comfortable for installation than using adb shell....
thanks
P.S. Adb don't work correctly for me, so the only available option is obviously flashable .zip file...
...
Has anyone tried this with FW 1.2.2 yet?
jptiger said:
Has anyone tried this with FW 1.2.2 yet?
Click to expand...
Click to collapse
If the original services.jar was patched, it will break NTMM since that relies on patches. But if you can discern what the additional patches are you could patch the 1.2.2 file used in NookManager.
Edit: but if you just want to see how it might work, you can probably use the 1.2.1 jar without any problems. When I first started working on the update to NookManager I used the original 1.2.0 jars that were provided with FW 1.2.2 and saw no evidence of problems. A diff showed very minor changes. Depending on how extensive the patching is for this mod, it might be easier--if you still want the use of NTMM--to patch the file in post #8 for NTMM since the patches are well documented on github. Otherwise you have a lot of diffs to look at and sort out.