• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Bootloop - No Recovery - No USB Debugging

Alright, since your device comes up as as a bootloader interface, we need to test it. Creat a new folder on your desktop for putting files in. Download our mini-sdk from our site, and unzip all the files into that folder your created.

Next we need to download the Nexus factory image from here. Once again extract everything into that folder you created on the desktop. Don't extract the zip file that comes out of the tgz.

Once that is done, we should test your driver. Open that folder and then hold ctrl + shift and then right click. You should see an option to open command prompt here. Once open, type the command:


Let me know what the output says.

The link you provided doesn't working. Same issue on my nexus 4 please help.
 
Upvote 0
The link you provided doesn't working. Same issue on my nexus 4 please help.

Here's an updated link to the Mini SDK:

http://androidforums.com/attachments/faqs/71016d1400442113-adb-guide-updated-2013-05-21-sdk-tools.zip

(located in this post: http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081)

The Nexus factory images link is still good.

Also, please see this excellent page for additional help and instructions:

http://androidforums.com/android-system-mods-scripts-hacks/706533-guide-how-flash-nexus-factory-image-manually.html

Cheers and best of luck!
 
Upvote 0
Hi i really need someone's help...
i cannot complete the booting of my phone nexus 4 but i can only go to custom recovery however i am not able to make my device discoverable by the PC.
I could do anything if i only could connect it to the laptop: anybody can help?

thanks a lot in advance!

roberto

Roberto,

Apologies for not seeing your post until now--I'm guessing it's long past needed, but for others with USB connectivity issues, see the Universal Windows ADB Driver courtesy of Koushik Dutta as mentioned in this thread: [Guide]How to flash a Nexus Factory Image manually.
 
Upvote 0
Hey guys
I'm having a Lenovo a6000 plus smartphone .
Today i tried to flash a custome using TWRP custome recovery and the flashing completed successfully.
Then i hit "reboot now" and the phone was stuck in screen where the logo is displayed.
I tried to reboot it to recovery mod but it is just restarting to the logo screen.
USB Debugging is also not turned on in my phone .


So Please Help me.........
 
Upvote 0
Hi ! I am sorry if i can't ask my question because i have an other device but the same problem after installed super su I reboot my devices but it block. with adb on my computer i have ? anauthorized and i have not a custom recovery, i am on lenovo k3 note. i want to install a cmw recovery but adb don't work . and i have the official rom on my computer. Can you help me ? I read the threat but i have not understand and the file he downloaded is perhaps just for his Android.
 
Upvote 0
I'm completely new at this stuff, so please forgive my ignorance,

I was running PA 3.99, on a Nexus 4 and when the KitKat 4.4 aosp came out, I got curious. I downloaded it and tried to flash, it didn't work with TWRP, so I temporarily booted CWM using their playstore app and flashed 4.4, and after it asked me to get rid of the recovery.

I can't remember the exact wording, (it was late). It started to boot with the word "android" flashing in grey, it then booted for 7 hours. I tried to unroot and flash custom recovery using Nexus Root Toolkit 1.7.3, but it said "can't find fastboot device" I tried to reinstall the drivers, but USB debugging wasn't enabled, so I can't.

I then booted into stock recovery and on the advice of another forum I wiped data.

Now it won't get past the google sign.

It's still unlocked and I can get into bootloader mode.

In essentials, these are my problems:

Since I have no recovery, I cannot restore a backup
Since I can't restore, I need to flash stock and unroot
To do that my computer needs to find my phone as a fast boot device, but it can't.
To make it see my phone, I need to install the right drivers
To install the drivers I need USB debugging enabled
To turn on USB Debugging I need to not be in a bootloop

Does anybody see a way around this?

Thank you so much for this post first of all..My phone had a similar problem as yours and everywhere i searched on the internet (xda forums, you tube...etc) the solutions were posted for phones which had custom recovery installed..but not in my case where the phone had never been modifiedin any way..but i have been able to solve this problem with Wugs toolkit mentioned in one of the above posts by @scary alien (thank you so much !!) ..I want to post my problem in detail and how i arrived at the soluion so it can help others who run into the same situation because as i already said this problem is a little unique in the way that most devices running into a bootloop have usually been tinkered with and got soft bricked while either trying to install a custom ROM or being manipulated in some way,,but in my case I didnt even know what a custom ROM or custom recovery meant ( until 2 days back when my phone ran into this bootloop issue),,
Here I am posing the link again for wugs toolkit posted by @scary alien for those who dont want to scroll and search all the way up

http://forum.xda-developers.com/showthread.php?t=2015469

(I'm sorry i am new to these forums i'm not sure how to quote that message, I hope I get it right...)

Ah, cool, megsto! :thumbup:

Welcome to our AndroidForums (but sorry it's under these circumstances) :).

I've moved you over to the Nexus 4 all-things-root area as previously mentioned.

Not totally sure if there are newer USB drivers for adb and fastboot available since I posted that GNex thread, so you might want to take a peek here in the N4 ATR area for what they guys here have posted.

Hopefully the good folks in here will be able to get you going in short order.

Cheers!

edit: there are two root toolkits you might try:


(don't know which one you had previously used; I usually do my stuff manually so I'm not really familiar with the above toolkits other than they automate the manual processes for you).


Here is what happened to my phone in detail--

Phone --- NEXUS 4 (Mako)
android version - 5.1 (i think this was the last official android OTA update received for nexus 4 users )
phone status -- LOCKED , UNROOTED , NO CUSTOM RECOVERY installed ( NO CWM or TWRP) , running stock android .I have owned this device since 2013 but never fiddled with it...it has been running everything in factory condition - never rooted , unlocked or any custom ROM installed.

how the problem started- a few hours before my whats app was crashing constantly..whether it was the cause of the problem or the initial symptoms of something else that was wrong i do not know...I put the phone on charging and after a while when i tried to wake it up from sleep the screen was stuck at colourful circles logo that appear while loading android 5.1 version and it could not proceed ahead to the android logo..here's what i tried and didnt work-

1.restarting it a couple of times
2.let it restart overnight
3.enter bootloader and recovery mode--> factory reset and wiping cache partition
4.Mskip's Unified Android Toolkit (link in @scary alien post) although it did help in unloacking the bootloader but beyond that couldnt help much because the ADB access was not available.This could possibly be because
  • the developer options were turned off so USB debugging could not be turned on and since the phone was in a bootloop and unable to boot..thus the device was stuck with USB debugging off and to turn these on it needed to come out of the bootloop but it was that bootloop itself which prevented access to USB debugging (cause-effect-cause infinite loop).
  • there was an issue with the drivers installed...the device manager showed the phone as MTP device under the portable device options when plugged in via USB cable. it did detect the phone in the bootloader state as it showed up in the device manager as bootloader state under the Lemobile android device option.Now it shows up as nexus 4
  • device-manager.gif
Thus without ADB access or custom recovery only thing that was possible was flash a stock android ROM..honestly I did not expect it to work and I could say i got lucky because that was the only option availble and i was like lets go with it what do I have to lose ..
and mind you, I had taken my device to an
authorised LG service centre the same day and the engineer said it was a hardware issue with the motherboard and it needed replacement.

Finally the steps i followed on how to re install the factory image using WUGs toolkit (usinf the software is very simple and self explanatory ...the software is designed with easy to follow steps and provides help at every step.)

1. Select the correct device and the android version
2. Reinstall the drivers... test them using the "test full driver test " under step 4. Dont expect them to work but install them anyways
step-1---driver-installation.gif


3.Unlock the Bootloader (if not already done so)
step-2--unlock-bootloader.gif



4. The most important step is now to install the stock ROM after selecting the soft brick/bootloop option under the same heading.

flash-stock-image.gif



5.Now wait for 10-20 minutes.This is important because it takes time to boot the first time after flashing stock image.Try not to freak out if it doesnt boot in first 5 minutes, be patient it will reboot completely now.!!

It would be a good idea now to install a a custom recovery like TWRP and make a NANDroid backup ...just in case.
A big big thanks to @scary alien and the original poster ..you guys have no idea how happy I was ..and of course saved me $$$$ ..i owe you guys :)
 
  • Like
Reactions: scary alien
Upvote 0
Guys, I'm having a similar problem. I'm just stuck in the CWM Recovery mode, Advanced back up and restore... Will my battery run out? I have a Xperia C, I can't get it running, can't go back to any screen, can't go back to anything. The volume bottoms just switch to rainbow mode, It sucks... The power and the camera bottom have the same function, it's a turn on, turn off function... Can someone help me?
 
Upvote 0
Do you have a nandroid backup?
you can try and restore it... Let me know if it works
Did you try and let it drain the battery completely and then try to restart the phone ? Maybe it will boot normally,..
Otherwise if the USB debugging was enabled before ( assuming you can't access it now since the phone is stuck on recovery screen), You can try to flash the factory ROM
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones