Database Users

[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 7 2012 (GSM) Booting Failed/No OS

i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)

niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:

Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?

cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??

Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5

niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796

Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:

UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig

Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.

As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5

^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.

where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks

None of the above
Sent from my Nexus 5

Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:

finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers

[Q] Wugfresh stucks on: send bootloader(1280kb)

Well, i tried to install stock Bootloader, stock recovery and stockrom with wugfresh tool under "Back to Stock", and so thats the problem:
When i try to send the bootloader, it stucks and the tablet posts under the infos on the bootloader screen: FASTBOOT STATUS - DATA00140000.
And thats it. I waited 2 hour, it still stucks on sending bootloader. So i downloaded the Unified Android Toolkit, install the fastboot driver and tick the option to install a new recovery... It still stucks on sending bootloader. In Youtube Videos, i saw, that the sending finished about 0,2 s. Thats 1280kb! Why doesnt work it on my tablet. I had root, but i didnt tick the usb debugging. So when i switch on my tablet, it comes to the bootloader, and its the activated bootloader( i can switch to recovery, reboot bootloader, power off, reboot system,..) and its unlocked. If i reboot into the recovery, it also comes to the activated bootloader. Its also when i tick the reboot system. So what can i do? Is it hardware bricked? Or whats the problem? I have the bootloader version MANTAMF01 and the H/W Version 8. Can anyone helps me?
And yes, i am the Admin on my PC

The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.

funkym0nkee said:
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just resolved this issue on my own about a minute before your response lol. The problem was that I wasn't using the stock USB cord. Holy cheese and rice, I've been sitting here for the past 5 hours at wits end trying to figure out the problem. My problem was exactly like MrCreeper's, it was just stuck on "sending 'bootloader'" with no progress whatsoever on either PC or tablet. Who woulda thunk the problem was simply that I was using the incorrect USB cord -_- *sigh*
Anyway, thank you for your prompt reply. I did use a few of your tips from your other posts when I ran into other problems trying to flash stock image, so cheers for that!

[Q] Nexus 10 stuck on Google logo

Hi I've done stupid thing for myself:
i tried flashing 4.4.2 stock rom. coming from 4.2 (i think) did the usual format data/cache. then rebooted then it loops on google logo. I can go to recovery mode.

So are you rooted? Custom recovery? Looking to flash stock? What bootloader do you have? Ota flash? Fastboot flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app

Hoygl3n said:
Hi I've done stupid thing for myself:
i tried flashing 4.4.2 stock rom. coming from 4.2 (i think) did the usual format data/cache. then rebooted then it loops on google logo. I can go to recovery mode.
Click to expand...
Click to collapse
Read this fourm I just help this user recover from the same thing!!
http://forum.xda-developers.com/showthread.php?t=2663286

lj50036 said:
Read this fourm I just help this user recover from the same thing!!
http://forum.xda-developers.com/showthread.php?t=2663286
Click to expand...
Click to collapse
demkantor said:
So are you rooted? Custom recovery? Looking to flash stock? What bootloader do you have? Ota flash? Fastboot flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hi i followed all the instruction till CMD and tried typing fastboot
and nothing came up.

This will help
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
This will help
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I still cant get fastboot up. ive used minimal fastboot and/or SDK Package. also changed the path for environmental variables.

So more info will help, usually the more info you give the faster your issues can be fixed
Are you in bootloader mode? I take it your using windows, what version? Has adb or fastboot ever worked before? When you type
fastboot devices
You get nothing? Can you post a screen shot of terminal, of environmental variables? Are all proper drivers installed? Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? Are you using factory USB cable?
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
So more info will help, usually the more info you give the faster your issues can be fixed
Are you in bootloader mode? I take it your using windows, what version? Has adb or fastboot ever worked before? When you type
fastboot devices
You get nothing? Can you post a screen shot of terminal, of environmental variables? Are all proper drivers installed? Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? Are you using factory USB cable?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry about that.
im in fastboot mode with power and both volumes pressed. i can also go into recovery mode TWRP v2.5.0.0
also rooted and yes windows 7 64 bit. recovery mode or fastboot mode . it doesnt recognized my nexus.
not sure if i have the right drivers. i cant find any drivers to download for nexus 10
Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? - No
and yes im using nexus 10 OEM cable.
i really appreciate the time to help me out with this issue.

Its no problem,
The SDK should have the drivers you need, or you can install the universal drivers made by koush or a number of others as well. Just Google search or a search xda for terms like
Nexus 10 drivers
Universal android drivers
Android naked drivers
You will find many that will work just fine for you
If in cmd you type
fastboot
And you see a list of commands than you know you have it installed
When you type
fastboot devices
And you see your serial number your good, if just a blank line then you need to get tab to communicate, this is most often a driver issue. If you can't find ones that work let me know and I'll link some to you, also you may need to uninstall old drivers and than manually install new ones, windows doesn't always do the best job of picking the correct drivers
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Its no problem,
The SDK should have the drivers you need, or you can install the universal drivers made by koush or a number of others as well. Just Google search or a search xda for terms like
Nexus 10 drivers
Universal android drivers
Android naked drivers
You will find many that will work just fine for you
If in cmd you type
fastboot
And you see a list of commands than you know you have it installed
When you type
fastboot devices
And you see your serial number your good, if just a blank line then you need to get tab to communicate, this is most often a driver issue. If you can't find ones that work let me know and I'll link some to you, also you may need to uninstall old drivers and than manually install new ones, windows doesn't always do the best job of picking the correct drivers
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
finally found the driver that works and now
i get R32D2009DAT
Im assuming thats serial number whats the next step

Google search
Android factory images
Here you will download the correct one, latest manta for the nexus 10
Then extract the contents of the zip
Now if you want to keep custom recovery that's a good idea but if you want KitKat you will need stock or at least update to the newest twrp (as you current one won't flash kk)
So if you want twrp then google search
Twrp recovery manta
And then find the latest image, 2.6.x?
Oh and its a good idea to check md5sum for both the zip from android source and for the recovery image, both will tell you what it should be in download screen and there are many ways to check, just google search
Windows md5
There is both official and none official, I personally use Linux command line and can't recall the name of the program I use for windows off hand
Also note that the following commands will wipe all from tablet, it is good to do this but if there is anything real important back it up first
Now from fastboot, enter these commands
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now find the bootloader image you extracted from the android .zip
fastboot flash bootloader nameofbootloader.img
Now if you want stock find the system image
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now find the twrp recovery image
fastboot flash recovery nameofrecovery.img
Here you can boot to new recovery and install superuser or just boot to pure stock, or if you want one of the many great custom ROMs you can boot to recovery and use adb sideload to flash one
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
google search
android factory images
here you will download the correct one, latest manta for the nexus 10
then extract the contents of the zip
now if you want to keep custom recovery that's a good idea but if you want kitkat you will need stock or at least update to the newest twrp (as you current one won't flash kk)
so if you want twrp then google search
twrp recovery manta
and then find the latest image, 2.6.x?
Oh and its a good idea to check md5sum for both the zip from android source and for the recovery image, both will tell you what it should be in download screen and there are many ways to check, just google search
windows md5
there is both official and none official, i personally use linux command line and can't recall the name of the program i use for windows off hand
also note that the following commands will wipe all from tablet, it is good to do this but if there is anything real important back it up first
now from fastboot, enter these commands
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now find the bootloader image you extracted from the android .zip
fastboot flash bootloader nameofbootloader.img
now if you want stock find the system image
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
now find the twrp recovery image
fastboot flash recovery nameofrecovery.img
here you can boot to new recovery and install superuser or just boot to pure stock, or if you want one of the many great custom roms you can boot to recovery and use adb sideload to flash one
sent from my nexus 4 using xda premium 4 mobile app
Click to expand...
Click to collapse
never mind its fixed
you are the man!
Thank you so much!

[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