So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?
am3606 said:
So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?
Click to expand...
Click to collapse
are you sure that you "rooted" it, or did you just unlock the bootloader? thgat open android with the red sign is the stock recovery btw. what you need to do is flash a custom recovery via fastboot, either twrp or cwm, then flash the latest supersu via your new custom recovery. thats all that you need to do.
latest supersu http://download.chainfire.eu/supersu
Well I rooted it but due to some problems had to reset the whole thing. Before I reseted it, I had SuperSU installed and it said that the device was rooted.
I can't access the bootloader is the problem, when I go to recovery mode I go to the "stock recovery" with the android with the red sign saying no command. So am I suppose to place the zip file using android file transfer?
am3606 said:
Well I rooted it but due to some problems had to reset the whole thing. Before I reseted it, I had SuperSU installed and it said that the device was rooted.
I can't access the bootloader is the problem, when I go to recovery mode I go to the "stock recovery" with the android with the red sign saying no command. So am I suppose to place the zip file using android file transfer?
Click to expand...
Click to collapse
to access the bootloader, power off first. then power on holding the volume down button and the power button. that is the bootloader. thats what gives you the options to go into recovery, reboot bootloader, boot up, or power off. in order for you to be able to flash the latest supersu, you need to flash a custom recovery first.
simms22 said:
to access the bootloader, power off first. then power on holding the volume down button and the power button. that is the bootloader. thats what gives you the options to go into recovery, reboot bootloader, boot up, or power off. in order for you to be able to flash the latest supersu, you need to flash a custom recovery first.
Click to expand...
Click to collapse
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?
am3606 said:
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?
Click to expand...
Click to collapse
you need to flash it via fastboot while your phone is in the bootloader(there are instruction here). follow the "installing a custom recovery" part http://forum.xda-developers.com/showthread.php?t=2507905
am3606 said:
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?
Click to expand...
Click to collapse
You must have flashed a custom recovery before to flash root.
If you're confused at this moment , its a good idea to put your phone down and get a cup of tea.
Then, read the how to unlock your bootloader / root thread stuck at the top of general.
Read through it. To have been rooted, you must have done all that stuff before. It has instructions for each step. But importantly, read don't do until you're familiar with it all
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
If you're confused at this moment , its a good idea to put your phone down and get a cup of tea.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
thats one of the best pieces of advice ive read!
sometimes, just taking a step back, a breather, a time out, opens your eyes to things right in front of you that you dont see. plus gives you a chance to read up and make yourself better prepared.
rootSU said:
...its a good idea to put your phone down and get a cup of tea...
Click to expand...
Click to collapse
You're so damn civilized across the pond. It's enviable.
You can also download the app "Goo Manager", in the settings menu there is an option to install the latest TWRP recovery. ☺
Sent from my Nexus 5
you can use nexus root toolkit to unlock bootloader and flash supersu:
am3606 said:
So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?
Click to expand...
Click to collapse
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
iburtondroid said:
you can use nexus root toolkit to unlock bootloader and flash supersu:
Click to expand...
Click to collapse
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed
lichti1901 said:
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed
Click to expand...
Click to collapse
agree, I have just proposed him, if he is not sure what he was doing wrong, also, correct me if I am wrong, but maybe he didn't enable developer options (not sure if this is a must for other steps he needs to take)
Developer Options are only applicable when Android is booted, has no bearing on things when in fastboot. They also have no bearing on root.
If the OP doesn't know what they're doing then they should read up on everything and LEARN the adb/fastoot commands. It takes all of 10 minutes reading to know the basics and will hold you in good stead for future Android handsets
PhilipTD said:
You're so damn civilized across the pond.
Click to expand...
Click to collapse
Well I couldn't say shoot up and rob a granny now could I?
</poor taste>
rootSU said:
Well I couldn't say shoot up and rob a granny now could I?
</poor taste>
Click to expand...
Click to collapse
LMAO
lichti1901 said:
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed
Click to expand...
Click to collapse
mysd card? I thought all I needed is the usb...
I was in class much of yesterday and of today so forgive me for the update.
Downloading the SDK and just downloaded the twrp recovery.img.
TCWadey said:
You can also download the app "Goo Manager", in the settings menu there is an option to install the latest TWRP recovery. ☺
Sent from my Nexus 5
Click to expand...
Click to collapse
you can, but you need root for it to work. the name of this thread is.. "Nexus 5 "No SU binary installed and SuperSU? cannot Install it".
@PhilipTD @rootSU, Sorry to bump this thread, but I had to lol :laugh::laugh::laugh:
Related
Removed all my Dropbox links because they disabled my account due to too much traffic, if you guys want them back please consider donating a buck or two for a Mediafire Pro account...I didn't develop this, just getting the word out that's it's officially available for the Nexus 7. You can either install the "normal" version or touch version from ROM Manager
UPDATE 11/16 new version posted by Koush 6.0.1.9
CWM Regular
CWM Touch
Here is the CWM ZIP by osm0sis:
Touch 6.0.1.9
Regualr 6.0.1.9
You NEED an unlocked bootloader in order to flash this check this thread on how-to unlock/root etc Nexus 7 Toolkit
If you just want to apply an OTA update and you haven't got it, you can do so by booting into CWM without installing it or having root.
first download and save OTA files from OTA 4.1.1 files and save to your /sdcard
then use
./adb reboot bootloader
./fastboot boot recovery-clockwork-touch-6.0.1.9-grouper.img
select install zip from sdcard
toggle signature verification and make sure it's disabled
select the file you downloaded earlier and install
reboot and you will be updated
Click to expand...
Click to collapse
If you want to have CWM permantly installed, first make sure you have root...use Root Explorer or any other file manager with root access and go to /system and delete recovery-from-boot.p
now use
./adb reboot bootloader
./fastboot flash recovery recovery-clockwork-touch-6.0.1.9-grouper.img
./adb reboot
Click to expand...
Click to collapse
You now have CWM installed.
I'm not responsible if you brick your tablet, it blows up mid flash etc
Make sure you know how to use ADB and have the SDK installed, you need that in order to do all of the above steps
Also make sure you have the recovery files saved to /sdk/platform-tools and also fastboot.exe has to be there also
Any commands that start with ./ are for linux/osx...just remove those when using windows
Click to expand...
Click to collapse
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
** edit 7/21/12**
Here's the zip file for the new touch recovery 6.0.1.0 http://db.tt/pLDeKXEf
Feel free to mirror!
Sent from my Nexus 7 using xda app-developers app
Flashing when I get home thanks.
Sent from my Galaxy Nexus using xda app-developers app
I flashed this from rom manager and so far have not had any of the problems I have had in some of the interim CWM's like inability to delete back ups or mounting system.
hey dude it's 6.0.0.6 not 6.0.6
mrich137 said:
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Shano56 said:
hey dude it's 6.0.0.6 not 6.0.6
Click to expand...
Click to collapse
oops, typo...thanks, I will fix it now
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
It works as long as you're connected to a computer, so you can access recovery from bootloader you just need to be hooked to a computer.
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
JoeM01 said:
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
camblue said:
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
Click to expand...
Click to collapse
Flashed fine here also. Works without flaw so far.
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
Did you install the ota after you rooted and installed the recovery? I soft bricked too and I think that was the reason why. Something about the ota overwrote the recovery partition. Best thing to do is download ROM manager and click the first option to flash cwm. Then click the next button to boot into recovery. Then just flash the zip I posted to upgrade to touch.
**edit** just tried to boot into recovery from the boot loader and got stuck at the Google screen too. Holding all three buttons rebooted and started up as normal. Maybe the boot loader boot into recovery is pointing to a different partition for some reason?
Booting into recovery from ROM manager works though. That's how I've been getting in.
Sent from my Galaxy Nexus using xda app-developers app
thanks for the heads up
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
What did you try?
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
BennyJr said:
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
Click to expand...
Click to collapse
camblue said:
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
Click to expand...
Click to collapse
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Bootloader = fastboot. Any adb commands wont work
BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Which is correct. You won't be able to do adb commands in the bootloader. The command he asked you to try was a fastboot command, which should work
Sent from my Galaxy Nexus using xda app-developers app
Make sure the drivers are installed had this problem with windows 7 download the naked driver pack and follow the instructions
Sent from my Nexus 7 using xda premium
I'm sure there will be a lot of people running the 2.20 root then not knowing what to do. So follow this guide.
Make sure you have adb and fastboot available to use.
Download custom recovery, TWRP is preferred: http://teamw.in/project/twrp2/99
Download the ROM you want to run, plus associated gapps to your phone, place them in the download folder (look in the android development and android original development threads)
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
If you have the newer HBOOT 1.14 (you probably do if coming from stock 2.20), boot.img's will have to be flashed separately via fastboot. Extract the boot.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes)
You can then flash the ROM and gapps via recovery and reboot and enjoy.
GuyIncognito721 said:
I'm sure there will be a lot of people running the 2.20 root then not knowing what to do. So follow this guide.
Make sure you have adb and fastboot available to use.
Download custom recovery, TWRP is preferred: http://teamw.in/project/twrp2/99
Download the ROM you want to run, plus associated gapps to your phone, place them in the download folder (look in the android development and android original development threads)
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
If you have the newer HBOOT, radio and boot.imgs will have to be flashed separately via fastboot. Extract the boot.img and radio.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes) and 'fastboot flash radio radio.img'
You can then flash the ROM and gapps via recovery and reboot and enjoy.
Click to expand...
Click to collapse
Also, this thread will be useful for flash-aholics :http://forum.xda-developers.com/showthread.php?t=1910294
What if I only see the boot.img and not the radio. The rom is CleanRom V5
may I ask which ROM for a stable AOSP experience ? I daresay none of us 2.20 sufferers have been frequenting the ROM sub-forums
JustTheHustle said:
What if I only see the boot.img and not the radio. The rom is CleanRom V5
Click to expand...
Click to collapse
Sorry, I removed the part about flashing radios. You ca't with the newer HBOOT. Only if we had S-OFF.
GuyIncognito721 said:
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
Click to expand...
Click to collapse
Would you mind expanding on that? I'm new to this even though I've had the phone since May. I'm unable to put the phone into bootloader mode by holding power and volume down (phone just boots normally) so I need another way.
Thanks
sandys1 said:
may I ask which ROM for a stable AOSP experience ? I daresay none of us 2.20 sufferers have been frequenting the ROM sub-forums
Click to expand...
Click to collapse
RebelMOD. Jelly Bean and everything works.
Sent from my HTC One XL
Epos7 said:
Would you mind expanding on that? I'm new to this even though I've had the phone since May. I'm unable to put the phone into bootloader mode by holding power and volume down (phone just boots normally) so I need another way.
Thanks
Click to expand...
Click to collapse
More specifically I'm not sure how to connect to the device in cmd. If I run 'adb reboot bootloader' it returns "device offline"
edit - closing/re-opening cmd appears to have solved the problem.
I'm not sure what I did, but I can no longer boot into bootloader mode. When I try now, I see a phone with a red exclamation mark inside a triangle. Does anyone know what I've done wrong or how to fix this? After a minute or two the phone reboots normally.
edit - I re-ran the script for 2.20 root to create a new backup and am now back in bootloader mode.
When i wrote adb rebot recovery it did not work what happened?
so say i want to run the viper rom i just pull the boot.img out of the rom and place it with my fastboot.exe file ( i have that and my adb files from when i unlocked the bootloader in the same folder) and flash it then i boot into recovery and wipe everything and install like normal? i came from a mytouch 4g and it was as simple as putting on the sd card wiping and flashing. this has got me a little worried i may screw up somewhere
another thing, the file is just named boot do i need to rename it boot.img before i flash it?
jrlatta said:
another thing, the file is just named boot do i need to rename it boot.img before i flash it?
Click to expand...
Click to collapse
I'm guessing the filename extension is just being hidden. Did you try typing boot.img in cmd? If that works you know the extension is there.
i went ahead and flashed everything and its finished now, hopefully everything boots, well i just got a snake so i guess so far so good
ImmenseGT said:
When i wrote adb rebot recovery it did not work what happened?
Click to expand...
Click to collapse
FWIW I had to flash TWRP twice. Didn't stick the first time for some reason.
Sent from my cm_tenderloin using xda app-developers app
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
---------- Post added at 03:12 AM ---------- Previous post was at 03:08 AM ----------
Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
Click to expand...
Click to collapse
also do I do a factory reset in recovery before I do my fast boot flash boot.img? or do I first flash the boot.img, then reboot to recovery and do factory reset?
Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
Click to expand...
Click to collapse
I believe so. That is what I have been doing.
Epos7 said:
................................oops
Click to expand...
Click to collapse
what?
---------- Post added at 03:24 AM ---------- Previous post was at 03:18 AM ----------
Epos7 said:
I believe so. That is what I have been doing.
Click to expand...
Click to collapse
did you get venom installed ok like that?
Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
---------- Post added at 03:12 AM ---------- Previous post was at 03:08 AM ----------
also do I do a factory reset in recovery before I do my fast boot flash boot.img? or do I first flash the boot.img, then reboot to recovery and do factory reset?
Click to expand...
Click to collapse
i booted into recovery and wiped everything and then went and flashed the boot image then from bootloader, used the volume keys to get to recovery, booted into recovery and selected the file i wanted to flash let it run and presto it worked, i did not choose to wipe again since i wiped before flashing the boot image because i was afraid it would erase it
Just let you guys know, my toolkit allows you to flash boot.img. Just place the boot.img in the /Data/Kernels folder and press "With this command" and it'll flash it!
http://forum.xda-developers.com/showthread.php?t=1952426
yep working for me too.
Hi to all,
I want to install a cwm (the last one) becouse the android update 4.4.4 has erase my recovery.
I run the program, i go to launch and I click Recovery in boot/Flash image.
The program download the last version of recovery anche restart nexus5 in bootloader menu and instal a recovery.
After that restart the phone again and it works perfectly but when I go to recovery mode, it doesn't work. I try more times but doesn't work!
The phone is unlocked and before update 4.4.4 the recovery worked perfectly.
Somebody can resolve thi problem?
Thanks.
Fastboot
moscast said:
Hi to all,
I want to install a cwm (the last one) becouse the android update 4.4.4 has erase my recovery.
I run the program, i go to launch and I click Recovery in boot/Flash image.
The program download the last version of recovery anche restart nexus5 in bootloader menu and instal a recovery.
After that restart the phone again and it works perfectly but when I go to recovery mode, it doesn't work. I try more times but doesn't work!
The phone is unlocked and before update 4.4.4 the recovery worked perfectly.
Somebody can resolve thi problem?
Thanks.
Click to expand...
Click to collapse
Flash through fastboot and see if it works, but that's the wrong section to ask a question..
thunder_bolt96 said:
Flash through fastboot and see if it works, but that's the wrong section to ask a question..
Click to expand...
Click to collapse
ok thanks but can i use this tool?
http://forum.xda-developers.com/goo...tool-nexus-5-multi-tool-3-unlock-cwm-t2509428
The problem is that the link for downloading it does't work.
The firs time that I unlock, and flash recovery and root I used that software.
Can you replace it or give me another link?
Thanks again anche sorry for wonge section....
No. Do NOT use tools like this.
OTA removes root and replaces recovery.
If you want a recovery Download cwm, philz or twrp and fastboot flash recovery image from your pc
If you click the link to the sticky roll-up in my signature, you will find a thread there in section 1 called "adb and fastboot, what is it?". Please read it. You will know everything you need to know
Sent from my Nexus 5 using Tapatalk
moscast said:
ok thanks but can i use this tool?
http://forum.xda-developers.com/goo...tool-nexus-5-multi-tool-3-unlock-cwm-t2509428
The problem is that the link for downloading it does't work.
The firs time that I unlock, and flash recovery and root I used that software.
Can you replace it or give me another link?
Thanks again anche sorry for wonge section....
Click to expand...
Click to collapse
Fastboot flashing a recovery would take less time than it took for you to type out that post.
Thanks all.
I read and I understand that I have to send this commands:
Adb reboot and when device go to bootloader a send:
Fastboot flash recovery recovery. Img
Is it correct?
Sent from my Nexus 5 using XDA Premium 4 mobile app
moscast said:
Thanks all.
I read and I understand that I have to send this commands:
Adb reboot and when device go to bootloader a send:
Fastboot flash recovery recovery. Img
Is it correct?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Multiple ways to get into the bootloader. Another is hold vol down whilst turning on your phone
Since I suggested you read my adb and fastboot thread, I added a new section about command prompt. It explains that you need to tell cmd where the recovery image is but otherwise correct.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Multiple ways to get into the bootloader. Another is hold vol down whilst turning on your phone
Since I suggested you read my adb and fastboot thread, I added a new section about command prompt. It explains that you need to tell cmd where the recovery image is but otherwise correct.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!
moscast said:
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
sweet, and you did it the right way. now honestly, compared to a root toolkits, isnt the right way easy?
moscast said:
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
I'm so glad you took the time to read, understand and do. Now when you have other issues, the knowledge you just learnt will be invaluable.
Sent from my Nexus 5 using Tapatalk
Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!
Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V2.49 BETA and RICDefeat & remove KingRoot apps.
Lothgar said:
Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!
Click to expand...
Click to collapse
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Enycz11 said:
Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V.249 BETA and RICDefeat & remove KingRoot apps.
Click to expand...
Click to collapse
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Thanks! Trying right now!
linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.
Lothgar said:
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.
Click to expand...
Click to collapse
But you have to do a fastboot flash recovery recovery.img . Did you do that ?
linuxct said:
But you have to do a fastboot flash recovery recovery.img . Did you do that ?
Click to expand...
Click to collapse
Yep.
Lothgar said:
Yep.
Click to expand...
Click to collapse
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...
linuxct said:
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...
Click to expand...
Click to collapse
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
EDIT: Reflashed now only if i try to enter recovery the lines shows up!
Lothgar said:
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
Click to expand...
Click to collapse
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.
linuxct said:
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.
Click to expand...
Click to collapse
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.
Lothgar said:
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.
Click to expand...
Click to collapse
Maybe is a screen driver problem, but on a D2303?? For me it's working
linuxct said:
Maybe is a screen driver problem, but on a D2303?? For me it's working
Click to expand...
Click to collapse
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?
Lothgar said:
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?
Click to expand...
Click to collapse
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.
linuxct said:
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.
Click to expand...
Click to collapse
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:
Lothgar said:
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:
Click to expand...
Click to collapse
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...
linuxct said:
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...
Click to expand...
Click to collapse
CM recovery. If i downgrade the kernel the adb doesn't start! And yes is enabled in the settings.
EDIT: Solved trying now for the locked bootloader method!
Installed philz recovery with locked bootloader method but i cant flash omnirom! (status 7)
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader