Hello everyone. I did something wrong, and now the phone is kind of bricked.
It was unlocked, and wanted to lock again but after trying to do so, the phone was stucked in opening screen. I cannot turn it on. Recovery mode says "no commend", when I try to flash rom, it says " Check 'Allow OEM Unlock' in Android Settings > Developer" but I cannot turn it on.
I tried Rescue and Smart Assistant as well, but when I try to start rescue, it gives warning: "To avoid damage to the device caused by flashing , RSA recommends that you go to the customer center for help."
So I cannot do anything. Neither I can flash a rom, nor unlock again, nor turn it on. Do you know what should I do? Is it gone now?
Related
So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.
Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.
Is this the wrong forum for this question?
JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck
Hey guys
So last night my nexus 5 restarted and got stuck on the google logo screen, and won't load past it.
When I go into the bootloader and attempt to enter recovery mode all that happens is a blank screen, with a faint backlight on.
I've tried to use nexus root toolkit and chain fire auto root, but neither of them seem to work.
With the nexus root toolkit, I tried several times using the flash stock/unroot option. It would work fine until the phone prompt titled 'unlock bootloader?' which when I chose yes would then attempt to reboot the device into bootloader mode, but all that happens is my phone will show the charging symbol. There were a few times where the bootloader would flash quickly on screen and show that it was unlocked, but then afterwards the charging symbol would show.
With Chain Fire auto root, after the phone prompt saying 'unlock bootloader' and me selecting yes, it will load the bootloader again and show that it is unlocked, after which the program gets an unknown error.
I'm a complete novice in this area so if anyone has ideas, detailed instructions would be greatly appreciated
I have a feeling its a hardware issue, but am posting just in case.
Thanks heaps for any input!
Few days ago, my Google Pixel2 suddenly reboot by itself & then stuck in screen with android logo with option "Start", "Recovery Mode", "Barcode", "Power Off". Aside from "Power Off" & "Barcode" function all function like Start/RecoveryMode doesn't work- it will eventually return to same screen with Android logo. On the screen, it was indicated :
- Device state: Locked
- "ERROR: Slot Unbootable: Load Error"
My phone is still in OEM-locked status (before this issue occur) and i couldn't get into "RecoveryMode" to perform factory reset.
I tried using fastboot/ADB to unlock the phone, to flash with new image, to switch boot-slot from a to b.... all attempted failed with error that the phone is locked.
I did searched for different forums and tried different methods but can't find any solution to fix this problem (Seems like there were quite a number of people having same issue within these few months). The fastboot toolkit seems to recognize my phone but basically none of the command to flash the phone could work.
I suspect there was an auto-update that had cause this sudden reboot. I tried various ways to reboot but nothing works. When i plug in USB to phone on my laptop, it was not detected and when you right-click on the USB icon to eject, it shows "Eject Android"- when i eject, it shows "Android bootloader interface removed". If i check in DeviceManager on Microsoft Windows, the Pixel2 wasn't really detected.
It would be a great help if you can guide me to solve this as I really love this phone and hope i could fix this. I'd tried contacting Google.. according to them I'm eligible for RMA but I need to be in US in order to claim that. Unfortunately, that would not be an option as I'm currently located in Malaysia. Hence, was just trying to reach out for any help/guide from experts out there
Thanks a lot~
meeeei said:
Few days ago, my Google Pixel2 suddenly reboot by itself & then stuck in screen with android logo with option "Start", "Recovery Mode", "Barcode", "Power Off". Aside from "Power Off" & "Barcode" function all function like Start/RecoveryMode doesn't work- it will eventually return to same screen with Android logo. On the screen, it was indicated :
- Device state: Locked
- "ERROR: Slot Unbootable: Load Error"
My phone is still in OEM-locked status (before this issue occur) and i couldn't get into "RecoveryMode" to perform factory reset.
I tried using fastboot/ADB to unlock the phone, to flash with new image, to switch boot-slot from a to b.... all attempted failed with error that the phone is locked.
I did searched for different forums and tried different methods but can't find any solution to fix this problem (Seems like there were quite a number of people having same issue within these few months). The fastboot toolkit seems to recognize my phone but basically none of the command to flash the phone could work.
I suspect there was an auto-update that had cause this sudden reboot. I tried various ways to reboot but nothing works. When i plug in USB to phone on my laptop, it was not detected and when you right-click on the USB icon to eject, it shows "Eject Android"- when i eject, it shows "Android bootloader interface removed". If i check in DeviceManager on Microsoft Windows, the Pixel2 wasn't really detected.
It would be a great help if you can guide me to solve this as I really love this phone and hope i could fix this. I'd tried contacting Google.. according to them I'm eligible for RMA but I need to be in US in order to claim that. Unfortunately, that would not be an option as I'm currently located in Malaysia. Hence, was just trying to reach out for any help/guide from experts out there
Thanks a lot~
Click to expand...
Click to collapse
What happens when you try to boot into recovery?
jd1639 said:
What happens when you try to boot into recovery?
Click to expand...
Click to collapse
When i select "Recovery Mode" and press Power button, the screen turn black for a second and then the screen is back to the Android logo with the previous option of "Start"/"RecoveryMode"/Barcode/PowerOff.
Other post mentoned that I should see "Google" logo after selecting RecoveryMode.... I couldn't get into the Google logo at all. It is as if stuck in that AndroidSleepingLogo page
Kind of the same happened to me yesterday: https://forum.xda-developers.com/pixel-2/help/pixel-2-bricked-t3914178. Maybe it helps you...
Have tmobile oneplus 8 and when trying to unlock with the cust-unlock command it gives me an error as shown in the image attached. made sure that the oem unlocking switch is enabled in the settings
This only happens when you didn't enable OEM unlocking, I know you said you did, but I'd double check. Boot the phone up, go to Settings -> About phone and tap "build number" a bunch of times til the message pops up.
Than go to Settings -> System -> Developer options and enable OEM Unlocking.
Then repeat the same steps in fastboot to unlock.
Restarted my phone turned it off. Then restarted again and turned it on. And still no luck
FoxyDrew said:
This only happens when you didn't enable OEM unlocking, I know you said you did, but I'd double check. Boot the phone up, go to Settings -> About phone and tap "build number" a bunch of times til the message pops up.
Than go to Settings -> System -> Developer options and enable OEM Unlocking.
Then repeat the same steps in fastboot to unlock.
Click to expand...
Click to collapse
Restarted my phone turned it off. Then restarted again and turned it on. And still no luck
Snekxs said:
Restarted my phone turned it off. Then restarted again and turned it on. And still no luck
Click to expand...
Click to collapse
Are you on stock T-Mo firmware, and have taken all OTA updates? I saw you said in another thread that after using MSM tool "the software update button is greyed out in the settings". If that's still the case...well it shouldn't be lol. I would MSM again back to OOS10, than immedietly try booting the phone up enabling OEM unlocking and try to unlock the bootloader again.
FoxyDrew said:
Are you on stock T-Mo firmware, and have taken all OTA updates? I saw you said in another thread that after using MSM tool "the software update button is greyed out in the settings". If that's still the case...well it shouldn't be lol. I would MSM again back to OOS10, than immedietly try booting the phone up enabling OEM unlocking and try to unlock the bootloader again.
Click to expand...
Click to collapse
Yeah. The button was greyed out but my phone still installed an update. Gonna try to use msm again and see
Curious if you found a solution to this one? Been fighting a similar situation, not the MSM tool just but the unwillingness to let me run the unlock bin token.
The phone doesen't starts when it is not plugged in, but when I plug in the cable it only shows the Huawei logo and then reboots. I managed to get to fastboot mode, but can I do anything from there to get my data? The bootloader seems to be Unlocked, as it reads "Phone Unlocked". But I don't think OEM Unlock was enabled in settings. I tried flashing TWRP, but I get "remote: Command not allowed" error.
Recovering data from a boolooping phone isn't possible at all.
Deleted member 1890170 said:
Recovering data from a boolooping phone isn't possible at all.
Click to expand...
Click to collapse
I took the phone to a repair center and they fixed it while keeping data. I wonder how they did it.
The only option to recover data from a bricked phone is to apply an update on top. This option would be to update the phone.