Been semi bricked for hours... I messed up the emmc partitions using adb gparted dev/block/mmcbkl0 and now nook won't boot.. not even off SD card
the only thing i can get to boot off sd card image is rootpack which boots me into recovery.. i tried everything but no matter what I do in recovery i always get errors regarding the mounting of my cache and data, which obviously is because i deleted the partitions...
when i try to edit the partition table from adb parted denies me permission
please help... i'm very new to the nook and everything I just said I learned in the past 4 hours that i have been reading through forums trying to fix it..
thank you
In this very forum..
http://forum.xda-developers.com/showthread.php?t=958748
Besides, what makes you think you deleted the partitions? Did you?
on adb parted i went through every single one of the partitions and deleted them... only left one intact.. so i'm pretty sure i deleted them..
I have already tried flashing this and it flashed just fine however when I go back into the recovery menu I get the same error
E:\ something something can't mount data/recoverylog.log
E:\ something something can't mount cache/recoverylog.log
and four others just like it..
if anyone is willingto help the errors i get in clockwork recovery are
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log
ralphsancho said:
on adb parted i went through every single one of the partitions and deleted them... only left one intact.. so i'm pretty sure i deleted them..
I have already tried flashing this and it flashed just fine however when I go back into the recovery menu I get the same error
E:\ something something can't mount data/recoverylog.log
E:\ something something can't mount cache/recoverylog.log
and four others just like it..
Click to expand...
Click to collapse
And why in gods name did you do that?
Anyway, get the repartition/fix tool that's in these forums.. I think in Development, might be in General. It just works.
Related
So today i rooted my phone installed JF1.41, i partitioned my sd card IN MY G1, since i have a mac and for some reason it wont partition the card right. Then i did the apps2sd deal... Then i wanted to use a theme, well that screwed everything, and it wouldnt get back to normal or even start again. So completely formatted my card, which now has NO PARTITIONS(i guess just 1), and i think the phone is trying to read files on a partition that dont exist now, and NOTHING is working. Anyone on here that can help? I am rather smart with this stuff, but really am going to need someone to help me. I need my phone tomorrow.
Thanks.
How did you reformat your sdcard? Did you check in parted to see that you in fact only had 1 partition again? I suggest you flash a new updated ROM like Cyanogen 4.2.5. That has apps2sd script built into the rom. It will do it automatically so you don't have to mess with all that.
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
illthinking said:
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
Click to expand...
Click to collapse
you're going to need a second partition for apps2sd to work. I suggest you do that first before you flash a rom, or else you will just have to end up reflashing.
Ok Downloaded Cyanogen4.2.5
This is the problem i keep having when i try to apply the update it say
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
So i think it has to do with the fact it wants to read /dev/block...etc from the partition of the sdcard that is now non existent
problem is i have a mac and cant properly fromat the 2nd partition (ext2)
unless you know of a way
the way i first did it was using some code i got off of here to have the phone do it itself... now that i cant start the phone i cant do the partition
what recovery do you have? I suggest you put this one on your phone.
http://forum.xda-developers.com/showthread.php?t=566669
It partitions your sd card for you.
Also for Cyanogen, you need to flash the htc OTA update one, then flash his update for those to work.
ok...
so i found some plugins for the new Snow Leopard OS for mac called MacFuse 2.0 along with its counterpart fuse-ext2 and i partitioned my card
you might want to upgrade to ext3. it's faster than ext2 and runs smoother
just tried to flash the recovery found here
http://forum.xda-developers.com/showthread.php?t=566669
with no avail and tried to start the phone(power+camera) and said no image
heres what it said for the recovery
/ # mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument
mount: mounting /system/modules/modules.cramfs on / system/modules failed: No such file or directory
mount: mounting /system/xbin.cramfs on /system/xbin failed: No such file or directory
I mean, what i want to know is how to build the file format back on my sd card so itll work, or build it so it will look on my actual phone... People put up the code to have it switch where it reads things from, there MUST be a way to switch it back manually as well
Use fastboot and write the recovery image
here's a link to fastboot
http://developer.htc.com/adp.html
then when thats running plug in your G1 and turn on holding Power and camera when the screen turns on you might have to press back to enable FB but once its enabled type in terminal
Code:
cd *where ever your recovery image is*
fastboot flash recovery *recoveryname*.img
reboot
can someone hook up a quick step by step on how to hook my phone up fastbooted? I have a mac and i can get the phone to say fastboot, but im lost after that... If you want to reroute me to a different thread, please verify that it REALLY has the info before posting it.
i have been trying to find the name of the device and im getting
/dev/tty.Bluetooth-Modem as the device name, but a Permission Denied thing... now i cant just go click something in the phone menus, since i cant get the phone to start, so is there a way to get permissions through the Terminal application?
that error you get when you type mount -a is normal continue as instructed:
flash_image recovery /(whatever your recovery image is called)
if you have adb you could try parted /dev/block/mmcblk0 and type print to see your parttitions.
so i can get it to say it flashes the recovery, but still not starting
so when i try to do any updates it says SDCARD wont mount
any input?
Looks like im going to go for a broken record, until SOMEONE can help me figure my phone out... I need to get it running, and i know someone can figure it out
I used this hardware mod on all 50 of the tablets with great success. Just be careful to not remove any of the other little chips, I used heat to loosen the glue.
http://forum.xda-developers.com/showthread.php?t=1877585
Good luck
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Reference Material:
Fix for the P1000 - This is exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1711150
Fix for the Atrix 4G - Again, exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1766939
Another Example
http://forum.xda-developers.com/showthread.php?t=1463756&highlight=ics
Re-partition steps:
http://forum.xda-developers.com/showthread.php?t=845708 <- this did not work
Heimdall Suite re-partition with known good pit file <- This did not work
I'm on the exact same place, attempting the exact same, currently I was trying to edit vold.fstab as well as init.rc but it seems you have a better grasp of this.
I use a Sprint sph-p100, a CDMA version just like yours and as far as I know fully compatible with anything (save modem but I only use wi-fi).
I've tried your first link with a GB rom and failed (didn't pass first Samsung logo), but I will keep trying and post back anything I achieve.
If you indeed make a kernel or image that makes them boot please share it with us and I will GLADLY test it out.
I'm also aware that an easy solution is to open up the hardware and remove the internal SD Card (the kernel will assume the external is mmcblk0 instantly) but I dislike doing butchery and maybe breaking my device.
Chris... much progress has been made on this... first off. I am dumping the Gingerbread Verizon images for the CyanogenMod 9 Rc1 for P1c. I am currently following the kernel rebuild instructions from the device developer "cdesai" is working on. Those instructions are here:
http://forum.xda-developers.com/showpost.php?p=20162940&postcount=3
with repo setup here:
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
With the instructions on how to build just the kernel I will modify the initramfs.list among other files to get the required results. What I will need to help you is do the exact same thing, just with the initramfs.list for your P100 device ??
Are you willing to use CyanogenMod 9? I have pretty much abandon Gingerbread unless someone can hook me up with a known working P1c Gingerbread git.
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
ChrisCTX said:
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
Click to expand...
Click to collapse
Mine is detected too. But fails when you try and fdisk is. I have several devices with the same results. If you want try to fdisk /dev/block/mmcblk0
Tell me if that eventually shows up as a 32mb disk with an empty partition
The correct commands are
adb shell
su
fdisk /dev/block/mmcblk0
p
q
Don't have a rooted rom on it now (can't really install anything besides flashing), but I tried it minus "su" and it didn't do anything at all.
Update the status. I have made the changes to support booting from the SDCard. For the first time I can mount the /data directory via the recovery. There is an install sequence that I haven't yet mastered. Will be in touch
Sounds great Jim, thanks for all the effort so far
I am waiting for the release of this. My tab internal SD crapped out also.
please help
im on the same boat if in need to take of the internal storage let me know i will do it just tell me some directions
Same issue
JimRich said:
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Hey guys I am having the same issues (as far as i can tell) with my Verizon Samsung Galaxy Tab SCH-i800. so the first issue is i tried to install a stock rom to fix a corrupted cache partition. now it tries to boot US Cellular. As of this moment the error i get when i put the device in recovery mode:
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
# MANUAL MODE #
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
I am wondering if i can just create a new partition on a new SD card? i bought this device on ebay a couple weeks ago and i don't want to continue attempting sketchy leads for fear of hard bricking it. All help is greatly appreciated. I really don't want to give up on this thing because i feel like the soultion is out there... I am very good with performing commands via command prompt if that is nessasary, also i have access to an Ubuntu 12.4 computer if that would make things easier? Please help?
***Also as far as i know this is equipped with android Froyo and the issue developed after the previous user attempted to update. Please email me a reply or reply to my post.
Thanks,
-Andy
I switched to a hardware modification. This worked great!
http://forum.xda-developers.com/showthread.php?t=1877585
I am trying to restore a NC that won't boot. After making a new bootable CMW sd card, the nook will boot but has the error message
E: Can't mount /cache/recovery/command, etc.
I have tried various boot images tonight - Leapinlar's, eyeballer's, and another one. I have tried several SD cards. I still get the same error message. I have fixed the 'no boot' problem on a couple of NC's by fixing the partitions, but have not seen this error myself before.
I have searched and found this error mentioned a lot here in the forums, but have yet to find a definitive answer or solution. Is it hardware related, or SD related?
Has anyone had this error and found a solution that worked?
Thanks for any help or suggestions.
k8108 said:
I am trying to restore a NC that won't boot. After making a new bootable CMW sd card, the nook will boot but has the error message
E: Can't mount /cache/recovery/command, etc.
I have tried various boot images tonight - Leapinlar's, eyeballer's, and another one. I have tried several SD cards. I still get the same error message. I have fixed the 'no boot' problem on a couple of NC's by fixing the partitions, but have not seen this error myself before.
I have searched and found this error mentioned a lot here in the forums, but have yet to find a definitive answer or solution. Is it hardware related, or SD related?
Has anyone had this error and found a solution that worked?
Thanks for any help or suggestions.
Click to expand...
Click to collapse
You messed up your partition table. You'll need to look at this tutorial by leapinlar http://forum.xda-developers.com/showthread.php?t=1759558
sagirfahmid3 said:
You messed up your partition table. You'll need to look at this tutorial by leapinlar http://forum.xda-developers.com/showthread.php?t=1759558
Click to expand...
Click to collapse
I realize that my partitions do need to be fixed, but I can't get past the error message to run the zip files.
k8108 said:
I realize that my partitions do need to be fixed, but I can't get past the error message to run the zip files.
Click to expand...
Click to collapse
Hmm...Can you at least get ADB working on your pc? It should work even if your partitions are messed up. It sure did for my Nook Tablet. I totally bricked it and ended up repairing it from adb shell alone (had to manually remake partitions).
Type in "adb shell" in the command line. Should list your serial number. If it shows "00000000" then your ROM partition is prob. messed up.
Type in "fdisk -l /dev/block/mmcblk0" (press q to quit after observing the partitions listed). Type "blkid" If it lists your factory partition (for me, it's mmcblk0p3) and it is still intact, you can get your ROM partition's info back and that will allow you to boot successfully.
That error message is an indication that your /cache partition is not functional (probably along with your other partitions). Are you saying this error prevents you from flashing anything?
If so, your solution is to get ADB working and using fdisk to manually rebuild the partitions.
You might also try putting a ROM on SD and see if that boots. Then you can use Terminal Emulator to run fdisk.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
That error message is an indication that your /cache partition is not functional (probably along with your other partitions). Are you saying this error prevents you from flashing anything?
If so, your solution is to get ADB working and using fdisk to manually rebuild the partitions.
You might also try putting a ROM on SD and see if that boots. Then you can use Terminal Emulator to run fdisk.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Correct, I can not flash anything from recovery.
I did make a boot-able SD using your image (leapinlar) and the nook wouldn't boot. (It would have been great if it had!) So I'm going to keep working to see if I can understand and work ADB.
sagirfahmid3 said:
Hmm...Can you at least get ADB working on your pc? It should work even if your partitions are messed up. It sure did for my Nook Tablet. I totally bricked it and ended up repairing it from adb shell alone (had to manually remake partitions).
Type in "adb shell" in the command line. Should list your serial number. If it shows "00000000" then your ROM partition is prob. messed up.
Type in "fdisk -l /dev/block/mmcblk0" (press q to quit after observing the partitions listed). Type "blkid" If it lists your factory partition (for me, it's mmcblk0p3) and it is still intact, you can get your ROM partition's info back and that will allow you to boot successfully.
Click to expand...
Click to collapse
Yes, I got list
It says
Device Boot start end blocks ID system
Dev/block/mmcblk0p1 * 1 3865 31165952 c win95 fat32 <lba>
then I used blkid
it says
/dev/block/vold/179:1: UUID="1cd2-ff94" type="vfat"
/dev/block/mmcblk0p1: UUID="1cd2-ff94" type="vfat"
please help me now.. further..
I want to start my device.. its in cwm 6.0.4.3 recvovery mode.
and e can't moount errorss..
please help me further in adb how to delete these stupid block and get my note 2 n7100 back in life
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...
My phone was slowly corrupting some files inside the external sd card, but I thought it might have been because I had named a file with a $ sign and it had some problems when I plugged the usb.
After I had taken the file out and deleted the corrupted files (Some of my game saves died too :crying, I thought it was going to be okay, but the corruption did go on after some time.
One day, when I was using the phone, suddenly, I got a white line accross the screen and the phone rebooted, then every time it turned on, it worked for 1~3 seconds then, again, white line and reboot.
Tried to fix it in various ways, turning off wi-fi, changing the brightness and things like that in the moment before it rebooted, but I couldn't make it work.
After some tries/time, it gave me an error saying it needed to be wiped and reseted, but I really need some files inside of it, so I didn't wipe it, and now it just stops at the samsung logo.
I can get it into recovery mode or that "custom rom" screen, by using the volume buttons when booting up, and I could even get it to show in adb when in recovery mode, but I can't mount the sd card with it (It always tells me I can't do it, something about privileges, I think).
I just wanted to get some files from the internal memory, after that, I think I'll be flashing it with CyanogenMod so it'll be a Android 4.4
But, for now, what can I do to recover those files?
Thanks in advance
Edit: Recovery menu says:
--init-recovery...
E: failed to mount /data (invalid argument)
can't mount /data (invalid argument)
Then it tries to apply "multi-csc" and after it "successfully applies" it, then it shows the "failed to moun /data" error again
Well the easiest way would be to flash TWRP recovery and use the file manager to copy the files that you need to your mem card... if u couldn't access the internal memory just mount it manually either from the option "mount sdcard" or use the a shell command.. I believe there is a terminal emulator there