Related
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.
Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
fastboot
just check for fastboot. the rest is easy cheeze.
how much is a good deal ?
unlocked $300 (cad)
What should I check? Instruct me plz, I never had a nexus one or even a Droid phone before ... (coming from 2 years old HTC cruise, with WM 6.5 with an XDA rom ....)
If I meet the guy, how to I check that hes not selling me a bricked nexus lol ?
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Amritttt said:
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Click to expand...
Click to collapse
are you 100% ?
I dont mind working on it, I just want to make sure that it is reparable via software/roms.
ppl plz tell yours, im just about calling this guy, really dont wanna waste $300
what is its restarts so much, that I cant flash the rom or something? there's no way that that could be the case, right?
sold ... goddamit lol But I'll get one one way or another
I was having this happen to me a lot. I moved in to a new place with no cable or internet yet, so my N1 was under extremely heavy use. And when it was warm, it would get both the touch screen problem and the random reboots.
I was using pershoots 2.35 Kernal. I went back to the stock kernal and the phone has since been running a lot cooler. Zero reboots, touch screen responds correctly. I take the stock kernal stability over an OC kernal any day.
It's a kernel issue that can most likely be fixed by flashing a new
ROM/Kernel, however there is always a small chance that it is triggered by faulty hardware.
My Nexus had this Problem Was unfixable by software. Hardware defect. I wouldn't buy.
Still waiting for my swap unit
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
xxlikquidxx said:
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
Click to expand...
Click to collapse
all is not lost if you can still get into hboot:
Have you tried to restore these original files via adb?
boot boot.img
recovery.img
system.img
I have this problem now...
It keeps on rebooting and rebooting ... and just comes not forther than the flashing X..
I tried system wipe but this didnt help ( I installed a battery widget which wasn't for my rom)
how can i restore my nexus now?
Pleas help!
Edit: Found a way...
Unlock you phone, fastboot, clockworkmod(?) recovery and the select the nandroid backup...
about passimg (see lower) i have no clue
passimg FRG33...
Sent from my Nexus One using XDA App
Even though solved, something to keep in mind: Its probably a ROM (or kernel issue as they said), but I had a revolving X due to a bad battery too.
it can be solved
ViSK said:
Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
Click to expand...
Click to collapse
4 color problem can be solved ..
I have rooted my fascinate, no problem, I have installed the Deodex, no problem, then I put the captivate keyboard zip on and rebooted, and the whole thing went to ****. I can't do anything except light up the keys, this is a real pain in the ass, especially since all the real hard stuff went smooth. I am now trying to boot into clockwork and I can't seem to do that.
What happens when you try to boot to Clockwork ?
If you've installed CWM, you should be able to get to a shell via adb and put the files back the way they were.. I know you can do this as long as you're at the recovery menu, but depending on what's happening during boot-up, it might allow access to the shell without getting to recovery.
Basically just run 'adb shell' from your command prompt and see what you get (obviously the phone needs to be connected via USB).
Thanks guys, i got it working but I was scared ****less. I managed to get to clockwork and luckily I had a backup so I restored from there, I believe the problem came from flashing deodex.
Sent from my SCH-I500 using XDA App
Had a problem which I thought was down to spilling wine on my phone (yeh not a good idea) however it may turn out to be the update to 2.3.4. Now the problem is that my computer wont recognise the phone at all and I have tried allsorts and after searching the web it seems the update has derped some peoples phones.
The problem now is that I went back to stock and now cant boot into recovery. Is there a way of putting the recovery img on to the phone via say Awesome drop or an alternative? I am still unlocked but got a stock rom on?
Haizum74 said:
Had a problem which I thought was down to spilling wine on my phone (yeh not a good idea) however it may turn out to be the update to 2.3.4. Now the problem is that my computer wont recognise the phone at all and I have tried allsorts and after searching the web it seems the update has derped some peoples phones.
The problem now is that I went back to stock and now cant boot into recovery. Is there a way of putting the recovery img on to the phone via say Awesome drop or an alternative? I am still unlocked but got a stock rom on?
Click to expand...
Click to collapse
If you still have root access you can use either the flash_image binary or Rom Manager to flash a new recovery.
If you do not then you will need to use fastboot and flash recovery manually.
Use terminal on your phone and flash recovery that way.
Sent from my Nexus S 4G using XDA App
No, not got root (just checked). Not 100% how to go about this if my comp isnt recognising my phone. Any ideas? Cheers
Maybe you could try another computer....or a Mac perhaps? (I have both, when one's acting up, i use the other)
Tried another and the same, it seems strange that it could be the USb port on the phone when its only happened after installing 2.3.4
Hey All,
I've never had issues installing roms in the past, but now that I have encountered a problem it seems to be a big one.
I 'updated' from a nightly build of CM10.2 to the Milestone 1 version of CM10.2.
My phone booted after the update, but things were closing and not responding, so I decided to see if a reboot would solve some issues. It didn't.
Now my phone won't get past the boot screen. When I go into recovery, CWM states that it can't mount or open /sdcard, /cache/recovery/log, /cache/recovery/last_log.
I can't do anything.
In addition, adb won't find my device.
Any suggestions?
Thanks
Are you using the latest version of CWM?
I am not. I believe the version I have is 6.0.2.3.
I was thinking I would be able to sideload the newer version of CWM, but couldn't find a way to do that if ADB won't recognize the device.
I suggest flashing the update again just to be sure. You can flash a new recovery from the bootloader using fastboot.
Welp, I think it's a lost cause. Device is now non-responsive to anything. It's been plugged into the wall-charger for a few hours now... Any attempt to turn it on or get into bootloader results in a red LED notification.
Thanks for taking the time to respond!