Database Users

nexus 4 stuck on google logo

Hi
my nexus 4 stuck on the google logo after updating to kit kat
i tried to flash stock room 4.3 but it is stop on the google logo
i tried to flash stock rooms 4.2.2 and 4.2.1 but the same thing is happen
importnat note:
1-I can not go into recovery mode (when choose recovery mode the phone stop on google logo)
2- I can go into bootloader
3- bootloader it unlocked
4-usb debugging is not enabled
please helpe me it is a challenge for me.

Sideload the ota update. Guide. Files. And make sure adb is properly configured on your pc.

arffrhn said:
Sideload the ota update. Guide. Files. And make sure adb is properly configured on your pc.
Click to expand...
Click to collapse
how i can check the adb configuration on my PC

hralzarwi said:
how i can check the adb configuration on my PC
Click to expand...
Click to collapse
If you don't know it then I assume you haven't have adb set up on your pc. No worries, look here for a step by step guide how to set it up.
Edit: How did you try to flash the 4.3 after a failed 4.4 ota update? Now that I see, if you can't enter recovery, then you can't sideload. Try and download wug's toolkits. Some said that it can work even if your device can't get pass the google screen.

arffrhn said:
If you don't know it then I assume you haven't have adb set up on your pc. No worries, look here for a step by step guide how to set it up.
Edit: How did you try to flash the 4.3 after a failed 4.4 ota update?
Click to expand...
Click to collapse
i did it using nexus 4 toolkit number 9 then 2 after in put the stock room in (put_factory_image_here) folder
also I used nexus root toolkit (flash stock + unroot)

hralzarwi said:
Hi
my nexus 4 stuck on the google logo after updating to kit kat
i tried to flash stock room 4.3 but it is stop on the google logo
i tried to flash stock rooms 4.2.2 and 4.2.1 but the same thing is happen
importnat note:
1-I can not go into recovery mode (when choose recovery mode the phone stop on google logo)
2- I can go into bootloader
3- bootloader it unlocked
4-usb debugging is not enabled
please helpe me it is a challenge for me.
Click to expand...
Click to collapse
Do you have any custom recovery installed?
Do you already tried flash using fastboot or ADB?
(You can use the Unified Android Toolkit and performer a full flash).

davidbranco said:
Do you have any custom recovery installed?
Do you already tried flash using fastboot or ADB?
(You can use the Unified Android Toolkit and performer a full flash).
Click to expand...
Click to collapse
thank you too much
no i do not have any custom recovery
yes i tried to flash more than one room using fastboot but nothing
i will search of unified android toolkit
thanks again

Maybe you should try lock your bootloader and than relock it again? Type in fastboot (when your phone is in bootloader mode) : fastboot oem lock, than fastboot oem unlock. It can help. Regards
Wysłane z mojego Nexus 4 przy użyciu Tapatalka

I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please

ProrokX said:
Maybe you should try lock your bootloader and than relock it again? Type in fastboot (when your phone is in bootloader mode) : fastboot oem lock, than fastboot oem unlock. It can help. Regards
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
Click to expand...
Click to collapse
thank you
i did it but still the device is not working

hralzarwi said:
I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please
Click to expand...
Click to collapse
Are you sure the factory images got flashed properly? I once had this problem...but in my case adb doesn't work as the phone wasn't detected on pc. But luckily, recovery still works. You're stuck at Google screen because there is no system in your device. Maybe as a result of incomplete flash or broken system.img. Is your phone gets detected in adb? Plug in your phone. Open CMD in platform-tools and type in adb devices. See if your device serial number is listed as device in cmd.
Sent from my Nexus 4 using xda premium

hralzarwi said:
I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please
Click to expand...
Click to collapse
Try this.
1. Download a factory image from here. For my instructions, I'm using 4.4 KitKat, feel free to install previous versions of Android.
2. Extract it
3. Drill down into occam-krt16o (or whatever build you're using) Double check to make sure the folder name starts with "occam". That means it's the right image for the Nexus 4
4. Copy all of the contents of that folder, should be 6 files, into your platform-tools folder, where you are issuing adb commands from.
5. Once all 6 files are copied into your platform-tools folder (or wherever fastboot.exe is, really. Where you're issuing commands from.)
6. Boot into your bootloader (Turn phone off, hold power and Vol-, or just use 'adb reboot bootloader')
7. In the command prompt that you should have opened in the same folder as fastboot.exe and the 6 files from the factory image, type 'flash-all.bat'
8. Sit back and wait while it reformats and reflashes every partition on your phone.
9. Boot up and make sure it worked.
Let me know if that worked, or where you're getting hung up on and why and I'll try to walk you through this, step-by-step.

Johmama said:
Try this.
1. Download a factory image from here. For my instructions, I'm using 4.4 KitKat, feel free to install previous versions of Android.
2. Extract it
3. Drill down into occam-krt16o (or whatever build you're using) Double check to make sure the folder name starts with "occam". That means it's the right image for the Nexus 4
4. Copy all of the contents of that folder, should be 6 files, into your platform-tools folder, where you are issuing adb commands from.
5. Once all 6 files are copied into your platform-tools folder (or wherever fastboot.exe is, really. Where you're issuing commands from.)
6. Boot into your bootloader (Turn phone off, hold power and Vol-, or just use 'adb reboot bootloader')
7. In the command prompt that you should have opened in the same folder as fastboot.exe and the 6 files from the factory image, type 'flash-all.bat'
8. Sit back and wait while it reformats and reflashes every partition on your phone.
9. Boot up and make sure it worked.
Let me know if that worked, or where you're getting hung up on and why and I'll try to walk you through this, step-by-step.
Click to expand...
Click to collapse
I did it perfectly but i still have the same problem
but i find this and i do not know if it is an error or what?
{
"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"
}
my phone still stuck on google logo
thank you too much for your concern

arffrhn said:
Are you sure the factory images got flashed properly? I once had this problem...but in my case adb doesn't work as the phone wasn't detected on pc. But luckily, recovery still works. You're stuck at Google screen because there is no system in your device. Maybe as a result of incomplete flash or broken system.img. Is your phone gets detected in adb? Plug in your phone. Open CMD in platform-tools and type in adb devices. See if your device serial number is listed as device in cmd.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I think no , please see the message

hralzarwi said:
I did it perfectly but i still have the same problem
but i find this and i do not know if it is an error or what?
my phone still stuck on google logo
thank you too much for your concern
Click to expand...
Click to collapse
Well that is kind of weird, espeically considering you just got a bunch of 'OKAY' messages. Does a device come up if you type 'fastboot devices' while you're in the bootloader? If not, your drivers aren't quite installed correctly and this is an easier fix than what it could be. If so, then maybe try letting your phone sit at the Google logo. The initial start ups are usually long, maybe it just needs time.
If your device DOES come up in fastboot devices and you think you've given it enough time to start and it won't, then we might try to flash the images manually (even though it says they flashed successfully, which is annoying). Since you already have the factory image inside your platform-tools folder, try this:
1. Extract the image-occam-krt16o.zip into the platform-tools folder
2. You should now have, among other files, 6 .img files in your platform-tools folder Again, make sure those images are from an 'occam' image
3. Run these commands:
Code:
fastboot flash bootloader bootloader-mako-makoz20i.img
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
4. Once those are all done, try rebooting
This all might seem redundant, but this is a weird case and we're taking everything one step at a time. If you're still stuck, try updating your sdk and getting a newer fastboot.exe. If you have the sdk installed, just open SDK Manager.exe in the sdk\ folder

hralzarwi said:
I think no , please see the message
Click to expand...
Click to collapse
Well the CMD images you post earlier shows no issues when it flashes the factory images. That archive does contain bla bla bla is normal. Seems your device is not properly detected in adb. But the try this, when you are in fastboot type fastboot device. See if your device is listed.

Johmama said:
Well that is kind of weird, espeically considering you just got a bunch of 'OKAY' messages. Does a device come up if you type 'fastboot devices' while you're in the bootloader? If not, your drivers aren't quite installed correctly and this is an easier fix than what it could be. If so, then maybe try letting your phone sit at the Google logo. The initial start ups are usually long, maybe it just needs time.
If your device DOES come up in fastboot devices and you think you've given it enough time to start and it won't, then we might try to flash the images manually (even though it says they flashed successfully, which is annoying). Since you already have the factory image inside your platform-tools folder, try this:
1. Extract the image-occam-krt16o.zip into the platform-tools folder
2. You should now have, among other files, 6 .img files in your platform-tools folder Again, make sure those images are from an 'occam' image
3. Run these commands:
Code:
fastboot flash bootloader bootloader-mako-makoz20i.img
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
4. Once those are all done, try rebooting
This all might seem redundant, but this is a weird case and we're taking everything one step at a time. If you're still stuck, try updating your sdk and getting a newer fastboot.exe. If you have the sdk installed, just open SDK Manager.exe in the sdk\ folder
Click to expand...
Click to collapse
woooooooooooooooooooow you are great man
after I give him a time but it is very long time about 5 hours my device is work probably but when I restart it it is stuck on goggle logo
LOOOOOOOOOOOOOOOOOOOOOOL
what do you think why it is stuck now?

arffrhn said:
Well the CMD images you post earlier shows no issues when it flashes the factory images. That archive does contain bla bla bla is normal. Seems your device is not properly detected in adb. But the try this, when you are in fastboot type fastboot device. See if your device is listed.
Click to expand...
Click to collapse
MR.arffrhn
thank you too much for your help and what do you think now why it is stuck ?

hralzarwi said:
MR.arffrhn
thank you too much for your help and what do you think now why it is stuck ?
Click to expand...
Click to collapse
So your device is working now? Well there are many that complained that their device got stuck in google screen after upgrading to 4.4. And the solution to that is a simple factory reset. If you can boot into system and still stuck on google screen, you can try this. http://forum.xda-developers.com/showpost.php?p=47846788&postcount=2

Well I'm confused as ****.
Tried to install 4.4. Failed. Was stuck on google circles. Fast forward , I gave up and tried to install 4.3.
....google logo for like 5 minutes. Then the "X" goes on forever.....
bootloader,rooted,etc,etc. Running PA 4.2 before this. Now all I want is a working phone lol.
google factory images ofc
---------- Post added at 01:17 AM ---------- Previous post was at 12:53 AM ----------
arffrhn said:
So your device is working now? Well there are many that complained that their device got stuck in google screen after upgrading to 4.4. And the solution to that is a simple factory reset. If you can boot into system and still stuck on google screen, you can try this. http://forum.xda-developers.com/showpost.php?p=47846788&postcount=2
Click to expand...
Click to collapse
no /system and /cache, can't sideload.... didn't apply that .zip update though?
After redoing it all with the .zip update.. no cache... TWRP still can't sideload.
android can be such a nightmare sometimes. I should have been done like 6 hours ago. Luckily, just a few minutes ago, I found this:
http://forum.xda-developers.com/showpost.php?p=44322165&postcount=30
And found that locking, then unlocking the bootloader FIXED THE PROBLEM!!!!
I hate android so much after this. I'll probably forget all about it like last time (lololol)

[Q] Google nexus 7 (2012) - Unrooting leads to total failure(no recovery, no boot up)

Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"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 think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated ​

Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk

Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )

Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid

Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk

I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?

Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet

Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...

Stock Nexus 7 (Wifi, 2012) Boot Loop and Soft Brick

Hey All,
So here's the deal, I have a nexus 7 Wifi 2012, and it's soft bricked into a boot loop. Some FAQS:
1) It boot loops forever.
2) Yes, I can get into fast boot.
3) The recovery image is currently destroyed, so even though I have the recovery option, it just boots to a 'Dead Android' Image.
4) Fastboot is currently locked.
5) USB Debugging mode was of off and because of the boot loop, I can't turn it on.
6) I've tried with ADB Fastboor, and with WugFreshs Nexus Root Tool (v2.1.0) to restore the recovery image, or the system itself, and I'm having no luck.
7) I've referred to threads such as this one: http://forum.xda-developers.com/showthread.php?t=2595736, and I still can't find a solution.
While I've tried many things, if I can solve getting the bootloader to unlock, then I'll be on my merry way. When I use the Nexus root toolkit, I follow the instructions to unlock the bootloader, I get the splash screen asking me if I want to unlock it, I select 'Yes', and then the device just powers off. It doesn't restart (Even though that's what it says it will do). If I turn it on at the power switch, I get 4 swirling dots (Which is different from the boot loop I get stuck on usually), and my PC tries to install a device driver called 'MTP USB Device', but it fails.
I've tried installing the Google drivers as per: http://developer.android.com/sdk/win-usb.html and here: http://developer.android.com/tools/extras/oem-usb.html and I'm confident I've done it right, but no dice. I suspect it's a drivers issue, but I'm getting really stuck on solving this.
Just as a note, when using ADB Fastboot, I get an unknown failed error:
{
"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 anyone assist?

If you can get into fastboot mode, have you tried flashing a custom recovery or are you unable to do that also?

TheGoldenMagikhrp said:
If you can get into fastboot mode, have you tried flashing a custom recovery or are you unable to do that also?
Click to expand...
Click to collapse
Hey,
Thanks for the response. I wasn't having much luck with a custom recovery, but my understanding was that I wouldn't be able to flash a custom recovery without unlocking the bootloader?
If you can recommend a recovery image for this device, I'd be more then willing to give it a second shot.

HDCerberus said:
Hey,
Thanks for the response. I wasn't having much luck with a custom recovery, but my understanding was that I wouldn't be able to flash a custom recovery without unlocking the boot-loader?
If you can recommend a recovery image for this device, I'd be more then willing to give it a second shot.
Click to expand...
Click to collapse
I would personally recommend the latest built of the TWRP recovery, that one seemed to work for me when I was stuck in a similar situation. Unless I'm mistaken, I have flashed recovery with a locked boot-loader before on the same device. If the recovery doesn't work, try downloading the 'Nexus Root Toolkit' (this should work assuming that your computer can recognize the Nexus in some way). What I'm primarily trying to achieve here is a custom recovery as it would be a good starting point for solving this boot-loop problem!

TheGoldenMagikhrp said:
I would personally recommend the latest built of the TWRP recovery, that one seemed to work for me when I was stuck in a similar situation. If the recovery doesn't work, try downloading the 'Nexus Root Toolkit' (this should work assuming that your computer can recognize the Nexus in some way). What I'm primarily trying to achieve here is a custom recovery as it would be a good starting point for solving this boot-loop problem!
Click to expand...
Click to collapse
Thanks, I'll try this when I get home and update. I've been using the 'Nexus Root Toolkit' and I'm getting a response from it, but was struggling after that. Will update with how it goes.

TheGoldenMagikhrp said:
I would personally recommend the latest built of the TWRP recovery, that one seemed to work for me when I was stuck in a similar situation. Unless I'm mistaken, I have flashed recovery with a locked boot-loader before on the same device. If the recovery doesn't work, try downloading the 'Nexus Root Toolkit' (this should work assuming that your computer can recognize the Nexus in some way). What I'm primarily trying to achieve here is a custom recovery as it would be a good starting point for solving this boot-loop problem!
Click to expand...
Click to collapse
Seems I've had no luck. The Device responds, but just times out when it tries to apply the recovery image. Here's the log from Nexus Root:
Nexus Root Toolkit v2.1.0
Masterlists:
- LatestToolkitFiles.ini 3105
- AndroidDeviceListFull.ini 3105
- AndroidDeviceListFlash.ini 3105
NAKASI-GROUPER: Android 4.1.0 - Build: JRN84D
Live log initiated [2015-12-18]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
015d3b65f653ec0a fastboot
Connectivity Status: Fastboot Device Connected
Temporarily Booting modified boot.img to enable running privileged commands...
fastboot boot "I:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Modified_Boot\modified_boot_nakasi_4.1.0_JRN84D.img"
Waiting for your device...
Any ideas what to try next?

HDCerberus said:
Seems I've had no luck. The Device responds, but just times out when it tries to apply the recovery image. Here's the log from Nexus Root:
Nexus Root Toolkit v2.1.0
Masterlists:
- LatestToolkitFiles.ini3105
- AndroidDeviceListFull.ini3105
- AndroidDeviceListFlash.ini3105
NAKASI-GROUPER: Android 4.1.0 - Build: JRN84D
Live log initiated [2015-12-18]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
015d3b65f653ec0afastboot
Connectivity Status: Fastboot Device Connected
Temporarily Booting modified boot.img to enable running privileged commands...
fastboot boot "I:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Modified_Boot\modified_boot_nakasi_4.1.0_JRN84D.img"
Waiting for your device...
Any ideas what to try next?
Click to expand...
Click to collapse
Does the same thing happen when to attempt to unlock the boot-loader?
Edit: Try using an alternate method to the tooklit, use the Windows drivers and open the command window in 'platform-tools' then use the 'fastboot oem unlock' command.
Edit 2: Can you also try flashing either a full stock ROM from Google or a Cyanogen Mod ROM via fastboot (using the command prompt method).

TheGoldenMagikhrp said:
Does the same thing happen when to attempt to unlock the boot-loader?
Edit: Try using an alternate method to the tooklit, use the Windows drivers and open the command window in 'platform-tools' then use the 'fastboot oem unlock' command.
Edit 2: Can you also try flashing either a full stock ROM from Google or a Cyanogen Mod ROM via fastboot (using the command prompt method).
Click to expand...
Click to collapse
Thanks for the help so far. I've tried all of these a few times, and the issue I have is I can't get the bootloader to unlock. If I try flashing the recovery, I get FAILED (remote: Bootloader is locked.) in the command line.
When I try 'fastboot oem unlock', this fails for some unknown reason, with the following in the command line:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 6.870s
And while the device does ask me if I want to unlock the bootloader, it freezes with an 'Unlocking now...' message in the top left, while it doesn't appear to actually unlock the device.
Is my device beyond repair, or is there anything else I can try?

HDCerberus said:
Thanks for the help so far. I've tried all of these a few times, and the issue I have is I can't get the bootloader to unlock. If I try flashing the recovery, I get FAILED (remote: Bootloader is locked.) in the command line.
When I try 'fastboot oem unlock', this fails for some unknown reason, with the following in the command line:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 6.870s
And while the device does ask me if I want to unlock the bootloader, it freezes with an 'Unlocking now...' message in the top left, while it doesn't appear to actually unlock the device.
Is my device beyond repair, or is there anything else I can try?
Click to expand...
Click to collapse
Well there's one final solution I can think of, keep in mind, there are many people on this forum and surely many others with the same problem, so there might be someone with a solution out there. But here's what I'm thinking. Download an extracted bootloader.img file and flash it to the Nexus 7. You see I would have suggested this earlier but the reason I didn't is because of the risks that come along with it, I wanted to try all the safe, reasonable options to see if they worked but clearly not. I would personally take extreme caution while doing this and only use it as a last resort. I'm so hesitant in recommending this solution as it can cause what is known as a hard bricked device (I'm sure you're aware what this is already) but basically it means your device could potentially never boot again.
If you want further help, let me know and I'll help but keep in mind that if you choose to do this, you're doing so at your own risk!

TheGoldenMagikhrp said:
Well there's one final solution I can think of, keep in mind, there are many people on this forum and surely many others with the same problem, so there might be someone with a solution out there. But here's what I'm thinking. Download an extracted bootloader.img file and flash it to the Nexus 7. You see I would have suggested this earlier but the reason I didn't is because of the risks that come along with it, I wanted to try all the safe, reasonable options to see if they worked but clearly not. I would personally take extreme caution while doing this and only use it as a last resort. I'm so hesitant in recommending this solution as it can cause what is known as a hard bricked device (I'm sure you're aware what this is already) but basically it means your device could potentially never boot again.
If you want further help, let me know and I'll help but keep in mind that if you choose to do this, you're doing so at your own risk!
Click to expand...
Click to collapse
Hey,
I appreciate the help so far, but I actually already tried this a while back, and the error I get then is:
sending 'bootloader' (2100 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.020s
So it looks like I can't unlock the bootloader as it's bust, and I therefore can't replace it with a working bootloader, and thus I'm stuck.....

HDCerberus said:
Hey,
I appreciate the help so far, but I actually already tried this a while back, and the error I get then is:
sending 'bootloader' (2100 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.020s
So it looks like I can't unlock the bootloader as it's bust, and I therefore can't replace it with a working bootloader, and thus I'm stuck.....
Click to expand...
Click to collapse
Hmmm, this is quiet a tricky situation, I was sure that I was able to flash a bootloader even with the current bootloader locked previously. I've completely run out of advice or solutions for the problem, the only other think I can think of doing is attempting to simulate the problem and have a play around with it myself, otherwise, I would suggest consulting Asus or Google with your issue. I'll let you know if I find another potential solution but in the meantime I would recommend either having a look around on the internet some more or looking to have it fixed by Google or Asus if you think it's worth it.

TheGoldenMagikhrp said:
Hmmm, this is quiet a tricky situation, I was sure that I was able to flash a bootloader even with the current bootloader locked previously. I've completely run out of advice or solutions for the problem, the only other think I can think of doing is attempting to simulate the problem and have a play around with it myself, otherwise, I would suggest consulting Asus or Google with your issue. I'll let you know if I find another potential solution but in the meantime I would recommend either having a look around on the internet some more or looking to have it fixed by Google or Asus if you think it's worth it.
Click to expand...
Click to collapse
Cheers, but I think I've hit the end of the road here. Into the trash it goes!

HDCerberus said:
Cheers, but I think I've hit the end of the road here. Into the trash it goes!
Click to expand...
Click to collapse
If that's what you think is necessary. Sorry I couldn't help.
Sent from my Xperia Z Ultra using Tapatalk

[solved] Can't unlock bootloader / flash recovery

EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
The phone is working perfectly again.
Also, if this problem appeared when you tried flashing OOS 3.0, check out this guide.
I did a lot of google research, found a lot of stuff and I'm still stuck at my problem.
Some background information:
I wanted to flash the new Oxygen OS 3.0 Community Build, decided to perform a clean install (full wipe with system, cache, dalvik and data).
Went into TWRP, wiped phone, installed OOS 3.0 - worked.
Made my initial setup, then I wanted to boot into recovery - didn't work.
Then I booted into fastboot, tried fastboot oem unlock, it said:
fastboot oem unlock
...
OKAY [ 0.014s]
finished. total time: 0.014s
Click to expand...
Click to collapse
Afterwards I checked fastboot oem device-info:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.080s]
finished. total time: 0.080s
Click to expand...
Click to collapse
That means still locked.
The phone won't boot up by itself.
I had to go in fastboot, and then use "fastboot continue" to get into the OS.
At the beginning, I forgot to enable the 'Allow OEM unlock' option in developer settings, it is now enabled but effect remains the same.
My question:
How do I fix my obviously broken recovery? How can I reflash it with a locked bootloader or how do I even unlock the bootloader.
PLEASE do not link me to the unbrick guides - the device is NOT bricked - it boots up with fastboot continue and also shows up as ONE A2003 when connected to pc.
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Thanks in advance for your help & ideas!

Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS

Tierri said:
Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS
Click to expand...
Click to collapse
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003

GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
hum. Ask Naman Bahlla for help.

GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
When you try to flash a recovery, what error message do you get? Curiosity question.
But I'm gonna have to echo Tierri to use that unbricking method. I get you're not bricked, but that will work to fix your issue. To get the Qualcomm device thing to show in device manager, power down your phone completely. Then connect the USB cable and press VOL UP (don't press power). You should hear the Windows connection chime. Also make sure you're booted up with Windows Device Driver Signature check turned off.
EDIT: I've followed these directions in the past: http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543

I did the same thing.
Only way is boot to system (fastboot continue) backup all files from internal memory to pc,
Restore device completly as Tierri said using method 3 unbrick guide.
Unlock bootloader in system (oos 2.2.1 or 2.2.0).
and flash oos 3.0 beta with twrp from that thread: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Thanks for all your replies!
As you all suggested, I decided to go through the Bhallas unbricking guide on the OnePlus forums.
This seemed to be the quickest solution out there.
I'll update the Original post with the solution, thanks.
If mods see this, thread can be closed, tagge the thread as solved.

The real op oem fix
follow these steps:
1. launch your cmd
2. plug out your phone
3. power it off
4. power into fastboot
5. plug it into the pc
6. type these commands
"adb start-server"
"fastboot devices" (your device should show in fastboot)
"fastboot oem lock" (this will reboot your phone and reset everything make sure you backup if you need to)
7. skip all OP setup steps(skipping these steps saves your time cause this process will have to be done twice also put into DEV mode and allow usb debugging)
8. once you on your homescreen power off your OP
9. plug it out of the pc
10. put it back into fastboot
11. type these commands before plugging back into pc
"adb kill-server"
"adb start-server"
12. plug it back into the pc and type these commands
"fastboot devices"
"fastboot oem unlock" (sometimes it will prompt you in some kind of asian language asking if you want to reset all your data just click the first option this will also reset your phone again)
that should fix the OEM boot unlocker now
i made this solution my self after troubleshooting like crazzy cause i had the same problem like you but didnt have to do all the extra bs with download random crap that does not really help
~xjinx216

is your bootloader unlocked now after following naman's process? please help, i've been having the same problem for ages.

I'm having this issue as well. Tried every driver and just can't seem to unlock bootloader. Adb seems to work, can boot into fastboot but then it always says fastboot cannot be detected when I try anything. Or it gets stuck on waiting for device. I just want to get this thing rooted????

Im having the same issue and my device IS bricked (and im sure i may have somehow deleted my OS) And i can't do anything to fix it, but if i deleted/corrupted my OS can it still be oem locked?

Solution
GerRudi said:
EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
Click to expand...
Click to collapse
I had about the same problems with my phone (oem unlock shows okay but doesn't unlock, directly booted the not working recovery) i was then able to boot to system with "fastboot continue".
Solution i found (root needed): flash stock recovery (from oneplus 2 downloads section) in rom with "dd" command and do a oem unlock, it will then boot to stock recovery, where you have to confirm the unlock (works with all roms but only with stock recovery).
command used to flash recovery (in android terminal emulator, adb should work too): dd if="location of recovery.img to flash" of=/dev/block/bootdevice/by-name/recovery
You can also flash twrp on a locked bootloader like this (just make sure to have a stock recovery ready on the device).
You might want to include this in front page.

GerRudi said:
EDIT:
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Click to expand...
Click to collapse
I got into exactly the same situation now, the problem is that "Method 3 in Naman Bhalla's thread" is not working for me as it break on "sahara error". Actually the message says to restart phone and retry, but I'm always getting into this error again and again. I already tried to reinstall drivers many times and I'm running in testing mode... what else I can try to solve this? (Windows 10 Pro)
{
"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"
}

fastboot,unlock wont work

Hi All,
Loving my Nexus 6P but noticed after several of the OTA updates that the battery is getting worse so decided to do a factory reset, The May update hasn't come OTA yet either so thought might as well kill to birds with one stone.
Installed ADB tools on my Ubuntu machine and a quick "abd devices" brings the phone up, OEM Unlock is allowed in the developer options.
In fastboot mode "fastboot devices" also brings up the device.
so I then tried "fastboot flashing unlock" and it does nothing just brings up a list of all the options, I'm on adb 1.0.32 IIRC so the "fastboot OEM unlock" doesn't work either.
Anybody had this before, cant get it to unlock.

I noticed you said you checked oem unlock but didnt mention that you enabled usb debugging. Did you do that as well?

Yes sorry, debugging is enabled.

I used a pc but there is an article for this phone using linux (Debian/Ubuntu). You may have seen it but if not maybe this will help you out.
http://forum.xda-developers.com/nexus-6p/general/guide-unlock-nexus-6p-resorting-to-t3257388

When you initially plug phone in,were you prompted on phone to allow PC to connect to phone?
Sent from my Nexus 6P using XDA-Developers mobile app

Yes it came up and asked me if i wanted to allow fastboot or something similar, I accepted.

Fe Mike said:
I used a pc but there is an article for this phone using linux (Debian/Ubuntu). You may have seen it but if not maybe this will help you out.
http://forum.xda-developers.com/nexus-6p/general/guide-unlock-nexus-6p-resorting-to-t3257388
Click to expand...
Click to collapse
I will give this a go tomorrow! looks like it might resolve the issue.

ur on a ubuntu machine, so i cant help
but i got my wife a Nexus 5X the other day and it threw me on a loop when i couldnt "fastboot flashing unlock" since it will say "waiting on device".... im not new to this, been rooting and flashing since 2010..... and i had eom unlock and adb debug selected.... adb on android would give me serial... but not on fastboot..
came to find out i had to right click on device manager and update driver to "Android ADB Interface".... it worked fine after that
long story.... sounds to me like you may have a driver issue on ur machine connecting to the phone since the only difference between ur problem and mines is the computer used

AndrewJB88 said:
Hi All,
Loving my Nexus 6P but noticed after several of the OTA updates that the battery is getting worse so decided to do a factory reset, The May update hasn't come OTA yet either so thought might as well kill to birds with one stone.
Installed ADB tools on my Ubuntu machine and a quick "abd devices" brings the phone up, OEM Unlock is allowed in the developer options.
In fastboot mode "fastboot devices" also brings up the device.
so I then tried "fastboot flashing unlock" and it does nothing just brings up a list of all the options, I'm on adb 1.0.32 IIRC so the "fastboot OEM unlock" doesn't work either.
Anybody had this before, cant get it to unlock.
Click to expand...
Click to collapse
The problem is that your fastboot is out of date. If you're using the adb/fastboot that's native to your distro it won't work. You need to download the Android SDK and update the platform-tools package, then use that version of fastboot. Navigate to the platform-tools folder, select to open a command prompt in that location, and then issue your fastboot commands locally. This means you need to prefix each command with "./", so the commands would be like this:
Code:
./fastboot devices
./fastboot flashing unlock

chaco81 said:
ur on a ubuntu machine, so i cant help
but i got my wife a Nexus 5X the other day and it threw me on a loop when i couldnt "fastboot flashing unlock" since it will say "waiting on device".... im not new to this, been rooting and flashing since 2010..... and i had eom unlock and adb debug selected.... adb on android would give me serial... but not on fastboot..
came to find out i had to right click on device manager and update driver to "Android ADB Interface".... it worked fine after that
long story.... sounds to me like you may have a driver issue on ur machine connecting to the phone since the only difference between ur problem and mines is the computer used
Click to expand...
Click to collapse
It isn't a driver issue, adb and fastboot are native to Linux so no drivers are required.

Heisenberg said:
The problem is that your fastboot is out of date. If you're using the adb/fastboot that's native to your distro it won't work. You need to download the Android SDK and update the platform-tools package, then use that version of fastboot. Navigate to the platform-tools folder, select to open a command prompt in that location, and then issue your fastboot commands locally. This means you need to prefix each command with "./", so the commands would be like this:
Code:
./fastboot devices
./fastboot flashing unlock
Click to expand...
Click to collapse
I initially had the Ubuntu ADB tools installed but then installed the newer version over the top but that didn't resolve it either. I didn't get round to trying the guide above.

I didn't get round to fixing this, I decided to jump straight to developer preview 3 OTA which I was already running on my Nexus 9.
Battery seems a lot better.

AndrewJB88 said:
I initially had the Ubuntu ADB tools installed but then installed the newer version over the top but that didn't resolve it either. I didn't get round to trying the guide above.
Click to expand...
Click to collapse
Did you actually install the SDK from scratch? And remember to issue the prefixed (./) commands from within the platform-tools folder?

AndrewJB88 said:
I didn't get round to fixing this, I decided to jump straight to developer preview 3 OTA which I was already running on my Nexus 9.
Battery seems a lot better.
Click to expand...
Click to collapse
To update your SDK Platform-Tools package, which has the ADB, open command prompt and type
android update sdk
In the gui option select platform-tools and then OK.
{
"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"
}

Heisenberg said:
It isn't a driver issue, adb and fastboot are native to Linux so no drivers are required.
Click to expand...
Click to collapse
Thank you sir for the proper correction to my post.

I don't know if you ever resolved this, but I was having the same issue. At first I updated the sdk via manager. No luck. Then I did a complete new install, over the old. No luck. I then did a search for android to find the sdk folder on my computer to make sure there wasn't a duplicate. Turns out, the fresh install created a new location for the sdk. The one I used was still old, despite the update, apparently. I opened the new location, which was shown to have been created at the time of the new install. Ran the command, and it worked flawlessly.
Hope u worked it all out already, but if not, I'm sure urs was the same issue. I've been trying to get this done for hours. Finally got it unlocked!
Good luck

PS C:\> fastboot devices
CVH7N15A14007144 fastboot
PS C:\> fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.037s]
finished. total time: 0.037s
PS C:\> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
PS C:\> fastboot flashing unlock
usage: fastboot [ <option> ] <command>
any suggestion?
Note: USB Debugging and OEM unlocked before I experienced another bootloop.

Heisenberg said:
The problem is that your fastboot is out of date. If you're using the adb/fastboot that's native to your distro it won't work. You need to download the Android SDK and update the platform-tools package, then use that version of fastboot. Navigate to the platform-tools folder, select to open a command prompt in that location, and then issue your fastboot commands locally. This means you need to prefix each command with "./", so the commands would be like this:
Code:
./fastboot devices
./fastboot flashing unlock
Click to expand...
Click to collapse
Tut Tut-- You the man, thanks it woked, most of all it make sense.-:laugh: