Okay, thank you in first place for reading this.
Yesterday i wanted to clean install all my phone so i wiped it - changing partitiontype to f2fs, the next thing was ofc flashing the new twrp3.0 and here suddently I couldnt proceed - FAILED (remote: Device not unlocked cannot flash or erase) - ok said me to myself, lets unlock it then, so I just writed down "fastboot oem unlock" phone rebooted in twrp and asked me if i wanted to keep readonly or change stuff, clicked keepreadonly, rebooted in system, setup the phone(no unlock notify) then checked developer options (enable unlocking+usb debugging) reboot fastboot, still "locked" "device-info"-shows false on every single thing. Idk whats happening but i gently ask you to some advice, thanks.
solution is here.
http://forum.xda-developers.com/one...rick-guide-hard-bricked-t3272108/post64339270
Related
Hello, I've ran into some trouble with my nexus 9. After the last update my device seems to be bricked, just stuck on the white "google" logo during start up.
I'm trying to flash OEM android on my device and have been unsuccessful because my bootloader seems to be locked, and the only way I can find online is to do it through developer options which I cannot access now since my device is bricked. I've tried the fastboot command oem unlock and permission is denied. Prior to this I have not enabled developer option or usb debugging because I was ok with using stock software.
I can get into bootloader mode and access fastboot USB but I cannot flash my device due to bootloader being locked!
I've also tried Recovery -> wipe all data, and my device is still bricked afterwards!
Is there anything I can do at this point?
I've been running stock software the whole time! Never rooted / unlocked my device.
Forget about it.
Talk to the vendor (google / amazon / etc) the device is FUBAR
I am getting a new one, since there is no way to fix this.
period.
sorry for everyone affected, but google said, that there is no way to fix it.
damn..just called google and they said they will get back to me next week. this is pretty sad
doanb666 said:
Forget about it.
Talk to the vendor (google / amazon / etc) the device is FUBAR
I am getting a new one, since there is no way to fix this.
period.
sorry for everyone affected, but google said, that there is no way to fix it.
Click to expand...
Click to collapse
Ariadust said:
damn..just called google and they said they will get back to me next week. this is pretty sad
Click to expand...
Click to collapse
It seems, I have the same problem. I tried to wipe it several times, it is no use.
Maybe I am completely dumb, but could one not sideload from 5.1.1. to 5.0.2.?
adb sideload <>
is about the only thing that is working. I don't know, how ota-files are created.
Have you tried this?
http://forum.xda-developers.com/nex...-disabling-t2951312/post60702161#post60702161
Put Device in Fastboot mode:
Power and Volume down,
then in the bootloader, go to fastboot.
With the fastboot tool (google), type:
fastboot format cache
fastboot format:ext4 userdata
It fixed it for some users, because wiping the userdata is apparently different from a factory reset in the boot loader.
For me, it did not work out: I did not end in a boot loop but in a neverending boot sequence.
Trying to flash 5.1.1 on my N6; now stuck on colored dot bootloop. Tried fastboot format cache and fastboot format userdata; both fail because the bootloader is locked.
Google has completely ruined this. I've owned the Galaxy Nexus, Nexus 4, and Nexus 5, and I *never* had a single issue doing simple **** like this on those phones. Here, everything fails. All the time. This time it's failed hard enough, evidently, to cause a permanent brick. Thanks a lot, Google.
Hi all, this is my last hope at the moment. Any input would be highly thanked.
I own an ASUS Padfone 2 (KOT49H.WW_Padfone-11.8.4.23-20141028), stock firmware, that I managed to get soft-bricked, as I read they call it.
Phone is unrooted, ran KitKat, and I really don't know much more about it, I'm not really an expert unfortunately... No custom ROM or any of those pro stuff.
Scenario:
Every single app crashed upon opening, performed a reboot, phone got stuck into infinite boot-loop, at the company logo in the beginning.
What can the phone do and what I've done so far (all of which have been found through internet):
I can enter into recovery mode.
Did a factory reset and wiped cache partition before the following.
I entered what the phone calls "CSC mode", that other sources call "fastboot mode".
Followed this guide http://forum.xda-developers.com/showthread.php?t=2256977 , installed drivers, entered into the proper directory on CMD, and typed "fastboot boot recovery.img", but CMD says "OKAY" and all, but gets stuck at "booting...", even after like 15 minutes.
Then, for whatever reason I saw on the internet, I tried the command "fastboot oem unlock" that also didn't finish anything either in CMD or (seemingly) on the phone.
Then, I tried following this guide in CSC mode (even though I don't have the invalid kernel error) http://www.modaco.com/forums/topic/365818-padfone-2-invalid-kernel/#comment-2191432 , but also didn't get any further than CMD stuck at "booting..." for forever.
I suspect it could be possible to do some of those booting magic, but I have no clue how it works and how my problem inside the problem could be solved...
Thank you so much in advance.
(Please beware that I don't understand what the words bootloader, fastboot, flash or ROM mean. I'm a mere mortal.)
Hi Team,
i am using Lenovo ZUK Z1 , morning today, after restarting the phone manually, device has gone into endless restart loop, i can boot onto recovery menu as well as fastboot mode, from what i have read so far i have to flash Factory image, to be able to bring this to a usable state, i would like to tell you that i cannot get the bootloader to unlock since OEM unlock option in developer option is disabled, i dont have any custom recovery installed, neither can i use adb commands since USB debugging is disabled, i have tried factor reset but the phone still continue to reboot and optimizes apps, what should i do to get out of this?
I would like to apologize if i have failed to convey my point properly, also please pardon my ignorance, since this is my very first question on this forum
Thanks in advance.
Sorry to make my first post a request for help. Here's what happened.
I have a model KIW-L24 Honor 5X, with code-name kiwi with TWRP and Lineage OS 15.1 installed. Last night (today?) at around 2 AM PST or so (not sure of the exact time, I would have looked on my phone) my phone suddenly rebooted into recovery. I waited for the menu to pop up or something, but instead it eventually rebooted again. After that, every boot consists of "Boot/Recovery image verify failed!" "Please update to the authorized images." and then brings up the fastboot screen, which proudly displays "PHONE Locked" in green and "FRP unlock" in red. From what I understand, this means that the bootloader is locked (again).
Now, in theory, I can re-unlock the phone (once I find the relevant code again), flash lineage os again, and continue on my merry way. However, I have a password manager on my phone (Keypass2Android) that has not been backed up recently, so it would be preferable if I could recover that, at the very least. I've already tried booting both a custom recovery image and a stock recovery image via
Code:
fastboot boot <image>
but it only came back with
Code:
FAILED (remote: Command not allowed)
so I can only conclude that I cannot boot arbitrary images while the boot-loader is locked.
So, here's my options as I see it:
Unlock the bootloader again, wiping the device.
Flash stock, hope that that doesn't wipe my data. (EDIT: if it doesn't, hope that it doesn't bootloop or something requiring me to wipe)
Find some other method of recovering data from the device.
So, my questions are: how might the bootloader have gotten locked in the first place? Is there anything I can do to recover data, especially my password manager data? Please let me know if there's any other information you need.
Thanks in advance, regardless of the answer.
I (seemingly) successfully unlocked my Realme's bootloader yesterday, I even managed to get into the bootloader through the DeepTest app, flash TWRP and get into it, but after resetting the phone, the recovery got overwritten by the stock one and now I cannot get into fastboot by any means.
adb reboot bootloader only displays a message for a split second and then reboots into OS again. Which happened before as well.
However, the DeepTest app doesn't show the Check query button (through which I could get into the fastboot) anymore and the only other button there is Apply to exit in-depth test which only displays You can apply to exit in-depth test after carrying out bootloader lock operation in fastboot mode, but tapping on Ok doesn't do anything.
The phone still seems to be working (even fp sensor), I just cannot get into fastboot.
I've also tried flashing the EU (A.54) build to the B.63 build, nothing changed.
How do I resolve this?
/EDIT: I should also mention that after the first wipe (right after confirming bootloader unlock) the DeepTest app was still working as intended, however after the custom recovery was overwritten by the stock one, it started misbehaving as written above. Wiping the internal storage again (through recovery) didn't fix anything as well.