Related
Due to the number of people not reading the below instuctions, I am putting this annoyingly large font right here.
NOT A FLASHABLE ZIP. MUST EXTRACT Clockworkmod Folder to SD and recovery from CWM. Watch the video...
I pay to host these files. Donations are greatly appreciated if these have helped you.
This is a Backup Image of a stock BN NOOK Tablet after just flashing NT16or8gbV4.6 Root to it.
Demo of 8gb use of this hack! http://www.youtube.com/watch?v=0HC9XL_9aXk
Do not Mirror files.
16gb 1.4.0(NT250)Download Rom file:CWMrestore_1_4_0_ plus NTV16gbV4_6
MD5 Sums: Soon
8gb 1.4.2(NT250A)Download Rom file:CWMrestore_1_4_2_plus NTV8gbv4_6
MD5 Sums: Soon
Apps included in Root Process:
1. ADW
2. Amazon Appstore
3. Anycut
4. Home Manager
5. ES File Explorer
6. Spare parts
7. Homecatcher
8. NT Hidden Settings app
9. Titanium backup
10. Custom Keyboard
11. Live wallpaper
12. 3d Gallery
13. Nook Recovery Flasher
14. Nook Unrooter
This ROM can Also be used to easily restore back to FACTORY STOCK
How:
1. Extract Clockworkmod folder from zip file to root directory of SD card
2. Boot into CWM
3. Flash Rom w/ CWM Recovery
4. Use recovery flasher to flash stock recovery (16gb ONLY, skip this step for 8gb)
5. Run Unrooter
6. Bam!= Factory stock
This ROM can also be used to restore from a bootloop or bricked device
1. Use Root SD card to boot into CWM from SD Card
2. Flash Recovery
3. Bam!= Stock +NT16or8gbV4.6 Root
Video Demonstration- http://www.youtube.com/watch?v=YQfOswBrXIg
Video on how to restore to stock from CM7 using this file: http://www.youtube.com/watch?feature=player_embedded&v=mMj67tgGlew
Donate ;P and hit thanks
reserved for future use
people have been asking so i did it, made a video on how this can be used to restore back from CM7
This saved the day, after I restored my nandoid of rooted stock I lost all access to the barnes noble shop and could not access anything related to barnes and noble. I read of other people restoring there's back to stock and re rooting after experiencing the same issues as I to fix that issue. I knew there was an easier way and restoring this nand was it, seeing your back up was never registered in the first place. Your the man and I will be donating!
Sent from my BNTV250 saved by Albert's recovery rom.
Not working. Nothing working.
Ooo
Will you make one for 1.4.1? Or is there that much of a difference? Thanks for your work man!
jenuhferr said:
Trying very very very hard to do a factory restore but don't know how to do this:
3. Flash Rom w/ CWM Recovery
4. Use recovery flasher to flash stock recovery
5. Run Unrooter
Put file:CWMrestore_1_4_0_ plus NTV16gbV4_6 in sd card, booted into cwm. In video you have two cards. Not sure which card this one is and what to put on other card. Assume that this file is an update or something and now doesn't require two?
Trying to do factory restore and don't know how to do above. Chose zip from sd card, chose cwmrestore zip file and then it finds and starts to install then it is aborted. I have no idea if I'm even supposed to be doing this but there it is.
I have tried so many things from simple (the simple failed reboots method to very complex methods that I tried to follow very closely) and read so many threads and watched so many you tube videos that I can't even tell you how many things I've tried. Nothing works at least the way I'm doing it. I need to get this back to stock and start over because it is really f'd up. I think it was due to a bad sd card I used from the beginning.
Thanks for any help.
Click to expand...
Click to collapse
Can you access clockwork?
Sent from my PC36100 using xda premium
I can't get this to work with CM7. After choosing the zip file it goes through, but ends up with "Installation aborted."
I also tried wiping dalvik, cache, and format system, but nothing will wipe CM7 and return to stock.
What I when I select update from .zip file:
-- Installing: /sdcard/CWMrestore_1_4_0_plusNTV16gbV4_6.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
you have to unzip and extract the clockworkmod recovery folder to your root sd card...
albertwertz said:
you have to unzip and extract the clockworkmod recovery folder to your root sd card...
Click to expand...
Click to collapse
Not quite sure how. The recovery folder consisting of the etc folder and one file, recovery-from-boot.p, goes to the root and the rest of the zip goes to the recovery folder and renamed to factory.zip?
When I do that, it still brings up Cynaboot and I'm presented with the menu. Choosing zip from card and trying to update by choosing factory.zip still goes to the previous Installation aborted error.
---Update--
Wait, I'm mixing up restore methods, as I've tried a number of ways to restore to stock.
I'm in the process of trying to restore by copying to the root of the sd as you recommended.
Not sure what to do next
I decided to use the CM7 from the sd. I worked through this restore, however, I got the following message after it processed through restring .android_secure:
Error while restoring /sdcard/.android_secure!
I tried it again and keep getting the message:
Checking MD5 sums...
MD5 mismatch!
Not sure what to do next...any assistance would be greatly appreciated.
sangahm said:
Not quite sure how. The recovery folder consisting of the etc folder and one file, recovery-from-boot.p, goes to the root and the rest of the zip goes to the recovery folder and renamed to factory.zip?
When I do that, it still brings up Cynaboot and I'm presented with the menu. Choosing zip from card and trying to update by choosing factory.zip still goes to the previous Installation aborted error.
---Update--
Wait, I'm mixing up restore methods, as I've tried a number of ways to restore to stock.
I'm in the process of trying to restore by copying to the root of the sd as you recommended.
Click to expand...
Click to collapse
It worked beautifully. I had to Backup using CWM first to check on the folder structure, and saw that it was all neatly placed as-is in the zip folder. Restored and am now back on stock (and using CM7 on SD card).
Thanks!
new 8gb rom recovery on OP
NT8 recovery will not boot
albertwertz said:
new 8gb rom recovery on OP
Click to expand...
Click to collapse
I am EXTREMELY sad to report that the new "backup" image will not boot on my NT8.
I went through all the steps and CWM flashed the backup without any errors. It then returned to the main menu and I hit "Reboot System."
It just turns off (or goes into a sleep mode.) Nothing but a black screen. The Nook Power cable displays the yellow-red that seems to suggest that it is in a SOD.
I have tried every iteration of powering off for 30 secs and then trying, with/without the SDCard, with/without the Nook Power adapter, and nothing will turn it on.
However, as soon as I put either @meghd00t's NEW recovery SD or my CM7Alpha SD, they boot up without problems.
I CAN do ADB if there is a command that I need to issue to clear some register on the device? Anyone know what I should do?
Ray
After rooting with your sd i can`t access settings-keyboard, error: The aplication Settings has stoped bla bla bla...i wouldn`t bother, but i really need russian keys sometimes...(
btw, thanks a lot for booting cwm img and for recovery zip for sure too, saved me from brain damage)
PS: Nevermind fixed that by running any cut, creating shortcut and adding russian
i have a 8gb nt and i tried unbricking using this method... flashed recovery... and still stuck at the n screen. does not move past it.
Do I flash the rom or put the folder on sd card and restore if I am trying to do the unbrick process on my 8gb nt? I tried the restore but still just get stuck at the n screen.
any help would be appreciated.
mak0305 said:
Do I flash the rom or put the folder on sd card and restore if I am trying to do the unbrick process on my 8gb nt? I tried the restore but still just get stuck at the n screen.
any help would be appreciated.
Click to expand...
Click to collapse
Unzip the file and use clockworkmod to do a restore..
Thats what I have already tried... But im gonna try again, maybe I messed something up...
after flashing recovery, try clearing cache and devlik while in CWM, then reboot.
Guys,
I've looked long and hard on t'interwebs for an answer to this. I'm currently trying to do do a fresh reinstall on my Prime. My Prime hasn't been unlocked, it was rooted before I did the Jellybean update though and I removed a few Asus apps with Titanium backup. I'm trying to get it to run super smooth so that's why I want the complete fresh reinstall.
I've downloaded the latest V10.4.2.15 WW firmware off the Asus website, and upzipped the file so I'm left with the 2nd zip file which is contains. Put this on a FAT32 formatted SD card. I've also tried to copy this onto the root of the internal memory of the Prime. I just can't get the device to see the firmware and reinstall though. Is this because the device is already running V10.4.2.15? Is their any way around this without unlocking the Prime? I've also tried to reinstall using the boot menu, but it won't give me the option either.
Please help!
I also tried to reinstall the update by putting it on a sdcard and had no luck. I concluded that this method must only work for a true upgrade.
Chicaned_UK said:
Guys,
I've looked long and hard on t'interwebs for an answer to this. I'm currently trying to do do a fresh reinstall on my Prime. My Prime hasn't been unlocked, it was rooted before I did the Jellybean update though and I removed a few Asus apps with Titanium backup. I'm trying to get it to run super smooth so that's why I want the complete fresh reinstall.
I've downloaded the latest V10.4.2.15 WW firmware off the Asus website, and upzipped the file so I'm left with the 2nd zip file which is contains. Put this on a FAT32 formatted SD card. I've also tried to copy this onto the root of the internal memory of the Prime. I just can't get the device to see the firmware and reinstall though. Is this because the device is already running V10.4.2.15? Is their any way around this without unlocking the Prime? I've also tried to reinstall using the boot menu, but it won't give me the option either.
Please help!
Click to expand...
Click to collapse
Outside of trying in flash/recovery mode try this:
Rename the Zip file you put on the SDCard for JB to the same name as the last 9.4 OS: US_epad-user-9.4.2.28.zip
With that on the SDCard it may take a removal/reinsert of the SDCard but it should offer to "Downgrade" but once you reboot in to recovery it will be a full flash of new OS. It did NOT wipe my data. I would recommend doing that after. Shutting down and then booting with vol down and power on until the recovery menu comes on then using vol down I believe it is to move the selected option over to "WIPE" then vol up to initiate.
This should yield a "Clean install".
For those nay-sayers out there, I had partial root until I did the above and lost it so I know it overwrites the OS paritition.
Cheers. I'll give that a go when I get home. I'm not too fussed about losing root. I'm even thinking about trading my Prime in for a Nexus 10 depending on the performance of my Prime after the rebuild.
Hmm.. renamed the .zip to WW_epad-user-9.4.2.28.zip but when I when the Prime sees it, I get no notification Tried a reboot but still get nothing. Anyone with any other ideas for this? Can anyone else confirm this works for them?
Chicaned_UK said:
Hmm.. renamed the .zip to WW_epad-user-9.4.2.28.zip but when I when the Prime sees it, I get no notification Tried a reboot but still get nothing. Anyone with any other ideas for this? Can anyone else confirm this works for them?
Click to expand...
Click to collapse
Hrm, I just did it again with the US version because my exchange syncing broke.
My file was called US_epad-user-9.4.2.28.zip
Again, this assumes you have unzipped the official ASUS ROM download from their site and unzipped that file. This will yield a new zip file which is what I renambed and put on the ROOT of my SD card formated as FAT.
I just wrapped it up too, did a full app backup with the asus tool, wiped, reflashed this ROM again and restored and resynced exchange.
You might try giving it the US name. I don't think it would matter because the contents are correct for your device.
I'll try and format the card as FAT instead of FAT32. I'll also try US. Really hope this works!
Sent from my Galaxy Nexus using Tapatalk 2
No dice I'm afraid. Tried a different SD card and renaming it US but get no option to update
Sent from my Galaxy Nexus using Tapatalk 2
[See post http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 for the new version of this post with updated links/pointers to Succulent's recent CM10.1 builds as well as CWM/TWRP recovery tool compilation].
[Caveat emptor: adopt/follow this guide at your own risk].
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
FWIW, here the process I used to install CM10 internally on my 16GB Nook Tablet (i.e., on its emmc).
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows. If you are going to use this card for backing up your NT, keep in mind that each backup will require at least 600MB (for a barebone stock or CM config) and size the partition accordingly.
Obtain and copy to the SD card the following files:
MLO, u-boot.bin, and flashing_boot.img in SD_boot.zip obtained from http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/
either one of the two recovery program image files: cwm_6012_sd.img (ClockworkMod Recovery (aka CWM)) in CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, or twrp_2220_sd.img (TeamWin Recovery Project (aka TWRP)) in CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958, rename it to recovery.img. If you want to try out (or use) both, name your alternate choice altboot.img.
the file cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
the file gapps-jb-20121011-signed.zip from http://goo.im/gapps/gapps-jb-20121011-signed.zip
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select either SDC Recovery (or Alternate Boot depending on which recovery tool you want to use).
Select Backup to backup your current NT config (/boot, /recovery, /system, and /data). Before proceeding to next step, see note (ii) near the end of this post.
Select Wipe data & factory reset.
Select install zip from SD card and install cm-10 zip file.
Select install zip from SD card and install gapps zip file.
Select power of and remove SD card from NT and power NT on again using the power button (alternatively you can just remove SD card and select reboot).
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored)
A few additional points worth noting:
Installing CM10 ROM and gapps will override your NT's BN-provided boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using backup process in step #5 above, safekeep the backup data on your PC/Laptop and better yet archive it on CD/DVD. Your media files in the NT media partition BN allocates for user should be intact.
To play it safe you should do the above in 2 phases: steps 1 through 5, then exit recovery and remove and mount SD card on PC to verify that backup data got newly created; then insert SD card and continue steps 6 through 9.
CWM and TWRP use different backup archive formats, so keep this in mind if you decide to switch. Furthermore, CWM has changed its archive format going from release 5.x to 6.x, so I think it would be prudent to save a copy of the recovery program together with the backup data it generated. (FWIW I prefer the tar/zip compatible backup data structure TWRP uses (which CWM 5.x had also used) over the BLOb structure which CWM 6.x use -- but YMMV).
To restore from backup data, boot into SD card and select from boot menu the same recovery program that was used to create the backup data, then select the particular backup dataset (indexed by date/time) you want to reinstall on your NT.
I would advise against blindly using other functions of the CWM and TWRP without looking up info and researching to understand what they really do.
See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
My thanks to all the developers who collective work created this wonderful ROM as well as the tools and info I made use of to install it. IMHO this ROM helps make the Nook Tablet one of the best-value tablets for the money (at least at the moment).
great post...fwiw here's my experience to get two NT16's up and running (I started with an old CM7 on both of them).
Backup nook with titanium backup on existing 32GB card.
Take screenshots for replacements
Reset nook to stock (1.4.2) and update to latest (1.4.3) with a fresh SD Card with repart.img copied to root (my red 2GB card):
http://raywaldo.com/2012/06/make-unbrick-repartition-image/
http://www.youtube.com/watch?v=Nu6e4m62tFc
c. 1.4.3 can be downloaded from B&N site directly. (http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/)
Create a CWM SD Card (ideally 4GB SanDisk) as per these instructions - http://raywaldo.com/2012/05/root-nook-tablet-with-cwm-sdcard/
Copy CM7 BETA and compatible GAPPS onto this card or another blank one. You can get the files from here: http://forum.xda-developers.com/showthread.php?t=1481826 and http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Boot into this CWM Card, wipe data/wipe cache and dalvik cache. Install zip from sdcard (either current or pop in the new one). Choose cm-7 beta first, then gapps. Remove sd card. Reboot. Wait a while for it to set itself up.
Go into settings/applications and clear the cache for google market/play.
You now have CM7 installed and can setup the basics (google, wifi etc..)
Insert your 32GB (or 16 or 8 or whatever) Sandisk SD Card (it should ideally have the Titanium Backup folder from step 1, any media you want in Music and Movies folder and the CM10 and gapps zip in the downloads folder -- and that's it!)
Once mounted, download Goo Manager from the google play store and run it, accepting superuser requests.
Choose settings menu and "Install OpenRecoveryScript" and it should install openrecovery twrp recovery manager. Once it has installed and informed you of success, reboot into recovery (this is important), upon reboot hold the "n" and choose internal emmc recovery from the menu.
You will now find yourself in TWRP. From the install menu, add the CM10 PURE AOSP 4.1.2 JBV06.1-Hashcode and then the gapps-jb-20121011-signed.zip and swipe to confirm flash. This is it. Fingers Crossed!
NOTE: On one NT 16 (I have two), step 12 DID NOT WORK. It wouldn't install the CM10...zip -- and simply rebooted itself or hung...so I powered off, and rebooted to the CWM Card in #6..and used CWM to wipe caches etc… and then installed the two zips...and voila.
hope it helps.
digixmax said:
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
Click to expand...
Click to collapse
How do you feel about it now that you've installed it internally? I took the plunge as well today, but I'm not sure it's runs any better internally than it does from the sd card. Having said that, it runs so incredibly well from the card, so it's really hard to beat, but still... I'm actually having more issues with the internal install than the sd version.
I had had enough of the stock reader (that I'm actually pretty fond of) not remembering my place in sideloaded books, so I didn't feel I had anything to loose and am glad I made the install though. Installed once makes it easier to reinstall when an even better build comes along.
I made the switch since the stock ROM was so barebone and clumsy I virtually never use it since I had the NT, and the rooted stock ROM is just marginally better -- I found out there are so many apps I 've been using on CM10 that are simply not available for BN's (Android) Gingerbread. I also like the fact that I can now reboot (if ever needed) untethered.
I think performance-wise it runs about the same as it was running on SD, if it's better then it's not yet noticeable.
What kind of issues are you having with your new setup?
Some apps misbehaved. Didn't install properly or gave error messages. I decided to re flash and this this second install hasn't had any issues at all. Same files from the same card.
It is nice to have it internally and be able to switch sd cards should I want to.
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2 and SwiftKey
I ran into a problem with v12/08: when I connect the NT to the PC I do not get the “USB connected” notification with option to “turn on the USB storage”, and thus cannot access neither the emmc media partition nor the sdcard. The problem exists with both CM10 running on emmc and running on sdcard. Furthermore when running on sdcard, hitting “storage” in “settings” results in a force-close of “settings”.
I am curious if anyone else has the same problem, or I am just missing some setup setting somewhere.
In the meantime, I am back to running another ROM off SD.
Those storage setting issue I had with the 1118 build but not with later ones. Connection to PC work fine but I don't think I need to do the turn on USB thing. No PC nearby at the moment
Edit: I am now near a PC, and I do get the "touch to turn on USB" or words to that effect. So it works as it should..
Sent from my Nook Tablet using Tapatalk 2 and SwiftKey
Thanks, I've tried reinstalling a couple of times (as well as installing a different ROM) without success.
I found the answer to my problem: I was used to getting the full-screen alert “USB mass storage” (upon insertion of tethered USB cable), and didn’t notice the tiny alert “USB connected” on the status bar (which when pulled down would in turn launch the “USB mass storage” alert).
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Cm7 is a gingerbread rom, it can be flashed by cwm 5 and 6 both. But cm10 is jellybean and must be flashed with cwm 6 only (or twrp) . And once you have cm7, you get cyanoboot (2nd bootloader) which is necessary to load cwm6, whether its internally flashed recovery or SD card recovery.
If you still have your bootable SD card, boot into recovery and check the version (cwm 5 most likely) , then do the longer, but simpler method - stock > cm7 > flash cwm6 internal and boot into it from cyanoboot > cm10.
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
...
I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Click to expand...
Click to collapse
Yes, you can use this process to go directly from stock or rooted stock to CM10 -- I used it to go from rooted 1.4.3 directly to CM10. With SD-based flash, there is no need to go the circuitous multi-stage flashing process.
And if you use Succulent's CM10 builds from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/ his ROM zip files all include emmc recovery so you don't even have to separately flash recovery as you would have with other ROMs. I think his approach, in addition to being convenient, has the benefit of avoiding intermediate states where there is potential incompatibility between ROM and recovery versions (which I think is conducive to causing bootloop).
Of course if for some reason you later prefer a different version of recovery than the one he includes (CWM 6.0.2.5) you can always reflash your particular choice of recovery by itself.
FWIW I am running Succulent's cm-10-20121225-acclaim-HD.zip (GCC 4.6) at the moment and it works great.
Dean1650 said:
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Click to expand...
Click to collapse
Everything that gets flashed via recovery (either CWM or TWRP) comes in zip archive form, and this applies to ROM, gapps, as well as recovery itself. (If you ever want to flash recovery, the simplest way is to get a recovery zip file, such as one of those with keyword emmc from http://forum.xda-developers.com/showthread.php?t=1640958, and flash it from SD using the process in the first post, just as you would flash a ROM build or gapps).
If you are curious about what gets installed and where, just open (but don't extract) the to-be-flashed zip file (e.g., using winrar/winzip/7-zip): everything except the META-INF folder is what get installed, and the updater-script file in META-INF\com\google\android\ (which you can open using a text editor like notepad) contains installation script detailing where (i.e., which partition on the NT) various components of the zip file get installed.
Typical ROM builds zip contain boot.img which gets installed on /boot partition, and a bunch of system files and apps to be installed on /system partition. Succulent's ROM builds also include recovery which gets installed on /recovery partition. Finally gapps apps get installed on /system as well.
Really, really appreciate this OP, the replies, and the knowledge. VERY helpful. Wont do this til the 1st and will let you know the results... Again, THANKs
Sent from my SAMSUNG-SGH-I317 using xda premium
Well your method worked flawlessly. I had a few minor operator errors but it went just as you explained. I did, however, have a fatal bug in the rom. Not sure who to report it to, but while messing around in settings I tried to change the color of the clock in the status bar. It totally blew away systemui. I tried everything I knew of to restart and recover but had to resort to wipe/factory reset. Could not figure out what data file got corrupted. That in turn made me have to flash the gapps again because none of the Google apps worked including play store. The net result is to add 1 more step to your method. BEFORE messsing with settings, and after the initial setup is complete, boot to recovery and do another backup..I forgot to mention I flashed 20121231, which is the latest release. Thank you so much for your knowledge and reseach. STOCK ROOTED TO CM10 RELEASED.
Sent from my SAMSUNG-SGH-I317 using xda premium
Stuck on backup in CWM 6.0.1.2
My 16gbNT is currently running Team_B CM7. I'm trying to install Kuzma30's CM10.1 from a SD card. Following the instructions from this OP. While trying to perform my backup the process gets about 3/4 of the way through and then sticks at the file named "generic11.lda". It doesn't continue after that and I have left it alone for a considerable amount of time. Any idea what's causing the stick? I've tried it about three or four times with occasionally sticking at different files but it is still about 3/4 of the way through. Backup will not finish.
Any help is greatly appreciated.
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Backup success, Install failure
digixmax said:
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Click to expand...
Click to collapse
Backup successful! Thanks button pressed. Now on the install I used CWM 6.0.1.2 and I'm not allowed to complete the install. It aborts installation and gives the following error:
"Installing update...
set_perm: some changes failed
E:Error in /sdcard/cm-10.1-20130102-UNOFFICIAL-acclaim.zip
(Status 7)
Installation aborted."
Any ideas?
Your guide is quite clear but somehow it is not working for me. I have a fresh NT 8GB with stock 1.2 on it.
I obtained the 6 files you mention:
- u-boot.bin
- MLO
- flashing_boot.img
- recovery.img (= cwm_6012_sd.img)
- gapps-jb-20121011-signed.zip
- cm-10-20121231-NOOKTABLET-acclaim-HD.zip (from: http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/)
I copied them to a 16GB 10x SD card and placed the SD card in my NT.
The problem is that whatever I do, it always boots the stock os and never into Cyanoboot. I know I have to connect the NT to my computer with USB and wait for it to boot, but even then it only load the stock OS.
Am I doing something wrong here?
Help much appreciated!
Nabi 2 Disney return to stock for Dummies?
Pretty much what the title says, I've got a Nabi 2 Disney model that I rooted (at least I think I did) in an attempt to free up more space on the tablet, and would now like to restore to stock so we can get the OTA 3.0 to KitKat update.
While there are a lot of informative posts here some of this stuff is beyond me, even being an IT guy myself (but not a lot of experience with Android, other than what comes with our phones, tablets etc.).
Are there any guides to returning the Nabi 2 to stock from a beginners standpoint, or really good step by step that even someone like me can understand? Here is the information that I have:
Model
NABI2-NV7A
Edition
NABI2-NV7A-US-D
Android Version
4.1.1
TWRP v2.8.5.0 Nabi Jellybean
To make things more interesting (of course) I cannot locate the stock image to recover it with, when I go into recovery in TWRP there is no package to restore, checked the external microSD and there is nothing there either. The original laptop I used to root the Nabi originally has since been wiped so I can't even look for it there.
Can this thing be restored to Disney stock without losing the "Disney" customization? Can TWRP be removed to allow the OTA update to install? We can download the OTA update just fine but when it reboots the Nabi goes right into TWRP.
Any help would be appreciated.
TMOSteel said:
Can this thing be restored to Disney stock without losing the "Disney" customization? Can TWRP be removed to allow the OTA update to install? We can download the OTA update just fine but when it reboots the Nabi goes right into TWRP.
Any help would be appreciated.
Click to expand...
Click to collapse
Should be possible. Yes TWRP can be removed, it depends on the OTA but TWRP can sometimes deal with the OTA as long as it's not a 2 part update.I would do the following, EXCEPT I don't have a Nabi Disney, and the restore I made has never been tested. Up to you if you want to try but Nabi Disney is almost impossible to brick.
-You should have a backup of your current system before starting.
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.4 Disney ROM and bootloader.
- Download 304 stock ROM http://www.nabtabhacks.com/downloads/304D.zip
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 304D.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.4 ROM.
- Download the KK304bootloader zip attached to bottom of this post.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK304bootloader.zip you downloaded and install it.
- Reboot
At this point you should start using the KK TWRP going forward. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
If all this works you wont need to restore stock recovery as you will be on the latest. Of course you are the first one to attempt to use this 304D AFAIK.
aicjofs said:
Should be possible. Yes TWRP can be removed, it depends on the OTA but TWRP can sometimes deal with the OTA as long as it's not a 2 part update.I would do the following, EXCEPT I don't have a Nabi Disney, and the restore I made has never been tested. Up to you if you want to try but Nabi Disney is almost impossible to brick.
-You should have a backup of your current system before starting.
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.4 Disney ROM and bootloader.
- Download 304 stock ROM http://www.nabtabhacks.com/downloads/304D.zip
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 304D.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.4 ROM.
- Download the KK304bootloader zip attached to bottom of this post.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK304bootloader.zip you downloaded and install it.
- Reboot
At this point you should start using the KK TWRP going forward. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
If all this works you wont need to restore stock recovery as you will be on the latest. Of course you are the first one to attempt to use this 304D AFAIK.
Click to expand...
Click to collapse
Just what I needed, thanks for this, hopefully by Sunday I'll get to this and report back how it went (can't handle anymore "Daddy when are you going to fix my Nabi" questions...).
It worked like a charm, followed your instructions to a T, shut it down once or twice as it seemed to get stuck on "loading" or "syncing" screen (sorry, forgot which) after the modules were updated but eventually everything loaded and then we had to sign in with the Nabi ID like it was the first time.
All the Disney apps are still there that we didn't remove to make room for the update but I'll think we'll trim things down more as there is now less than 500MB of free space on the internal memory.
Still a lot of demos she doesn't play with so I'll let her enjoy things for a few days and then we'll start thinning things out.
Thanks again for all your help, people like you are what make the internet a great place.
TMOSteel said:
It worked like a charm, followed your instructions to a T, shut it down once or twice as it seemed to get stuck on "loading" or "syncing" screen (sorry, forgot which) after the modules were updated but eventually everything loaded and then we had to sign in with the Nabi ID like it was the first time.
All the Disney apps are still there that we didn't remove to make room for the update but I'll think we'll trim things down more as there is now less than 500MB of free space on the internal memory.
Still a lot of demos she doesn't play with so I'll let her enjoy things for a few days and then we'll start thinning things out.
Thanks again for all your help, people like you are what make the internet a great place.
Click to expand...
Click to collapse
So glad it worked. I owned a Disney edition for about a day and a half however many years ago, and I had to make that ROM by just reverse engineering it up to the latest version. Never had a chance to see if it actually worked until now. So thank you!
Can i use this rom on my non-disney version? would it add all the extra disney stuff?
mjw2k11 said:
Can i use this rom on my non-disney version? would it add all the extra disney stuff?
Click to expand...
Click to collapse
The partition sizes for "system" and "addon" are different between the Nabi2 orig, Nick, and Disney versions. For example if the the system partition for the Original is 500MB you can't install the 800MB ROM for the Disney, it won't fit.
That said, with nvflash it is possible to change the partition sizes... but for even the above average technical person it's not possible.
Hi,
I need to restore some twrp images. I have these on my PC but I forget where they should go. I've tried putting there on the SD card in TWRP\Backup but restore doesn't see them so I moved them to the top of the SD card but it still doesn't see them. Where should they go?
FYII recently had my vf-895 play up. I'd previously installed twrp and magisk and it was working if rather slow. Then it started to take 20min to send or receive txts and swapping sim to another phone stopped that (so fault was with phone). I thought I'd try LineageOS since getdriodtips site says there is a 14.1 version for the smart prime 6. Didn't work for me although I'm not sure I did it right. I just pointed twrp at the zip. But also zip has 839 in the name not 895 and more googling suggests the getdriodtips for for the smart ultra 7 (or 6 I forget, not not the prime anyway). The other getdroidtips suggestion of MIUI 8 also didn't work for me but maybe I'm not doing it right.
Will twrp just install a zipped custom rom or does it have to be a special zip? Or how to I do this (other than using adb which often take a while to get working I find).
Thanks
UPDATE, after posting this I had a though, do a backup and see where it goes. Now I'm really confused as the files I have are TWRP 3.0.0-0_VF-895N.img and the like so all *.img where as the backup is a folder with *.win and *.win.md5.
I've come to the conclusion that TWRP 3.0.0-0_VF-895N.img is just the recovery img to load TWRP instead of stock recovery. Hence I don't have a backup like I thought. If anyone has a TWRP backup for a smart prime 6 (UK) I would appreciate a copy.
I've tried stock rom downloads but they all use sugar and I can't get sugar to recognise the phone and/or install the usb drivers. When I put TWRP in adb sideload then the phone with adb appears in control panel so the cable works.
I've tried other ROM and some even flash but after the phone just boot loops.