Related
Anyone have any suggestions? Booting into recovery froze my device on the Google screen.
Sent from my Galaxy Nexus using xda app-developers app
Bump. Anyone have any suggestions?
joshtb86 said:
Bump. Anyone have any suggestions?
Click to expand...
Click to collapse
I suggest to install the Android ask and use the following fastboot commands.
fastboot oem unlock
fastboot flash recovery recovery.img
*change recovery.img to whatever filename the recovery is and put it in the same directory as your fastboot.
This way you'll learn what a "rootkit" does and be on your way to learning more .
Sent from my Nexus 7 using xda premium
mwalt2 said:
I suggest to install the Android ask and use the following fastboot commands.
fastboot oem unlock
fastboot flash recovery recovery.img
*change recovery.img to whatever filename the recovery is and put it in the same directory as your fastboot.
This way you'll learn what a "rootkit" does and be on your way to learning more .
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you know where i can get a version of CWM that works for the n7?
thanks!
joshtb86 said:
do you know where i can get a version of CWM that works for the n7?
thanks!
Click to expand...
Click to collapse
Here ya go.
before i do this, do i need to be booted or in bootloader. bootloader, because its using fastboot, right?
joshtb86 said:
before i do this, do i need to be booted or in bootloader. bootloader, because its using fastboot, right?
Click to expand...
Click to collapse
Fastboot mode within bootloader i believe.
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.
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
If tried reinstalling the drivers and also using the toolkit. I choose not to flash a recovery, just temporary boot so I can install stuff. I tried using fastboot to boot twrp but all I get is a black screen. Seems like sometimes the driver changes. Never had this problem on 4.2
Sent from my Nexus 7 using Tapatalk 4
biggyk said:
If tried reinstalling the drivers and also using the toolkit. I choose not to flash a recovery, just temporary boot so I can install stuff. I tried using fastboot to boot twrp but all I get is a black screen. Seems like sometimes the driver changes. Never had this problem on 4.2
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Boot your Nexus to the bootloader by first powering down the phone then simultaneously press and hold the volume down and power buttons for 2 seconds. Once in the bootloader connect the USB cable from the Nexus to your computer. Open a command prompt in the folder where you have installed fastboot, type "fastboot devices", and press enter. If you see a deviceID listed, you will be able to flash TWRP with the command "fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img" (assuming you are installing TWRP v2.6.0.0); otherwise, you will need to reinstall the Nexus drivers.
^The op wants to boot the recovery, not flash it.
Google removed the "fastboot boot" command in the new 4.3 bootloader. The new way to do this is by using the following command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Sent using xda-developers app
Chromium_ said:
^The op wants to boot the recovery, not flash it.
Google removed the "fastboot boot" command in the new 4.3 bootloader. The new way to do this is by using the following command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Sent using xda-developers app
Click to expand...
Click to collapse
Thank you. Worked fine!!:victory:
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!