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?
Related
After several hours of trying to fix my soft bricked gt-p6210 (stuck on samsung start up screen), I finally got it. At least, my tab boots up now.I was getting a bunch of error messages in Android Recovery and nothing seemed to fix it. Finally, I used odin and flashed the .pit file for a p6211 from Mod2Xtreme along with the bootloader, csc, and pda files i found on xda (I think). Thank you so much to everyone who posted files and gave information. I saw several people with this issue and most just returned their tablet. I attaching the files that worked for me, I am not guaranteeing they will not hurt your device. The upload window changed to an internet explorer error window? Tell me how to fix that and I will. If I am not supposed to post them, let me know. Just unzip them, load them into odin, check re-partition, and start. I am restoring back to stock, so I imagine it will restore the proper .pit for the p6210. If this is the case and someone wants to tell me how to upload it from my tab, I will be haapy to do this. I know next to nothing about any of this, so you can ask questions but I probably won't know the answer. Woo Hoo!
Help
Hi friend, please upload the files and do a mini tutorial. I have the same problem with boot looping
Enter Android recovery mode using volume up and power. clear cache, clear data, then reboot. when it is stuck on the samsung screen, enter download mode (volume down and power) and plug into pc. make sure you have kies and odin installed. open odin and load the following files GT-P6211 px_20111010_WIFI_16G.pit into .pit, GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5 into csc, P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5 into bootloader, and P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship_16G.tar.md5 into pda. leave phone blank, check re-partition and start. you have to unzip both files. when it reboots, it will be in russian. just fumble through to settings and change to language of your choice. any questions let me know.
It wont let me upload files, so get GT-P6211 px_20111010_WIFI_16G from http://www.mod2xtreme.com/showthread.php?t=11722 and P6210XXKL2_OXEKK1_16G from http://forum.xda-developers.com/showpost.php?p=20030890&postcount=11
Do realize by using a CSC file from a different country will cause you tab t have certain apps it shouldn't and won't have apps it should with Peel being one of them (I know from experience).
Just a warning.
ya, i noticed, but it is better than the tab being stuck in a boot loop. No one seems to have the right files to restore it to original. Will the ics update fix this?
If you can get your hands on a US based CSC file yes you can. I have yet to find one.
Or just flash a US based firmware to revert it to a US 6210. Recovery will have an error in it stating there is a missing folder but it is nothing to worry about.
Just use this post and use the password from the OP to open the archive.
http://forum.xda-developers.com/showpost.php?p=23320950&postcount=93
Works! Thank you!
Man, it works, and my tablet works like a charm now. Thank you !
Now i want to put ad-work wifi in my gt-p6210...i have a nokia N8 with joikuspot application( a tethering app), but my tablet don't recognize the wifi connection from my n8...
is it possible to work ad-hoc wifi on galaxy tab p6200 ou p6210??
Due to Samsung not releasing the source code for the wifi driver no adhoc support cannot be added.
worked here too man, saved my butt.
thnaks
Other files?
roc102782 said:
Enter Android recovery mode using volume up and power. clear cache, clear data, then reboot. when it is stuck on the samsung screen, enter download mode (volume down and power) and plug into pc. make sure you have kies and odin installed. open odin and load the following files GT-P6211 px_20111010_WIFI_16G.pit into .pit, GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5 into csc, P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5 into bootloader, and P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship_16G.tar.md5 into pda. leave phone blank, check re-partition and start. you have to unzip both files. when it reboots, it will be in russian. just fumble through to settings and change to language of your choice. any questions let me know.
It wont let me upload files, so get GT-P6211 px_20111010_WIFI_16G from http://www.mod2xtreme.com/showthread.php?t=11722 and P6210XXKL2_OXEKK1_16G from http://forum.xda-developers.com/showpost.php?p=20030890&postcount=11
Click to expand...
Click to collapse
And where do I get the other files you mentioned? Thanks in advance!
Cosmonal said:
And where do I get the other files you mentioned? Thanks in advance!
Click to expand...
Click to collapse
I have a p6200 with 3g module. Are these files OK also for my tablet?
Pit file for P6210 at the end of 1st post
http://forum.xda-developers.com/showthread.php?t=1667886
can someone tell how to get the bootloader and csc? Been searching through google and can't find anything, just pit files. Thanks
btw, i'm using p6200
valkyrie-randgris said:
can someone tell how to get the bootloader and csc? Been searching through google and can't find anything, just pit files. Thanks
btw, i'm using p6200
Click to expand...
Click to collapse
same here... tried looking for those files for gt-p6200 but can't find them... been trying to unbrick my tab too and i tried flashing HC stock thru odin and heimdall but all i have is boot loop and this following things when am trying to go to stock recovery mode:
# MANUAL MODE#
--Updating application....
E:failed to mount /data (Invalid argument)
E:install_application_for_costumer:Can't mount/data
your status not prepared yet, please use UI menu for format and reboot actions.
--Appling Multi-CSC..
Installing Multi-CSC
Can't access to '/system/csc/ITV/system/'.
E:failed to mount /data (Invalid argument)
E:multi_csc:Can't mount /data/media
your storage not prepared yet. please use UI menu for format and rebootactions.
Multi-csc applied failed.
those strings are when i was flashing stock Honeycombs using odin or even Heimdall though the flashing methods are completed, am still stuck in bootloop and those things are showed when am trying to go to recovery mode... and one more thing, when i was trying to Wipe Data/Factory reset it never showed complete anymore... the device just rebooted by itslef anymore... please help me i didn't know what to do anyomore
zepoy said:
same here... tried looking for those files for gt-p6200 but can't find them... been trying to unbrick my tab too and i tried flashing HC stock thru odin and heimdall but all i have is boot loop and this following things when am trying to go to stock recovery mode:
# MANUAL MODE#
--Updating application....
E:failed to mount /data (Invalid argument)
E:install_application_for_costumer:Can't mount/data
your status not prepared yet, please use UI menu for format and reboot actions.
--Appling Multi-CSC..
Installing Multi-CSC
Can't access to '/system/csc/ITV/system/'.
E:failed to mount /data (Invalid argument)
E:multi_csc:Can't mount /data/media
your storage not prepared yet. please use UI menu for format and rebootactions.
Multi-csc applied failed.
those strings are when i was flashing stock Honeycombs using odin or even Heimdall though the flashing methods are completed, am still stuck in bootloop and those things are showed when am trying to go to recovery mode... and one more thing, when i was trying to Wipe Data/Factory reset it never showed complete anymore... the device just rebooted by itslef anymore... please help me i didn't know what to do anyomore
Click to expand...
Click to collapse
I hav same problem before n sent to samsung centre...they changed my mainboard..but if u want to solve urself, then try to search Pit-patch for P6200 n using it...
Sent from my GT-P6200 using XDA Premium
roc102782 said:
Enter Android recovery mode using volume up and power. clear cache, clear data, then reboot. when it is stuck on the samsung screen, enter download mode (volume down and power) and plug into pc. make sure you have kies and odin installed. open odin and load the following files GT-P6211 px_20111010_WIFI_16G.pit into .pit, GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5 into csc, P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5 into bootloader, and P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship _16G.tar.md5 into pda. leave phone blank, check re-partition and start. you have to unzip both files. when it reboots, it will be in russian. just fumble through to settings and change to language of your choice. any questions let me know.
It wont let me upload files, so get GT-P6211 px_20111010_WIFI_16G from http://www.mod2xtreme.com/showthread.php?t=11722 and P6210XXKL2_OXEKK1_16G from http://forum.xda-developers.com/showpost.php?p=20030890&postcount=11
Click to expand...
Click to collapse
Where can I get these files? Want to try this before sending mine back.
Update: Sent back to Samsung...my power button was sunken in as well, so hopefully kill 2 birds with 1 stone.
Hello all. I've been at it for a most of the day now and I am still stuck, and I feel like I am going in circles so it is time to ask for some help. I'm posting how I got to where I am, so you can skip the next two paragraphs if you can help me without them.
Yesterday I rooted my phone with Odin3 and CWM, and then I flashed CyanogenMod 7 to my phone. Before playing around too much with my new powers I realized that the texts I was sending were blank. I went looking for a fix, and found that if you flash your modem from EH09 back to EE19 the SMS sending should be fixed. I looked for EE19 for quite awhile, to no avail. Oh well - I decided to go back to FULL stock and say to hell with it (this paragraph represents about 15 hours of work haha).
I found this thread explaining how to get back to stock: http://forum.xda-developers.com/showthread.php?t=881064 Great! Well, they were Megaupload links. However on page 16 someone was nice enough to rehost the files I needed: http://cdn.kpsn.org/android/mesmerize/ I tried going back to stock with the EH09 rar file and the EE19 zip file as per the instructions on page 1 of the thread. In both instances, when I turned on my phone after running Odin3 CWM booted automatically in a different way than I had seen before. There was blue text as usual but there was also red text. This was the error: can't mount \dev\block\stl11.
Here is my current state:
If I try to turn my phone on by solely pressing the power button, I get booted into a normal version of CWM. Except I get several errors on boot:
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
When I choose the "reboot system now" option it just cycles back into CWM, and the "Samsung" logo never even shows up. I can give more details if necessary and if anyone is willing to help it is greatly appreciated!
I've been thinking about it and I think the files from the 2nd link above might be the problem, but I can't find any other files elsewhere.
SOLVED!! Funny I was stuck for 4-5 hours then I posted this thread and got it figured out shortly after. Oh well, glad I'm back to normal now with EH09. From the 2nd link in the OP download the file named Samsung_i500_Mesmerize_EH09.rar and follow the instructions in the first link from the OP. Cheers.
Thanks for this Thread !
I had done same thing and was also getting error message in recovery ...
Downloaded the MD5 file and fixed through odin !
I Love XDA !!!
wow thank you
hi there thanks for the great info , i was stuck in cwm recovery mode due to a rom i installed on my ace plus but i wiped cache and wiped all user dater tried a fresh rom to no avail the problem was i tried everything and was about to throw the towel in when i came across my old superuser.apk file for making stock rom a super user (sorry if i sound noobish its because i am ) lol) strange i know i opened odin 3 and re flashed in download mode with the md5 file and got back my stock operating system back (virgin media rom) which i was amazed that it worked lol big hands up to you guys and thanks for saving me a ins claim lol ) thank you will thank author in a mo
I was using my XT925 normally. Then it hanged for some time and I restarted it. Suddenly it wouldn't get past the circling cm boot. I tried to wipe cache to see if it solved the situation. Entered recovery mode, wiped cache, tried to restart again, now it won't even turn on.
Except when I use power + vol -, it goes to the bootloader unlocked screen and stops there.
Is there something I can do about it?
somehow got into recovery mode. Tried to wipe cache and this appeared:
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
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O error)
Update 2:
Using rsdlite I got this error:
failed flashing process 1/19 flash sbl1 "sb1_signed" -> Phone returned FAIL
remove "get var"line from xml,then flash away
Thanks for the answer, but early today I went to a Motorola oficial store to see what they could do about it. They told me it was a hardware problem with the memory. I guess downgrading won't fix, if they're right.
It's really sad to have your phone not working anymore 1 month past the warranty limit. :/
There are ways... I ll check with you tomorrow man. It may still work
Wireless...
xusa said:
Thanks for the answer, but early today I went to a Motorola oficial store to see what they could do about it. They told me it was a hardware problem with the memory. I guess downgrading won't fix, if they're right.
It's really sad to have your phone not working anymore 1 month past the warranty limit. :/
Click to expand...
Click to collapse
Happy ? year
Ur phone working?
Wireless...
hbenz2008 said:
Happy ? year
Ur phone working?
Wireless...
Click to expand...
Click to collapse
Nah. I've decided to get a 2nd gen Moto G. I've expired all known troubleshoots and wasn't capable of solving this issue :/
weird man, what android were you running, you had cm ,right?
I would still try and flash gpt and tz if you still have it.
Anyway peace out man
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?
So i was using my phone 5 days ago like normal and sudendly it decided to reboot itself, after that it got stuck on the 4 balls android logo and doesnt boot into the system anymore.
what iv tried so far:
-Full Wipe
-Download and flash a full factory image, then full wipe
-Download and flash TWRP with SlimRom + Gapps then full wipe
Nothing works, it always get stuck in bootlogo, it just sits there dancing like its booting normally but it never does, im runing out of options here, what can i do guys?
Note: i have access to bootloader, all button works, also have access to recovery without any issues.
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
Let me download a kitkat image and see what happens, ill report back as soon as i do it
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
mediavieja said:
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
Click to expand...
Click to collapse
Aight so i flahshed twrp and slimrom again but im once again stuck on bootloop what do u suggest?
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
audit13 said:
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
Click to expand...
Click to collapse
Nope, tried stock MM (latest stock) and didnt work
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
audit13 said:
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
Click to expand...
Click to collapse
Must be then, cause i tried LP and didnt worked
I think it has something to do with differences in partition layouts between kk and LP/mm.
audit13 said:
I think it has something to do with differences in partition layouts between kk and LP/mm.
Click to expand...
Click to collapse
Do u know if theres anyway to fix it?
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
audit13 said:
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
Click to expand...
Click to collapse
Awww well thanks anyway for all ur help men, i really apreciate it
You are very welcome. We are all here to help and learn from each other.
The cheapest solution may be to buy a used nexus with a busted screen but working motherboard and perform a bit of phone surgery. I've done this a few times over the years with great results.
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
HSF3232 said:
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
Click to expand...
Click to collapse
Well i followed the procedure to fix persist, i was getting Unable to mount "/persist" (Invalid argument) so bu running command e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist i was able to mount it, after that i rebooted the phone to bootloader and i was able to flash and run the latest software update so i have to say thank you very much sir im gonna try to put slimrom now on this bad boy and change the post title to fixed