Related
*Sigh*
I’m a newbie (more like retard) when it comes to this whole update android, leaked Rom’s, recovery, root etc. Can someone please help me get some clarity?
1. Will there be a problem if I try to install the official 2.1 update when I have a rooted phone and Villain 3.4? (No stock 1.5 ROM available via nandroid since I didn’t know what I was doing at the time I first updated it).
2. What is the simplest way to change one's recovery ROM? Do I have to use this whole adb/fastboot (whatever that means) and mess around with things I don’t understand and probably brick my damn Hero, or is there a simple way á la download-copy to SD-click install? The things written in hXXp://forum.xda-developers.com/showthread.php?t=561124 makes me nauseous!
3. What do the terms "Dalvik-cache" and "SD:ext partition" mean, and why would i want to wipe them? (Found them in the wipe-section of my recovery ROM: RA-hero-v1.5.2). Am I supposed to wipe these as well to do what “nprussel” (hXXp://forum.xda-developers.com/showthread.php?t=622468) calls a “full wipe” or is a reset to factory enough?
4. When using nandroid, what is the difference between "nand backup", "nand + ext backup" and "BART backup"?
5. What do you gain from partitioning your SD-card?
To those of you who care to answer my questions – thank you!
ThisTaam said:
*Sigh*
I’m a newbie (more like retard) when it comes to this whole update android, leaked Rom’s, recovery, root etc. Can someone please help me get some clarity?
Click to expand...
Click to collapse
From one noob to another, I'll *try* to answer what i can.
1,... Having a custom ROM will not stop you from being able to get 2.1 when it is officially released. I'm sure everything you need will be posted somewhere for easy access. But if you want to download from HTC's website you may need to flash one of the stock ROMS first. You can find all of them at http://android.modaco.com/content/h...oms-radios-in-update-zip-format-for-gsm-hero/
I reckon using one of the HTC generic ones would be your best bet.
2,... This is the method I used:
I. Installing a recovery image:
1. On your phone, go to Settings > Applications - and make sure "Unknown Source" is ticked.
2. On your phone, go to Settings > SD card and phone storage - click Unmount SD card.
3. Then click Format SD card.
4. Plug the phone into the computer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
hxxp://zenthought.org/content/project/flashrec - FlashRec.apk
hxxp://forum.xda-developers.com/showthread.php?t=561124 - Amon_Ra’s Hero Recovery Image
6. Copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
7. Unplug the phone from the computer once they are downloaded to the SD card.
8. Go to the Market and download ASTRO File Manager or any file manager program if you do not already have one.
9. Open the file manager and find the FlashRec apk file and click it and choose open app manager and then install it.
10. When it is installed click Open. Click on Backup Recovery Image and wait for it to finish. If you get "backup failed" response see the "Ib. Installing the correct HTC ROM" section for more details, if the backup is a success carry on.
11. Once done, click on the empty text box in the FlashRec program and type:
/sdcard/recovery-RA-hero-v1.6.2.img
(replace exact name as new versions come out)
Then click on the Flash Recovery Image button and wait for it to finish.
... Big props to BTDAG for those instructions. (from http://forum.xda-developers.com/showthread.php?t=645253 -- [Guide] How to Root & Install a Custom Rom on Orange UK & T-Mobile UK [Updated 13/03])
3,... I think a full wipe would be select Wipe Data/Factory Reset, then select Wipe Dalvik cache, then Wipe SD. This is an assumption as they were the steps I followed. (Again, from BTDAG's thread)
4,... Sorry, ain't got a scooby. No Idea.
5,... I think it does something like setting aside a specific amount of room for system files. Some ROMs need partitioned SD cards for the Apps2SD function to work.
I hope some of that helps,... Peace.
Nandroid backs up your phones image (i.e. like a photo of how your phone is on that day)
Nandroid + ext also backs up your ext partition on your sd card (only used if you want to activate and use apps2sd)
Bart is another backup utility, not sure what exactly it does as I have only ever wanted to/needed to use nandroid.
You only need to partition your sd card if you wish to use Apps2SD.
- basically what this does is give you the ability to save and run apps from your sd card as your phone has a limit on how many apps it can have (in file size not number of apps) so if your someone with hundreds of apps then you need to use this but the majority of us don't need to worry about it.
If you root now and want to remain rooted then don't install the official 2.1 it won't take long for a pre-rooted version to come out (a matter of hours) so just wait and install the pre-rooted one
ddotpatel, Lennyuk - Thank you! Your help is greatly appreciated!
Hello everyone i have just bought a droid eris to pass my time until septemeber/october. it should be stock android 1.5/1.6. I wanted to know how to go about installing this rom? i read this is one of the most stable and reliable which is what i want. I know the basics of how to flash as per the sticky and youtube videos, but was wondering if there's any guide specific to CELB froyo from stock? Thank you in advance!
You should be able to just use the One Click Root app by Jcase from the Market to root the phone (follow all of the rebooting instructions) and just flash the rom like normal. It's been a little while since I tried CELB, but I don't remember doing anything else.
Flash the ROM and flash the google apps as well, make sure to use the verison of GAPPS listed in his thread and not one of the newer gingerbread ones.
how do you go about installing gapps? put on root of sd card then..? also, do i have to first flash the root-me.zip or can i replace that with the CELB froyo rom?
manchintz said:
how do you go about installing gapps? put on root of sd card then..? also, do i have to first flash the root-me.zip or can i replace that with the CELB froyo rom?
Click to expand...
Click to collapse
The Q&A and stickys on top here has very detailed steps, please take time to read & follow it closely - also, if you go to the Wiki on the top & follow it, there's an entire section dedicated to the Eris, everything you'll need and tools/links on what & where to find/download.
Yes, select the correct Gapps - it should have a *mdpi* strings in the filename as you do NOT want to use the *gb* file as your gapps - and yes, it go on the root of the sd card. I find it very helpful & useful to start with a clean & freshly FAT32 formatted SD card, 8 MB microSD will do just fine (and, if in a pinch, go with a 4 MB card).
To do things right, flash the root-me.zip first and make sure the phone rebooted properly, and is running - you should not have to reactivate the device or update the PRL (by doing a *22891)
After you confirmed that the phone's been rooted, proceed with the CELB rom loaded on the SD card - but only after you do a NAND backup, just in case - then, flash gapps - and reboot the phone, be patient as it could take 5 to 10 minutes to boot up the new ROM for the 1st. time - and when you see the Welcome Screen with the Android, you are ready to setup & customize the phone. Do it slow & take your time - AND, make sure your battery is fully charged. Have fun & good luck !
manchintz said:
how do you go about installing gapps? put on root of sd card then..? also, do i have to first flash the root-me.zip or can i replace that with the CELB froyo rom?
Click to expand...
Click to collapse
Actually, as long as you have Amon_RA recovery running, there is no reason to flash rootme.zip first. That's intended only for the stock Eris build, to give you the apps and settings that you need to allow apps that require root-level access to run. CELB has all of that built-in.
The CELB thread has a location that shows where to download a zip file that includes the Google apps. So, the flash procedure, in a nutshell, would be:
- copy the CELB and gapps zip files to your SD card
- restart in Recovery
- Backup/Restore menu
- Nandroid backup (just in case...)
- back to the main menu, then to the Wipe menu
- Wipe data/factory reset
- Wipe Dalvik cache
- Back to the main menu, then to the Flash a zip from SD card menu
- choose the CELB zip file from the list
- Back to the Flash a zip from SD card menu
- choose the gapps zip file
- restart the phone
everything worked out, except now, it's not recognizing my 8gb sd card? what is going on??
It recognizes my 1gb micro sd, but not the 8gb microsdhc i originaly used to root it in the first place..help?
all is good! thank you all
Hi
I have flashed the cyanogenmod 7.1.0 on my htc legend which went fine, but after som time i realized the gps wasn't working, i tried for severel hours all kinds of gps fix advices i found in google but without any luck.
Because of this i want to go back to stock android 2.2 or 2.3 if possible.
I am having some problems returning to stock android and again tried severel guides.
I tried downloading the newest htc sync and run a RUU update but the updater can not connect to the phone, no htc sync support in cyanogenmod is the problem i think.
I tried downloadning severel different image files of different versions of android on to the sd card and rebot to recovery mode throug clockwork and tried flash a zip file from sd card. But either the update stops because the file is "bad" or it need a newer version of something the cyanogenmod updated when it was installed.
I can see i should be able to do a nandroid backup if i have made such one, guess the guide i used didnt mention that, only i shoud remember to backup my pictures/music/sms....
If you need any more information please ask
Hi,
try this sequence:
1. Open ROM manager application
2. Scroll down to "All clockworkMod recoveries" and click on it
3. choose from that list 2.5.0.7 and press OK
4. Now download a sense ROM from XDA like Blay0's ROM here http://forum.xda-developers.com/showthread.php?t=866849 (if you want to keep this rom download also the patch for upgrade to b0.8.4)
5. Copy the ROM and patch to the SD card
6. From the ROM manager reboot into recovery
7. In recovery mode wipe data and cache
8. Still in recovery mode instal zip from SD card: first the b0.8 ROM and then the b0.8.4 patch
9 Reboot
Now you should have a stock based ROM and do whatever you like (go back to really stock rom which I don't reccommend)
Let me know how it works!
Thanks ill give it a try
[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!
After a disastrous experience trying to root my phone through Magisk and their "modified" boot.img, I lost everything on my phone. Worse even, TWRP was unable to restore my system from my TWRP nandroid backup.
But after days of investigating solutions, trying tirelessly, I finally, FINALLY was able to restore my nandroid into my phone.
It should have been straight forward, that's the purpose of a nandroid, right? But it wasn't, because my TWRP backup (nandroid) was some updates behind my current phone OS, and apparently that was enough, because phone brands and google can't stop messing with low level android "for our safety and privacy" (google taking care of our privacy, LOL!), and as such they keep changing stuff about partitions, boots, protections, all this new crap about A/B slots, 'vendor' and 'vbmeta' .img files, and whatnot. There's even a file called 'uefi_sec.mbn' in the ROMs now.
When I was trying to restore from my nandroid backup, half of my partitions were giving me errors at restoring, and /data was giving me the infamous "createTarFork() process ended with ERROR=255". Rebooting only gave me either bootloops, or a reboot only to the bootloader.
Something in the partitions had irreversibly changed with the new updates, and not even a previous nandroid was able to deal with it and put it all back as it was before. All my stuff *right there* in that backup, ready to surface again in a supposedly seamless process, and I was unable to reach it. So close and yet so far away. It was infuriating.
So I decided to trace back everything. What I tried *and worked* after many attempts, was this:
(NOTE: this will recover virtually everything you had in your system when you made the nandroid, but it could wipe your internal storage, depending on your ahead decisions)
— Make sure you have ADB and Fastboot tools installed on your desktop computer, and also the same ROM you had when you made the nandroid or another one close enough (more details ahead), and the same TWRP version from which you created the nandroid. — Have an SD card and copy your nandroid backup there (the whole "TWRP" folder in your storage root), if it isn't there already. — Get a ROM closer in version/date to the one you had when you created the nandroid backup. If it's the same even better, no matter if it's outdated, you want it outdated, since it matches your also outdated nandroid. E.g, if your phone was on MIUI 13 and you made your nandroid when you had MIUI 12.0.2, then get the 12.0.2 ROM or another close enough. Also match the other ROM specifications you have in your nandroid backup (Global/India(Indonesia/China/Russia). And get the FASTBOOT ROM version instead of the recovery version, and save it to your desktop computer. — Now decompress the gzip file of that ROM: you'll get a .tar file, decompress this one either, until you get a folder with files inside and a 'images' folder. Winrar or 7Zip will decompress those easily. To avoid long pathnames, put this folder in the root of your hard drive. — Boot your phone into bootloader/fastboot, connect it to your PC/MAC, and install that ROM via fastboot, with the script files included in the rom folder flash_all.bat (flash_all.sh for linux or Mac). Mind you this script will also wipe your internal storage, so make sure you have previously backed your stuff from there (search the internet on how to pull/save files from internal storage through adb pull, or even easier, put a SD card and save your stuff to it, assuming your internal storage isn't reading 0bytes as mine was...)NOTE: If you really want to preserve your internal storage you can instead run the script flash_all_except_data_storage.bat/(.sh), but I don't know if it will be as effective. — Once the rom is flashed through fastboot, reboot the phone and config the device with the initial settings screen (I don't know if this step is really necessary, but it worked with me), until you can see app icons on the home screen. — Now reboot the phone into bootloader mode (fastboot), connect it to the PC, and boot TWRP WITHOUT flashing, you'll just boot it by running TWRP into the ram disk of the phone. The recovery of the now installed ROM needs to be untouched, or you'll have bootloops. To boot TWRP without flashing it, you enter this on the command line: fastboot boot twrp.img (considering twrp.img is the name of your TWRP file, and it's present in your current path)NOTE: It may be important to work with a twrp version similar in version to the one you used when creating the nandroid backup, you never know... — Now with TWRP running from the phone's RAM, use your PIN to unencrypt the phone storage if it is asked. — Using the Mount button, mount every partition you see except OTG_USB. I don't know if this step is necesssary, but it worked with me.
— Do a normal wipe to the phone (no need to go to the advanced wipe). Again, I don't know if it's necessary, but it doesn't hurt. But it's almost certain this will wipe your internal storage, so you decide. — Now finally go to the restore button of TWRP, select your external SDcard as the storage where your backup is, select the backup from the folder browser, and choose to restore ALL the partitions from your nandroid backup (when I created my nandroid backup, I backuped every partition except maybe dalvik cache)
Now you wait, drink a glass of wine, go outside, it may take a while restoring everything, specially if you created your nandroid with compression enabled. Hopefully this won't give any errors, or at least no significant ones. Once it's done, reboot, wait a little longer since it may take longer to reboot this one time. When that is also done, hopefully you have your phone the way you had it when you created the nandroid backup, with your system, preferences, apps AND all their data, home app folders, chats, SMS messages, etc.
You may find some small stuff slightly off, like having the day theme while you're sure your phone always had the night theme, the clock now has a different setting, no fingertprints installed, maybe this is stuff inherited from the rom you flashed that remained, but all of this is easily configurable to what you want.
And that's it!
Now, after all this, you want to go to your appstore app and update all your apps -- they are the very same apps stored in the nandroid, they may be outdated, my nandroid was 6 months old -- and also update your OS through OTA or other means, since your rom is also outdated.
Optionally, after all this is done, you may want to make another nandroid backup: reboot into bootloader, connect the phone to the PC, again reboot to TWRP without installing it since it's better if your original recovery remains untouch (do fastboot boot twrp.img ), -- this time you can use an updated TWRP version -- select the storage you want to save the nandroid backup to (either internal storage or the SD card), and select all your phone partitions for backup except internal storage, SD card, and cache. Reboot your phone to system, and save your new nandroid somewhere safe in your PC's hard drive. If you encrypted your nandroid with a password, save that too, otherwise if a time of need arrives, you'll have nothing.
And very important, DON'T TRY TO ROOT IT with Magisk with that altered boot.img process they have, which supposedly "doesn't touch your partitions". You'll only get tears with that, since not even trying to flash your original boot.img will get your system back. Maybe they'll correct this in the near future, but for now avoid it like the plague. They also have an older way of installing root through TWRP and a zip file, I don't know if this one still works. But AVOID the other one.
This process helped me immensely, I hope it also helps someone with the same problem I had.