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.
hello xda. i need your help. im desperate. i dont know what else to do with my moto g here's what happened:
first of all, i dropped my moto g into the water.
right after i got it out, it startet bootlooping. then it turned off by itself after almost an hour had passed.
i put it in a bag full of rice for the rest of the night and almost the whole following day. then i plugged it into the wall charger, and it wouldnt charge at all. the only sign of life was the blinking led.
so i took it to Movistar-Peru for repair, and told me the obvious: water damage was not covered in the warranty, then my phone was returned to me.
so i decided to tear it down by myself.
everything was looking fine. the water indicators were red, but everything was clean except for the battery socket: there was mineral condensation around it. i wiped it out, cleaned it away and then the phone would actually charge the battery icon displayed normally.
so i let it charge for 3 hours and after it was completely charged i turned it on. just to run into a black screen after the bootnimation.
good news is it actually can boot into fastboot mode and can access recovery menu.
i did some research here, and seemed like my phone needed a full stock flash (that´s what i thought). i decided to unlock the bootloader, using motorola unique code. (i thought it may be needed for flashing, but it seems it is not necessary)
in recovery, my sdcard folders display normally, i can wipe data/factory reset it normally, BUT when i try to erase cache partition, the phone reboots.
so i started flashing my device through fastboot. i should mention that before i dropped it into the water, i had installed 4.4.2 ota update. but whenever i tried to flash a 4.4.2 rom, i got hab check failed for sysyem, for recovery and sometimes for boot.
now, i've tried several official motorola signed jelly bean roms (nextel br, movistar sp, claro ar, etc etc) including original Movistar Pe jb rom (which ive already flashed uncountable times) with no errors on flashing, but neither of them got me passed the black screen after bootanimation. (the phone is not off, cause the backlight remains on). the only way of getting out of it is rebooting into fastboot mode again (volume- and power).
i've also tried relocking the bootloader, and the process gives me no errors (the word "locked" displays by the end, though the phone then reboots into the "warning bl unlcked" screen) , but regardless of that and the relocking process turning out okay, status code 3 is displayed in menu, meaning the bl wasnt really relocked..?)
in short:
-dropped into water, started bootloop, then it turned itself off.
-next day it would display black screen after bootnimation, no matter what i did.
-if i choose wipe cache partition, the phone reboots.
-i've flashed it "sucsessfully" several times, still runs into a black screen after bootnimation.
-i've unlocked the boootloader
-if i try to reclock: process turns out okay("locked" word by the end), but status code remains being 3.
-i dont care about backups, i had nothing important in my phone (gdrive ftw)
my concearns are:
-possible hardware unrepairable damage
-bootloader got corrupted
-mineral condensation is still there deep inside the components
-maybe gpu? emmc corrupted? semi brick? idk..
my questions are:
-what can i do from now?
-i've read that a new bootloader can be flashed into the phone. risk of bricking my phone?
-if the bootloader is the problem, flashing a new one would solve it?
-in general, what am i doing wrong in all of this? has my phone any chance of functioning normally, at all?
please help me , i miss my phone, i got it for christmas, it is my first smartphone and i woudl like to bring it back to life if possible. thank you for reading.
I can help!
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Thank you for replying to my problem
i have already done your steps uncountable times.
every time i try to wipe cache, the phone reboots. it does not wipe anything at all, it just instantly reboots. then bootanimation, then black screen again, but nothing happens. not even after 2 minutes, after 5 or 10. nothing. just black screen until battery drains completely from continously powering the backlight. do you think maybe the water hardware-bricked my phone? also, im ocassionally getting blue screens out of a sudden, then the phone powers itself off.
Ah, ok, sorry my suggestion didn't help. I had exactly the same problem, so surprised this didn't help you. After being dropped in water, all I got was a black screen after the initial start animation. I don't really know much about phones tbh, I just managed to fix mine through trial and error. My girlfriends phone was initially sent to a shop for repair, and although the guy couldn't fix it, he said there was no signs of water damage. Not really sure then why the phone stopped working, but the method I suggested did work for me. I don't think there was anything else I tried. It's worth mentioning maybe that it took 6 weeks before I could fix the phone. Maybe it took that long to fully dry out? Straight after the accident though the phone was put in a bowl of rice for days so it should have been dried pretty quick. Don't really know what else to suggest, sorry I couldn't be more help. Have faith though, I reckon it'll come back to life soon
thank you for posting a reply and thank you for your advice. i appreciatte the attention given. i will further try some other methods in hope of a solution.
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
Click to expand...
Click to collapse
are you sure it has nothing to do with the bootloader? now that you mention this.. can a 4.4.2 bl load a 4.3 rom successfully? and moreover, if i flash another bl, it will overwrite my original one right? is there eny problem on that? i am asking because no matter what i do, regardless of the "locked!" message, the menu keeps showing code status 3.
what happens if i flash the recovery and cant mount or flash any rom? or if the black screen persist after that?
and i wish i had known the rice trick before, cause i kept the bag closed for almost a day :s
grahameaddicott said:
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Click to expand...
Click to collapse
It worked for me, Thanks
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Click to expand...
Click to collapse
ok i did what you said, i tried to flash cwm and fastboot presented no problems, (output is "okay"), but un the phone screen there's a message "mismatched partition size (recovery)", and when i enter recovery, it boots normal STOCK recovery!! i donw know whats happening. i renamed the cwm image to cwm.img and typed in these commands:
fastboot erase recovery
fastboot flash recovery cwm.img
then i clicked recovery option in the bootloader menu... but it booted into stock recovery!! this is so confusing
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
thank you i will proceed to try what you said. though i have a question: is it possible for the bootloader to be overwritten with a previous version?
and what does it mean when the phone outputs "hab check failed for boot/recovery/system (etc)" ? i sometimes get those errors when flashing other region (official) roms
liveroy said:
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
Click to expand...
Click to collapse
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
tenjou_89 said:
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
Click to expand...
Click to collapse
Hmm, maybe leave the recovery aside for now and try to boot a 4.3 ROM (stock one).
Also you cannot downgrade to bootloader afaik, but the newer ones work fine with 4.3 ROMs.
I don't think that the eMMC got damaged, cos nothing will work then.I really can't say if your problems are coming from the water dip or it's just the Moto G being stubborn if you do even one thing the wrong way.
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
what about the ram? a guy on some other forum said that maybe the ram got damaged to a point where only a part of it is now writable, and it gets flooded just before the complete boot up of the system, wichi is why the phone would then crash and display a black screen. what do you think about that theory?
i am going to try with 4.3 roms now. oficial and custom and post the results.
liveroy said:
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
Click to expand...
Click to collapse
yes, exactly that way.
edit: except i have images instead of bins, so:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot bootloader
Typo of mine, should be .img
About that RAM theory, it really doesn't sound viable to me, but who knows.
If I have to guess, I would say it's probably some crucial component failing to initialize properly and the kernel halts the system.
hmmm do you know of a method of checking for the conditions of individual hardware componets through a pc? like probing or running a full check of everything, not just the emmc..?
These seem not to work.
But if you find the correct details, maybe there is something to test in the service menu.
I have the same problem without water damage. I guess its the 4.4 OTA bug.
Tried reflashing the firmware i already have but of no use.
Mine shows the Blue Motorola logo and then doesn't show the boot animation.
Please can anyone help me out :'(
So I've had my htc one s for about 2 years or so now and this problem has started happening rather recently. No matter what I try, I cannot access the recovery menu.
I've tried:
1.Hardware Keys (Going into bootloader and trying the recovery from there) = no go.
2.App that would allow me to reboot to recovery = no go
3.Installing another recovery to see if that would help = no go
I've also tried the method of erasing the cache through fastboot to no avail.
I'm currently running a really outdated version of cyanogenmod (10.1 i believe) and my phone is now currently stuck at the beginning trying to boot up.
I'm not sure what else I can try. Oh and another thing. It seems like when I tried to install another recovery image, it didn't overwrite what was already there and so now I believe that my phone currently has to recovery menus.
I've already searched through the forums looking for help and while some of the threads that I found came close, none of them except for the erasing of the cache one came close to helping me figure out what was going on.
Please help.
Macrophage001 said:
So I've had my htc one s for about 2 years or so now and this problem has started happening rather recently. No matter what I try, I cannot access the recovery menu.
I've tried:
1.Hardware Keys (Going into bootloader and trying the recovery from there) = no go.
2.App that would allow me to reboot to recovery = no go
3.Installing another recovery to see if that would help = no go
I've also tried the method of erasing the cache through fastboot to no avail.
I'm currently running a really outdated version of cyanogenmod (10.1 i believe) and my phone is now currently stuck at the beginning trying to boot up.
I'm not sure what else I can try. Oh and another thing. It seems like when I tried to install another recovery image, it didn't overwrite what was already there and so now I believe that my phone currently has to recovery menus.
I've already searched through the forums looking for help and while some of the threads that I found came close, none of them except for the erasing of the cache one came close to helping me figure out what was going on.
Please help.
Click to expand...
Click to collapse
You can get into bootloader, so just relock it and run an RUU.
Then you can go through the steps of unlocking, installing a recovery and ROM again.
tivofool said:
You can get into bootloader, so just relock it and run an RUU.
Then you can go through the steps of unlocking, installing a recovery and ROM again.
Click to expand...
Click to collapse
Ah ok, I'm going to try that. The problem now is that my phone won't boot up and my volume down button doesn't work. It just stays at the portion of boot up with the cyanogenmod logo. I guess my only option now is wait until my phone dies for it to turn off since it won't stay off by simply shutting it down.
Macrophage001 said:
Ah ok, I'm going to try that. The problem now is that my phone won't boot up and my volume down button doesn't work. It just stays at the portion of boot up with the cyanogenmod logo. I guess my only option now is wait until my phone dies for it to turn off since it won't stay off by simply shutting it down.
Click to expand...
Click to collapse
If you mean your volume down is physically broken, then yikes you might be in trouble. Might have to watch a video on youtube to learn to take it apart and fix/clean the rocker contact.
If you mean it isn't working because of the boot loop, ok. If you hold power down for like 10 seconds it should reset and then you hold down volume down to get to bootloader.
tivofool said:
If you mean your volume down is physically broken, then yikes you might be in trouble. Might have to watch a video on youtube to learn to take it apart and fix/clean the rocker contact.
If you mean it isn't working because of the boot loop, ok. If you hold power down for like 10 seconds it should reset and then you hold down volume down to get to bootloader.
Click to expand...
Click to collapse
Yeah I meant it's actually physically broken. I was hoping that wouldn't be the case but it seems like I'm going to have to find out how to take my phone apart.
Thanks for the help.
So I decided to upgrade to the Android P beta DP3 right from stock (most recent version) and all went seemingly well. I downloaded the ROM, installed it with the local upgrade, pressed the restart button that appeared (instead of manually shutting it down) and booted right into P.
I noticed that everything was still installed, and I'd rather start fresh, so I booted to recovery and selected the wipe data option, which removes all userdata, as suggested in the official installation guide.
After wiping I booted back into Android and got the normal popup to enter my pin, accept license agreement and accept/decline a bunch of things like notification offer and stuff. After this, however, I end up in the 'Checking for updates...' screen which is taking ages (25+ minutes) and never seems to finish.
At this point I don't really know what to do. I've tried both wifi and though the mobile network, neither seem to work. There also isn't a skip button or anything as far as I can see.
Given that all data is wiped debugging also isn't enabled so adb appears to be out of the question. Booting into recovery also doesn't appear to work, as I always end up just starting Android. And last but not least the bootloader was still locked as this wasn't needed for the P beta.
I've tried making a thread on the official OnePlus forums, but it seems I'm still lacking in rep over there.
Any suggestions?
and i m pretty sure before trying that u should have atleast enabled oem unlock just to be safe T_T
Yup, I guess so too. Ah well, I posted the issue in multiple places, including as a bug report on the OnePlus forums. I'll just wait a few more days to see if anyone has an idea and otherwise I'll send it back for repairs and see if they can do something.
Hi,
reboot into Recovery and wipe data.
After a further reboot follow the setup wizard to the point where you can login to your Google Acc. Skip everything from this point on and you will get to the Homescreen. Wait a couple of minutes an you will be asked to finish the setup wizard.
I always have this annoying bug, too...
Thanks for the suggestion. Unfortunately I can't seem to boot into recovery anymore. No matter what I do, no matter the order of volume down+power (volume first then power, power first then volume, or pressing them exactly at the same time), nothing seems to actually get me into recovery. In each and every case it just boots straight to the Android setup. It also doesn't appear that I'm doing anything wrong, because I've got a few older Android phones here and on each one of them I can easily get into recovery.
I've also made an official bug report, so lets see how that pans out. But if anyone has any other suggestions in the meantime, I'm all ears.
Xylon- said:
Thanks for the suggestion. Unfortunately I can't seem to boot into recovery anymore. No matter what I do, no matter the order of volume down+power (volume first then power, power first then volume, or pressing them exactly at the same time), nothing seems to actually get me into recovery. In each and every case it just boots straight to the Android setup. It also doesn't appear that I'm doing anything wrong, because I've got a few older Android phones here and on each one of them I can easily get into recovery.
I've also made an official bug report, so lets see how that pans out. But if anyone has any other suggestions in the meantime, I'm all ears.
Click to expand...
Click to collapse
U have corrupted u r data partition. You have to flash fastboot flashable rom via fastboot mode but u will loose u r all internal data too.
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
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.