"Error...Run "nandroid-mobile.sh" via adb!" - Droid Eris Android Development

ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??

Mime has done that too. I've noticed it when my battery was below 15%. Try connecting to a charger or let your battery charge a little bit.
After I did that I had no more problems.

iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
Click to expand...
Click to collapse
yea its most likely because your battery is low, charge it a bit then restore

iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
everything worked fine up until now.
And i dont think its the rom that did this.
lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
Click to expand...
Click to collapse
ya it usually does that with a low battery .....
only happened to me once ..... but a very wise man told me this was almost always the cause

ive been charged all day. still no luck.. :-(

iflip said:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on
my screen:
"Error...Run "nandroid-mobile.sh" via adb!"
Click to expand...
Click to collapse
I think I had the "Error : run 'nandroid-mobile.sh restore' via adb!" problem before when trying to restore a rom in recovery, but i think it was because of renaming the folder inside the "nandroid" folder on the sd card.

i didnt rename anything

quick question what recovery are you using?
I had problems similar to this on CLOCKWORKMOD recovery, to the point where i couldn't flash or restore any nand. I even tried flashing root rom and that also failed. when It tried to write boot and the system in failed and then i had to replace my phone because it wouldn't even boot after trying to flash root rom.

using amon ra.
i think im gonna try to reinstall recovery img via adb. any requests to stop me go right ahead.

i tried reinstalling recoery img via adb and still nothing!!!! AARRGH!!!

Sounds lime my issue js rather unique. Doesnt seem like anyone else had this problem yet. Well i guess for now im .sh out of luck.
-------------------------------------
Sent via the XDA Tapatalk App

iflip said:
Sounds lime my issue js rather unique. Doesnt seem like anyone else had this problem yet. Well i guess for now im .sh out of luck.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I had this problem when the memory on my sd card was almost full. I deleted a bunch of zip files and a bunch of the nand backups and it worked fine. I've also experienced the low power and the invalid rename issue too. hope this helps.

That sounds like a solution. Thx. i will trh to free up space on sd. Ive been pretty full for a while tho, but never encountered this msg.
-------------------------------------
Sent via the XDA Tapatalk App

nand restore error run nandoid mobile via adb
I just got this error and simply needed to have power plugged in to complete the restore. Hope this helps.

Well, there's two ways to go about solving this type of problem.
One would be to use the built in functionality of the Recovery menu system to copy the recovery log file (/cache/recovery/log) to your SD card and then - oh, I don't know, maybe look at it to see what error messages are in there? Really super-duper users could even just do a "adb shell cat /cache/recovery/log | more" with the recovery console still running, but that presumes a high level of skill (operating a space bar on the keyboard).
The other way would be to ask a bunch of strangers on the internet to speculate about what the problem might be.
I prefer the 2nd way; it's far less efficient, but much more entertaining. Hours of fun, really.
J/K. Have a look at Amon_RA's announcement post for the Eris, where he says:
Always check recovery.log before posting your issues!
bftb0

i am having the same exact problem with my nexus one. the error: run 'nandroid-mobile.sh restore' via adb. i am a new root user and this is my first time attempting to do any nand restores, and i get that error. is it possible i used the newer recorvery which is not compatible with cyanogen 5.0.7 ROM? i just followed all the links on the rooting guide and said to use all latest files.
my battery is 100% and my sd card has 2gb of free space. i'm really at a loss what to do. thanks.

Verify that there is a folder named nandroid in the root directory of your SDcard. If not, create one. I was having the exact same problem until I did that.

there is definitely a nandroid folder on my sdcard root drive, and inside that folder are 3 backup folders with associated files. i'm going nuts.

you can rename the back up files with names starting with "BDS-". You can't rename the folder directly under "nandroid" in your directory. if you do, you will get the "run mobile.sh" error. you will also get this error if your battery is low or you have no storage left. the folder directly under the "nandroid" folder it is your serial number. if you're having issues, just go to the "other" menu and select "send recovery.log to SD card." then go in and search the recovery.log file on your sdcard for "serialno=" right after that there will be a 12 character string of capital letters and numbers directly followed by lower case letters that are useless for this purpose. Create a folder with the same name as that string (capital letters and numbers only, no lower case) and place your previously renamed backups into that folder and voila! you'll be able to restore them.

My issue never got fixed, but I did try a different memory card, copied over my backups, and now they restore fine. And I did rename them to "stockROM" and they restore just fine. So the name does not matter.
I tried formatting the original memory card then copied all the contents back onto it, and still will not work with nand restores. It took me 5 hours to dump my card and reload it, so some files on that card must be screwing something up. Sucks cause now I'm stuck with this small card and with my music on it now It's full, so I have no room to do anything. Wish I could get my main card working with backups.

Related

Problems preparing to flash ROM

My vibrant is running stock 2.2 Froyo. Lately, it dies silently and so frequently in sleep that I can't rely on it for every day usage. I've missed many important calls. So I am trying prepare my phone to flash another ROM. First, I got the phone rooted no problem at all.
Then the first problem I have is with the ROM manager. I purchased the Premium Version 3.0.1.3 and flashed the latest ClockworkMod Recovery 2.5.1.2. Upon rebooting into Recovery, there is, however, no Nandroid backup, just the normal menu shows up with
Samsung Recovery Utils -for BML-
.reboot now
.reinstall packages
.delete all user data
.delete cache data
.format internal sd card
I remove update.zip on the phone and on the sd card and retried and retried without success. Why don't I have Nandroid backup showing up to save the phone before flashing new ROM?
The second problem is with the Titanium Backup. I downloaded the free version and it works fine and could get root privilege without problem. Then I purchased the donated version and followed the instruction to uninstall the app and reinstall it to get the upgrade through the license file. The license file is read correctly and the upgrade version acknowledges that. However, Titanium Backup paid version now fails to get root privilege. I verify that other apps can get root without problem. I've searched all over yesterday and it seems that few people have the same problem getting root with the upgraded version, but no one has offered a solution.
So here I am paying but not able to backup the phone to start flashing anything. Could someone enlighten me about what I did wrong here?
Thank you.
For recovery, just select reinstall packages. Sometimes you have to do it twice.
For titanium backup, click the problems button to get the latest busybox.
You should be good after that.
Sent from my GT-I9000 using XDA Premium App
What offdutyninja808 said, also check your Superuser app, click Titanium and tell it to forget it if it's there.
We'll get you sorted out!
I have the same set-up and I have the same issue. I've selecting reinstall packages several times. Did not work. I tried different, methods: using Rom Manager and AIO Vibrant Toolbox. Didn't work. At first it said said it wasn't signed, and I four a fix for that. Now It loads and says replacing stock recovery with Clockwork... but boots back into the stock one. Is there anything else I can do?
birgertime said:
What offdutyninja808 said, also check your Superuser app, click Titanium and tell it to forget it if it's there.
We'll get you sorted out!
Click to expand...
Click to collapse
+1 Both Off duty and birgertime are correct. Most of the new roms will delete all things for you unless they say to do something particular (like some of the EDT roms) you should be ok, we are here to help if you run into further problems
If hitting "reinstall packages" don't take you to the clockwork recovery, also you can just reinstall the recovery thru rom manager.
Then once you reboot and if it don't take you to clockwork recovery, then hit reinstall packages again. Ya should get to it the second time.
I had this issue a lot when first rooted the phone and installed clockwork recovery.
Sometimes it will even boot halfway into stock recovery then quickly reboot itself into clockwork.
Also, just make sure that there is only ONE update.zip in there. So delete the update.zip using "my files" then open Rom Manager and choose install clockwork recovery. That way you are sure there is only one update.zip there then try the previous mentioned methods
Thanks for your advice. I still have problem with selecting "reinstall packages" in the Recovery menu. If I select that, it says:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
This repeats if I keep selecting "reinstall packages" again. My SD card is still the original 2GB card that comes with the phone. It still has plenty of space.
Thanks again for helping
FWIW, I upgraded BusyBox and could solve the Titanium Backup problem. However, still can not do a nandroid backup as mentioned above, even with the donated version. So I abandoned my plan to flash another ROM and stay with the rooted stock.
However, what a difference it makes when I replace the 2GB SD card that came with the Vibrant with a 16GB SD card class 10. The unit comes up faster, the UI is no longer sluggish as before. I hope that this was the issue that caused my Vibrant to die in sleep. I need to phone for daily use and don't have a lot of time to muck around with it. Maybe next year when I have another phone to use as main phone, then I can take some risk to flash without nandroid backup. For now I hope that it no longer dies in sleep. Thanks for all your help.
Just a quick note to end this thread.
Since I have plenty of disk space on the internal memory, I removed the SD which I don't need and the phone seems to become reasonably fast responsive with rooted stock 2.2. It's now quite usable for me so I have no more need to flash it with another ROM. People who complain about slowness of their stock 2.2 ROM should try to remove the SD card first.
Thanks again for all your help.

bricked?

I am stock at tmobile screen, it doesnt go any further
i went in recovery it returns as
E:Can't Mount /cache/recovery
all the way down
the "fastboot erase recovery" returns with "FAILED (remote: not allowed)" and the "fastboot flash recovery recovery.img" returns the same thing. Any other suggestions???
I tried to restore pd15img and
it works little bit, and it asked me to upgrade, i pressed the volume up
1 BOOTLOADER - Fail-PU
partiton update fail!
update fail!
This has happened to quite a few people lately and I don't think they have been able to come back from it. Out of curiosity though, what caused this? Were you flashing something and this happened? Do you have the engineering bootloader? Attached is a thread of someone with the same problem, and like I said, there are a couple more out there.
http://forum.xda-developers.com/showthread.php?t=984790
I change roms many times, and recovery many times, this time i had been using 3.006 modified with battery charge.
didnt have a problem until i put the royalglacior 1.5 version.
than i could use the wifi, it gave me an error, i rebooted few times, and always error, and finally gave up.
I had the same fastboot errors when trying to flash from 3.0.0.5 to 2.5.1.2 after i mistakenly flashed 2.5.1.2 when i had cm7. You may need to update your sdk. I had to install my HTCdrivers on a new box and Download the tools folder from here http://forum.xda-developers.com/showthread.php?t=928370 to get it working.
theghazi said:
I change roms many times, and recovery many times, this time i had been using 3.006 modified with battery charge.
didnt have a problem until i put the royalglacior 1.5 version.
than i could use the wifi, it gave me an error, i rebooted few times, and always error, and finally gave up.
Click to expand...
Click to collapse
First, there is only RoyalGlacier v 1.2 as of the latest for now. Since you used that CWM 3.0.0.6 while battery charge off, there is a chance it might have reverted back to CWM 3.0.0.5 and RoyalGlacier requires 3.0.0.6 and stock restore requires 2.5.1.4 but your recovery may be 3.0.0.5. Try flashing a ROM that just requires 3.0.0.5. For future reference, use this version of CWM 3.0.0.6 from here (http://forum.xda-developers.com/showthread.php?t=944681). That sticks and never reverts back to .5.
Thanks for replies, n advices.
I have tried every which way possible to put the recoveries, and all failed.
I have had 3.0.0.6 modified for a while. was not going back and forth with 2.5.1.4
anyone else come out of this mess,
if not is there a way to get it to even at s - on and unroot?
I dont think so, but worth to ask
thanks
I'm having the same issue where it gets stuck at the Tmobile spash screen and when i boot into clockwork, it gives me the cache error. Formatting it through clockwork doesnt work, and when i try to restore it it also give me an error. I tried to format through adb but that hasn't worked either, unless I'm typing in the command wrong
I dnt believe there is a way to fix that issue,i had that issue awhile back on my 1st mytouch 4g,i had cm7 & made the mistake of tryin to nandroid restore a backup which I forgot was stocked froyo & everythin flashed ok but got stuck in bootloop,so battery pulled went to recovery & had all those errors u mentioned & never found a fix.....called tmobile,got a replacement no problems 2 mnth later & warranty still there..... Now I have clockwork 3.0.0.6 & havent ran into that issue yet,goodluck let us knw if u find a fix....
Permrooted s=off-MyTouch 4g-White
Eng-0.85.2007
Rom-RoyalGinger
I like balls
I am not using tmobile. I know it is covered under HTC but wont they refuse if they see s off?
Sent from my HTC Glacier using XDA App
theghazi said:
I am not using tmobile. I know it is covered under HTC but wont they refuse if they see s off?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Im not really to sure,a friend of mine had the same issue & went thru HTC & got a replacement so want im guessin is they dnt care but dnt hold it against me,it could of been 1 of those lucky times. All he said was that the phone wnt boot & they just sd it was a known issue & sent him another one...
well I think I've successfully bricked my mt4g. It was working fine until I installed the latest clockwork version and RoyalGinger, tried to restore some applications + data with mybackup root but it froze. Then it was stuck on a bootloop, went back into clockwork and started getting the "can't mount cache" errors. Now it's stuck on the T-Mobile splash screen if I try to do a normal boot, bootloader works and it also goes into clockwork, but it's not able to do any factory resets/wipe. Tried the factory image file and it fails on the first 5 or 6 items, skips another item and hangs at flashing the radio. Now it needs to be replaced and T-Mo is out of stock of the red mt4g's, so I have to wait until they have stock of red ones, then it's going to suck if I get one with a bad screen. I got offered a black one, but I just like my red one too much.
did you include the part file when flashing the PD15IMG.zip?
"there needs to be part7backup-1294463706.bin file on your sd card with the PD15IMG.zip file...both on the root of sd card."
I'm thinking that the file comes stock on the sdcard, but when we format our sdcard it wipes it. I know I personally ran the PD15IMG.zip file twice on my phone and both times it worked great, but both times I did it before I wiped my sdcard (and I do remember a ridiculous amount of extra stuff on the sdcard when it came with the phone).
darinmc said:
did you include the part file when flashing the PD15IMG.zip?
"there needs to be part7backup-1294463706.bin file on your sd card with the PD15IMG.zip file...both on the root of sd card."
I'm thinking that the file comes stock on the sdcard, but when we format our sdcard it wipes it. I know I personally ran the PD15IMG.zip file twice on my phone and both times it worked great, but both times I did it before I wiped my sdcard (and I do remember a ridiculous amount of extra stuff on the sdcard when it came with the phone).
Click to expand...
Click to collapse
That part7-xxxxx.bin file is created when u root with the gfree method,it doesnt come stock on the sd card... what method did u use to root...dnt use unlockr.com methods,its old & doesnt give true oerm root...
I made an assumption, i just used the basic root.sh script so I didn't read into the gfree method (see no need). I just know that people who have had trouble reverting to stock with the PD15IMG.zip fixed the issue by putting that part7backup file on the root of their sdcard.
darinmc said:
I made an assumption, i just used the basic root.sh script so I didn't read into the gfree method (see no need). I just know that people who have had trouble reverting to stock with the PD15IMG.zip fixed the issue by putting that part7backup file on the root of their sdcard.
Click to expand...
Click to collapse
gfree method would of gave u S off & that backup file,really I dnt think theres a fix for that just yet,without that file..... For future reference never restore data fron any backup app(ex.titanium,astro erc) u can only restore apps cause then u restorin data from a different rom & tryin to put it on a current rom that probably isnt the same...
cmdmilitia13 said:
gfree method would of gave u S off & that backup file,really I dnt think theres a fix for that just yet,without that file..... For future reference never restore data fron any backup app(ex.titanium,astro erc) u can only restore apps cause then u restorin data from a different rom & tryin to put it on a current rom that probably isnt the same...
Click to expand...
Click to collapse
no idea where this is coming from. I was just offering a suggestion to the op. As you can clearly see I am not the op. I do not have issues. I simply made an assumption about the gfree method, which was cleared up, though I still think it's a very real possibility that the op didn't put the part7 file on the root of his sdcard when he flashed the pd15img.zip. Either way, I thank you for your advice, but I'm not the one seeking it here.
darinmc said:
no idea where this is coming from. I was just offering a suggestion to the op. As you can clearly see I am not the op. I do not have issues. I simply made an assumption about the gfree method, which was cleared up, though I still think it's a very real possibility that the op didn't put the part7 file on the root of his sdcard when he flashed the pd15img.zip. Either way, I thank you for your advice, but I'm not the one seeking it here.
Click to expand...
Click to collapse
My fault I should of double read,i have an issue with just skimmin thru things & look what happens lol...
Has anyone found a fix for this? Same issue.
Isubbie said:
Has anyone found a fix for this? Same issue.
Click to expand...
Click to collapse
nope nothing yet,not that I knw off...

Troubles with Rom Manager and Flashing

I am having a lot of issues with Rom manager. Whenever I create a backup and try to back it up it refuses to work. It acts like it worked. But when I try to restore to that backup it says MD5 mismatch. I am currently running a froyo leedroid rom. I have tried to flash over to a GB Leedroid rom and a Coredroid rom. Neither of them work.
It says finding update package
opening update package
can't open file bad.
I am seriously annoyed with rom manager WTF is the point in creating a damn backup if I can't restore it at a later point?
Now my sdcard will not mount says its is mounted as read only and it wont do a damn thing now...
Bump wondering how to check an MD5. Still wondering what is up with Rom manager. Silly question but am I having troubles because I bought a different memory card for the phone? I did a partition and wiped it but just not sure.
http://www.softpedia.com/get/System/File-Management/MD5-Checker.shtml
use that to check the MD5. Obviously something getting corrupt along the way. I cant imagine its the memory card but Im not 100%. Hopefully someone with more knowledge than me will pop along shortly.
berserkerx87 said:
I am having a lot of issues with Rom manager. Whenever I create a backup and try to back it up it refuses to work. It acts like it worked. But when I try to restore to that backup it says MD5 mismatch. I am currently running a froyo leedroid rom. I have tried to flash over to a GB Leedroid rom and a Coredroid rom. Neither of them work.
It says finding update package
opening update package
can't open file bad.
I am seriously annoyed with rom manager WTF is the point in creating a damn backup if I can't restore it at a later point?
Click to expand...
Click to collapse
Hi I'm pretty new here so I'm may be wrong about this, but could it be a problem with Froyo and GB? It's like using office 2010 and 2007 version, may not be backward compatible. But I may be wrong, just a a guess on my part.
berserkerx87 said:
It says finding update package
opening update package
can't open file bad.
Click to expand...
Click to collapse
Looks to me like you've got a flaky SD card, certainly I have no problems creating and restoring backups although I am on CM7 but that shouldn't make a difference, first off though make sure youre running the lastest ROM Manager and Clockwork versions then try a different SD card.
Okay I am still having issues with Rom manager. I tried putting in a new sd card and it will not mount to the system. I hit mount and it just pops back up saying its ready to remove. I now can't reboot into recovery nor flash clockwork recovery. It said an error occurred while flashing your recovery.
Also I really don't like that I can't even take a picture or use my camera because it says it can't save to the SD card due to insufficient file permissions. Yes I have done fix permissions in rom manager. But it still wont work..
have you tried to do it directly in CWM?
if so, try to flash a newer CWM version (through fastboot, ROM Manager is known to cause some problems).
Hello iam also having problems but i am have my DHD freeze at the splash screen when trying to enter recovery, any ideas please.
berserkerx87 said:
Okay I am still having issues with Rom manager. I tried putting in a new sd card and it will not mount to the system. I hit mount and it just pops back up saying its ready to remove. I now can't reboot into recovery nor flash clockwork recovery. It said an error occurred while flashing your recovery.
Also I really don't like that I can't even take a picture or use my camera because it says it can't save to the SD card due to insufficient file permissions. Yes I have done fix permissions in rom manager. But it still wont work..
Click to expand...
Click to collapse
ROM manager wouldn't prevent mounting of a new SD card, thats got to be a hardware issue or an issue with your current ROM, try flashing either a different custom ROM or a stock ROM if your SD card woes continue it's a hardware issue, if not it's a ROM issue but either way I think we can safely rule out ROM manager.
sidon100uk said:
Hello iam also having problems but i am have my DHD freeze at the splash screen when trying to enter recovery, any ideas please.
Click to expand...
Click to collapse
Try reflashing Clockwork recovery, either from Fastboot or from ROM manager.
Tried using ROM Manager but got nowhere so i followed this post and it worked first time http://forum.xda-developers.com/showthread.php?t=1003723 , it was great for new guys like me.
But thank you for your help.
I figured out what the problem was. Even though I had formatted that new sd card it still wouldn't mount so I formatted it on the computer and now everything is fine. I don't use that other sd card anymore. I guess it was really just a bad sd card. So a word of advice to everyone that not all sd cards are created equal!
Thanks for all the help everyone!
Wise words there! I've been through 4 memory cards lol and each one broke. One after the other.
I use Rom Manager only to install CWM, and then I flashed all new rom by recovery from SD card.
I propose not to save a money on buying cheap card. It so important

Need Stock-i500-VZW-Kernel.tar.md5

Hosed my Fascinate by trying to flash a recovery through Odin -> The recovery also had a kernel in the file that I didn't realize. Phone attempts to boot then reboots into recovery. I would prefer not to do a factory reset until I try reflashing the right kernel.
I am aware of this thread that used to have the file I need, but evidently the guy has removed it from his Dropbox now. Does anyone have a copy they can throw up for me? I think I could use the recovery image, too, but it is a little bit easier to find so don't go to great lengths for the recovery.
Will reflashing the correct kernel even fix my problem? I haven't touched /system. Should all my stuff still be there when I get back in?
Skyroket said:
Hosed my Fascinate by trying to flash a recovery through Odin -> The recovery also had a kernel in the file that I didn't realize. Phone attempts to boot then reboots into recovery. I would prefer not to do a factory reset until I try reflashing the right kernel.
I am aware of this thread that used to have the file I need, but evidently the guy has removed it from his Dropbox now. Does anyone have a copy they can throw up for me? I think I could use the recovery image, too, but it is a little bit easier to find so don't go to great lengths for the recovery.
Will reflashing the correct kernel even fix my problem? I haven't touched /system. Should all my stuff still be there when I get back in?
Click to expand...
Click to collapse
If you have access to your sd card via windows, look for http://forum.xda-developers.com/showthread.php?t=1459905 on kernels. The stock is in post 1 at the bottom with the rest of the links. Download it, copy to your sd card and install it via recovery and it should work. If not, find droidstyle's guide, download the CWM 2.5 flash that in Odin, then install kernel.
Sent from my SCH-I500 using XDA App
Edit: Got it. Thanks!! It's booting up fully!!
Nothing below this line matters anymore, but I am leaving it for Google arrivals. The problem I list in this post was caused by excessive copying of the files. I first downloaded the file from the internet, copied it from Firefox downloads folder to my desktop, copied it up to my LAN server, copied it over to my Motorola Droid Bionic SD card, unmounted the SD card and put it into the Fascinate for installation.
The RIGHT way that worked was removing the network component. I just plugged the Bionic into the PC and mounted USB storage mode, copied files over, unplugged, let the SD card remount on the Bionic, manually unmount on the Bionic, remove the card and put it into the Fascinate.
Thanks for being patient with me. Your thread is obvious at the top of the forum but I ignored that method because it was flashing zips in recovery, which I couldn't get into at the time. I got the CWM 2.5 to work, and I did make a successful nandroid backup (will a factory reset restore the kernel, now that I have a backup?).
I did try to flash both versions of that stock kernel kernel-eh03-GB.zip and kernel-eh03-GB_signed.zip and get the same error on both. I even tried with a different SD card:
-- Installing: SDCARD:kernel-eh03-GB.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/kernel-eh03-GB.zip
(bad)
Installation aborted.​
I've tried downloading the files again, too. I wonder if it's worth noting that I did previously try to mount the SD card to Windows from CWM. It mounted, but when I tried to copy the file over, Windows told me the media was write-protected. WTF? Haven't seen that since floppies.
I think I'm going to call it a night and if I don't hear anything else on this in the morning I'll just do a factory reset and see if that restores the kernel. Then I can reinstall CWM and restore my backup. *long sigh*
Thanks again, man.
Skyroket said:
Thanks for being patient with me. Your thread is obvious at the top of the forum but I ignored that method because it was flashing zips in recovery, which I couldn't get into at the time. I got the CWM 2.5 to work, and I did make a successful nandroid backup (will a factory reset restore the kernel, now that I have a backup?).
I did try to flash both versions of that stock kernel kernel-eh03-GB.zip and kernel-eh03-GB_signed.zip and get the same error on both. I even tried with a different SD card:
-- Installing: SDCARD:kernel-eh03-GB.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/kernel-eh03-GB.zip
(bad)
Installation aborted.​
I've tried downloading the files again, too. I wonder if it's worth noting that I did previously try to mount the SD card in CWM. It mounted, but when I tried to copy the file over, Windows told me the media was write-protected. WTF? Haven't seen that since floppies.
I think I'm going to call it a night and if I don't hear anything else on this in the morning I'll just do a factory reset and see if that restores the kernel. Then I can reinstall CWM and restore my backup. *long sigh*
Thanks again, man.
Click to expand...
Click to collapse
Thats alright, dont worry about it man. Yeah it does sound like you need a factory reset. your phone isnt accepting the download. for ****s and giggles tho, try not using CWM to put the file onto your SD card, and plug it directly into your computer and redownload and transfer that way and see if it takes, if not then you'll definatly have to factory reset. Go here http://forum.xda-developers.com/showthread.php?t=1238070 Follow section 4 to return to stock. That should fix it.
Please note my previous edit. Thanks, again!
Skyroket said:
Please note my previous edit. Thanks, again!
Click to expand...
Click to collapse
Lol didn't see that till after I clicked reply. No problem. Glad you got it working bro
Sent from my SCH-I500 using XDA App

[Q] n7 wont boot

i tried to flash paranoid android on my n7 running stock 4.2( i was rooted and unlocked ) after flashing all i get is setup wizard has stopped repeatedly i can boot back to recovery but when i click on install zip there are no files there anymore and the backup i made is no longer there either im not sure what to do next i can get to bootloader and recovery but i cant mount sd card or do anything really any help would be greatly appreciated ive been googling for a couple of hours and cant find my specific problem thanks
Recovery > Factory Reset / Wipe
^ that should get it back to working
You can also "adb shell" in while in recovery and look if your backups are in a subfolder of /data/media, like /data/media/0 most likely.
And in the future always keep a copy of your backups on your PC
HellcatDroid said:
Recovery > Factory Reset / Wipe
^ that should get it back to working
You can also "adb shell" in while in recovery and look if your backups are in a subfolder of /data/media, like /data/media/0 most likely.
And in the future always keep a copy of your backups on your PC
Click to expand...
Click to collapse
i tried recovery but it does nothing im trying to set up adb but it just makes no sense to me at all its almost like the computer doesnt even see the phone i know it has to be something simple as to why i cant access the files from clockwork recovery but for the life of me i cant figure it out
Download Google Nexus 7 Toolkit V3.2.0
choose option "9. Download, Extract + Flash Google Factory Stock Rom and follow the instructions..
i had the exact same problem with my nexus 7 and this worked like a charm
hope it helps.
Thanks for the help but I fixed the problem. I let it boot to the setup screen where it kept saying setup wizard has stopped. From there I could recognize the device on a computer and transfer files over even though it read grouper on full android and not nexus 7. Now I'm on eclipse and it seems to be working great but I'm going to get rid of clockwork and install twrp just so I can hopefully not have that happen again. One weird thing though when I look for my backup I made prior to all of this and even the paranoid android ROM and gapps I can't find them anywhere on my SD card its like they literally vanished.
Sent from my Nexus 7 using Tapatalk 2
oogabooga912666 said:
Thanks for the help but I fixed the problem. I let it boot to the setup screen where it kept saying setup wizard has stopped. From there I could recognize the device on a computer and transfer files over even though it read grouper on full android and not nexus 7. Now I'm on eclipse and it seems to be working great but I'm going to get rid of clockwork and install twrp just so I can hopefully not have that happen again. One weird thing though when I look for my backup I made prior to all of this and even the paranoid android ROM and gapps I can't find them anywhere on my SD card its like they literally vanished.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Where did you copy the files to? I have the same thing. The only folders I have are: Alarms, android, carbon, clockworkmod, dcim, digital editions, download, mobile systems, movies music notifications pictures podcasts and ringtones?
Unless there is a wy for it to be an actual drive right now it shows up as a music device in my computer.
when you did a wipe did you wipe all data? I know when I went to flash a ROM I wiped data like I did with my bolt and it erased everything on my n7.
Sent from my Infected HTC Rezound using Tapatalk 4 Beta
Hi guys, I hope this thread is still active...
I'm having the same problem here. I tried installing cyanogenmod onto my n7 and am now getting the same "unfortunately, setup wizard has stopped" message. I've tried wiping the data and rebooting, to no avail. I have the toolkit, but it won't recognize the tablet so I can't reboot from there. I have a backup on my PC, but can't get to it! Sigh...
Thanks in advance for the help

Categories

Resources