Database Users

Nexus S Forgot Security PIN

Hey all,
Hopefuly someone can help me otherwise i'm going to have to take this phone back to the o2 shop where I got it from.
I have a Nexus S, was looking at custom roms the other night and decieded to unlock and root it and flash the CyW7 rom onto it.....after a couple hours of playing with the new software I decieded it wasn't for me so flashed the device back to stock 2.3.1 software.
2.3.1 loaded fine and I installed the 2.3.2 update before rooting it so I could install adblock.
Got it all working fine, setup a security PIN (8 digits) and went to bed.
Woke up this morning and found the phone was not accepting the PIN, ive tried rebooting, trying the PIN in different varations incase I setup a wrong PIN in the first place......still no luck
So, i've looked into reflashing the device with stock 2.3.1 software again but USB debug mode isn't on and I can't install the USB drivers in Fastboot mode (says no compatible driver found for my hardware error)
How do I move forward here? Is there anything I can do to fix it?
Thanks a billion for anyone who gives me advice....

Boot into recovery and factory reset.

Boot recovery took me to a error screen where I had to take battery out to reset it.
I've managed to get the USB drivers to work now, and flashed the clockwordmod recovery image, then reset the phone.
Can I just confirm;
Is this the correct proceedure for the Nexus S to stop the Clockwordmod recovery from been removed.
1. Download the custom recovery image and save it to your computer
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe)
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of each line:</p><p>fastboot flash recovery recovery.img
4. Once it is flashed, leave the phone in plugged in and in fastboot mode.
6. Root the Phone
7. In fastboot mode, select Recovery using the volume buttons and power button and wait for it to boot into recovery mode.
8. Download the Superuser flashable zip file and save it to your computer.
9. Once in recovery mode, select Mounts and Storage then select Mount USB Storage so we can transfer files to the sd while it is in recovery mode.
10. Copy the Superuser.zip file to the root of your internal storage (do NOT extract it, do NOT put it in any folders, just on the phones storage itself).
11. Select Unmount on the phone.
12. Select Mount System, then select Go Back to get back to the main menu.
13. Then scroll to flash zip from sdcard and then choose zip from sd card and select the superuser.zip file and wait for it to finish flashing.
14. Once it is done, select Go Back then Reboot System and wait for the phone to reboot.
15. Stop the Phone from Uninstalling the Custom Recovery Image
16. Once the phone is booted up, plug it in via USB cable and do NOT mount the storage.
17. Open a command prompt on the computer and type the following with hitting enter at the end of each line:
adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh.
18. Turn off the phone and turn it back on by holding down Volume Up and Power to get into fastboot mode.
19. Plug the phone in via USB cable while in fastboot mode and open the command prompt again and type the following with hitting enter at the end of each line:
cd c:\androidsdk\tools\
adb reboot bootloader
fastboot flash recovery recovery.img

rom installed not rebooting stuck on unlocked screen

hey anything please i wiped everything and installed zip"rom" from sd and installed secussful and then i clicked reboot and it just stays on the motorola screen with unlocked in the corner and is stuck there what am i not doing or doing wrong its rooted and unlocked

INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"

clod007 said:
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
Click to expand...
Click to collapse
i made a back up with titanium and android recovery....
i pulled the battery installed it 2 or 3 times and same thing
what exactly do i type in my cmd prompt on fastboot

If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"

clod007 said:
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
Click to expand...
Click to collapse
i dont know how to reinstall it but i made back ups of everything

Enter in Android recovery mod
Backup
Chose restore
Atrix - "CM7"

Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight

android-DEP said:
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
Click to expand...
Click to collapse
ok it rebooted and went off the screen now its in a boot loop and flashes the motorola sign then shuts down and keeps going

ok, so the issue was partly the cache not being wiped prior the rom being installed and something went wrong with the installation of the kernel. That happens if the boot.img didnt properly extract and write to partition or its just incompatible with the rom\device.
Visit faux123's thread with kernels for ATT froyo, GB, CM7 & CM9
download the kernel that's compatible for your rom(froyo, gb, cm7 or cm9). Once you download the zip, go in there and pull out the "boot.img" file and put it into the same folder you have fastboot.exe in and boot into fastboot again.
quickly check connectivity with "fastboot devices" to verify and if that checks out, use this command.
"fastboot flash boot boot.img"
it takes like 3 seconds or something to complete so its an easy fix, after its done just do the "fastboot reboot" command.
i had this same exact issue last week plus my recovery was being erased along with this problem so i keep boot.img & recovery.img just sitting inside the fastboot folder just in case
atrix reboot project - it has every single file thats for the atrix and copies of systems, roms, tools, recovery files, mods, tweaks

Try this:
Pull battery
Replace battery while holding volume down until you see fastboot
Tap volume down to until you see android recovery, then press volume up to enter recovery
First try wiping cache/dalvik, if that doesn't work restore nandroid backup, if that doesn't work reflash rom

[Q] No USB debugging, can I adb?

Back story: Nexus 7 2012 WiFi, unlocked, rooted, TWRP, ROM'd
Tried to stock to 4.3. Power + volume down = Android on his back. can scroll Start, Restart Bootloader, Recovery Mode, Power Off. Select anything but Power Off and "booting failed" pops up in top left corner.
Anyone.....Anywhere.....Any IDEAS?
Without access I can't turn on USB debugging. I am no pro, but I'm not new. I have spent days trying to breathe life into this dude and I am at my end.

You don't need debugging to use fastboot. Look at the sticky at the top that says how to restore a factory image or something like that.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
You don't need debugging to use fastboot. Look at the sticky at the top that says how to restore a factory image or something like that.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
Exactly, fastboot has absolutely nothing to do with a switch within Android such as that of USB debugging. You have two courses of action; either flash stock images as suggested or proceed to flash a custom recovery, from which you can flash any custom ROM.

let me try again...
Via terminal: adb finds no devices; fast boot returns with a number for a device found, but when you flash from fast boot... nothing actually happens. I assumed that USB debugging was a moot point, but it seems most of the direction's you read a always start with "turn on USB debugging". When I go through and type in erase this, reboot that it say failed. Is there any caveman way of replacing fast boot? As I said, the cable is good, the USB port is good, I have gone at it through both Windows 7 Pro 64bit and Linux Mint 15 and I believe I have tried every suggestion I could find on the web. I will check the sticky above as suggested but I am stumped.

Fastboot and adb are not cross compatible. You cannot expect adb commands to work work in fastboot just as you should not expect fastboot commands to work in adb.
You have not actually stated WHAT you have tried in fastboot. What commands are you typing and what files are you using? You ask how to replace fastboot yet that is not possible nor is it sane to even think to replace it. Fastboot is there for a reason.
Sent from my Galaxy Nexus

boot into recovery TWRP
goto advanced > adb sideload
on your pc command prompt goto adb (where ever your sdk is installed) and push the rom image to root directory
after that's done, cancel out of adb sideload and go back to main. do a wipe (factory reset, cache, dalvik cache, system) and go back to main.
click install and find the rom image (click internal storage on top)

Open Source Paul said:
Via terminal: adb finds no devices; fast boot returns with a number for a device found, but when you flash from fast boot... nothing actually happens. I assumed that USB debugging was a moot point, but it seems most of the direction's you read a always start with "turn on USB debugging". When I go through and type in erase this, reboot that it say failed. Is there any caveman way of replacing fast boot? As I said, the cable is good, the USB port is good, I have gone at it through both Windows 7 Pro 64bit and Linux Mint 15 and I believe I have tried every suggestion I could find on the web. I will check the sticky above as suggested but I am stumped.
Click to expand...
Click to collapse
Let us try, AGAIN. ADB and FASTBOOT are 2 DIFFERENT programs. Stop trying to use ADB to reinstall the OS. At the top of this page there is a sticky that literally holds your hand through the FASTBOOT command process. Read that. Forget for the time being that ADB exists. Think of it as ADB ONLY exists if you have a working OS. You currently don't so you NEED to use FASTBOOT.
Flashing a factory image using fastboot/restore to stock
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.23.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jwr66v.zip

[Q] N4 stuck in boot loop after OTA update

Hello,
I saw that the OTA update to Lollipop was available on my phone today, so I went ahead and let it download. Upon completion of the download, it restarted and applied patches, then restarted again and has been stuck in boot loop for about an hour. After reading several other threads on how to try to reset the phone, I'm stuck. When I try power + volume up or down, the LED status indicator flashes red and I never get to any kind of other screen. Am I completely screwed? I previously had stock 4.4.2 with no modifications.

Finally was able to get to the bootloader menu. Apparently having the phone plugged into the charger was preventing me from getting there for some reason. I ended up having to wipe the phone to get it to boot

so you can get into clock recovery right? download nexus 4 toolkit..that might save your phone. I suggest you to unroot and flash everything to stock and then unlock again and start everything from scratch. good luck.

Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?

Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
I guess TWRP Recovery has option to enable MTP and you can access the internal SD card by connecting mobile with computer using usb cable.
---------- Post added at 06:37 PM ---------- Previous post was at 05:37 PM ----------
Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
Flash TWRP Recovery using fastboot.
1. If you have otg y cable, connect it and use file manager to copy all the files.
2. OTG method is failed then select “Mount”, then select only “Data” and connect your Nexus 4 to your computer and Enable MTP in TWRP. now you can use adb pull and push commands.

I ended up going the factory reset route, which wasn't really a bad thing. My photos had been backed up in dropbox and the play store remembered all the apps and were able to reload them. The only things I really had to do was reload some music onto the phone and re-enter passwords for apps.

Same story here: sideloaded the OTA zip file, then had bootloop. Tried a few approaches, but none worked. In the end only wiping the data was the solution for me. Lost some userdata in a few important Apps...

I went through this yesterday. The only way to get it to boot is a Factory Reset from Recovery. It works like magic, but sucks you lose the data.

Got the OTA yesterday and also got a bootloop(stuck in boot screen animation). I couldnt afford losing my photos/videos as i had no backup , so i figured out a super easy to get it to boot without wiping data .
I was unrooted with stock recovery running stock 4.4.2, bootloader was unlocked. I flashed CWM recovery through fastboot and wiped chache+ Dalvik from there then simply rebooted the phone .
I had already tried wiping cache from the stock Android recovery,needless to say that didnt work for me.
If anyone else is having the same problem please try the method above and report back, cheers!

I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/for...Q/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexu...image-t2010312 + HelpMyNexus

nexus 6p updated to android 8.0 stuck in recovery mode reboot cycle

Hello,
Today I got a prompt to update Android to 8.0.0. Not sure why this came for the first time only now, I've been on version 6 for over a year.
After updating I got a notice that data was corrupt, and I must either retry recovery mode boot or factory reset.
Needless to say I don't want to reset and lose all data.
I have downloaded ADB and rebooted into Bootloader but cannot get the device to show up in my PC in order to backup data.
while in bootloader adb devices returns no results
fastboot devices returns my devices serial ## fastboot
however, when I try to enter recovery mode I just get the data corrupt loop again and ADP can't see anything.
d I'm not sure what the correct fastboot command is to backup or create an image that will allow device to boot.
If I use fastboot to load a flash will it wipe my user and app data? are there any other options to make a backup?
Thanks!
UPDATE:
After holding down power button for 15-20 seconds got a longer boot cycle. then going into boot loader and selecting Recovery Mode twice in a row I was able to get into normal recovery mode with full options. now trying to wipe cache and sideload using ADB but no resolution yet.
Note ADB NEVER showed my device when queried, even though it showed up in fastboot, but if I unplugged and plugged the USB and then just ran the ADB sideload command it is working.
https://productforums.google.com/forum/#!topic/nexus/cwyTP3gr10s;context-place=topicsearchin/nexus/nexus$206p$20can$27t$20load$20android
OPR6.170623.019 does not work
OPR5.170623.014 does not work
Tried OPM6.171019.030.E1 based on above link. IT WORKED!!
suggestion: go with latest build not your current which is causing issues.