Database Users

[Q] Can't mount /dev/block/mmcblk0p8

I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.

DrPlumEU said:
I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.
Click to expand...
Click to collapse
try this
If you are using Thor's CWM. And his recovery only;
Here are the steps to completely wipe all internal data. And give it a clean internal system (according to Thor)
Note: Optional Formatting.
If you really want to remove EVERYTHING in Internal Memory, at this point, go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
Note, this will format EVERYTHING in internal memory (not ext sd card)
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
After you reboot, I believe it resets back to the defaults.
try to install the rom with the normal procedures.
this what i used and it worked great no problems
note** i am just fowarding info that was passed to me. and this will erase you backups
---------------------------------------------------------------------------------------------
IF you are running RA Revamped Recovery, then you may want to contact Drellisdee at his thread;
http://forum.xda-developers.com/show....php?t=1459821
He knows the procedures to do the same.it's a tricky process, and he knows more about his recovery than I do.

Thank you for the prompt response. Already tried your recipe with no luck.
I need access to the DATA partition and do not know how to go about that. Once have access to the internal disk, would like to know how to completely wipe this if that what it takes.
Thanks
PS: If I truly have bricked the device it is still in 12mo warranty, so will contact Acer care centre if no tricks work.
PPS: Maybe I now have excuse needed to upgrade to Tegra 3 device. The Acer Iconia A700 looks tempting

i think i have seen something like that when fixing mine but did not touch it....as im not a pro, hopefully somone with a litle more in depth knowledge sees this and can help.
sorry

Have you tried restoring your nandroid backup? This has recovered the error for me on my phone before when the /data partition became corrupt. Worth a shot.

Sadly, restoration of the nandroid backup was not successful.
I have notice that I pressed wrong volume button when attempting the hard reset. Will try the correct procedure later after work. Hopefully a proper hard reset then restore with one of Vache stock roms will have me up and running.
UPDATE: Sadly hard reset fails to load. My poor a500 needs resuscitation at acer clinic

I had the exact same problem, although I caused the problem in a different manner. You need to be able to use adb to get it going again. If you are not familiar with adb, do a search and you can find plenty of help. That's what I had to do. Unfortunately, my skills with adb are pretty much non-existent, so I can't really help you with that part.
Once you get adb going on your computer and it recognizes your A500, follow these steps:
You will need to boot into my recovery and open adb shell.
This will cause loss of all data contained on /data which will lose your /data/media.
From adb shell:
mount (This is to check data isn't mounted. If mounted use "umount data")
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8
After this is done your file system on /data will be fixed. You can install the ROM of your choice. Good luck!
(These instructions were originally provided to me by drellisdee)

Thanks for the answer on your previous post. I fixed my /data mount.
Love to unbrick my acer for the 50th time
Did not have this error tho, before I tried to convert the /data mount to ext4

DrPlumEU said:
I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.
Click to expand...
Click to collapse
If you switch the A500 off and whilst switching it on hold the volume up button and start toggling the rotation lock on and off it should clear the internal memory completely. Then flash an update.zip from a MicroSD. Otherwise use the Iconia software update tool that's floating around in APX mode. Make sure you have your UID for this

Ping192 said:
Did not have this error tho, before I tried to convert the /data mount to ext4
Click to expand...
Click to collapse
That's exactly what caused my problem. Glad you are working again.

Resolved by great customer support...
To close this thread I wish to congratulate the Acer customer support team in Plymouth who have restored my Acer Iconia A500 to working order in under a week.
It is upgraded OTA to Android 3.2.1.
As still in warranty, no charge for the failure of the hard-drive partitioning!
Great work. Good customer service.

thanks lovable people in this thread
thanks lovable people in this thread you solved my problem . especially Dr. McKnight (23rd February 2012, 03:48 PM) back in the beginning of the thread. His solution using thor's recovery was enough to solve my problem. Wonderful and thank you
/Mikkel

spoupard said:
From adb shell:
mount (This is to check data isn't mounted. If mounted use "umount data")
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8
Click to expand...
Click to collapse
When I do the "mke2fs -j -b 4096 /dev/block/mmcblk0p8" command from adb's shell, it takes forever (I let it run for hours). Something I was thinking about, could I simply "rm -rf /dev/block/mmcblk0p8" first, and then run the above commands? Also, should I not add the "-t ext4" option to the mke2fs command?

kerijan2003 said:
When I do the "mke2fs -j -b 4096 /dev/block/mmcblk0p8" command from adb's shell, it takes forever (I let it run for hours). Something I was thinking about, could I simply "rm -rf /dev/block/mmcblk0p8" first, and then run the above commands? Also, should I not add the "-t ext4" option to the mke2fs command?
Click to expand...
Click to collapse
Try in fastboot mode execute:
fastboot -w

Can't access anything in my N7

Hi all, I tried searching through the forums and I wasn't able to find a solution and was hoping you could help me out.
I recently tried flashing a custom rom and because it was giving me problems, I decided to go back and recover from my back up.
But everytime I tried, it tells me that "Couldn't open directory. No files found."
I found this to be odd, so I rebooted back in the rom and tried to see if I could go through the N7 to put a new .zip file to flash.
When I go into Nexus 7 in My Computer, it just shows up blank.
I'm guessing there is something going on that messed up my ability to access the device storage.
If I go into mounts and storage in CWM, my /sdcard and /system are not mounted.
So I tried mounting both. /system mounts up just find, but /sdcard doesn't.
I'm not sure if this is significant, but in CWM, if I go to "install zip from sd card" -> "choose zip from sdcard" it doesn't show up what it used to which was just all the folders and such in my N7.
It now shows, 0 /, clockworkmod/, legacy/ and obb/...
I also tried to reinstall all drivers on my computer in case that was what was causing an issue. But it didn't fix the problem.
Does anyone have a solution?
The device itself seems to be recognized by my computer..
Would I be able to use the Nexus 7 tool kit to flash back to stock to unroot again?
Thank you in advance!

I had a similar problem, but it was a while ago. Can't quite remember but I think uninstalling the drivers, unplugging the device, turning off usb-debugging and then plugging it back in fixed it. YMMV.
Hope it helps.

rotarynerd said:
I'm not sure if this is significant, but in CWM, if I go to "install zip from sd card" -> "choose zip from sdcard" it doesn't show up what it used to which was just all the folders and such in my N7.
It now shows, 0 /, clockworkmod/, legacy/ and obb/...
Click to expand...
Click to collapse
I believe that is significant. With 4.2.x, the "SD card" mount is now supposed to happen at
/data/media/0
instead of
/data/media
I use TWRP (not CWM) but I too experienced a "missing backup" issue, and then later found it at
/data/media/TWRP
rather than
/data/media/0/TWRP
If I were you I would poke around using a root file explorer and see if you have backup data in either
/data/media/clockworkmod or
/data/media/0/clockworkmod (or even)
/data/media/0/0/.../0/clockworkmod
then (a) use a recovery which can succeed at "mount /sdcard", and (b) move the clockworkmod folder using your (root-aware) file manager so it is within the /sdcard mount point of the recovery.
There has been some recent flux in the past few months with buggy behaviors in custom recoveries, including that 0/0/0.../0 phenomenon; it might be time for you to upgrade your current recovery to a newer version.
usually a mount failure happens for only one of two reasons:
- the mount point doesn't exist, or
- the file sysem is corrupted.
Seems improbable that it could be the 2nd of those issues - the "/sdcard" mount point is a little bit odd - it is sort of like a "hard link" or loopback mount with some behaviors that mask the underlying (true) file ownership information. If the underlying /data (ext4) filesystem was corrupted, then /data itself would also not be mounting. That would certainly wedg your ROM boot though, and it sounds as if your ROM is operating adequately.
Note that the possibility does exist that you simply erased or formatted your entire /data partition at one point or another and those backups actually got erased.
good luck

[Q] Yet another bricked defy. can't restore cwm backup

Hi,
well... what can i say... i bricked my beloved defy. =(
How it happened:
Since Quarx's CyanogenMod 7 i used several CyanogenMod Versions from Quarx und Epsylon until about 2 weeks ago. I had the CM10 (4.1.2) Version from 11.05. installed.
Then i saw Quarx new release from 16.06.
Before i flashed the new version i made a full backup with cwm 5.7.0. Then i installed the new version trough cwm. everything look fine. But there wen't something really wrong. After rebooting the phone got stuck even before 2ndinit. I tried it several times but the the phone wasn't booting any more.
I thought: no problem. I have a backup. Let's restore is quickly. The easiest way to me was:
- start the phone in bootloader
- flash a stock sbf with rsd lite (sbf: JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_UCAJRDNFRYORTCOREEU_P023_A008_HWp3_Service1FF.sbf
- root the phone with superoneclick
- install 2ndinit for defy (SndInitDefy_2.3.apk i think it's cwm 5.0.3.1)
- restore backup
but here the problem beginns trying to recover /system(log from recovery):
2013-06-17.15.18.36:
logo.img is present. 1024 kB
recovery.img is present. 8192 kB
devtree.img is present. 512 kB
boot.img is present. 8192 kB
data.ext3.tar is present. 1039389 kB
system.ext3.tar is present. 323612 kB
Checking MD5 sums...
./system.ext3.tar: OK
I:couldn't find default type
Found new backup image: /sdcard/clockworkmod/backup/2013-06-17.15.18.36//system.ext3.tar
Restoring system...
Skip system unmount, remount read-only
Remount /system read-only
I:/system is not safe to format
I:Erasing from device...
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Skip system unmount, remount read-only
Remount /system read-only
50-cm.sh60-baseband.sh70-bootmenu.sh70-gapps.sh80-battd.shApollo.apkApplicationsProvider.apkAudioEffectSettings.apkBackupRestoreConfirmation.apkBluetooth.apkBrowser.apkCMFileManager.apkCMFileManagerThemes.apkCMWallpapers.apkCalculator.apkCalendar.apkCalendarProvider.apk
..... and so on and so on. (is quite a long list ).....
Error while restoring /system!
Problem while restoring system !
-------------------------------------------------------
i tried so many things like:
- install cm10 an try restoring with cwm 5.7.0 (same error)
- different stock sbf's (makes no difference)
- extracting system.ext3.tar and copying i to /system with adb (stops copying at about 50%)
and much much more... i forgot the rest ^^
the thing is.... i have no idea what exactly is going wrong. In my opinion it's here in the log: "Remount /system read-only". how should cwm be able to write the backup into system i it is mounted as "read-only".
im working on it since the last 2 weeks and it is getting super frustrating =(
Hopefully someone has better ideas than me? I would appreciate it.
At least: thanks for reading!

There are 2 possibilities according to me (I may be wrong:silly
1. Your backup might be corrupt -> try another backup
2. Your eMMC memory chip may be corrupt -> send your phone for service
TRY Wipe system cache and data then restore.
OR
Install CM10 with cwm (example 26 March build), restore only data, then dirty flash the latest CM10 (only wipe cache and dalvik). Old builds of CM10 can cause problems.

hotdog125 said:
There are 2 possibilities according to me (I may be wrong:silly
1. Your backup might be corrupt -> try another backup
2. Your eMMC memory chip may be corrupt -> send your phone for service
TRY Wipe system cache and data then restore.
OR
Install CM10 with cwm (example 26 March build), restore only data, then dirty flash the latest CM10 (only wipe cache and dalvik). Old builds of CM10 can cause problems.
Click to expand...
Click to collapse
Thank you for your answer!
I believe the backup files are ok. md5 is ok and the recovery log says: backup ok, but internal storage.... is weired.
Maybe a fried eMMC. But how? And buying a new phone is sadly way cheaper than service.
I wiped cache and data endless times. But no luck.
Is it possible to wipe (format) system?
I installed different versions from cm10 and they are running fine. But i really would like to restore my backup. There's a lot of work in it. =(
Tried this also 2 times: http://forum.xda-developers.com/showthread.php?t=1807899
But with this method, the phone won't boot up and got stuck in a bootloop. Can't even see the cm logo. An it makes no difference what version of CM10 is installed.

dediknight said:
Thank you for your answer!
I believe the backup files are ok. md5 is ok and the recovery log says: backup ok, but internal storage.... is weired.
Maybe a fried eMMC. But how? And buying a new phone is sadly way cheaper than service.
I wiped cache and data endless times. But no luck.
Is it possible to wipe (format) system?
I installed different versions from cm10 and they are running fine. But i really would like to restore my backup. There's a lot of work in it. =(
Tried this also 2 times: http://forum.xda-developers.com/showthread.php?t=1807899
But with this method, the phone won't boot up and got stuck in a bootloop. Can't even see the cm logo. An it makes no difference what version of CM10 is installed.
Click to expand...
Click to collapse
Yes, wiping system is important in this case. The option is present on the main screen of CWM.

hotdog125 said:
Yes, wiping system is important in this case. The option is present on the main screen of CWM.
Click to expand...
Click to collapse
I would like to format /system. But how? I can't find this option in cwm (5.7.0).
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and restore
- Mounts and storage
- Advanced
- Power off
- Exit Recovery
- Go Back
It is possible to format some unmounted partitions in "Mounts and storage". But if i unmount /system there is only the option to "remount /system" but nothing linke "format /system".

dediknight said:
I would like to format /system. But how? I can't find this option in cwm (5.7.0).
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and restore
- Mounts and storage
- Advanced
- Power off
- Exit Recovery
- Go Back
It is possible to format some unmounted partitions in "Mounts and storage". But if i unmount /system there is only the option to "remount /system" but nothing linke "format /system".
Click to expand...
Click to collapse
My bad. You can try Defy full wiper (DO NOT REBOOT AFTER FULL WIPE).

hotdog125 said:
My bad. You can try Defy full wiper (DO NOT REBOOT AFTER FULL WIPE).
Click to expand...
Click to collapse
Thank you very much. Sadly, it wasn't the solution to my Problem. But the error messages getting a bit clearer now ^^.
Here is the recovery log:
-- Installing: /sdcard/defy_fullwipe_ext3.zip
Finding update package...
I:Update location: /sdcard/defy_fullwipe_ext3.zip
Opening update package...
Installing update...
FULL WIPE FOR MOTO DEFYmount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p25 at /data: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
.
..
...
....
.....
......
.......
........
.........
..........
...........
***********
script result was [because /system got wiped]
Congrats, your ass is now wiped
!!Do not reboot now!!
If you do, you will have to flash an SBF
because /system got wiped
Install from sdcard complete.
2013-06-17.15.18.36:
logo.img is present. 1024 kB
recovery.img is present. 8192 kB
devtree.img is present. 512 kB
boot.img is present. 8192 kB
data.ext3.tar is present. 1039389 kB
system.ext3.tar is present. 323612 kB
Checking MD5 sums...
./system.ext3.tar: OK
I:couldn't find default type
Found new backup image: /sdcard/clockworkmod/backup/2013-06-17.15.18.36//system.ext3.tar
Restoring system...
Skip system unmount, remount read-only
Remount /system read-only
E:format_volume failed to unmount "/system"
Error while formatting device /system!
Problem while restoring system !
--End of log--
OK, somehow the devices are "busy" so the wipe script couldn't wipe. Although in cwm it said it was successful.
So i tried unmounting /system, /cache and /data before running the script. Here's what i got:
-- Installing: /sdcard/defy_fullwipe_ext3.zip
Finding update package...
I:Update location: /sdcard/defy_fullwipe_ext3.zip
Opening update package...
Installing update...
FULL WIPE FOR MOTO DEFYmount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p25 at /data: Invalid argument
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
unmount of /data failed; no such volume
script result was [because /system got wiped]
.
..
...
....
.....
......
.......
........
.........
..........
...........
***********
Congrats, your ass is now wiped
!!Do not reboot now!!
If you do, you will have to flash an SBF
because /system got wiped
Install from sdcard complete.
--End of log--
Is it possible to do something about the "busy" partitions. Whatever they're busy doing

Check out these threads, not sure they'll help - http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/.
AND http://forum.xda-developers.com/showthread.php?p=20707200
Your partitions may be in the wrong format.
EDIT - You can try starting from sbf, then installing your preferred CM10 release, and then extracting the backups into the respective directories using ES file explorer (only the files that you've changed).
EDIT 2 - Install CM10 with clockworkmod (not TWRP) and then go to bootmenu (press go back on the main screen of recovery), and then format system and data to ext4, and then try restoring backup. <------ try this first

why??
sir. i tried this 2 xperia ROM. my unit is OT 918n. i completed the installation of BRAVIA_LACV--Es_V4 & Xperia by Jarey..
why is it the screen wont work. i mean the touch panel. so i can setup the setting at 1st boot. why it wont work the touch panel??
and 1 thing. i backup 1st my phone before i follow this instraction. just keeping safe. and if i restore the backup it stock in the white alcatel with sounds. just in their always repeating it will not continue to the main menu. WHy? can you answer it please.

chawnix said:
sir. i tried this 2 xperia ROM. my unit is OT 918n. i completed the installation of BRAVIA_LACV--Es_V4 & Xperia by Jarey..
why is it the screen wont work. i mean the touch panel. so i can setup the setting at 1st boot. why it wont work the touch panel??
and 1 thing. i backup 1st my phone before i follow this instraction. just keeping safe. and if i restore the backup it stock in the white alcatel with sounds. just in their always repeating it will not continue to the main menu. WHy? can you answer it please.
Click to expand...
Click to collapse
You are in the wrong device forum.
Sent from my Nexus 7 using Tapatalk

:good::fingers-crossed:Thank you, i have a similar problem. My battery's Defy was completly discharge. Normaly, i plug my Defy, wait for 10 % charging, and i turn it on and i let the battery charging all night. But, i forgot to turn my defy on, and the morning when i turn it on, the cyanogen 7 logo bootloop.
I do a wipe system reset to factory, the defy turn on, and when i restore my backup, bootloop again.
I do what hotdog125 write, i was thinking its works, but it didn't.
I lost my data, :crying::crying::crying::crying: but i have a nice cyanogen 10 bootloop :laugh::laugh::laugh:

I finaly restore my defy with a backup do with recorvery when my phone make a bootloop.
I put cyanogen 7 and i found an application name Nandroid Manager http://forum.xda-developers.com/showthread.php?t=2044414 , 1,46 euros, that permit to restore all or a part of the backup you do.
I restore my apps, my sms, my mms, my call log etc... i want to keep. My contact was backup on my gmail account.
Like i saw it works, i put cyanogen 11 and redo the partial restore.
My defy was fine, and increased from mb525 to mb526 when i install Cyanogen 11.
I recommand when you have an android phone to root it, put an recorvery, put Nandroid Manager and backup with recorvery regularly, you could restore all your phone if you don't change your rom, or resotre partial data if you change your rom.
Thank you to your site.:laugh::highfive:

[Q] system partition corrupted (can't umount)

Just now after a reboot, I found that Google Play Service stops working. It happened quiet a few times before, so I decided to do what I always do - remove the Google Play Service and flash it again.
So I rebooted into recovery, removed gapps backup script under /system/addon.d using Aromafm, and tried to flash the latest CM nightly - and the flash failed with status 7.
Then I found that I can no longer boot into system, but I still have access to boot loader (fastboot) and recovery. So I begin to check what's wrong with my /system partition and found that once it's mounted, I can not umount it. At first I thought it's a file system problem so I tried to fix it with e2fsck - but I can't umount it so e2fsck won't work!
So I rebooted my phone again, executed e2fsck -cfy /dev/block/platform/msm_sdcc.1/by-name/system but it didn't show any error - it's like the file system is file but I just can't umount it for some reason I can not understand (If I try umount it, I'll get "invalid arguments")
Lucky enough there's nothing wrong with the secondary system partition (I have TDB enabled before and always been using system1) so I managed to flash the latest nightly to system2 and get my phone booted, but I still can't get access to system1
Anyone, help :crying:

Update
This is becoming weirder and weirder...
After a few days of usage, I did a lot modification to 2nd /system partition, I noticed that sometimes I got boot loop - if I connect the phone to my laptop and use adb logcat I can see the logcat loops forever. Using adb reboot can make my phone reboot and get into Android system.
So I powered off my phone, booted to recovery, and as I expected, the same thing happens to 2nd /system partition - it can be mounted with no problem, but I can not unmount it (except for power off the phone, of course)
I thought maybe there's something wrong with that partition, maybe bad block or whatever, so I copied the entire 2nd /system to 1st /system partition using dd - Then the 1st /system partition can't be unmounted as well.
Now I'm f_cked, so I decided to format 1st /system partition once again and start fresh, after format I went and try mount then unmount 2nd /system partition - now it can be successfully unmounted. I was shocked at the time that I thought something went wrong I acturally formatted both partitions, but turns out all data in 2nd /system partition is fine and the "can't unmount" issue is gone.
Now boot loop doesn't happen anymore, but I'm too afraid to do any more modifications to /system partition, therefore I have skipped a few nightly updates. I won't risk brick my phone until I can get my hands on a new one (It's just too hard to find a phone that has a great performance and not that freaking huge! Seriously, I would buy another Mi 2S if they still sell it.)
Does anyone know what could possibly happening here... I'm so confused...

Restore Rom Install Failed (Simple Touch) Tried Everything - no Dice. Please Help :)

The Issue
Hi, I have a Nook Simple Touch that gets stuck trying to boot. First I see the Barnes and Noble Screen, Next for a brief moment it tries to load a Rom and shows a small nook icon with a loading bar. Next it says "Install Failed". I am unable to do anything other than a factory reset, which doesn't help.
Background
I should add that the device previously was working fine, then one day it froze as I was highlighting some text. When I tried to boot it, it was stuck in the scenario described above. I believe it was already updated to 1.2.2 with seemingly no issues.
What I've tried:
I have tried restoring it back with noogie and a backup, and I have also tried the Nook Manager- Rescue from .zip and Rescue from backup to no avail. Still get that same blasted "Rom Restore Image" Screen followed by "Install Failed".
I have an update from Barnes and Noble called "nook_1_2_update.zip" which I tried to copy over to the nook but the file is too large.
Any ideas? I love this thing and don't want to let it go!:crying::good:

I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?

Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?

Trigrammaton said:
... I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
Im not quite sure. Another version, etc...
You can use NST boot partition image from this post
For preparing another booting SD card too...

Trigrammaton said:
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
If you restore the image from a different device the serial number, MAC address, etc. will be messed up. You will never be able to register the device. This may not be an issue, but just so you are aware.

nmyshkin said:
If you restore the image from a different device the serial number, MAC address, etc. will be messed up.
Click to expand...
Click to collapse
The serial number is written inside the little door for the SD card (if you haven't worn it off).
The serial number and the MAC are also on a sticker in the inside.

ucy74 said:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Click to expand...
Click to collapse
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen. What do you mean by "new" sd? If i put a blank sd into the slot and boot?
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!

Trigrammaton said:
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen.
Click to expand...
Click to collapse
Super, it means so You can connect to Your Nook and dump boot partition files to PC using ADB.
What do you mean by "new" sd? If i put a blank sd into the slot and boot?
Click to expand...
Click to collapse
You can copy files dumped above onto vfat formated SD card. Then try to boot from this "new" - freshly prepared card. Check whats happen.
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Click to expand...
Click to collapse
NOT SO FAST!!! Do not put linked partinion into nook! There are different cases and commands to do that. If You are new to ADB lets try to dump boot partition first, as mentioned before. Maybe there will be not necessary to replace whole partition rather than single file.
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Click to expand...
Click to collapse
Prepare this dumped SD first. We try to heal it to make bootable...

Thanks! I will give it a whirl this weekend and report back. Really appreciate you taking time to respond - Very kind of you!