So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
So during fastboot, the screen actually doesn't go black. I am still able to remain communication and That is when I tried flashing the factory image. How do you make sure that the checksum is correct? I didn't receive any errors during the flash indicating that it didn't flash properly.
If you're using Windows, Hashtab is a good, free checksum program with a GUI.
Download
Info/Review
On Google's image download page, copy the SHA-256 listed, and compare it to what you have locally (which you used to flash onto your phone).
how to boot into twrp? almost the same issue to you, adb cant find my phone.
jcd173339 said:
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
Click to expand...
Click to collapse
bush911 said:
how to boot into twrp? almost the same issue to you, adb cant find my phone.
Click to expand...
Click to collapse
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
It looks like your freezer method works. Putting it in the freezer actually gets the phone to boot completely into google's factory image. its usuable for about a minute until the problem of freezing and turning off reoccurs. It feels like the phone warms up while running so maybe i have a hardware problem rather than software.
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
thank you sir, I have twrp installed previously. but the screen doesnt turn on so I can't choose the recovery model. and try to hold the power button for a while the phone will become warm. no other response:crying:
jcd173339 said:
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
Click to expand...
Click to collapse
Thufail19 said:
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
Click to expand...
Click to collapse
Maybe try locking the bootloader? I might try to do that since you and i both are experiencing the same problem with an unlocked bootloader. But i can't see why that would impact anything.
Related
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.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
After 8 years of tinkering with Android phones I have no clue how this happened.
PIXEL 2 (Walleye, non-xl)
Tried getting TWRP and ElementalX working but either one or both weren't doing there thing, though I could at least boot and use my phone normally. Finally ended in a situation where I couldn't boot passed fastboot with an error at the bottom "ERROR: LoadImageAndAuth Failed: Load Error". Found a fix that said to change the active partition. Set it to b and that worked and surprise it loads TWRP...so somehow TWRP was installed, but I can't actually load Android.
Grabbed the latest factory image and manually flashed all the files in the zip-within-the-zip. Everything flashed with no hiccups so I rebooted to bootloader with the intention to then reboot the system, and now this is happening:
TLDR Phone won't turn on. Holding PWR+VolDown SEEMS to do nothing, but it actually flashes a line on the screen like it's trying to load something for a milisecond, then does nothing. Holding PWR+VolUp does nothing. Holding PWR+VolUp+VolDown does the same screen flash followed by the notification LED blinking red 2 or 3 times. Please help!
EDIT: if it matters, the phone is about 50% battery and currently still on judging purely by the fact that it's been warm for about an hour.
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices? If it shows in devices, can you run platform-tools and see if it shows up via fastboot devices with an ID? If you can connect to fastboot, you could attempt to flash images that way.
djer34 said:
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices?
Click to expand...
Click to collapse
Nothing happens if I plug into the computer, no sound and not listed in devices. Plugging it in to the charger does nothing except possibly charges it, but I wouldn't know because the screen doesn't seem to be able to turn on for more than a milisecond of a flash.
I had this same problem when I flashed Elemental X kernel over top of the flash kernel and all I did was use the flash-all script that is included with the system image from google. This got me back to my OS where I flashed elemental and magisk. Do you have insurance through your provider?
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
try charging the phone for a few hours
se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.
sounds like u need a new battery
ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.
@bmark240
help please
se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.
kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os
THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.
i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.
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.