So,
I wanted to install a new recovery because i want to try out multirom (http://forum.xda-developers.com/oneplus-x/orig-development/mod-multirom-v32-t3316937).
But when i wanted to flash the recovery I found out that the bootloader is again locked.
I tried to unlock if again but the fist problem was, that it said "error: device offline" every time i did "adb reboot bootloader".
So i just bootet into fastboot myself and did "fastboot oem unlock". Then the program said that it finished and my phone launched TWRP.
I heard that you need to press "Yes" in your recovery but nothing showed up. The phone is still locked and i can`t figure out what to do/ what i do wrong.
I hope you guys can help me,
Andy
Related
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
Hello all, greetings from Indonesia.
Can you help me to fix my OPX, my OPX is stuck on logo (bootloop), can't go to recovery but can go to fastboot using power + vol up. FYI; my phone is not rooted.
The problem is, everytime I try to unlock the phone via ADB using command, "fastboot oem unlock" it's always fail, it's written bla bla bla False.
I also try to flash TWRP via ADB using command, "fastboot flash recovery twrp.img" it's also written fail.
Please somebody help me, what's wrong with my phone.
Hi guys,
In the past days i've been troubling my head with trying to unlock the bootloader on my lenovo tb-x103f, but cant seem to enter fastboot mode
I've been using this guide as reference, among other searches from all around, trying to work around this, but cant really seem to come to the bottom of this.
from cmd
adb recognizes my device
"adb reboot bootloader" tablet just boots into the startupscreen
"fastboot devices" somehow "confirms" that im in fastboot, even tho Im acctually not (right?)
"fastboot oem unlock-go" finishes, and says its successfull, but nothing happens (obviusly, since its not acctually in fastboot mode)
from there it just sits there, and nothing happens. have to reboot it myself, either via cmd or the button
why is it not entering fastboot mode? is there any fix for this?
This is getting really frustrating as I just wanna root the tablet and most likely install lineageOS, or some other custom ROM..
thanks in advance
If you can reboot it with a command than you are connected in fastboot mode. It sounds like you have unlocked you tablet. Enter fastboot mode through adb again and try "fastboot oem device-info"
Hello,
as I said in another thread, I bricked my tablet while trying to root it, and made it worse while trying to fix it: it's in a bootloop.
Fastboot mode works still, but no recovery I tried does anything. So I might have fried the bootloader by doing something stupid like "fastboot flash boot <file.img>". I can't remember whether I did this during my desperate attemps of getting out of the bootloop, but if I did, how would I find out?
As far as I understand the boot process (now ), there is a piece of code that initializes the device and then loads the actual bootloader into memory. When I'm in fastboot mode, am I already within the bootloader or still inside that piece of initial code?
When I chose "recovery" or "normal boot", is it first then that the bootloader is started? Or is it already the bootloader that shows those options ("recovery", "normal boot" and "fastboot")?
When I do a "fastboot getvar all" I do get a lot of variables all starting with "(bootloader)", mostly "partition-size" and "partition-type". So is my bootloader still ok and if not, how do I find out whether it's the bootloader broken or the recovery I'm trying to flash, and which one is causing the bootloop?
Thanks for any hints.
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
salmanvai said:
Hi, My Nokia 1 (TA-1047) is now in "No Command" mode.
I installed TWRP recovery previously and tried to root but failed. Then I installed stock recovery and phone started normally. As the phone started normally, I locked OEM through Fastboot mode and disabled OEM unlocking from "Developer Option".
But while installing "system update" from "Settings", it showed error and went to "No Command" mode.
Now I'm unable to flash anything through Fastboot mode because the OEM is locked. Also I'm unable to change OEM unlocking from "Developer Option" as the phone is not starting.
Is there any option to unlock OEM without the help of "Developer Option"?
Click to expand...
Click to collapse
Edit. Okay, ignore most of what i said down there as after re-reading your post you seem to have a grasp on fastboot, the no command bit still applies though i think
"No Command" mode
If your talking about the recovery with the android image in the background, then there might still be hope, for some reason, the recovery starts up in this mode, showing the "no cammand" message, its fiddly, but you have to press the power button and either volume up or volume down repeatedly, in the end i was button spamming all the buttons and eventually the recovery menu showed up. Carefull to stop pushing buttons when the menu shows up as the buttons are how you navigate(v+,v-) and choose options(power button)
Whether that gives you any options i dont know, you could try a factory reset from the recovery menu, i suppose, or try the posted ota in the other thread if nokia has`nt released official firmware, although im not sure if you can use stock recovery to flash unofficial firmware, best bet is to try and boot into fastboot and use adb on another computer to flash the firmware that way, assuming the firmware files are available.
Most android devices have a way to boot into recovery or fastboot/bootloader using hardware keys
Quick google found this (works?)
Power off
Connect Micro USB to computer.
"In the next step hold down Volume Down + Power key for a short while"
Let go of the buttons when fastboot comes up
Using the computer with adb installed, go to a command terminal and type "fastboot devices" without quotes, you`ll know everythings working if your the device is listed in terminal after typing that command. From there look up fastboot flashing firmware or something to that extent, this is assuming you managed to find the correct firmware for your device and have it stored in your computer
I`d be real carefull here with fastboot, flashing wrong image file could make things much worse, at least it seems you can boot to recovery, so hopefully a factory reset fixes things, use fastboot as last resort i.e if its new job is a paperweight, as i dont think theres any particular guide on doing this specifically for the nokia 1, but i havent checked thouroughly so i could be wrong, take a look and see..............
And let us know if/how you managed to get it working
Goodluck