[Q] Does not start, stopped on screen samsung - Galaxy Tab Q&A, Help & Troubleshooting

My tablet P1000L not want to start, getting stopped at the samsung screen. All updates have been made official, unofficial unchanged. When trying to power it (power + volume +) it reports the following error message:
cant mount / dev/block/mmcblk0p1
E:copy_dbdata_media: cant mount sdcard
your storage not prepared yet, please use UI menu for format and reboot actions.
In windows 7, when I plug the tablet in USB, it recognizes as unknown device. Does anyone know how to solve?

Related

GalaxyTab Model SGH-T849

Hello,
A friend gave me his previously new Samsung galaxy tab for T-Mobile tablet, he said he's ordered a new nexus 7,and doesn't need the galaxy anymore. The problem with it is when I power it on, it goes through the booting process (the animated screen with music)..then it just 'stops' @ the Samsung logo, and just stays there. When I power it down and press the power key + the volume + key together, it goes to the 'recovery' screen. It's says the following:
--Verifying internal MMC block...
checksum confirmation -> check(0)
Not need checksum confirmation
already executed!!...
# MANUAL MODE #
-- Updating application...
E:failed to mount /preload (No such file or directory)
E:install_application_for_customer:Can't mount /preload
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed.
--Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/PHN/system/'.
Successfully applied multi-CSC.
Does all of this actually mean the tablet is 'un-usable', or can it somehow be re-loaded with 'stock' firmware ? The previous owner never rooted this tablet, or installed ClockWorkMod on it either. Hopefully....someone else has had this issue before.
Thanks,
David :crying:
Try to flash the SHW-M180S firmware...I m using it on my t849 and it works like charm
Just google "White Identity Final.tar" (4shared)

[Q] i9000 bricked, help!

so my brother's phone got bricked for some reason. I tried searching for answers but I can't find answers. I'll be detailed as possible so imma list down the problems
Problems:
1. When turning on the device, it gets stuck on the Samsung Galaxy S logo
2. I can open recovery mode (CWM v3.0.0.5) but then these errors show up:
"E: unknown volume for path [/data]
E: Unable process volume! Skipping...
E: can't mount /cache
E: can't open /volume"
...etc
3. ADB can't see/detect the device
4. Went to Download mode but then Odin does not detect it. (I have the latest drivers from Samsung. I also tried connecting my Note 2 and Odin can detect it. I also tried different cables but none would work)
5. Tried inserting an SD card but i cant seem to find a way to flash from a zip file
6. Also tried restoring but errors appear (see #2)
How it got bricked:
My brother said that he simply rebooted the phone because of lag and that happened.
I'm not sure if USB debugging's on before this phone got bricked.
It's running Optimum Jellybean by Likeman and yes it's rooted
Help please (

Can't root Exynos Note 9: 'could not mount /data and unable to find crypto footer'

Bought a used TM-N960F that came with Android 9. Updated to Android 10 (maybe that was my problem?)
I did the "OEM unlock".
The Samsung USB drivers are installed.
I reboot the Note 9 to download mode
- Hold [VOLUME DOWN] + [BIXBY] and connect usb cable; press [VOLUME UP] to begin
I run Odin3 v3.13 in Admin mode and load twrp-3.2.3-0-crownlte_UNOFFICIAL.tar into the "AP" slot
I hold [VOLUME UP] + [BIXBY] + [POWER] on the phone and then press start on Odin.
- I hold the buttons until I see TWRP
* chose “Keep Read Only” to enter TWRP recovery
* selected “Wipe”
* selected "Format Data"
* typed "yes"
Then the errors come.
The first is:
"Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder."
There are more later but they are probably known to you and related.
Help?
Edit:
After the initial "format data" failed, I tried again and it seemed to work... I continued by attempting to install "N9_S9_Root_for_OEM_issue_devices_V3.zip" via TWRP. I see the following error when it attempts to install Magisks:
! Boot image patched by unsupported programs
! Please restore stock boot image
I guess that's my problem? Can someone please direct me to the steps by which I can restore the stock boot image?
Edit: I got the stock boot image restored I think. I followed the instructions here (given to me by my new best friend):
https://forum.xda-developers.com/ga...icial-stock-fw-update-odin-thread-xx-t3825204

Samsung Note-9 in Bootloop and Restart Loop Issue. Not able to restart

Dear Experts,
I need your help and Support to get a solution for the issue, I am currently facing.
What went Wrong
1. I bought this phone from one of my friend, which is FRP Locked and I was not able to remove the FRP Lock, though I tried and followed seeing many videos and posts online.
2. Then I used 4uKey for Android application to remove FRP.
3. I made my phone go into download mode, then used the above application to remove FRP. The application asked for the PDA and the required PDA info was not listed. As per the instructions I used the nearly matching PDA info and tried the further process.
4. Every time I tried with various PDA info, it started saying there is no matching data available.
5. Then I removed my phone from USB connection and as soon as I removed it from USB Connection, it started flashing with the following information.
#Reboot Recovery Cause is [BL:Recovery Mode Set by Key]#
E:Failed to mount/cache: Invalid argument
Support Single-SKU
Block-Based OTA
Supported API: 3
#MANUAL MODE v1.0.0#
E:Failed to mount /cache: Invalid argument
E:Failed to mount /cache: Invalid argument
E:Failed to mount /cache: Invalid argument
E:Failed to mount /cache: Invalid argument
E:Can't mount /cache/recover/last_locale
(After the above message, screen gets blank and again the same above message flashes and it happens repeatedly)
Solutions tried
1. After searching a lot on internet, i followed couple of possible solutions (all gone in vein)
2. I tried to restart by pressing the Power Button + Volume Down Button, it goes to the the position where it shows the Samsung Logo with Model Name and keep repeating the same, until I keep holding the button combination.
3. I tried to restart or to go the recover/reboot menu by pressing Boxy Button + Volume Up + Power Button, nothing happens.
4. I found somewhere, someone had posted that wait until the battery drains out and the phone gets powered off, then restart the phone it will work. That also did not work.
I could not attached the Image and Video for your reference. Not sure, how to attach. Please let me know, how to attach.
Kindly help me with the best option to resolve the issue. I have got Odin 3.13.1 installed. I have ReiBoot for Android available. None of these works, as the phone does not get into the Download mode or reboot mode.
Model - SM-N960F

[HELP] Samsung Note 5 suddenly stopped booting up and in recovery mode has dm-verity and failed to mount errors?

Hi guys, so all of sudden when I was trying to use my note 5 (no root), I noticed that it was powered off and I couldn't power it on with power button. Can you please tell me if there is a way I can recover data on my phone without losing them? I also have Google Authenticator which is connected to many accounts online, If I lose data I will lose everything! Here is what I tried so far:
First thing I did was a soft reset ( power button + volume down) and the mobile turned on but unfortunately it kept looping on the Samsung logo screen. Then I tried to go to recovery mode (power button + home button + volume up) and from there I tried "reboot system now", "wiping cache partition (which I hope it doesn't remove any data?)" and "Run graphics test: which failed with error no command and then wiping cached data" all of them without success. One thing I noticed in the bottom section of recovery mode there are these errors:
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
E: failed to mount / system (Invalid argument)
anyone?
Your nand is dead. get a new board, they're like 35 usd...
Why do you think the nand is dead? The phone is still working.

Categories

Resources