Database Develop

Rogers Dream vs. HTC Dream (normal?) + noob me.

Alright.
Seriously, whats the deal with the Rogers Dream and the normal Dream? I dont get the difference. Please explain some in detail.
The only thing I've been reading for a while is the DRE2100 or something compared to the normal thing.
seriously. What is rooting?
I have a Rogers Dream and I really want to know where to start playing around with it.
Its sad however that I have to look for threads with "Rogers" tagged on it.
previously, I had an HTC Kaiser, and I played around/flashed it a LOT. and I moved on to a Rogers Dream, I've had it for quite a while, just didn't know where to start.
Thanks

Theres a few minor differences between the 2. The main one is the frequency it runs on. But to get you started understanding everything this is what you need to look at.
http://forum.xda-developers.com/showthread.php?t=519523

Alright. I am so. tired of looking up stuff. I'm not going to do anything yet.
I barely get anything.
What is root for?
what is it used for?
I have used Ubuntu and Fedora a couple of times but, seriously, root was just a command really.
After I root. then what?
Also. I was wondering. can Rogers ever be converted into the DREAM100/DREAM110?. i dont know, just wondering. If that was possible, It would make things very simple for people like me.

I believe that dream100/110 are boards so they could never be converted.
Root is basicly in windows terms- the admin, getting root allows you su like the sudo command in linux. Having root allows you to flash custom roms, nandroid backup, themes, allow deeper hardware access, full privs to the kernel processes of the system, allowing apps to sd, allow you to wipe or activate gps from sms, dentonate nuclear warheads, so on and so on
Have I answer the ? Sufficently enough yet
Oh and root on linux is the same thing and not just a command

da pavinator said:
Alright. I am so. tired of looking up stuff. I'm not going to do anything yet.
I barely get anything.
What is root for?
what is it used for?
I have used Ubuntu and Fedora a couple of times but, seriously, root was just a command really.
After I root. then what?
Also. I was wondering. can Rogers ever be converted into the DREAM100/DREAM110?. i dont know, just wondering. If that was possible, It would make things very simple for people like me.
Click to expand...
Click to collapse
Since you're a lazy noob (at least to the G1), check the link in my sig that will answer most of your preliminary questions. Also look in the development forum's stickies, as there is A LOT of information for noobs about rooting (how to do it, and what it's good for, etc.) and flashing SPL, Recovery, and ROMs.

^That noob thread should be stickied. lol
So now, I am following instructions.
and I am a bit confused.
I am right now setting up my pc for rooting
http://developer.android.com/guide/developing/device.html
It says
Setting up a Device for Development said:
Step 1.) Declare your application as "debuggable" in your Android Manifest.
In Eclipse, you can do this from the Application tab when viewing the Manifest (on the right side, set Debuggable to true). Otherwise, in the AndroidManifest.xml file, add android:debuggable="true" to the <application> element.
Click to expand...
Click to collapse
What exactly does this mean?
Which application.
I have learned that AndroidManifest.xml is used for every application
I have the AndroidSDK on my computer, and I have also installed the usb driver
And when I searched in there, boy I got lots of results for "AndroidManifest.xml"
A little help?
Thanks a lot.
EDIT-
See, while here, I just had a simple question
http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
HyeProfile said:
Rooting the Rogers Dream
3.Install the proper drivers for your device, and make sure you can mount the microSD card and access it from your computer
Click to expand...
Click to collapse
Does this mean, being able to access the MicroSD card straight from you computer with an adapter/card reader? or though the phone?
I can access it from the phone btw

Follow the simple root link in my signature. Takes you to a thread specific to root on a Roger's dream along with a crowd of other canucks executing the same procedure.

A 1gig swap, way way overkill and completely useless to have anywhere near that much

LG Phoenix Boot Errors

Hey all, Let me start by apologizing for not posting this in the right place (More than likely). i didnt see any threads for LG p505 Phoenix.
On to buisness, i had an error booting into ClockWorkMod Recovery. My phone is booting incorrectly ever since. ive tried to take the battery out and replace it, but that didnt work. I tried to follow some repair work listed on the forums, but i need further assistance. ive gotten as far as the SDK dev package and attempting to restart the bootloader, but no luck. it keeps saying it cant detect the device. the computer recognizes it as ASUS Android Bootloader Interface. Any help?

Where did you learn how to put CWM on you phone? If it wasn't here, why not try those forums where you did?
Try this
http://forums.androidcentral.com/t-lg-phoenix-thrive/

Well, i got CWM on my phone via the Rom Manager App on the Market. but, after toying around with my phone trying to fix it, it appears that it is stuck on the bootloader, and not CWM. when it DOES "boot up", it only displays lines of code that varies when i plug it into a power source or my PC.

Are you rooted?

yeah i am. couldnt have gotten this far without that step.

FawkesPhone said:
yeah i am. couldnt have gotten this far without that step.
Click to expand...
Click to collapse
Just didn't want you thinking you could flash cwm by installing rom manager.
What exactly is going on. Give lots of details.
* iTouched Epic

Well, good for you. im such a rookie that would be entirely possible. lol. anywho, i asked for help on another forum, who a couple people on have some experience with programing and such, and i pretty much explained everything there is to explain there.
however, the website wont let me post a link to said post, so im going to try to copy/paste because i REALLY dont feel like typing all that out again if i dont have to.

Copy link and put (dot) as the dot .
* iTouched Epic

the story is, i tried to boot my phone (LG phoenix [p505], running CarloROM, standard Kernnel) into ClockWorkMod Recovery Mode, but upon booting up, teh device went to a black screen, save for a couple words, most partial. the readable text says "UDC_Start()". on pluging it into the PC, it displays the following text:
-- suspend --
-- reset --
EP1/out FAIL nfo=40 pg0=74000
-- portchange --
usb_read() transaction failed
-- reset --
-- portchange --
fastboot: oops !
fastboot: Processing commands
i am trying to utilize the only fix ive found, which is to reboot the bootloader via andriod developer debug window. i tell the command prompt to run the "adb reboot bootloader" function but it says it cant find the device.
it also appears on the PC as "ASUS android bootloader interface"
Click to expand...
Click to collapse
here's all the details ive got thus far

Try flashing stock recovery on it. Flash back to complete stock. Did you check to make sure cwm was compatible with your device?
Was the other forum not helpful to you?
* iTouched Epic

boborone said:
Try flashing stock recovery on it. Flash back to complete stock. Did you check to make sure cwm was compatible with your device?
Was the other forum not helpful to you?
* iTouched Epic
Click to expand...
Click to collapse
First, not the other forum isnt helping as it's a small user group and no one's responded yet. second, as previously stated, after posting this thread, ive determined that the phone did NOT boot to CWM. and second, yes, CWM is compatable and has worked in the past. i heard about it from someone that has used it on his p505 and it works perfectly.

There are a lot of devices that only run a modded version of cwm. I have a Samsung intercept that won't run with standard cwm.
* iTouched Epic

people on the android central forum you posted a link to say the phoenix runs just fine with standard CWM

Did you try flashing the touch version of cwm? My epic touch sgsll bricks with that?
* iTouched Epic

i rooted my phone, downloaded ROM Manager, gave it Super user permissions, and flashed Optimus One (Old BaseBand). exactly as instructed.

Where did you learn about doing this? You said you tried asking on another forum. What did they say? Did you try what they said? Have you tried what I said about going stock?
* iTouched Epic

i learned all this from here: http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm.html
no one has responded on the other forum as previously stated
i have learned that my device is booting to the bootloader, not CWM, also as previously stated.
thus, flashing a new ROM of any sort is impossible.

FawkesPhone said:
i learned all this from here: http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm.html
no one has responded on the other forum as previously stated
i have learned that my device is booting to the bootloader, not CWM, also as previously stated.
thus, flashing a new ROM of any sort is impossible.
Click to expand...
Click to collapse
You never said you didn't get any responses from the other forum. If you posted the question yesterday and gave it a couple hours, no responses, then started flipping out cause your is phone is messed up and so you decided to join for the soul reason of using it as a technical support and post in off topic cause this site doesn't even develop (notice I didn't say support) your phone, I say you need to chill out and go back to other site and get a lil bit more in depth with your question. Cause honestly I would have overlooked your question with how it was written and the little information given. Those guys know about your bootloader. I don't. Not many here do. LG doesn't make flagship devices, hence why they're not here.
I can tell you that if nobody does help you, you need to read up on how to shell into the phone and flash something else like that.
* iTouched Epic

FawkesPhone said:
First, no, the other forum isnt helping as it's a small user group and no one's responded yet.
Click to expand...
Click to collapse
Also, why waste an hour of my time? If you're gonna tell me to eff off, why not do it at the beginning?

FawkesPhone said:
Also, why waste an hour of my time? If you're gonna tell me to eff off, why not do it at the beginning?
Click to expand...
Click to collapse
I didn't tell you to f off, but, in all seriousness, I don't like it when people join this site just to ask a question.
Then you post in the wrong forum about a phone that isn't even developed on here.
Sub-Forums : General discussion
Forum
Last PostStats
About xda-developers.com
Anything to do more with the site than with the phones. Feature requests, announcements, praise, moaning, etc.
General
Anything that involves all of the phones and doesn't fit in any of the other fora.
Paid Software Announcement and Discussion
Are you a developer wanting to promote for-pay software? Feel free to post announcements about your apps here and have the community discuss them.
Questions and Answers
This forum is for all questions, big or small, you might have. Please read the rules in this forum before asking.
Hardware Hacking
For discussion of development boards, hardware interfaces, datasheets, circuit modification and related tools
NFC Hacking
For discussion of Near Field Communication (NFC) hacking and development
Upgrading, Modifying and Unlocking
Some of the more advanced issues, involving multiple phones.
Accessories
For accessories that involves multiple phone-types. Car-kits, headphones, cables, chargers, extra batteries, replacement screens, sources for connectors, etc.
Networking
GPRS or WAP-settings, WiFi, ... This forum is for anything to do with getting your device talking to the rest of the world.
XDA TV
Here's your chance to communicate directly with the stars of XDA TV!
Off-topic
Anything not related to the phones.
^ Just wanted to point that out. ^
And I did try to help you. I don't know LG bootloaders. But I went through seeing if you made some noob mistake that I could help with. Then when that was sorted out, I told you how to help yourself. If you're are going to take someone telling you how to help yourself as telling you to f off, not sure you are going to make it here on XDA. Good luck with that attitude.
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
Did you try to search here on this site?
Searched here on XDA and found this:
http://forum.xda-developers.com/showthread.php?t=1289265&page=3
You see, we don't mind helping people at all, it's the people that won't help themselves that get on people's nerves. Look man, I will help you as much as I can. But you have to be willing to help yourself, too. Finding threads like the one I posted above is what I mean by searching and reading on how to shell into the phone, using adb to fix your problems. You have a jacked up phone, don't get frustrated and mad at the world, calm down, chill out. You can fix it.

cannot mount read write

hi i have been trying to mount the phone to read/write in order to access the /system folder for copying files
however, i am unable to do this
i have tried the mount r/w applications online but not working as well
i have tried all the commends on adb as well, what i get is "remount fail: read-only file system
i have used the abd to run super user, but it shows im already a super user
i have tried to set adb to set as root and it also shows already running as root.
any ideas guys??
i have tried reflashing several kernels and also roms, same thing.

oh additional note, i have tried adb in recovery mode and also in normal mode, doesnt work.
and my usb debugging is already checked

Very interesting development. Download Link please... :silly:
Despite that this surely the wrong thread you could tell us whether you have this problem on a toaster or a tumble dryer...
And what are you trying?
adb push iOS5.apk /system/s**t or what?

hi there, thank you for the really useless reply there. unfortunately you are right, i had put this in the wrong place. anyway, thanks to the admin for helping me move it to the right place.
in case you have been in a cave or dont have google, many people have issues trying to mount read/write capabilities in their /system folders be it to be able to move some things in there or to push applications.
as most people who ask questions here dont get much answers because of people like you, i had to do my own searching and try everything on the web and sadly it didnt work.
so, for people who have come to this thread looking for answers, please try the following (only if you have tried everything)
SOLUTION
it would seem that after flashing many roms, the /system folder has issues.
please go to recovery (CWM) > mounts and storage> format /system
once you have done this, please reinstall your rom. this will fix your issues.
as for trahzef*ck: i'll give u a thanks since you being a d*ck helped me figure out my solution and you look like you need a hand in being nice

vyraz said:
hi there, thank you for the really useless reply there. unfortunately you are right, i had put this in the wrong place. anyway, thanks to the admin for helping me move it to the right place.
in case you have been in a cave or dont have google, many people have issues trying to mount read/write capabilities in their /system folders be it to be able to move some things in there or to push applications.
as most people who ask questions here dont get much answers because of people like you, i had to do my own searching and try everything on the web and sadly it didnt work.
so, for people who have come to this thread looking for answers, please try the following (only if you have tried everything)
SOLUTION
it would seem that after flashing many roms, the /system folder has issues.
please go to recovery (CWM) > mounts and storage> format /system
once you have done this, please reinstall your rom. this will fix your issues.
as for trahzef*ck: i'll give u a thanks since you being a d*ck helped me figure out my solution and you look like you need a hand in being nice
Click to expand...
Click to collapse
Congrats! Obviously you have learned something. Learning by own research will help more than to be spooned.
To be honest: Maybe my answer was harsh. But be aware for the following:
- Post in the right section
- Give people, who want to help the needed information. Rom, Version, Kernel etc. So that they can help.
- and don't try to be so smart ass cause you found a format command. There are already enough on XDA.
As your thank meter is Zero I give u one back. for your most intelligent word/spelling creations. It's your first one. maybe the last.
Halleluja! An new &%/()&%%$ on XDA. Thank god.

Maybe you have partial root. Try Busybox from playstore and update the binaries.

trahzebuck said:
Congrats! Obviously you have learned something. Learning by own research will help more than to be spooned.
To be honest: Maybe my answer was harsh. But be aware for the following:
- Post in the right section
- Give people, who want to help the needed information. Rom, Version, Kernel etc. So that they can help.
- and don't try to be so smart ass cause you found a format command. There are already enough on XDA.
As your thank meter is Zero I give u one back. for your most intelligent word/spelling creations. It's your first one. maybe the last.
Halleluja! An new &%/()&%%$ on XDA. Thank god.
Click to expand...
Click to collapse
haha well i dont care about hard answers, just answers, you on the other hand gave nothing. no wonder although your status shows "senior member" all you have is a measly 200 odd thanks. half of them must have been like mine, pity thanks for nothing.
i will however take your advice on the first two, but i dont have to be one because you apparently are one big enough to cover most of the members here.
thanks for the thanks but i think you may need one more then me.
and last but not least, yes i can spell, and its quite obvious much better then you can and if i am another *ssh0le on the forum, i must have learnt from the best, thanks a mil trasherf*ck! you're my hero
sahilarora2003 said:
Maybe you have partial root. Try Busybox from playstore and update the binaries.
Click to expand...
Click to collapse
erm nope, i checked with afew other guys, who root alot as well, apparently sometimes the /system file will get mucked up like that once in awhile. so this doesnt really apply to specific phones or tabs but to all who may have this issue.
but the issue has been resolved. thanks for the suggestion tho...

Thread closed
sahilarora2003 said:
Maybe you have partial root. Try Busybox from playstore and update the binaries.
Click to expand...
Click to collapse
Thank you, sahilarora2003, you are the only responsible poster in this thread.
If a post is placed in the wrong subforum, simply hit the report button and we'll move it. There is no need for the drippingly sarcastic responses I see here, provoked or not.
The rest of you need to smarten up.

Phone was locked by an idiot, usb debugging off

I dont know much about this kind of stuff. I spent all day researching but all I understand is that I need usb debugging on in order to use ADB. is there a way to get this usb thing enabled with my phone locked? I cant factory restore this thing it has way to many important things on it and frankly I will end up doing something immensely stupid to the person that cost me that... I really need help or im screwed.

ChristianMonty said:
I dont know much about this kind of stuff. I spent all day researching but all I understand is that I need usb debugging on in order to use ADB. is there a way to get this usb thing enabled with my phone locked? I cant factory restore this thing it has way to many important things on it and frankly I will end up doing something immensely stupid to the person that cost me that... I really need help or im screwed.
Click to expand...
Click to collapse
you can try logging in with your google account linked with that phone..

n205des said:
you can try logging in with your google account linked with that phone..
Click to expand...
Click to collapse
oh wow totally didnt think of that /sarcasm its been like 3 years since I got the phone, hell if I remember.

ChristianMonty said:
oh wow totally didnt think of that /sarcasm its been like 3 years since I got the phone, hell if I remember.
Click to expand...
Click to collapse
Calm down and think of alternative points of entry. That was a valid and helpful suggestion above as it is easy if you only had a few accounts.
Have you flashed a custom recovery to the phone in the past? If not, research getting into the bootloader to flash a custom recovery first.
Then back up the system in recovery and copy files to PC before trying alterations to bypass system security.
First thought is to edit the build.prop file of the system from recovery, to turn on USB debugging. Then proceed with whatever other info you found before this thread.
Could also try to alter the system partition via recovery zip. There may be a mod out there for this: http://en.miui.com/thread-5684-1-1.html but do have to be wary of compatibility with your ROM. Best to check it out and ask first before flashing.

Flash a custom recovery, make a NANDroid, backup the SD card. Copy whatever you need from the NANDroid, factory reset, copy it back. Done

ChristianMonty said:
oh wow totally didnt think of that /sarcasm its been like 3 years since I got the phone, hell if I remember.
Click to expand...
Click to collapse
OP, folks are trying to help, and I am watching this thread too, I suggest if you have a legitimate issue, you contact your carrier as well.
I hope you get your problem resolved, but being disrespectful in your plight is not proper, for you or any user.

[Q] Nexus 6 Rooting Help

I just received my Nexus 6 that I bought from Best Buy yesterday and have got it activated today.
I really want to root and try flashing my first rom. I have been reading thread after thread trying to learn and understand what it takes to root a Nexus 6, flash a rom, and what the proper way to do it is. Spent at least 5 hours reading threads and I have been so confused as to what to do.
First, I have read that you should do the ADB way to unlock, root, flash etc. (Nexus 6 all in one Beginners Guide) because using a toolkit will make flashing roms more trouble than its worth.
Next, I have read repeatedly that the method used when the Nexus 6 first came out is still a valid and perfectly fine way to unlock, root, flash, etc , but then I have found in another thread that in order to root it you will need to flash a custom kernal of some sort so i'm unsure what I need to do.
The Nexus 6 All-in-One Beginners Guide seems pretty straightforward and easy, however this is my first time flashing anything and rooting a Nexus device so i'm unsure what I should trust.
Thanks in advance for anyone willing to help give this newbie some advice.
Any help is appreciated, I am just frustrated with trying to find a current method of unlocking, rooting, flashing, etc because nearly every thread I have read is dated back to when the device first came out and I usually am able to learn visually very easily but many videos for the N6 on youtube are from when the N6 came out, dating back 6-9 months ago.
So again, any help would be greatly appreciated because I am getting a bit frustrated with sorting out all the information and learning what I can trust so I don't damage my phone beyond repair.
Thank you again for reading and giving advice if you choose to and I apologize if this sounded like a rant. I just really need some help understanding what to do. Thank you.
If anyone is able to clear up my confusion on the issues I brought up, thank you.

1. Use Wugs to unlock and root
(Sure knowing how to adb is important, but just do that)
2. Wugs will install a custom recovery - you flash roms in said recovery.
3. Apps I recommend you get after obtaining root:
(Some paid, some free)
SuperSU Pro (paid)
Buaybox Pro (paid)
Root Explorer (paid)
Titanium Backup (paid/free)
Then you'll have a pretty good start at supporting the devs, while having a good file/folder control app, and a way to protect yourself against data loss - with a simple way of reverting back to a previous build should you dislike a rom.
Keep reading. You're off to a gold start but I learn more and more every day. Never underestimate the value of reading everything prior to flashing/modifying it just might save you a headache when your phone inevitably bootloops for a silly reason.

iRub1Out said:
1. Use Wugs to unlock and root
(Sure knowing how to adb is important, but just do that)
2. Wugs will install a custom recovery - you flash roms in said recovery.
3. Apps I recommend you get after obtaining root:
(Some paid, some free)
SuperSU Pro (paid)
Buaybox Pro (paid)
Root Explorer (paid)
Titanium Backup (paid/free)
Then you'll have a pretty good start at supporting the devs, while having a good file/folder control app, and a way to protect yourself against data loss - with a simple way of reverting back to a previous build should you dislike a rom.
Keep reading. You're off to a gold start but I learn more and more every day. Never underestimate the value of reading everything prior to flashing/modifying it just might save you a headache when your phone inevitably bootloops for a silly reason.
Click to expand...
Click to collapse
Thank you for your advice. May I ask the difference of doing it with a Toolkit rather than the ADB way ? It just seems that one is easier than the other.
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?

Iandrew124 said:
Thank you for your advice. May I ask the difference of doing it with a Toolkit rather than the ADB way ? It just seems that one is easier than the other.
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Click to expand...
Click to collapse
The adb way teaches you how to do it at the base level - this method would allow you to pull files/folders without the phone booting, or flash individual partitions without having to flash a whole image - there's a LOT of reasons to know and understand adb, and you eventually should, as it could save your phone when all else fails.... It has its benefits, but for simplicity's sake - for now - just use Wugs.
Using toolkits in effect gives you a crutch. With this crutch you then are forced to depend on this crutch for future needs. What happens when you get a update or different phone that Wugs doesn't work with or do what you need to do? THATS where adb understanding would come in handy.
I NEVER recommend people use toolkits exclusively as this can and WILL eventually lead to major issues that the user is now at step 1 of the learning process all over again - or - are forced to wait for toolkits to be made to do something as simple as obtain root. That's annoying.
In this case, I hope you will make yourself more familiar with adb when you can, use it, try it out, understand what it does and what it's for - but just to get you up and running you can use the kit, just don't expect it to be that easy every time because, I promise you, it won't be and at some point adb will be the only option you have. You don't want to have to be in a panic situation when that knowledge could have saved you.
That's just how I like to help people learn this stuff. Start off slow just so they can do what they want to do - but heavily stress the importance of HOW that toolkit works - because its doing what you need to learn how to do - it just does it all for you.
Don't rely on that crutch - it won't always be there.

Iandrew124 said:
. . .
May I ask the pros and cons of doing it the Toolkit way and the ADB way ?
Click to expand...
Click to collapse
Manual flashing has the advantage that you controls the 'speed of the process. Because you have to enter commands one by one.
Toolkits use scripts instead of commands. And you have a choice from many options.
You won't be fast enough to stop when using a wrong option/script.
The post of irub1out is a good method.
After point 1. wait a day and go on with reading and posting.

adb is not used in the rooting process. fastboot is used to unlock the bootloader and then flash a custom recovery.
It's a really simple process after installing fastboot.
1. fastboot oem unlock
2. fastboot flash recovery recovery.img
3. Put SuperSU flashable zip on sdcard
4. Boot into recovery and flash that zip
There really shouldn't be any need to use a toolkit and if you do it manually, you KNOW your computer is configured properly so if you need it for recovery purposes later and something is not working, you know it's not the computer that is the issue.
Use the toolkit for other things once you've done the unlock and flash manually by all means. But NEVER use the toolkit first. This is a recipe for disaster.
Although the previous posts stress the importance of learning manually, they kind of miss part of the point as to why and I bet 90% of our experienced users here will agree with me...NO SHORTCUTS FIRST TIME.
If you need more info on fastboot, there's an adb and fastboot thread in general > sticky roll-up thread.

I concur with @danarama. We spend half our time in this forum trying to fix mistakes made with toolkit.

really, if the user doesnt have the proper knowledge to make the simple choices given in the toolkit, they are not going to choose the right files to do it manually.
so it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
but regardless of what any user might claim, the toolkit doesnt make mistakes. it executes the same commands you would use manually via a script based on your choices.
there is no margin of error other than the users input.

j
bweN diorD said:
really, if the user doesnt have the proper knowledge to make the simple choices given in the toolkit, they are not going to choose the right files to do it manually.
so it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
but regardless of what any user might claim, the toolkit doesnt make mistakes. it executes the same commands you would use manually via a script based on your choices.
there is no margin of error other than the users input.
Click to expand...
Click to collapse
first off, toolkits DO occasionally make mistakes, it has been proven, so dont argue with that. sure, its not always, but it happens. secondly, the user choosing files.. ok, if you do it the right way, there are only two files you need. and the user doesnt have a choice to pick them. they are the twrp recovery, and supersu. the user has to go find them, not pick out of a list. and witj my time on the n6 since last November, not one person picked the wrong files to root their phones. again, its because they arent given a choice.

bweN diorD said:
it makes no difference really, other than the person gaining the knowledge to understand exactly what they are doing
Click to expand...
Click to collapse
...and to ensure fastboot is Working, as I mentioned in my post. So it does make a difference.

a person gaining knowledge to understand what they are doing is by far the most important thing that can happen. thats something thatll never happen with a root toolkit.

Iv'e had several good flashes and some bad using the exact same files and same options during testing and playing. Worst button/option to even be available to noobs is the lock after flash or even a relock button at all. Remove that option and you are pretty much safe from hard brick. Then only have to come back and ask us to walk through fastboot when the flash goes belly up. Need an audit on how many times we have seen this exact scenario.

prdog1 said:
Iv'e had several good flashes and some bad using the exact same files and same options during testing and playing. Worst button/option to even be available to noobs is the lock after flash or even a relock button at all. Remove that option and you are pretty much safe from hard brick. Then only have to come back and ask us to walk through fastboot when the flash goes belly up. Need an audit on how many times we have seen this exact scenario.
Click to expand...
Click to collapse
That's another good point.. When 5.1 came out and locking the bootloader after flash, if it didn't boot, it would be a brick.. Toolkits would do this after a flash and brick phones.. You have to wait until the toolkit is updated before using it safely.

simms22 said:
j
first off, toolkits DO occasionally make mistakes, it has been proven, so dont argue with that. sure, its not always, but it happens. secondly, the user choosing files.. ok, if you do it the right way, there are only two files you need. and the user doesnt have a choice to pick them. they are the twrp recovery, and supersu. the user has to go find them, not pick out of a list. and witj my time on the n6 since last November, not one person picked the wrong files to root their phones. again, its because they arent given a choice.
Click to expand...
Click to collapse
i sir, will argue with whatever i wish.
in the year i maintained a toolkit for the last moto i had, 20k+ downloads, not one user accused the toolkit of flashing something it wasnt supposed to. the code is fairly simple, one option points to a command and file (simply put), etc. etc.
is it possible some one in a million error happened, doubtful but ok.
my comment was more directed at the previous poster who said something about spending 1/2 his time helping users with toolkit problems.
thats very unlikely, unless the toolkit coding is done very poorly.
---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------
danarama said:
...and to ensure fastboot is Working, as I mentioned in my post. So it does make a difference.
Click to expand...
Click to collapse
how about you quote the rest of my sentence next time, where i agreed with your logic on that.
unless your intentionally trying to start an argument? cause thats what it looks like.

bweN diorD said:
how about you quote the rest of my sentence next time, where i agreed with your logic on that.
Click to expand...
Click to collapse
Because the rest of your sentence was nothing to do with what I wanted to say and you didn't agree with my logic at all. In fact your sentence (even complete) suggests that what I had said wouldn't even factor in to anything.
bweN diorD said:
unless your intentionally trying to start an argument? cause thats what it looks like.
Click to expand...
Click to collapse
I'm 35 years old. I've got better things to do than try to create arguments in Internet forums. I was expanding on your sentence on something you missed. Kick yourself for the omission, not me for pointing it out.
Don't be so bloody confrontational. You're coming off as a petulant child, as does everyone who starts a sentence "how about" without trying to understand what they're talking about first.

bweN diorD said:
i sir, will argue with whatever i wish.
in the year i maintained a toolkit for the last moto i had, 20k+ downloads, not one user accused the toolkit of flashing something it wasnt supposed to. the code is fairly simple, one option points to a command and file (simply put), etc. etc.
is it possible some one in a million error happened, doubtful but ok.
my comment was more directed at the previous poster who said something about spending 1/2 his time helping users with toolkit problems.
thats very unlikely, unless the toolkit coding is done very poorly.
Click to expand...
Click to collapse
if i can get someone that will make a toolkit that does what it does, and goes through every step explaining the process of what its doing and how to do it manually, id be a happy man. seriously.

danarama said:
Because the rest of your sentence was nothing to do with what I wanted to say and you didn't agree with my logic at all. In fact your sentence (even complete) suggests that what I had said wouldn't even factor in to anything.
I'm 35 years old. I've got better things to do than try to create arguments in Internet forums. I was expanding on your sentence on something you missed. Kick yourself for the omission, not me for pointing it out.
Don't be so bloody confrontational. You're coming off as a petulant child, as does everyone who starts a sentence "how about" without trying to understand what they're talking about first.
Click to expand...
Click to collapse
funny, it looks like i am agreeing with the manual logic...
other than the person gaining the knowledge to understand exactly what they are doing, which i agree with,
Click to expand...
Click to collapse

simms22 said:
if i can get someone that will make a toolkit that does what it does, and goes through every step explaining the process of what its doing and how to do it manually, id be a happy man. seriously.
Click to expand...
Click to collapse
I honestly considered making that in the past.
---------- Post added at 05:44 PM ---------- Previous post was at 05:37 PM ----------
bweN diorD said:
funny, it looks like i am agreeing with the manual logic...
Click to expand...
Click to collapse
That's not what we're talking about. I never said you didn't agree with the "manual logic"
Please re-read my post. I think you've misunderstood what I said. Let me know if you'd like me to explain what were talking about afterwards if you still dont understand

Tbh, not using toolkits comes down to this:
Its the easiest ****ing thing ever to do with out one. If you need one, you have a major gap in your understanding... And you need to fix that first. Well you don't "need" to unfortunately, but acquiring root access is taking over being the admin for your device. If you are choosing to do that, you should probably understand the basic tools.

I am in approximately the same position as the OP with a brand new Nexus 6 and I have a question. Should I take any OTA updates that are available before starting the unlock bootloader and rooting process?