Related
Hi, my phone now is working and all ( the is it bricked post) Thanks guys
Here is the new problem...I would like to go to 2.2.1 ( the passimg.zip is 2.2) is there a way to update without unlocking bootloader.
I tried Androot and superoneclick....Androot gives me the Fugu message and SuperOneClick says its Rooted...but when I go to rom manager or other apps that need superuser...
I get this message : An error occured while attemting to run privileged commands!
So basically Root isn't working.
Also, when trying to install Cyan cm6...Rom manager reboots...but I get the Triangle with the exclamation point with the green man next to it...
Is it still possible to have my cake and eat it? ( locked phone, with root access so I can install modded roms)
Again...can someone help me with this
Thanks!
You didn't have to make a duplicate post. I already answered one of your questions in the other thread.
Dont make another post next time...
I rooted FRG83D with superoneclick root, But if its not working for ya you will have to unlock the bootloader via fastboot. Then push a custom recovery. With the recovery you can install the su binaries.
Manual root:
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
Ok i'll only answer here now for this question:
I don't want to loose my warranty. Hence the softroot way.
I thought of something dunno if its possible:
is there a stock FRG83 image like the FRG33 I just installed....maybe 2.2.1 will be compatible with androot or superoneclick
Thanks
You need to do a few things before you go any further. There are key steps you are leaving out that are just a recipe for disaster. I'll detail them below, in the specific order you should follow them. There shall be no deviation from this list.
1 - Put your phone down. Seriously, stop messing with it. Just quit.
2 - Read the Wiki that you've been linked to, in both threads, several times.
2a - Now that you've read the Wiki, really read the Wiki. Yeah, you skimmed it the first time, I know you did.
2b - Now go read it again. I'm sure you'll notice something new this time.
2c - Now go read the links in the Wiki. Explore those threads.
2d - Those threads that the Wiki links to? They have links in them. Go read those.
3 - Rinse and repeat all steps from 2a to 2d for, oh, about 4 days. During this time you are allowed:
To post general chit chat on the forum. No technical stuff, no help threads, no questions. Just read. If you have questions, you need to read some more.
No more than 3 app installs per day, from the market. Thou shalt not download and install any APKs from any source that is not the Android Market.
To tweak settings on your phone, provided those settings are all done via the touchscreen on your phone. You shall forget the acronym "ADB".
Once you've done that, you'll root your phone in no time, and you won't be worried that you've bricked it. Then, and only then, can you start asking questions.
Why? Because all of your questions right now are answered. You're jumping the gun, and it's obvious you haven't done much research at all. Seriously, go read.
I hate to be mean, but if you want to understand stuff, you need to try and understand it on your own first. You're here looking for solutions (that are already spelled out) to problems that you created (because you didn't read anything). Quit looking for the easy way out. If you want to enjoy your phone and the features of what you're trying to accomplish...put some work in yourself, and stop expecting everyone else to fix everything and spell it out. People here are more than happy to help, but you gotta start helping yourself.
@Soberguy: Thumbs up to you. Couldn't have said it any better.
musashiken said:
@Soberguy: Thumbs up to you. Couldn't have said it any better.
Click to expand...
Click to collapse
Thanks, mate. Didn't mean to quote the guy above me, just noticed I did that. Fixed it.
I'm amazed at the patience some folks have. Maybe it was my rough 3 day weekend that's left me a bit short... Appreciate the thanks, all the same.
Ok, I do go a bit fast.
I'll read...it just that I tried the cm7 mod ( i know its experimental) and the phone
would'nt boot.
With the help of the great people on the board, I got my phone working again but on FRG33 (2.2)
My last question was if it was possible ( or someone knows of because Ive checked the net) to root without unlocking ( androot and superoneclick that i know of) if I have FRG33 ( Because Ive been getting permission errors)
Finally, I wanted to know if a FRG83 stock image was available so that I could recover to it without unlocking bootloader. (or any other stock that lets me root without unlock)
I'll unlock the phone as a last option...I'm sorry...And if anyone is pissed at my posts ...well sorry I just taught some of you experts could help.
pooky2010 said:
Ok, I do go a bit fast.
I'll unlock the phone as a last option...I'm sorry...And if anyone is pissed at my posts ...well sorry I just taught some of you experts could help.
Click to expand...
Click to collapse
See? Looking for the easy way out again.
It's not about anyone being pissed or short on patience. Look at how frustrated you are with the situation. You're frustrated. Why? Cause you did it wrong. Why? Cause you didn't read enough first. Even after several suggestions, you still want it done, with help, right now, or you'll sulk about someone pissed and how no one held your hand through it.
Is it possible to do what you want? Absolutely! Pretty easy, too. But if you read and help yourself, you'll better understand how to update in the future, as well as how to root the future update. Or, you'll learn how to root what you have, and flash a pre-rooted stock ROM (yes, those are here as well).
So call me an ass, cool. You did in your mind, that's fine. But really, I'm trying to let you know what will help you the most, and that's having a better understanding of how to prevent a boot loop in the future, or at least how to fix it if it happens. Best of luck, man.
Sent from my Sexy Nexy, courtesy of the fine developers of Tapatalk
Here's the deal.
I did a one click root without unlocking the bootloader. Then I installed rom manager and flashed clockwork recovery. Then I did a backup ( both done in rom manager) then I went back into rom manager and installed cyanogenmod 7 and my nexus is now haxored gingerbread. Make sure you do a full wipe before flashing new roms and it'll always work.
I didn't update my radio, my hboot or anything like that. And it all just works and is dead simple. I would suggest trying z4root or universal androot and then downloading rom manager from the market.
How you managed to **** up something so simple is pretty funny dude.
I'm using an at&t band n1 with an smiled. Not the one with super LCD. I heard a rumor that the super LCD n1s have problems with certain mods. You might want to figure out what type of screen you have too.
The cyanogenmod wiki at cyanogenmod.com might help you too.
Sent from my Nexus One using Tapatalk
OP, you have to learn the hard way. Stop using "newbie" as an excuse.
I was also a "newbie" when I first got my Nexus One in February. Everything about android was new and alien to me. It actually took me a couple of months of lurking in xda and reading up on tutorials before I took the plunge to rooting my phone. And I did not bother anyone on that. I made sure I understood the steps and triple checked every move I made in following instructions even though I did not understand them.
I also was worried about warranty and actually did the manual way of rooting my phone without unlocking the bootloader using some method that involved cutting a piece of plastic from my battery. That was nerve wrecking and no where as simple as the superoneclick thingy you have now. Yet I survived and I did it on my own.
I must admit that you have to be a little bit confident in using computers and have some basic knowledge of typing commands in cmd. But everyone has to start from somewhere.
Seriously if it's too much trouble or too complicated, maybe staying stock or going Iphone is a more comfortable alternative.
I'm actually pretty good with computers...
Also, I have bricked 4 phones (the provider took them back) fooling around...
I could brought this one back ( they didnt check). But I want to learn...I'm pretty impulsif...Anyway so far
With FRG33 z4root works (read thanks)
Now I trying to flash clockwork...( when I download cyan 6 +google apps) it reboots but I get the triangle thingy...I click power volume up ( read that thanks) I get a blue menu...I kinda scared to click an option so I rebooted...I'm trying to use rom manager for updates because its really simple ...anyway
Thats it for tonight All of you guys are nice dudes and I'll learn and will try to help im my own way...I know I'm a newbie that likes short cuts (hell I read all day at my day job...lol) This is fun ( playing with male toys)
Thanks guys!
hi,
I want to root my Desire Z as I would like to use Titanium Back Up Pro. I have checked thru the threads here. And, well, I am totally confused.
On TheRomMistress's great sticky there are 27 guides with at least 11 dealing with rooting the phone. Some of these guides refer you to other guides and these refer you to yet more guides for various reasons (updates etc).
I know a lot of the guides were initially worked out before the whole NAND lock was cleared up.
So my question is which guide should a noob follow to get root?
I love the whole android experience, love Sense and think my phone is all shiny, sparkly etc. I may want at a later stage to try out some of the other ROMs but so far I really love stock (heck, my previous phone was a windows 2003 Magician with BigStorage courtesy of XDA!!). I just want to be able to back it up.
Thanks for your help guys.
personally i used this guide:
http://forum.xda-developers.com/showthread.php?t=843014
worked well once i had reset my phone and made sure my sd card was clean. Read up on adb before you attempt though so you know what is happening at each stage, it makes the whole process easier. And if things don't work as expected you'll be able to sort it.
The method listed in the official Wiki is the one recommended by most people nowadays: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#OTA_Updates.
It is generally considered the "safe" way to attempt root at this point. There were reports of semi-bricks caused by the permroot function in Visionary so general consensus is not to use it. For other guides (such as the one linked to earlier), if you have a typo while flashing the engineering HBOOT, you could cause a semi-brick as well (though if you follow the instructions carefully, it shouldn't be a problem).
A typo with the Wiki method shouldn't lead to a semi-brick though. It also has the added benefits of not only giving you root, but also true radio S-OFF, SuperCID, and subsidy unlock (if your phone was originally locked to a specific carrier).
That being said, as long as you read carefully and follow instructions, you should be fine following most any of the guides.
thanks guys for the answers and sorry for my delay in replying. The wife came home with a new netbook that she "needs". I do get the joy of setting up something I'll never get to use. Yay!! hmmmm
I'll read thru all this and hope to try this out over the weekend.
Again thanks guys.
Just use gfree method, its painless
Sent from my HTC Vision using XDA App
Sorry for responding so late, just wanted to say thanks again. Took me ages to get around to doing this. Work just went crazy busy Again thanks for your help guys.
ok a little backround i switched from a palm pre 4 months ago so i got myself pretty comfortable with the web os and i got the pre the first day it came out so i actually had to root it this was before all the one touch stuff. but there was always the webos dr to help me out if i screwed up. as far as my shift goes unfortunatly ive updated it so i know im gonna have to wait to root it. But can someone point me in the direction of where i can find info on the process. i am by no means a tech guy but i follow directions well. Ive been reading on adb and sdk and i dont quite understand everything i am reading. is there some things i should put on my pc. any advise or help is appreciated thanks
On tapatalk so to lazy to find links but:
One of the stickies on the dev forum is what exactly you're looking for.
Edit: the stuff below does not work according to another thread
Also someone smarter needs to verify this but I believe you can ruu back to an older version which would enable you to root.
Find the one zip unroot thread, also in the dev section. I believe the op has multiple versions now. Find the oldest version, restore your phone to that version and root using the guide mentioned above.
again, not 100% on that so be careful
Sent from my PG06100 using Tapatalk
Check the dev forum, you also don't need adb or the sdk to root the phone its just easier to copy and past the commands. As soon as root came out for this phone I put the files in the root of my sdcard and used connectbot to run the commands.
Sent from my PG06100 using XDA App
Phandroid has a pretty simple root guide in the Shift forums if you are still running Froyo (2.2). They basically tell you what to do step by step.
"Rooting" the pre was easy. If you tried to but 2.1 on the Sprint Pre, you had to perform some command line functions. Android tends to play nicer with windows in regard to that area.
They don't have the root process for the update yet. So unfortunately, there's nothing to look for.
Evo SHIFT
Starting off, I'm probably posting in the wrong section. Excuse my forum etiquette, but I need help with this because I'm insanely frustrated and in pain (Decided to learn how to exploit the android OS while recovering from my surgery).
So, if you've read past that first part and are still willing to help, thank you.
Moderators: If you absolutely need to move this post, please move it to a section where it will actually get attention and I can get an answer. Thanks.
Anyway, the breakdown of my problem is this;
I wanted to root my new day old Sprint CMDA Nexus S, I've never rooted anything android, and if anything the most I've done with a droid OS is installed it on my old iphone 2g.
So I did some googling and first thing to come up was this guide:
nexusshacks(dotcom)/nexus-s-hacks/how-to-root-nexus-s/
Now, usually I would do a bit more research, but because of the lack of blood in my body I'm doing dumb things, making bad decisions, whatever.
So obviously this guide doesn't work, even a quick skim of the comments shows that, I try to follow this guide-
I followed step "fastboot flash boot rootboot.img" then tried to reboot. It freezes at the google boot logo. This is where I start getting a bit nervous because I have absolutely no idea what I'm doing.
So I think "Well, if I jump over to someone elses tutorial and do that it should overwrite any "root"ing data I've tried to put into the device.
So I jump over to this:
androidadvices(dotcom)/root-sprint-nexus-gingerbread-235-update/3/
It has me install PDANet and it's frozen since on the installing PDAnet to your phone.
I just want to get my Nexus S back to original factory default so I can start fresh from there without a terrible guide.
Can someone please help me get there?
Thanks.
tl;dr:
Bad guide soft bricked my phone and I want to restore it to factory defaults
agnl said:
Starting off, I'm probably posting in the wrong section. Excuse my forum etiquette, but I need help with this because I'm insanely frustrated and in pain (Decided to learn how to exploit the android OS while recovering from my surgery).
So, if you've read past that first part and are still willing to help, thank you.
Moderators: If you absolutely need to move this post, please move it to a section where it will actually get attention and I can get an answer. Thanks.
Anyway, the breakdown of my problem is this;
I wanted to root my new day old Sprint CMDA Nexus S, I've never rooted anything android, and if anything the most I've done with a droid OS is installed it on my old iphone 2g.
So I did some googling and first thing to come up was this guide:
nexusshacks(dotcom)/nexus-s-hacks/how-to-root-nexus-s/
Now, usually I would do a bit more research, but because of the lack of blood in my body I'm doing dumb things, making bad decisions, whatever.
So obviously this guide doesn't work, even a quick skim of the comments shows that, I try to follow this guide-
I followed step "fastboot flash boot rootboot.img" then tried to reboot. It freezes at the google boot logo. This is where I start getting a bit nervous because I have absolutely no idea what I'm doing.
So I think "Well, if I jump over to someone elses tutorial and do that it should overwrite any "root"ing data I've tried to put into the device.
So I jump over to this:
androidadvices(dotcom)/root-sprint-nexus-gingerbread-235-update/3/
It has me install PDANet and it's frozen since on the installing PDAnet to your phone.
I just want to get my Nexus S back to original factory default so I can start fresh from there without a terrible guide.
Can someone please help me get there?
Thanks.
tl;dr:
Bad guide soft bricked my phone and I want to restore it to factory defaults
Click to expand...
Click to collapse
Ok I can see you need help but I am inclined to warn you instead. Stop. If you cannot figure out how to root the easiest phone to root then you shouldn't be messing around with your phone. You will end up screwing something up, won't know how to fix it, and come crying here for help. Do yourself some research before you go and ruin your phone.
Yes you posted in the wrong place.
There is a thread in this forum on how to root the nexus s 4g. Rooting is model specific. The T-Mobile Nexus s is different from the sprint, att, Rodgers, o2 etc.
Please please do some more research!
Sent from my PC36100 using XDA Premium App
Thanks for a reply, and I understand I dug a hole.
Now I need to get out of said hole, so if you had any directions of how to dig myself out, that'd be great.
if you can get into fastboot then you are still cool, if not you're gonna have to odin it. I dont actually know where the tar files are, Micheal posted it up but i think they deleted the thread. You should have came to xda first,we have one clicks.
actually rooting is the same across the board. same steps same everything... in fact the one click root version 1 would work on any and all of them, version 2 branches out a bit further due to that it installs cwm.
anyways boot into fastboot, download stock fastboot images from petes thread found here http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip and flash them all in fastboot.
youll be back on stock grj22 but youll at least be booting.. from there follow a guide for rooting this phone that has you flash cwm (not a prerooted kernel). or be lazy and use my one click root
You sir are a class act. We need a ton more guys like you here at XDA
shabbypenguin said:
actually rooting is the same across the board. same steps same everything... in fact the one click root version 1 would work on any and all of them, version 2 branches out a bit further due to that it installs cwm.
anyways boot into fastboot, download stock fastboot images from petes thread found here http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip and flash them all in fastboot.
youll be back on stock grj22 but youll at least be booting.. from there follow a guide for rooting this phone that has you flash cwm (not a prerooted kernel). or be lazy and use my one click root
Click to expand...
Click to collapse
mikeyinid said:
You sir are a class act. We need a ton more guys like you here at XDA
Click to expand...
Click to collapse
+1
Sent from my Nexus S 4G using XDA Premium App
mikeyinid said:
You sir are a class act. We need a ton more guys like you here at XDA
Click to expand...
Click to collapse
lol you give me way too much credit mikey but thanks for teh vote of confidence
Hi all,
I see the android development section has a lot of goodies in there and i have had great experience with custom ROMs on my old Galaxy S1. But for the GN4. Is there any value addition to the stock ROM, in the custom builds so far?. Kindly share your feedback on the custom ROMs that you.
P.S: I haven't yet rooted the device (i know) ... can someone kindly send me the easiest way to do that as well.
Thanks a bunch for your time.
As far as rooting go just download the toolkit from the dev section follow the instructions on that thread.
And with the custom roms read the thread try them out every dev adds there own tweets. You can always go back to a backup
Sent from my E10i using Tapatalk 2
Personally, I read through the pinned threads and unlocked my bootloader, flashed touch CWM and rooted my phone right after getting it. As for custom ROMs - I don't feel the slightest urge as the rom is imho perfect; although I was a keen flasher before I sold my Galaxy S II.
Custom ROM for N4 are very stable and smooth like stock, maybe even more smoother. More feature like editing nav bar and so on. Happy flashing
Sent from my Nexus 4 using Tapatalk 2
Thanks guys. definitely gona root the device, gona make a nand and try a couple of customs out as well.
ChrisHRocks said:
As far as rooting go just download the toolkit from the dev section follow the instructions on that thread.
And with the custom roms read the thread try them out every dev adds there own tweets. You can always go back to a backup
Sent from my E10i using Tapatalk 2
Click to expand...
Click to collapse
Highly advise against doing this. Prefer yarox method do it manually as you'll need to do fast boot and adb commands eventually. Just take the 20-25 minutes and learn how to do it now. It's very easy and they are stickied for a reason.
Toolkits are very dangerous. The shortcut isn't worth it.
Sent from my Nexus 4 using xda premium
zephiK said:
Highly advise against doing this. Prefer yarox method do it manually as you'll need to do fast boot and adb commands eventually. Just take the 20-25 minutes and learn how to do it now. It's very easy and they are stickied for a reason.
Toolkits are very dangerous. The shortcut isn't worth it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Never liked them!! Besides you don't learn anything using toolkits...
yyz71 said:
Never liked them!! Besides you don't learn anything using toolkits...
Click to expand...
Click to collapse
Exactly. It's not like you're learning useless crap that you wouldn't use.
In fact for anyone flashing anything on their phone and not knowing a plan b if something goes wrong is scary, then they start panicking and out of no where make a forum thread. Bricked phone??? Uh no man. Anyone bricking a nexus device doesn't deserve one to be honest. It's so hard to brick one because of fast boot factory stock images.
A simple 20-25 minute step by step guide. It pretty much carries you through it and is more important than that lecture you attend every Tuesday that chances are you'd fall asleep because the professor isn't enthusiastic with his studies
Sent from my Nexus 4 using xda premium
May I suggest using wug's nexus root toolkit. Safe and easy with just clicking your mouse. You will be amaze!
Sent from my Nexus 4 using Tapatalk 2
droidmeup said:
May I suggest using wug's nexus root toolkit. Safe and easy with just clicking your mouse. You will be amaze!
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
No. Did you really just say that after what we just said?
It's easy using a toolkit but also very easy to screw up your phone because people using it are clueless and flash whatever links making their phone into a non boot able state.
http://forum.xda-developers.com/showthread.php?t=1469909 is a great read on this topic.
Sent from my Nexus 4 using xda premium
zephiK said:
No. Did you really just say that after what we just said?
It's easy using a toolkit but also very easy to screw up your phone because people using it are clueless and flash whatever links making their phone into a non boot able state.
http://forum.xda-developers.com/showthread.php?t=1469909 is a great read on this topic.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
But the thing is people can choose whatever method they want to root their phone. Old way using adb or the new step by step on screen instruction toolkit. I choose toolkit to root my n4 just to try it out. I was just amaze how wug's toolkit was so easy as it had on screen instructions every click. I don't see how newbies could brick using wug's toolkit. I don't really care what method people use.
Sent from my Nexus 4 using Tapatalk 2
droidmeup said:
But the thing is people can choose whatever method they want to root their phone. Old way using adb or the new step by step on screen instruction toolkit. I choose toolkit to root my n4 just to try it out. I was just amaze how wug's toolkit was so easy as it had on screen instructions every click. I don't see how newbies could brick using wug's toolkit. I don't really care what method people use.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
It's not the OLD way whatsoever. It's not newbies bricking their phones using the toolkit. It's what they do AFTERWARDS, go read the Q&A forums. Many of the problems coming out of threads are from users doing things that they don't understand because they lack the basic knowledge of the Android system with ADB & Fastboot (they mention toolkit in OP post). Some people rooted using the toolkit and they don't even know how to flash a flashable zip or even restore their phone back to stock because they want to send it in for a RMA.
Like I said in many threads, two methods,
1) Learn how to get from Point A to Point B by using a map and planning it out
2) Using a toolkit and have it get you from Point A to Point B without knowing how you got there.
Let's see what happens.
1) Since you planned it out and have a map beforehand using a step-by-step guide (its not hard) you can remap yourself on how to get there. What if you went to back half way because you forgot to pick up something at the store? You know how to get there
2) Toolkit... oh im at point B, i want to go to the supermarket at Point A.5, how do I get there? exactly. You don't know, you then proceed to ask questions on how to get there (in this case it would be Q&A forum on how to fix their phone because its not booting up).
By spending 20-25 minutes, people are aware of how fastboot works and how to restore their phone when its in a nonbootable state and not mistakenly say that their phone is bricked. This is XDA developers not XDA shortcuts
No one asked for your opinion on what method people used so I don't care that you don't care either?
Next time you should read the thread I posted before commenting. It has nothing to do with 'old ways' vs 'new ways.' If toolkit is the new way then oh man... we are in deep trouble.
Just like my two cases, he couldn't say it any better.
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
I don't constantly post in threads about "OH DONT USE A TOOLKIT ITS TOO EASY. go old fashion with command prompt" for no reason. I do it with a good reason and no one should ever endorse toolkits for this very reason. Learn how to do it, it doesn't take a rocket scientist to know how to fastboot/adb when it's in a step-by-step tutorial. It's not hard to unlock a bootloader on a Nexus device. If it was a device with a difficult unlocking method through a exploit, then yes I would endorse a toolkit but for a Nexus its so easy to unlock.
1. set up ADB (do it once and you're SET for life on that computer.. dont have to do it again).
2. install ADB drivers http://forum.xda-developers.com/showthread.php?t=1514942
3. boot into bootloader using combo keys
4. command prompt into fastboot -> fastboot oem unlock
5. fastboot flash recovery <whateverthenametherecoveryis>.img
6. DONE.
@zephik
You've inspired me. I don't have my N4 yet but just got my 7 for Christmas. I'm going to pop it back to stock and redo the whole process manually.
I knew I was taking the lazy way out, you have guilted me into doing it properly as you said you learn nothing from a toolkit. Lol
Sent from my Nexus 7 using Tapatalk 2
ChrisHRocks said:
@zephik
You've inspired me. I don't have my N4 yet but just got my 7 for Christmas. I'm going to pop it back to stock and redo the whole process manually.
I knew I was taking the lazy way out, you have guilted me into doing it properly as you said you learn nothing from a toolkit. Lol
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Glad to know that I can do a kind of a change. If you need any further assistance or questions ahead of time, feel free to PM me.
Honestly, I'm not doing it to be a bad guy or to waste people's time. If it wasn't important, then I wouldn't stress how imperative ADB & Fastboot are to ANY device, but particularly towards Nexus devices. Fastboot isn't present in all devices, other devices such as Samsung Galaxy etc etc use Odin (Samsung's Firmware Flasher) which is the same thing but its more GUI friendly but it can still cause bricks and fastboot is easier in my opinion.
Just like what franco said,
Why would something happen? This kernel won't brick anything, a Nexus is pretty unbrickable unless someone is very dumb or simply a hardware bug ****s the device up. If anyone bricks this device or any Nexus I'll award him idiot of the year trophy.
Click to expand...
Click to collapse
It is REALLY REALLY difficult to brick a Nexus device, and I'm not surprised that it does happen to people because they use the toolkit and aren't aware of what they're doing. It's like solving a math problem, what's the point in getting spoon fed the answer? Just work it out. Except for Nexus devices, you don't even have to work it out!!! all you do is read a GUIDE that one person spent time on writing up. At least have the decency on reading it. You read it, and you do the step, then proceed until you're at the end. It's not difficult, and you get to know what you're doing it and why you are doing it.
People do things and their phone cant boot up but can access bootloader mode. They don't even know how to fastboot flash and then post a thread in Q&A forum saying their phone is bricked.
And you don't have to redo the 7 process lol. Manually unlocking bootloader is one thing and then knowing how to flash is the easy part.
Even the ghetto guide I posted a couple posts above works for any nexus device.
1. set up ADB environment (google sdk) basically get fastboot binary.. if you want ADB you'll need the adb.exe binary
2. install drivers http://forum.xda-developers.com/showthread.php?t=1514942
3. bootloader mode
4. fastboot oem unlock
5. unlock the phone on screen using vol keys
6. fastboot flash whatever.img [put in same folder as fastboot.exe]
7. done. you successfully flashed a 3rd-party recovery. now just put a zip file on the sdcard when android starts
8. receovery, wipe factory/dalvik/cache
9. flash rom,gapps(optional depending what rom), kernel (optional)
10. congrats you flashed a rom and kernel.
@zephiK. Thanks for the expert advice. I used Samsung S1 in the past and never used adb, was scared of it. I took your advice. Followed the guide and got rooted, the adb way. I have to admit. It was pretty satisfying to know what i was doing. Thanks again to everyone here.
thanks
zephiK said:
It's not the OLD way whatsoever. It's not newbies bricking their phones using the toolkit. It's what they do AFTERWARDS, go read the Q&A forums. Many of the problems coming out of threads are from users doing things that they don't understand because they lack the basic knowledge of the Android system with ADB & Fastboot (they mention toolkit in OP post). Some people rooted using the toolkit and they don't even know how to flash a flashable zip or even restore their phone back to stock because they want to send it in for a RMA.
Like I said in many threads, two methods,
1) Learn how to get from Point A to Point B by using a map and planning it out
2) Using a toolkit and have it get you from Point A to Point B without knowing how you got there.
Let's see what happens.
1) Since you planned it out and have a map beforehand using a step-by-step guide (its not hard) you can remap yourself on how to get there. What if you went to back half way because you forgot to pick up something at the store? You know how to get there
2) Toolkit... oh im at point B, i want to go to the supermarket at Point A.5, how do I get there? exactly. You don't know, you then proceed to ask questions on how to get there (in this case it would be Q&A forum on how to fix their phone because its not booting up).
By spending 20-25 minutes, people are aware of how fastboot works and how to restore their phone when its in a nonbootable state and not mistakenly say that their phone is bricked. This is XDA developers not XDA shortcuts
No one asked for your opinion on what method people used so I don't care that you don't care either?
Next time you should read the thread I posted before commenting. It has nothing to do with 'old ways' vs 'new ways.' If toolkit is the new way then oh man... we are in deep trouble.
Just like my two cases, he couldn't say it any better.
I don't constantly post in threads about "OH DONT USE A TOOLKIT ITS TOO EASY. go old fashion with command prompt" for no reason. I do it with a good reason and no one should ever endorse toolkits for this very reason. Learn how to do it, it doesn't take a rocket scientist to know how to fastboot/adb when it's in a step-by-step tutorial. It's not hard to unlock a bootloader on a Nexus device. If it was a device with a difficult unlocking method through a exploit, then yes I would endorse a toolkit but for a Nexus its so easy to unlock.
1. set up ADB (do it once and you're SET for life on that computer.. dont have to do it again).
2. install ADB drivers http://forum.xda-developers.com/showthread.php?t=1514942
3. boot into bootloader using combo keys
4. command prompt into fastboot -> fastboot oem unlock
5. fastboot flash recovery <whateverthenametherecoveryis>.img
6. DONE.
Click to expand...
Click to collapse
wow. good post. thanks a lot!
Is wallet working on all to Roms? Sorry to butt in this thread..
malikusmanrasheed said:
@zephiK. Thanks for the expert advice. I used Samsung S1 in the past and never used adb, was scared of it. I took your advice. Followed the guide and got rooted, the adb way. I have to admit. It was pretty satisfying to know what i was doing. Thanks again to everyone here.
Click to expand...
Click to collapse
Not a expert advice by any means. Just been around for a long time so I observe the commonalities between all users. I just really dislike it when people say or recommend things when really they don't know anything. Not saying I'm perfect by any means, but people need to stop being so cocky on the forums acting like they know everything. Instead of trying to defend themselves, ask questions on why I feel this way or whatever.
That's what forums are all about right? That's what XDA is all about. Spreading information. Not clicking a button that spoon feeds you something and you don't know how or why it's like that.
If someone gave you a car with one click (toolkit), what's the point in having a car if you can't drive it? (Toolkit) do you expect to click one button and the car drives you from home to where you need to be and back? What happens if it doesn't work? You ask questions on how to do this and th at.
You have to go through the procedure of learning how to use it. If you learn from the beginning (like I said, it's not hard, if it was then it's understandable about a toolkit) then it'll be a breeze. When I first got started, I was a lurker on XDA, I didn't post. All I did was read. I didn't have toolkits, I had to telnet my G1 to obtain root access through a exploit that took 40-55 minutes, one mess up and I would of bricked my phone and i had to do it with my hands, that's a scary thought knowing that you can't go back once you started. People nowadays should be grateful that unlocking bootloaders aren't as difficult anymore but yet people still feel the need to use a toolkit when it already is simple.
wow. good post. thanks a lot!
Click to expand...
Click to collapse
I didn't post it. That guy did. Definitely a great read and pretty much what I always believed in when I saw a toolkit. Should be banned from the forums but eh, who am I to call the shots
Is wallet working on all to Roms? Sorry to butt in this thread..
Click to expand...
Click to collapse
Yes Google Wallet works on any ROM as well as kernel. It says incompatible because you're rooted but it should work regardless of that text on the top of the app. Flash away!
Edit: May 5, 2009: http://androidandme.com/2009/05/beg...r-rooting-your-android-g1-to-install-cupcake/
August 17, 2009: http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
First guide one of the first rooting methods. August 17 is sort of one clickish but you still had to do a lot of things to get through it. So as you can see, it's not spoon fed to you, compare that to what you have to do now. Tell me that unlocking the Nexus bootloader is hard after reading all that ... it isn't.
@zephiK Can you link me to where it shows me how to root, and install CWM? Please
Sent from my Nexus 4 using xda premium
xxMAGICxx said:
@zephiK Can you link me to where it shows me how to root, and install CWM? Please
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2019273
I actually prefer TWRP over CWM. Your preference though.
Both can be found in Android Development Forum.