Guest Alien*46*UK Posted December 24, 2009 Report Posted December 24, 2009 Hi All I get an annoying error when trying a Nadroid + Ext backup: Error: Run 'nandroid-mobile.sh' via adb! A Normal Nandroid backup is fine, but the Ext is the issue. Currently only running the December update with Superboot and Custom Recovery. Running the stock 2Gb card but have a SanDisk 8Gb waiting to be used (maybe an issue with the stock card?) ... Only did the December update, superboot and recovery program this morning, before that it was running completely standard with an Earlier Build Date ... Now reads November something after December update installed. Many thanks in advance. P.s. I searched and search for a result with no joy. I was sure vB had a topid search function but obviously not.
Guest Dan Mullen Posted December 24, 2009 Report Posted December 24, 2009 Hi All I get an annoying error when trying a Nadroid + Ext backup: Error: Run 'nandroid-mobile.sh' via adb! A Normal Nandroid backup is fine, but the Ext is the issue. Currently only running the December update with Superboot and Custom Recovery. Running the stock 2Gb card but have a SanDisk 8Gb waiting to be used (maybe an issue with the stock card?) ... Only did the December update, superboot and recovery program this morning, before that it was running completely standard with an Earlier Build Date ... Now reads November something after December update installed. Many thanks in advance. P.s. I searched and search for a result with no joy. I was sure vB had a topid search function but obviously not. Are you getting the error on backup or restore? I know there was an issue with nandroid+ext restore in AMON-RA 1.5.1. This is fixed in 1.5.2.
Guest Alien*46*UK Posted December 24, 2009 Report Posted December 24, 2009 It's during backup ... Sorry, forgot to mention that ... Also running the latest AMON-RA as link by the sticky.
Guest Neron Posted December 24, 2009 Report Posted December 24, 2009 Hi All I get an annoying error when trying a Nadroid + Ext backup: Error: Run 'nandroid-mobile.sh' via adb! A Normal Nandroid backup is fine, but the Ext is the issue. Currently only running the December update with Superboot and Custom Recovery. Running the stock 2Gb card but have a SanDisk 8Gb waiting to be used (maybe an issue with the stock card?) ... Only did the December update, superboot and recovery program this morning, before that it was running completely standard with an Earlier Build Date ... Now reads November something after December update installed. Many thanks in advance. P.s. I searched and search for a result with no joy. I was sure vB had a topid search function but obviously not. It might be down to capacity of speed of the sd card as I dont have any issues with the Nadroid + Ext on my phone same MCR but I have a 8gb class 6 card.
Guest Alien*46*UK Posted December 24, 2009 Report Posted December 24, 2009 Hmm I'll give it a try, I'll just go ahead with a ROM install withough the EXT backup ... (Assume this is just a backup of thw SD card??) ... The important stuff will be on the Nandroid anyways ... Then once the 8Gb has some data I'll try again ... And yeh, mine is a class 6.
Guest Alien*46*UK Posted December 24, 2009 Report Posted December 24, 2009 98% odd ... Fresh charge, currently 100% and still does it.
Guest scoobydoo99 Posted January 2, 2010 Report Posted January 2, 2010 98% odd ... Fresh charge, currently 100% and still does it. I got the same error message trying to do a backup of Nandroid + Ext. Solved by only backing up Nandroid without the Ext.
Guest Dan Mullen Posted January 2, 2010 Report Posted January 2, 2010 I got the same error message trying to do a backup of Nandroid + Ext. Solved by only backing up Nandroid without the Ext. Maybe try a repair of the ext partition prior to the nand+ext backup?
Guest niko1986 Posted January 2, 2010 Report Posted January 2, 2010 That error was supposed to be fixed in the 1.5.2 version of the recovery for HTC devices on xda developers, i think the bug perhaps wasnt fixed in the Pulse version by Amon Ra.
Guest Dan Mullen Posted January 2, 2010 Report Posted January 2, 2010 That error was supposed to be fixed in the 1.5.2 version of the recovery for HTC devices on xda developers, i think the bug perhaps wasnt fixed in the Pulse version by Amon Ra. It works on my brother's Pulse running 1.5.2.
Guest Josh04 Posted January 2, 2010 Report Posted January 2, 2010 Do you have an ext partition on your memory card at all? If you don't it errors out like that.
Guest Alien*46*UK Posted January 3, 2010 Report Posted January 3, 2010 (edited) Do you have an ext partition on your memory card at all? If you don't it errors out like that. I do. SWAP = 0; EXT4 = 512; Rest is the norm FAT32. I've not tried it since putting in the new card, so will give it a try at some point. Edited January 3, 2010 by Alien*46*UK
Guest niko1986 Posted January 3, 2010 Report Posted January 3, 2010 It works on my brother's Pulse running 1.5.2. The bug happens intermitently for me
Guest Dan Mullen Posted January 3, 2010 Report Posted January 3, 2010 The bug happens intermitently for me It did for him to - I meant that the repair option in the recovery menu works OK. Since switching to ext3 he hasn't had the problem, but I don't think he has rebooted too many times since then, so we'll see...
Guest niko1986 Posted January 3, 2010 Report Posted January 3, 2010 It did for him to - I meant that the repair option in the recovery menu works OK. Since switching to ext3 he hasn't had the problem, but I don't think he has rebooted too many times since then, so we'll see... Seems i should try ext3 cos im hating how slow the tmobile original firmware is :S
Guest Casper-vH Posted January 3, 2010 Report Posted January 3, 2010 I hade the same error. Tried running it drom adb, didnt work either. My problem was that there was already a nandroid backup. I deleted the nandroid folder on my SD card ( I guess renaming or moving to your pc will work too). Then I tried again and it worked fine :)
Guest Dan Mullen Posted January 3, 2010 Report Posted January 3, 2010 Ah well, it turns out that moving from ext2 to ext3 hasn't solved the problem of not being able to install apps after a reboot. My brother had to repair it again today. A2SD seems very flaky in the Pulse ROMs...
Guest giryan Posted January 4, 2010 Report Posted January 4, 2010 Ah well, it turns out that moving from ext2 to ext3 hasn't solved the problem of not being able to install apps after a reboot. My brother had to repair it again today. A2SD seems very flaky in the Pulse ROMs... Yeah, I deleted my ext partition entirely, and haven't had any issues at all since. Prior to that I had 5-6 instances of the issue where the phone totally fails to boot, and countless times I had to repair ext.
Guest TylerDurdenK Posted January 7, 2010 Report Posted January 7, 2010 I am having this issue too. Cannot perform a Nandroid and Ext back either. I am using the new v1.5.2 recovery too.
Guest vatvedt Posted March 9, 2010 Report Posted March 9, 2010 Yeah, I deleted my ext partition entirely, and haven't had any issues at all since. Prior to that I had 5-6 instances of the issue where the phone totally fails to boot, and countless times I had to repair ext. Does repairing the ext partition lose the data? Or is the data intact after an repair?
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now