[Q] Botlooped/Bricked Nexus 7 from build.prop mod recovery help? - Nexus 7 Q&A, Help & Troubleshooting

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

Related

Installed cutom rom now stuck on google screen :(

Ive checked other nexus 7 threads... but this isn't the case.
My nexus 7 is stuck on the google Boot I cannot rub Fastboot or recovery from the toolkit .. nothing at all. It cant find the device .
When I plug in the usb it still makes the sound on windows and so on.
It happened when I was prepairing to install a Custom ROM using JROMFlasher..
I followed all the steps, and when it came to install the ROM to the SD card it just rebooted (transferred to quickly I thought)
And then Ever since it has Just been stuck on the google screen.
I am quite pissed :L
Any Ideas?
I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Download the zip located here : platform-tools.zip Extract the contents to a folder name the folder Nexus7 or whatever you want.
Once thats done go ahead and open a command prompt window in that folder you can do that by Shift+Right clicking inside the folder and selecting "Open Command Prompt Here" or if on XP then open CMD and
Code:
cd C:\Users\Name-of-User\Desktop\Nexus7
Once in the CMD issue the command
Code:
fastboot devices
To see if the computer recognizes the device in fastboot mode. It should spit out a gibberish looking code with ....... Device at the end.
Then you going to flash the recovery to do that you issue this command
Code:
fastboot flash recovery name-of-recovery.img
inside the zip the openrecovery-twrp-2.3.1.0.img that is what you will put in place of "name-of-recovery.img" it will show on the screen writing recovery when its done hit the volume up button until the "START" Turn to "Recovery Mode." Then hit the power button you will boot into recovery mode. Once in recovery mode place the ROM.zip you want to flash in the same folder as the stuff you extracted to.
Then issue this command
Code:
adb push Name-of-ROM.zip /data/media
Of course you will replace name-of-ROM.zip with the actual name of the ROM you are flashing. Make sure you also have a gapps packaged which can be found on goo.im/gapps/ latest package is gapps-jb-20121011-signed.zip you will want to adb push that as well.
IF all is done correctly you should be able to install that ROM please follow this procedure.
1. Go to Wipe
2. Factory Reset (this will delete all your apps and apps data not the sd card)
3.Wipe Cache Partition
4. Wipe Dalvik Cache
5. Format System
6. Go to install and find the two ROM.zip and Gapps package at the bottom of the root of the sd card (/sdcard0)
7. Select to flash the ROM and then the Gapps
8. Reboot
Click to expand...
Click to collapse
You should be good to go now.
ÜBER™ said:
I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Click to expand...
Click to collapse
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.
QuantumCipher said:
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.
Click to expand...
Click to collapse
Its all good wrote you up a quick guide follow that and it'll get you back on track .
ÜBER™ said:
Its all good wrote you up a quick guide follow that and it'll get you back on track .
Click to expand...
Click to collapse
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)
QuantumCipher said:
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)
Click to expand...
Click to collapse
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.
ÜBER™ said:
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.
Click to expand...
Click to collapse
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..
QuantumCipher said:
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..
Click to expand...
Click to collapse
Acutally its a zip of multiple components not just png's. The bootaniamtion.zip as a whole is what makes up that boot up animation. If you want to change the bootanimation you would replace that entire zip with one that you want. And then set the permissions and reboot. Some will even have a flashable. In order to modify system files you need root and a root explorer. There are multiple on the play store i would recommend Root Explorer if you have the money otherwise ES File Manager or Solid Explorer.
Bricked after wiping with twc
When I look for fastboot devices, nothing happens...
where do I go from here?
http://forum.xda-developers.com/showthread.php?p=35777264
Sent from my Nexus 7 using xda premium

[Q] Help! Kernel Stopped Nexus 7 from booting!

My Nexus 7 is at Android 4.2.1 and after installing the Elite Kernel to make it boot faster with CLockWork Mod, its stuck at the X animation. I can still access fastboot mode and clockwork recovery mod but I still can start the device. Please help
reflash your rom in your cwm recovery.
Tried
simms22 said:
reflash your rom in your cwm recovery.
Click to expand...
Click to collapse
I just tried doing that and it said it was succesfully installed but I need to reboot. After tapping reboot system my Nexus 7 is still stuck in that X animation and wont boot.
1100G19 said:
I just tried doing that and it said it was succesfully installed but I need to reboot. After tapping reboot system my Nexus 7 is still stuck in that X animation and wont boot.
Click to expand...
Click to collapse
go into the bootloader/fastboot and try booring from there. you also might need to wipe data/factory reset then reflash your rom. also, sometimes force rebooting from a bootloop will boot it(long press the power button while in the bootloop, hold the power button for 10-20 seconds).
I had this happen to me yesterday when trying to flash a custom kernel to use with CM 10.1. The way I was able to fix it, was to pull the boot.img from the ROM zip and flash it through fastboot in the bootloader. The short and simple way is this:
Open the command prompt or terminal in the folder where fastboot is on your computer, extract the boot.img from the zip file of the ROM your using and place it in the folder with fastboot, then on your Nexus 7, hold in power + volume up + volume down to turn it off. Then hold down volume down and press power to boot into the bootloader. Once there, type in the command prompt/terminal: fastboot flash boot boot.img then reboot and you should be good to go.
Can I just remove the ROM?
simms22 said:
go into the bootloader/fastboot and try booring from there. you also might need to wipe data/factory reset then reflash your rom. also, sometimes force rebooting from a bootloop will boot it(long press the power button while in the bootloop, hold the power button for 10-20 seconds).
Click to expand...
Click to collapse
So if I back up the devices files with CWM and factory reseting it will remove the backup, so is there a way to send the backup onto my laptop?
Also is it possible to just remove the rom because I feel like my life would be easier if I unintalled it.
Thank You!
Hmmmmmm
Hanger84 said:
I had this happen to me yesterday when trying to flash a custom kernel to use with CM 10.1. The way I was able to fix it, was to pull the boot.img from the ROM zip and flash it through fastboot in the bootloader. The short and simple way is this:
Open the command prompt or terminal in the folder where fastboot is on your computer, extract the boot.img from the zip file of the ROM your using and place it in the folder with fastboot, then on your Nexus 7, hold in power + volume up + volume down to turn it off. Then hold down volume down and press power to boot into the bootloader. Once there, type in the command prompt/terminal: fastboot flash boot boot.img then reboot and you should be good to go.
Click to expand...
Click to collapse
Its a bit complicated. Also how do I get the boot.img to my computer from my nexus 7 because when I connected the Nexus 7 folder is not under "My Computer"
Thank you
Sounds like you need to go to fastboot and flash 4.13 bootloader.
Sent from my Nexus 7 using xda premium
Dont know
rebel1699 said:
Sounds like you need to go to fastboot and flash 4.13 bootloader.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
How do I flash 4.13 bootloader?
All you have to do is download the same ROM on your computer that you have on your phone. If its stock 4.2.1, then download the factory image of it and extract the boot image from the zip file and follow the same steps I outlined, though instead of using: fastboot flash boot boot.img, it would be fast boot flash boot <name of boot image>.img
If you still have trouble, feel free to message me here or on GTalk and I'll walk you through it.
Sent from my Nexus 7 using Tapatalk HD
There's an important lesson to be learned here, and you unfortunately learned it the hard way. Never, ever, blindly flash something. You need to read the OP as well as catch up on at least the last page or two of the thread. Had you done so, you would have noted that Clemsyn's Elite kernels are not compatible with 4.2.1.
I'm not saying this to be a condescending, but rather to save you the possibility of getting into situations like this again. Fortunately, Nexus devices are easily recoverable from various user errors.

Please help! Stuck on

Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command
In twrp, it keeps saying starting adb sideload feature
i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!
Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2

Messed up mako(Resolved)

I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app
anoymonos said:
I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.
----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
gee2012 said:
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.
Click to expand...
Click to collapse
any other suggestions
anoymonos said:
----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
any other suggestions
Click to expand...
Click to collapse
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore
gee2012 said:
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore
Click to expand...
Click to collapse
ya but no red andriod appeared it just stayed in fastboot mode
anoymonos said:
ya but no red andriod appeared it just stayed in fastboot mode
Click to expand...
Click to collapse
Close CF Auto root, disconnect and reconnect usb and open CF Auto root again and try again.
If that doesn`t work flash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img in fastboot and flash this superSU zip http://download.chainfire.eu/331/SuperSU/UPDATE-SuperSU-v1.32.zip in recovery
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Do a data factory reset in recovery, wipe cache and reboot. And try rooting again after you enabled usb debugging.
anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
PS: If you have no rom/etc due to erasure, you can 'adb push' the zip files to /sdcard while in recovery.
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
kbeezie said:
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
Click to expand...
Click to collapse
anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.
anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
Dude why you are flasing a bootloader!
kbeezie said:
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.
Click to expand...
Click to collapse
i have folled this link and am syuck at flashing bootloader.http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
basically all i can access is fastboot
This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.
zephiK said:
This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.
Click to expand...
Click to collapse
thats the problem it wont let me flash anything through fastboot
anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
Do a data factory reset/ wipe cache in recovery and reboot.
anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051
gee2012 said:
Do a data factory reset/ wipe cache in recovery and reboot.
Click to expand...
Click to collapse
i dont have a recovery everything got wiped
zephiK said:
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051
Click to expand...
Click to collapse
yes proper drivers installed. Just unrooted and relocked old nexus 4 for return and then tried to root and unlock new one and it **** on me
It probably will if you use the proper syntax since you have to tell it which partition.
If you go and grab the TWRP 2.5.0.0 recovery image from their website for mako, you can use the following
fastboot flash recovery nameofrecovery.img
Making sure there are 4 parts as the word recovery is part of the command.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
Thus why you download one and flash. It's nearly impossible to hard brick a Nexus. Just helps not to receive panic. Take a couple breaths and figure out the proper commands.
Sent from my Nexus 7 using XDA Premium HD app

[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

Categories

Resources