Related
I used the Nexus 7 toolkit to flash the latest CWM recovery. If I boot into fastboot and choose recovery mode it just hangs on the Google boot animation. I can boot to it from the toolkit though. Anyone else experience this/know what I did wrong?
SpencerRelly said:
I used the Nexus 7 toolkit to flash the latest CWM recovery. If I boot into fastboot and choose recovery mode it just hangs on the Google boot animation. I can boot to it from the toolkit though. Anyone else experience this/know what I did wrong?
Click to expand...
Click to collapse
Its a known issue that is yet to be fixed. You did nothing wrong.
Sent from my Nexus 7 using xda premium
leelaa said:
Its a known issue that is yet to be fixed. You did nothing wrong.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Alright. Thanks for the reply!
SpencerRelly said:
I used the Nexus 7 toolkit to flash the latest CWM recovery. If I boot into fastboot and choose recovery mode it just hangs on the Google boot animation. I can boot to it from the toolkit though. Anyone else experience this/know what I did wrong?
Click to expand...
Click to collapse
You need to have a USB cable connected to the Nexus 7, and if you're in fastboot it'll load into recovery. Known bug
Wrong section dude but as said before known bug
Sent from my Nexus 7 using Tapatalk 2
flash twrp recovery, its not buggy and is more functional.
SpencerRelly said:
I used the Nexus 7 toolkit to flash the latest CWM recovery. If I boot into fastboot and choose recovery mode it just hangs on the Google boot animation. I can boot to it from the toolkit though. Anyone else experience this/know what I did wrong?
Click to expand...
Click to collapse
It's a problem with the boot loader. For now you will need to be plugged into a computer to go into recovery. It doesn't even have to have drivers or anything installed.
Plug in tablet into computer
Use power and volume buttons to get into recovery
And no, this problem won't be fixed by flashing twrp because it deals with the boot loader.
Just boot to recovery from Rom manager or similar.
I can confirm that quick boot does work to get you into recovery.
-----
Sent from my Nexus 7
Moved to QA...The Development section is for..........development only, not questions...
Same problem
I've read in other threads that deleting the stock recovery, or modifying it's filename, will fix this problem. Does anyone know if this is true? I can boot recovery through Rom manager or through the power menu. The only worry I have is if I ever get stuck in a bootloop, or brick. It is good to know about the usb trick to load CWM, thanks for that.
Flash TWRP, and use an app like quick boot to reboot into recovery.
Sent from my Nexus 7 using xda app-developers app
I use TWRP and boot to recovery through the roms power menu. I've been very happy with TWRP though, I use a recovery because of stability and performance. I could really care less if it's touch or if it has themes, so when I recommend TWRP it's because I've been using it so long on my transformer prime and nexus 7 and it has done nothing but work exactly like it should.
veeman said:
It's a problem with the boot loader. For now you will need to be plugged into a computer to go into recovery. It doesn't even have to have drivers or anything installed.
Plug in tablet into computer
Use power and volume buttons to get into recovery
And no, this problem won't be fixed by flashing twrp because it deals with the boot loader.
Click to expand...
Click to collapse
Weird because today I tried to get into CWR for the first time since I rooted, and it wouldn't work. I got the red ! triangle [sticking out of the green robot].
I plugged it into my laptop.. [and btw I was holding vol UP/DOWN, press power, in the bootloader then selecting 'Recovery' then <Power>] and this time it showed the "Google" and the unlocked lock.. but then booted into the Android OS.
So I flash TWRP [using Ubuntu, and $ fastboot install recovery {TWRP-filename.img}. And what do you know. It booted perfectly into recovery.
So how do you explain that?
mvmacd said:
Weird because today I tried to get into CWR for the first time since I rooted, and it wouldn't work. I got the red ! triangle [sticking out of the green robot].
I plugged it into my laptop.. [and btw I was holding vol UP/DOWN, press power, in the bootloader then selecting 'Recovery' then ] and this time it showed the "Google" and the unlocked lock.. but then booted into the Android OS.
So I flash TWRP [using Ubuntu, and $ fastboot install recovery {TWRP-filename.img}. And what do you know. It booted perfectly into recovery.
So how do you explain that?
Click to expand...
Click to collapse
The only possible ways to boot into recovery from a working system partition is by either using an app that reboots for you/terminal command.
To reboot from bootloader/button combination you need to have a USB connection otherwise it will freeze at the Google logo. This is bootloader related and not recovery related as any recovery (stock/cwm/twrp) show the same behavior.
You can try fully powering off the tablet and try booting by button combo and you will see it freezes. Using the power adapter will completely freeze your bootloader if you try, so you require a USB connection to a computer to get into recovery.
For me to boot into recovery , I have to use the tool kit all the time. Is that what everyone is doing??? Because every time I go to fastboot and choose recovery (with my N7 plugged on the usb) I get the Android with the exclamation point.
Sent from my HTC One X using xda app-developers app
Skunk2 DC said:
For me to boot into recovery , I have to use the tool kit all the time. Is that what everyone is doing??? Because every time I go to fastboot and choose recovery (with my N7 plugged on the usb) I get the Android with the exclamation point.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I had the same thing, but I flashed TWRP and it works most of the time. let me know if you try it.
So I just unlocked my boot loader and rooted it + installed CMw recovery, and after I did that I was able to get into recovery mode, however I put a custom kernel in my internal storage so that I could flash it but now I can't get into recovery mode... when I clicked recovery it goes to the black screen with the Google symbol on it and stays there.... any idea what I can do here?
Sent from my Nexus 7 using xda app-developers app
MRsf27 said:
So I just unlocked my boot loader and rooted it + installed CMw recovery, and after I did that I was able to get into recovery mode, however I put a custom kernel in my internal storage so that I could flash it but now I can't get into recovery mode... when I clicked recovery it goes to the black screen with the Google symbol on it and stays there.... any idea what I can do here?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You can't get into recovery without a USB cable connected. Install Quickboot from the Google Play Store. That's how i boot into recovery.Quickboot is the only way to do it without a cable.
theandroidrooter88 said:
You can't get into recovery without a USB cable connected. Install Quickboot from the Google Play Store. That's how i boot into recovery.
Click to expand...
Click to collapse
oh damn, lol thanks alot, had no idea that you needed to be connected, i'll definately be installing quickboot i feel like such a moron
IF A MOD WANTS TO DELETE THIS NOW THEY CANT, THANKS AGAIN!
Yes you can get into recovery without a usb . I'm not sure what the quickboot thing is all its doing is executing a command like
#reboot recovery
That's all it does. If you have terminal execute that command.
But if you're recovery is broken just reflash it using
#fastboot flash recovery nameofrecovery.img
Or just use the toolkit.
carved via Ville
OK so I got quick boot and it works like a charm.. I just click recovery and it takes me to recovery, works like a charm
Sent from my Nexus 7 using xda app-developers app
Hi guys !
I need your help for trying to recover my information from my Nexus 4... (Thanks in advance)
First, my N4 is:
With the screen cracked, so, the bottom half of the screen is not responding to any touch
Locked with a lock pattern (and because of the damaged screen, I can't unlock the phone)
With stock Android
With USB debugging on
Not rooted
With no other modification whatsoever (No custom ROM or recovery mode, etc)
First I tried the obvious, I connected the N4 to my computer expecting a miracle; as the phone is locked, and I can't unlock it, ADB just didn't worked.
I also tried sending a .zip thought "adb sideload" (using the stock recovery mode) to delete the files where the lock pattern is, but an "signature verification error" occurred (because the phone is not rooted, I guess). I've tried to delete the files with "adb -d shell" but (obviously) as ADB is not working, a "device not found" error showed up.
So I guess the question here is... What are my options ? Is there any way I can recover my photos and files ?
Thanks in advance!
Try going into recovery and using adb from there. Turn off the phone then turn it boot into the bootloader using volume down and power. Use the volume rockers to scroll and highlight Recovery mode, then use power to select it. Once in recovery press and hold power, then volume up to enter the menu. Then try "adb devices", and if the phone is recognized you can use what you want.
chromium96 said:
Try going into recovery and using adb from there. Turn off the phone then turn it boot into the bootloader using volume down and power. Use the volume rockers to scroll and highlight Recovery mode, then use power to select it. Once in recovery press and hold power, then volume up to enter the menu. Then try "adb devices", and if the phone is recognized you can use what you want.
Click to expand...
Click to collapse
Hi chromium96 !
That didn't work.. :S
Any other idea ?
Thanks for replying !
Flash a custom recovery and boot into it... I think custom recoveries support adb.. If USB debugging is ON and proper drivers are installed on your PC, you can do 'adb pull' for the necessary files
Sent from my Nexus 4 using Tapatalk 4
badhri said:
Flash a custom recovery and boot into it... I think custom recoveries support adb.. If USB debugging is ON and proper drivers are installed on your PC, you can do 'adb pull' for the necessary files
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Is that going to delete all my information ?
Thanks !
AlejandroFloresV said:
Is that going to delete all my information ?
Thanks !
Click to expand...
Click to collapse
To flash the recovery you will need to unlock your bootloader which is meant to wipe all your data. However if you flash the recovery right after unlocking the bootloader (no reboot in between) the data should not get wiped.
chromium96 said:
To flash the recovery you will need to unlock your bootloader which is meant to wipe all your data. However if you flash the recovery right after unlocking the bootloader (no reboot in between) the data should not get wiped.
Click to expand...
Click to collapse
I don't know if that's true...
Sent from my Nexus 7 using Tapatalk 4
korockinout13 said:
I don't know if that's true...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
It is true. Ive done it successfully on several n4's and its even been talked about a couple times on xda: http://forum.xda-developers.com/showthread.php?t=2266928
Yes.. I have done that too.. It doesn't wipe the data.. Just flash cwm, right after the boot loader unlock..
Sent from my Nexus 4 using Tapatalk 4
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
go to settings/storage open 3dots menu /usb computer connection. if nothing is selected that is why your phone doesn't connect. select mtp an problem solved.
if it's not that i cannot help you except suggesting to reinstall android from scratch using wug toolkit.
wasabitobiko said:
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
Click to expand...
Click to collapse
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
acejavelin said:
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
Click to expand...
Click to collapse
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
wasabitobiko said:
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
Click to expand...
Click to collapse
OK, so your fastboot commands are not working, that would likely be a driver issue? If you do
Code:
fastboot devices
and get a result, then keep going, if you don't, use one of the driver options in Wugfresh's toolkit, follow the instructions TO THE LETTER...
If you are just trying to get root and are unlocked, download the latest SuperSU.zip (to your phone preferably) from http://download.chainfire.eu/supersu and openrecovery-twrp-2.7.0.0-mako.img then start phone in Fastboot mode and enter:
Code:
fastboot boot openrecovery-twrp-2.7.0.0-mako.img
this will start TWRP on your device WITHOUT flashing it.
If the SuperSU zip file is on your phone, just use TWRP's Install button and navigate the file and flash it, then reboot and enjoy.
If the SuperSU zip is on your PC, then in TWRP go to Advanced, and start ADB Sideload, give it a few seconds for it to be recognized by your PC, you should be able to enter
Code:
adb devices
and get a result of SIDELOAD back, then enter:
Code:
adb sideload UPDATE-SuperSU-v1.94.zip
Or whatever the current SuperSU zip file is named. Then reboot and enjoy, your rooted!
Remember that adb commands only work in android and custom recovery NOT in fastboot mode.
Sent from my Nexus 4 using XDA Free mobile app
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload is a special mode that recovery can be placed into, it only allows the "sideload" command to be used. Fastboot is different, it uses the fastboot.exe program and fastboot mode on the android device to allow a limited list of features to be used.
I don't know what you are using for a rooting guide, but basically the end result is to flash SuperSU via recovery, that is all that is really needed.
Sent from my Nexus 4 using Tapatalk
Well, basically if your boot loader is unlocked and you have a custom recovery installed just download the latest superSU zip to your SD card. Reboot into recovery, install SuperSU, reboot. Alas, you're rooted.
Sent from my Nexus 4 using XDA Free mobile app
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If you unlocked your bootloader your drivers should be working fine. If you rebooted your phone now you'd see it works fine. Next step in rooting is to flash custom recovery. Download a custom recovery, I recommend latest version of TWRP, then flash the recovery image. 'fastboot flash recovery recovery.img' (replace recovery.img with whatever .img file you are flashing.
Once custom recovery is installed you can boot into it to flash supersu. If using TWRP it will prompt you to root when you reboot it.
Thanks.. And please don't take offense to this but re-read the thread. Ever since I used wug's rootkit to unlock the bootloader, neither my pc nor linux machine will recognize the Nexus 4. When I plug it in I get a usb error "device failed to load".. When I look at the device mgr it's listed as unknown device. Btw.. I've restarted both my phone and machine multiple times to no avail.
Sent from my Nexus 4 using XDA Free mobile app
Unknown device? Youve probably installed no or wrong fastboot drivers.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Google tool 15 second adb xda
Sent from my Nexus 5 using XDA Free mobile app
UPDATE: It looks like the micro usb port on the phone is fried... had been charging fine until today. I'll keep you posted. Thanks for all the help. Does anyone know if this is a relatively easy fix?
Update: Fixed..
Replacing the usb port on the Nexus 4 is super easy. Thanks for the help guys. Everything's working and root has been achieved.
Hello everyone, I would need to understand if my Nexus 7 2012 WiFi is definitely Hard Bricked or not.
The other day I installed Slimkat ROM and had the error 7 during installation...
I like it better: In Nexus it's root and it unlock with the Recovery CWM, which start with the sequence of Volume Down- Power On keys. I have done the wrong not to do before installing a backup with the Recovery CWM and now I am in the situation of having the Nexus that normally light up on the Google logo and if I start shooting, it is not copied on the sdcard the right ROM, unable to install anything. I seem to have read that I had installed the TWPR Recovery instead of an external USB with an OTG cable, which is impossible with the CWM.
This is my question: Is there any way to copy files to the SDCard? If I don't see the Nexus in ADB, can I install TWRP Recovery up the CWM? (for use the USB/OTG performance)
Thanks for the help and congratulations for the forum ...
luca
Hard to understand you actually... but boot to bootloader and fastboot flash the TWRP, use MTP to copy over what you need to flash and go ahead, in case you never used fastboot check Google there're plenty of guides out there, good luck...
Sent from my Nexus 7 using XDA Labs
Sam Nakamura said:
Hard to understand you actually... but boot to bootloader and fastboot flash the TWRP, use MTP to copy over what you need to flash and go ahead, in case you never used fastboot check Google there're plenty of guides out there, good luck...
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your answer. But I installed CWM Recovery and I can not access to Nexus in fastboot or adb, so I can not install the Recovery TWRP. I've tried both with MAC OSX and Windows, but the Nexus is not seen by the system. Exist an alternative method for flashing the recovery TWRP without using fastboot or adb?
lucafict said:
Hello everyone, I would need to understand if my Nexus 7 2012 WiFi is definitely Hard Bricked or not.
The other day I installed Slimkat ROM and had the error 7 during installation...
I like it better: In Nexus it's root and it unlock with the Recovery CWM, which start with the sequence of Volume Down- Power On keys. I have done the wrong not to do before installing a backup with the Recovery CWM and now I am in the situation of having the Nexus that normally light up on the Google logo and if I start shooting, it is not copied on the sdcard the right ROM, unable to install anything. I seem to have read that I had installed the TWPR Recovery instead of an external USB with an OTG cable, which is impossible with the CWM.
This is my question: Is there any way to copy files to the SDCard? If I don't see the Nexus in ADB, can I install TWRP Recovery up the CWM? (for use the USB/OTG performance)
Thanks for the help and congratulations for the forum ...
luca
Click to expand...
Click to collapse
Tried with Nexus root toolkit ?
twrp better than cwm
lucafict said:
Thank you so much for your answer. But I installed CWM Recovery and I can not access to Nexus in fastboot or adb, so I can not install the Recovery TWRP. I've tried both with MAC OSX and Windows, but the Nexus is not seen by the system. Exist an alternative method for flashing the recovery TWRP without using fastboot or adb?
Click to expand...
Click to collapse
Bootloader is not Recovery nore ADB, it's independent from those!
Boot up by holding power & volume down till you have the bootloader screen (picture attached), if you see it plug it in your (windows) computer and check "fastboot devices", there then fastboot flash TWRP image...
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Bootloader is not Recovery nore ADB, it's independent from those!
Boot up by holding power & volume down till you have the bootloader screen (picture attached), if you see it plug it in your (windows) computer and check "fastboot devices", there then fastboot flash TWRP image...
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Attacched my Fastboot page, but nothing... no devices show with “fastboot devices” command.
lucafict said:
Attacched my Fastboot page, but nothing... no devices show with “fastboot devices” command.
Click to expand...
Click to collapse
Have you another device at hand to check weather fastboot is working with a different device, just to make sure that your fastboot environment is working properly...
Sent from my OnePlus 3T using XDA Labs
Yes, with another Nexus 7, if I connect it to pc, the device is show in section device list of pc. I think the problem is that this Bricked Nexus in fastboot not start the usb driver...