Related
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
I have spent the past 3 hours scouring over these forums before doing a post and I could find lots of great information if I could just get past the perpetual loop and access either the Recovery or Download Modes of my phone.
It is a Telus Samsung Galaxy Fascinate [SGH-T989D] and I have been tinkering with it for that past 24 hours to get it rooted and play with some of the ROMs out there.
I have gotten past the 3e Recovery Issues, resolved a Soft Brick and tested out 3 ROMs but now I am completely stuck and I think it is entirely my own fault but now I need some assistance in getting out of it.
This morning I threw on ICS_NBv9.2 and as it warned it went into a bit of a panic mode and has hit a perpetual Boot Loop. Now every post I have read says go into Download Mode and Odin back to Stock...I can't...it comes up with the Battery Image twice and then starts the boot up cycle all over again. The other option is to Flash the ROM again...problem is it continuously cycles through the Boot and never goes anywhere.
I have tried multiple Cables, reinstalled the USB Drivers, tried on 4 different Computers (2 Linux and 2 Windows) and well lets just say I am at the end of my rope.
Is there any known way to stop this kernel panic and let me get back to stock and put a functional ROM on the phone.
Thanks in Advance.
I may be able to help you...
Here are some solutions I can think of from the top of my head.
Try to see if your phone will connect to samsung kies on your computer via USB, there should be a way to restore it from there.
If you can't do this, then the next step would be to try and enter CWM Recovery mode (you should have this installed already, just look online how to enter into recovery mode). Next, mount your phone using recovery and put a stable rom (.zip) onto your phone. Factory reset, and wipe your phone, then flash the rom.
If you can't enter CWM Recovery, then the next step I can think of is to find a stable rom and flash it through ODIN.
If this isn't working either, then you just made yourself a very stylish paper weight! congrats.
There may stil be hope that if you call your carrier and tell them a sob story like, "my phone restarted on it's own and now it won't work properly." - and answer no if they ask you if you flashed, or downloaded 3rd party apps - then they might send you a free replacement.
Next time you want to flash your phone, remember... MAKE A BACKUP (nandroid) FIRST. That way if anything goes wrong, you can just restore it back the way it was.
Here is a site that may help you as well for rooting and making a backup for the t-989D (samsung galaxy s2 x - telus):
http://androidforums.com/galaxy-s2-...d-ultimate-root-optimization-guide-steps.html
Good luck,
J
Try This..
Remove Data Cable from Phone
Remove battery and re insert after 3-5 secs
now try to enter Downloading mode..
then insert data cable. and flash stock FW.
it should work..
The Paper Weight Theory
Thanks Input_Method and ranjan.
Unfortunately the reboot takes effect and cycles through before Kies, ODIN or anything else can take hold of the device.
I have tried the cable trick, Recovery Mode is a no go and it would appear to be an issue with CWM mismatch which is causing the reboot.
Hoping that a local "phone hacker" can help me out with a JTAG reboot this weekend but I am not overly optimistic.
Thanks again.
I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!
try installing kies odin wouldnt see my phone until i installed it
Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.
okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.
If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?
rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....
Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!
I customized a Samsung Galaxy Appeal phone, installing
root, clockworkmod 5.0.2.8 and busybox, using Odin (source:
Area51) some time ago.
Recently I decided to erase /dalvik_cache (thru recovery), as
this sounded harmless and I thought it might free-up some
space from orphaned apps.
Ever since then, I've been stuck at the CWM recovery menu - no
matter what erasing, re-flashing, rebooting, removing battery etc. I do, I always
end up at the recovery page. I've tried various remedies
suggested for 'boot-loops' and the like, including
'fix_permissions'. Maybe I haven't done the exactly-needed steps
in the exactly-correct order.
I have even 'successfully' restored from an earlier nandroid,
and also tried to re-install the original customization, which came close to working, but I still
end up at the recovery page. I haven't tried adb/fastboot yet because the 'quick-downloads' won't download.
Is something that needs to be erased, not getting erased?
One possible clue is the show-log: it appears to be very short,
ending after the 'missing extended_commands' line.
tfj said:
I customized a Samsung Galaxy Appeal phone, installing
root, clockworkmod 5.0.2.8 and busybox, using Odin (source:
Area51) some time ago.
Recently I decided to erase /dalvik_cache (thru recovery), as
this sounded harmless and I thought it might free-up some
space from orphaned apps.
Ever since then, I've been stuck at the CWM recovery menu - no
matter what erasing, re-flashing, rebooting, removing battery etc. I do, I always
end up at the recovery page. I've tried various remedies
suggested for 'boot-loops' and the like, including
'fix_permissions'. Maybe I haven't done the exactly-needed steps
in the exactly-correct order.
I have even 'successfully' restored from an earlier nandroid,
and also tried to re-install the original customization, which came close to working, but I still
end up at the recovery page. I haven't tried adb/fastboot yet because the 'quick-downloads' won't download.
Is something that needs to be erased, not getting erased?
One possible clue is the show-log: it appears to be very short,
ending after the 'missing extended_commands' line.
Click to expand...
Click to collapse
Just flash the stock firmware via ODIN. Once done you can switch to a custom rom again.
SamMobile.com provides the needed firmware.
LS.xD said:
Just flash the stock firmware via ODIN. Once done you can switch to a custom rom again.
SamMobile.com provides the needed firmware.
Click to expand...
Click to collapse
Apparently, sammobile doesn't have it - it lists it, but but it's not available.
Also, neither adb nor fastboot can find the device (which is always in active CWM menu mode).
Update: adb (but not fastboot) now sees the device (as "recovery"); will experiment
tfj said:
Apparently, sammobile doesn't have it - it lists it, but but it's not available.
Also, neither adb nor fastboot can find the device (which is always in active CWM menu mode).
Update: adb (but not fastboot) now sees the device (as "recovery"); will experiment
Click to expand...
Click to collapse
Samsung phones do not provide a fastboot mode but the download mode.
Which firmware do you need?
LS.xD said:
Samsung phones do not provide a fastboot mode but the download mode.
Which firmware do you need?
Click to expand...
Click to collapse
I'm not sure what you're asking; the phone is a galaxy appeal sgh-i827.
Can you suggest what I can check using adb? There are a large number of shell commands available in /sbin and /system/bin,sbin,xbin. <bugreport> fails, apparently because dalvik is missing something.
tfj said:
I'm not sure what you're asking; the phone is a galaxy appeal sgh-i827.
Can you suggest what I can check using adb? There are a large number of shell commands available in /sbin and /system/bin,sbin,xbin. <bugreport> fails, apparently because dalvik is missing something.
Click to expand...
Click to collapse
Have you any rom you can flash to the phone?
LS.xD said:
Have you any rom you can flash to the phone?
Click to expand...
Click to collapse
I believe AndroidArea51 has a rooted, but otherwise stock, ROM.
I'm doing this at a public library, and would appreciate any tips
about how to download large files - are there Download
Managers - whether online, or Browser add-ons, or Android apps
(downloading to a phone over wifi would be convenient) - that can resume a download precisely, after 2 weeks of complete dis-connection (including reboots)?
SOLVED:
... I'm back ... (boy, that took a long time).
A near-stock ROM for the Samsung Appeal (I think it's rooted) was available at the AndroidArea51 website (try different links; one - 'code.google'? - worked for me). It's 250 MB.
Once I had the ROM in hand, Odin fixed things in a flash.
In fact, on pressing Odin's 'Start' button, the flashing
took less than 10 seconds - apparently because it only
needed to re-flash the 21-Kb "cache.ext4.tar" file.
The phone was back to normal.
Then, as a test, I again ran the 'Erase Dalvik Cache'
procedure in the phone's custom recovery, and once
again, this put the Appeal into a semi-bricked state
(and was easily fixed with Odin).
So, the lesson here is, if you hear that erasing
'cache files' is perfectly harmless, that may not
apply to the Dalvik-cache; that'll need re-flashing.
Here are the steps I used to recover from a Dalvik-cache
erasure on the Samsung Appeal, using Odin3 v1.85:
====================================================
Install the Samsung USB-drivers for the Appeal
It's possible the phone's 'usb-developer' mode and/or
'unknown-sources' mode need to be on (in a semi-bricked
state, there's likely nothing you can do about this).
Turn off the phone.
Put the Appeal into Download mode:
Hold power and volume-down buttons until the phone
vibrates (about 2 seconds); immediately release buttons.
Read warning and follow instructions on phone's screen to get
into Download mode, or not (to back out of Download mode,
assuming you *aren't* in the middle of downloading anything,
press the power button down for about ten seconds, the phone
will vibrate and then (attempt to) re-boot).
Execute the Odin program; a 'box-screen' displays.
Plug the phone into a USB port; in Odin's screen, the
"ID:COM" box should fill-in with color and a number.
This means Odin has recognized your device.
In the Odin screen, the default 'AutoReboot' and 'F.ResetTime' options are the only ones selected.
Unzip the Romfile, in some easy-to-find folder.
The enclosed file that's needed is "cache.ext4.tar"
(and any files with nearly-identical names, like "cache.ext4.tar.a")
Press Odin's "PDA" button (*not* the "PHONE" button! - that
ought to be renamed "RADIO") and browse the filesystem until the
"cache.ext4.tar" file is listed.
Press Odin's start button.
... Success.
Hi,
Apologies if this has been asked before, but I've done a relatively thorough search and I can't find a solution to this problem.
I have an S6 (SM-G920F), It was playing up for a few weeks before this, not charging well, and what not, thought it was a cable/hardware issue. Then it stopped working entirely. Initially when it was plugged into the wall it would say it was 91% charged, but if you tried to turn it on it would turn off, and reboot into the charging screen.
I've done quite alot of reading and I've ended up flashing it with Odin (I have a single .md5 file, which i've loaded onto the phone via AP) using the most recent FIrmware UK EE for the SM-G20F. This was successful, however now it only loads the Black screen with white text Samsung S6 powered by android screen and then goes blank and back to the white text screen.
I downloaded an alternative firmware (the one previous version), but this has had the same effect. I've tried to repartition with odin, but this fails.
1.) Is there anyway I can fix this?
2.) If not Is there anyway to remove files whilst in downlod mode?
3.) If I cannot fix it or recover my data, is there anyway to wipe the data securely from my phone so I can sell it for parts?
At present, I can't access recovery mode, only download mode. But whilst Odin communicates with the phone in download mode, I can't seem to access my files from explorer?
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
King-V said:
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
Click to expand...
Click to collapse
Thanks for your reply! So after flashing it goes straight back into the boot loop. Weirdly if its plugged into my laptop it spend about a second or two on the "Samsung Galaxy S6: Powered by Android" screen before plunging into darkness and shortly after repeating the same message. However if I plug it into the wall it spend over twice as long on that screen before repeating the cycle. It never goes any further.
I've tried your suggestion about perhaps its timing for recovery mode, but even if I go straight from cancelling download mode to trying the power, up and home key it doesn't go to recovery. I've tried a variety of timings both plugged into my laptop and plugged into the wall to no avail. If the phone isn't plugged in, it literally won't do anything whatsoever, won't even hint at turning on.
So Next I tried flashing it with TWRP via Odin and nothings changed, exactly the same bootloop and I still can't get into recovery mode.
I'm starting to think that sadly this phone my be beyond repair! Thanks for your help though, much appreciated.
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
vinicius_guerra said:
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
Click to expand...
Click to collapse
Hi Vinicius,
Thanks for the suggestion. Unfortunately it didn't work, I even tried flashing it back to a standard ROM from TWRP, but it still didn't do anything, just back to the Samsung logo and the loop continues ever more!
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Melioetta Zyguard said:
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Click to expand...
Click to collapse
Same experience. For all those 6 years that I used this device, the wifi was okay until now. It (wifi) is very buggy (turning on and off, and sometimes won't turn on at all) so I restarted the device, then bootloop happens. I flashed the stock rom via odin and clear data and cache. But it is still bootlooping. I think this is the sign that I need to replace my phone IF I couldn't find a fix to this.