o I rooted my nexus 5. No issues. Installed TWRP. Same. Downloaded CM and GA to the phone. Then, very foolishly, wiped everything to prep for the install - SD card included. Now, all I can load is TWRP. No ROM to be found - obviously. Computer won't recognize the phone to load a ROM that way. Would be VERY appreciative of any help. TY!S
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
meangreenie said:
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
Click to expand...
Click to collapse
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
bradley.robt said:
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
Click to expand...
Click to collapse
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
aldyu said:
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
Click to expand...
Click to collapse
Sorry, assume 'adb devices' is in the command prompt, but noob town - which folder in the ADT parent folder?
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
That's what I figured, but...challenge accepted. Thanks for the links.
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
RoyJ,
Appreciate the help. TY, all's good.
Happened to me a few times tinkering with the gnex, n4...boneheadedly wiped the internal storage. Easiest fix in my opinion is to just flash factory stock and start back from stretch. If not like they said you're in for a long night trying to get your phone to sync up to push the files via adb if you aren't familiar with the stuff.
Do wish you the best. Been there.
I have not been in that situation but couldn't you use a OTG cable (a Y type one which accepts power as well) and a SD card or stick and then mount it within TWRP to access a ROM to flash...?
EDIT: Also consider the Nexus Toolkit - very useful.
I really think that the faster way is to flash stock firmware back (if you have no experience with ADB commands).
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
TheLastSidekick said:
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It's really not that hard.. You plug it in, open a folder, open the prompt and type a few words.. My advice is to try and learn.
sent from my Nexus 5
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Glad you got it sorted.
Letharqy said:
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Click to expand...
Click to collapse
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
TheLastSidekick said:
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No, you didn;t get my point. I told him to straight away restore by images just because his phone wasn't working at all. He can learn all that stuff later, but atleast he should be with no phone at all.
Seadra said:
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
Click to expand...
Click to collapse
How would you flash the .imgs without using adb/fastboot?
Letharqy said:
How would you flash the .imgs without using adb/fastboot?
Click to expand...
Click to collapse
by adb drivers, I mean adb/fastboot or SDK and drivers of the phone that's always included.
Related
So basically
Unlock
Reboot
Install Goo Manger
Install Open Script
Reboot into recovery
Install ROM/Gapps
{PROFIT}!?
I'm running Official Jelly Bean, and I am rooted.
Let me know if that is the right process
Thanks!
David522d said:
So basically
Unlock
Reboot
Install Goo Manger
Install Open Script
Reboot into recovery
Install ROM/Gapps
{PROFIT}!?
I'm running Official Jelly Bean, and I am rooted.
Let me know if that is the right process
Thanks!
Click to expand...
Click to collapse
Thats right!
If you like Asus' Jelly Bean, but would like it a bit faster, I'd go with CleanRom Inheritance.
I think most of us do!
Good luck and have fun!
adelancker said:
Thats right!
If you like Asus' Jelly Bean, but would like it a bit faster, I'd go with CleanRom Inheritance.
I think most of us do!
Good luck and have fun!
Click to expand...
Click to collapse
Sweet, Have you tried others, Baked Bean / Liquid
I can't decide if i want to do this with my brand new infinity Knowing my luck as soon as i do it I'd need warranty work. I assume this fixes the pausing while browsing and stuff like keyboard lag? After you unlock it doesnt really matter what OTA updates come out does it?
can someone please explain open script? I searched the net but nothing useful came up. thanks
mrjayviper said:
can someone please explain open script? I searched the net but nothing useful came up. thanks
Click to expand...
Click to collapse
"Install open script" basically stands for "Install TWRP recovery"
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
"Install open script" basically stands for "Install TWRP recovery"
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
thanks
berfles said:
I can't decide if i want to do this with my brand new infinity Knowing my luck as soon as i do it I'd need warranty work. I assume this fixes the pausing while browsing and stuff like keyboard lag? After you unlock it doesnt really matter what OTA updates come out does it?
Click to expand...
Click to collapse
I wouldn't expect wonders but I'm using CM10 and it's definitely an improvement.
I just rooted and unlocked my tablet last night. Doing some reading atm and it looks like my next step would be to install CWM/ROM Manager and then go to town with the ROMs. My question though is what can I do without a Windows desktop/laptop? I'm currently deployed and forgot to bring my laptop charger. I had enough battery left to root my tablet and thats about it. Then I unlocked it with only the tablet. Do I need to use a computer for most ROMs? Or can I download them directly to the tablet and then install them? I've also got a Samsung Galaxy Player 5.0(stock/not rooted)...can that be used for anything that might require a desktop/laptop?
Is Goo Manager better than ROM Manager?
Do not use rom manager. You will brick your device!
lol thats good to know. Goo Manager it is then it looks like.
Coors said:
lol thats good to know. Goo Manager it is then it looks like.
Click to expand...
Click to collapse
You can use Goo but have to be rooted to do so.
Other way is fastboot. You'll need to be able to use a cmd prompt and have the adroid sdk installed.
Download the TWRP 2.3.1.0 version from the goo website (rename to twrp.blob) and use the following commands to to flash it whilst the tablet is in fastboot mode:
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
sbdags said:
You can use Goo but have to be rooted to do so.
Other way is fastboot. You'll need to be able to use a cmd prompt and have the adroid sdk installed.
Download the TWRP 2.3.1.0 version from the goo website (rename to twrp.blob) and use the following commands to to flash it whilst the tablet is in fastboot mode:
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
Thanks. I'll go with Goo Manager and TWRP. For my other question though is rooting one of the only things that requires to be plugged into a Windows PC? Atm I only plan to install a rom and probably the Data2SD mod when my microSD card comes in the mail. I don't have access to a PC since my laptop battery is dead and no charger.
Coors said:
Thanks. I'll go with Goo Manager and TWRP. For my other question though is rooting one of the only things that requires to be plugged into a Windows PC? Atm I only plan to install a rom and probably the Data2SD mod when my microSD card comes in the mail. I don't have access to a PC since my laptop battery is dead and no charger.
Click to expand...
Click to collapse
Rooting also works fine with a Linux PC.
_that said:
Rooting also works fine with a Linux PC.
Click to expand...
Click to collapse
I was able to root last night on my laptop. Problem is my laptop battery is now dead and my charger is 7000 miles away lol. I was just curious if there is anything else that needs to be plugged in to do. All I have right now is the TF700 and my Samsung Galaxy Player 5.0. I'm thinking one of my limitations will be formatting my microSD card if I need it to be a certain file system.
Coors said:
I was able to root last night on my laptop. Problem is my laptop battery is now dead and my charger is 7000 miles away lol. I was just curious if there is anything else that needs to be plugged in to do. All I have right now is the TF700 and my Samsung Galaxy Player 5.0. I'm thinking one of my limitations will be formatting my microSD card if I need it to be a certain file system.
Click to expand...
Click to collapse
If it's still at the pretty much factory default for most manufacturers (i.e., FAT32), you'll be fine. How are you going to get the custom ROM file on that card?
MartyHulskemper said:
If it's still at the pretty much factory default for most manufacturers (i.e., FAT32), you'll be fine. How are you going to get the custom ROM file on that card?
Click to expand...
Click to collapse
Can I not download it with the tablet and move it over?
Coors said:
Can I not download it with the tablet and move it over?
Click to expand...
Click to collapse
Yes, you should be able to as long as it is on the root of the sdcard and not in any folder.
sbdags said:
Do not use rom manager. You will brick your device!
Click to expand...
Click to collapse
Yes! Please listen to sbdags!
okantomi said:
Yes! Please listen to sbdags!
Click to expand...
Click to collapse
A couple of questions to add since I am in a similar situation with a new, locked tf700. I've read as much as I could about everything but I just want to be very certain of the order of things I have to do.
I'm on ICS (.26).
1. unlock
2. nvflash
3. update to jb (should i do .20 or .23?)
4. flash twrp
5. flash cleanrom
Is that all?
Or should I root in ICS and use OTA rootkeeper and use goomanager at JB?
Thanks for the help!
Progress circles keep circling til battery dies. Coldboot didn't work. (Although Asus said I shouldn't try android icon.)
Don't want to wipe data if I don't have to because I was in the middle of backing up data when it got stuck (can I connect it to my 2 1/2 yr. old laptop to copy files I need?)
Have all updates except last one two weeks ago. Not under warranty.
hi
Try to connect it to PC when you turn it on..if your computer recognized it...other wise no way to copy data as far as i know..(I am also not a PRO).
For your tablet to boot again i think go into recovery and then wipe everything and it ll re format your tablet then it should be in factory condition.
If this dosent works try my guide see the first posts in here u ll find it!!..
Hope u ll recover it!
You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Can't Find adb download link
UndisputedGuy said:
You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto
pjspener said:
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto
Click to expand...
Click to collapse
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
How to find Link to sdk with adb
UndisputedGuy said:
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Forgive my ignorance. That link didnt lead me to an sdk with adb in the directories, which sdk do I use?
Also, I cant figure out how to get a list of the guides on this forum or all forums.
Thanks!
If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.
adb devices command didnt work
UndisputedGuy said:
If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.
Click to expand...
Click to collapse
"adb devices" didn't work for me either, how did you make it work? I'm in the same place you were.
Also are there separate adb drivers?
Thanks
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot
DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.
Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.
zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0
same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp
still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point
still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,
Hey,
So I think I deleted everything from my phone. I can get to the TWRM screen and play around there, but when I want to restart my phone, it says,' NO OS installaed!'
When I go to restart it, I'm just stuck at the google screen.
I cant transfer a custom rom to my phone because my phone isn't in a state where I can put transfer filed to my phone.
Please help ASAP!
Two options:
1) Adb push a ROM in custom recovery.
2) Flash the factory image with fastboot in the bootloader.
Sent from my Nexus 5
if you can enter fastboot just flash a ROM through it ...you'll be fine
sirajgoku said:
if you can enter fastboot just push a ROM through adb ...you'll be fine
Click to expand...
Click to collapse
Massive contradiction in terms - you can't use adb commands in fastboot, you use fastboot commands in fastboot
Sent from my Nexus 5 using XDA Premium 4 mobile app
If this were me I would adb push a custom rom via recovery. Although I love stock, if I were in your shoes I would go with cataclysm or slim.
mmavani said:
Hey,
So I think I deleted everything from my phone. I can get to the TWRM screen and play around there, but when I want to restart my phone, it says,' NO OS installaed!'
When I go to restart it, I'm just stuck at the google screen.
I cant transfer a custom rom to my phone because my phone isn't in a state where I can put transfer filed to my phone.
Please help ASAP!
Click to expand...
Click to collapse
Have you tried flashing the factory image? This should be a requirement before coming on here and asking for help.
instruction
El Daddy said:
Two options:
1) Adb push a ROM in custom recovery.
2) Flash the factory image with fastboot in the bootloader.
Sent from my Nexus 5
Click to expand...
Click to collapse
can you send me guide? instructions? video?
mmavani said:
can you send me guide? instructions? video?
Click to expand...
Click to collapse
The sticky threads in general and Q&A would be a good place to look.
Sent from my Nexus 5
mmavani said:
can you send me guide? instructions? video?
Click to expand...
Click to collapse
Ay yay yay, I hear kittens dying.
This is a perfect example of why toolkits aren't beneficial to new users. If the OP had rooted manually, he'd be familiar with both fastboot and adb, and would be able to solve this issue easily.
Toolkits should only be used by experienced users, in order to save time... NOT as a pacifier for the uninitiated. :-\
Sent from my Nexus 5 using Tapatalk
@mmavani,
Despite my obvious bemusement, I'm going to try to help out... First, check here - http://forum.xda-developers.com/showthread.php?t=2507905
Also, do a Google search on adb and fastboot, and find out what they do, and why you need to be familiar with them. If you research, read , and understand the information, then you should have no problem doing this - adb push "romxyz.zip" /sdcard/download.
If you can't (or don't want to) take time to educate yourself about unlocking, rooting, and flashing, then you need to reconsider whether you have any business being rooted.
Sent from my Nexus 5 using Tapatalk
Fixed
jjhiza said:
@mmavani,
Despite my obvious bemusement, I'm going to try to help out... First, check here - http://forum.xda-developers.com/showthread.php?t=2507905
Also, do a Google search on adb and fastboot, and find out what they do, and why you need to be familiar with them. If you research, read , and understand the information, then you should have no problem doing this - adb push "romxyz.zip" /sdcard/download.
If you can't (or don't want to) take time to educate yourself about unlocking, rooting, and flashing, then you need to reconsider whether you have any business being rooted.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's already fixed.
Thanks for your help
Hey guys,
I am pretty new to the rooting stuff on the Nexus.
I read the sticky threat from rootSU (http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527) and followed his description. So I installed ADB and fastboot through the "15 sec. installer" (http://forum.xda-developers.com/showthread.php?t=2588979).
So fast so good, everything went fine. But as I tried to "check" if ADB and fastboot are recognizing my device with the command "adb devices" and "fastboot devices" in cmd, I got some strange output (look at the picture).
How can it be that ADB "sees" my device and fastboot not? What I did wrong there?
(I didn't installed the drivers with the 15 sec tool; when I plugged in my device to the computer, it downloaded the drivers itself)
Any help would be very appreciated!
Follow the next step on my thread and install the naked drivers
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Blackbox421 said:
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Click to expand...
Click to collapse
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
EddyOS said:
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
Click to expand...
Click to collapse
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Blackbox421 said:
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Click to expand...
Click to collapse
@rootSU has posted some new guides on rooting Lollipop, so best read his threads in the General section
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Blackbox421 said:
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Click to expand...
Click to collapse
That's correct!
EddyOS said:
That's correct!
Click to expand...
Click to collapse
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Blackbox421 said:
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Click to expand...
Click to collapse
It's all very easy with a Nexus device
EddyOS said:
It's all very easy with a Nexus device
Click to expand...
Click to collapse
Yeah I think I got it now. I unlocked my bootloader and flashed the official 4.4.4. factory image from the google developers website. Afterwards I booted into the stock recovery and wiped data/factory reset and reboot. Everything is fine now!
Thank you for your help! Learned a lot of basic understandings.
Jnewell05 said:
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Click to expand...
Click to collapse
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
rootSU said:
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
Click to expand...
Click to collapse
Huh, I thought the methods from your thread would be only for KitKat
Blackbox421 said:
Huh, I thought the methods from your thread would be only for KitKat
Click to expand...
Click to collapse
I usualy root my Nexus by booting into a custom recovery (TWRP), flash the latest superSU.zip and any mod i want and reboot/done That way i keep my stock recovery.