Database Users

1 Click root brick?!

So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard

I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.

Stop using one click crap. If you don't know what you're then you should not be messing with your device.

Sent from my DROIDX using XDA App

I can. Just won't.

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.

albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for

The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.

csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.

Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.

Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App

Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process

After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.

@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.

In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?

Unlocking Xoom's bootloader

It's easier as you may think .
1st - Be sure you want it, because you will format your internal data and lose your warranty!!!
Ok then after accepting the 1st option let's continue
Download the archives on the attachment.
Unzip it on C:. Or, if you prefer: C:\
Now plug your Xoom via usb.
Wait windows install ALL drivers
Then open cmd and type:
Code:
cd C:\Xoom bootloader unlocker
adb reboot bootloader
fastboot oem unlock
Read the Caution message on Xoom (maybe in the next weeks I post it here), and to accept press vol down and then vol up. If you changed your mind while reading the Caution page (like me ), just press vol up, then softreset your tablet pressing vol up+power button and pressing for like 3-4 seconds.
I hope it helps you to unlock bootloader, as well I learned, with some facebook posts help, I wanted to share with you.
(Optional)
If you want to Root and install CWM too, follow this rules:
1st - Download this recovery image: http://api.viglink.com/api/click?fo...rs&txt=here.&jsonp=vglnk_jsonp_13180302664331
2nd - save it on C:\Xoom bootloader unlock
3rd - type on cdm:
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
4th - Boot into recovery by booting the tablet (using power button + vol up), pressing vol down and vol up on Android Recovery
4.5th - To use CWM use the vol buttons to select the option and power button to enter.
5th - Then on CWM install the zip (this one http://api.viglink.com/api/click?fo... version 1.0&jsonp=vglnk_jsonp_13180304832863 remember to put it on your sd card!) from sd card (sorry you need one ).
(Ps.: A very BIG THANKS to solarnz for this root option. Remember to thank him on his post (http://forum.xda-developers.com/showthread.php?p=17135571&posted=1#post17135571))
Cheers and Good Luck .

Reserved this one

I guess a free bump for you but this is really common knowledge now. Been so since day 1...

I know it, but i just did it cause i know there are people who doesn't know how to do it. And i want help them , do you understand?
Cheers.
Sent from my MZ605 using XDA App

XxLordxX said:
I know it, but i just did it cause i know there are people who doesn't know how to do it. And i want help them , do you understand?
Cheers.
Sent from my MZ605 using XDA App
Click to expand...
Click to collapse
FWIW - I don't understand the need to start a new thread that is essentially a copy of someone else's work, and adds nothing new .... In fact, several good reasons not to. Just saying ....

Moved to general because this is pretty much common knowledge by now and not really development. Thread not deleted / closed despite the fact that this information is elsewhere because the OP has done a good job at making this very basic for even the noobiest of users to follow.

Moderator thanks for understanding me

I having some problems typing the cmd fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img. It will say error: cannot load 'recovery-Tiamat-R4c-100611-1150-cwm.img'. The file I downloaded doesn't have an image file with it, but so I installed one from a another xda forum. will it go in same C:\Xoom bootloader unlocker file. or could it be messing up since i'm running xoom wifi 3.2.1
Edit:After looking over the command lines again I forgot to put cd C:\Xoom bootloader unlocker, and that fixed it! I gave you a five star for this thread. I've been trying to root my device for about two weeks non-stop. Saved me $50, because I was going to pay somebody that much to do it for me.

I'm happy for helping you

Does this apply for xoom 3.2?
Sent from my PG86100 using XDA App

Links also doesn't work.
Sent from my PG86100 using XDA App

Thanks for sharing

MarioJp, tell me the links not working...
Murtexx You are welcome
Sent from my MZ605 using XDA App

mariojp said:
Does this apply for xoom 3.2?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Sorry but don't know :s maybe works, because ig's the bootloader not the android version, anyway the root works (on official post it says it's universal, but I don't have 3.2 to tell you)
Sent from my MZ605 using XDA App

....................... +1

I don't understand why anyone except a very rabid hacker who hasn't already done this (like me - only had mine a few weeks) would go through the hassles of doing this only to have to undo it with ICS coming relatively soon.
But we all have our hobbies - it's all good.

I just get error: device not found
My Xoom is plugged in and I even turned on USB debugging mode. I can see it in Explorer. Are there some drivers I am missing?

Download some from motodev, just search for Xoom drivers. The link is here: developer.motorola.com/docstools/US...ou need it.
Sent from my MZ605 using XDA App

Just putting it again on the 1st page of the forum, want people view it to be helped

ok so i was able to unlock boot loader but it doesn't apply the root it gives me the error
:cannot load recovery and it does go on adroid recovery but that's it what am i missing?

Stuck on X, Reflashed using Toolkit and still stuck. How do I know build?

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.

how to flash(format) N4.

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:

Did you use a toolkit ?

So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app

yes
Sent from my Nexus 4 using xda app-developers app

Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688

Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4

g2uzer said:
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
I used Mr Skip's and it worked really well, most important thing to get right is installing the drivers on your PC, I donated to him cause it has so many options and worked so well

Never have and never will. Once you learn fastboot it's too much fun playing in the command prompt lol.

spaceman860 said:
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475

g2uzer said:
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4

spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
i disagree with you..
instead of using "done", id use "profit" :silly:

spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app

soham_sss said:
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device

simms22 said:
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
Click to expand...
Click to collapse
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app

g2uzer said:
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd like a video of this too.
Can you brick your phone while unlocking? Or just while flashing?

g2uzer said:
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
use the nexus 4 toolkit by msskip..
its the best one so far and very easy to use...and dont worry abt bricking..
post if any issues,,.

No toolkit. It's important to know how to use fastboot.
Sent from my Nexus 4 using Tapatalk 4 Beta

Unlocking the bootloader and rooting for new users
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:

sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app

g2uzer said:
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, like I said, the toolkit makes it a lot easier to flash a factory image and frankly, I think it's safer. Less room for mistakes. The less you toy around with flashing the bootloader and the radio, the better chance you have of not bricking your device. Fortunately, when your bootloader is unlocked, as long as you aren't doing anything crazy, you will have a hard time bricking your device. If you have any further questions while you're working on it shoot me a PM and I will try to help. Good Luck!

sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Superb, all this I know already as I did this with one v
But, I read in some tutorial that if you don't reboot to stock recovery and data reset your phone AFTER you've unlocked the boot loader, you will end up with a soft brick? Is it true?
Sent from my Nexus 4 using xda app-developers app

I've been playing g with androids for a long time and dozens of devices. Personally have never used a toolkit and its hard for me to recommend or knock them.
My view is a toolkit teaches you nothing
If a toolkit was made so was another method
Everyone will have an issue with something at some point, so the more you learn now the less freaking out latter
Learning to do thongs yourself will always be safer, I mean yes manually typing a dd command can be dangerous but if you know what you are doing you know when to be cautious, there will always be an example for either argument on this, but I truly can't see a reason to believe a tool kit is safer
But I'm a to each their own sorta guy, but also one who feels the need to learn as much as possible so will promote as much manually methods for anything in life and will do my best to stay away from auto-just-about-anything.... Just a my $.02
Sent from my Nexus 7 using xda premium