Bell Galaxy S dead (unable to mount /sdcard) -> LAGFIX Problem? - Vibrant Q&A, Help & Troubleshooting

Hi Guys.
I have a Galaxy S on bell's network, running JPK.
I looked at my phone last night and there was an orange "!" caution icon in the notification area. Said something about the internal sdcard not unmounting properly. So I rebooted the phone and now its booting to a black screen.
I have Ryan's OCLF from the market installed. I'm not sure if this is what is causing the problem (may be confused about ext2?)
I can boot into recovery, but no access to su from there. I can get into download mode. I tried re-flashing JPK, which flashed ok but I still have the same problem.
The error I'm seeing in recovery is:
E:Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
I tried flash sdcard from recovery but didnt work.
Can anyone help me get my phone back? I heard flashing stock 2.1 Bell firmware may fix my issue, but I don't have that firmware. Please help!

This should help.
http://forum.xda-developers.com/showthread.php?t=739091

this will work for you
this is the erro that comes up
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
this is the way you fix the problem.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine

You might be better off sticking to the i9000 forums in the future, given that your Bell Vibrant resembles our T-Mobile Vibrant in name only. It's far more similar to the international i9000.

alcangel64, will this work with the GT-i9000? I also see the caution about don't do it if you've flashed JP3.. should I ignore that warning?
alcangel64 said:
this will work for you
this is the erro that comes up
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
this is the way you fix the problem.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine
Click to expand...
Click to collapse

while in recovery mode, if you have adb installed u can adb reboot download and it'll take u to download mode. Then you'll be able to restore through odin. But I warn u, if it has something to do with the filesystem (ext2, ext4) ur in for a long ride. Other day I spent all day trying to get my phone to boot after flashing like 20+ times in odin due to an error in my filesystem

I think the title is bit misleading. It was likely not JPK that broke but rather the EXT2 loopback created by the lag fix. You might consider changing the title of the thread to something else.
If you get it working again, I wouldn't suggest applying the OCLF again. When the internal SD mounted improperly, it was likely corrupted. This can happen at anytime since the EXT2 is not journaled like Samsung's RFS or EXT4. You might be able to fix the file system corruption if you can run fsck on it through ADB.
Selecting the repartition option in ODIN may get you past any file corruption issues with the SD but it will wipe your internal SD. So, just restore from backup.

I agree. I think it was the lagfix, ultimately. I think the problem now is that I can't reflash because none of these PDA firmwares know anything about ext2.
Are there any releases with ext2 enabled right in the firmware? That might let me re-mount /sdcard at least, or at least remove the symbolic links?
epakrat75 said:
I think the title is bit misleading. It was likely not JPK that broke but rather the EXT2 loopback created by the lag fix. You might consider changing the title of the thread to something else.
If you get it working again, I wouldn't suggest applying the OCLF again. When the internal SD mounted improperly, it was likely corrupted. This can happen at anytime since the EXT2 is not journaled like Samsung's RFS or EXT4. You might be able to fix the file system corruption if you can run fsck on it through ADB.
Selecting the repartition option in ODIN may get you past any file corruption issues with the SD but it will wipe your internal SD. So, just restore from backup.
Click to expand...
Click to collapse

What did you do to fix it? Problem is I can't su in recovery mode. If I could I could at least remove the ext2 symbolic links and continue.
jroid said:
while in recovery mode, if you have adb installed u can adb reboot download and it'll take u to download mode. Then you'll be able to restore through odin. But I warn u, if it has something to do with the filesystem (ext2, ext4) ur in for a long ride. Other day I spent all day trying to get my phone to boot after flashing like 20+ times in odin due to an error in my filesystem
Click to expand...
Click to collapse

moophone said:
Are there any releases with ext2 enabled right in the firmware? That might let me re-mount /sdcard at least, or at least remove the symbolic links?
Click to expand...
Click to collapse
The stock 2.1 / 2.2 kernel should already support EXT2 however it won't mount a corrupted / damaged partition. You should try flashing back to 2.1 with the repartition option checked through ODIN. Once the internal SD is formatted by the repartition, it should then finally mount. It will also return everything back to RFS.

What kernel exactly? I tried flashing i9000_Kernel.tar, and then I9000XXJPH_KERNEL.tar from JPH. I tried JPC. I don't have a stock Bell kernel but none of those did anything.
Could you refer me to a specific kernel that will restore the /sdcard partition?
Thanks,
Greg
epakrat75 said:
The stock 2.1 / 2.2 kernel should already support EXT2 however it won't mount a corrupted / damaged partition. You should try flashing back to 2.1 with the repartition option checked through ODIN. Once the internal SD is formatted by the repartition, it should then finally mount. It will also return everything back to RFS.
Click to expand...
Click to collapse

moophone said:
What kernel exactly? I tried flashing i9000_Kernel.tar, and then I9000XXJPH_KERNEL.tar from JPH. I tried JPC. I don't have a stock Bell kernel but none of those did anything.
Could you refer me to a specific kernel that will restore the /sdcard partition?
Thanks,
Greg
Click to expand...
Click to collapse
After about 30 tries I was able to boot my phone with UGJH2. The funy part is for it to work and boot OK .. I have to leave my external SD card in it. It will error saying that it can't mount it once booted and both my internal 16G sd or my external 8G sd can't be mounted. All the rest of the phone works perfectly. If there was just a way for format or repartition the internal SD card from in the OS or ADB it would be fine. At least my phone now works until I can get a replacement phone from bell.
I tried to remove the external SDcard and the phone crashed. If I leave it in there , it works fine ??

Having this problem after flashing jp6 on my Bell i9000m. It worked great for like 2 days but suddenly it stopped working and i can't boot anymore. I did apply a lagfix but i removed it soon after because i did not see any speed improvements. Downloading the roms suggested in this thread right now... hope it works

Flashing again doesn't help*
I've flashed back to stock rom and used wipe factory and cache, but it still doesn't fix the issue.
I've read something about using adb to fix it, however adb doesn't even reconize my damn phone. Odin does on the other hand.
If adb reconize your phone, you should be able to push some files,and follow some other procedures to fix the internal sd card then flash it again with odin.
The other solution is changing your internal sd card, don't know how though people have sent back their device to their carrier or went to phone shop, i heard it costs one guy around 80$ to change it.

Related

{FIXED} :) 0.00 internal storage problem

ok i flashed with odin back to stock but now my internal storage is at 0 ..any ideas?
{FIXED}
This is what i did
1. Flash Odin Stock http://forum.xda-developers.com/showthread.php?t=782204
2. Root Phone Via One click root http://forum.androidcentral.com/fasc...-how-root.html
3. Remove Voodoo & Replace Files http://forum.xda-developers.com/showthread.php?t=804784
4. After step 3 do not restart just yet While in clockwork after you install Stock.zip go to "WIPE DATA" then "Restart"
It should work now. it did for me... *THANK THE HEAVENS* and the devs on here. i didnt have to do that long ass process that was stated earlier even though it was much
Did you wipe and format your sd card. Cause that's where the voodoo file is located. Delete and redo Odin.
also if u flashed with Odin back to stock u must do the disable lagfix. First off, I take it u flashed voodoo, before u flashed back to stock with Odin did u disable the lagfix?
Sent from my SCH-I500 using XDA App
i thought i wiped it... so if i didnt how do i get rid of it..i tried the adb push but it kept telling me premission denied even though i could get into adb shell
HELP*** lol
Install v0.2, it fixes the internal storage problem.
OK here is what I would do. I would do the root explorer thing and add the folder disable_lagfix in sdcard>voodoo. Add the folder there and turn off the phone, then power up the phone. The phone will acknowledge the disable lagfix you installed. Give it some time . Then once the phone reboots, check your internal memory.
i cant download and install anything because of the damn 0 internal
can you get into your sd card at all?
i reformated it now i put the update.zip back on the root for clock work but now i cant boot into clockwork via normal recovery using update.zip gives me a failed signature error
oik i see odin has a option for re partition next to auto boot..should i do that?
I'm having the same problems as you. Hope someone can figure this out. I went thru with odin restore after voodoo messed things up now I am stuck.
geez i keep gettin a E: cant mount /dv/block/mmcblk0p1 (invalid argument)
Idk what the hell you are talking about. Take out your sd card completely. Put another sd card in there format it to your phone. Do Odin on your phone. Odin clockwork recovery. Apply update DI01. Then root it. Now put back your 16gb sd, format it first before hand. Then flash voodoo.
dialect129 said:
geez i keep gettin a E: cant mount /dv/block/mmcblk0p1 (invalid argument)
Click to expand...
Click to collapse
Your mbr doesn't seem to be back to stock. You can try getting into the OS and doing a privacy wipe, but if your mbr is still the voodoo mbr it won't work.
In that case you should basically try re-installing voodoo like new, then walk through the uninstall process again. You need to remove the /sdcard/Voodoo/disable_lagfix file in order to re-install voodoo.
If you get this error in stock recovery each time, the problem is still there.
namebrandon said:
Your mbr doesn't seem to be back to stock. You can try getting into the OS and doing a privacy wipe, but if your mbr is still the voodoo mbr it won't work.
In that case you should basically try re-installing voodoo like new, then walk through the uninstall process again. You need to remove the /sdcard/Voodoo/disable_lagfix file in order to re-install voodoo.
If you get this error in stock recovery each time, the problem is still there.
Click to expand...
Click to collapse
Well right now update.zip fails so we can't get back to clockwork to try to re-install voodoo
yeah i've gone back to stock numerous times i dont have voodoo onthe phoen anymore no way it could be wiped phone wiped cache wipe sd card but still no goo even put a new sd card in
Does anyone know if it is safe to try to restore thru odin with phone boot loader update checked. Just was wondering if that might solve it.
nemesis2all said:
Well right now update.zip fails so we can't get back to clockwork to try to re-install voodoo
Click to expand...
Click to collapse
Have you tried going into cwm recovery manually?
meaning how? i've done cm2recovery.tar through odin but still no luck

[Q] [SOLVED] I can't leave recovery ... ever

Soooooooo ... here's what happened.
I was trying to condense my internal and external sdcards from my computer. Once i backed everything up, I formatted one of the drives through windows. Problem is, it COMPLETELY formatted it, including the partition for app data. The phone booted, but with 0Mb for apps, and would freeze up and give me the black screen with lit buttons.
Then I go into DL mode, flash the stock firmware and during the reboot, it gets stuck in recovery with this error:
-- Movi_check Start...!!
checksum confirmation need check_sum[1301305579]
MBR_ChkSum in header : 5.0
MBR checksum : E9A2186CA7912EE54F5EFCB478D44960
MBR Checksum Error
Movinand Checksum Confirmation Fail
lfs pass open fail
--movi_checking undone!...
update media. please wait
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA:
copy default media content failed
I can Get into clockwork, but it won't flash bionix1.7, I get a line 81 error. I can't mount the sd while in recovery any more. I can't get into DL mode again. whenever I try to reboot, it throws me into recovery with that error ... I'm completely lost right now and any help would be GREATLY appreciated.
dav3wash said:
Soooooooo ... here's what happened.
I was trying to condense my internal and external sdcards from my computer. Once i backed everything up, I formatted one of the drives through windows. Problem is, it COMPLETELY formatted it, including the partition for app data. The phone booted, but with 0Mb for apps, and would freeze up and give me the black screen with lit buttons.
Then I go into DL mode, flash the stock firmware and during the reboot, it gets stuck in recovery with this error:
-- Movi_check Start...!!
checksum confirmation need check_sum[1301305579]
MBR_ChkSum in header : 5.0
MBR checksum : E9A2186CA7912EE54F5EFCB478D44960
MBR Checksum Error
Movinand Checksum Confirmation Fail
lfs pass open fail
--movi_checking undone!...
update media. please wait
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA:
copy default media content failed
I can Get into clockwork, but it won't flash bionix1.7, I get a line 81 error. I can't mount the sd while in recovery any more. I can't get into DL mode again. whenever I try to reboot, it throws me into recovery with that error ... I'm completely lost right now and any help would be GREATLY appreciated.
Click to expand...
Click to collapse
try booting in dl mode from your pc. Install the android SDK and USB drivers for samsung. The SDK can be found by googling and search the forum for the USB drivers. They in the command line type "<PathToSDK>\tools\adb.exe reboot download. That should get you into download mode. Then flash the stock image and make sure the "Re-Partition" is checked.
I think this should work.
MonkySlap said:
try booting in dl mode from your pc. Install the android SDK and USB drivers for samsung. The SDK can be found by googling and search the forum for the USB drivers. They in the command line type "<PathToSDK>\tools\adb.exe reboot download. That should get you into download mode. Then flash the stock image and make sure the "Re-Partition" is checked.
I think this should work.
Click to expand...
Click to collapse
tried that, it didn't work either. It still takes me into recovery even though i put adb reboot download. I think I'm just going to have Asurion replace it again
Boot into Clockwork recovery and post the results of:
adb shell mount
silow said:
Boot into Clockwork recovery and post the results of:
adb shell mount
Click to expand...
Click to collapse
Once i go into clockwork, my computer no longer recognizes clockwork.
Idk if its the same thing, but here's what it says outside of clockwork
I would try and reformat your partitions through clockwork. I dont know if you might of reformated the partions NTFS or what.
MonkySlap said:
I would try and reformat your partitions through clockwork. I dont know if you might of reformated the partions NTFS or what.
Click to expand...
Click to collapse
Looks like this at least let me get into dl mode ... flashing stock now, we'll see what happens
Good to hear. I bet when you reformated in windows, it formated the internal sdcard as NTFS which Android cant read.
Just to put it out there if you press the menu button from recovery i believe its the same as DL mode .
got it!
First off, thanks for all the tips guys.
I had to flash Eugene's Froyo that doesnt brick with re-partition checked (no other rom would work) which brought me back, and then i downgraded from there.
Just in case anybody else gets that!
did it get rid of the mbr checksum error? I still have it but can flash whatever.

Doom brick?

Tried to go from CM7 #11 to Simply Honey 3.5 Revolution, but when that didn't work, I ended up Odin-flashing stock KB1... and now I get this when booting:
Android system recovery <3e>
System Recovery Utils
- for BML -
reboot system now
reinstall packages
delete all user data
delete cache\
format internal sd-card
update media, please wait
E:Can't mount dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
Click to expand...
Click to collapse
Got the same error message when attempting to format the internal sd-card, and more importantly, when putting the device into download mode, it's no longer detected by Odin...
EDIT: Fixed! At least in the sense that I was able to flash back to stock JFD, by choosing the 512 PIT instead of the 803 PIT, and by physically disconnecting/reconnecting the micro USB cable while Odin was open. Whew! A frightening lesson, but it's reinforced the importance of flashing back to stock before switching ROMs.
EDIT #2: On the other hand, when I root JFD, then install ROM Manager from the Market, then flash CWM 2.5.1.2, reboot into CWM recovery through ROM Manager (instead of 3-button), then try to flash a ROM, it seems to hang/freeze at "finding update package"... but rebooting into recovery by 3-button fixed this, thankfully.
glad you got it resolved, but next time, remember to review/look over standard procedures in the noob bible. Your problems were because of your actions....... operator error...........

[Q] HELP !!! Streak wont read SDCard to flash Update.pkg

hi
I ahve downloaded a pkg from dell and want to load the phone back but i am just getting errors
it says it cant mount the SDCard:Update.pkg
any ideas ??
This is the wrong section bro. Are you using the stock recovery?
Sent from my Dell Streak 7 using XDA Premium App
If you are trying to install from recovery rename the package to update.pkg. This will wipe all your apps and settings.
You must use stock recovery to install a .pkg file.
You may need to flash the proper recovery first.
See: Radimus’s Universal Guide to Flashing a ROM
Note: if you downloaded direct from Dell tapping on the download complete notice in the notification should start the update process.This will update without wiping your apsp and settings.
followed that guide and when it should be installing from SD i get the following
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(no such file or directory)
E:Can't mount SDCARD:update.pkg
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(no such file or directory)
E:Can't mount SDCARD:update.zip
sorted now, that guide sorted it, but had to change SD Card it was not working in the streak but was ok in the PC.......
anyways... I have never been so happy to see the O2 screen in my life
kelvinbrotherston said:
sorted now, that guide sorted it, but had to change SD Card it was not working in the streak but was ok in the PC.......
anyways... I have never been so happy to see the O2 screen in my life
Click to expand...
Click to collapse
I had same problem with SD today. Windows PC doesn't format card correctly for phone. Remove the external SD card you are currently using. REPLACE WITH CARD THAT WONT WORK. Reboot phone until it will reboot completely. Go to SETTINGS==>SD CARD & PHONE STORAGE==>UNMOUNT SD CARD==>FORMAT SD CARD. Card will now work in Streak. MAKE CERTAIN YOU DON'T FORMAT THE CARD THAT IS WORKING!!!!!
I've had this same problem, I can't flash anything. I've tried to flash 1.9.1, because I only have 1.9, and I get the same error. I -have- tried changing the name. Doesn't work. Can anyone give me a complete step by step to fix this?
i got it solved
so... this is how it's happened to me.
when i reboot the streak after i fastboot flashed the streak with streakmod recovery, the recovery will be back to stock recovery. so... i have to delete install-recovery.sh from /system/etc to prevent the streak reinstalling the stock recovery, before it succeed to boot android OS.
so i flashed to streakmod recovery and reboot it to go into recovery mode and plan to choose "update from sdcard".
and when i tried to choose the update.zip from sdcard, there's error message:
"can't mount /sdcard"
so, i think that maybe because my sdcard was plugged into PC and got 'half-mounted', so recovery can't mount it.
so i powered it off, eject and re-insert the external sdcard again, powered it on and go into recovery mode, choose the superuser.zip to root my streak... AND... TADAAAA.... i'm all rooted

post root Bricked? Nook HD+ by Trimmer, weird boot behaviour, boots only with SD in

Hi
I'll try to make it brief. Some time ago, my stock Nook slowed down like a mule so I decided to root it, then applied Trimmer to enable trim. Beforehand I'd checked the eMMc with a Brickbug app and it popped up with "sane chip", as I'd read some Nooks had a faulty Samsung eMMc.
It went into a bootloop, and only started showing shredded Nook letters on an abstract background during boot. Then I tried various bootable SD cards to try to flash various stuff, as per available XDA threads, especially - leapinlar's, verygreen's and amaces'. First it would not complete the flashing of a ROM, just froze towards the end, then eventually wouldn't boot up at all.
Here's the weird part. Without an SD card, it doesn't boot up at all.
When I make a bootable SD, it only boots to TWRP 2.6.0.0 (some other versions [amaces] it won't boot to), but doesn't see any zips on the card and won't let me flash anything, even though it previously did, but wouldn't complete the flash.
Whatever else I burn on the card, it either doesn't boot up at all, or boots to whatever it is you can see on the attached printscreens, and won't mount anything. So if I'm guessing right, the eMMc is not borked, as it seems the device boots to some remnants of something that's there, and not on the SD.
Is there a way of fixing that mess? I'd appreciate any ideas.
Best
W.
You can try to flash this flashable_fix_bootdata-ovation.zip which typically should cure corrupted or missing bootdata issues.
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it won't see the zips on it. So how can I flash the fix bootdata zip?
wojtasys said:
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it w on't see the zips on it. So how can I flash the fix bootdata zip?
Click to expand...
Click to collapse
Have you tried the verygreen's old SD-based CWM recovery?
If you mean the one from that thread:
https://forum.xda-developers.com/showthread.php?t=2600572
I have. The download links for the initial card image don't work. I looked elsewhere - nowhere to be found.
Sorry about the trouble, guys, forgot to update the dns when the server moved. I just updated it, but it'll take some time to propagate. The actual new ip address is now 178.34.187.142 - you can place it into your hosts file if you don't want to wait.
Nook HD+ Bootloop error
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
wojtasys said:
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
Click to expand...
Click to collapse
Assuming that your flashing of stock recovery was successful (recovery's reports of successful completion can sometimes be erroneous) and also your factory backup partition is still intact, you can try to initiate a factory reset by using the "8 failed boots" method: with the Nook in the power-off state, power it on, then as soon as the boot screen appears hold down the power button until it powers off, do this 8 times, and the Nook should go into stock recovery to revert to factory-fresh state.
Flashing your flashable_restore_stock-recovery-ovation zip ends with the screen I'm attaching.
Then I tried "8 failed boots" but it only boots to CWM SD, without the card - it doesn't power up at all.
Eventually, nothing changes.
Tried putting the stock ROM on the card and flashing that, but the partition size is too small, even though its a 16GB card.
wojtasys said:
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
Click to expand...
Click to collapse
If the issue is about the two files, you could mount /bootdata and copy them manually (ADB shell should be functional with any of these recoveries). You'd extract BCB and BootCnt from ZIP, and copy them onto SD card, then do something like:
Code:
mkdir -p /bootdata
mount -t vfat /dev/block/mmcblk0p6 /bootdata
cd /external_sd or /sdcard or /emmc (wherever SD card root is mounted)
cp BCB BootCnt /bootdata/
Or, you could edit the updater-script inside ZIP to remove the device assert line like in the attachment here. By the way, are the updated images here also failing?
Flashing your flashable_fix_bootdata-ovation-no-assert.zip shows "install from sd card complete" but the device still won't power up without the card.
Trying to mount bootdata results in "error mounting bootdata".
There's no adb command line in that sd recovery, just adb sideload. TWRP 2.6 had it but it didn't access the files on the sd.
Then, I'm not sure I'll know how to edit the updater-script inside ZIP to remove the device assert line.
Chances are your EMMC is hosed, in which case you can try running CM entirely off SD card using the succulent special build available at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.

Categories

Resources