Related
********Please Mods remove thread if possible!! New Tatuyama fix (ext4) has been incorporated into SuperRooter by DesignGears ********
LINK: http://forum.xda-developers.com/showthread.php?t=751934
DISCLAIMER
DO IT ON YOUR OWN RISK.
ME OR ANYONE ELSE ON THIS FORUM IS NOT RESPONSIBLE FOR BRICKED/DEAD DEVICES AND/OR DEAD SD CARDS.
YOU SHOULD UNDERSTAND EVERY STEP IN THIS HOW-TO BEFORE ATTEMPTING TO FOLLOW.
**********EDIT LOG*******************
8/10/2010: Added Startup Issue Reversion
8/11/2010: Added Alternate Manual Method that might work better than AUTO
8/11/2010: Added Possible Method of Backing EXT2 Partition
Here everyone... I have been trying lag fixes all over the place and I always seem to have issues partitioning the external sd for the apps... so after so many attempts, this was BY FAR the best lag fix out there.... It doesn't rely on the externalsd for functionality.
Easy and nothing special needed.
The steps below are pretty good, but I did things a little different.
Copied the update.zip to my external sdcard.
Then used Root Explorer to copy the update.zip to my internal sd card.
(******Here is the updated filed: http://forum.xda-developers.com/attachment.php?attachmentid=376882&d=1281390347******)
Then I used ROM Manager (Reboot into Recovery) to boot into the Linux Loader
Then I said update using update.zip (not install update.zip)
Then Reboot
For some reason it didn't install busybox 1.17.1 so install it manually
(located: http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229)
Make sure after you install busybox.apk that you go into busybox and check to MAKE SURE you are running 1.17.1 ONLY. You might have an older version or newer version but it must be 1.17.1; if different just click install.
After that follow the MCR Scripts below. (Took about 6 minutes to do everything)
*** If MCR Scripts DOES NOT show up, its probably because you don't have the non market install hack on your phone. In the update.zip you can find the apk and install via ADB, but I didn't do it this way. ******
(Original Thread! Alternate method on OP in link below! Some people say it worked better for them.)
http://forum.xda-developers.com/showpost.php?p=7587405&postcount=417
@Tayutama
I ran the Tayutama update.zip using the up+power+menu button method, it installed in seconds and I restarted the phone. I ran the benchmark but still got 8xx scores. I'm an Noob, so needed more thorough instructions. These are now given below. NOTE: THIS METHOD IS MUCH MORE NOOB FRIENDLY AND DOES NOT REQUIRE A PC OR USB DEBUGGING MODE.
EDIT I had realised I needed to launch the newly installed MCR app after restart and choose a lagfix file to run. I ran the file and 'all complete'. This worked a treat. Ran Quadrant and now have a top score of 2114 running on JM2. System is much snappier. This mod of RyanZA fix by Tayutama is the most noob friendly also. Full instructions as follows:
EDIT Requirements: Make sure your phone has 'superuser' app installed by checking your app list. If it isn't installed, you can use a newer beta version of Tayutama's update.zip
available at; http://forum.xda-developers.com/atta...4&d=1281437129
Full instructions:
1. The update.zip installs all the files needed. It is attached here; http://forum.xda-developers.com/atta...2&d=1281390347
2. Place it on your internal sdcard
3. Turn off your phone.
4. Hold down Up+powerbutton+Menubutton for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it
7. It installs root, correct busybox (1.17.1) as well as all the scripts needed for the fix and the 'MCR Scripts' app to run the scripts. (NOTE: This version does not install superuser.app which is needed, although the beta update.zip does, so read 'requirements' above if needed)
8. After install, the phone restarts.
9. Go to the newly installed 'MCR Scripts' application from the app list, open it and choose from 3 scripts. For example, Lagfix10024 is the 1gb ex2 version.
10. The script should run and take a few minutes.
11. You should see an 'all complete' prompt, and this means you can close the application.
12. Run quadrant to test if the fix was applied.
Originally Posted by Tayutama
Don't know if you mind me posting this here RyanZA, but i made a update.zip out of your script. NOTE THIS ONLY WORKS ON 2.1
What this update.zip file does is that it copies a few files to your internal sdcard and installs ASE which can be used to run .sh files without the need to use a terminal.
There are 3 scripts included:
LagFix1024.sh - Makes a 1GB file on /data
LagFix512.sh - Makes a 512MB file on /data
RemoveFix.sh - Removes the lagfix
This also includes BusyBox 1.17.1 so no need to install that first.
Testet this on JM1
Click to expand...
Click to collapse
********Alternate Method that might even work better!! ****************
All the files are located in the update.zip file that you need to download.
1. Connect phone to PC, make sure adb can see it:
adb devices
2. adb kill-server
3. adb push createlagfix.txt /sdcard/createlagfix.sh
4. adb push playlogos1 /sdcard/playlogos1
5. adb push userinit.sh /sdcard/userinit.sh
6. adb shell su -c "/system/bin/sh /sdcard/createlagfix.sh"
7. adb kill-server
8. adb reboot
************ Reverting back if there are boot up and black screen issues ****************
If you have black screen and doesn't boot into the desktop, this is the fix to return back to normal state:
To fix that problem:
1. Boot into Recovery Mode (Vol Up + Vol Down + Power) Let go of Power after you see AT&T.
2. Delete User Cache
3. Delete All User Data
4. Then see if your phone boots up
5. If your phone does boot up then navigate to Settings -> Security -> Factory Reset
6. After factory reset your phone should be useable again.
DO NOT INSTALL THIS UPDATE IF YOU DO NOT KNOW WHAT YOU ARE DOING.
**********Possible method of Backing up Your EXT2 Partition **********
BTW I would also perform a NANDROID Backup as well which can be done by using ROM Manager to boot into the Android Loader....
Nandroid does NOT back up the apps off your SD card.
AppsToSD (I'm speaking re MoDaCo's rom here) uses the ext2 partition on your SD card for the /data/app and /data/app-private folders, where your actual downloaded application files are kept. Nandroid does NOT back this up, and simply mounting your SD card and copying the files off also does not back this up.
The only way to back up these critical folders is to directly copy them to somewhere else. You can use command line or Droid Explorer.
If you want to use command line, do this from an ADB shell or terminal:
mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
This will create two folders on your SD card: app and app-private, both in a folder called Backup. It will then copy the entire contents of your /data/app and /data/app-private folders to your SD card.
After you do this, back up the entire contents of your SD card as normal.
To restore the files after replacing/partitioning your SD card, head to this thread:
http://forum.xda-developers.com/showthread.php?t=585349
Click to expand...
Click to collapse
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
slider2828 said:
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
Click to expand...
Click to collapse
Does it show strong real world improvements?
good job explaining nothing. troll harder
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
hm... i applied the update in clockwork mod recovery, i have super user and the correct busybox version installed and rebooted the system. i went to the app list and could not find the "MCR SCRIPT" you mentioned i should be seeing... am i doing something wrong?
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
solufein said:
good job explaining nothing. troll harder
Click to expand...
Click to collapse
What the hell does that mean.... You saying it doesn't work? Why not try it and it is an EXT2 fix.
max_warheads said:
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
Click to expand...
Click to collapse
This isn't one step because I don't have the USB cable with me. I just had a USB adapter for the microsd and I can't boot into the linux loader correctly without the cable, so I used ROM Manager. It would have been easier if I did.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Yup it is but on the internal card. Are you sure its the same? Look at the OG thread, a LOT of people have tried it with great success....
darth_vato said:
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
Click to expand...
Click to collapse
How do you back it up?
i updated the zip and rebooted used busy box and i dont have that MCR app
Bionicboto said:
i updated the zip and rebooted used busy box and i dont have that MCR app
Click to expand...
Click to collapse
Same instructions before, did you download the update.zip? I just added that instruction. Can you try again after that?
slider2828 said:
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
Click to expand...
Click to collapse
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
its still the same cant find the app i reboot to recovery apply sd card update.zip go to yes and it says installed reboot and its not there
arsinic said:
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
Click to expand...
Click to collapse
Sorry for the bad reply.
Rename the update.zip that is already on the internal sd cards root because that is ROM Managers using ROOT Explorer
Then copy the update.zip that you downloaded to the external SD card.
Then copy update.zip from the external sd card to the internal sd cards root.
Then use ROM Manager to reboot into the linux loader.
Hope that helps?
-Ken
slider2828 said:
Sorry for the bad reply.
The update.zip that you use download, copy it the the internal sd card's root... (Basically where ROM Manager update.zip was. Like you did Rename the update.zip that is already there, because that is ROM Managers).
Hope that helps?
Click to expand...
Click to collapse
hm... the only update.zip i have is in the Recovery Mod folder named: recovery-update.zip. the only update.zip i have in the sdcard root is the update.zip i downloaded from the your url and have been applying that as the update. i seem to be having the same problem as Bionicboto.
should i have the rom manager's update.zip in there also or it doesn't matter? and i also have no external sd card. is that something i need in order to get this update working properly?
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Basically when I log into root explorer and click on SDCARD.... you should see the update.zip in that folder along with Android folder, busybox folder, clockworkmod folder, DCIM folder, downloads folder, etc etc....
slider2828 said:
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Click to expand...
Click to collapse
i preformed a backup right before i did all this. i did notice the update.zip in there. i took it out and put in the update.zip you uploaded. do i need both in there?
thanks for the quick replies btw.
Nope... Try this... with ROM Manager,
Choose Flash ClockWorkMod Recovery and that will recreate the boot files for ROM Manager.... and also backup your current ROM again.
Then try the steps again.
OMG Dude I noticed you in oakland, I am in hayward/san leandro.... We can try after I get off work which is in 30 minutes. and then take 30 minutes to get back to SL....
You wanna meet at the starbux on marina?
Flashed and installed perfectly. Bumped my quadrant up to 2117. Good post, thanks.
Hey all!
I am new to the NC community, but have quite a bit of experience working with my Samsung Fascinate. I have some minor themeing experience.
Just ordered a NC from ebay for 119 and was curious what sort of setup (ROM, KERNEL) etc are stable and working well?
What OC is stable?
Is Honeycomb worked out as fully functional?
I have done some sticky reading, and I would like to just make a bootable sdcard, and leave the Emmc alone for now.
What are the recommendations?
Thanks!
CM7 is definitely the best for this. Honeycomb did not have access to the sources and so was more of a demo.
We hope that ICS may make it onto the NC one day but for now CM7 gives a really good stable experience.
You can choose to use the latest stable CM 7.1 or choose to use one of the late nightly builds. There has been an issue with what is called SOD (Sleep of death) where the device occasionally doesn't wake up from sleep and needs a reboot. This was an issue even with 7.1 on some devices. It now appears to have been solved but requires an extra patch which should make it into a nightly soon.
Installing onto a boot SD or emmc is both easy tasks and there are plenty of guide material on this. If you are going to boot from SD make sure you use a Sandisk card (e.g. a class 4 16 or 32GB). These give much better performance when used in this role over other brands.
If you end up primarily using CM7 and not reverting to stock then I would say it is worth going full emmc. It is easy to revert to stock if you ever need to. Running from emmc gives more overall memory and makes management and back up more straightforward.
Most Nooks OC fine up to 1300 and remain stable. The boost in performance is fairly dramatic. For some reason some graphics benchmarks peak at 1200MHz and get worse if the OC is pushed higher. I guess the GPU may end up clocking lower if the main clock is pushed too far.
Thanks BOB!
I had used CM7.1 on my fascinate, but it was a short stay as it wouldn't play nice with wifi at my house. Hopefully that's not the case with the NC.
How is MIUI on the NC? From what I see it has done pretty good. Do you have any particular experience with it?
As far as kernels, what are the stable ones by name?
I have plenty of experience of writing ROMS to the internal memory with CWM so I shouldn't be too far off if I need to do that, or choose to go that route.
If you use cm7 can you still use the stock Nook Reader? or what is the reader of choice?
I believe you can only use the Stock reader in the Stock ROM. There is a standard Nook App for Android but it is not the same. Works OK for your standard reading etc but not as nice as the stock reader.
If you want to use the Stock Reader and CM& then I think your choices are ...
1) Run CM7 on the SD card and boot into Stock whenever you want to use the Stock reader.
2) Make a Stock ROM set up on a SD card, Install CM7 on emmc and reverse the procedure of 1.
3) Install a dual boot Stock and CM7 off the emmc. At start up you then choose whether to boot into Stock or CM7 and the SD card remains fully usable as data.
I did use method 3 for a while when I first started with Nook but I so rarely went into stock and I don't really need to access the stock reader that I gave up and redid the emmc as full CM7.
I did try MIUI out but I ended up reverting to standard CM7 really just to keep compatibility with other CM7s I use.
Advantages of Internal Dual boot over SDcard boot?
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
charles_w said:
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
Click to expand...
Click to collapse
I personally would stay away from dual booting on emmc. It plays with your internal partitions which is not a good idea. I would keep stock on emmc and the newly released 7.2-RC1 on SD. By making one simple change to stock you can have both systems share the 32GB card and not have to take the card out ever. The boot menu of CM7 makes it very easy to boot between the two.
Sent from my Nook Color running ICS and Tapatalk
Thanks for the reply.
leapinlar said:
By making one simple change to stock you can have both systems share the 32GB card
Click to expand...
Click to collapse
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
charles_w said:
Thanks for the reply.
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
Click to expand...
Click to collapse
It does have advantages, you don't have to worry about SD card switches, etc. I was just saying it is non-standard and risky to your partitions. One of the partitions, (2) is vital to your system (it has your serial #, etc in it) and since you have to write to the partition table to accomplish dual boot, you risk the possibility of corrupting it as you are setting up dual boot. But a lot of people have done it with no problem.
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file. But there are plenty of rooting threads that tell you how. You can even unroot after you have fixed the file if you want. The other way is to change the file on your PC using adb. Both methods take a little extra effort, but it is worth it to not have to swap SD cards all the time. Both systems then share the SD card storage area. By making this change, I know of no advantage to dual boot and it is much safer (and you already have the SD set up).
And you use the boot menu to select which operating system you want to boot to. That comes with CM7. (But you know that having run CM7 for a year).
Sent from my Nook Color running ICS and Tapatalk
found the link for sharing sdcard
leapinlar said:
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file.
Click to expand...
Click to collapse
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmx to be rooted.
Charles
Click to expand...
Click to collapse
good job!
Sent from my Nook Color running ICS and Tapatalk
charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
Click to expand...
Click to collapse
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
The free version of ES Explorer allows mounting system as r/w.
Little update....
I have found that the best setup I have found so far is CM 7.2 RC1 (03042012) with V6 (Update 9 RC6.9) supercharger set to option 9 (super 1000HP) supercharge (link for the V6 is on Mr666's page). The ICS transitions included in RC1 are swift and with the supercharger everything is super smooth. I can say I have noticed a small increase in my battery life as well. I toyed around with the UV/OC settings and returned to the sleep of death's I was getting on 7.1. So I re-flashed and just have left everything set to default in the peformance settings that comes with 7.2. So far, no SOD"s and I have a very capable tablet.
leapinlar said:
The free version of ES Explorer allows mounting system as r/w.
Click to expand...
Click to collapse
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
You don't need to mount it where racks said. You can mount it in /data, which you should be able to make r/w. Where it says /mnt/nooksys, substitute /data/nooksys. First go to /data with es explorer and manually create the nooksys folder (you need to set your home directory to / in es explorer before you can see /data). Then follow his steps except don't do the mkdir command since you did it manually. And wherever it says /mnt substitute /data.
Edit: you need to modify the mount command, it now needs to have appended to the end, -t ext4. - Scratch that. It's only necessary if you are trying to do it from CM9. CM7 works OK as written.
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Sherip said:
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
What is the -o in the line for? And you manually created the folder first? And you did check the root button in settings?
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Sherip said:
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Click to expand...
Click to collapse
After you created the folder, did you check it. By that I mean open it? It should be an empty folder. Exit out of the folder, but leave Es explorer open. Use the home key to get back to home screen so you can open terminal. I don't know much about es, maybe it has to stay open to keep root access.
Edit: the :not found error is saying it cannot understand the mount command. Are you using all lower case? Very important. Terminal does not like upper case.
Hi All,
I set out to flash my tablet back to stock with the goal of copying some of the awesome asus-specific widgets and applications and installing them back on my tablet after I re-rooted/modded it. I accomplished part of this goal by finding some of the .apk's I wanted, like the Asus weather & battery widgets, the Supernote.apk, anda few others (I still wasn't able to find the Swype Keyboard.apk file)
Anywho, I tried to install the .apk's on my tablet after re-installing cm9 and rooting it but it just says "Application not installed". Anyone have any ideas? And can anyone elaborate on how to copy that swype keyboard APK that I desperately want? I found the other .apk's in the /system/app folder but swype wasn't there.
My other questions relate to CM9:
1) is there any way to decrease the boot time for CM9, or at least customize the boot screen?
2) I'm currently running an older version of cm9 (rc0 unofficial) and I have the stable rc1 of cm9 but when i tried to flash it, it didn't work (i can get the exact error message if needed). Did I do something wrong in updating or is RC1 not compatible with the device? Should I just wait till CM10 comes out?
3) When I initially rooted/flashed cm9, I was able to connect my tablet to my computer and the root of the / directory, but after flashing stock and trying again, I don't have the same luck. Is there some step I missed?
I appreciate any responses, thanks.
- Opethfan89
3 days, 300 views, no responses. BUMP anyone?
opethfan89 said:
Hi All,
I set out to flash my tablet back to stock with the goal of copying some of the awesome asus-specific widgets and applications and installing them back on my tablet after I re-rooted/modded it. I accomplished part of this goal by finding some of the .apk's I wanted, like the Asus weather & battery widgets, the Supernote.apk, anda few others (I still wasn't able to find the Swype Keyboard.apk file)
Anywho, I tried to install the .apk's on my tablet after re-installing cm9 and rooting it but it just says "Application not installed". Anyone have any ideas? And can anyone elaborate on how to copy that swype keyboard APK that I desperately want? I found the other .apk's in the /system/app folder but swype wasn't there.
My other questions relate to CM9:
1) is there any way to decrease the boot time for CM9, or at least customize the boot screen?
2) I'm currently running an older version of cm9 (rc0 unofficial) and I have the stable rc1 of cm9 but when i tried to flash it, it didn't work (i can get the exact error message if needed). Did I do something wrong in updating or is RC1 not compatible with the device? Should I just wait till CM10 comes out?
3) When I initially rooted/flashed cm9, I was able to connect my tablet to my computer and the root of the / directory, but after flashing stock and trying again, I don't have the same luck. Is there some step I missed?
I appreciate any responses, thanks.
- Opethfan89
Click to expand...
Click to collapse
I haven't tried this, but it may work. If you have ADB on your computer, try doing an adb push [name of file].apk /system/app/
If you can't do that, try copy/pasting them there using a root explorer on your device itself. Make sure the permissions are set properly (I don't remember what they are off the top of my head).
After doing that, reboot. See if it works.
As for your CM Questions:
1) I'm not sure if you can reduce the time. For customizing the animation, look at something like Rom Toolbox Pro (which also includes a root explorer like I mentioned above).
2) All CM9 TF300T downloads are located here: http://get.cm/?device=tf300t RC1 is listed there so I'm assuming you did something wrong (what's the error you get?)
3) Did you re-root? I'm not sure I understand.
Link9228 said:
I haven't tried this, but it may work. If you have ADB on your computer, try doing an adb push [name of file].apk /system/app/
If you can't do that, try copy/pasting them there using a root explorer on your device itself. Make sure the permissions are set properly (I don't remember what they are off the top of my head).
After doing that, reboot. See if it works.
As for your CM Questions:
1) I'm not sure if you can reduce the time. For customizing the animation, look at something like Rom Toolbox Pro (which also includes a root explorer like I mentioned above).
2) All CM9 TF300T downloads are located here: http://get.cm/?device=tf300t RC1 is listed there so I'm assuming you did something wrong (what's the error you get?)
3) Did you re-root? I'm not sure I understand.
Click to expand...
Click to collapse
I apologize for the vagueness of my original post. I made this thread in anticipation of flashing everything back to stock, trying to copy over those Asus-specific .apk's (which I managed to do), and then re-rooting/re-flashing CM9.
I flashed the .30 firmware to get back to stock and found the Asus widgets & apk's I was looking for in the /system/app directory. After some bootloops and other fun, I was able to flash back to CM9 and when I tried to install the .apk's I immediately get the message "The Application was not installed"
Of the asus items I wanted, Supernote and Polaris Office were my top two picks, and I was able to acquire Supernote through 3-rd party means and install it. So I'm stoked to have Supernote on a CM9-flashed tablet. I wasn't able to find Polaris Office so I hope to at least be able to find a work-around to install that.
In response to #3 - yes I re-rooted my tablet (lost root with the .30 firmware) and previously I was able to browse the root directory of my tablet while it was connected to my computer. Now, I can only browse the SD card. I still haven't figured out a solution to this, but I just transfer files to my memory card and then to my tablet from there. I'm looking into how to do OTA file transfers via bluetooth or wi-fi, if at all possible.
opethfan89 said:
I apologize for the vagueness of my original post. I made this thread in anticipation of flashing everything back to stock, trying to copy over those Asus-specific .apk's (which I managed to do), and then re-rooting/re-flashing CM9.
I flashed the .30 firmware to get back to stock and found the Asus widgets & apk's I was looking for in the /system/app directory. After some bootloops and other fun, I was able to flash back to CM9 and when I tried to install the .apk's I immediately get the message "The Application was not installed"
Of the asus items I wanted, Supernote and Polaris Office were my top two picks, and I was able to acquire Supernote through 3-rd party means and install it. So I'm stoked to have Supernote on a CM9-flashed tablet. I wasn't able to find Polaris Office so I hope to at least be able to find a work-around to install that.
In response to #3 - yes I re-rooted my tablet (lost root with the .30 firmware) and previously I was able to browse the root directory of my tablet while it was connected to my computer. Now, I can only browse the SD card. I still haven't figured out a solution to this, but I just transfer files to my memory card and then to my tablet from there. I'm looking into how to do OTA file transfers via bluetooth or wi-fi, if at all possible.
Click to expand...
Click to collapse
So did you try what I suggested in my post (pushing the files to /system/app on your tablet, rather than trying to install them through File Browser or whatever)?
I'm not sure if they rely on any custom Asus framework stuffs, like with many other OEMs. I personally doubt it because Asus barely changes anything. I think it *should* work, but can't guarantee it.
The easiest way to get the files to /system/app (if you're not very ADB or tech. savvy) is to download a root explorer (like Rom Toolbox Pro has, for example) and copy all the .apks that you want from your sdcard to /system/app.
Link9228 said:
So did you try what I suggested in my post (pushing the files to /system/app on your tablet, rather than trying to install them through File Browser or whatever)?
I'm not sure if they rely on any custom Asus framework stuffs, like with many other OEMs. I personally doubt it because Asus barely changes anything. I think it *should* work, but can't guarantee it.
The easiest way to get the files to /system/app (if you're not very ADB or tech. savvy) is to download a root explorer (like Rom Toolbox Pro has, for example) and copy all the .apks that you want from your sdcard to /system/app.
Click to expand...
Click to collapse
I haven't tried pushing the files via ADB yet. I just wiped out my computer so I need to re-install the drivers to get the tablet recognized and/or the the Android SDK.
In the 3rd point of your point, do you mean my external SD card or the internal memory?
the Transformer Pad has a good portion of internal memory partitioned as an sdcard and mounts it at /sdcard/. I haven't used an external SD card with my tablet yet. Either one should work.
I also found out that Polaris Office has some library files that you probably should grab as well. You can find them at:
/system/lib/libpolarisoffice_tablet.so
/system/lib/libpolarisofficedump.so
/system/lib/libtfapps-polaris.so
/system/lib/libtflua-polaris.so
Click to expand...
Click to collapse
There might be some library files for the other apps. You might want to look around in the /system/lib folder for other libraries as well.
Link9228 said:
the Transformer Pad has a good portion of internal memory partitioned as an sdcard and mounts it at /sdcard/. I haven't used an external SD card with my tablet yet. Either one should work.
I also found out that Polaris Office has some library files that you probably should grab as well. You can find them at:
There might be some library files for the other apps. You might want to look around in the /system/lib folder for other libraries as well.
Click to expand...
Click to collapse
That's awesome, thanks. If I'm able to get this working I will post a guide for others to follow. I ended up just signing up for the swype beta (which I think is stupid since I paid for that app when I bought my tablet, shouldn't have to get a reduced version)
I was able to find a working supernote.apk app on a 3rd-party website and it installed and worked perfectly.
My other issue I'm having is I try to push the files with ADB and it tells me my tablet is read-only? it gives that same message no matter which directory I try to push to. I have the superuser app and have root, but superusers' log shows the 'adb shell' is consistently being denied root permission (if i try to do su or something similar). Any thoughts?
opethfan89 said:
That's awesome, thanks. If I'm able to get this working I will post a guide for others to follow. I ended up just signing up for the swype beta (which I think is stupid since I paid for that app when I bought my tablet, shouldn't have to get a reduced version)
I was able to find a working supernote.apk app on a 3rd-party website and it installed and worked perfectly.
My other issue I'm having is I try to push the files with ADB and it tells me my tablet is read-only? it gives that same message no matter which directory I try to push to. I have the superuser app and have root, but superusers' log shows the 'adb shell' is consistently being denied root permission (if i try to do su or something similar). Any thoughts?
Click to expand...
Click to collapse
You need to remount your system as read-write. Trying doing an adb remount. If that doesn't work, try typing the following into a terminal emulator:
su
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
Try ADB pushing again after that.
if you are able to install the apps by adb push. then maybe a .zip file can be created and use CWM to install all the stock apps.
Link9228 said:
You need to remount your system as read-write. Trying doing an adb remount. If that doesn't work, try typing the following into a terminal emulator:
Try ADB pushing again after that.
Click to expand...
Click to collapse
Well part of the issue is that I can't "su" while in adb shell. It says permission denied. When I type ADB devices normally, it'll list my device. But when I'm in "adb shell" it doesn't show anything. "adb remount" gives me the message "error: device not found".
Any other suggestions?
opethfan89 said:
Well part of the issue is that I can't "su" while in adb shell. It says permission denied. When I type ADB devices normally, it'll list my device. But when I'm in "adb shell" it doesn't show anything. "adb remount" gives me the message "error: device not found".
Any other suggestions?
Click to expand...
Click to collapse
That's weird. I've never seen that before. Are you certain that your adb drivers are installed properly? You can always use a terminal emulator on your device itself to remount the system as read/write and then use adb afterwards.
Link9228 said:
That's weird. I've never seen that before. Are you certain that your adb drivers are installed properly? You can always use a terminal emulator on your device itself to remount the system as read/write and then use adb afterwards.
Click to expand...
Click to collapse
I'm pretty sure my drivers are installed correctly. Everything shows up in device manager, "adb devices" lists my device, fastboot flashes files just fine, so yea.
And yea I have the terminal emulator on my tablet and I've used it before for some stuff (installing Ubuntu) so I will try the steps you guys have mentioned. I'm in the process of trying out some other ROM's right now (Hydro atm, and then probably CleanROM) so once I go back to stock and have access to the appropriate files I'll try these steps.
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
**Removed - wait for JCSullins official release**
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
For those not in the know, it is recommended to update your recovery and essential if you plan to update to cm10. This fixes s file system corruption bug that shows up when expanding the partition in preparation for cm10.
Sent from my HP TouchPad using Tapatalk 2
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
"Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here."
Click to expand...
Click to collapse
Open terminal
type
su
umount -o remount,rw /boot
then use es file explorer.
chadster1976 said:
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
Click to expand...
Click to collapse
Rom Toolbox lite will allow you to .
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
I flashed it and now I'm soft bricked. Can't boot into sk8's CWR6, CM10 or anything.
Lesson learned, ask developers before posting there work
Sent from my Galaxy Nexus using xda app-developers app
It likely not the CWM6 that did it but the boot partition full. If you have an extra webos kernel, some moboot themes, TWRP, and then this new larger uImage for CWM you will likely run out of space.
Probably should put that warning here it's pretty important people realize it and/or add a script to remove TWRP, to prevent issues with this zip.
@jcsullins +1 Feedback. Installed your CWM uImage manually. Mounted as mass storage in CWM, copied files, Installed latest CM10 12/05(over older CM10 installed with Acme3), Installed Gapps, Installed Camera Preview 3 patch, Installed WEBCM10, cleared both caches in CWM and noticed no issues during all the processes.
I ACMEU wiped and ACME3'd the whole deal back on w/new recovery. It needed the clean up anyways and I had a NAND from yesterday.
Nice, thanks JC.
Roland Makes oopsy
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Thank you for taking the time to create this great new CWM6. I have been really enjoying the new looks and graphics. I have tested flashing different zips and Roms. I have made and restored Nandroid backups and even restored older CWM5 backups with CWM6. I do this to try and help but sometimes I really step in $#@# trying to help, like with the 4.2gapps.
Sorry about being so anxious to get this out to the public. I have had a lot of complaints about Bricked TouchPads and would like to get the word out about the problem and how to fix/prevent it.
I feel very responsible for the people affected due to me making an install video without knowledge of the corruption issue beforehand.
I wanted to make a video explaining that there was an issue but to fix it they can, Backup, uninstall, reinstall and restore. To prevent future issues I want to included this in my install instructions. They would of course need your New CWM6 to do this and I have been eagerly awaiting this fix.
Sorry about all my stupid mistakes, I get a bit over excited about Tech stuff at times. Please accept my sincerest apologies.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
I'm sorry, but I didn't see your post in Rootzwiki or I would have posted there.
This cwm has worked flawlessly. I haven't had a chance to try all the new features, but the ones I did try worked fine.
Thanks so much for this. The old 5.0.2.6 was starting to show its age. I hope this cwm does away with the sporadic partitioning problems I'd been seeing.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
New Backup Options
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
webdroidmt said:
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
Click to expand...
Click to collapse
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
RolandDeschain79 said:
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
Click to expand...
Click to collapse
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
.dup & .tar enlightenment
webdroidmt said:
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
Click to expand...
Click to collapse
Thank you very much for the detailed response. I’m feeling good now that I am starting to understand the new recovery. I also really liked having those individual .tar backups:good:, I made one for each version of CM. I wonder how .dup backups will affect the free space on my device. I also backup a lot but I did find that i was able to restore the older CWM5 backups without a problem. I will probably just keep the older CWM5 .tars for CM7, CM9 and do my CM10 backing up with the newer .dup. Time to transfer some backups:victory:
Can we maybe get rid of the link in op? Jc has stated this was only for testing, you shouldn't host a devs work without permission, and maybe for the fact of it will soft brick a TP? Just saying....
Sent from my HTC VLE_U using xda app-developers app
Sorry for possibly misunderstanding but is it recommended to use this yet due to possible corruption issues with older versions of CWM or only intended for testing atm? I've been meaning to ACME uninstall the TP and reinstall CM10 clean again and if this newer version of recovery is recommended for flashing I'll throw it on there while I'm at it
Thx JCSullins! :fingers-crossed:
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Hello,
Sorry for that :/
I haven't seen your rootzwiki post and so far I was just willing to help users to install it
easily (seems that was my mistake :x) because after I gave it a try it solved the issues
I was having with the previous CWM one. There is just one thing that disturb me, in
Backup and Restore menu, 'choose backup format' should be rename in something like
"choose default backup format".
That's just my 2cents and besides this all functions work well, thanks for your hard work.
I'll remove the link from the OP post and wait for your public release
Sincerely, menthe.
Has anyone tried the adb sideload yet?
When attempting to sideload I get: * failed to write data 'protocol fault (no status)' *
Any other adb commands I issue are met with "error:closed"
I am stuck here because I don't have a power button to do a hard reset... please someone tell me this function is working and I am just doing something wrong. My TP has a full charge and I don't feel like waiting 8hrs for it to die so it can be reset.
Edit: just took the whole thing apart and pulled the battery
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 *