This probably happened to many people before, but I can't find a similar situation on xda or any android forums for that matter that was solved..
I have a Nexus S i9020a running an AOSP strawberry rom (http://forum.xda-developers.com/showthread.php?t=1843301), I wanted to flash miui rom so I booted back into recovery, backed up the rom, wiped data, cache, dalvik, system then installed the zip and rebooted (install was very quick so I suspect the zip might have been damaged but I'm not quite sure of it)
After install and reboot phone is stuck on google logo. I can boot into fastboot but I cant do anything from there, the volume buttons don't seem to work in it (I can't navigate to recovery or any option), and my power button is broken for about a month now so that's useless. I can boot into fastboot by unplugging the battery, plugging again, then holding volume up while inserting micro usb cable which will power the phone on.
I can't get the pc to recognize the phone using adb or fastboot devices, it says no devices detected, and when I try any command it says waiting for device and nothing happens. I have all the drivers installed and I use fastboot and adb almost everyday so I know they work.
Anyone experienced something similar or has a solution?
Responses much appreciated.
Amjad
amjadfirst said:
This probably happened to many people before, but I can't find a similar situation on xda or any android forums for that matter that was solved..
I have a Nexus S i9020a running an AOSP strawberry rom (http://forum.xda-developers.com/showthread.php?t=1843301), I wanted to flash miui rom so I booted back into recovery, backed up the rom, wiped data, cache, dalvik, system then installed the zip and rebooted (install was very quick so I suspect the zip might have been damaged but I'm not quite sure of it)
After install and reboot phone is stuck on google logo. I can boot into fastboot but I cant do anything from there, the volume buttons don't seem to work in it (I can't navigate to recovery or any option), and my power button is broken for about a month now so that's useless. I can boot into fastboot by unplugging the battery, plugging again, then holding volume up while inserting micro usb cable which will power the phone on.
I can't get the pc to recognize the phone using adb or fastboot devices, it says no devices detected, and when I try any command it says waiting for device and nothing happens. I have all the drivers installed and I use fastboot and adb almost everyday so I know they work.
Anyone experienced something similar or has a solution?
Responses much appreciated.
Amjad
Click to expand...
Click to collapse
It's a known problem that you won't be able to scroll in fastboot when your power button is broken. It's because the power button is stuck as "enabled". I don't think there's really an easy solution other than "unfreezing" the power button by fixing it yourself or getting it fixed.
Yea after a bit more of research I think fixing the power button is the only solution.. the only problem with that is that it seems it'll cost more than the phone is worth these days
amjadfirst said:
Yea after a bit more of research I think fixing the power button is the only solution.. the only problem with that is that it seems it'll cost more than the phone is worth these days
Click to expand...
Click to collapse
I imagine it depends where you get a quote from. Samsung seems to be very nice on the repairs, unlike some would believe. Might be a good idea to try to get it repaired by them if possible.
Related
My power button is broken so I need to take my phone in to get it replaced. Following the instructions to get it unrooted/return to stock, I need my phone to be recognized in fastboot. It's not happening; I've tried it on three PC's and none of them even see a device connected. It's not even a matter of drivers because when I'm in fastboot it's like nothing is connected at all.
I can't use my volume buttons in fastboot, basicaly I can't do anything at all in fastboot...no volume buttons, no power button and it can't be recognized.
Volume buttons work when phone is turned on. I can do anything I want in recovery or when the phone is up, but in fastboot I can't do anything.
Someone please help!!
By the way, ADB works perfectly but obviously fastboot does not because my PC thinks nothing is connected when fastboot is up on my phone and as I mentioned, my phone is completely unresponsive to anything that I do when I'm in fastboot. I can't use the "volume up/volume down" and tap the power button to get into downloading mode either because MY STUPID POWER BUTTON IS BROKEN!!!
Thank you again in advance....you will be my hero if you can help me with this!!!
forumsid987 said:
My power button is broken so I need to take my phone in to get it replaced. Following the instructions to get it unrooted/return to stock, I need my phone to be recognized in fastboot. It's not happening. I also can't use my volume buttons in fastboot, basicaly I can't do anything at all in fastboot...no volume buttons, no power button and it can't be recognized.
Volume buttons work when phone is turned on.
Someone please help!!
Click to expand...
Click to collapse
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
delete pls , my mistake sry
simms22 said:
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
Click to expand...
Click to collapse
I have tried that so much I think I'm going to break my phone.
I just need someway to return this phone to stock without expecting fastboot to work because it seems like it is unresponsive since the power button is not working. I know this sounds weird as heck but I have all the correct drivers installed but three different computers don't see any kind of usb device connected when the phone is in fastboot. I sincerely believe it's because while in fastboot my messed up powerbutton is screwing it up because it's thinking that the power button is held down the entire time.
If anyone has any ideas on how I can get back to stock please tell me. I have 100% access on my phone when it's in recovery because I can use the buttons at the bottom and I have 100% access when it's fully booted up but when it's in fastboot I can't do anything and no computer even sees a USB device connected to it.
Pleaseeee help!!
forumsid987 said:
I have tried that so much I think I'm going to break my phone.
I just need someway to return this phone to stock without expecting fastboot to work because it seems like it is unresponsive since the power button is not working. I know this sounds weird as heck but I have all the correct drivers installed but three different computers don't see any kind of usb device connected when the phone is in fastboot. I sincerely believe it's because while in fastboot my messed up powerbutton is screwing it up because it's thinking that the power button is held down the entire time.
If anyone has any ideas on how I can get back to stock please tell me. I have 100% access on my phone when it's in recovery because I can use the buttons at the bottom and I have 100% access when it's fully booted up but when it's in fastboot I can't do anything and no computer even sees a USB device connected to it.
Pleaseeee help!!
Click to expand...
Click to collapse
i believe that my phone thinks my power button is always pressed down too, but fastboot works here. my suggestion is that you try a different usb chord. i had an usb chord that i could charge with fine, but nothing else worked. i thought my nexus one was messed up until i tried another usb chord.
simms22 said:
i believe that my phone thinks my power button is always pressed down too, but fastboot works here. my suggestion is that you try a different usb chord. i had an usb chord that i could charge with fine, but nothing else worked. i thought my nexus one was messed up until i tried another usb chord.
Click to expand...
Click to collapse
I tried 3 cords, I'm going crazy here! USB works perfect everywhere but both fastboot and recovery don't let me use my volume or power buttons...at least I can get by in recovery because of the capacitve buttons but I need fastboot to return to stock to get a new phone. I am so frustrated!!!!
forumsid987 said:
I tried 3 cords, I'm going crazy here! USB works perfect everywhere but both fastboot and recovery don't let me use my volume or power buttons...at least I can get by in recovery because of the capacitve buttons but I need fastboot to return to stock to get a new phone. I am so frustrated!!!!
Click to expand...
Click to collapse
have you tried pdanets website? http://junefabrics.com/android/
go there, download the free download and install it to youre computer. its tethering software. but thats not why you should try it. follow the on screen instructions after its installed and itll install the proper latest drivers for your phone. theres a chance your drivers might be out of date.
oh yeah. Used pdanet drivers and Google drivers. No luck with either. I can adb with both but like I said the deicer is not the issue it's that fastboot is totally unresponsive so it looks like nothing is connected to the pc
Sent from my Nexus S 4G using XDA App
anyone have any other options/ideas for me?? It would be greatly appreciated
Find an Odin package. Put phone into download mode by installing battery, holding volume buttons while connected to USB.
Does anyone know if the 301k ohm resistor jig works for ns?
Sent from my Nexus S 4G using xda premium
ODIN doesn't work because of the gosh darn power button being broken.
I went kinda crazy and erased everything in recovery so now all the phone does is boot straight into fast boot. I deleted the boot.img recovery everything, hahahaha (I laugh but really I'm crying inside).
I need a fix ASAP, I'm officially out of a phone.
simms22 said:
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
Click to expand...
Click to collapse
Wow, this actually worked for me Thanks Simms!
I just got stuck in the same situation (http://forum.xda-developers.com/showpost.php?p=22884288&postcount=24) so I kept tapping the back of my phone (with the back cover off). Fastboot kept restarting at first, but then my volume keys started allowing me to change options. I selected recovery and nandroid restored my phone. Now all is well *wipes brow*
Funny thing is, my power button now works properly again (it hasn't been working for the past week)
forumsid987 said:
oh yeah. Used pdanet drivers and Google drivers. No luck with either. I can adb with both but like I said the deicer is not the issue it's that fastboot is totally unresponsive so it looks like nothing is connected to the pc
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
have you found any solution? I have the exact same problem here: powerbutton stucks and no usb-recognition in fastboot (no luck with the tapping either) but no problem with adb in normal mode.
would be great to know if you found a way to deal with this. Thanks!
kajik123 said:
have you found any solution? I have the exact same problem here: powerbutton stucks and no usb-recognition in fastboot (no luck with the tapping either) but no problem with adb in normal mode.
would be great to know if you found a way to deal with this. Thanks!
Click to expand...
Click to collapse
Same problem here.... going crazy since the power button just died on me. I think the device thinks the button is pressed all the time, which makes it a hw issue.. any help to retrieve data on phone would be great!
Having the same problem as the OP...
Pls can someone find us guys a solution.:crying:
Thanks
I had a broken power button and had the same problem. I just sent it back to Samsung with no ROM on it and they fixed the power button and put Gingerbread back on it even though I had voided my warranty by unlocking the bootloader ;')
MistaJae said:
Funny thing is, my power button now works properly again (it hasn't been working for the past week)
Click to expand...
Click to collapse
yeah. mine started workin again after installing jb... almost made me believe it was software problem
Sent from my Nexus S using xda app-developers app
caleb1783 said:
yeah. mine started workin again after installing jb... almost made me believe it was software problem
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Mine broke when I installed Jelly Bean. Something fishy is going on. Now I have the same issue as OP.
Hi,
my phone died yesterday because the battery was empty - so I charged it a little but the phone won't turn back on. The only thing I see are the touch buttons flashing when I hold the power button. And when I hold it long enough, the screen just flashes... When I tried to connect it my computer I got the ADB to work - I even managed to get to the recovery one time (i used the command adb reboot recovery for almost a hundred times before it came on). I wiped everything, reinstalled the rom (TrickDroid 4.0.0), but when I tried to reboot it nothing changed... it's still not working. Fastboot is not working.
Is there anything I can do about it?
Thanks.
Mmm, are you using CWM perhaps? If so, once you get the phone into fastboot - flash twrp.
Some suggestions you can try:
keep trying vol- + power untill you get into fastboot, it should work eventually.
Charge the phone a bit, unplug the usb cable, try and boot it <- This worked for me when my phone acted up like this, took a couple of tries though.
Have you tried spamming adb reboot bootloader ? That should also put you into fastboot eventually.
Once in fastboot, reflash the boot.img for the rom as well.
And once it works again, dont let the battery go flat, this seems like quite a common issue when the battery runs out.
Thanks for suggestions - I wrote a script that tired adb reboot bootloader every 20s .. and after like 400 runs it booted - I have no idea what this is about - but I should buy a new phone...
Tahnks again!
Running CM 10.1, 06/08 Nightly
I did search the threads and google, but could not find any posts about a phone that works normally except for download and recovery.
Problems:
1. Can't boot into recovery (via apps, power menu, or manually). It gets to the boot logo, and then blank screen and resets. It will keep resetting trying to go into recovery (a battery pull will put it back to normal).
2. Can't stay in download mode. When I put the phone in download mode, it turns off after a couple seconds. I can't ODIN it if it keeps turning off.
3. Power button doesn't work properly (sometimes it works, most of the times it doesn't). Example: I press the power button to close the screen. No response. A few minutes later I might press it, and the screen will close, but come back on and this time with power menu. I took out the button to verify that it wasn't stuck, and tried pressing the actual button inside the phone with the stick. I can feel it click, but it still has the same problems. Pretty sure it's not a stuck button.
What's working:
-Everything else. If I let the phone boot normally, it loads perfectly fine and into cyanogenmod. No issues with voice/data, any apps, or instability. No battery issue. No lag. No crashes. The only issue is with the power button, and my inability to boot into recovery or go into download mode.
History:
-I was experiencing a random reboot problem (and power button issue) from an earlier nightly, and I waited a couple months for a more stable version. The CWM recovery for some reason only worked sometimes. When I did get it to work, I flashed RC5 (format and wipe data, dalvik, cache, factory reset, etc.), which fixed my reboot problem, but not my power button.
-I came across this thread: at plus.google(.com)104277415207525128383/posts/iAVpVPYqMtM and updated the radio, even though the RC5 fixed my random reboot.
-I did try flashing CWM, TWRP, and Stock recoveries (the latest ones, and from CWM/EZ recovery apps), but have not tried CWM Touch. It doesn't seem to matter, it won't boot into recovery.
Perceived Solution:
-I have a plan with Best Buy - I am considering smashing the phone and getting it replaced with a refurb, but would like to avoid that if possible.
Anyone have any ideas? I am okay with the phone as is, but I would like to be able to update CM or to another ROM in the future
Thanks for helping me out!
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
DarkMenace said:
Can you get into recovey just long enough to do a system wipe?
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Click to expand...
Click to collapse
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
phospholipid1 said:
Thanks for responding; It doesn't boot into recovery at all. Right after holding Vol. Up, Menu + Power, I get the screen with the small text in the corner, so you know it's going to enter recovery. Then the logo appears, except after that the phone either hangs with a blank screen, shuts off, or resets itself.
I think something got corrupted, but I'm not sure how to find out what, or what steps I could take to fix it.
Click to expand...
Click to collapse
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
DarkMenace said:
Unfortunately if you can't get into the recovery mode or the Odin mode then you would need to replace the phone. It's bricked.
Click to expand...
Click to collapse
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
phospholipid1 said:
Thanks for the response.
Yeah, that's what I thought. I've never really heard or seen someone with a "functionally bricked" phone, so I'm not sure what to do.
Before I go ahead and smash it for the insurance replacement, I want to see if anyone else has any ideas..
Like I said, the phone boots normally just fine. Is there some kind of app that can flash files? Or maybe some commands I can enter in the terminal emulator?
Click to expand...
Click to collapse
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Thanks for responding, guys
rellomar said:
Have you tried Odin Mobile Pro? I've never used it myself, but I've heard a lot of good things about from some friends.
Click to expand...
Click to collapse
Yes, I did. This brings me back into download mode, at which the phone just turns off.
BadUsername said:
It sounds to me like a faulty power button, it isn't hardbricked because your phone is able to boot into recovery and download mode. But If for some reason your power button is stuck in the on position, it will skip booting into recovery and eventually boot out of download mode. Just because the power button physically moves and clicks doesn't mean it can't get stuck, there's obviously something funny going on with it that isn't rom/kernel regulated.
You can try terminal emulator to see if it will work, but I honestly wouldn't do anything in any menu because your phone has the potential to reboot during a process and destroy your phone. Commands are:
su
reboot recovery
su
reboot download
If it's a power button issue, best buy should replace it anyways, you shouldn't have to smash it. Samsung will also fix it under your manufacturer warranty despite it being rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the commands; they ended up just shutting the phone off.
Yeah, I did ponder the idea that even though the power button "clicked," it might not necessarily be working. I google searched "galaxy s 3 broken power button" and there was a video with a description where the guy mentioned something about the circuit always being switched "on"
But his phone experienced different symptoms than mine (because the circuit was always switched on, the phone actually restarted itself while in normal operation. This hasn't happened to me).
Is there an app for me to definitely determine which buttons are being registered as they are pressed? Similar to programs that tell you what buttons you're pressing on your keyboard.
I would take it back to Best Buy, but I just don't want to give them any reason to say it was my own fault since I rooted and put a custom ROM on it.
Haha, I'll dunk it in salt water in favor of smashing it
Thanks again for your suggestions and ideas :cyclops:
Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.
Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".
Guess need to close this thread now.
Hey everyone, I hope this is the right place to ask for help. Something very weird happened yesterday. After removing my 2-year old Y2 from charging, I started using it normally. After a few minutes, it lagged somewhat and then stopped responding. Without thinking much, I pressed and held the power button to restart it like I have done many times before. But this time, it got stuck on the Mi logo. It kept getting stuck on the Mi logo (after switching off for about a second) no matter how many times I held the power button to restart again. I left it on the logo overnight and it stayed that way.
What I have tried yet:
1. As I said, I tried to restart it multiple times by holding the power button to no positive effect.
2. I tried to boot it up into recovery mode by holding Volume up and power button. That restarts the phone back to the Mi logo and it is stuck again. The "Main Menu" (which I think is the recovery mode) with options like Reboot, Wipe data, etc doesn't appear.
3. I tried to boot it into fastboot mode by holding Volume down and power button. It boots up to the fastboot logo so I guess it is working.
4. I followed the steps in this video. The phone stays in fastboot and nothing happens.
5. I let the phone discharge completely once, and tried charging and booting again. This also did not make any difference.
I could not find any information about something like this anywhere. Since it happened on its own, maybe it is a hardware problem? I did not install anything new in the past few days, not even a new app. Maybe it has got something to do with the battery or some other part?
I'd really appreciate any type of help in how to fix this, in particular the following issues:
1. Is there any way to know if it is a software or hardware problem without complicated tampering with the hardware?
2. Can I do anything to recover the data? I'd be really upset if I lost it all.
3. What all steps can I take to fix it if it is a software problem, preferably without losing the data?
4. If it is likely a hardware problem or a difficult to solve software problem, how I can I encrypt (or even wipe) the data before giving it to someone for repairs? (since I'm not able to boot into recovery mode)
Some extra information if you need it: my phone is not rooted, bootloader is locked, OS is Miui 11 (Miui 12 is also available for it but I haven't installed it yet. Maybe there's a way to install it externally which would boot up my phone?)
Thank you for your help! I'd really appreciate it
Same problem with me please suggest some best sort of solution
pcjha said:
Same problem with me please suggest some best sort of solution
Click to expand...
Click to collapse
Hi, I recommend you first of all back up your data if still possible.
Then, reboot into fastboot.
-fastboot erase system
-fastboot erase cache
- fastboot erase userdata
-fastboot erase recovery.
Then clean flash a rom.