I keep getting this. I am pretty sure my adb drivers are properly installed since fastboot detects it just fine, and I even got USB debugging enabled and the RSA fingerprint thing checked out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I type in fastboot oem unlock it just shows finished and nothing happens on my device. However I am still able to use fastboot oem device-info and fastboot reboot to reboot into OS no issues. Never had an issue unlocking bootloaders in my entire life. What now? Windows 10 issue? Did I miss something?
It's done. Mine did the same thing. No response from the phone at all but it had in fact done the unlock.
Sent from my ONE A2001 using Tapatalk
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
Type fastboot oem device-info and see if it days unlocked=true to check
Sent from my ONE A2001 using Tapatalk
gmac1990 said:
It's done. Mine did the same thing. No response from the phone at all but it had in fact done the unlock.
Sent from my ONE A2001 using Tapatalk
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
Type fastboot oem device-info and see if it days unlocked=true to check
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
LOL yeah turns out my phone was already bootloader unlocked as I bought it used... Just did a bit more googling and found out another dude having the same problem on his OPO, turns out it was unlocked as well. Got TWRP and SuperSU up and running now. :good:
My problem is a little diferent, using W/ 64 and the generic android USB drivers
- adb devices don't get a response
- fastboot commands run without a problem
I still managed to unlock bootloader!
Related
Hi guys, i just flashed the touch cwm from official site.
When i try to turn on in recovery mode, phone gave me this message:
Secure booting error
Cause: boot certification verify
I did a research on xda and found this: http://forum.xda-developers.com/showthread.php?p=45518562
I tryed to flash the bootloader but, i dont think it worked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After i opened Reboot2Recovery and got this:
What can i do?
Hi, i also had this problem...
At first you must unlock the boot loader than you can install cwm from ROM manager. (I did it so)
Try to search Google for another boot loader unlock. Then it must work Good luck
Sent from my LG-P700 using xda premium
solved
I opened the bat with notepad and saw the location must be in C not on desktop..
http://www.lg-phones.org/how-to-unlock-bootloader-on-lg-optimus-l7.html try this
Sent from my LG-P700 using xda premium
the solution is to have the .img file in c:\, not on desktop
You must have adb.exe and the .IMG in one directory then it must work
Sent from my LG-P700 using xda premium
AleCs14 said:
Hi guys, i just flashed the touch cwm from official site.
When i try to turn on in recovery mode, phone gave me this message:
Secure booting error
Cause: boot certification verify
I did a research on xda and found this: http://forum.xda-developers.com/showthread.php?p=45518562
I tryed to flash the bootloader but, i dont think it worked:
After i opened Reboot2Recovery and got this:
What can i do?
Click to expand...
Click to collapse
Hey, I got the same error in my old L7, but I had the stock rom and it appeared after my phone ran out of battery; when I tried to charge the battery via plugging to alternate current i got that error...
Is there a way to revive my phone without losing all the data in it?
HEEEEELP!!! I'm in great need of assistance! I'm new to modified roms and I'm at a lose with my Motorola defy (MB525). it seems to be bricked and won't detect in my computer
Here is what i did:
1. I had rooted it with superone click
2. unlocked bootloader
3. I had installed clockwork mod and flashed CM10.1 Android 4.2.2. Everything was working but some of my google play services and data
4. The problem showed up when I tried to upgrade and install CM 10.2 Android 4.3
5. It flashed successfully but very time it would power on, it would forget all the settings. It also wouldn't boot into clockwork recovery mode and would reboot when installing third apps like Rom Manager.
6. I tried wiping cache but now it won't even boot up, just black screen.
7. I tried putting the clockwork mod back on but it goes to the andorid boot menu and can't find a custom recovery
8. Now it boots staight to android boot menu, It will not detect in my Mac or friend's PC
9. Downloaded motorola drivers, RSD Lite for pc and tried entering bootloader mode but battery is too low to put in USB transferring mode
10. Tried charging for hours but it is still not charged enough to do bootloader mode
Not sure what else I can do, any suggestions? Please and thanks!
Charge the battery outside the phone? Using one of these
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 02:04 AM ---------- Previous post was at 02:04 AM ----------
Charge the battery outside the phone? Using one of these
Then reload an SBF.
Try this http://forum.xda-developers.com/showthread.php?t=892026. "red goes to the + terminal, black goes to the - terminal"
DanFragoso said:
Try this http://forum.xda-developers.com/showthread.php?t=892026. "red goes to the + terminal, black goes to the - terminal"
Click to expand...
Click to collapse
This worked like a charm, thanks alot
Hello everyone,
First of all, I apologize if this post is in the wrong section. Also I'd like to say how awesome it is everyone that is involved in these projects.
My Issue is I can't get ANYTHING to work, I have tried so many roms that apparently work for my phone and I always, foot errors, signature errors though the adb. I have tried every program to unlock bootloader but apparently does not work unless you are running V2 551 2.40.*.* so I went and downloaded this, and wants again can't flash the ROM. The unlock bootloader was weird, I went through all the installation and I don't even know if it worked to be honest. I can boot into the phone via power and volume down, and get a menu that includes, apply apps from ADB, wipe/restore phone, fastboot mode * which goes as far as my phone saying *FASTBOOT !!!* then thats it will not continue. The power and volume up does the same thing. So basically I'm starting to think this piece of crap phone will never have a decent operating system on it. The phone is in developer mode and USB debugging is on also. * Basically have done every single tutorial I can find and nothing works*. Also the twrp doesn't even work. I have even tried flashing back to an older version on the phone and get the same ADB errors. I have installed all the ADB and also minimal adb and fastboot and all drivers for the phone as well. * TRYING NOT TO MISS ANYTHING*
My phone specs:
Model: ASUS_z00LD
Android: 5.0.2
Baseband Version: 202c10_10.0.0_160120
Kernel: 3.10.49-gec27b65
Build: LRX22G.WW_user_1.17.40.1106_20160202044030520_2015052101030010000300001
IMAGES:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hope it works
Did you try to unlock bootloader the official way? I myself unlocked the ZE550kl following this thread http://forum.xda-developers.com/zenfone-2-laser/general/ze600kl-official-bootloader-unlock-t3273263
You can check if bootloader is lock or not from fastboot by entering "adb>fastboot oem device-info" should show up somewhere between the lines "Device unlocked: true"
After unlock only then you can install Official recovery TWRP 3.0.0-0 from here http://forum.xda-developers.com/zen...recovery-twrp-3-0-0-0-touch-recovery-t3317513 .
If needed TWRP will also help you root your phone once is installed.
Good luck!
Folks, after a successful downgrade to 6.01 and re-lock the bootloader, i can install all ota's, but the one thing is, that the device will always stays on bootloader after reboot. Right now, i am on the latest MM and will update now to N. Everything works fine. This device must be locked.
I need manually press "START" to reboot into system or recovery mode.
I want to stay on originally software. How can this issue be fixed?
Try connecting your device to your computer, then whilst your device is at the bootloader, in the adb terminal on your computer type 'fastboot oem fb_mode_clear' (without quotes). This may allow your device to reboot properly.
echo92 said:
Try connecting your device to your computer, then whilst your device is at the bootloader, in the adb terminal on your computer type 'fastboot oem fb_mode_clear' (without quotes). This may allow your device to reboot properly.
Click to expand...
Click to collapse
Good job, works, right now
After the latest update to 7.0/NPJ25.93-14/16 it shows instead logo, ID=Bad key, this device is unlocked bla bla bla, but it isn't. Once i did this serveral month ago, it works but not now. MM does not shows a bad key.
i know i can flash a logo to cover this but it should be in original state. Screenshots follows_
After the latest update to 7.0/NPJ25.93-14/16 it shows instead logo, ID=Bad key, this device is unlocked bla bla bla, but it isn't. Once i did this serveral month ago, it works but not now. MM does not shows a bad key.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone help?
Gesendet von meinem Moto G (4) mit Tapatalk
No need to worry about,
after N update, everyone's phone has "bad key" ..
Just ignore it, it's nothing..
Ok so hear me out i have the pixel 2 vzw model and i was playing around with it and found out that if you factory reset it and then run `adb shell pm uninstall --user 0 com.android.phone` and reboot the phone twice the oem unlocking switch will work and you can enable it however when you reboot the phone into fastboot mode it will say oem unlocking is not allowed and the switch will just regreay out the phone was running the latest verison of android 11 for it from what i was told when you run the `fastboot flashing unlock` command it checks the phones imei to see if its a vzw or not so if there were a way to spoof the imei to a factory unlocked one without root it could be possable to unlock the bootloader on the vzw pixel 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I give up on this i thought it could be possable but its not i was going to sell it on swappa but swappa wants me to replace the battery on it and for the same price of doing that i could just go buy a factory unlocked model and im not investing money into a verizon model phone and the only reason why i have this is because i got scammed and i was told this was factory unlocked but its this vzw bull****
Unfortunately I feel like Swappa is dead except to resellers. Total cost to sell a $400 phone a few months back was over $50!!! Insane!!! Facebook market place from now on!
Scottx86 said:
Ok so hear me out i have the pixel 2 vzw model and i was playing around with it and found out that if you factory reset it and then run `adb shell pm uninstall --user 0 com.android.phone` and reboot the phone twice the oem unlocking switch will work and you can enable it however when you reboot the phone into fastboot mode it will say oem unlocking is not allowed and the switch will just regreay out the phone was running the latest verison of android 11 for it from what i was told when you run the `fastboot flashing unlock` command it checks the phones imei to see if its a vzw or not so if there were a way to spoof the imei to a factory unlocked one without root it could be possable to unlock the bootloader on the vzw pixel 2 View attachment 5351665
Click to expand...
Click to collapse
holy run on sentence
Scottx86, sorry to hear about this.
Factory unlocked - means you can use any carrier.
Bootloader unlockable is a whole different beast.