I am trying to upgrade from CM7 to CM10 using this guide: http://forum.xda-developers.com/showthread.php?p=35669871#post35669871
Got everything in place, get into recovery, start the backup, and that's as far as I can get because the backup hangs. If I use CWM, it gets to a point where it says "Baseline.par" and hangs, if I use TWRP it gets system backed up, gets to "Generating MD5 system.ext4.win" and hangs. I tried with an 2gb card & an 16gb card. Same results. I've let it sit for a good 45 minutes and nothing.
Not sure if this matters with it, but after I re-booted I forgot to swap out the cards & still had the one with all the files on it in the nook. The nook was not plugged in to USB. As it came back up, it gave a message that I had a "bad boot file (in memory)". Is this because I didn't have the USB cord attached? I've never gotten that message before.
I posted all this in the thread itself, so I apologize for a bit of a double post but I'm hoping someone might notice the problem if it's in it's own thread & I don't really think it has to do with loading CM10, anyway.
Suggestions? Thanks!
rsdown said:
I am trying to upgrade from CM7 to CM10 using this guide: http://forum.xda-developers.com/showthread.php?p=35669871#post35669871
Got everything in place, get into recovery, start the backup, and that's as far as I can get because the backup hangs. If I use CWM, it gets to a point where it says "Baseline.par" and hangs, if I use TWRP it gets system backed up, gets to "Generating MD5 system.ext4.win" and hangs. I tried with an 2gb card & an 16gb card. Same results. I've let it sit for a good 45 minutes and nothing.
Not sure if this matters with it, but after I re-booted I forgot to swap out the cards & still had the one with all the files on it in the nook. The nook was not plugged in to USB. As it came back up, it gave a message that I had a "bad boot file (in memory)". Is this because I didn't have the USB cord attached? I've never gotten that message before.
I posted all this in the thread itself, so I apologize for a bit of a double post but I'm hoping someone might notice the problem if it's in it's own thread & I don't really think it has to do with loading CM10, anyway.
Suggestions? Thanks!
Click to expand...
Click to collapse
Use Titanium Backup to backup all your files. Or manually save them all on your computer then put them in the right spots when you update.
Related
I have found that I can't perform either a Bart or nandroid backup from recovery. Any ideas? Do I perhaps need to update Among RA? My version is 1.6.2.
Sent from my FroyoEris using XDA App
gospodinwizard said:
I have found that I can't perform either a Bart or nandroid backup from recovery. Any ideas? Do I perhaps need to update Among RA? My version is 1.6.2.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Does it just get like 1 or 2 dots into it and then says it can't?
Sometimes it has to do with it properly mounting your SD card.
Try plugging USB into a computer, turning on USB-MS toggle for a second, then turning off USB-MS Toggle. SOmetimes that works.
Otherwise, turn off the phone, pull out the SD Card, put it back in, then boot back into Recovery.
This happens to me occasionally. You can't Flash from Zip either, when this happens. It's annoying but it'll work eventually.
I haven't tried removing the SD Card, but I will try that. Flashing from zip still works fine. And I can still use nandroid-mobile.sh via adb to make backups with no issues. Restoring from recovery works fine as well. It seems to get about half way through the backup process before it craps out and tells me to use nandroid-mobile.sh. And this all happens even if the battery is at 100% or plugged into the wall charger.
gospodinwizard said:
I haven't tried removing the SD Card, but I will try that. Flashing from zip still works fine. And I can still use nandroid-mobile.sh via adb to make backups with no issues. Restoring from recovery works fine as well. It seems to get about half way through the backup process before it craps out and tells me to use nandroid-mobile.sh. And this all happens even if the battery is at 100% or plugged into the wall charger.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7661952&postcount=1
Your SD card possibly needs to be re-formatted.
Don't forget to back it up first.
Once I formatted my card with normal FAT and had very strange behavior as such.
And even if you already did as FAT32, sometimes recovery (and android) only likes it if you use home > menu > settings > Sd card and storage > format to format it.
Once, I had to format it fat32, then go into android and format it again.
Odd, I think. But something about how it writes blocks of data, and it can't seem to write it the way it wants in recovery, even though windows can with nandroid-mobile.sh.
I don't know how well this works for our phone, but this might be worth a shot:
http://erlern.wordpress.com/2010/06/03/error-run-nandroid-mobile-sh-via-console/
I had this problem last nite. Possibly your battery may be low or something with the SD card. For me was as easy as letting the phone charge for like 20 minutes then try again
Sent from my Eris using XDA App
dragon1018 said:
I had this problem last nite. Possibly your battery may be low or something with the SD card. For me was as easy as letting the phone charge for like 20 minutes then try again
Sent from my Eris using XDA App
Click to expand...
Click to collapse
I was thinking the same thing, but he said:
And this all happens even if the battery is at 100% or plugged into the wall charger.
Click to expand...
Click to collapse
OK just to top this all off and make it even weirder, nandroid backup from recovery just started working again. I have no concrete idea why, but I did notice something a bit odd. I was poking around in the terminal emulator to see what I could decipher. I entered "whoami" and got the response "app54". So I typed "su" and a message popped on the screen that "Titanium Backup has been granted root access". Another "whoami" returned "root". I uninstalled TB and booted into recovery but the backup still didn't work. Rebooted, reinstalled TB, and went back to recovery at which point nandroid backup decided it was time to work. I can't imagine what, if any, the connection is with my backup problems but nonetheless this is what transpired. I was left wondering if TB had done something with/to busybox that caused the problem.
Hello
I have nFlashed my devices twice, after each I just recirculate the TapNTap animation. I know I need to wipe data as that as worked in the past, but I can get get into CWM to do that. Im pretty sure I have CWM extracted on my internal card, but when I boot and press Vol+ I get the android screen, then a Big yield sign with an ! in the middle, then the device reboots itself.
What am I doing wrong? I also have cwmod in the external card but I do not think that card is being looked at upon boot. Any help is appreciated.
Thanks,
RalphTrent
I removed the update/recovery on the external card and re-extracted CWM onto the external card and I was able to get into CWM.
That was crazy
1. Wrong section...this is not development
2. This question has been asked and answered at least 200 times
3. Try searching before posting
http://forum.xda-developers.com/showthread.php?t=892090
Sorry, I thought this would be development and not general. I guess that is my why searches did not show anything. Also, as noted, i did resolve it my self. I could have probably deleted the entry, but I figured I would leave it out in case someone else comes into this thread looking for a similar issue.
Hello people. I have a 32 GB Wi-Fi only Tab, running seraphimserapis' CM9 preview kang.
I'll dive right into things here. Earlier today, I flashed the above ROM, everything went perfectly, booted up just fine, and got all my apps back up and running. I was using my tab fine for the entire day with no problems to speak of. Later in the day, I began transferring some misc. files (documents, music, etc) to my internal SD card via MTP USB transfer. After the transfer was complete, I unplugged my tab, and went on my merry way. The next time I booted up, everything began FCing on me, and nearly every app I tried to open immediately FCed. Thinking it was a temporary bug, I rebooted my tab, but the same problem persisted, multiple different processes fced upon boot, and almost all my apps would fc as soon as I opened them. After trying a few more times, I gave up, and booted back into CWM (which I can do perfectly fine), cleared cahce and delvik cache, and did a factory reset. This however,seemed to only augment the problem. Upon booting up (after doing that initial tab setup), trebuchet FCes (in a "FC loop", as it continually tries to open), and the tablet is completely unusable. I have tried wiping cache, reformatting and rebooting several times, each time with the same result
I am able to get into settings however, by plugging in the tab, and clicking USB debugging (for whatever reason, settings does not FC), and am able to connect to my internal memory via MTP. When the tab pops up in my computer, it says I have 25 GB out of 28 available GB, but when I click on the folder, it is completely empty. If i try to move files over to my tab, or even create a new folder, I get an error message saying "the device has stopped responding or has been removed". (Pictures below)
http://img141.imageshack.us/img141/9855/75464072.jpg
http://img190.imageshack.us/img190/3395/61277691.jpg
I do not believe this is a problem with the rom for two reasons. (1) no one else has had this problem (to my knowledge), and (2) it was working fine the whole day, until i did that file transfer (that being said, this is my own amateur opinion, which you may choose to completely disregard it in your diagnosis). I am 99% sure I didn't unplug the tab while files were still transferring, but I did not unmount the storage or eject it or anything fancy of that nature before I unplugged it.
My question is, is there any way I can somehow reformat the internal memory of my tab? Otherwise, is there some other possible fix you experts may possibly have? Or am I screwed?
I apologize in advance if you ask me to try something and I cant respond promptly. Its 3AM here and i need to wake up early tomorrow. Thank you in advance
Edit:
I am quite convinced there is some kind of internal memory corruption problem here, but I really am not an expert enough to know for certain. The tablet still boots up fine, but is completely unusable as trebuchet fc loops 90% of the time i reboot the tab. Obviously, the entire thing isnt trashed as it appears to boot and get into the system fine, but I it's still completely unusable from that point on.
I have tried formatting the /data and /cache partitions of the internal memory to no avail. I would try formatting /system, but from my understanding, thats only advisable if you are able to flash a new rom after formatting, but if i cannot write into my internal memory, then there's no way i can flash a new rom. Conveniently enough, I deleted the .zip file for the rom off my internal sd, and i cannot access my clockworkmod recovery from CWM (gives an error, I don't think that would have worked anyway) since the internal sd is (i believe) corrupted. I also tried mounting as USB from CWM, and that also gives an error...
I am clean out of ideas. I'm not sure if this is a completely unfixable problem, or if self repairing is well within the realm of possibility. If someone can shed some light on me that would REALLY be appreciated. Otherwise i might have to send it back to sammy (still under warranty), which i dont mind doing, but if they boot it to find an ICS rom, they probably wont be so keen to repair it...perhaps there's a way to brick it further so they can't tell?
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
.......HOW??
brennanyama said:
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
Click to expand...
Click to collapse
I'm hoping you see this reply as its been quite a while since you've had the issue. I'm working with a Galaxy S2 Skyrocket with the same intenal memory corruption/ files system corruption you were facing. I followed what you did regarding push a rom thru adb and that worked for me, but my question is, how did you get the roms to successfully write if you couldnt write to internal memory? My system is mounted as read only apparently and locked itself with whatever I had on there on August 28th. No matter how many times I format, erase, or wipe it, it returns to the same state as if its a deep lock on it.
I have been scouring these boards for hours and can't find my exact problem so I think I need to post this as a noob. I did Albert Wertz's method of rooting my Nook Tablet 16GB which he states will void the warranty. Afterwards I showed version 9.9.9 so I think it was rooted however I never saw superuser and such. I did something where the main menu bar no longer appears when pressing the n button too, annoying, I want it back too.
Anyway I booted into CWM from SD and then removed my boot SD and installed another SD with the img files on it. I have about 4 img files on it from throughout the day trying to update to CM7 and then tried a restore and just a CWM flash, every img file I select starts to perform it's update and somewhere around "extracting files" it says "installation aborted". At first I thought I had a bad memory card but both cards behave the same so I think they are good (creating 70MB partition on the CWM). I did a system restore on it and now it reports version 1.4.0 but I still get all the same errors, I'm stuck. I've spent about 9 hours of messing with this today and can’t think straight. I am going to bed and will try tomorrow, but if anyone could please tell me what I am missing I would very much appreciate it. Happy Easter ! Thanks, Mark O
markols said:
I have been scouring these boards for hours and can't find my exact problem so I think I need to post this as a noob. I did Albert Wertz's method of rooting my Nook Tablet 16GB which he states will void the warranty. Afterwards I showed version 9.9.9 so I think it was rooted however I never saw superuser and such. I did something where the main menu bar no longer appears when pressing the n button too, annoying, I want it back too.
Anyway I booted into CWM from SD and then removed my boot SD and installed another SD with the img files on it. I have about 4 img files on it from throughout the day trying to update to CM7 and then tried a restore and just a CWM flash, every img file I select starts to perform it's update and somewhere around "extracting files" it says "installation aborted". At first I thought I had a bad memory card but both cards behave the same so I think they are good (creating 70MB partition on the CWM). I did a system restore on it and now it reports version 1.4.0 but I still get all the same errors, I'm stuck. I've spent about 9 hours of messing with this today and can’t think straight. I am going to bed and will try tomorrow, but if anyone could please tell me what I am missing I would very much appreciate it. Happy Easter ! Thanks, Mark O
Click to expand...
Click to collapse
In CWM, you need to install from .zip files. It sound like you're trying to install .img.
Thanks... I was installing .zip files, not .img. I was pretty useless last night. I used Alberts 4_5SD recovery this morn and got it rooted to 9.9.9 and I had superuser and titanium backup so all was good. I ran NWM from internal on the tablet and told it to install ROM from the SD card. I pointed to the file and told it to backup, then install the new ROM it said an error had occured when I tried this. I then booted from another SD card to go to CWM and after the white screen with the box, it went into backup and then restored the ROM, however it took me back to a unrooted version. It looked for the ROM I wanted to load but that was on the other SD card. Now I am back at square one, frustrated...
I think I might have found the problem but I am not sure. When I was doing the original CM7 update I wrote CWM to the E drive, (MyNook) so now the drive reports a total size of .99GB with 433MB free. So CWM is installed on this drive and I think that is the proplem. Is there a way to get CWM off the E drive? If I can just uninstall it, will that be sufficient enough to get the root back and then correctly install CM7? Thanks again in advance.
I guess this is turning out to be an ongoing update from me, lol... I am back to a rooted Nook Tablet with 9.9.9 So since I am a glutton for punishment I will try again tonight to do the CM7. I simply deleted the CWM file that I found in the internal memory and it seemed to not hurt anything.
This time I am planning to download Indirect’s latest "NOOK Tab Recovery Flasher.apk" directly to my Nook Tablet, (at the inlaws now and no wifi
If I understand correctly it will install CWM direct on my tablet, I am just wondering where it will end up installed? Then I downloaded the file for internal CM7 installation, the file is named "Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed" I have it and nothing else on the sd card. So when I run CWM from the Nook, I point to the .zip file on the SD card. Sounds easy but after three screw ups, I am aprehensive.
If someone could please confirm that this procedure and the files I am using are compatible and should work with my 16GB Nook Tablet. Again thanks very much and I hope all have been enjoying this Easter holiday........
markols said:
I guess this is turning out to be an ongoing update from me, lol... I am back to a rooted Nook Tablet with 9.9.9 So since I am a glutton for punishment I will try again tonight to do the CM7. I simply deleted the CWM file that I found in the internal memory and it seemed to not hurt anything.
This time I am planning to download Indirect’s latest "NOOK Tab Recovery Flasher.apk" directly to my Nook Tablet, (at the inlaws now and no wifi
If I understand correctly it will install CWM direct on my tablet, I am just wondering where it will end up installed? Then I downloaded the file for internal CM7 installation, the file is named "Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed" I have it and nothing else on the sd card. So when I run CWM from the Nook, I point to the .zip file on the SD card. Sounds easy but after three screw ups, I am aprehensive.
If someone could please confirm that this procedure and the files I am using are compatible and should work with my 16GB Nook Tablet. Again thanks very much and I hope all have been enjoying this Easter holiday........
Click to expand...
Click to collapse
The steps that you have listed in this post are correct. If you do this exactly, everything should go according to plan.
Indirect's great app installs CWM to the recovery partition of your device, overwriting the B&N stock recovery. You can always go back to stock recovery if need be, though, so don't worry.
Thanks Solar.Plexus
The procedure worked as I hoped. I don't understand what went so wrong in my first attempt but the main thing is my wife doesn't look at me with THAT look anymore, since she thought I bricked her 12 hour old NT.....
markols said:
Thanks Solar.Plexus
The procedure worked as I hoped. I don't understand what went so wrong in my first attempt but the main thing is my wife doesn't look at me with THAT look anymore, since she thought I bricked her 12 hour old NT.....
Click to expand...
Click to collapse
No problem. Glad to hear your wife's happy again!
installaton aborted while installing clockmodrecovery
hii i am sagar
i want solution to this problem any body have solution means please reply
i am using micromax mad a94
when i am trying to install clockworkmod on my phone it always show like these
install/sdcard.....
finding update package......
opening update package.....
verifying update package....
installation aborted........
anybody have solution to this problem
please tell me
thank you
Did u solve it yet?
Sent from my iPod touch using Tapatalk
Hello,
I've installed CM internal to (2) NT 16GBs without incident, and I got stumbled by the n button not working with 1.4.1 that was on my third. Ultimately - I downgraded to 1.4.0, installed CM7, and then did the dumb thing.
I meant to hit wipe data and cache, and I clicked factory reset in CWM. (And at this point - it is stuck in a state where I can boot to CWM - but cannot get CM7 to boot in any form from the internal rom).
I attempted the following
1) acclaim restore (just tried didn't do anything)
2) backup / restore from alternate nook Tablet 16Gb (man this seemed promising ...)
3) couple of the different unbrick scenarios - but I don't have adb, and it seems like windows 7 is not a happy camper with nook usb devices, (and adb isn't happy either.)
4) meghd00t restores (couple of different variations.)
does anyone have any starter threads that I should start walking down for the same stuff - I have browsed, and it's been a couple of hours and I'm exhausted. will poke back in tommorow, and will get this thing plugged into a linux host.
It didn't seem like adb could be so hard ...
--Adrian
Hmmm interesting... ok first of all doing this "I meant to hit wipe data and cache, and I clicked factory reset in CWM" is not dumb is ok to do but is not good signal the hang actually is very weird. Maybe all you have is a corrupted cwm recovery flash. Now be explicit if you indeed could try some unbrick methods succesfully (the ones running from sdcard) and what methods exactly did you try.
~ Veronica
things I've tried - part 1
1) just try to restore to factory with acclaim_update.zip on non-booting sdcard , (this is the 1.4.0 image) - I get the grey n, a flash of white - (like it's going to boot), and that that "please restart your device and try again..."
(This worked when it was factory), but it seems like the logic to check the sd card and start to recover isn't working.
2) Tried the thread here - http://forum.xda-developers.com/showthread.php?t=1562130 - meghd00tr4-sdimg.zip boots, but first time - get red reverse highlighted line - "booti: bad boot image magic in memory" - s5 in the upper left corner of the cyanoboot screen, and the n button doesn't seem to do anything.
3) same thread different image - repart.img, this runs fine- and after about 30 seconds of boot, I get a green check, (waited a full (2) minutes after that green check before I unplugged it.) - same message after boot.
4) full restore of nook tablet from current good cm7 image (and this is the one that most concerns me) - NT16gbV4_6 based cwm v5.5.04 - attempting restore of backed up alternate nook tablet - and the exact same thing happens at boot - does the image not touch partions that aren't related to the root install -(this seems like maybe there is something the bootloader is looking for in the image that isn't right, and it wedges?)
I am going to work on getting an adb setup going that works and then start working down a couple of fix recovery scenarios today / tonight.
It doesn't seem like this is unrecoverable - and the worst part is -I had cm7 booting fine for a couple of reboots, and then something went awry.
--Adrian
as I think about this ...
I do have (2) differnt backups, and I wonder if that restore was the wrong thing to do.
I got to thinking this as I saw the restore of the .android_secure file, from the ALTERNATE nook. I have the backup from the 1.4.0 "original working" image of this nook before the cm 7 issues- but I put it on an SD card that is safetly out of my reach. (In a friends cell phone.)
I think an easy thing will be to restore that backup as another test.
-Adrian
peril said:
I do have (2) differnt backups, and I wonder if that restore was the wrong thing to do.
I got to thinking this as I saw the restore of the .android_secure file, from the ALTERNATE nook. I have the backup from the 1.4.0 "original working" image of this nook before the cm 7 issues- but I put it on an SD card that is safetly out of my reach. (In a friends cell phone.)
I think an easy thing will be to restore that backup as another test.
-Adrian
Click to expand...
Click to collapse
Right, try that first, dont attempt anything advanced yet. Your problem could be solved easily
Just to make sure you flashed cwm from @Indirect app?
~ Veronica
Sent from my Nook Tablet using xda premium
Wait, can you boot into a CM7 SD ROM? From there you could try reflashing recovery.
Sent from my R800x
FIXED
I used this method - and I was good to go.
http://forum.xda-developers.com/showthread.php?t=1470910
In one of the flashes - must have hit the power prior to something being complete with the recovery.
thanks all for your support - and really appreciate the time in the forum. I'm going to put together a torrent with the recovery stuff in it, and make sure it's available as my little part. (Give me a day or so.)
Thanks again.
--Adrian
The problem with that is that you will lose your original serial ID's and MAC address if you didnt backup your rom partition (mmcblk0p5) first so if you use B&N services you wont be able to register after flash any stock rom.
~ Veronica
Sent from my Nook Tablet using xda premium
I also screwed up...Reverting to 1.4.0
Tried to revert to 1.4.0, and followed all instructions as showned on a youtube video. Unfortunately, as it was reverting back to older version as soon as it finished the process - the tablet wouldn't start back up. Did any one ever have this happen to them.. Fortunately, I had just bought today at WalMart. So, I'm going to replace it...
Was just curious, if it ever happened to any one. If so what did I possibly do wrong....
mr_truevision said:
Tried to revert to 1.4.0, and followed all instructions as showned on a youtube video. Unfortunately, as it was reverting back to older version as soon as it finished the process - the tablet wouldn't start back up. Did any one ever have this happen to them.. Fortunately, I had just bought today at WalMart. So, I'm going to replace it...
Was just curious, if it ever happened to any one. If so what did I possibly do wrong....
Click to expand...
Click to collapse
Hmm i think you have a 8GB Nook Tablet and the acclaim_update.zip is only for 16GB NT.
~ Veronica
ubuntu recovery.
This was strictly for CM7. I have no problem with being locked out of the B&N services. (I use the nook application for that access.)
Wish I would have known the serial number before / after. I was able to login to my B&N account after 1.4.0 was restored from ubuntu.
--Adrian
lavero.burgos said:
The problem with that is that you will lose your original serial ID's and MAC address if you didnt backup your rom partition (mmcblk0p5) first so if you use B&N services you wont be able to register after flash any stock rom.
~ Veronica
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse