Database Users

I can't enter recovery console & I have tryed EVERYTHING !!!

I'm just trying to enter recovery console. I have tryed EVERY button combination & used a computer to just did use SDK. Any help would be GREAT ! Thank you

Just to make sure: you need to release the button at the right time.
Turn off your phone and take out the battery for 5 sec then put the battery back. Then hold power+vol up + vol down together and once you see the Vibrant logo, release the power button immediately WHILE pressing vol up+vol down.

That didn't work tryed 3 times.
Sent from my SGH-T959 using XDA App

Have you tried via adb:
adb reboot recovery
I had difficulty getting to recovery when I reflashed the stock ROM via ODIN. But once it was rooted and I got Clockwork Recovery back on there, I haven't had an issue via the button combination t get into recovery.

I will try that thx for the info.
Sent from my SGH-T959 using XDA App

GalaxyS_Bweb2185 said:
I'm just trying to enter recovery console. I have tryed EVERY button combination & used a computer to just did use SDK. Any help would be GREAT ! Thank you
Click to expand...
Click to collapse
I was on the same boat as you. I just gave up and did the one-click root process. It wasn't exactly one-click, but it was simple enough. Now I've got the Clockwork ROM manager, which will let you boot into its recovery through the application itself.

I downloaded the one click lag fix app that roots your phone & fix the lag but I just can't get into recovery mode.
Sent from my SGH-T959 using XDA App

I was in the same boat then read to do the 3 button thingy but do not let go of anything until the 2nd time the word vibrant comes up then let go of everything...after hours of frustration,i can't believe how easy it was....not sure why this tip is not in a sticky or easily found on xda.
Sent from my SGH-T959 using XDA App

that does not seem to work. I am pretty sure the newer models have this disabled somehow.

Not true, I just bought my vibrant yesterday and I can get into recovery console just fine...
Sent from my SGH-T959 using XDA App

are you rooted?
Download a terminal emulator from the market.
then do
su
reboot recovery

JakeRadden said:
Not true, I just bought my vibrant yesterday and I can get into recovery console just fine...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
What date code is on your vibrant box? I am on my second phone both built in august and the buttons do not work on either. I had to root via adb recovery. The earlier built phones are rumored to be fine. Dosent seem to matter when you got the phone more when it was made.

My first Vibrant got into recovery no problem, I received a replacement phone which would not get into recovery using the hardware buttons. I called T-Mobile and told them of the problem and they sent me out a new phone. This last one boots into recovery first try. I know there is a common problem with some Vibrants out there not booting into recovery, thankfully T-Mobile will exchange if it won't.

Let me check when I get back home. Is this a t-mobile acknowledged issue with vibrants now?
Sent from my SGH-T959 using XDA App

When mine gets finicky, I just plug it to my Windows machine, Enable USB Debugging, open the command prompt, and type "adb reboot recovery" without quotes. Works every time. You can also use "adb reboot download" to get into download mode.

andryga said:
I was in the same boat then read to do the 3 button thingy but do not let go of anything until the 2nd time the word vibrant comes up then let go of everything...after hours of frustration,i can't believe how easy it was....not sure why this tip is not in a sticky or easily found on xda.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
For what it's worth, this helped me.
Hold volume up, volume down, and power all together, wait for Vibrant to come for the second time, then let go of the power button but not the menu button. After another second, I let go of the volume buttons and instantly went into recovery.
Good luck.

I tried terminal and it said it was not permitted
Sent from my SGH-T959 using XDA App

Someone on the I9000 boards posted that recovery can also be invoked by heat! He used an oven, but suggested a hair dryer to be safe.

sabooher said:
What date code is on your vibrant box? I am on my second phone both built in august and the buttons do not work on either. I had to root via adb recovery. The earlier built phones are rumored to be fine. Dosent seem to matter when you got the phone more when it was made.
Click to expand...
Click to collapse
I agree with this one. My Vibrant has a date of 8/14/10, and for the life of me it will not button into recovery. I really have read every thread on the topic here as well as other android forums, and tried every combination (over and over).
Rooting was a no brainer with one touch, and with that, I can get to recovery easily. The problem I see, is in the event of a miss step somewhere down the line.
I can't tell you the relief that I felt doing a battery pull to button recovery with my G1(many times). When you are in a bootloop or the like, and nothing else will work, you just need that capability.
Sadly, my Vibrant will be going back because of this. I don't understand why they would hobble the devise this way. I'm sure they will get many more phones returned because of it.

You need to type su first.
From terminal:
su
reboot recovery
Sent from my SGH-T959 using XDA App

(Solved!) Cannot boot into fastboot

I have tried at least 10 times with no results. I power down the device, hold both volume buttons and the power button, and nothing. I do get a vibrate after about 2 seconds, but nothing on the screen and then it vibrates every 6-7 seconds until I let go of the buttons. Kind of disappointed as I was all nice and comfortable on the couch, ready to use the Nexus 10 toolkit to do the all-in-one.

Anyone else experience this problem?
Sent from my SCH-I535 using Tapatalk HD

jmcharles said:
I have tried at least 10 times with no results. I power down the device, hold both volume buttons and the power button, and nothing. I do get a vibrate after about 2 seconds, but nothing on the screen and then it vibrates every 6-7 seconds until I let go of the buttons. Kind of disappointed as I was all nice and comfortable on the couch, ready to use the Nexus 10 toolkit to do the all-in-one.
Click to expand...
Click to collapse
Try releasing then power button (but hold the other two) when you feel the first vibration. I've found that holding the power button can make a continuous reboot happen.
Sent from my Galaxy Nexus using Tapatalk 2

Tried that, but no luck. I also went a different route and tried to do it using mskip's toolkit in original android development. After installing the drivers and choosing the options to boot into fastboot, the device vibrated once and nothing showed up on the screen. BUT...when I refreshed the main menu the toolkit recognized the device as in fastboot mode. Really weird happenings with this, and starting to be concerned that my device has some issues. What point is a Google device if I can't unlock or root it?!
Sent from my SCH-I535

I've had the best luck holding the vol up/down button down first, then while that's down, pressing and holding power until the fastboot menu comes up.

Well, I am at a complete loss. Is this cause for replacement?
Sent from my Nexus 10 using Tapatalk HD

Hold all three buttons at the same time and wait for the vibration and release. It should work.
Sent from my DROID RAZR HD using xda premium

Ok, so, I'm not sure what to make of the recent events. Bottom line, I was booting to fastboot mode, but the screen was just blank. I followed the instructions via the toolkit just by selecting the buttons and hoping it was making the correct selections in fastboot mode. Now unlocked, rooted, and a happy man! Still not sure why the fastboot menu would not show up though.
Sent from my SCH-I535 using Tapatalk HD

jmcharles said:
Ok, so, I'm not sure what to make of the recent events. Bottom line, I was booting to fastboot mode, but the screen was just blank. I followed the instructions via the toolkit just by selecting the buttons and hoping it was making the correct selections in fastboot mode. Now unlocked, rooted, and a happy man! Still not sure why the fastboot menu would not show up though.
Sent from my SCH-I535 using Tapatalk HD
Click to expand...
Click to collapse
I cant get the toolkit to recognize my tablet in fastboot mode. Is there a soluton to the black screen?

If the toolkit does not recognize the device in fastboot, then there's a good chance you didn't install the drivers correctly. Did you follow the directions correctly to get the toolkit to recognize the device?
Sent from my SCH-I535

jmcharles said:
If the toolkit does not recognize the device in fastboot, then there's a good chance you didn't install the drivers correctly. Did you follow the directions correctly to get the toolkit to recognize the device?
Sent from my SCH-I535
Click to expand...
Click to collapse
I got my device unlocked and the device did install the drivers. However, the problem was not that. But here's the thing, my N10 never showed me the fastboot menu. But connected to the PC it does show its connected. I never saw the screen that confirms "do you want to unlock the bootleader" (it goes completely black and vibrates every 5 seconds).
Workaround to unlock: For anyone with this problem, I just had to "guess" that menu (I think its clicking the vol button down once and then the power button). For me it bootlooped. so I pressed the Vol+ and power and in fastboot I booted to stock recovery, from there just wipe factory settings, and voila.
Weird tho that my fastboot screen was completely black

El Niche said:
I got my device unlocked and the device did install the drivers. However, the problem was not that. But here's the thing, my N10 never showed me the fastboot menu. But connected to the PC it does show its connected. I never saw the screen that confirms "do you want to unlock the bootleader" (it goes completely black and vibrates every 5 seconds).
Workaround to unlock: For anyone with this problem, I just had to "guess" that menu (I think its clicking the vol button down once and then the power button). For me it bootlooped. so I pressed the Vol+ and power and in fastboot I booted to stock recovery, from there just wipe factory settings, and voila.
Weird tho that my fastboot screen was completely black
Click to expand...
Click to collapse
This is exactly how I had to do it. It's a 50/50 shot, since I think the options are yes or no. Apparently the problem is a little more common, as evidenced by this thread I started in Android General, http://forum.xda-developers.com/showthread.php?t=2018777
Sent from my Nexus 10 using Tapatalk HD

I am stuck at the flashing X....with the toolkit. Kinda at a lose right now.

mike02vr6 said:
I am stuck at the flashing X....with the toolkit. Kinda at a lose right now.
Click to expand...
Click to collapse
Reboot into boot loader, choose recovery, press all three buttons at top at same time if you don't have options to select, then factory reset. This will solve your boot loop.
Sent from my SCH-I605 using Tapatalk 2

The post above is correct. Same thing happened to me. Just factory reset and you should be good to go
Sent from my Nexus 10 using xda app-developers app

[Q] Cant Get into AP Fast Boot!

I accidentally,... . unknowingly wiped the RED "system" button in Safestrap 3.12 on my Droid RAZR M today. (I was suppose to be wiping the cash and dalvik, but missed) I'm a retard I know. :crying:
Now I cant get into AP Fastboot to restore the phone from this hard brick!
When I press the power button along with the volume buttons, the only thing that happens is the red Motorola 'M" appears for a few seconds then the safe strap screen appears with the little sad robot, but that's it no AP Fastboot. Pressing the on screen buttons to enter Safestrap Recover do not respond. Oh boy I'm afraid I really did it this time. Its on the charger but i don't know if its even charging with out as OS?
Battery power was at 60% before i bricked it (i think). RSD Lite or my PC for that matter don't even see the phone when its plugged in.
Can this be saved? Or do I need to take a trip down to the Verizon Wireless store?
Droid RAZR M
4.1.2 OTA
Rooted
Locked Bootloader
Safestrap 3.12
Partitioned 64GB SD card utilizing Linked2SD

You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2

sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Really? Well I hope your right. It gives me some hope. lol So do you have any idea of what alternative key combo i might have to use? Thank you for the reply.

Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2

http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:

sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! You were right! was able to get into AP Fastboot with a different button combo like u said. :victory:

shane1 said:
Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2
Click to expand...
Click to collapse
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect

bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
It worked! I utilized the NEWER version of Mat's utility and it did it!!! Woo Hoo!! Thank you so very much. Thank you all for all the speedy help.

SARM1084 said:
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect
Click to expand...
Click to collapse
hey no prob! i try to help as much as i can !

bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min

Halp
This thread saved my life, then killed me. The suggestion about the different keys was spot on, i got into fast boot mode, then ran that utility. It totally failed me, I must have killed my phone pretty dead, and now there are no more key combos (the suggested one worked at first but now its just making the screen go blank) to try to get back into fast boot to try again. any more suggestions? on the up side verizon just pushed that update so i figure i can blame that to attempt an exchange

Did you take the update before using that utility? If you did, which version did you use? If you were already updated, then you needed to run 1.20. If you ran the wrong utility, that will cause issues. Now, since you can't boot, it sounds like your battery is dead. When you get to the blank screen, plug it in and leave it to charge for a while.

I'm no expert by any means but I'll try to help as best i can. If not me I'm confident someone else will. Now, I apologize because I didn't understand your original post.
Could you elaborate a little more please?
1. What were you trying to do with your phone prior to things going wrong, if they went wrong at all.
2. you mentioned AP Fastboot. So IM going to assume that at least you can access it. (not the same problem that I was having) that's a good thing! lol
3. Are you utilizing a utility like the one by Matt? Or are you doing something else? Like flashing firmware etc.
4. What were you in Fastboot for? What were your intentions?
I hope this doesn't come over a condescending. Just trying to get a Clearer understand of your issue so we can help.
Sent from my XT907 using xda app-developers app

Sorry double post

PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Look at my previous post
Sent from my XT907 using xda app-developers app

Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app

PartyOnINSANE said:
Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No problems brother. Glad to see your up and running.
Sent from my XT907 using xda app-developers app

Stuck in a Boot Loop
PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.

gjhkl said:
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.
Click to expand...
Click to collapse
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.

RikRong said:
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.
Click to expand...
Click to collapse
I have done your steps and I get the menu up, but when I try to scroll down with the volume down button, it doesn't move. It just stays on "normal powerup". How can I fix this?

Did my Nexus 7 just die on me?!

Hi guys, just got a new Nexus 7, and I love it - or loved; 'cause it doesn't power on anymore.
When I took it out of the box, it told me it had to update to 4.3, which it succesfully did (I checked the about tablet section in the settings to make sure). After installing 4.3, I set it up and used it for a few days, until this afternoon. I was on the train and it said it had downloaded an update. I clicked it to see the changelog and was suprised to see that it said it had to upgrade to 4.3 again.
I ignored the update and stuffed the tablet in my bag.
Here's when the trouble starts. When I took it out, it was powered off. Holding the power button for a few seconds did nothing, neither did holding it long or pressing it shortly, or vol+ and vol- and power for fastboot. Suddenly it turned on again, but it was unusable because it kept spamming "unfortunately, process.gapps. has stopt. I rebooted it into safe mode, but this didn't help. After turning it off again, it now won't start again. I don't have USB debugging enabled and couldn't get to the setting so using fastboot commands won't work.
Could anyone please help?
Thanks a ton in advance!

It was stock? Sounds like it sit down in the middle of the update. I berry flashing the latest gapps would fix..
Sent from my Nexus 7 using xda app-developers app

markvdn said:
Hi guys, just got a new Nexus 7, and I love it - or loved; 'cause it doesn't power on anymore.
When I took it out of the box, it told me it had to update to 4.3, which it succesfully did (I checked the about tablet section in the settings to make sure). After installing 4.3, I set it up and used it for a few days, until this afternoon. I was on the train and it said it had downloaded an update. I clicked it to see the changelog and was suprised to see that it said it had to upgrade to 4.3 again.
I ignored the update and stuffed the tablet in my bag.
Here's when the trouble starts. When I took it out, it was powered off. Holding the power button for a few seconds did nothing, neither did holding it long or pressing it shortly, or vol+ and vol- and power for fastboot.
Click to expand...
Click to collapse
Isn't it volume down + power button to get into the bootloader?

BTW, it's not repeatedly updating TO 4.3, the updates are FOR 4.3. You'd see the build number in About changing, while version stays the same (4.3)

You do NOT need USB debugging on to use fastboot, only adb. Fastboot works independent of anything system related. That's the whole point of fastboot.

Where have you bought your device?
I think it's the best solution to return your device to the shop you bought it and request for a new one...

just power + vol down for fastboot (after power off)
than flash factory image.... lots of guides here.

Flashing the new gapps via cwm should fix it
Sent from my GT-I9505 using Tapatalk 2

meekrawb said:
Isn't it volume down + power button to get into the bootloader?
Click to expand...
Click to collapse
Yeah, some ****ty site got it wrong. I found out and unlocked the bootloader, which factory reset it. But now it won't boot at all.

Richieboy67 said:
It was stock? Sounds like it sit down in the middle of the update. I berry flashing the latest gapps would fix..
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That might be the case, power button must have been pressed in my pocket.
I'll try a flash of the stock rom later. I unlocked the bootloader and now it won't boot at all.

di11igaf said:
You do NOT need USB debugging on to use fastboot, only adb. Fastboot works independent of anything system related. That's the whole point of fastboot.
Click to expand...
Click to collapse
Yeah, figured that one out today. Problem was, fastboot and adb needed to be updated to verify the device.

GoneTomorrow said:
BTW, it's not repeatedly updating TO 4.3, the updates are FOR 4.3. You'd see the build number in About changing, while version stays the same (4.3)
Click to expand...
Click to collapse
Ah right, that makes more sense. Probably a wonky translation or i've misread the text. It didn't make any sense to me

Maybe you can try to use "Nexus Root Toolkit 1.7.2" and install a stock rom 4.3 from Google's repositories. But I'm not sure your tablet will let the computer modify anything if you did not accepted his ID on debugging menu.

[Q] Stock Nexus 4 - Committed Suicide (Stuck On Bootloader Screen)

Hey guys, long timer lurker but finally got an account today! But I'm afraid I don't come bearing good news
Little backstory: I had bought my sexy Nexy within the first 30 sec. that online orders were opened in the U.S. (and I managed to snag this puppy during class just in time). Suffice to say, I love my phone. Never rooted it, never blinged it out, as stock as they come.
Unfortunately, last night my phone was sitting on my desk and I noticed it had restarted by itself. Come to find out that it won't get past the bootloader screen (where the 4 google circles dance around, sorta like drunk hippies dancing in a field. Best analogy I could think of ). I've been searching online, and I've been finding a lot of mixed solutions to fix this issue. And even most of those applied only to rooted phones, or to people who bricked theirs while rooting.
I had backed my phone's data about a month ago, but my last month's worth of photos (mom & pops' 25th anniversary, mom's b-day, a bunch of awesome events with my friends, parties, etc) never got a chance to be backed up. Since I know how awesome the N4 forum is on here, I wanted help from you guys in regards to what I can do in order to backup/recover my data (or at least, the photos). I don't want to do a factory reset because I fear it would just wipe all data, and of course connecting it to my computer while it's stuck inevitably on the bootloader screen doesn't do anything.
Some important things to note/which might help:
I got the 4.4.3 update a few days ago, not sure if that did anything.
App sideloading is enabled on my phone (however, I'm not sure if I ever enabled the developed mode on my phone).
What options do I have in regards to recovering my pics/data from my poor Nexy?
I'm sorta willing to try anything at this point, because from what I've read, an eventual factory reset is inevitable.
Thanks for your help! :highfive:

Hi there,
Dont factory reset just yet. Are u able to go to recovery? If so, try just wiping cache and dalvik cache then reboot system.
Dont think your bricked.
Good luck and cheers.
Sent from my Nexus 4 using xda app-developers app

Sgace said:
Hi there,
Dont factory reset just yet. Are u able to go to recovery? If so, try just wiping cache and dalvik cache then reboot system.
Dont think your bricked.
Good luck and cheers.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hi! Would you mind walking me step-by-step through how I can go into recovery mode and wipe the cache/dalvik cache and then reboot? I don't want to mess up any steps and make my situation worse lol. What will the recovery-mode screen look like, and what options should I stay away from?
Thanks for your help! :laugh:

SidCurry said:
Hi! Would you mind walking me step-by-step through how I can go into recovery mode and wipe the cache/dalvik cache and then reboot? I don't want to mess up any steps and make my situation worse lol. What will the recovery-mode screen look like, and what options should I stay away from?
Thanks for your help! :laugh:
Click to expand...
Click to collapse
Turn off your phone. When it's off, power it on by pressing the power button and volume up button. It should bring you into recovery mode. Navigate using the volume buttons and select options using the power button.
If there's an option to "Wipe Cache/Dalvik Cache", choose that and you won't lose anything, first boot will take a while.
If there isn't any Wipe Cache option, there should be a "Wipe Data" option, this will reset the phone but things in the SD Card SHOULD NOT be erased (at least in custom recovery).
Can't provide screenshot cuz you can't do that on recovery mode and I've never use stock recovery.
Good luck.
Sent from my Nexus 4 using XDA Premium 4 mobile app

uchihakurtz said:
Turn off your phone. When it's off, power it on by pressing the power button and volume up button. It should bring you into recovery mode. Navigate using the volume buttons and select options using the power button.
If there's an option to "Wipe Cache/Dalvik Cache", choose that and you won't lose anything, first boot will take a while.
If there isn't any Wipe Cache option, there should be a "Wipe Data" option, this will reset the phone but things in the SD Card SHOULD NOT be erased (at least in custom recovery).
Can't provide screenshot cuz you can't do that on recovery mode and I've never use stock recovery.
Good luck.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@ uchihakurtz beat me to it:thumbup:
Well explaned, except for one thing:
Once u pushed power + volume up u will end up in bootloader mode. From here navigate with volume key to recoverymode and press powerbutton. Now u will end up booting to recoverymode. In here u can choose "wipe cache" and "wipe dalvikcache".
Good luck.
Sent from my Nexus 4 using xda app-developers app

Sgace said:
@ uchihakurtz beat me to it:thumbup:
Well explaned, except for one thing:
Once u pushed power + volume up u will end up in bootloader mode. From here navigate with volume key to recoverymode and press powerbutton. Now u will end up booting to recoverymode. In here u can choose "wipe cache" and "wipe dalvikcache".
Good luck.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
LOL, I never remembered whether it's up or down since there's always an advanced reboot option (for me), thanks for clearing it up dude

DO NOT wipe data in the stock recovery. It will wipe everything
This is tedious but will backup your device http://forum.xda-developers.com/showthread.php?p=20868527
Sent from my Nexus 5 using XDA Free mobile app

Sgace said:
@ uchihakurtz beat me to it:thumbup:
Well explaned, except for one thing:
Once u pushed power + volume up u will end up in bootloader mode. From here navigate with volume key to recoverymode and press powerbutton. Now u will end up booting to recoverymode. In here u can choose "wipe cache" and "wipe dalvikcache".
Good luck.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
So, if I have this correct, once the phone's off:
1) Press POWER and VOLUME + button at the same time to enter bootloader mode
2) Using VOLUME +/- key to navigate to RECOVERY MODE option
3) Press POWER button to select RECOVERY MODE option
4) Inside RECOVERY MODE, navigate to WIPE CACHE and WIPE DALVIK CACHE using VOLUME +/- button
Is that correct? And in step 1, is it POWER and VOLUME + or POWER and VOLUME - to go into bootloader mode? I keep seeing Power & Volume - in several threads when it comes to booting into recovery mode.
And secondly, should my phone be connected to my laptop during this entire process? Or just have the phone solo and foreveralone :crying: by itself?
Finally, once I complete Step 4, will me phone restart automatically or will I have to power it down + power it back up again?
Thanks!

jd1639 said:
DO NOT wipe data in the stock recovery. It will wipe everything
This is tedious but will backup your device http://forum.xda-developers.com/showthread.php?p=20868527
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Will this work even though my phone's stuck in the bootloader loop? From the gist of it, that post makes it seems as if your phone needs to be able to actually work in order to unlock the stock bootloader using that method along with Android SDK + Android SDK Platform tools.
Thanks again for the help!

SidCurry said:
Will this work even though my phone's stuck in the bootloader loop? From the gist of it, that post makes it seems as if your phone needs to be able to actually work in order to unlock the stock bootloader using that method along with Android SDK + Android SDK Platform tools.
Thanks again for the help!
Click to expand...
Click to collapse
If your bootloader is locked you're going to have a problem. With it locked there's no way you're going to be able to recover your files. Adb will work if you can boot into recovery
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If your bootloader is locked you're going to have a problem. With it locked there's no way you're going to be able to recover your files. Adb will work if you can boot into recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your help, I'm not extremely familiar with rooting/using ADB, etc so I'm having a huge panic attack.
What would you recommend is the best course of action? If I choose to pursue using ADB to backup my phone's data, would you please mind pointing me to the noob-friendly threads (or even help me yourself by holding my hand along the process ) for:
1) Step-by-step of how to properly install Android SDK and 1.a) How to enable ADB functionality?
2) How to correctly enter Recovery mode on my N4 (button combos) and whether I should attempt to wipe cache/Dalvik?
3) How to use Android SDK/ADB to backup my data from my nexus 4?
Again, I really appreciate your help. As you can imagine, I'm really worried about losing photos of some huge moments in my life and I'm slightly overwhelmed at the different methods people seem to be using (and trying to figure out whether those apply to me). Thanks.

SidCurry said:
Thanks for your help, I'm not extremely familiar with rooting/using ADB, etc so I'm having a huge panic attack.
What would you recommend is the best course of action? If I choose to pursue using ADB to backup my phone's data, would you please mind pointing me to the noob-friendly threads (or even help me yourself by holding my hand along the process ) for:
1) Step-by-step of how to properly install Android SDK and 1.a) How to enable ADB functionality?
2) How to correctly enter Recovery mode on my N4 (button combos) and whether I should attempt to wipe cache/Dalvik?
3) How to use Android SDK/ADB to backup my data from my nexus 4?
Again, I really appreciate your help. As you can imagine, I'm really worried about losing photos of some huge moments in my life and I'm slightly overwhelmed at the different methods people seem to be using (and trying to figure out whether those apply to me). Thanks.
Click to expand...
Click to collapse
To setup adb. Google 15 second adb drivers xda. That'll give you everything you need.
To boot into recovery you need to boot into the bootloader. Vol down plus power button. Then use the vol keys to navigate to recovery
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
To setup adb. Google 15 second adb drivers xda. That'll give you everything you need.
To boot into recovery you need to boot into the bootloader. Vol down plus power button. Then use the vol keys to navigate to recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Great, I'll give that a try and let you know how it goes.
I had a general question: When I boot into recovery, how do I find out if I have USB debugging enabled? Is there some way for me to find out if I did indeed enable it a while ago (I can't quite remember)?
And if I enter Recovery mode, is there a way for me to exit this mode and turn my phone off/restart it (or do I HAVE to select one of the options?) I want to go in and see if I have USB debugging enabled first, and then turn my phone off without wiping any caches, etc, and then download + setup ADB.
Thanks!

SidCurry said:
Great, I'll give that a try and let you know how it goes.
I had a general question: When I boot into recovery, how do I find out if I have USB debugging enabled? Is there some way for me to find out if I did indeed enable it a while ago (I can't quite remember)?
And if I enter Recovery mode, is there a way for me to exit this mode and turn my phone off/restart it (or do I HAVE to select one of the options?) I want to go in and see if I have USB debugging enabled first, and then turn my phone off without wiping any caches, etc, and then download + setup ADB.
Thanks!
Click to expand...
Click to collapse
After entering recovery and wiping both caches there is an option to reboot system. U can use this to boot your phone back up again.
(Sorry, it indeed is vol down + power button to enter bootloader menu) my bad
Sent from my Nexus 4 using xda app-developers app

@SidCurry did you made some progres in retreiving your data?
Cheers
Sent from my Nexus 4 using xda app-developers app