I tried to recover my phone with Pete's Motorola Tools. I did all the process and says was succesful but after the las reboot now my phone keeps rebooting on the red eye and do nothing. What can I do? Should I had bricked my phone?
Let is sit for at least 5 minutes then if it continues it is bricked. There is a topic on here with sbf files to restore your phone. DO NOT LET YOUR BATTERY DRAIN, IT WILL MAKE THE ISSUE ALOT WORSE.
If you do accidentally let it drain all the way, refer to THIS thread
May thanks! I just recovered with another solution. God I was sweating a lot! But finally get my phone back to normal
Related
Hi everyone,
I have a problematic Nexus One. I've googled the issue and read all the corresponding threads and none of them seem to have boot loop issues as bad as mine. At least I dont think so, anyway.
Where should I start? I recently bought the phone off ebay. The seller did clearly state the phone's issues and that he couldn't be bothered fixing it, let alone paying over $200 to send it back to Google to be repaired or replaced (from Australia). Call me a sucker for punishment, but I do like dabbling in electronics so I thought I'd give this a go and hopefully will be successful. It wouldn't bother me if it rebooted once every few days then rebooted again normally but this isn't the case. I'll try to describe it's behaviour as precisely as I an and I sincerely hope the collective expertise on this forum will be able to help me successfully resolve this issue. BTW, I've been using a gorgeous Desire since July.
The Nexus one is running Modaco r21, 4.06.00.12_7 radio, 2.6.32.9 kernel, CMR 2.5.1.0.
1. When the phone has been powered down for at least 5 mins, it will power up as normal. If left alone on the bench or very lightly used ie a few minutes, then pwr button sleep, no problem. If I continue 'sleeping' the phone every few minutes while using it it continues to function normally for a few hours. If I don't 'sleep' the phone and use it continuously, then after about 20 mins it goes into a reboot cycle with the static 'X' going on and off every few seconds then ending up with the continuously on "X" with the unlocked padlock underneath, which is unrecoverable until the battery is pulled.
2. Battery reinserted immediately after removal and the reboot cycle continues. I can boot into the white Recovery or Fastboot sreens but when I select an action like Recovery, the boot loops starts again. Battery pulled and reinserted again, boot loop occurs again. Pull battery and leave it out or powered down with battery inserted for 5 mins, reboots normally. Then point '1' above continues.
3. I have Rom Manager, Titanium and Superuser Permissions installed. I received the phone with Eclair installed and after many attempts managed to install the new radio and Modaco R21. Last night I tried doing a back up via Rom Manager since I cant get into the black Recovery screen and now Titanium and SU are force closing.
This is all I can think of right now and will update with more info as they come to light. I've been trying to install setcpu to see if underclocking will help however I have been unsuccessful due to SU force closing. I am an Android and Linux noob but am always willing to learn. I really would like to get more stability in this phone so I can either use it as my primary or back up.
Thanks in advance for all your help.
Edit. I magaed to do a factory reset when it dont momentarily allow me into Recovery mode. Wiped all data and davlic as well.
My first instinct is that the phone has suffered or is suffering from a heat problem of some type.
Do you have the android SDK set up on your computer? You should be able to flash an aftermarket recovery using the "fastboot flash" commands. You could also use the "adb reboot recovery" command to reboot the phone directly into recovery mode.
I'll give your suggestions a try. What fastboot commands should I be entering? I am an absolute virgin with all this.
Sent from my HTC Desire using XDA App
I think this thread should have some good information for you
Thanks for the link, mate. I'll have a read and I'm sure there'll be more Q's soon.
Sent from my HTC Desire using XDA App
Hi again,
I've installed Android SDK and usb drivers. Where do I go from there? I am a complete newbie at this so please be kind.
julian.kueh i was posting to ask how things have been progressing along this matter?
I got the same problem. No matter what I do, I can get into Recovery. It stay in loop with X
I change twice recover and nothing.
Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!
LiquidArrogance said:
Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!
Click to expand...
Click to collapse
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.
muniz_ri said:
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.
Click to expand...
Click to collapse
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop
Is there physical damage on the phone, thus why att didn't do the warranty?
Sent from my HTC One_M8 using Tapatalk
LiquidArrogance said:
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop
Click to expand...
Click to collapse
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck
muniz_ri said:
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck
Click to expand...
Click to collapse
No idea what just happened. I've been messing around throwing the kernel you recommended at it as well as the stock partitions. Kept getting back to boot loop but at one point it stuck out, said it was upgrading, optimizing apps, and now it's running. So weird.
I'm way too scared to do the factory reset at this point, though.
Thank you again for your help, I really appreciate it!
Edit: Unplugged the USB cable and it immediately shut off and went back into boot loop. Wow.
this sounds like a hardware problem.. i sent my phone to Samsung and they actually repaired it, it was the pba board, i had the same problem.. i flashed everything it needed to recover from a bootloop. and sometimes it would become non responsive. go to best buy and see what they tell you.
Sent from my UNROOTED SAMSUNG-SM-G900A on OF2
Update:
Thanks to everyone for their replies. I was able to get the phone to boot thanks to everyone's help. Did this by flashing kernel then partitions which would allow the phone to boot.
I finally figured out that the phone would only boot if plugged directly into a power source. As soon as I disconnected the power cable, it would send it right back into the boot loop. I ran some battery "repair" and "calibration" tools but these did not fix the issue. Whenever I would run a battery drain tool, the stress on the battery would cause the phone to shut down.
All of this led me to believe it was an issue with the battery. I held my wife's S4 battery to the contacts on the S5, and it works just fine, even disconnected, and even with the stress test on the battery.
SO -- I'm going to buy a new battery and see if this fixes my problems. I think I just had the perfect storm of battery issues coupled with firmware problems.
I'm pretty sure I know what caused the battery to go haywire. I work in a max security prison and have to leave my phone in the car all day. Outside temperatures regularly hit 105F+ during the summer, so who knows how hot it's getting in the car. Obviously I always leave the phone turned off, but I suspect the high temperatures caused the damage.
Going to try to find a new battery today. Will keep everyone posted! Thank you again for all of the replies.
I had the same issue and would just like to thank you for the files! They helped me unbrick my phone! Much appreciated.
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
AntonJart said:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
Click to expand...
Click to collapse
I saw that thread, but most of those people started having the issue after the update. If the kit kat update fixes it then i'm at a loss. And since a new board fixed the issue for you that means most likely the the memory is beginning to fail. That's how SSDs die anyway.
tempy1 said:
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
Click to expand...
Click to collapse
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
tempy1 said:
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
Click to expand...
Click to collapse
Without battery in freezer.
No idea how it works but good thing is hopefully it will work cuz lot of users even recover their hard bricked devices by this.
As you said you have nothing to lose so give it a try and make sure be patient dont give up and do this when you have enough time to do at least couple of hours.
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
keithwwalker said:
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
Click to expand...
Click to collapse
so wait the freezer thing was not even a permanent fix?
No, the freezer sometimes helps you get a bricked device so that it turns on. It doesn't fix thermal issues. I believe it helps some electrical connection that has broken come into contact again.
I can't go to download mode or recovery. I tried both ways But there is no way to use my device.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
So i recently had a baby, thus i had no time at all to get my phone to work. WakeLock app was working alright.
But last night the phone just died. all attempts to revive failed. I left it in the freezer until the morning and it booted up but quickly locked up after about 5 minutes of use and became unresponsive.
I tried your method.
I failed right away. Modem could not be written..
I tried flashing the pit files like i did previously and that failed as well.
Any suggestions are appreciated. I am phoneless
EDIT#2: After I left the phone in the freezer for longer (3 hours). The odin firmware update went through !!!! This furtherst i've gone so far.
I went into recovery and did everything you said.
BUT now i have Kernel Panic Upload Mode on my screen with a little green android
EDit#3 few battery pulls later. And an over 15 minute wait time on the android logo and then about the same on the t-mobile logo i got into the OS. I did the OTA update, the phone heated up and a few restarts later it froze up like it did previously
Back to square 1
EDIT: THIS helped for a few days
https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335
Day 2: and all went back to the phone not waking up and after screen is turned off
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
your phone partition got messed up you have to put TWRP back and then go in wipe and then you have to do file repairwhen you fix file then ran back the stock firmware which will fix bootloader
then go back install twrp and install custom rom with root
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
once you fix file then do the format within twrp
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
there is the list of stock firmware try them see which one works with twrp, you have to install twrp first so you can fix the problem using repair files in twrp
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/
also read this for installing twrp on 910t
https://forum.xda-developers.com/no...nt/tool-utility-twrp-2-8-1-0-teamwin-t2915588
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
Befour flashing twrp make sure you uncheck Auto reboot....when it's done flashing pull your battery, put it back in the phone but don't power on....you want to boot right into recovery......then twrp will stick
Hi all.
So yesterday, I flashed a modified version of the eRecovery and tried upgrading, but upon reboot my device goes into error mode and I think it might be hard bricked.
There's no fastboot. eRecovery, dload method doesn't work and I can't switch it off either because it always goes into error mode upon reboot. Luckily I've opened up my device and unplugged the battery to prevent it from draining.
Is there any hope of flashing back to stock? ANY help would be appreciated!
9bestenbier said:
Hi all.
So yesterday, I flashed a modified version of the eRecovery and tried upgrading, but upon reboot my device goes into error mode and I think it might be hard bricked.
There's no fastboot. eRecovery, dload method doesn't work and I can't switch it off either because it always goes into error mode upon reboot. Luckily I've opened up my device and unplugged the battery to prevent it from draining.
Is there any hope of flashing back to stock? ANY help would be appreciated!
Click to expand...
Click to collapse
Put the battery back in place and turn the phone on until battery drains. Then, connect it to the PC while pressing the volume button to access fastboot and reflash twrp. Good luck!
CarlosAG10 said:
Put the battery back in place and turn the phone on until battery drains. Then, connect it to the PC while pressing the volume button to access fastboot and reflash twrp. Good luck!
Click to expand...
Click to collapse
I've actually thought of that so I plugged the battery in again and switched on the phone and let it go into error mode. It'll probably take several hours for it to drain because it was around 60% before I bricked it. So I'll let it drain and see if something happens when I reconnect it. Hopefully it'll go to fastboot. If not, I'll probably have to save up for something new. But I'll try a few more times to see if I can unbrick my device.
9bestenbier said:
I've actually thought of that so I plugged the battery in again and switched on the phone and let it go into error mode. It'll probably take several hours for it to drain because it was around 60% before I bricked it. So I'll let it drain and see if something happens when I reconnect it. Hopefully it'll go to fastboot. If not, I'll probably have to save up for something new. But I'll try a few more times to see if I can unbrick my device.
Click to expand...
Click to collapse
Hi,
If your bootloader partition is safe, and that should be the case, then you will always be able to fix your phone. Just a matter of time/attempts.
Good luck ?