Database Users

I'm bricked .. Getting worries. (Yes I've read the forums ...)

Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "ADB reboot loader" or ..."fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!

Rovon said:
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Click to expand...
Click to collapse
Use Wugfresh's toolkit and press "return to stock"

rohan32 said:
Use Wugfresh's toolkit and press "return to stock"
Click to expand...
Click to collapse
"I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen. "

Here's an update:
I think I've made it worse ...
Nothing will boot now and it's currently locked. Any time I hit "Start" it says "Booting Failed"
My CMD now says; Error: Cannot Load "Bootloader Grouper-3.34.img"
I'm seriously lost. I've been working on this for about 6 hours now ....

Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??

markj338 said:
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
Click to expand...
Click to collapse
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"

Rovon said:
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Click to expand...
Click to collapse
Where does it say boot failed? On the device?

markj338 said:
Where does it say boot failed? On the device?
Click to expand...
Click to collapse
Yes. Top left hand corner.

Rovon said:
Yes. Top left hand corner.
Click to expand...
Click to collapse
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?

markj338 said:
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
Click to expand...
Click to collapse
No I can't get into the recovery at all. When I turn on the device I don't even need to use the rocker keys to get into bootloader either. Actually my bootloader is a bit different now too. I have the 'Google' logo and at the top the regular options for Start, Recovery, Power Off, etc.
In simple terms: I can't even get to the animated splash screen anymore

Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.

Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app

Alkaloid said:
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I've followed the instructions in the file. From previous research, I've had these files. My device does communicate with Fastboot. When I give the command for Devices it gives me my serial. Also, when I ask it to reboot-bootloader in CMD it does.
My issue is when I get to "Fastboot flash bootloader-grouper-3.34.img". CMD states "Error: Cannot load bootloader-grouper-3.34.img"
I've followed the commands previous to that. (Erase boot, cache, recovery, system, userdata)
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Click to expand...
Click to collapse
Yes my device is unlocked again, but I still can't get into recovery mode. It just tells me "Recovery Failed" in small text in the upper left hand corner of my N7.

UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
For the love of God..stop using the toolkit from here on out.. learn how to use ADB and Fastboot so you can avoid these issues.
Sent from my Galaxy Nexus using Tapatalk 2

So you erased the recovery then wonder why you could not boot into recovery....
You flashed or tried to flash the bootloader. You already had the same bootloader installed and there was no need to do so to try and fix your issue.
You still don't know what you're doing and are back using the tool that lead you to this issues. A toolkit. Learn what you're doing and you wont face this type of silly issue again.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
I think you should reread this post and hit the thanks button of everyone who took the time to help you out of this mess - its good manners. Oh, and learn how to use adb & fastboot
Sent from my Nexus 7 using xda premium

Inaccessible boot loader :/
If you try to fastboot flash all you get nothing?
Sent from my Nexus 7 using xda app-developers app
---------
nvm you fixed it, good job
Don't use toolkits. Most people don't have a clue what the toolkit is actually doing so if something goes wrong they aren't in a good position

Its always nice to see threads like these where the N7 in the face of death but in the end with cutting edge medical technology it is brought back to life and healthy.

[Q] Botlooped/Bricked Nexus 7 from build.prop mod recovery help?

Hello. I'm new to this forum and I joined because I was searchingother forums like nexus4nexus7 for a way for me to play Modern Combat 2 on my Nexus 7.
I couldn't find any threads specific enough to fit my needs. Perhaps I didn't look hard enough, but I figured I'd give it a shot.
To do this I decided to use the build.prop of a Nexus 4, because it has a Tegra 2 which the game supports, unlike the badass Tegra 3 quad core processor of the 7.
So I replaced the original build.prop, making a backup of the stock. I rebooted, and it never responded since.
I have used the bootloader screen, but accessing the recovery program from that just said, "no command." In no manner was fast boot or any other of the options doing anything to help me.
I am/was unlocked and rooted obviously, and I would really like to not lose my music.
I believe I have TWRP but I have no honest idea how to get to it.
I would appreciate a way to retrieve my files and restore it, or even better revert it back to it's glorious rooted days with no loss of data. Thanks for the help!

LouisMarshall said:
Hello. I'm new to this forum and I joined because I was searchingother forums like nexus4nexus7 for a way for me to play Modern Combat 2 on my Nexus 7.
I couldn't find any threads specific enough to fit my needs. Perhaps I didn't look hard enough, but I figured I'd give it a shot.
To do this I decided to use the build.prop of a Nexus 4, because it has a Tegra 2 which the game supports, unlike the badass Tegra 3 quad core processor of the 7.
So I replaced the original build.prop, making a backup of the stock. I rebooted, and it never responded since.
I have used the bootloader screen, but accessing the recovery program from that just said, "no command." In no manner was fast boot or any other of the options doing anything to help me.
I am/was unlocked and rooted obviously, and I would really like to not lose my music.
I believe I have TWRP but I have no honest idea how to get to it.
I would appreciate a way to retrieve my files and restore it, or even better revert it back to it's glorious rooted days with no loss of data. Thanks for the help!
Click to expand...
Click to collapse
As far as I know TWRP has a built in file manager, so just boot in the bootloader, select recovery with the volume up/down keys and press power to confirm. In TWRP you use the file manager to overwrite the build.prop with your backup / to delete the build.prop and copy the backup back. Should work (if you just replaced the build.prop and not anything else). No data will be lost when you try it
If it's not working I could upload a flashable .zip that replaces the build.prop with your old one :good:

mihahn said:
As far as I know TWRP has a built in file manager, so just boot in the bootloader, select recovery with the volume up/down keys and press power to confirm. In TWRP you use the file manager to overwrite the build.prop with your backup / to delete the build.prop and copy the backup back. Should work (if you just replaced the build.prop and not anything else). No data will be lost when you try it
If it's not working I could upload a flashable .zip that replaces the build.prop with your old one :good:
Click to expand...
Click to collapse
Thanks for your reply. Recovery does not work for me. It just says "no command" when I select it. Good Idea though.

LouisMarshall said:
Thanks for your reply. Recovery does not work for me. It just says "no command" when I select it. Good Idea though.
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes, download the latest TWRP recovery image and boot in the bootloader. Then use fastboot to flash it
Code:
fastboot flash recovery twrp-recovery-image-name.img
That's it. Then you are able to use TWRP :good:

If your bootloader is unlocked, fastboot should work for you, I.e boot the device into fastboot mode, then flash TWRP recovery again by
fastboot flash recovery <recovery.IMG>
and after that a
fastboot reboot recovery
From there you are able to copy back your old build.prop file either by using the file manager or by using adb:
adb mount /system
adb cp /system/build.prop.back /system/build.prop
adb reboot
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
If your bootloader is unlocked, fastboot should work for you, I.e boot the device into fastboot mode, then flash TWRP recovery again by
fastboot flash recovery <recovery.IMG>
and after that a
fastboot reboot recovery
From there you are able to copy back your old build.prop file either by using the file manager or by using adb:
adb mount /system
adb cp /system/build.prop.back /system/build.prop
adb reboot
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It might have been a .bak
Also can you describe to me exactly how to boot into fastboot.
I am unlocked and rooted.
Is adb an external program? I have a mac at the moment.
- - - - - - - - - - - - - - - -
fastboot flash recovery <recovery.IMG>
fastboot reboot recovery
How do I enter these commands? With adb. Can I use adb on a mac? Thanks for your quick response.

mihahn said:
Is your bootloader unlocked? If yes, download the latest TWRP recovery image and boot in the bootloader. Then use fastboot to flash it
Code:
fastboot flash recovery twrp-recovery-image-name.img
That's it. Then you are able to use TWRP :good:
Click to expand...
Click to collapse
Just tried booting into bootloader. Now I have this eternal ant race going on.
I can no longer access fastboot. And it seems the same goes for my bootloader.
Uhm any other ideas. I had no Idea how to boot into bootloader... so I followed this guys intruction from android forums, "Hold Vol Up + Vol Down + Power until it shuts off, then Vol Down + Power to boot into bootloader." It's like static but with lines. This is a new problem, is it not only a software, but a hardware issue now? Or is it just not charged? Thanks a million for your help so far
***It seems it was a problem with the charge... its fine now. Can get into bootloader ***

Did your pc detect the device?
Turn off your device and turn on during the google logo press and hold volume down +power until you see android ley down. Then try vol up or down to see recovery hit power. Good luck
Sent from my SPH-D710 using xda premium

LouisMarshall said:
***It seems it was a problem with the charge... its fine now. Can get into bootloader ***
Click to expand...
Click to collapse
Now that you are able to get in the bootloader, just flash the recovery image and try replacing the build.prop
Sent from my Nexus 4 running Android 4.2.2

mihahn said:
Now that you are able to get in the bootloader, just flash the recovery image and try replacing the build.prop
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
Okay... How do I flash the Recovery Image? Thank

evobb10 said:
Did your pc detect the device?
Turn off your device and turn on during the google logo press and hold volume down +power until you see android ley down. Then try vol up or down to see recovery hit power. Good luck
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It won't detect it. When I select recovery it says, "No Command" huh

LouisMarshall said:
Okay... How do I flash the Recovery Image? Thank
Click to expand...
Click to collapse
Either you use a toolkit for Mac to flash the recovery or you install fastboot and adb (android sdk) for Mac on your PC. Then there will be a program named fastboot. You download the recovery.img, place it in the same directory where fastboot is and type in the fastboot console:
Code:
fastboot flash recovery recovery.img
To boot into bootloader turn off the device and press power and volume down at the same time
If it's too hard with fastboot, use a toolkit for Mac like I said. Should work too
Btw you need the build.prop backup as a build.prop (in your sdcard) or build.prop.bak (then just delete the build.prop and rename the build.prop.bak if renaming is possible in TWRP file manager). Then reboot and it should work :good:
Sent from my Nexus 4 running Android 4.2.2

mihahn said:
Either you use a toolkit for Mac to flash the recovery or you install fastboot and adb (android sdk) for Mac on your PC. Then there will be a program named fastboot. You download the recovery.img, place it in the same directory where fastboot is and type in the fastboot console:
Code:
fastboot flash recovery recovery.img
To boot into bootloader turn off the device and press power and volume down at the same time
If it's too hard with fastboot, use a toolkit for Mac like I said. Should work too
Btw you need the build.prop backup as a build.prop (in your sdcard) or build.prop.bak (then just delete the build.prop and rename the build.prop.bak if renaming is possible in TWRP file manager). Then reboot and it should work :good:
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
I have the adb and fastboot programs from the sdk on my mac and know how to execute them, but when I use "adb devices" it can't detect it. As long as it can't detect it, it seems like both of your methods are obsolete. I have to be in bootloader for it to recognize the nexus 7 right? I'll try your method regardless and report back. Thanks so much for your help!!
Should I use TWRP or CWM Recovery images? Or if neither which?

LouisMarshall said:
Should I use TWRP or CWM Recovery images? Or if neither which?
Click to expand...
Click to collapse
Use TWRP because it should have a file manager built in
Sent from my Nexus 4 running Android 4.2.2

mihahn said:
Use TWRP because it should have a file manager built in
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
Yes I used TWRP and it does have a file manager (THANK YOU!) ... but it doesn't seem to see the build.prop and build.prop.bak in the system folder... Does it have root permission? Can I refresh? You've been great so far! xD So close!

Probably you need to mount /system first, because in recovery normally no system and/or data partitions are mounted automatically. There is an option innTWRP, too, to mount /system.
Sent from my Nexus 7 using xda app-developers app

LouisMarshall said:
Yes I used TWRP and it does have a file manager (THANK YOU!) ... but it doesn't seem to see the build.prop and build.prop.bak in the system folder... Does it have root permission? Can I refresh? You've been great so far! xD So close!
Click to expand...
Click to collapse
All the other folders in the system folder are present and only the build.prop is missing?
If you can't go on by mounting system and data like the guy above said, I could upload a flashable .zip which flashes the old build.prop back
Please tell us on which Android version you were before (4.1.2/4.2.2) and which model you own (wifi only/3g) :good:
Sent from my Nexus 4 running Android 4.2.2

mihahn said:
All the other folders in the system folder are present and only the build.prop is missing?
If you can't go on by mounting system and data like the guy above said, I could upload a flashable .zip which flashes the old build.prop back
Please tell us on which Android version you were before (4.1.2/4.2.2) and which model you own (wifi only/3g) :good:
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
I have the WiFi only model. It was running on 4.1.2. I'll try mounting system first because looking back I can't even browse the root directory. I see a flashable zip that would be nice... well I only had data and cache mounted! Yes the build.prop is showing up! And the .bak! I fixed it LOVE you guys. Thanks a million you guys were a great help! DDD

AndDiSa said:
Probably you need to mount /system first, because in recovery normally no system and/or data partitions are mounted automatically. There is an option innTWRP, too, to mount /system.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks that was what I was missing

LouisMarshall said:
I have the WiFi only model. It was running on 4.1.2. I'll try mounting system first because looking back I can't even browse the root directory. I see a flashable zip that would be nice... well I only had data and cache mounted! Yes the build.prop is showing up! And the .bak! I fixed it LOVE you guys. Thanks a million you guys were a great help! DDD
Click to expand...
Click to collapse
Great it works again! Enjoy your device now
And next time please don't play with system files if you don't know exactly what you are doing or simply do a nandroid backup before (in TWRP or cwm) which you can restore if something goes wrong

Nexus 4 stuck in bootloader no recovery

hello i tried to download and flash paranoid ROM on my nexus 4 after some time i dnt like it so try to revert back to nexus 4 stock rom but something went very wrong and now my phone stock in boot loader
wen i try to switch on my phone it directly goes to boot loader i cnt do anything if scroll down and go to recovery my phone went black and its also not starting that.
wen try to connect my phone to computer to recover it ...most of the tool kits showing msg that u dnt have usb debugging on
Please help how to recover my phone

I had that issue once with when flash back from PA. I have to flash IMG files using a toolkit
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 08:06 AM ---------- Previous post was at 08:04 AM ----------
This is the took kit that I used and I had no debug on
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4

Zehlek said:
I had that issue once with when flash back from PA. I have to flash IMG files using a toolkit
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Can u please tell me whice toolkit i should use and what is the procedure to do that many thanx

You'll have to do it the old fashioned way, i.e. use fastboot. If you're not familiar, don't rush it, research each step and ensure you have the drivers set up, adb and fastboot installed, etc...
Did you flash the stock recovery back on? IIRC once selecting Recovery from the bootloader you're presented with a black screen, and then must hold the power button for a second or two and then the stock recovery will show up. Limited options available however, wipe data, cache, etc...
http://forum.xda-developers.com/showthread.php?t=2010312

core81 said:
Can u please tell me whice toolkit i should use and what is the procedure to do that many thanx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
First select 1 to install drivers. Then download Google factory image and put Boot, System, Recovery in folder(to flash IMG files) in your toolkit folder. Then use option 11 to flash each one. Make sure you are in bootloader mode

axtzenswas
Zehlek said:
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
okay i ll try and get back to you..but should my computer can identify the device in boot loader mood?
any way i ll try the stock recovery method also and get back to you guys
many thanx for your time

core81 said:
okay i ll try and get back to you..but should my computer can identify the device in boot loader mood?
any way i ll try the stock recovery method also and get back to you guys
many thanx for your time
Click to expand...
Click to collapse
fastboot commands work from BL, adb doesn't. So long as the drivers are installed you will be able to see your phone.

https://developers.google.com/android/nexus/images#occam
That is the link to the factory images for the nexus 4.
http://forum.xda-developers.com/showthread.php?p=42407269
That is the fastboot you will need. (FOR WINDOWS)
turn off the phone and plug it in to fully charge it.
install fastboot
extract the files from the factory image into the fastboot folder.
turn on the device and leave it in the bootloader. (if need be turn off the device and hold vol up and down plus the power until you see bootloader)
run "fastboot devices", this will list any devices that fastboot sees. if your device is not in the list something more is wrong.
This images shows "adb devices" but it is the same output for "fastboot devices" https://sites.google.com/site/rodsmods13/_/rsrc/1370839220039/home/example screenshot.png
now run the "flash-all.bat"

dl200010 said:
...now run the "flash-all.bat"
Click to expand...
Click to collapse
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.

CMNein said:
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
Click to expand...
Click to collapse
Yeah I completely forgot that! I don't have the image downloaded to look at to list the commands to install without using the bat file.

dl200010 said:
Yeah I completely forgot that! I don't have the image downloaded to look at to list the commands to install without using the bat file.
Click to expand...
Click to collapse
bat file is definitely the way to go however*, I've grown to hate typing terminal commands :laugh:
*Except for that one time I forgot to edit stuff

CMNein said:
bat file is definitely the way to go however*, I've grown to hate typing terminal commands :laugh:
*Except for that one time I forgot to edit stuff
Click to expand...
Click to collapse
I admin three Linux headless servers, so it is like second nature to me. Maybe best route for him is for one of us to modify the bat and post it.
Sent from my Nexus 4 using XDA Premium 4 mobile app

CMNein said:
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
Click to expand...
Click to collapse
my frnd can u please explain little bit more about the process

THANKS TO CMNein dl200010
MY PHONE IS BACK TO NORMAL
thanks alot

core81 said:
my frnd can u please explain little bit more about the process
Click to expand...
Click to collapse
One you have the factory image in hand and have the following files extracted to your platform-tools folder, you'll want to keep on opening the archives until you're left with the following, but don't extract anything from the zip file:
-bootloader-mako-makoz20i.img
-radio-mako-m9615a-cefwmazm-2.0.1700.84.img
-image-occam-jwr66y.zip
-flash-all.bat
You'll want to open the image .ZIP and delete userdata.img.
Then open the flash-all.bat and delete the -w as seen on line 23 in the screen capture.

core81 said:
THANKS TO CMNein dl200010
MY PHONE IS BACK TO NORMAL
thanks alot
Click to expand...
Click to collapse
Awesome, I see you got yourself sorted out while I was replying :highfive:

[Q] Boot doesn't go beyond rotating circles. Help!!

I tried to search, but in vain.
Hardware: Nexus 4
Software : Android 4.4.4
For reasons that are not clear to me the machine restarted and is stuck in those 4 rotating circles, and doesnt go beyond it. Tried multiple things such rebooting, rebooting into recovery and booting again, tried adb to see if it can see the machine in recovery mode, but to no avail.
Can someone please help? Thanks in advance.

Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot. Is there a way to press some button and hard reset it?

Concoran said:
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot.
Click to expand...
Click to collapse
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Click to expand...
Click to collapse
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.

Concoran said:
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Click to expand...
Click to collapse
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?

Concoran said:
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Click to expand...
Click to collapse
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.

Concoran said:
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Click to expand...
Click to collapse
Flash the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
I installed both TWRP and CWM alternatively, installed factory images using flash-all.bat, install CM11. But in both cases, 1. factory image : The system get stuck in boot mode where those 4 circles keep rotating around each other, 2. In CM11, the arrow keep rotating indefinitely.
I don't know what else I can do.
Any pointers? Thanks in advance.
I am beginning to suspect hardware malfunction. In which case, is there a log somehow I can see?
As an Aside: 1. Adb refuses to see the device in fastboot mode. Not sure if this is an expected behavior. Fastboot can.
2. Stock Android USB Drivers never work. I had to get the WugFresh Development drivers.
This is Windows 8 environment.

jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics

Concoran said:
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Click to expand...
Click to collapse
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Click to expand...
Click to collapse
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.

Concoran said:
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Click to expand...
Click to collapse
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Click to expand...
Click to collapse
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.

Concoran said:
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Click to expand...
Click to collapse
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Click to expand...
Click to collapse
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'

Concoran said:
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Click to expand...
Click to collapse
Ok, you can't use that file (tgz) in cwm, adb or fastboot. What you can do is extract it and then use the zip file. But, you'll have to boot into the bootloader and then use the command
fastboot update update.zip
Sent from my Nexus 5 using XDA Free mobile app

[Q] help please nexus 4 cant go back to stock

hello everyone
im pretty new to the forums but have always seeked help from here so i know this is probably the best place to get more help.
so my nexus four is a little messed up. i had an error regarding "com.android.systemui" so i tried to factory reset but it still popped up over and over. i then accidently wiped everythin off my phone including the OS.
so i used skipsoft toolkit do work on my phone so i tried to use it to help me but everytime i try to load google stock image from the options but i get an extraction error and keeps getting errors when extracting the .tar file.
and i cant seem to push files to my phone so i can install via recovery. so im all confused and i downloaded the stock firmware from google.
any advice would be great.
and im stuck on the google logo and i can get into recovery and fastboot mode and the lock state is unlocked.
thanks

You need to be able to boot into fastboot to flash a factory image. If your phone is rebooting in a loop hold vol down and power for about 10 seconds (until the phone shuts off) then let go of power, continue to hold vol down and it should boot in fastboot.
If that's successful then you can try flash a factory image, you'll need fastboot drivers working (I use koush universal driver) and fastboot.exe in the same directory as the factory image (or added to your cmd path). If everything's good you can click the flash-all.bat in the factory image to flash your phone back to stock.
The factory image comes a compressed tar, I've noticed when you download it the extension is wrong sometimes, make sure you have a .tgz file (rename if necessary) and winrar/7zip will extract it fine.
If you can't get into fastboot you need this guide http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

Flash the factory image in fastboot. Google nexus 4 image for the image to flash.
Sent from my Nexus 5 using XDA Free mobile app

DrFredPhD said:
You need to be able to boot into fastboot to flash a factory image. If your phone is rebooting in a loop hold vol down and power for about 10 seconds (until the phone shuts off) then let go of power, continue to hold vol down and it should boot in fastboot.
If that's successful then you can try flash a factory image, you'll need fastboot drivers working (I use koush universal driver) and fastboot.exe in the same directory as the factory image (or added to your cmd path). If everything's good you can click the flash-all.bat in the factory image to flash your phone back to stock.
If you can't get into fastboot you need this guide http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
hey thanks..so yes i can get into fast boot but im not too good cmd or anythin like that. so koush universal driver is that easy to use?

jd1639 said:
Flash the factory image in fastboot. Google nexus 4 image for the image to flash.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok silly question, how do i flash the image in fastboot ? sorry im still a noob haha

wink4lif said:
ok silly question, how do i flash the image in fastboot ? sorry im still a noob haha
Click to expand...
Click to collapse
Google 15 second adb install xda. That'll setup fastboot and install the drivers. After you download the factory image, extract it. In there you'll find a flash-all.bat. Boot into the bootloader, connect your device to the usb and simply double click the flash-all.bat. It'll wipe your device so back up first.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Google 15 second adb install xda. That'll setup fastboot and install the drivers. After you download the factory image, extract it. In there you'll find a flash-all.bat. Boot into the bootloader, connect your device to the usb and simply double click the flash-all.bat. It'll wipe your device so back up first.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
perfect thanks, once i manage to download it ill give it a shot. thanks