So i flashed cm 5.07 and now when i try to nandroid something it says
Error: Run 'nandroid-mobile.sh' via adb!
Idk what that means can anyone help?
Nandroids work for me. Is the battery level low. If the level is low it will give this error. Low level is 30% or less.
did you lose root?Check and see if you still have root permissions
I have been having the same issue for a few weeks. Backups seem to work fine, but unless I backup the ext part, I cannot restore. Same error as op.
Still have root.
Anyone?
yes i still have root and my battery was at 90%. i can nandroid if im on 5.06 but i cant do it for 5.07, its goes about 4 dots in and gives me that error message
your partition could be trashed on your sd card, try taking all the filles off of it, reformatting from recovery, then put your files back, worked for me
the partition is fine, like i said everything works perfectly making nandroid backups on 5.06 just not 5.07
Which recovery are you on?
amon ra 1.7
I was getting this as well with a fully charged battery.
This will sound bloody stupid, but it worked fine if I boot up while plugged into the charger. But it didn't work while running on battery power.
Could you try this and see if I'm going mad?
been there done that, im pretty much just not caring anymore and just gonna wait for cm 6, im perfectly happy with cm 5.6
Related
Hi all,
I just installed ClockworkMod Recover using ROM Manager on my G1, replacing Amon_RA. Immediately before replacing, I did a Nandroid backup using Amon_RA. No problems, lots of dots and then it returned. After I installed ClockworkMod, I tried creating another Nandroid backup, first from the recovery screen and then from the ROM Manager app. Both times the backup hung on the message "Backing up .android_secure..." and required a battery pull to get back. The last time I let it go for over an hour before giving up. I'm running CM6 stable, if that matters.
Any idea? I'm about to put Amon_RA back on, so I can get good Nandroid backups again.
I know this is an old post but I am getting the same thing. Going to continue researching.
hmmm last time i had an issue kinda like this it was the recovery... need to re flash it somehow.. maybe the sd ext has something to do with it also...? im not sure but i would try to re flash recovery or maybe switch back to amon-ra if all else fails can always re-root
Mine took over 20 minutes today. Just when I was about to pull the battery, it moved on. Probably down the amount of stuff you have on your phone I guess.
I'm running a 32GB card stuffed with apps
havent used clockworkmod in a long time, i stick with amonra -- but if i remember right with clockwork isnt there an option to have a status bar so you can see how things are moving along? maybe not...
Can anyone give me a hand with this?
I was running CM7 n40 with ALSA and dalingrin's 0413a kernel. Watching videos in vevo when the nook froze and reset itself and got stuck looping at the CM7 animation.
I've rebooted into CWR, tried first wiping Dalvik cache, it didn't seem to make a difference. I then tried formatting /cache and reinstalling n40 and dalingrin's 0404 kernel. No joy either.
Short of reinstalling everything, is there anything else I can try?
If you are running from an SD card then your problem is likely the card. If you aren't running from an SD card then... Maybe someone else can help you.
Forgot to add, running from eMMC.
I had the same thing, only with CM stable...ended up having to rebuild my / boot with the file here.... http://forum.xda-developers.com/showthread.php?t=914690.
Very last file in first post. Had to flash it then start all over....
Sent from my NookColor using XDA Premium App
You are not alone, mine just did this after updating to the latest nightly and restoring with Titanium Backup. I did not flash a kernel, just the nightly using Rom Manager.
My symptoms were that it seemed to run OK, then I opened the gallery to set a different wallpaper and got constant FCs, so then I restarted. Now I'm watching the circle go round and round.
OK, back to previous, just restored the nandroid backup Rom Manager made prior to the update. Seems to be working fine.
I flashed n40 and dalingrin's oc kernel 0404. Stable and happy as can be.
I'm thinking the issue was with ALSA and experimental kernel 0413a, which has been reported to crash video playback in some cases. Don't know how or why it would corrupt my install though.
Let me just mention a lot of people are claiming false boot loops lately. Sometimes it just takes a long time to reboot, especially after it froze. I've had it take up to 20mins before with the little skateboard android.
So next time unless it's giving you "Touch The Future" and then the CWM treatment, give it a bit to load and see if it does after 10 mins or so. (Usually just after the screen dims, my nook loads up just fine)
No that's unacceptable. Considering the amount of data it should be loading, something is very wrong with your nook if it takes more than 5 minutes to boot.
And yes it was boot looping, the animation restarted itself repeatedly (wasn't just the arrow spinning).
Can't help at all but to offer another data point: I was on nightly 39, ALSA update, and kernel 0413a. Was flicking between homescreens when it locked up, forcing a hard shutdown. When I booted back up, it was stuck in a bootloop. Tried all the usual paths to recovery, but had to resort to a backup.
Moved on to n41 (ALSA included) and kernel 0418c. Stable in every case so far.
I'm having same issue and mine is still not working no matter what I did.
I even tried to restore it back to stock - Format/ Fdisk / DD / etc... tried everything I could find. I even had my back up but couldn't restore. I think I created more problem while I was trying to fix it.
Now I can only boot from SD. So I was not the only one.
Eww, I would never touch any sort of partition change with eMMC installs. Usually I just go back to stock or latest backup. Found out there may be an issue with backups created from CWR flashed to eMMC (MD5 check failure). SO anyone who's made a backp from that, do yourself a favor and boot off a CWR SD and do a backup onto that just to be safe.
Sorry about your troubles, hope you get it sorted. Guess I got away easy with just format and nightly re-flash.
First:
I'm running 1.2.0, stock + root
Stock Kernel + OC
Ok, I know that's a lame post title, but I couldn't think of a better one. My microSD crapped out on me earlier today and I, for the life of me, can't remember how I had it set up (yes, I have copy/paste backups on my PC). Read on, I'll explain.
Before, I could keep my flashable microSD in all the Nook all the time and boot, reboot at will without being forced into CWM. Shortly after my microSD crapped out on me, my Nook got stuck in a bootloop. This happened, I assume, because in my insomnia-dazed brain, I copy/pasted my microSD backup without making it flashable and then updated CWM via Rom Manager when it told me there was an update.
Anyway, I grabbed a CWM image from here and flashed it up, got everything going again, but now my system boots directly into CWM with my microSD inserted in the Nook. What the heck do I need to flash to take it back the way it used to be? Pardon my lack of common sense. It's been a busy day and I've gotten about 8 hours of sleep over the past 3 days.
No ideas at all?
N/M, got it all worked out....ya worthless bastards.
i was hoping maybe someone could help me with the fact that i can't boot up past the htc screen. i did a search, but couldn't find anything that worked. anyway, i haven't changed anything on my phone - same rom and all - but it was getting laggy lately, and so i thought i would clear the data and dalvik and all that. i figured i'd do a backup first - using RA 1.6.2 it said "performing backup" and the dots kept filling the page, but 15 minutes later it wasn't done so i pulled the battery. now i can't boot the phone (which i find weird since i didn't pull the battery during a restore or anything, so it shouldn't have messed with any files). i did give it over an hour to boot up btw, in case it just needed time to rebuild. tried a backup again (figuring the one i stopped would be corrupt, and thought maybe the phone thought it was still backing up and wanted a complete nandroid to be done?) and it said run via adb. so, i tried flashing clockwork 2.5.0.7 and it looked like it was working at first, but then it just got stuck on "sysinit." i wiped everything and formatted the sd card in case something was corrupt, but still no luck. i realize i COULD reinstall a rom (i'm using aosp froyo) but i'd prefer not to only because i don't have a backup and i'd rather not lose my texts and voicemails if i don't have to.
hopefully i provided enough information. and the battery is fully charged btw. thanks for any help you could provide
That run via ADB message pops up when the battery is below 30%. At this point don't worry about saving the ROM you have right now, all the text messages and voicemails are erased when you do all the wipes. Download a new ROM, put it on the SD card, Wipe everything and flash.
In the future, if you port your number to google voice all your texts and voicemails will be accessible from any computer or new phone no matter what you do.
Okay guys, listen up. My phone is screwed. I was running Helly Bean 4.1.2 on the Devil 1.9.5 CMC kernel(a standard setup, I don't see anything wrong here), OC'd to 1.2GHz and that's it. Last night my phone was working fine, played a bit of minecraft, bought Asphalt 5, downloaded its files, I'm not using an external SD, just the internal 16 gigs. Now, what happened is that I woke up, my phone didn't react to the power button, when I pressed it once or held it for a few seconds to boot, so I took out my battery like normal. I thought my phone was SODing. But then, my phone booted to recovery. I choose "Reboot device" thinking it was some boot bug or whatever, but then it booted just back to recovery. I thought my system was effed up, so I went to do a full wipe, but it didn't want to wipe my device. I tried Install zip from SD, and then it happened. "Can't mount E:"
So, I did the standard procedure. Odin --> KK4 --> Corn Kernel. And guess what? No luck, it still won't load my internal SD, it won't even boot. I even tried to wipe the internal SD in the stock samsung recovery, but nope.
Guys, is it over? Did my Cappy hit rock bottom? Bit the grass? Is there a way to fix stuff?
NoDze said:
Okay guys, listen up. My phone is screwed. I was running Helly Bean 4.1.2 on the Devil 1.9.5 CMC kernel(a standard setup, I don't see anything wrong here), OC'd to 1.2GHz and that's it. Last night my phone was working fine, played a bit of minecraft, bought Asphalt 5, downloaded its files, I'm not using an external SD, just the internal 16 gigs. Now, what happened is that I woke up, my phone didn't react to the power button, when I pressed it once or held it for a few seconds to boot, so I took out my battery like normal. I thought my phone was SODing. But then, my phone booted to recovery. I choose "Reboot device" thinking it was some boot bug or whatever, but then it booted just back to recovery. I thought my system was effed up, so I went to do a full wipe, but it didn't want to wipe my device. I tried Install zip from SD, and then it happened. "Can't mount E:"
So, I did the standard procedure. Odin --> KK4 --> Corn Kernel. And guess what? No luck, it still won't load my internal SD, it won't even boot. I even tried to wipe the internal SD in the stock samsung recovery, but nope.
Guys, is it over? Did my Cappy hit rock bottom? Bit the grass? Is there a way to fix stuff?
Click to expand...
Click to collapse
Seems like your internal sd might be fried. Was your device overeating from time to time (or a lot)?
BWolf56 said:
Seems like your internal sd might be fried. Was your device overeating from time to time (or a lot)?
Click to expand...
Click to collapse
No, and that's what bugs me the most. Yes, it was getting hot when playing games or being on wifi a lot, but I would just let it cool down after that. And no, I wasn't playing games all the time. I mean, the phone was ok before I went to sleep, it was ok at 5AM when I went to get myself a glass of water, but when I woke up later, dead. Well, looks like I'm leaving this community then :/ I'll get myself a feature phone and an mp3 player. That'll work.
NoDze said:
No, and that's what bugs me the most. Yes, it was getting hot when playing games or being on wifi a lot, but I would just let it cool down after that. And no, I wasn't playing games all the time. I mean, the phone was ok before I went to sleep, it was ok at 5AM when I went to get myself a glass of water, but when I woke up later, dead. Well, looks like I'm leaving this community then :/ I'll get myself a feature phone and an mp3 player. That'll work.
Click to expand...
Click to collapse
Here's a thread that might help you: http://forum.xda-developers.com/showthread.php?t=1988051
It's not much of a solution but if files are readable with your pc, transfer them and try other ROMs/formating to FAT32.
BWolf56 said:
Here's a thread that might help you: http://forum.xda-developers.com/showthread.php?t=1988051
It's not much of a solution but if files are readable with your pc, transfer them and try other ROMs/formating to FAT32.
Click to expand...
Click to collapse
Well, I gave the phone to my friend, he'll take a look inside, the hardware and stuff and then he'll bring it back, but the thread you linked doesn't provide any answers either. I'm sure I can't mount my internal to my pc, or is there a way to mount it while in download mode Anyway, it's the end of the road Thank you BWolf for your help, you have my thanks anyway