Related
I have a Mac, none of these .exe files will run. Is there a way I can just mount my Hero, download a zipfile, drop it in there and get a 2.1 ROM? I thought I could with Damageless?
um I have a MAC and you don't need any .exe files to root your phone. use the guide in the sticky at the top of the forum and your good to go.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
No, you must gain root one way or another to get a recovery image on there to flash ROMs...
Here:
http://forum.xda-developers.com/showthread.php?t=581686
Thanks, but I cant be assed doing all that work. Isnt there something that auto roots for you with a download and a few clicks?
yeah, but its an .exe. honestly, if you cant be assed to take 5 minutes to root manually, youre in wrong forum.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
abcdfv said:
yeah, but its an .exe. honestly, if you cant be assed to take 5 minutes to root manually, youre in wrong forum.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
I see. Once I root, I then have to flash a ROM too. This all takes 5 minutes? The instructions to flash dont look too detailed. Is there alot involved?
Rooting- quick. Flashing- pretty quick. First boot-dreadfully long.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
but u could flash it quicker with the Godspeed recovery.
Not to be a ****, but.....wow, are you going to piss and moan in every forum online about this? Didn't you say you were done with the Hero and going back to the iphone or something not to long ago in phandroid........Just root and get it over with already.
mbell75 said:
Thanks, but I cant be assed doing all that work. Isnt there something that auto roots for you with a download and a few clicks?
Click to expand...
Click to collapse
mbell75 said:
Thanks, but I cant be assed doing all that work. Isnt there something that auto roots for you with a download and a few clicks?
Click to expand...
Click to collapse
Well if you don't want do all that work then I suggest you just wait for the official release.
The only auto rooter is for windows. Rooting and flashing ROMs can lead to problems. If you are unwilling to put some effort into it then you are going to end up bricking your phone or running into what we on the forum would consider a small problem. However, it will turn into a huge issue because you don't understand some basic functionality of the recovery shell and wouldn't know how to access ADB to enter a couple commands to help diagnose.
This is an issue about you coming back and asking 101 questions and have people hold your hand because you can't be bothered to learn a couple things about a new world you are trying to enter.
If you are unwilling to learn then please leave these forums because I can tell you are going to be nothing but trouble.
spend the time reading everything fully first, this will save you time and make you more comfortable.
BTW, you can root with the flashrec method if you'd like with any computer platform, but to do anything useful like remove bloatware, you're going to need the adb from the SDK at least. I would root through terminal if I were you, its not hard and many helpful people on here, including myself. I've rooted 2 phones on mac, and 3 on PC already. Just give me a pm, if you run into trouble somewhere.
Things not to forget
USB debugging needs to be on (settings--applications--development)
commands in terminal require ./ before the adb commands
Rooting is easier on a mac than pc... no drivers to install.
rufflez2010 said:
spend the time reading everything fully first, this will save you time and make you more comfortable.
BTW, you can root with the flashrec method if you'd like with any computer platform, but to do anything useful like remove bloatware, you're going to need the adb from the SDK at least. I would root through terminal if I were you, its not hard and many helpful people on here, including myself. I've rooted 2 phones on mac, and 3 on PC already. Just give me a pm, if you run into trouble somewhere.
Things not to forget
USB debugging needs to be on (settings--applications--development)
commands in terminal require ./ before the adb commands
Rooting is easier on a mac than pc... no drivers to install.
Click to expand...
Click to collapse
Thanks. PM'd you.
mbell75 said:
Thanks, but I cant be assed doing all that work.
Click to expand...
Click to collapse
wow.. really?????
you cant be assed.. but your can be an a..
yes.. you can get 2.1 without Rooting.....
buy a phone with it on it!!!
i am normally really easy going and try to help.. I dont know much, but try to pass on what i have learned.. because others have helped me...
you and your statement above... has rubbed me.. in the wrong way.
Dan330 said:
wow.. really?????
you cant be assed.. but your can be an a..
yes.. you can get 2.1 without Rooting.....
buy a phone with it on it!!!
i am normally really easy going and try to help.. I dont know much, but try to pass on what i have learned.. because others have helped me...
you and your statement above... has rubbed me.. in the wrong way.
Click to expand...
Click to collapse
I so agree, just reading this guys post gave me a headache!
Tried doing this method http://forum.xda-developers.com/showthread.php?t=584029 and get stuck with the exclamation point triangle. Seems I need to do a wipe before flashing? Where do you get the zip that wipes the phone?
mbell75 said:
Tried doing this method http://forum.xda-developers.com/showthread.php?t=584029 and get stuck with the exclamation point triangle. Seems I need to do a wipe before flashing? Where do you get the zip that wipes the phone?
Click to expand...
Click to collapse
dont use flashrec jus do it through adb go to the stiki wiki and read how to root hero cdma for mac all you have to do is download the sdk it basically sets itsself up download asroot2 put it in the tools folder in your sdk and the recovery image of choice then simply copy and paste the commands from the guide its really that simple..
root with godspeed..........................woot woot
I would suggest rooting manually. You will learn some basic ADB commands.
maybe its just me but cant u use bootcamp and install xp or win7 and do it from there or is your Apple IIc just not up to the task..
mbell, didnt you get banned from android forums for spamming/flaming/trolling?
nothing personal but dont do that here or you''ll get banned even quicker.
But on the side note welcome to the forums! xD
Hello, I am new to XDA as being a member. This is my first post, and I promise I have spent at least an hour looking for similar threads to no avail.
Now to explain my problem,
Last night I rooted my kindle again after the 6.3 update that destroyed my last root. I used the Kindle Fire utility 9.5 by Vashypoo, and selected install permanent root with superuser.
As I discovered after this, I needed to get team win recovery before getting 6.3, so the KFU installed it for me, and it backed up my data before continuing with the rest of the root. After it said complete, I booted up my kindle, to find a yellow triangle and in a couple seconds, i got sent to this page automatically that I know now is the team win main menu. Every time I boot up my kindle, I get sent to the team win main page. I saw on a video by Nat3mil that the reason this was happening was because my kindle was automatically booting in recovery, so I tried to use kindle's bootmode menu to change the bootmode back to normal (4000) whenever I try, I get a message saying "The system cannot find the drive specified", and it would stop doing anything. I tried to manually set the bootmode back to normal by using command lines from a forum here on xda, similar to my problem, HOWEVER, whenever I try to connect my kindle to the pc, 9 out of ten times, my computer doesnt even recognize my kindle is connected, and when it does, it installs software, KFU says adb is online, and STILL whenever I try using KFU, command lines, or the Kindle Unbrick utility, it says "waiting for device". I literally cannot do a thing without help.... So to sum up, my problem is that I cannot connect my kindle to the computer, and second, I don't know what else to try... I really need help, and I have been doing tons of research (over six hours) to no avail, or progress.
Thank you for your time, and I hope that someone can help me.
Read this guide. It will give you an idea of what your problem is and what you are doing wrong. Its lengthy but worth it if you want do much with your Kindle, like installing recovery.
http://forum.xda-developers.com/showthread.php?p=23747567
Sent from my Amazon Kindle Fire using xda premium
your on the right path When you get it to say waiting for device hold the power button to shut the kindle off and then turn it back on and it will connect during boot up
soupmagnet said:
Read this guide. It will give you an idea of what your problem is and what you are doing wrong. Its lengthy but worth it if you want do much with your Kindle, like installing recovery.
http://forum.xda-developers.com/showthread.php?p=23747567
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
MLS_Dumpster said:
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
Click to expand...
Click to collapse
You have to get it to how you had it to say waiting for device... reinstall the drivers, reboot comp what ever you have to do than do what i posted... you can even open a command promp from the KFU tools folder by going to tools hold shift and right click... open command than type..
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
It happens randomly, You see, another problem I have been having is that, My kindle has no problem connecting to the computer, in device manager, I have adb interface up and running, my kindle connected, but it isnt useable, it says my adb is offline, and whenever that happens, I cannot do a thing... There is no tred whatsoever as to how to get adb working, as it happens at random tries of me installing the drivers, and restarting my comp/kindle, do you have any idea how to get it working? Thanks by the way, You literally are a lifesaver.
MLS_Dumpster said:
It happens randomly, You see, another problem I have been having is that, My kindle has no problem connecting to the computer, in device manager, I have adb interface up and running, my kindle connected, but it isnt useable, it says my adb is offline, and whenever that happens, I cannot do a thing... There is no tred whatsoever as to how to get adb working, as it happens at random tries of me installing the drivers, and restarting my comp/kindle, do you have any idea how to get it working? Thanks by the way, You literally are a lifesaver.
Click to expand...
Click to collapse
Im on linux so idk how to set it up on windows.... i have read of people having issues with the drivers and having to reinstall them after using kfu.. id just make sure you delete the kindle driver and the android adb composite driver and start fresh.. or even try and mount it threw twrp mabe that will help
Thanks for helping me, seriously. Windows is annoying with drivers. I'll try what you suggested. Thanks again
DJLamontagneIII said:
Im on linux so idk how to set it up on windows.... i have read of people having issues with the drivers and having to reinstall them after using kfu.. id just make sure you delete the kindle driver and the android adb composite driver and start fresh.. or even try and mount it threw twrp mabe that will help
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU
IT WORKED. YOU, sir, are a life saver.
Thanks again.
MLS_Dumpster said:
THANK YOU THANK YOU THANK YOU THANK YOU
IT WORKED. YOU, sir, are a life saver.
Thanks again.
Click to expand...
Click to collapse
Awsome
MLS_Dumpster said:
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
Click to expand...
Click to collapse
I wasn't trying to be rude but the exact problem you were having was covered in the thread that I posted along with the same solution suggested by DJLamontagnelll.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
I wasn't trying to be rude but the exact problem you were having was covered in the thread that I posted along with the same solution suggested by DJLamontagnelll.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I think I sounded more harsh than I meant to be. The solutions on the thread only cover one of my problems, and thats the drive thing. Thanks, you did help.
Sent from my Kindle Fire using XDA
Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.
nicolas_h18 said:
Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.
Click to expand...
Click to collapse
Please post in correct forum. G2 Q&A, Help & Troubleshooting
so long story short, i wiped all my data to flash a rom and forgot i hadnt re downloaded the zip and accidentlly hit reboot now and now i am stuck on the GOOGLE screen....ive tried reflashing the stock rom through the tool kit but all it keeps saying is waiting for adb...what do i do??? please help asap, thank you!
Try using wugs root tool to revert to stock. There is an option you need to check in that program which says that your tablet cannot boot up.
EDIT:
WugFresh said:
IF THE PROGRAM IS STALLING ON YOU (FOR ADB CHECK):
Restart the toolkit
On the main interface hit the "Launch" button to open Advanced utilities
In the advanced utilities interface; hit the "Launch CMD Prompt" button
Type the following cmd
Code:
adb start-server
Now you should be able to use any of the utilities in the toolkit without it stalling.
This extra step is just a temporary solution, until I release v1.5.3; then this won't be necessary.
Click to expand...
Click to collapse
Why does this not STOP, Your using the wrong section..
Also to fix the adb thing it says it in the original OP
Reboot into bootloader mods, hold power until it turns off, then hold power+volume down
Now go into toolkit and go to advance and click launch cmd, then type "adb start-server"
exit out of cmd and restore stock, make sure it says device is not on.
Some people just dont know how to read. SMH
im using the nexus 7 tool kit v 1.1.0 ....i opened..open manual command or whatever and typed what you said and it told me adb is not recognized as an internal or external command, operable program or batch file....omg, im screwed arent i ???? ....can u please guide me through this step by step...i havent had this thing 3 days already and its completely froze
it will not shut off!!! i hit all the buttons you have said and it just reboots to the google screen everytime....im lost!
blueizee said:
im using the nexus 7 tool kit v 1.1.0 ....i opened..open manual command or whatever and typed what you said and it told me adb is not recognized as an internal or external command, operable program or batch file....omg, im screwed arent i ???? ....can u please guide me through this step by step...i havent had this thing 3 days already and its completely froze
Click to expand...
Click to collapse
Did you open it up within the wugs toolkit? You need to open it up through the program, not through windows..
It honestly isn't hard. To be perfectly honest, if you can't figure out how to use a toolkit, or adb for that matter, you shouldn't be flashing roms.
P.S. You are far from bricked..
In the first place this does not belong here.
What the dude said, if you don't know what android sdk or java jde is dont flash roms
Install those two programs i mentioned reboot computer, now type that in.
Wow again??? This has to stop lol seriously
Everyday Thiers 2-3 post in the wrong section
Please pay attention ppl
Sent from my Nexus 7 using xda premium
listen big mouths...i made a simple mistake if you read my OP, i accidentlly hit reboot my tablet when i shouldnt have (first time mistake)...not on purpose, ok...and i apologize for posting here, i meant to go in Q&A but i panicked and didnt realize i was still in development...i know how to flash roms...im no genius but i know the basics and never bricked any of my android devices before, so i would appreciate you guys stop jumping to conclusions and give me a helping hand...thats what this site is for isnt it ? not smartass's. THANK YOU!
blueizee said:
listen big mouths...i made a simple mistake if you read my OP, i accidentlly hit reboot my tablet when i shouldnt have (first time mistake)...not on purpose, ok...and i apologize for posting here, i meant to go in Q&A but i panicked and didnt realize i was still in development...i know how to flash roms...im no genius but i know the basics and never bricked any of my android devices before, so i would appreciate you guys stop jumping to conclusions and give me a helping hand...thats what this site is for isnt it ? not smartass's. THANK YOU!
Click to expand...
Click to collapse
This isn't tech support
Sent from my SGH-I727 using xda premium
If what was posted above doesn't work
Hold power till it turns off
Hold power and vol down to boot into bootloader
Pulled straight from Google, a little searching goes a long way
On your PC, copy CWM-grouper-recovery.img into the same the folder where fastboot.exe is located. You can find fastboot.exe in the platform-tools directory inside the Android SDK folder.
Open a command terminal and navigate it to where fastboot.exe is located. Type this command and press Enter:
fastboot flash recovery CWM-grouper-recovery.img
After a successful flash, type this command:
fastboot reboot-bootloader
Select Recovery from the bootloader menu on your tablet to boot it into Recovery Mode.
Click to expand...
Click to collapse
You will probably have to do everything manually and push the new or stock rom if you don't know how to do that, you got a lot to read.
This is why tool kits are bad. If you had adb and knew a few basics this thread wouldn't exist.
Sent from my SCH-I535 using Tapatalk 2
BaconStep said:
This isn't tech support
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Sure seems like I saw people trying to help you out with some storage issues you were having in the Glazed thread. I don't have anything to help the OP, but I felt like calling out a hypocrite.
Semantics said:
Sure seems like I saw people trying to help you out with some storage issues you were having in the Glazed thread. I don't have anything to help the OP, but I felt like calling out a hypocrite.
Click to expand...
Click to collapse
Lol
Sent from my SGH-I727 using xda premium
Learn to use fastboot and flash factory images. Read the guide. Read it again. Fix your device.
/ end thread
I received a nexus 7 from a family member that has a X on it. I downloaded Nexus 7 Toolkit 4.0.0 and tried the stock reflash and all (option 9?) and it finally seemed to complete correctly after randomly closing a few times but now it's still stuck on the X.
How do I know my build to make sure I am selecting the right image? I just googled my baseband and the version 4.1.2 popped upbeside it in searches so I went with that.
It seems like I can't get the most recent update to the toolkit unless I pay for it, but I only planned on using it once and don't even know if that would solve my problem. If i knew for sure it would, sure I would purchase it. Any idea what I might be doing wrong?
Thanks
kmad86 said:
I received a nexus 7 from a family member that has a X on it. I downloaded Nexus 7 Toolkit 4.0.0 and tried the stock reflash and all (option 9?) and it finally seemed to complete correctly after randomly closing a few times but now it's still stuck on the X.
How do I know my build to make sure I am selecting the right image? I just googled my baseband and the version 4.1.2 popped upbeside it in searches so I went with that.
It seems like I can't get the most recent update to the toolkit unless I pay for it, but I only planned on using it once and don't even know if that would solve my problem. If i knew for sure it would, sure I would purchase it. Any idea what I might be doing wrong?
Thanks
Click to expand...
Click to collapse
I know this may seem kinda silly, but I had a really similar problem and I solved it by going into Recovery and wiping everything, then I was able to flash another ROM from too manager.
MarioES said:
I know this may seem kinda silly, but I had a really similar problem and I solved it by going into Recovery and wiping everything, then I was able to flash another ROM from too manager.
Click to expand...
Click to collapse
Yeah, that was the first thing I tried.
kmad86 said:
Yeah, that was the first thing I tried.
Click to expand...
Click to collapse
If that didn't work I'm afraid a manual flash is your only option, don't think any toolkits will work.
http://forum.xda-developers.com/showthread.php?t=1781250
Check that out, pretty straightforward and should do the trick.
MarioES said:
If that didn't work I'm afraid a manual flash is your only option, don't think any toolkits will work.
http://forum.xda-developers.com/showthread.php?t=1781250
Check that out, pretty straightforward and should do the trick.
Click to expand...
Click to collapse
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
kmad86 said:
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
Click to expand...
Click to collapse
You need to download the Android SDK for that so you can have the fastboot program. Download and install that first then you can proceed to flashing a rom using the fastboot command.
kmad86 said:
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
Click to expand...
Click to collapse
I'm not very good at this stuff either, and a manual flash was the first thing I tried. You'll get it!
If you can't boot into Android skip step 3 and go to 4, which is the same (just that you're loaded into the bootloader, which you should be able to access).
About the other issue, google it and look for a londatiga.net link (can't post links as a new user). All you need is the Android SDK
MarioES said:
I'm not very good at this stuff either, and a manual flash was the first thing I tried. You'll get it!
If you can't boot into Android skip step 3 and go to 4, which is the same (just that you're loaded into the bootloader, which you should be able to access).
About the other issue, google it and look for a londatiga.net link (can't post links as a new user). All you need is the Android SDK
Click to expand...
Click to collapse
I found FastBoot in the Platform-Tools folder, but I double click it and a command prompt looking screen pops up, but disappears.
EDIT: Got it.
Thanks for the help
Ok, so I figured out the command prompt.
For those of you searching for this, and in the same situation as I, I clicked on Start>and searched Command where my command prompt popped up as C:\users\admin> and i was really confused. From there my Toolkit was in Desktop>Nexus 7 Stuff>Toolkit>ADT Bundle>SDK>Platform-Tools.
I typed in command prompt "cd desktop" and enter. Then I was at C:\users\admin\desktop> From there I entered "cd nexus 7 stuff" and enter. and on to toolkit, then the next until I was at platform tools. Then I followed the instructions and whala!
(Now I am stuck on writing "boot") i've searched and found nothing.
Is lg or Google providing flasher for N4.if yes then how to get it.
If no then which is safest way to flash N4.
I an not having any idea about android . N4 is my first android device so please help me.
http://developer.android.com/sdk/index.html
Then read the many tutorials around here.. Stay away from Toolkits..
Toolkits are for begginers. He's not gonna know how to fastboot flash that fast either. But I recommend that being your last option.
Sent from my Nexus 4 using xda premium
styckx said:
http://developer.android.com/sdk/index.html
Then read the many tutorials around here.. Stay away from Toolkits..
Click to expand...
Click to collapse
I am reading couple of tread but I can't stuck to one of the method.now I am reading efrant method shall i try this. basically i am not understand collecting drivers and flashing .is their any method just installing pc suit & all legal work which we use for older devices. one more how to launch command prompt do i type it in "RUN".
I dont understand why he should stay away from toolkits, I mean that f he doesn't want to learn how to develops roms than toolkits are the best for him
Sent from my Nexus 4 using xda app-developers app
Odp: how to flash(format) N4.
OH cmon guys. Toolkits are good for noobs. I tried to use those all tutorials and i didn't even install proper drivers correctly. IF he screw up smth he will be dissapointed. My opinion first toolkit than learn and do it manualy if you want.
Sent from my Nexus 4 using xda app-developers app
GS150R said:
I am reading couple of tread but I can't stuck to one of the method.now I am reading efrant method shall i try this. basically i am not understand collecting drivers and flashing .is their any method just installing pc suit & all legal work which we use for older devices. one more how to launch command prompt do i type it in "RUN".
Click to expand...
Click to collapse
- Install the Naked usb drivers 0.72 from here http://forum.xda-developers.com/showthread.php?t=1996051
- Install the Platform-tools from here http://developer.android.com/tools/sdk/tools-notes.html.
- Connect the phone with the pc and install the drivers you downloaded.
Set up adb, here is a how to http://forum.xda-developers.com/showthread.php?t=1590800
Open cmd and type : adb devices, you should see a serial number now.
Type the command and hit enter.
Some Adb commands:
See if the adb drivers are installed correctly: adb devices
Reboot: adb reboot oem
Bootloader: adb reboot bootloader
See if the fastboot drivers are installed correctly: fastboot devices
Unlock bootloader: fastboot oem unlock
Flash recovery: fastboot flash recovery recovery-name.img
Flash kernel: fastboot flash boot name boot.img.
I hope this is a kind of a start to get familiar with this stuff, the problem with toolkits is that you will stay a noob forever and when a problem occurs people have no idea how to fix it because they often have no clue whats happening.
Using a toolkits is like watching tv all the time, it prevents you to think and it softens the brain
Odp: how to flash(format) N4.
Open command and write: adb devices. Nothing happen. I got installed drivers correctly because i root my phone already. Wrong command or filename.
Sent from my Nexus 4 using xda app-developers app
Adikbzik said:
Open command and write: adb devices. Nothing happen. I got installed drivers correctly because i root my phone already. Wrong command or filename.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
first type: cd c:\android-sdk\platform-tools or wherever you installed the sdk. The sdk folder must be installed directly on the C (or other) drive and NOT in a map/folder.
Here is a tutorial to set up adb: http://www.youtube.com/watch?v=oaNM-lt_aHw
Adikbzik said:
OH cmon guys. Toolkits are good for noobs. I tried to use those all tutorials and i didn't even install proper drivers correctly. IF he screw up smth he will be dissapointed. My opinion first toolkit than learn and do it manualy if you want.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
toolkits are great, but every single time ive used them for nex4 i had a broken phone afterwards. even for such simple things like flashing a recovery. fastboot is such a simple tool, i would also recommend using that instead.
molesarecoming said:
toolkits are great, but every single time ive used them for nex4 i had a broken phone afterwards. fastboot is such a simple tool, i would also recommend using that instead.
Click to expand...
Click to collapse
Everything you know or are able to do is easy
The first time you do this however is always a search and trial and error thing.
I agree, efrants guide is kinda confusing if your completely new to android. But its very complete, here's another way you can go about using it...
1st, follow steps 1-8 (stop after unlocking boot loader) in this root tutorial. http://www.androidrootz.com/2012/11/how-to-root-nexus-4-on-windows.html?m=1 . this is an easy way to get your fastboot folder set up. Power off phone when done.
Next, download the nexus 4 Occam image here: https://developers.google.com/android/nexus/images#occamjdq39 . use 7-zip to extract it anything that is a zip file. Youll probably have to extract 2-3 times to get all 6 .img files you need. Once you get all 6 img files, move them to the Rootnexus4 folder.
Last, power your phone back into the boot loader by holding the vol buttons + power. Go back to efrants tutorial, go back to your command prompt, and start with part D) 6 (the part about flashing boot loader). Keep on following the instructions from there and u should be good to go http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using xda app-developers app
I got SDK working now. Thanks for video, nowhere says to add path in Computer properties that's why my command didn't read adb. Now i can use brain to flash :victory: