Hi folks,
I'm sorry for posting this but I need some of expertise here, because I managed to brick my Samsung Galaxy Tab 10.1 (IO Edition) and I've tried what I know and what I can find from searching here and on other boards.
The basic problem I believe is that I think the /data partition is trashed. I can't mount it from clocksworksmod, or from a recovery adb shell, and it seems like my internal storage is no longer visible.
1. If I'm booted into clockworksmod, and am in an adb shell, doing
"mount /data" results in error:
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
2. I can't see my internal storage anymore... Error:
"Unable to open ums lunfile" No such file or directory".
3. I've tried to wipe the data partition, but it no longer wipes. And I'm unable to do any recovery from clockworksmod.
4. I've tried to manually fastboot flash the boot/system/data from the 3.1 OTA image from droidbasement, but that didn't boot at all (stuck at the Samsung Galaxy Tab 10.1 splash screen)
http://droidbasement.com/db-blog/?p=2035
5. I've followed the direction to using Odin 3 to reflash my tablet from the suggestion of this thread
http://forum.xda-developers.com/showpost.php?p=14011086&postcount=26
When I did this, it boots up, but it's stuck in a "enter a password screen". I never locked this tablet, and I still can't mount the data partition and the internal storage is still not visible.
Does anyone have any suggestions on how to fix this? Some background information about what I did to get to this nightmare state.
*I was running clockworksmod 3.1.0.1 as the recovery image
*I successfully updated my tablet to HC 3.1 with the OTA update, and it booted and ran fine.
*After my HC 3.1 update, I rebooted into recovery because I wanted to take a backup of my system using clockworksmod. (Go figure that my decision to do a backup backup would end up causing this)
*For whatever reasons, I stupidly entered "reboot recover" from a adb root shell, and the device went into a hung state.
*I powered down/and powered back up by holding the power button for a few seconds....The tablet ended up going into a reboot loop.
*From the adb logcat, it appears that the /data partition was being mounted in read-only mode
--------- beginning of /dev/log/main
I/DEBUG ( 90): debuggerd: May 5 2011 01:05:44
I/Netd ( 89): Netd 1.0 starting
I/ ( 96): ServiceManager: 0x13858
E/DataRouter( 102): Main entered
E/DataRouter( 102): Data Router: INIT+
E/DataRouter( 102): dr_pcsync_init
E/DataRouter( 102): dr_init_pcsync_ipc
--------- beginning of /dev/log/system
I/Vold ( 88): Vold 2.1 (the revenge) firing up
D/Vold ( 88): USB mass storage support is not enabled in the kernel
W/Vold ( 88): dev_media add: /mnt/sdcard/usbStorage/->/devices/platform/tegra-ehci.0
D/Vold ( 88): void VolumeManager::handleBlockEvent(NetlinkEvent*)++ /devices/virtual/block/loop0
W/Vold ( 88): Can't handled block event for '/devices/virtual/block/loop0'
D/Vold ( 88): void VolumeManager::handleBlockEvent(NetlinkEvent*)++ /devices/virtual/block/loop1
W/Vold ( 88): Can't handled block event for '/devices/virtual/block/loop1'
D/Vold ( 88): void VolumeManager::handleBlockEvent(NetlinkEvent*)++ /devices/virtual/block/loop2
W/Vold ( 88): Can't handled block event for '/devices/virtual/block/loop2'
D/Vold ( 88): void VolumeManager::handleBlockEvent(NetlinkEvent*)++ /devices/virtual/block/loop3
...
...
..
W/UsageStats( 209): Error : java.io.IOException: Read-only file system reading data from file:/data/system/usagestats/usage-20110612
D/dalvikvm( 209): GC_CONCURRENT freed 139K, 4% free 6628K/6855K, paused 2ms+2ms
W/BatteryStats( 209): Error writing battery statistics
W/BatteryStats( 209): java.io.FileNotFoundException: /data/system/batterystats.bin.tmp (Read-only file system)
(more errors about read-only)....
*I rebooted into clocksworkmod recovery. And from a console shell on my laptop, did "adb shell"
*I did a mount "/data" from the adb shell, and tried to run e2fsck on the partition. e2fsck reported that my /data partition contained errors, and when I tried to run repair on it manually, it failed. When I did an "ls" on /data, I got a an IO error log/ directory.... I couldn't delete the log directory... At this point my internal storage was still available.
*I tried to do a wipe data/factory reset from clockworksmod recovery image...It failed.
*I then updated recovery to 3.2.0.1... And rebooted back into recovery.
*I then attempted to wipe the user data from clockworksmod recovery... This time it successfully wiped my user data... But it my internal storage (/sdcard) also disappeared and was gone.
* Tried to mount /data, and it failed....
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
*Tried to flash boot/system/data from the 3.1 HC zip file from droidbasement
http://droidbasement.com/db-blog/?p=2035
Flash seemed to complete, but can't boot at all
*Used Odin v3 and flashed the boot/system/recovery from bonzai3558
http://forum.xda-developers.com/showpost.php?p=14011086&postcount=26
but while it booted, it was stuck at a password screen and neither the /data nor the /sdcard is pointing to a valid file system.
Really could appreciate anyone's suggestion. Is there a way to explicitly recreate the /data partition and what do I do about the internal storage not showing up?
Ok. after mucking around with this all day, I finally got my tablet working again...
What I ended up having to do is
1) Using Odin 3, reflash the stock boot, system, recovery images
The stock images and odin 3 version I used were from here:
http://forum.xda-developers.com/showthread.php?p=14661061
And prior to using Odin 3, I installed kies,which includes the needed drivers used by Odin.. Kies download from here:
http://www.samsung.com/ca/support/m...softwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
2)After reflashing the tablet, I rebooted into fastboot mode and using a local copy of clockworksmod 3.2.0.1 image, I booted the clockworksmod recovery image locally
"fastboot boot recovery-cwm_3.2.0.1-sam-tab-10.1.img"
3)Once in clockworksmod recovery, I went to advanced->Reboot Recovery to reboot the STOCK recovery image on the tablet.
4)I then wiped the data partition using the stock recovery image and rebooted.
I don't understand why, but I could not property wipe the data partition using clockworksmod recovery 3.2.0.1 or 3.1.0.1, since it never mounted the /data partition correctly. The stock recovery image however works...Unfortunately, I also lost everything on my data partition and my internal storage (sdcard), but at least it's no longer bricked.
That sounds like a nightmare, well done on getting yourself out of it.
I have a feeling this will prove to be a very helpful post once the user-base grows
I was able to revive my IO edition with fastboot
I posted the procedures here.
http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111
novicejeep said:
I was able to revive my IO edition with fastboot
I posted the procedures here.
http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111
Click to expand...
Click to collapse
I saw your posting, but unfortunately it didn't work for me.
I ran into issues using the clockworksmod (3.1.0.1 and 3.2.0.1) to wipe the /data partition. It appears once I wiped the /data partition, it was totally trashed. It wouldn't mount again, and I couldn't fastboot flash the data partition at all. When I went back into clockworksmod to attempt to re-wipe /data, it wouldn't let me, and dropping back into adb shell while running the clockworksmod recovery image, I wasn't able to manually mount the partition either. Maybe it was just a fluke, since I'm sure others are using the clockworksmod recovery without a problem. But for the time being, I'm leaving the stock recovery image on my tablet, and I need to use the clockworksmod recovery, I'll just boot it locally from my laptop by doing a fastboot boot <clockworksmod>.
you, sir, are a gentleman and a scholar. go into my stable and take my finest horse! his name is winchester and he is the finest steed int he land.
seriously though, thank you. I almost started thinking that my device was unrecoverable.
Everyone confronting the password screen after 3.01 flashing, please bother to clear cache and data before running the rom!!!
Related
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.
So my phone is in a bootloop. I flashed CWM recovery via Odin to try to mount the internal storage since i have some things i need to recover before flashing new rom. in CWM under "mounts and storage" i tried everything, but nothing would show up in a computer. Also, mounting system says "Error mounting system" and adb devices doesn't recognize my device now with CWM. it did with stock recovery though, when put in adb mode
edit: flashed original revocery, got adb working, found some adbfileexplorer.jar file from the forums, that shows my device and some files/folders, eg /efs, /preload , cache etc. so they are not the files i'm looking for.
And when writing adb shell in cmd, i get "- exec '/system/bin/sh' failed: No such file or directory (2) -" error
Try philz recovery and aroma file manager to access the data partition.
A sudden boot loop in normal use usually means one or more of the partitions are corrupt, so you may not be able to access data.
boomboomer said:
Try philz recovery and aroma file manager to access the data partition.
A sudden boot loop in normal use usually means one or more of the partitions are corrupt, so you may not be able to access data.
Click to expand...
Click to collapse
Ok well now i got to use adb and via command "adb pull /" i pulled everything there was (This is the right command to do it, right?)
but only two folders, sys and tmp were pulled, none of which contain any relevant data, it would appear
Hello,
Device:
Samsung Galaxy S3 International
I have Cyanogenmod 11 and Clockworkmod Recovery v6.0.4.6 on my phone.
Problem:
Opening up CWM recovery:
Mounts and Storage Menu:
Error mounting /efs!
Error mounting /data!
Formatting /data. . .
Done.
Now /data and /sdcard mount successfully
Install update from zip file:
choose zip from /sdcard
No files found.
Now I'm sure only /efs is the problem.
Even wiped dalvik cache
After rebooting it still gets stuck even after reinstalling firmware
here's the log CWM Recovery gives:
Code:
mount: mounting /dev/block/mmcblk0p3 on /efs failed: Invalid argument
W: failed to mount /dev/block/mmcblk0p3 (File exists)
Error mounting /efs!
After rebooting and wiping cache
I: Can't partition non mmcblk device: /devices/platform/s33-sdhci.2/mmc_host/mmc1
How I messed up:
My battery is dying (literally, I need a new one) and I thought I plugged it in when charging but used a cord that wasn't connected. When I turned it on the screen froze after a couple of seconds, had to pull out battery and when rebooting it got stuck on cyanogenmod logo, pulled out battery again then it got stuck in boot.
Edit: replacing CWM gives
error: device not found
in adb
SOLUTION FOUND:
USED A NEW CORD, CONNECTED TO ODIN AND REPLACED BOOTLOADER IN ODIN 3.07
UNPACK ATTACHEMENT AND LOAD ONTO YOUR PHONE, REBOOT
I have a friends phone that gets stuck at the Samsung glowing logo during boot.
I can access download mode (Odin). In Odin mode I have tried to download files using the Odin3 (3.07) Windows app, along with the packaged cooperve_0623.pit, and S5830i_XXLA2_ODDLA1_DDLA1_by_Domnic79 (CSC, Modem, PDA). Odin download seemed to go OK. However on reboot I still see the same boot cycle, nothing more.
I can also access Recovery mode. (Vol+, Home, Power).
Here I see
Code:
Android System recovery <3e>
Android system recovery utility.
...
If I select "Apply update from sdcard I get:
Code:
Install from sdcard complete
E: failed to mount /sdcard (No such file or directory)
E: Can't mount /sdcard
(Assuming this is referring to the external sdcard slot, then this makes sense. There is no sd card.)
When I select reboot now
I see
Code:
--Applying Multi-CSC--
Multi_CSC: There are common apks
E: failed to mount /data (Invalid argument)
E: copy_log_files_to_data :: can't mount /dataRebooting...
When connected to the device in recovery mode, on my PC I see a few devices with warning labels under Device Manager. These are CDC Abstract Control Model, CDC ACM Data, CDC OBEX Data, CDC Object Exchange.
I have Kies installed. This is a handset for United Kingdom use.
I'm at a bit of a dead end. Because this phone is fairly old a lot of the links seem to point to files that are no longer hosted, or worse are hidden behind crappy subscription walls.
Any help appreciated.
hi @captainbadger, First get yourself SD card ( formatted properly for further use inside your legacy device ) , then follow through @ post#4 ; my comments ; starts from the line "1. Download one of the newest ,, till you reach the end of the post" , and log file entry of your Odin is much appropriated for the record mate. <Uninstall/disable kies , pretty useless piece of software and tempting to get in the way>
OK thanks I'll give that a shot.