Related
I installed gummy 1.9.1 on my wifes charge a few weeks ago and she hasn't had any problems at all. Out of the blue her phone won't boot past the Samsumg logo screen. I can't get the phone recognized on odin and she doesn't have a backup from CWM. She didn't do anything to the phone to cause it. Anything I can do?
I was able to get into download mode and was able to get odin to recognize the phone. I reflashed gummy 1.9.1 through odin. Put battery back in phone and rebooted and the phone is still stuck on the samsung boot logo.
Try the instructions in this thread.
http://forum.xda-developers.com/showthread.php?t=1111486
If you want to go straight to EE4, use the PIT file from that thread, and download the stock EE4 rom from this thread.
http://forum.xda-developers.com/showthread.php?t=1116867
Have you wiped cache and data?
Sent from my SCH-I510
Yes I wiped. I'm trying the How To Fix Phone method and so far have no luck.
ercDROID said:
Yes I wiped. I'm trying the How To Fix Phone method and so far have no luck.
Click to expand...
Click to collapse
what is happening in odin when you use the ee4 stock and pit file?
you are following this right? Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.
Everything goes through fine and it says that it passes. I reboot and the same error comes up and it boots into stock android recovery.
fitti28 said:
what is happening in odin when you use the ee4 stock and pit file?
you are following this right? Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.
Click to expand...
Click to collapse
don't uncheck auto reset or f. reset time unless you want to bork whatever your flashing and have your data wiped on the first few reboots
blazing through on my 4G Droid Charge
ercDROID said:
Everything goes through fine and it says that it passes. I reboot and the same error comes up and it boots into stock android recovery.
Click to expand...
Click to collapse
blue android system recovery <3e>? If so i had that last night.
I had to odin FE1.9.1 to get me back in order
I tried that already. I tried the Samsung PST method going back to stock. All I get now is the samsung logo and then the charge boot animation and then it goes into a boot loop. I'm getting very tired and frustrated at this point. What would cause this to happen? My wife doesn't do any flashing or anything on her phone. I flashed this rom a month ago and she already had the OTA EE4 update. Would Verizon know what software is on the phone if i can't boot into the phone? At this point I don't know what software is on there.
This is the error I always get
--bootmode=7 from cmdline...
E:Can't mount /dev/block/mmcblk0p1
(No such file of directory)
-- Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
-- movi_checking done!...
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
Still not working. I tried the full odin of gummy 1.9.1 and the CWM did come over. I can't do anything inside of there though. I keep getting:
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I'm hoping that somebody can help me out. I'm lost at this point.
It does not seem like the PIT file works. I have tried so many things. If anyone is out there that can help please PM me and we can talk over the phone.
ercDROID said:
This is the error I always get
--bootmode=7 from cmdline...
E:Can't mount /dev/block/mmcblk0p1
(No such file of directory)
-- Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
-- movi_checking done!...
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
Click to expand...
Click to collapse
damn, you know what you may need to pm Imnuts or Kejar for their help... I was trying to help another guy with this exact problem a few days ago and we got nowhere unfortunately, though that error is related to the /cache partition if it helps in your search
I contacted IMNUTS. Hopefully he gets back to me and helps me out. I have the phone going through the boot animation loop and after a few it goes to a black screen that shows my status bar(showing no connection), battery icon and time. Then it goes back to the boot animation loop.
Did you ever get this resolved? I'm having the same issue right now.
I was on GummyCharged GBE 2.1 and sometime last night it died out of no where. Wondering if it had to do with DST.
Anyhow...I've been unsucessful in getting anywhere, I've googled just about everything I can think of, and I've been working on this thing on and off for about 5hours.
Pretty new at this stuff too, so not sure if I messed it up somehow.
LinkinPrime said:
Did you ever get this resolved? I'm having the same issue right now.
I was on GummyCharged GBE 2.1 and sometime last night it died out of no where. Wondering if it had to do with DST.
Anyhow...I've been unsucessful in getting anywhere, I've googled just about everything I can think of, and I've been working on this thing on and off for about 5hours.
Pretty new at this stuff too, so not sure if I messed it up somehow.
Click to expand...
Click to collapse
through trying to guide others with this issue, troubleshooting, talking with devs, and attempting every kind of recovery I've learned that this /cache partition error (E:Can't mount /dev/block/mmcblk0p3) is a sort of perma-brick that is unrecoverable, or at least no one's been able to come up with a definite cause or fix yet... just try to Odin back to stock for whatever good it'll do and take it to verizon to get replaced
****I'll say it again for anyone who may get this error in the future: as of now there is no known cause or fix for this error, it seems to happen at random and cannot be recovered from. Please try and Odin back to stock for whatever good it'll do (at least so it looks like an accident) and see about having verizon replace it
That's what I feared. Mine's back on stock, and it just loops on the Droid Eye flash screen, I'll take my chances with Verizon.
Were you able to get your exchanged? If so, any tips on what you said?
LinkinPrime said:
That's what I feared. Mine's back on stock, and it just loops on the Droid Eye flash screen, I'll take my chances with Verizon.
Were you able to get your exchanged? If so, any tips on what you said?
Click to expand...
Click to collapse
I haven't had it happen to me but in another thread myself and others were trying to help about a half dozen people with the same issue and i believe those who reported back said they got it replaced no problem but didn't say how unfortunately
LinkinPrime said:
That's what I feared. Mine's back on stock, and it just loops on the Droid Eye flash screen, I'll take my chances with Verizon.
Were you able to get your exchanged? If so, any tips on what you said?
Click to expand...
Click to collapse
So did you get a replacement and did you have any issues in sending yours back?
Hello,
I'm having a problem with restoring my phone to life.
Since yesterday he stays in the white htc screen when power on.
I read many topics about that situation but non of them really solved it for me.
I have the phone S-OFF and rooted with Revolutionar.
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
I want to install CyanogenMod 7 for the HTC Desire S :: V7.1.0
So i press volume down / power into the -Revolutionary- screen.
Then RECOVERY, the phone then reboots in to clockworkmod recovery 5.0.2.0
I get the folowing messages:
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I ignore the messenges en choose to wipe cache.
I takes a long time and then i get a message:
Cache wipe complete.
E: Can't mount /case/recovery/log
E: Can't open /case/recovery/log
E: Can't mount /case/recovery/last_log
E: Can't open /case/recovery/last_log
Now i choose to wipe data/factory reset.
Again i takes awile and then i get a message:
--Wiping data..
Formating /data..
Formating / cache..
Formating / sd-ext..
Formating / sdcard/.android_secure
Data whipe complete.
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
Now i choose advanced to wipe Dalvik Cache.
I don't get any message after this.
Now i choose to reboot recovery.
The phone reboots.
Now i choose to Wipe Data/Factory Reset once more.
Again the same messages as before - Data wipe complete.
I think the phone is empty by now.
So i choose instal zip from sdcard - choose zip from sd card.
i choose update-cm-7.1.0-DesireS-signed.zip
Confirm install - Yes install update-cm-7.1.0-DesireS-signed.zip
I get the message:
Finding update package...
opening update package...
Installing update...
E:Error in /sdcard/update-cm-7.1.0-DesireS-signed.zip
(Status 1)
Instalation aborted.
I get this message all the time even with diverent mods.
What does this meen? Please help me out of this mess
Had exactly the same issue today..
Read this if u want.. http://forum.xda-developers.com/showthread.php?t=1150917
I flashed custom recovery from here http://forum.xda-developers.com/showthread.php?t=1130004
And everyng is fine again!
pa3e said:
Had exactly the same issue today..
Read this if u want.. http://forum.xda-developers.com/showthread.php?t=1150917
I flashed custom recovery from here http://forum.xda-developers.com/showthread.php?t=1130004
And everyng is fine again!
Click to expand...
Click to collapse
I'm going to trie it in a few hours thanks for the tip!
I wil post if its works for me too.
It did not work, now i'm trying some other things see here:
[GUIDE] Read this before going for eMMC replacement.
If the beyond solution fails, take a look at this, it may help you.
http://forum.xda-developers.com/showthread.php?t=1284196
Swyped from my HTC Desire S
The answer to your problem:
Possible FIX for the infamous eMMC problem..
Just got a message from HTC Netherlands after sending my phone to them.
They say that the eMMc was fried by the s-off tool I had used. And thats why my warranty is now void. They tell me the replacement of the main board cost me €180,-
But if i dont want that and just want to get my phone back, i still need to pay them €30,- for the research of it. WTF!! next time i will microwave the freaking phone before i sent it to them. Now they just refurbish it and give it away....
I'm totaly done with this policy. thanks again for everybody's help.
spankranger said:
Just got a message from HTC Netherlands after sending my phone to them.
They say that the eMMc was fried by the s-off tool I had used. And thats why my warranty is now void. They tell me the replacement of the main board cost me €180,-
But if i dont want that and just want to get my phone back, i still need to pay them €30,- for the research of it. WTF!! next time i will microwave the freaking phone before i sent it to them. Now they just refurbish it and give it away....
I'm totaly done with this policy. thanks again for everybody's help.
Click to expand...
Click to collapse
Same thing happened to me.
In Italy they asked me € 201
I think tomorrow I'll bring back the phone.
I asked some of the forum and I think there is a solution for not spending all that money
kramegna said:
Same thing happened to me.
In Italy they asked me € 201
I think tomorrow I'll bring back the phone.
I asked some of the forum and I think there is a solution for not spending all that money
Click to expand...
Click to collapse
Im intressested, maybe we can mobilize some Desire S owners and claim a repair of this faulty chip.
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
otisranson said:
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Click to expand...
Click to collapse
otisranson said:
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
Click to expand...
Click to collapse
yup, this ones explainable. classic symptoms of a ns with its internal sd card dying/dead. it happens way too often unfortunately. luckily its a fairly easy and inexpensive repair, if youre not under warranty.
Any direction on how to fix it while not under warranty?
Or take it to tmobile?
otisranson said:
Any direction on how to fix it while not under warranty?
Click to expand...
Click to collapse
check out any local mobile device repair shops. you could probably do it yourself if you dont fear taking the phone apart, it should be to difficult of a repair. its just a matter of buying a replacement(ebay?), taking the phone apart, and replacing the sd.
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
I've been having similar issues..what is the exact part name for the SD?...I wanna search to buy one
Sent from my Nexus S 4G using XDA Premium App
I think its:
Samsung KB100D00WM-A453 memory package and S5PC110A01 1GHz Cortex A8 Hummingbird Processor.
I'm going to try to find another nexus s mother board as a whole, that's my only option.
otisranson said:
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
Click to expand...
Click to collapse
I think it's in step 10
i seen something a few weeks ago online on how to replace this...it was a video..i just cant remember where i seen it!
I ended up just purchasing a new phone on ebay.. If I find a nexus s with a cracked screen, I will swap out the mobo.
You can check whether there are blocks flagged as bad by FTL (Flash Translation Layer) in recovery. Check recovery.log file (it can be, the bad blocks will show up after formats).
Hello,
Today I woke up to my phone boot-looping after leaving it to charge overnight, despite it having run fine for close to a month (I have been running Cayanogen Mod ROM and TWRP 2.6.4.3 since I got my Nexus 5).
After a long wait at the Google and Nexus logos, there's a system popup of 'Cayanogen logo" present on the screen. However, right after completing the 'updating of apps', the system popup 'Media Storage has stopped working' appears and the phone immediately restarts again.
Upon booting into TWRP, it presents me with a password screen, which I have never encountered before. After pressing 'Cancel' though, I'm directed to the TWRP main menu.
Attempts to factory reset the phone resulted in:
Formatting cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Then i am using Nexus Root Toolkit and all are option i am going but nothing to do..
So please Watch this Video and Solved My Problem Please.. Please...
All are Process i am apply...Please developer help me......
Try locking your bootloader and rebooting. if it remains unlocked it's time for RMA/warranty cause you emmc is gone.
Niflheimer said:
Try locking your bootloader and rebooting. if it remains unlocked it's time for RMA/warranty cause you emmc is gone.
Click to expand...
Click to collapse
How to locking bootloader.. Please
apurbamajumder said:
How to locking bootloader.. Please
Click to expand...
Click to collapse
Install ADB/fastboot drivers . There's a thread in the stickies with the 10 seconds adb driver.
Press and hold volume down and power ( with the phone OFF ).
Connect phone to pc
open a command window .
change path to where you installed adb/fastboot ( e.g. if you installed in C:\ADB you would type cd c:\adb )
type fastboot devices . there should be a long string of numbers. If so , all is good. If not (and you get a message like waiting for devices) then you did something wrong. return to step 1
type fastboot oem lock . this will lock your bootloader.
Reboot the phone into bootmanager ( see step 2)
If it says bootloader locked all is good . Proceed to unlock it with the command fastboot oem unlock
If nothing changes ... it's time for warranty.
And stop using toolkits if you dont know what they do!
apurbamajumder said:
Hello,
Today I woke up to my phone boot-looping after leaving it to charge overnight, despite it having run fine for close to a month (I have been running Cayanogen Mod ROM and TWRP 2.6.4.3 since I got my Nexus 5).
After a long wait at the Google and Nexus logos, there's a system popup of 'Cayanogen logo" present on the screen. However, right after completing the 'updating of apps', the system popup 'Media Storage has stopped working' appears and the phone immediately restarts again.
Upon booting into TWRP, it presents me with a password screen, which I have never encountered before. After pressing 'Cancel' though, I'm directed to the TWRP main menu.
Attempts to factory reset the phone resulted in:
Formatting cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Then i am using Nexus Root Toolkit and all are option i am going but nothing to do..
So please Watch this Video and Solved My Problem Please.. Please...
All are Process i am apply...Please developer help me......
Click to expand...
Click to collapse
Try to get into fastboot and flash a full factory image. Unlock bootloader in fastboot is by typing in cmd: fastboot oem unlock. BTW don`t use toolkits.
gee2012 said:
Try to get into fastboot and flash a full factory image. Unlock bootloader in fastboot is by typing in cmd: fastboot oem unlock. BTW don`t use toolkits.
Click to expand...
Click to collapse
This is the problem
Send it to LG/ Google - emmc is gone to greener pastures so your motherboard will need replacing.
Nexus 5 (32gb) Mobile Internal Memory Storage 0mb
Niflheimer said:
Send it to LG/ Google - emmc is gone to greener pastures so your motherboard will need replacing.
Click to expand...
Click to collapse
How to say? mymotherboard replace But my mobile is ON !!!!!
apurbamajumder said:
How to say? mymotherboard replace But my mobile is ON !!!!!
Click to expand...
Click to collapse
The internal memory got corrupted too bad to recover. Since you can't replace it alone ( at least in a cost effective way) the entire motherboard needs to be replaced.
Sure , LG/Google will probably just slap a new emmc on that board once it gets in their factory and put it up for the refurbished list but ... that doesn't mean you can do it.
Hello,
I've seen quite some threads relating to this fail on the tablet, but all of them were because they were installating some custom ROM or kernel or something like that.
In my case, the charger cable I was using broke, and the tablet ran out of battery. Until then all normal. I buy a new original cable in Amazon, charge it, and then when I turn it on it stays on this screen. I tried pressing the power button for some time, so that it'd turn off but it keeps rebooting. In one of the times, it kinda started up on a screen saying that the encripting could not be completly (I was doing nothing like that so I was like what the hell?) and telling me to return to stock the tablet, losing all the data I might have on it. I accepted so it'd maybe at least reboot normally even if I lost my data, but it keeps rebooting and haven't entered again on such screen. Just one time, it entered in recovery cause a bunch of files could not be loaded, or something like that from what I could read. Unluckily I pressed reboot now and now it wont go again into recovery so don't know which files were the ones giving trouble.
I've never tried any kind of custom ROM, kernel or anything on this tablet, just on my Galaxy Nexus phone, so no idea why it'd brick like this. Looks just so random.
Thanks in advance if anyone could give me a hand on this.
SilentVene said:
Hello,
I've seen quite some threads relating to this fail on the tablet, but all of them were because they were installating some custom ROM or kernel or something like that.
In my case, the charger cable I was using broke, and the tablet ran out of battery. Until then all normal. I buy a new original cable in Amazon, charge it, and then when I turn it on it stays on this screen. I tried pressing the power button for some time, so that it'd turn off but it keeps rebooting. In one of the times, it kinda started up on a screen saying that the encripting could not be completly (I was doing nothing like that so I was like what the hell?) and telling me to return to stock the tablet, losing all the data I might have on it. I accepted so it'd maybe at least reboot normally even if I lost my data, but it keeps rebooting and haven't entered again on such screen. Just one time, it entered in recovery cause a bunch of files could not be loaded, or something like that from what I could read. Unluckily I pressed reboot now and now it wont go again into recovery so don't know which files were the ones giving trouble.
I've never tried any kind of custom ROM, kernel or anything on this tablet, just on my Galaxy Nexus phone, so no idea why it'd brick like this. Looks just so random.
Thanks in advance if anyone could give me a hand on this.
Click to expand...
Click to collapse
Hi, you should be able to boot into recovery by holding volume down and power. When it gets to splash screen let go of power and continue holding vol. down. Should be able to clear data and cache then reboot. You will loose data, like apps and passwords but it should boot all the way and be ready for set up. Hope it goes well for you.
Sent from my GT-P5110 using Tapatalk
homephysician said:
Hi, you should be able to boot into recovery by holding volume down and power. When it gets to splash screen let go of power and continue holding vol. down. Should be able to clear data and cache then reboot. You will loose data, like apps and passwords but it should boot all the way and be ready for set up. Hope it goes well for you.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Hi homephysician,
I tried that, and I just got a green text on the top left corner of the screen saying: 'logo_espresso10.jpg' draw failed.
Edit: I could go into recovery again. Trying to wipe the data and cache.
Edit2: When I tried to wipe cache, it says error and rebooted to the same screen (green text saying 'logo_espresso10.jpg' draw failed.) Anways, when I'm inside the recovery, it says this:
E:failed to mount /cache (Invalid argument)
can't mount ' /cache' (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/lastrecovery
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
E:failed to mount /system (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
tried Download mode? the system can't mount, since you haven't done anything, so it looks like your tab emmc card is gone haywire.
billysam said:
tried Download mode? the system can't mount, since you haven't done anything, so it looks like your tab emmc card is gone haywire.
Click to expand...
Click to collapse
I've no idea on how to do that. Never tried installing another ROM on the tablet. Been looking around the forum, but can't find a tutorial about that so I'm kinda lost.
Gonna try to look for that around, but I'd really appreciate it if you could send me a link or tell me how to do that as well.
SilentVene said:
I've no idea on how to do that. Never tried installing another ROM on the tablet. Been looking around the forum, but can't find a tutorial about that so I'm kinda lost.
Gonna try to look for that around, but I'd really appreciate it if you could send me a link or tell me how to do that as well.
Click to expand...
Click to collapse
you can enter download mode by pressing volume up + power button, if it shows then you can connect it via a usb cable to your pc and try to flash a stock firmware from sammobile.com or find from here
http://forum.xda-developers.com/showthread.php?t=2203309 (this has pretty much good links)
or look for your respective firmware, and then use odin to flash it.
there are many guides, it will take time and patience, everything you need you will find it here, but you should be able to enter into recovery or download mode or even should be able to make your device detected atleast to your pc, hope it's not a corrupted card, then you will need local repairmen.
PS Dont forget to mention and check your device model number, don't use P5100 files on P5113.
billysam said:
you can enter download mode by pressing volume up + power button, if it shows then you can connect it via a usb cable to your pc and try to flash a stock firmware from sammobile.com or find from here
http://forum.xda-developers.com/showthread.php?t=2203309 (this has pretty much good links)
or look for your respective firmware, and then use odin to flash it.
there are many guides, it will take time and patience, everything you need you will find it here, but you should be able to enter into recovery or download mode or even should be able to make your device detected atleast to your pc, hope it's not a corrupted card, then you will need local repairmen.
PS Dont forget to mention and check your device model number, don't use P5100 files on P5113.
Click to expand...
Click to collapse
Thank you billysam, gonna look for a guide, try that and post the results here.
By the way, my model number is P5100. Guess I gotta install those (can't be any other model).
Edit: My PC can't detect the tablet. I tried entering the download mode, but it only wants to go in this screen saying: Reboot now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache, apply update from cache. Only way I get the "connected device sound" on Windows is in the 'logo_espresso10.jpg' draw failed. screen, and it doesn't connect really. Nor Kies nor Odin can detect. They get stuck at SetupConnection.
Could I get the firmware in a SDCard, and use the "install from external storage" option?
Edit2: To make it clear, it says: "Installing system update..." -> "No command" -> "Error!" and gets in the recovery screen.
Edit3: I tried from SDCard and nothing, says installing /sdcard but it reboots again into recovery displaying all the same errors as before... Don't know, I think my tablet just bricked itself somehow... :crying:
You have beeen in recovery not download mode. You can not flash files through stock recovery since there is no file signed from samsung.
somehow you're not bricked and it's good that you can enter recovery mode as well, but it's all messed up. don't worry. You should be able to get into download mode, though, maybe you're missing the part to get into download mode, try once again, try differently pressing both up and down + power..
have you installed latest samsung USB drivers?
youre on stock recovery, so it's hard to flash anything unless you're on custom recovery and to get custom recovery installed you need download mode or your tab os running. which is not, check your cable check your USB check your buttons, it should get detected.
billysam said:
somehow you're not bricked and it's good that you can enter recovery mode as well, but it's all messed up. don't worry. You should be able to get into download mode, though, maybe you're missing the part to get into download mode, try once again, try differently pressing both up and down + power..
have you installed latest samsung USB drivers?
youre on stock recovery, so it's hard to flash anything unless you're on custom recovery and to get custom recovery installed you need download mode or your tab os running. which is not, check your cable check your USB check your buttons, it should get detected.
Click to expand...
Click to collapse
Tried all that to get into download mode and nothing... Gonna try now to let the battery die, since I can't switch it off any other way and try from there. Maybe it's because of that. Will edit with the results. And thanks for the help guys, really appreciate it. :good:
Edit: OK, got the tablet into the download mode. Flashed the stock firmware from sammobile with Odin, it sais PASS in green, but the tablet just won't turn on. Dunno if I did something wrong or what. Got it charging, and hoping it's maybe loading the firmware or so...
Edit2: Nothing... Guess it's really bricked now. Doesn't react to any button. Nor gets detected by PC. Guess i ****ed up somewhere in the process...
SilentVene said:
Tried all that to get into download mode and nothing... Gonna try now to let the battery die, since I can't switch it off any other way and try from there. Maybe it's because of that. Will edit with the results. And thanks for the help guys, really appreciate it. :good:
Edit: OK, got the tablet into the download mode. Flashed the stock firmware from sammobile with Odin, it sais PASS in green, but the tablet just won't turn on. Dunno if I did something wrong or what. Got it charging, and hoping it's maybe loading the firmware or so...
Edit2: Nothing... Guess it's really bricked now. Doesn't react to any button. Nor gets detected by PC. Guess i ****ed up somewhere in the process...
Click to expand...
Click to collapse
if you've flashed the correct firmware meant for your specific device, in the right manner, and got success passed in Odin without interruptions, it should boot up eventually..maybe the battery has given up and is not charged up, you can't hard brick a device with a right firmware flash and no interruptions.
hard bricks happens by flashing wrong device firmware.
I would suspect, the battery or the charger? cause you drained it completely and had broken the wire and bought new from amazon, wonder if its really without any fault. ( if you look closely you can see there are 2 type of dark screen..one when the device is actually shut off, which will be complete dark, the second is when there is power, it will have little light to it, I have come across this situation where the device battery was drained out, and it took me a lot of hours to bring it back on charging state...yes, I had flashed custom rom, and battery got low pretty bad and closed, I thought it was bricked but it did turn on)
try keeping your finger on the tablet screen and press power on button.
if its not, then the device emmc has given up or something on your side. (just a guess, it maybe is not, don't be so sure no matter what)
billysam said:
if you've flashed the correct firmware meant for your specific device, in the right manner, and got success passed in Odin without interruptions, it should boot up eventually..maybe the battery has given up and is not charged up, you can't hard brick a device with a right firmware flash and no interruptions.
hard bricks happens by flashing wrong device firmware.
I would suspect, the battery or the charger? cause you drained it completely and had broken the wire and bought new from amazon, wonder if its really without any fault. ( if you look closely you can see there are 2 type of dark screen..one when the device is actually shut off, which will be complete dark, the second is when there is power, it will have little light to it, I have come across this situation where the device battery was drained out, and it took me a lot of hours to bring it back on charging state...yes, I had flashed custom rom, and battery got low pretty bad and closed, I thought it was bricked but it did turn on)
try keeping your finger on the tablet screen and press power on button.
if its not, then the device emmc has given up or something on your side. (just a guess, it maybe is not, don't be so sure no matter what)
Click to expand...
Click to collapse
I plugged it and it doesn't do anything (switched light off just to be sure if the tablet screen would turn on even a bit, but nothing). Gonna do as you say and leave it there for some hours. Sorry I'm just kinda pessimistic about it... But yeah will try to bring it back to life.
I downloaded the firmware from sammobile, from the P5100 page. The latest, and the one from my phone provider (Vodafone, Spain). Used Odin3 v3.07. It showed PASS in green after the process ended. Just that the tablet never rebooted. It should have rebooted alone, but it just switched off and never reacted to any button again. Strange really.
Edit: Well, still nothing. No more ideas on what to do. Kinda giving it up since it doesn't react at all. :/
Does the device react if you plug the cable/tablet in to a computer?? And does the computer react when you plug the tablet in?