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.
Hi all, this is my first time posting here, but I have been looking around for the past week at guides and How-to's.
Anyway to my point, my Nook Tablet is bricked and I can't find anyway to bring it back. As of right now, If I remove the SD card so It doesn't boot to CWM, or CM7 it just goes to the grey "N" logo screen with the "Adobe reader" text at the bottom, then immediately shuts off. If I plug in the USB it just goes to the same screen and keeps rebooting over and over. I fear I may of formatted something without really thinking about what I was doing (yes that was stupid of me) and to top that off, in my haste to root I forgot to make a backup (I know really stupid) I've tried many of the different guides and I can't figure out what to do now. So far these are the things I've done or have with my Nook Tablet [16GB]
-I have a CWM SD card
-I can boot from SD to CM7
-I've used ADB and used parted which showed my table, but no fix option. (I compared the table, it matched another user's table that was "fine"
-In ADB I managed to follow Lavero.burgos' guide and redo my partitions.
-I've tried various recovery roms, and I've also tried Adam's Ubuntu Recovery, but I get stuck at "writing zeroes to MLO"
-I also have the "E:\ can't mount" error's in CWM
-I've tried Ray Waldo's method in his video that involves the green check mark, but the NT will show a red X and will power off, powering it back on just leads to the grey "N" logo boot.
-Also my device ID in ADB shows up as a string of zero's "000000000000000" I guess that's the cherry on top of this sundae. (Is the serial number the same as the one on the box and SD flap? If so I guess I still have the number)
I've tried more things, I'm sure they'll come back to me the more I think about it. So what it seems is that I can't boot from internal anymore, that's just my guess. sorry for having this wall of text, I'm just trying to provide as much info as possible. I would just return it assuming that they wouldn't find rooted files or anything of the like since it won't even boot properly, but this Nook was brought into my store and traded in second hand. (Still have the box though)
Thanks for your time!
Hey, just some quick info. I bricked my nook the first week I got it. I users the sd restore method with the green check mark. It seemingly worked however when it booted it would go the screen with the yellow arrow. After getting frustrated from numerous boot loops, I left it plugged in overnight and the next day it was working fine. Anyways that method MAY be doing the same for you? Good luck and don't get too frustrated!
Sent from my SGH-T679 using xda app-developers app
Do you mean just leave it plugged into the wall charger or computer? Also do you mean you just left in plugged in so it would continuously go to the grey N logo screen?
Thanks for the reply by the way!
*edit*
On my original post, I clarified that Ray Waldo's green check mark method didn't produce a green check, just a red X
I left it plugged in charging overnight to the wall. But, I also got the green check mark before having done that. It would boot to the n screen then go to the yellow arrow screen immediately after. I don't have any other suggestions for you, sorry. I consider myself a noob when it comes to the nook. It seems like more of a pain in the ass than most other Android devices.
Sent from my SGH-T679 using xda app-developers app
can you list the "can't mount" errors?
ShinnAsuka said:
can you list the "can't mount" errors?
Click to expand...
Click to collapse
I believe he is referring to these errors (same as mine):
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
and these as well:
Formatting /data....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Formatting /cache....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/cache
Formatting /sd-ext....
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/ .android_secure...
Data wipe complete.
ShinnAsuka said:
can you list the "can't mount" errors?
Click to expand...
Click to collapse
Thanks for taking the time to post.
Anyway, the mount errors I get are the same as DanimalManimal.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
and these as well:
Formatting /data....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Formatting /cache....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/cache
Formatting /sd-ext....
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/ .android_secure...
Data wipe complete.
Depardieu said:
-Also my device ID in ADB shows up as a string of zero's "000000000000000" I guess that's the cherry on top of this sundae. (Is the serial number the same as the one on the box and SD flap? If so I guess I still have the number)
Click to expand...
Click to collapse
I get this too. I'd be interested in knowing how to fix the issue.
Depardieu said:
Thanks for taking the time to post.
Anyway, the mount errors I get are the same as DanimalManimal.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
**this first set of errors usually occurs when you accidentally format the usrdata partition which in stock partitions is the 1gb of user space on the 16gb nook. i had that happen and just followed the following thread to get it fixed: http://forum.xda-developers.com/showthread.php?t=1513583 **
and these as well:
Formatting /data....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Formatting /cache....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/cache
Formatting /sd-ext....
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/ .android_secure...
Data wipe complete.
Click to expand...
Click to collapse
this second set of mounting errors looks like your partitions are screwed up. but you say you fixed your partitions using lavero burgo's thread? is there any way you can confirm that your partitions are formatted the right way?
liquidzoo said:
I get this too. I'd be interested in knowing how to fix the issue.
Click to expand...
Click to collapse
the serial number with all zeroes is normal. its just adb not getting the correct information from the nook tablet. if you go into the rom folder and locate something that deals with a serial number and open it to view it, you will see that it isn't all zeroes...
not sure why adb gets serial information as all zeroes but w/e... as long as adb works thats all that matters.
Depardieu said:
Hi all, this is my first time posting here, but I have been looking around for the past week at guides and How-to's.
Anyway to my point, my Nook Tablet is bricked and I can't find anyway to bring it back. As of right now, If I remove the SD card so It doesn't boot to CWM, or CM7 it just goes to the grey "N" logo screen with the "Adobe reader" text at the bottom, then immediately shuts off. If I plug in the USB it just goes to the same screen and keeps rebooting over and over. I fear I may of formatted something without really thinking about what I was doing (yes that was stupid of me) and to top that off, in my haste to root I forgot to make a backup (I know really stupid) I've tried many of the different guides and I can't figure out what to do now. So far these are the things I've done or have with my Nook Tablet [16GB]
-I have a CWM SD card
-I can boot from SD to CM7
-I've used ADB and used parted which showed my table, but no fix option. (I compared the table, it matched another user's table that was "fine"
-In ADB I managed to follow Lavero.burgos' guide and redo my partitions.
-I've tried various recovery roms, and I've also tried Adam's Ubuntu Recovery, but I get stuck at "writing zeroes to MLO"
-I also have the "E:\ can't mount" error's in CWM
-I've tried Ray Waldo's method in his video that involves the green check mark, but the NT will show a red X and will power off, powering it back on just leads to the grey "N" logo boot.
-Also my device ID in ADB shows up as a string of zero's "000000000000000" I guess that's the cherry on top of this sundae. (Is the serial number the same as the one on the box and SD flap? If so I guess I still have the number)
I've tried more things, I'm sure they'll come back to me the more I think about it. So what it seems is that I can't boot from internal anymore, that's just my guess. sorry for having this wall of text, I'm just trying to provide as much info as possible. I would just return it assuming that they wouldn't find rooted files or anything of the like since it won't even boot properly, but this Nook was brought into my store and traded in second hand. (Still have the box though)
Thanks for your time!
Click to expand...
Click to collapse
Here is a link to a thread dedicated to your partition problems. http://forum.xda-developers.com/showthread.php?t=1513583
Good Luck!
ShinnAsuka said:
this second set of mounting errors looks like your partitions are screwed up. but you say you fixed your partitions using lavero burgo's thread? is there any way you can confirm that your partitions are formatted the right way?
Click to expand...
Click to collapse
Well I guess all I can really confirm was when I fixed the partitions, and ran a parted command, my Partition Table came up, and It had no mention of errors or told me to "type Y to fix corrupted partitions". I cross checked the partition sizes and they looked very similar to this:
Code:
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.9GB 12.9GB ext4 userdata
Which is, from what I've read, correct or what it should look like.
Perhaps I overlooked something within the repartition process, but from what it seems if I did do the repartition correct, I'd be good to go and get my nook back to working order? If so then obviously I must of missed something which I suppose can narrow it down considerably.
Thanks for your time by the way, it means a lot to actually talk to someone about the issue after being a bit frustrated.
tobdaryl said:
Here is a link to a thread dedicated to your partition problems. http://forum.xda-developers.com/showthread.php?t=1513583
Good Luck!
Click to expand...
Click to collapse
Ok I want to say I'm really close to fixing this now, I'm currently in ubuntu, since that was the only way I could ADB, I have the repartition files, I'm pretty sure I have it all mounted properly, and I can see my device ID come up, when i type in
Code:
parted /dev/block/mmcblk0 print
Then it tells me
Code:
WARNING: You are not superuser. Watch out for permissions.
Error: Could not stat device /dev/block/mmcblk0 - No Such file or directory
Which immediately leads me to believe I must be missing something important, or perhaps I haven't mounted everything correctly? Should my nook tablet be in CWM if that really matters?
*Edit*
To clarify to my previous post about my Partition Table, when I run the parted command, the file size match up, and it doesn't give an error saying its corrupt, but under the File system column, there is none, its just blank if that matters.
liquidzoo said:
I get this too. I'd be interested in knowing how to fix the issue.
Click to expand...
Click to collapse
My device shows up in ADB with my serial number, however it gets stuck on "first need to make sure you didn't lie about it showing up, I also need to check for root incase you want to run any updates!" I was using Nook&Zergy for ADB.
Hopefull the fact that my serial number still shows up in ADB is a good thing? Any help?
Well, I figure I'd just go for broke with this, and I started this guide for Completely Dead Nook's and fixing the Partition Table. Everything worked great up to the part where you recreate your partition, when I input that command, I get a "Permission Denied" error. I went back to the start but this time enabled "su" and I still get a Permission Denied.
Essentially I think I could get this working, except I'm just stonewalled at this one part. (Although I guess I could dig in for the long haul and manually recreate using the parted way...right?)
*edit*
OK I finally believe I've made some headway. While I got the "Permission Denied" error, I figured I could just go a manually recreate all my partitions, which I went and did going off the guide. Now when I boot back into CWM I no longer have the string of E:Mount Errors !
I'll report back on progress, I assume I'm heading in the right direction if the errors are gone no?
*Update*
Well the errors are gone in CWM, but I still am stuck with a bootloop/constant restarting at the grey/silver "n" logo. I tried Ray Waldo's unbrick, which has the whole green check mark stuff, but I still get a red x. Perhaps I missed something, any clues?
Another update, Adam's Ubuntu Recovery is no longer stuck at "writing zeroes to MLO". This seems to be a very good sign
Another update, It's working! I used Ray Waldo's unbrick method, got the green check, but now I get an error when it registers the device, which I know is tied to partition 5 which i recreated, I thought I had made a proper backup, but I guess I made a backup of when it was already formatted, so is it possible to get my Serial Number, MAC address what-have-you back, if not what are the options I have?
Depardieu said:
Well, I figure I'd just go for broke with this, and I started this guide for Completely Dead Nook's and fixing the Partition Table. Everything worked great up to the part where you recreate your partition, when I input that command, I get a "Permission Denied" error. I went back to the start but this time enabled "su" and I still get a Permission Denied.
Essentially I think I could get this working, except I'm just stonewalled at this one part. (Although I guess I could dig in for the long haul and manually recreate using the parted way...right?)
*edit*
OK I finally believe I've made some headway. While I got the "Permission Denied" error, I figured I could just go a manually recreate all my partitions, which I went and did going off the guide. Now when I boot back into CWM I no longer have the string of E:Mount Errors !
I'll report back on progress, I assume I'm heading in the right direction if the errors are gone no?
*Update*
Well the errors are gone in CWM, but I still am stuck with a bootloop/constant restarting at the grey/silver "n" logo. I tried Ray Waldo's unbrick, which has the whole green check mark stuff, but I still get a red x. Perhaps I missed something, any clues?
Another update, Adam's Ubuntu Recovery is no longer stuck at "writing zeroes to MLO". This seems to be a very good sign
Another update, It's working! I used Ray Waldo's unbrick method, got the green check, but now I get an error when it registers the device, which I know is tied to partition 5 which i recreated, I thought I had made a proper backup, but I guess I made a backup of when it was already formatted, so is it possible to get my Serial Number, MAC address what-have-you back, if not what are the options I have?
Click to expand...
Click to collapse
well since you redid your partitions, most likely the rom partition is missing files. that partition has all that info: serial number mac address,etc...
you can get the serial number easily if you registered your nook with b&n. just go to their website and log in to your b&n account and under my nook you should see it.
if you didn't register your nook, then that might be a bit more difficult. there is a thread in the dev section i think on getting back your original serial number.
also you can bypass registration if you want to get your nook back in working order with a custom rom and the like. just do a quick search on youtube and there will be video about it by albertcwertz
ShinnAsuka said:
well since you redid your partitions, most likely the rom partition is missing files. that partition has all that info: serial number mac address,etc...
you can get the serial number easily if you registered your nook with b&n. just go to their website and log in to your b&n account and under my nook you should see it.
Click to expand...
Click to collapse
Alright, I can confirm I have the serial, I just don't know how to put it back into the device, so the registration page picks it up. Any advice?
Thanks for the reply by the way!
Depardieu said:
Alright, I can confirm I have the serial, I just don't know how to put it back into the device, so the registration page picks it up. Any advice?
Thanks for the reply by the way!
Click to expand...
Click to collapse
sorry i am drawing a blank there. i restored my nook tablet using adam's total wipe and i had the problem your having now. not being able to register. i decided to just screw it since i won't use b&n software anyways. i bypassed regsitration and rooted again and then installed custom rom and all is fine lol.
even now when i use adb to get serial info it comes up as all zeroes, but when i go into my rom partition and open the serial number file, my serial number is in there. so i don't really know why registration doesn't pick up the serial number.
maybe b&n has a specific location for the registration process to find out where to look for the serial number info.
all i know is that the rom partition contains information pertaining to the device itself (serial num, mac address, etc).
hopefully someone else will be able to answer your question in more detail.
Well, I think I can just say case closed for now, I guess I didn't want to use stock B&N (Why else would I be here in the first place) I have found a rom I'm starting to really like. Thanks for your help though it is greatly appreciated!
Alrigh Nook gurus, I desperately need your help...please note that I'm only a few degrees above a noob:
*
NT 8GB, formerly running CM7 Beta.
*
I've accidently formatted my emmc and it's causing all kinds of mounting issues, mostly when locating or mounting the cache. Whenever I try to install anything (e.g. backup, new ROM, stock recovery, stock repart) the error "can't mount /cache" comes up and prevents me from doing most everything. When I power the unit on the 'n' splash screen appears for about 3 seconds, then the cyanoboot universal loader comes up states "loading emmc recovery" and goes right into TWRP. Although it states "hold 'n' for menu" it will continue to boot TWRP. Therefore I do not have the option of accessing fastboot, and even if I did it would likely result in the usual "can't mount /cache" error that I get when trying to flash anything. Here's what I've tried and a summary of the result:
*
I've tried the "repart.img" stock recovery method. It will load the downward arrow and say "updating", then it states that it will reboot and reminds me to remove my sd card. It does not reboot automatically, and when I manually power on it goes right back into TWRP.
*
I've tried the Ubuntu boot method, but after I downloaded the 1GB file, unzipped it, added .img to the file, flashed to SD, inserted into NT, power on...then goes right back into TWRP.
*
Everything else involving flashing recoveries (cwm, twrp, stock) I've tried, always resulting in cache mount errors and no change boot up. I am able to boot CM7 Alpha Final via SD card, but only when I insert the card and power the NT up via PC-USB connection. Also, I can boot into CWM recovery via SD card when powering via PC-USB connection. When I power up normally (with the power button) its as though the tablet disregards what is in the SD slot and goes right into the emmc recovery. If anybody has any insight as to what might fix this, please let me know.
Sent from my VS920 4G using xda app-developers app
spacetwin4 said:
Alrigh Nook gurus, I desperately need your help...please note that I'm only a few degrees above a noob:
*
NT 8GB, formerly running CM7 Beta.
*
I've accidently formatted my emmc and it's causing all kinds of mounting issues, mostly when locating or mounting the cache. Whenever I try to install anything (e.g. backup, new ROM, stock recovery, stock repart) the error "can't mount /cache" comes up and prevents me from doing most everything. When I power the unit on the 'n' splash screen appears for about 3 seconds, then the cyanoboot universal loader comes up states "loading emmc recovery" and goes right into TWRP. Although it states "hold 'n' for menu" it will continue to boot TWRP. Therefore I do not have the option of accessing fastboot, and even if I did it would likely result in the usual "can't mount /cache" error that I get when trying to flash anything. Here's what I've tried and a summary of the result:
*
I've tried the "repart.img" stock recovery method. It will load the downward arrow and say "updating", then it states that it will reboot and reminds me to remove my sd card. It does not reboot automatically, and when I manually power on it goes right back into TWRP.
*
I've tried the Ubuntu boot method, but after I downloaded the 1GB file, unzipped it, added .img to the file, flashed to SD, inserted into NT, power on...then goes right back into TWRP.
*
Everything else involving flashing recoveries (cwm, twrp, stock) I've tried, always resulting in cache mount errors and no change boot up. I am able to boot CM7 Alpha Final via SD card, but only when I insert the card and power the NT up via PC-USB connection. Also, I can boot into CWM recovery via SD card when powering via PC-USB connection. When I power up normally (with the power button) its as though the tablet disregards what is in the SD slot and goes right into the emmc recovery. If anybody has any insight as to what might fix this, please let me know.
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
Your tablet is basically in recovery mode. So you most likely have your partitions screwed up. Look at the thread in the development section about repartitioning your internal memory
Sent from my Barnes & Noble Nook Tablet using xda premium