So a friend of mine recently gave me this YP-G70, asking me to fix it for him. His cousin had promised to put KitKat on the device, no problem, as a replacement to the stock software. This is all I know.
When I received the device, it would not boot into any ROM, only into recovery (CWM was flashed). In CWM, I could see that /system, /data, /emmc, and /sdcard partitions were all unmounted. I tried to remount them in CWM, but alas, this did not survive a reboot, even just back into recovery.
I have tried to flash the stock firmware for this device (obtained from sammobile) through odin, which was a success... until it booted up, and found that again, the proper partitions were not mounted. From there, I went on to flash CM9, which ended me up to where I am now.
As it currently stands, /dbdata, /data, /emmc, and /sdcard are all unmounted and are stuck that way. Does anyone know how to solve this, cause I am lost right now.
nicholician said:
So a friend of mine recently gave me this YP-G70, asking me to fix it for him. His cousin had promised to put KitKat on the device, no problem, as a replacement to the stock software. This is all I know.
When I received the device, it would not boot into any ROM, only into recovery (CWM was flashed). In CWM, I could see that /system, /data, /emmc, and /sdcard partitions were all unmounted. I tried to remount them in CWM, but alas, this did not survive a reboot, even just back into recovery.
I have tried to flash the stock firmware for this device (obtained from sammobile) through odin, which was a success... until it booted up, and found that again, the proper partitions were not mounted. From there, I went on to flash CM9, which ended me up to where I am now.
As it currently stands, /dbdata, /data, /emmc, and /sdcard are all unmounted and are stuck that way. Does anyone know how to solve this, cause I am lost right now.
Click to expand...
Click to collapse
I would try to find out what the log files say. If you can still make a full backup under CWM, I suppose this should include the last log written by android. This is where I would start my investigation. It is of course strange that android fails to mount the /data partition. I have no clue what /dbdata is for. My gut feeling is that your friend messed up the partioning, but I think it is key to find out what happens during boot time.
Finally, since you didn't write about this: Did you try wipe the cache and dalvik cache in CWM?
Related
Ok hear me out. I have an idea. We need a "rom" that fills the phone with garbage, sort of like you would do a secure wipe, but one that leaves the recovery partition alone so it isn't truly bricked.
My reasoning is the seeming strange ability for parts of roms to linger. Such as when I went from KF to KGB and back to KF, it somehow merged some settings from KGB despite me doing a complete wipe between flashes. Now we have people who for some reason are griping about FC'ing constantly with Tazz GB.
What the rom could consist of is 128MB of /dev/urandom or something (or one huge file per partition however it is layed out.) And make sure it is signed so it will flash. With this rom, we could just download it once and leave it on our SD card and flash the phone with it between rom changes. We'd need to make sure that it overwrote /system /data and the dalvik cache partitions.
Plus it would be an interesting way to securely wipe a phone prior to running flashback and selling it or returning it to Verizon.
I'm sure the rom would take all of 5 minutes to make, we'd just have to make sure that it didn't touch recovery.
Then when someone is having all sorts of problems, recommend they flash BrickRom on it and then reflash back to what rom they had issues with.
adb is available when Amon_RA is running.
It's pretty trivial to go in there and mount /data after you have done a "wipe data/factory recovery". You should see nothing but the lost+found directories in both /data and /cache, and in /cache the /cache/recovery folder (which will contain the log file). Nothing else.
If you mount /system, you will see that it is still fully populated prior to flashing a ROM - that's intentional, so that if someone tries to flash a corrupted ROM, it will not pass verification (in Amon_RA, anyway) and so the phone should still boot into a FR'ed ROM. It is the ROM developer's responsibility to insert a "format SYSTEM:" directive in his/her ROM installer script; if that fails to happen, they could end up with a mixture of things in the /system mount from the new ROM and the prior ROM. I don't know if that has ever happened, though.
There are other possibilities revolving around the SD card - for instance if you moved apps to the SD card (/sdcard/.android_secure) for Froyo/GB, or the ext partition for Eclair ROM users. Amon_RA does not clean either of those up (whereas ClockworkMod does). If you install a ROM that has apps2sd installed by default, and you haven't manually cleaned up the ext partition... well, that's not really Amon_RA's fault.
If you can reliably repeat the behavior you are describing, then do a wipe (in Amon_RA), and then prior to flashing the new ROM, use adb (wth Amon_RA still booted, of course) to:
Code:
mount /system
cd /system
rm -rf /system/*
cd /
sync
umount /system
If the symptoms you are describing still persist (and you are using Amon_RA), then the problem most certainly results from stuff stored on the SD card.
I think a rom like that would be great, Stonent. I have had the same issue with certain roms. Are you thinking of some sort of rom that just contains format commands in the update script that doesn't actually flash a rom (a wiping rom)? I like that idea, but I have no idea how it could be made or if its possible, and I don't have much experience with things like that. Maybe someone could cook something like that up, I think its a good idea.
It's probably files on the SD card with identical names. Like if an app saves a config file to the SD and then KF looks for that same config file it'll carry over between ROMs.
Beginning with Froyo, Android keeps some files linked to your Google account (such as the wallpaper for example) I don't know if that is the same as this behavior but lots of apps store their data to SD (but not same as apps2sd)
I didn't know where to put this but I had to put this somewhere since it helped me so much.
I was trying to back up my ROM in cwm but it said it couldn't mount /system. I tried everything. I tried to update busybox, reinstall su, format SD card, everything. Nothing worked. I was going to wipe everything clean, when I had one last idea.
I tried to flash a new kernel in CWM, and when I did it remounted the system partition for me and I could create and restore backups! So if nothing works and you have the /system problem, try installing a kernel.zip from your SD card.
Hello,
I have posted this on the general q&a already but i think i can get a bit more help here.
I bought a Samsung Galaxy S2 a few days ago.
It is the international version (i9100).
The problem is, i had it rooted and installed cm9 on it.
Then when i tried to make a backup the file was only 16 mb because the sdcard wouldn't mount in cwm recovery.
When i try to mount it manually in cwm it also gives the same error: Error mounting /sdcard!
I already tried like everything, flashing other cwm, other rom, also the original samsung firmware flashed back on gives the same error, another kernel, factory reset and cleaned the cache.
I don't know what i can do now to remount the internal sd card again.
Even when i try to format /sdcard it gives the error.
The only thing i haven't tried is re-partition but i've heard that it will brick your device since it has the bootloader in it which you will also delete.
I am now running cm10 because i thought when you change to cm10 it repartitions automatically. Didn't help either.
I hope someone can get me out of this problem.
Erwin
I recently had some disruptive partition troubles. I don't know how they started (must've been a bad flash, or a flash which didn't finish seeing as though i was experimenting with the leaked roms) but basically, my /cache, /system, /data, and /emmc partitions were all corrupted.
Fixing the /emmc, /cache and /system partitions was quite easy. I booted up into fastboot mode, flashed an ADB enabled recovery (the one in the Atrix Development forum works fine) and downloaded ADB.
I booted up into recovery, and in CMD i went into adb shell and used "parted /dev/block/mmcblk0p18" to get into the emmc partition, "rm 1" to remove the corrupted partition and "mkpartfs" to make a new partition as ext2, start 0, end 11.5GB (or something like that) and let it finish. Then i went into Mounts and Storage in CWM and formatted emmc. Did the same for /cache (mmcblk0p15) and /system (mmcblk0p12).
So far so good, my random reboots were fixed and my deadly FC of all apps was gone. But not for long.
I noticed after about 24 hours of normal use, i would start FC everything and multiple reboots + clearing caches (including dalvik) would fix it temporarily. This was a headache as messaging, phone and whatsapp would all crash and not recover.
I chalked this down to the /data partition (also known as /userdata, which houses the dalvik cache). I must be hitting a corrupt part of it during my daily use which messed my device up (once i hit the corrupt part, i could not do ANYTHING with the device, including just checking a partition. I would ALWAYS have to reboot at least twice to even read the partition).
I tried the same method as before (mmcblk0p16 for userdata partition) but i couldn't do it. It would always fail at around 90% and say i/o error and needed a few reboots. If i made a fat32 partition, i couldn't format over it with CWM (error near the end). Same with any kind of partition. This was the partition which couldn't be fixed...
So i decided to go all out. I knew i never flashed OTA 2.3.4 (Gingerbread), so i downloaded the Gingerbread SBF from a quick google search, despite all the warnings (i also THINK you CAN flash this SBF even though you were on OTA 2.3.4, just NOT ANYTHING LOWER SUCH AS FROYO). I booted into RSD mode and hoped for the best. Flashing went fine, but i was in a bootloop (due to data partition). Tried clearing with the stock android recovery and i would get i/o errors even though it said successfully wiped.
It was here when i got angry.
I flashed the ADB enabled recovery via fastboot and booted into it. Went into adb and parted again (first i inspected emmc partition which was mmcblk0p18). Did "print" and it said couldn't find label or something (which meant no partition table was found). ALL my partitions were missing this partition table.
So i created one.
"mklabel msdos" for emmc partition, then mkpartfs to make a primary partition, ext2, start 0, end 11.5GB" (or something like that) and let it happen.
For cache partition, i did "mklabel loop" then mkpartfs ext2, etc etc, with data i did "mklabel loop" and made a partition, same with system.
Then i tried wiping them via CWM. SUCCESS! I formatted them 5 times each just to be sure and sure enough, they were working fine now. I flashed a new ROM (couldn't risk my backup partitions having a corrupt sector or something in them) and heavily used it for a few hours. Downloaded many apps and games, did loads of texting and test calls.
No reboots. No FC, no problems for 24 hours. Hope it stays this way.
I posted this in hopes that others would find a solution with this rare problem. My data partition was the killer, no matter what, i couldn't fix it without flashing sbf. Remember, don't flash froyo sbf, only gingerbread (just to be safe).
I have a Nook Tablet 16GB. It won't even power on to the "n" logo screen unless there is a CWM SD Boot card installed. I get mount errors once inside CWM.
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/
I've tried the Factory Restore (repart.img) and it runs through and tells me the device will shutdown in 5 seconds. (The other times I've used this it sits at a green check mark until I shut it down manually) This doesn't resolve the issue or make any changes at all.
I've tried Adam's Ubuntu method and the device boots to the SD card but sits at a blank screen after a few seconds and does nothing, even when left on over night. This doesn't resolve the issue or make any changes at all either.
I can connect to the device in ADB and the plan was to use parted to fix some partitions using Veronica's methods, but when I run the parted /dev/block/mmcblk0 print command no partitions are found at all on the device. I'm never prompted to fix any partitions either. The only thing it sees in the ext sd card partition. In the past when I've done this it shows 11 partitions with some details. This time it shows nothing. I am unable to find any information anywhere as to what to do next.
It is as though the internal SD Card (memory/hard drive whatever you call it) isn't working or detected by the system any longer.
Does anyone have any recommendations on what to try next? Please help!
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
digixmax said:
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
Click to expand...
Click to collapse
I made an SDCard using Succelent's repo and was able to boot to the Cyanoboot Bootloader but a few seconds later it just went to a blank screen. I rebooted and could get into recovery by holding the "n" button and selecting that. When I select to boot from SDC it just goes to Bootloader and then goes blank. It never boots into the OS.
I never mess around with partitions and I'm not sure how this thing got this way. I purchased it from eBay as a tablet for my daughter. It did say the device was bricked but that the hardware was okay. I've seen bricked devices in the past and the repart.img (Factory Reset) has always resolved the problem. I have a Nook Tablet that my son has been using so I've become pretty familiar with the basics of rooting, loading CWM, TWRP, Cyanogenmod, etc. But I've never seen it were I get mounting errors inside of CWM and am unable to flash anything. It won't even mount the external SDCard once inside CWM.
Not sure what to do and I hate to give up on this. Any help would be greatly appreciated.
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
This happened to me last year. There is a post in development section about fixing partition table by So****e. It's the last resort, but worked for me.Also, Adam Outlers Ubuntu method loses your serial number, gone forever. Good luck
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
DEjaVu
Happened to my first nookT not to long ago....It died but the best advice I can give has already been given try not to erase more stuff. Digimax helped me not to long ago. Make sure you format your sdcards correctly and if you can flash a recovery or boot into it you should be able to use one of Succulents cards. Good luck
digixmax said:
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
Click to expand...
Click to collapse
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found. I also tried wiping my cache partition again from inside cwm, but no luck. Still getting the mount errors.
I believe the real issue is that my device doesn't see /dev/block/mmcblk0 (or rather is sees it as the external SD card). there is no /dev/block/mmcblk1 either. I thought perhaps the internal and external were swapped, but that doesn't appear to be the case. So since the device can't recognize the internal SD card I don't think I will be able to get anything to flash until I get that resolved first. I'm certain that is why Adam Ubuntu fix and Meg's reprt.img aren't working.
Probably the only way to do that, if it is even possible, is to do it through ADB. Veronica has a thread that shows how to recreate all of the partitions, but when I attempt to do that it doesn't see the internal storage at all so I can't even get started.
I really hate giving up on anything so I will keep trying as long as it takes if I know it is possible to fix this, but I'm not sure what steps to take next to try and get the internal storage recognized.
For all I know it could be a permission issue.
Do you know any commands I can run from ADB Shell to try and get the internal storage recognized?
When I run a list command from ADB shell I get the following:
~ # ls
ls
boot fstab.acclaim sd-ext
bootdata init sdcard
cache init.rc sys
data internal_sd system
datadata proc tmp
default.prop recovery ueventd.acclaim.rc
dev res ueventd.goldfish.rc
emmc rom ueventd.rc
etc root
external_sd sbin
~ #
So it looks like the internal storage is working after all and I can get into some of these directories and files and CAT or TAIL them. Perhaps the MBR is messed up or something?
skelnik said:
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found.
...
Click to expand...
Click to collapse
You can try one of Succulent's more recent 10.2 builds listed at http://iamafanof.wordpress.com/2013...id-4-3-for-nook-tablet-imgsdc-boot-09aug2013/ which he uploaded onto Media Fire: "cm_acclaim_10.2.0-RC0_13OCT2013_HD_SDC_IMG.7z (mirror)".
You might also want to take a look at Succulent's recovery tools (in particular flash_stock_1.4.2.zip) at https://github.com/succulent/acclaim_recovery_sdcard.