Related
Hello,
I have a Telus milestone that I am using on ATT in the USA. Earlier tonight I installed app2sd. Everything was great, then when I restarted my phone it booted up goes to the unlock screen, I slide it to unlock and it gives me all these force closures, I am unabel to get past them. When I go to the Android system recovery and attempt to reflash the firmware it says:
verifying package...
E: failed to open /sdcard/update.zip (no such file or directory).
E: signature verification failed
install aborted.
I am going nuts, last time I had an issue I was able to reflash the firmware through the above process and worked fine. Now I cannot get it to do anything. I cannot get it to flash, and when I let it boot all the way I am unable to get the main screen. any suggestions? I really love this phone and want to get it working again. Please help.......
I forgot to mention, I had launchpro or launcherpro home screen installed. I think that when I installed the app2sd it might have copied that to the card, and now its missing on the device internal memory. That is why its not giving me the main screen or anything beyond just a force close screen.
jgregoryj1 said:
Hello,
I have a Telus milestone that I am using on ATT in the USA. Earlier tonight I installed app2sd. Everything was great, then when I restarted my phone it booted up goes to the unlock screen, I slide it to unlock and it gives me all these force closures, I am unabel to get past them. When I go to the Android system recovery and attempt to reflash the firmware it says:
verifying package...
E: failed to open /sdcard/update.zip (no such file or directory).
E: signature verification failed
install aborted.
I am going nuts, last time I had an issue I was able to reflash the firmware through the above process and worked fine. Now I cannot get it to do anything. I cannot get it to flash, and when I let it boot all the way I am unable to get the main screen. any suggestions? I really love this phone and want to get it working again. Please help.......
Click to expand...
Click to collapse
Sounds like you partitioned your card for apps2sd and wiped out everything that was on it in the process. So any files, media, backups etc you had on the card might be gone now - and also the update.zip from whatever custom recovery you use (skrilax OpenRecovery, G.O.T OpenRecovery, etc) would be gone. I do hope you saved your nandroid backups somewhere else other than on the card itself.
The most direct way back to a bootable phone (as long as you don't mind out wiping any other mods you've made) is to flash an SBF file using RSDLite from the bootloader mode. Try flashing the service version, and if it still won't boot, try flashing the non-service version.
http://and-developers.com/sbf:milestone
If you do have a backup you want to restore, or if you just want to undo the apps2sd mod using the function available in the recovery you were using (if it has one), then you will need to place the custom recovery folder and update.zip back on the SD card and then you'll be able to boot into it.
I tried the flash file from the Telus Service version and it failed. I will try the other non service. I did take a look at my sdcard and all my files are still on it. I will use another sdcard for the non service version. Thank you for your help. Will leave reply on what happens. thank you again.
Okay. I have tried both the service and the non service versions. nothing happens. it just says no such file or directory. I am totally stumped. I have tried to reflash with other recoverys GOT and its the same results. I am at a loss as to what to do. Any suggestions?
When I try to do a factory reset it does not do anything, its says wiping, but everything is still on the phone. hmmm... I am at a loss as to what to do.
Okay. I had to download RSD lite, and use the power button / dpad up. I was then able to reflash. Whoo.... thought I was gonna hae a serious panic attack. Thank you for your input. I really apreciate it
You're welcome. The mode which allows RSD Lite to flash is the bootloader. On the Milestone it acts as the "master reset switch" if anything borks too completely.
Sent from my Nexus One using XDA App
I have my milestone back to stock rom. I tried to do the app2sd again and it just put the phone in a boot loop. So I just removed it and did another reflash back again.
I have a question though. As I was reading about how to fix my phone last night I came across a modified version of the Telus Milestone firmware called TelusLite. I downloaded it, but it does not have a sbf file. It is a nandroid md5 file and a couple other files. How do I installl it? I tried repeatedly. I even tried the G.O.T. open recovery, I mean I tried to install that by the camera button/power button menu. But it just stops it saying no file or folder found. I am learning a lot about the phone and how it works but I cannot figure out how to install G.O.T. or any other open recovery software. Any help would be appreciated.
So I rooted my phone a few months ago but there weren't many mods out yet, so I waited until just today. I saw this one http://forum.xda-developers.com/showthread.php?t=1157593
I followed everything until I got to the part where I had to go into recovery mode, but before I was supposed to reinstall packages to get into CWM I accidently clicked on delete all user data and delete cache date because I misunderstood. So I got into CWM after and followed it and rebooted but nothing happened and the SGS4G screen just goes on and off. I didnt know what to do so I gave this a try. http://forum.xda-developers.com/showthread.php?t=1001759
I thought it would bring my phone back to stock and rooted because I couldnt recover or restore anything. It just put me in a more confused situation. When I reboot in recovery or just turn the power button on, the SGS4G screen goes on and off still.
So all I can do is this. Go to recovery. reboot,reinstall,delete user data or cache data. It says "signature verification failed" then "installation aborted" when I reinstall packages. And like I said, when I reboot the system all it does is the SGS4G screen problem.
Is there a way to start me fresh to a stock and rooted point? I dont think I have any files or anything on my phone anymore(if that is possible). I wanted to try this over again, but correctly obviously
Thanks for any help. I really need my phone soon
Were you in download mode when you used Odin? It should have worked. Make sure that it shows a yellow symbol with the android alien holding a shovel.
Sent from my SGH-T959V using XDA App
Thanks for the reply! And yeah i was in download mode. Odin said it went through and it lead my phone into recovery phone. After that I rebooted but I'm still experiencing the SGS4G screen going on and off still. Nothing else loads.
How did you set up Odin? You got the correct file loaded into the PDA box?
Sent from my SGH-T959V using XDA App
mrchovee said:
So I rooted my phone a few months ago but there weren't many mods out yet, so I waited until just today. I saw this one http://forum.xda-developers.com/showthread.php?t=1157593
I followed everything until I got to the part where I had to go into recovery mode, but before I was supposed to reinstall packages to get into CWM I accidently clicked on delete all user data and delete cache date because I misunderstood. So I got into CWM after and followed it and rebooted but nothing happened and the SGS4G screen just goes on and off. I didnt know what to do so I gave this a try. http://forum.xda-developers.com/showthread.php?t=1001759
I thought it would bring my phone back to stock and rooted because I couldnt recover or restore anything. It just put me in a more confused situation. When I reboot in recovery or just turn the power button on, the SGS4G screen goes on and off still.
So all I can do is this. Go to recovery. reboot,reinstall,delete user data or cache data. It says "signature verification failed" then "installation aborted" when I reinstall packages. And like I said, when I reboot the system all it does is the SGS4G screen problem.
Is there a way to start me fresh to a stock and rooted point? I dont think I have any files or anything on my phone anymore(if that is possible). I wanted to try this over again, but correctly obviously
Thanks for any help. I really need my phone soon
Click to expand...
Click to collapse
signature verificaton failed means u dont have a modified recovery record
u can get that out of the cwm final thread and push it to system/bin folder overwrite the one dont replace it that will solve that issue for u
I did exactly what the thread for Odin said. I already had the 64bit drivers installed. I downloaded the link that was provided for the ROM and then Odin. The rom took a while to download but it finally did. After that I held both volume buttons and then plugged in the usb and then it went into download mode. After that I opened odin and then clicked on PDA. The only thing that I could click on was the non-extracted rom that I downloaded aforementioned above.Gave it time to download and it said successful. Then I rebooted once it sent me to recovery mode. It also states to try and do it without sim and sd card in the phone which i just tried. It went through as well, but still has the SGS4G going on and off
RaverX3X said:
signature verificaton failed means u dont have a modified recovery record
u can get that out of the cwm final thread and push it to system/bin folder overwrite the one dont replace it that will solve that issue for u
Click to expand...
Click to collapse
I would try that but idk how i would be able to push it into the system/bin folder when all my phone is letting me do is go into recovery mode
Did u flash ext4 yet?
A suggestion for you.
If you can get into Down load mode which it sounds like you can, I would use ODIN to flash KC1 with its pit, PDA, Phone and CSC files and let it fully load up. Then ODIN Whitehawk's deoxed KD1 + root and try to flash your other ROM again.
It is very hard to hard brick these phones. Always take care to make sure the mount points in recovery are set to unmount, mount, mount and finally unmount when instructed to do so.
If your getting stuck with the ext4 section which causes this boot loop alot, what I have done is to disable voodoo lagfix, reboot into the newly flashed ROM then go back into recovery and enable voodoo. Has always worked for me.
This is my first post so I apologize if I don't make any sense lol. I develop android apps for a medical software company and I'm wanting to start creating ROMs to help out this great community.
I forgot to mention: http://forum.xda-developers.com/showthread.php?t=1117554 - [REF]{BIBLE} Galaxy S 4G (7/24/11) <5:00pm cst> is your best friend
icbinb is a great rom. you will definitely have to odin, as bytesfree says. you should use kc1 by raver. after you odin kc1, boot up normally and let the rom settle in for 10 minutes. then get a root manager, such as super manager or root explorer. download the 2 files from krylons final cwm thread. move both to the proper location using the root manager. make sure the recovery file is named properly. if it has the extra .bin extension in the filename, remove it. then shut down the phone, reboot into recovery, go to reinstall packages and the orange cwm will load. once that loads up, factory reset, wipe cache, go to mounts and check the mounts (u,m,m,u), go to install from sd card, flash the ext4 converter immediately followed by icbinb. all of these zip files should be on the root of your sd. let me know how it goes.
if you get it to flash, remember to leave the phone sitting for 10-15 minutes in order for it to settle in.
also, bytefree, welcome to xda. glad to have you contributing.
As Jager said, ICBINB and others such as Black Ice are great ROMS with lots of tweaks and features. The guys that create these ROMs are awesome in their intellect and programming abilities. Mrchovee, once you get the hang of the steps required to flash a ROM it becomes second nature, just keep at it and don't let a gimped flash bring ya down man. As I said before, these little phones are hard to brick.
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?
Hey Guys,
So I have been all threw the forum over the past week plus trying to find a solutions and have tried the majority of the ones on the site. Here is what happend:
HOW I GOT HERE:
I was running a CM10 nightly build from 01/15/2013 that was installed via CWM. I had been running it for about a week. When I went to bed I set my phone on the nightstand. About 2 hours into sleep the phone rebooted as I eventually woke up and noticed it thinking it was just the phone wonking out. When I up fully 6 hours later the phone was still rebooting. Since then when ever I cut on the phone it will no get passed the Google logo with the padlock. I can boot into fastboot and recovery. I am running the latest CWM 6.0.2.5.
PHONE VITALS QUICK GLANCE
Android ROM version: CM10 01/15/2013 Nightly Build
Baseband: D720SPRLC1
Bootloader: D720SPRKC5
Recovery: CWM v6.0.2.5
WHAT I HAVE TRIED
Restoring from backup
My first fix was to flash three different roms via recovery (doing full wipes each time)
Then I tried flashing a new recovery
Formatting /system, /cache, /data, and /boot and then flashing a new rom
Then I focused on trying to get the USB storage to mount so I tried using adb shell to repair the file system and that worked
Then I tried new roms and things got REALLY weird. When I would place a rom on “sdcard” it would be available to flash. When I flashed it though it would not take and upon returning to recovery it wouldn’t be there or when I mounted the storage again. After about 10 times of this I figured let me make sure I am not crazy and try the following.
Format the internal storage. In windows when I tried this windows would show that the device formatted and was empty one I dismounted after putting items on it and go back to storage by both remounting it or by recovery the old data would come right back. In Ubuntu when I tried formatting it both via disc recovery and gparted they both said the device was empty but that they were unable to create a partition.
So then I went down the path of all of the debricking tools out there including the one from AdamOutler's (I think it is called ressurector), ODIN, and the Nexus Root Tool all with varying results.
Ressurector kept saying injection failed
ODIN just does not work on the nexus s from what I can tell (spent a day researching and no one seems to give a definitive answer on this one)
And Nexus Root Tool attempts to flash back to stock but runs into an error with the baseband.
So next I decided to try and flash back to stock using the Google images. Using Ubuntu I ran the flash-all.sh that comes in the zip and kept running into the baseband issue.
So next I found OldBlue910’s post with all the OTA updates and I went after trying to use that to fix my phone. Thanks to the amount of instruction he gives I got a lot further and got the flash-all.sh in his stock zip to give me a better error message telling me which baseband I needed to have to go back to stock which when I double checked he includes in the zip. The problem is when I try to flash that radio fastboot tells me I was successful but the bootloader still reads as D720SPRLC1 and does not change regardless of what I do. When I try flashing the stock images again after flashing the radio I receive the same errors.
So now I think I have hit the real brick wall and unless someone has any advice I will need to go and buy a new phone. Hoping you guys can help. I figured if you guys can figure out a hard brick then this is still doable, I have just exhausted my own realm of knowledge.
Please and thank you’s to anyone with advice.
Could you get any lights ON? The buttons or the screen?
lights are on
Yes during the boot loop the Google logo comes up, then the screen goes black, then the Google logo comes back, and finally in about 20 seconds the lights come on. Once that happens after about 4 minutes the process starts all over again.
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?