Related
See: http://forum.xda-developers.com/showthread.php?t=1402440
Sorry - don't have enough posts to reply directly in the dev tree, but it would seem to me that if all the updates are just zip files, couldn't they be modified to include root? Then the normal update system would handle the installation? You wouldn't need root then.. Just dump it into the "kindleupdates" folder and let it do its thing. It would just install it.
It looks like the install is just running a script.. one of the first things it does is wipe the system folder.. doesn't mean you can't include additional files and copy them in afterwards with the script does it?
AndrewTL said:
See: http://forum.xda-developers.com/showthread.php?t=1402440
Sorry - don't have enough posts to reply directly in the dev tree, but it would seem to me that if all the updates are just zip files, couldn't they be modified to include root? Then the normal update system would handle the installation? You wouldn't need root then.. Just dump it into the "kindleupdates" folder and let it do its thing. It would just install it.
It looks like the install is just running a script.. one of the first things it does is wipe the system folder.. doesn't mean you can't include additional files and copy them in afterwards with the script does it?
Click to expand...
Click to collapse
You need to go through all the lines of code for that and I believe some of them are binary files as well. Possible but will take much time. For now we must wait until someone finds a better solution.
Sent from my Kindle Fire using Tapatalk
signature issues.
6.2.1 experiment?
transfuntioner said:
signature issues.
Click to expand...
Click to collapse
Maybe I don't follow the process.. but I'm guessing no signatures..
not a signed bootloader.. no signatures required...
Get beyond compare and look at the differences between the OTA updates and the zip that Eldarerathis put together.
The ".bin" files are just ".zip" files renamed.
Look at
META-INF/com/google/android/updater-script in the bin files they release.
It is just a script.
And to do the things that it is doing, it has to be getting root permissions while it is running.
I don't know how to recover if it doesn't work, but I half wonder if you were to take the zip that fellow created, change the extension to ".bin" and just dump it into the update folder if the fire would install it for you?
He took out the image files from the script. He's just updating the system tree directly. He doesn't update the bootloader, recovery or backup trees.
For that matter if those contained something nasty, they could probably be pulled from an earlier update.
== cut ===
package_extract_file("recovery.img", "/dev/block/platform/mmci-omap-hs.1/by-name/recovery");
show_progress(0.100000, 10);
package_extract_file("u-boot.bin", "/dev/block/platform/mmci-omap-hs.1/by-name/bootloader");
format("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/backup");
mount("ext4", "EMMC", "/dev/block/platform/mmci-omap-hs.1/by-name/backup", "/backup");
package_extract_file("backup_userdata.zip", "/backup/backup_userdata.zip");
== cut ===
Please nobody try this idea that doesn't know enough to recover if it doesn't work, because I've not a clue how.
But could someone explain why wouldn't it work?
Worst case the rev might need to be manually edited to bump it one for the script.
Seems like it might be an easy way to get around headaches with OTA updates.
Andrew,
Are you having issues with getting into recovery so that you can test this? The Devolopers have a copy of TWRP 2 working perfectly on the device so you can get a clean backup of the OS before you test.
You sound like you may know what to do to fix the issue and I just want to help you get a good recovery in case it doesn't pan out or for testing.
~enjoy.
Actually I'm just afraid of messing up what I have working now.
I've got TWRP 2 running with the 6.2.1 image.
I'm setting these up as gifts. I spent a good 12 hours yesterday fighting the darn things. Guess I'm getting gun shy. Had a lot of issues with adb. Kudos to the new utility and setting the second ports up. I'm learning.
The OTA install wipes the system directory. It's in the script.
I was tempted to just comment that line out and see if it would leave the rest alone.
If I brick the thing its going to be painful for me to sort out.
I also didn't want to risk losing root. I also haven't tried loading an older OTA version.
At the time, I couldn't ask the fellow that developed the rooted 6.2.1 zip the question in his thread as I didn't have enough posts.
I'm going to be out of pocket for quite some time. I'm not going to have time to spend like this again for at least a few days.
But I was checking the zip he made versus the .bin/.zip files that the OTA releases using beyond compare. I wanted to see what files had actually changed.
That's when I found that script. It is manipulating permissions directly. It has to be running at a root level. I don't see anything like a signature on it, so why couldn't their own update system be used to tweak their own updates to allow for root?
Just to add to the list - this is what I had to do to get my Thinkpad to update.
I was rooted, and had CWR installed. I downloaded the ICS update from Lenovo's Website (http://download.lenovo.com/slates/think/tablet1) file was (http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_03_0069_0130_US.zip). I was getting an indigo check error right away though when trying to flash.
I knew that I had to update the updater-script from META-INF\com\google\android\ in the zip file. Ultimately I totally removed the following lines from it:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_US:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0130_US:user/release-keys");
assert(getprop("ro.product.device") == "Indigo" ||
getprop("ro.build.product") == "Indigo");
I first tried doing this with Notepad++ on windows and ultimately got an error 6 when trying to flash. Luckily I have an Ubuntu (a type of linux) machine laying around and was able to edit the file within the zip using Ubuntu. I copied the ThinkPadTablet_A310_03_0069_0130_US.zip to my network, opened it up in Ubuntu, navigated to META-INF\com\google\android\ and opened updater-script. After removing those lines listed above, I closed out of Gedit and had a prompt asking if it should update the zip. I hit yes and that is the file that worked for me. If you don't have access to a linux machine it may be easy enough for you to make a live CD (https://help.ubuntu.com/community/LiveCD) that will allow you to boot into Ubuntu and not affect the OS of your computer. You could put your update zip file on a thumbdrive, boot the live cd, and edit it that way. Ubuntu is free and everything you need to update your zip should be included on the live CD (zip utility and a text editor).
With my new edited update.zip I started to flash, got much further and then bombed on busybox. I got the busybox file from this post (http://forum.xda-developers.com/showthread.php?t=1741623) file was (http://dl.dropbox.com/u/6846397/Original/busybox). I copied to my thinkpad and moved it to /system/xbin using Root Explorer (I've been an Android user since the G1 and made it this far without Root Explorer but bought it just for this - that App works great and you should get it). If you get an error that you can't write the file hit the Mount R/W at the top (and its always a good idea to rename the original so you have a backup).
At this point I backed up root with Voodoo OTA Rootkeeper, disabled root, rebooted into CWM and flashed my update. Finally things went smooth, i rebooted into ICS and used Voodoo Root Keeper to restore root.
Something else to note is that if you have a root file explorer (and root) you can browse to /cache/recovery and open the last_log file if you are still getting tripped up to see what is failing.
Now I am updated to ICS, restored root, and lost CWM. Hope this helps some of you guys that are stuck. What a pain this was.
karlherr said:
Just to add to the list - this is what I had to do to get my Thinkpad to update.
I was rooted, and had CWR installed. I downloaded the ICS update from Lenovo's Website (http://download.lenovo.com/slates/think/tablet1) file was (http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_03_0069_0130_US.zip). I was getting an indigo check error right away though when trying to flash.
I knew that I had to update the updater-script from META-INF\com\google\android\ in the zip file. Ultimately I totally removed the following lines from it:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_US:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0130_US:user/release-keys");
assert(getprop("ro.product.device") == "Indigo" ||
getprop("ro.build.product") == "Indigo");
I first tried doing this with Notepad++ on windows and ultimately got an error 6 when trying to flash. Luckily I have an Ubuntu (a type of linux) machine laying around and was able to edit the file within the zip using Ubuntu. I copied the ThinkPadTablet_A310_03_0069_0130_US.zip to my network, opened it up in Ubuntu, navigated to META-INF\com\google\android\ and opened updater-script. After removing those lines listed above, I closed out of Gedit and had a prompt asking if it should update the zip. I hit yes and that is the file that worked for me. If you don't have access to a linux machine it may be easy enough for you to make a live CD (https://help.ubuntu.com/community/LiveCD) that will allow you to boot into Ubuntu and not affect the OS of your computer. You could put your update zip file on a thumbdrive, boot the live cd, and edit it that way. Ubuntu is free and everything you need to update your zip should be included on the live CD (zip utility and a text editor).
With my new edited update.zip I started to flash, got much further and then bombed on busybox. I got the busybox file from this post (http://forum.xda-developers.com/showthread.php?t=1741623) file was (http://dl.dropbox.com/u/6846397/Original/busybox). I copied to my thinkpad and moved it to /system/xbin using Root Explorer (I've been an Android user since the G1 and made it this far without Root Explorer but bought it just for this - that App works great and you should get it). If you get an error that you can't write the file hit the Mount R/W at the top (and its always a good idea to rename the original so you have a backup).
At this point I backed up root with Voodoo OTA Rootkeeper, disabled root, rebooted into CWM and flashed my update. Finally things went smooth, i rebooted into ICS and used Voodoo Root Keeper to restore root.
Something else to note is that if you have a root file explorer (and root) you can browse to /cache/recovery and open the last_log file if you are still getting tripped up to see what is failing.
Now I am updated to ICS, restored root, and lost CWM. Hope this helps some of you guys that are stuck. What a pain this was.
Click to expand...
Click to collapse
At least you have official ICS, we K1 users have been lied to and have been waiting a month for ICS (the 3rd time around) because of some stupid but easy installation of the Play Store.
Thanks karlherr!
karlherr said:
Just to add to the list - this is what I had to do to get my Thinkpad to update.
I was rooted, and had CWR installed. I downloaded the ICS update from Lenovo's Website (http://download.lenovo.com/slates/think/tablet1) file was (http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_03_0069_0130_US.zip). I was getting an indigo check error right away though when trying to flash.
I knew that I had to update the updater-script from META-INF\com\google\android\ in the zip file. Ultimately I totally removed the following lines from it:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_US:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet_A400_03/0069_0130_US:user/release-keys");
assert(getprop("ro.product.device") == "Indigo" ||
getprop("ro.build.product") == "Indigo");
I first tried doing this with Notepad++ on windows and ultimately got an error 6 when trying to flash. Luckily I have an Ubuntu (a type of linux) machine laying around and was able to edit the file within the zip using Ubuntu. I copied the ThinkPadTablet_A310_03_0069_0130_US.zip to my network, opened it up in Ubuntu, navigated to META-INF\com\google\android\ and opened updater-script. After removing those lines listed above, I closed out of Gedit and had a prompt asking if it should update the zip. I hit yes and that is the file that worked for me. If you don't have access to a linux machine it may be easy enough for you to make a live CD (https://help.ubuntu.com/community/LiveCD) that will allow you to boot into Ubuntu and not affect the OS of your computer. You could put your update zip file on a thumbdrive, boot the live cd, and edit it that way. Ubuntu is free and everything you need to update your zip should be included on the live CD (zip utility and a text editor).
With my new edited update.zip I started to flash, got much further and then bombed on busybox. I got the busybox file from this post (http://forum.xda-developers.com/showthread.php?t=1741623) file was (http://dl.dropbox.com/u/6846397/Original/busybox). I copied to my thinkpad and moved it to /system/xbin using Root Explorer (I've been an Android user since the G1 and made it this far without Root Explorer but bought it just for this - that App works great and you should get it). If you get an error that you can't write the file hit the Mount R/W at the top (and its always a good idea to rename the original so you have a backup).
At this point I backed up root with Voodoo OTA Rootkeeper, disabled root, rebooted into CWM and flashed my update. Finally things went smooth, i rebooted into ICS and used Voodoo Root Keeper to restore root.
Something else to note is that if you have a root file explorer (and root) you can browse to /cache/recovery and open the last_log file if you are still getting tripped up to see what is failing.
Now I am updated to ICS, restored root, and lost CWM. Hope this helps some of you guys that are stuck. What a pain this was.
Click to expand...
Click to collapse
Thanks this worked very well! I'm late to the ICS party and spent hours reading through the various forums today before happening upon your post. I followed your advice pretty much to the letter except that I found that I could get the same results in windows 7 without having to go to linux. There is a gedit for windows at http://ftp.gnome.org/pub/gnome/binaries/win32/gedit/ . I used 7Zip, with gedit selected as the editor. I was able to open the ICS update.zip in 7Zip, edit out the indigo entry, and save the zip. Worked except that updater couldn't find notesmobile_len-oem.apk in system\apps though it was installed. Pulled that from http://forum.xda-developers.com/showthread.php?t=1243218 (thanks WyldStyl3) and then the update went through.
Need Help wit CWM Install
I have the US version Thinkpad running 4.0.3. I have successfully rooted the tablet. I have searched endlessly and tried many times to install CWM so I can eventually get Jellybean installed. Can you help with some simple instructions on how to install CWM.
You might want to look at Koshu's threads:
CWM: http://forum.xda-developers.com/showthread.php?t=1831161
CM10: http://forum.xda-developers.com/showthread.php?t=1846044
Thanks
Thanks for the links. Have read hundreds of threads but did not see any instructions on how to activate the PEN ONLY FUNCTION on the Lenovo Thinkpad US Version Running the rooted Jellybean. But I figured it out on my own. Here is how in case anyone else is interested.
1. Make sure your hardware buttons at the bottom edge are turned on.
2. TOggle the second button from the left and it changes from "touch screen off to on.
Then you can use your pen when the touch screen is off.
Thank you very much for this detailed and COMPLETE instruction set
I was crawling threads on various forums for three days now, and finally I am able to run the update.
Good work, u saved my weekend
Greetings from Austria,
norkarnt
Your welcome
Yea I know how frustrating that search was. Glad to help. By the way the 4.1.2 is great and clears all of the Lenovo useless and unsupported apps from the:good: tablet. You will have to purchase the full version of Docs To Go however. And Writepad is a good substitute for Notes Mobile.
Tim
norkarnt said:
Thank you very much for this detailed and COMPLETE instruction set
I was crawling threads on various forums for three days now, and finally I am able to run the update.
Good work, u saved my weekend
Greetings from Austria,
norkarnt
Click to expand...
Click to collapse
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
Hi,
I have a Nook Simple Touch, updated to UK version 1.2.1, and rooted using NookManager 0.5.0 with the NTGAppsAttack package.
I have installed the NoRefresh apk and am now looking to add the Multitouch mod, but I would want to keep the device's primary use for reading ebooks (so wouldn't want to loose quality there), and I wouldn't want to accidentally re-root it.
Therefore, would either of these be the right method to use, or is it possible to patch without replacing the kernel please?
http://forum.xda-developers.com/showthread.php?t=1906507
http://forum.xda-developers.com/showthread.php?t=1568560
I've found a few articles relating to multi-touch, but they seem to concern TouchNooter and NST firmware 1.1; hence why I'd like to double check before I try anything.
Cheers,
I went ahead and tried installing the multitouch.zip from a clockwork recovery image card, despite not being sure if it was even compatible with NookManager, and it said Installing and went through a process, but the device still doesn't support multitouch. At least it didn't kill it though
Could someone please point me in the right direction for adding multi-touch to a NookManager rooted NST please? I just can't seem to find the right method.
Donna80 said:
I went ahead and tried installing the multitouch.zip from a clockwork recovery image card, despite not being sure if it was even compatible with NookManager, and it said Installing and went through a process, but the device still doesn't support multitouch. At least it didn't kill it though
Could someone please point me in the right direction for adding multi-touch to a NookManager rooted NST please? I just can't seem to find the right method.
Click to expand...
Click to collapse
I'm using this kernel and it supports multitouch - http://forum.xda-developers.com/showthread.php?t=1906507 (build 174). It's not always obvious that multitouch is actually supported. So far I've only had pinch to zoom work in Opera Mobile and ADW, but it does work.
noodles2k said:
I'm using this kernel and it supports multitouch - http://forum.xda-developers.com/showthread.php?t=1906507 (build 174). It's not always obvious that multitouch is actually supported. So far I've only had pinch to zoom work in Opera Mobile and ADW, but it does work.
Click to expand...
Click to collapse
Another noob question -- I tried using Win32DiskImager to drop the uImage.img which that other thread contains onto an SD card, and then power-cycled my Nook with that card in place, but I saw no sign of an install -- is there any way to confirm that the install happened? Is that in fact the right way to attempt the install?
The uImage.img is not in fact an image that should be burned to an SD card. The file should actually be renamed to uImage and put in /boot. You either need a CWM-flashable zip or you can do it with adb (adb is quicker IMO since I don't have to prepare a CWM SD card).
Get ADB here:
http://forum.xda-developers.com/showthread.php?t=1474956
uImage instructions:
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
Kralik said:
The uImage.img is not in fact an image that should be burned to an SD card. The file should actually be renamed to uImage and put in /boot. You either need a CWM-flashable zip or you can do it with adb (adb is quicker IMO since I don't have to prepare a CWM SD card).
Get ADB here:
http://forum.xda-developers.com/showthread.php?t=1474956
uImage instructions:
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
Click to expand...
Click to collapse
Ah, thanks, that makes sense. In the meantime I achieved success by booting ClockwordMod and using it to install the 174 zip in its entirety. Multitouch now working, also fastmode, although the latter seems to cause glitching in CoolReader (but not in Nook Reader). . .
HELP!!!!
Kralik said:
The uImage.img is not in fact an image that should be burned to an SD card. The file should actually be renamed to uImage and put in /boot. You either need a CWM-flashable zip or you can do it with adb (adb is quicker IMO since I don't have to prepare a CWM SD card).
Get ADB here:
http://forum.xda-developers.com/showthread.php?t=1474956
uImage instructions:
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
Click to expand...
Click to collapse
Men I try very few time to upgrade trought this method and the result is always the same, a complete failure . In the console mode when I try to push the uImage in the /media directory the message is "cannot stad ´uImage´: No such file or directory". Any advice?
PD: Yes, I rename the uImage.img to uImage and still the same message ¬¬
For rooted devices running 1.2.1, I'd recommend Latuk's kernel from http://forum.xda-developers.com/showpost.php?p=43797159&postcount=172. According to Latuk, it's based on B&N's source for the 1.2.1 kernel, plus the multitouch/fastmode/overclocking patches, plus some extra features (usb host mode) plus the fix for Class 10 SD cards.
cowbutt said:
For rooted devices running 1.2.1, I'd recommend Latuk's kernel from http://forum.xda-developers.com/showpost.php?p=43797159&postcount=172. According to Latuk, it's based on B&N's source for the 1.2.1 kernel, plus the multitouch/fastmode/overclocking patches, plus some extra features (usb host mode) plus the fix for Class 10 SD cards.
Click to expand...
Click to collapse
Full disclosure, I write this as a n00b in developer's clothing. I took the CWM-installable zip from the guevor kernel (earlier in the same thread) and replaced the uImage with Latuk's. This means CWM installable zip of Latuk's kernel. Emphasis on should as I really don't know what I'm doing here. That said, I flashed it on my nook, and I now have multitouch and haven't had any problems. Yet. Flash at your own risk, or until somebody who actually knows what they're talking about reads this and says "no that should work fine."
Hope it helps those of us who can't get adb working properly.
is there a reasonably easy way to replace the factory.zip? (partition 3?)
I have what must be an older color, that if I do the 8 failed boots, it reverts all the way back to software 1.0.0
I find that it wont auto update to 1.4.3.
I have to first apply a 1.2 update, before it will take the stock B&N 1.4.3
(or manually thru cwm apply a 1.3 for example)
its not a deal breaker, but I'd prefer a solution that isnt boot into linux/dd the partition
this is a unit I muck around with, testing various roms, and getting it back to stock just involves a few extra steps.
thanks!
The easiest way to get it back to stock is just to flash it directly back with CWM. Go to my NC Tips thread linked in my signature and follow item A15. I have a CWM flashable 1.4.3 there.
However if you want to change the factory zip in partition 3, I can walk you through how to do that. It basically means mounting p3 in a rooted operating system like CM and copying the new zip there.
Sent from my BN NookHD+ using XDA Premium HD app
"However if you want to change the factory zip in partition 3, I can walk you through how to do that. It basically means mounting p3 in a rooted operating system like CM and copying the new zip there."
I'd like to try that if you are willing. Thanks!
I think im pretty experienced.
I have done cm7 / cm10 / on colors/NT many times, have run all the possible scripts you might think of more than once to fix various issues on many colors
one thing Ive noticed on this one after resetting data to the new partition scheme,
that just sort of nags at me, (besides not having a restore to the way I like it from the 8 failed boots)
after Im at 1.4.3 and think Im done, if I do a factory reset from within the stock rom
going to the "factory" screen (and before skipping oobe) seems to flipflop between thinking its got sw 1.0.0 and 1.4.3 , however, the running version in both cases is 1.4.3.
thanks again
----- edit -----
addl info:
I have a CM7 loaded / with the NookColorUMS am able to mount the partition, but have no idea how to maneuver to it, or the format of the zip I'd be dropping in it. (I assume its just a factory rom renamed) On the tablet, cant seem to find the partition after its mounted in either file manager program I've tried, and I've forgotten any real linux/Unix skills I used to have... and it would appear its not usable on the Windows side.
The zip to use is the one I referenced above in item A15. Just rename it factory.zip.
And since you have the UMS utility, mount p3 in the first section. Then plug in your USB cable to Windows and it should show up as a drive. Look at it with Windows Explorer. You can tell if you are there by seeing the factory.zip. Backup that one to your PC in case something goes wrong. Then copy the new factory.zip on the drive replacing the old one. Be careful with the other files there, especially the rombackup.zip. That is critical and needs to stay there. (In fact back that up to your PC too).
That's it, you're done. Next 8 failed boot you should be on 1.4.3.
Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier.
Sent from my BN NookHD+ using XDA Premium HD app
" And since you have the ums utility, mount p3 in the first section. Then plug in your USB cable to Windows and it should show up as a drive. Look at it with Windows Explorer."
Yeah, this is where the plan goes south,
anything mounted in UMS doesn't seem to be translated properly for Windows. I get a "you must format the disk" but no additional usable mapped drives.
the internal partitions in the version of cm7 UMS I have are all down below, in the 2nd section
do I have to mount the "big" extended partition first? then in the second tab of UMS the factory p3? (ill try it in a few)
No, don't do that. I'll give you alternate instructions.
Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory
The go to /factory with your root file manager.
Proceed as earlier instructed.
Did you see my edit above?
Edit: and the reason your drives are not showing properly in Windows is you must activate UMS in CM7. Pull up your notification area and tell it to allow access after you plug in the cable
Sent from my BN NookHD+ using XDA Premium HD app
the su/terminal thing is just what I need I think. will report back in 5
re:
"Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier."
Oh, I have no trouble getting em back to stock, and "close" to perfect, but I could sell this unit and 6 months from now I wanna be able to tell the user just do this ( 8 factory failed) , and its good to go, and Im not supporting a rebuild to stock 1.0, then 1.2, or a cwm flash.
Edit2:
re: " Edit: and the reason your drives are not showing properly in Windows is you must activate UMS in CM7. Pull up your notification area and tell it to allow access after you plug in the cable "
Yea, Im doing that. Does one have to disable debugging or something too?
Its not a big deal at all, just didn't have it committed to memory and hasn't been necessary to this point to access the protected partitions.
mikeataol said:
the su/terminal thing is just what I need I think. will report back in 5
re:
"Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier."
Oh, I have no trouble getting em back to stock, and "close" to perfect, but I could sell this unit and 6 months from now I wanna be able to tell the user just do this ( 8 factory failed) , and its good to go, and Im not supporting a rebuild to stock 1.0, then 1.2, or a cwm flash.
Click to expand...
Click to collapse
if you sell or give away your unit, be sure to erase and deregister with stock so it is removed as your device on the B&N servers. Otherwise the new user will not be able to register it. And you know stock recovery must be installed before the 8 failed boot works, right?
Also see my edit above about how to fix ums..... Yes you must disable debugging.
Sent from my BN NookHD+ using XDA Premium HD app
"Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory"
Hi, I did the whole process twice , just to be sure before coming back... 2nd time was with a newly downloaded copy of the signed A15 zip
Are you sure the factory recovery wants the signed zip file and not the stock?
after 8 failed boots it does a data reset, then tried the factory image reinstall but the factory image reinstall part fails about 1/3rd of the way through
---
had to wing it on the mounting / copy a little as just running terminal put me in a read only file system
but im 100% positive I Installed the signed1.4.3. into factory (backed up the 1.0.0 factory.zip first)
just noting , I DID use the repartition scripts on this prior, setting it to the "new" 5gb data / 1gb media
but it seems to me that the stock recovery isnt liking the signed zip file
mikeataol said:
"Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory"
Hi, I did the whole process twice , just to be sure before coming back... 2nd time was with a newly downloaded copy of the signed A15 zip
Are you sure the factory recovery wants the signed zip file and not the stock?
after 8 failed boots it does a data reset, then tried the factory image reinstall but the factory image reinstall part fails about 1/3rd of the way through
---
had to wing it on the mounting / copy a little as just running terminal put me in a read only file system
but im 100% positive I Installed the signed1.4.3. into factory (backed up the 1.0.0 factory.zip first)
just noting , I DID use the repartition scripts on this prior, setting it to the "new" 5gb data / 1gb media
but it seems to me that the stock recovery isnt liking the signed zip file
Click to expand...
Click to collapse
That is possible since I modified it. Go get a clean one from B&N. Go their support page and look for update. There will be a link to a big file that ends in .npk. Download that and rename to factory.zip.
Sent from my BN NookHD+ using XDA Premium HD app
It seems the 1.4.3 update zip from B&N isn't suitable as a factory.zip
neither the signed or unsigned works
I've grabbed 2 factory zips from other units
1.2.0 and 1.3.0 and copied them into factory, and they both work as expected on the 8 failed boots
I didn't get the complete result that I wanted , but good enough.
Thanks again for your help leapinlar, It's appreciated.
Could you put a custom rom as a factory.zip? Just a thought. It'd be cool to rollback to a stable rom like cm7 if something in a cm10/11 nightly goes wrong.