Database Users

[Q] So Much Information!!! Brains exploding! Assist!

When I found out that 2.2 wasnt coming out from this phone I decided that I would root the phone and load a 2.2 ROM, etc. etc. So I started researching all of these about 2 days ago... and for the past 2 days I have read so much information on this that I am now currently so mixed up and lost. There are soooo many different ROMs, different ways to do this, that, etc. I see some people do one thing that it works great, another person do the exact same thing and they havent the same luck.
Even when getting ready to just root the phone, I found an awesome post that had great information... but, then when I looked at it the post was from 7 months ago and in the N1 forums. So, I started to 2nd guess.
I suppose basically what Im in need of is possibly a normal/basic recommendation to get moving on this... Would a possible recommendation be to root the phone with the 1 click root being run through a file manager, then create a nandroid backup, then go with something popular like Cyanogen6 RC1? Its just that mod -seems- to be what a good bit of people have, and problems seem limited on it. But then again, ive read about 10 other ROMs that appear to be just as good, and people like just as well... so agian, this choice leaves me frozen as well.
Im just so overwhelmed with information ive just about frozen up... I think it need to bring it back to a basic simple plan to get moving on this. Everything I read in these forums sounds so awesome and just plain ole fun.... but like I said im currently frozen/lost. Please help if my request isnt too much...
Thanks! Any help with this will definitely melt this horrid ice!!!

Use this to root: http://forum.xda-developers.com/showthread.php?t=753910
Just do as it says and follow directions. I rooted both of my brother's phones this way. It works.
Then do as you were thinking: nandroid then install CM6 RC1. It will probably be your best bet for a solid 2.2 experience.

here's what I posted on my carriers facebook page. I kept things simple and to the point, and the point was to install 2.2 on a hero.
1. go to settings, applications and check allow installation from unknown sources.
2. install bar code scanner from the market if you don't have it.
3. scan the qr code from here: http://bit.ly/d1f0RN
4. download and install the app
5. open universal androot and click root
6. go to the market and download rom manager
7. open rom manager and click flash clockwork mod recovery
8. click backup current rom (you can always restore your backup later to go back to exactly how your phone was)
to load the rom after rooting:
1. download both the rom and google apps from http://forum.xda-developers.com/showthread.php?t=755795
2. copy the zip files to your sd card
3. open rom manager and click install rom from sd card
4. choose the rom file you copied to the sd card and click add zip, then choose the google apps file you downloaded earlier. Click ok and choose backup current rom and wipe data.
5. Enjoy android 2.2 on your Hero!!
(be careful restoring stuff using mybackup, open source roms and htc roms don't store data the same way. applications are safe to restore but system settings can potentially break things requiring you to wipe and reload again)

Not because it is my root method, but I would actually recommend using my root method and following all of the steps. It has you flash a custom recovery and patched boot.img so you keep full root via adb.
http://forum.xda-developers.com/showthread.php?t=694572

CM6 is the ONLY 2.2 ROM for the Hero at this point. But know that it doesn't have much of the Sprint/CDMA or HTC SenseUI functionality and stuff that you're used to from your current phone....like updating Profile and PRL; Sprint Navigation/Football/Nascar/etc.; your Contacts, Dialer, Messaging, and some other menus will be a little different....that's just a few things off the top of my head.
So if you kinda LIKE the way your phone is now (except maybe for some lag/slowness), CM6 won't be a very similar ROM. But you won't know unless you try it out Just offering some helpful info. Good luck -- we're here to help.

I have not found a 2.2 FroYo that I like for the Hero, it's rooted and running Fresh 2.3.3
http://geekfor.me/new-release/fresh-hero-233/

Awesome... the community here is absolutely incredible. Although I am literally tryin my best to read the ****in manual, I continue to fear that im reading something too old or outdated, or that there is something newer (easier) that I should be doing instead. I did the rooting with the 1click which was so simple... I cant believe I even spent that much time on it.
Thinking next the nandroid/recovery image thing would be a breeze, but it appears to almost be the hardest step. I see on most posts that they always tend to mention Nandroid for backups - is there a particular reason that I should use that one? Some other ones appear to be easier, but not as interesting or fun. However, im fearfully coming across a lack of exact guides that explain the process.
I truly think that once I can get the recovery image done, and I can start trying out other ROMs and such... this will become too much fun. But again, im getting so mixed up by should i do this, that, or maybe this... or wait, is that too old of information?
Regardless, thanks for all the help!

Download ROM Manager from the Market. From ROM Manager you can flash ClockworkMod recovery or Flash Alternate Recovery (I prefer this option RA Recovery) there is a newer relase but this works fine.
You can then reboot and go into recovery, back up your system as it is right now, that way you can always go back to the basic root version that you have right now. That my friend is a Nandriod back up. now you can install a ROM of your choice, once it is installed and functioning the way you like make a Nandriod back up of it, that way you always have a good platform to start from if anything isn't playing nice.

saltyclams said:
When I found out that 2.2 wasnt coming out from this phone I decided that I would root the phone and load a 2.2 ROM, etc. etc. So I started researching all of these about 2 days ago... and for the past 2 days I have read so much information on this that I am now currently so mixed up and lost. There are soooo many different ROMs, different ways to do this, that, etc. I see some people do one thing that it works great, another person do the exact same thing and they havent the same luck.
Even when getting ready to just root the phone, I found an awesome post that had great information... but, then when I looked at it the post was from 7 months ago and in the N1 forums. So, I started to 2nd guess.
I suppose basically what Im in need of is possibly a normal/basic recommendation to get moving on this... Would a possible recommendation be to root the phone with the 1 click root being run through a file manager, then create a nandroid backup, then go with something popular like Cyanogen6 RC1? Its just that mod -seems- to be what a good bit of people have, and problems seem limited on it. But then again, ive read about 10 other ROMs that appear to be just as good, and people like just as well... so agian, this choice leaves me frozen as well.
Im just so overwhelmed with information ive just about frozen up... I think it need to bring it back to a basic simple plan to get moving on this. Everything I read in these forums sounds so awesome and just plain ole fun.... but like I said im currently frozen/lost. Please help if my request isnt too much...
Thanks! Any help with this will definitely melt this horrid ice!!!
Click to expand...
Click to collapse
I know exactly what you mean. I've rooted my Hero the day the universal 1 click came out,but as yet have been reading everything I can on which new Rom to install first.
I went out and bought a new 16 gig sd card for more storage as well. I've been trying to read up on how and what is the best way to do all of the various partitions on it cause some say to just have a ext 2 partition,and others say have a ext3/4 partitions on it.Unfortunately I haven't found a easy way to make this happen except by using the FroydVillain 1.4.3 rom and I don't know if it will work with a cdma Sprint Hero or not yet.
I love the phone,and want to upgrade it to the best stable over clocked rom that will allow me to use it for everyday usage,but it doesn't look like it is going to easy as rooting the damn thing was. Seems to me that you need to be a programmer in Linux to make it work the best
I hate posting a bunch of neewb questions about it but I guess I will
Mac

Awesome! Okay perfect... it worked perfect! I know have CyanogenMod running - yeah, it def different. Seems like it will take some time to get used too. Esp since its so far from SenseUI off the bat... err well, just the way that it handles things and such.
I will definitely give it a fair shot before I even try out some other ones... but I def want to try to use one of those Fresh Roms as well.
Thanks a ton for all the help! Most appreciated!

[Q] Take 7.014.1 update before rooting ?

I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.

Zoandroid said:
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Click to expand...
Click to collapse
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean

timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
My concern, being still in the middle of researching just how to root the A500, was whether the update would have a similar effect as, for example, the more major update from 3.0 to 3.2, which, as I understand it totally changes the procedure used to achieve root. But if it won't matter one way or the other, I might as well take the update in the interim. I keep hoping to see a more simple 'one-click' style of root made available before I tackle this task. So far I've found something like 3 different ways to root the tablet between this forum and another. But each is a rather involved process.
Thanks!

timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
I downgraded, rooted, and then flashed the stock ROM without wiping. If going to any other rom, you might need to wipe.

There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢

timmyDean said:
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
Click to expand...
Click to collapse
Hi, and thank you VERY much for posting such a nice explanation, especially in addition to all the work you have done posting your thread rooting 3.2. I understand, and completely agree with your explanation, as well as your position on taking control of what we bought and paid for. I take even stronger offense with this tablet's bootloader being locked than I do on my phones. This is not a discounted phone with a service plan tied to a cell provider. It has WiFi, but " I " am the only one providing its data (it never leaves my home). There is no justification here that I am 'leasing' a provider's technology . It was a gift, so I can't speak to choosing the vendor. But I like your wheel lug analogy.
I've been reading the threads on rooting, and both my Android phones are rooted and ROMed, so I've been around the block a couple times from the rooting aspect. But thus far I have been rather confused as to which route to take with the tablet. I don't want to be limited to using terminal for su access, so I want to 'fully root' the tablet. My goal is to allow apps like Titanium Backup, Root Explorer, and others I use on the phones, as well as having Clockworkmod Recovery, or similar recovery capable of working with nandroid backups. But for now I don't have plans to use a custom ROM. So having rooted stock 3.2 would suffice.
Although I do fully understand the need to research these kinds of things before jumping in, I also know that often times information evolves, and lengthy threads which were once considered current info end up not getting updated during that evolution. This can lead to wasted time reading information which can no longer actually be used . So in the spirit of pursuing the most current info, could you recommend which thread I can use to get the best results while rooting this 3.2.1 OS Tablet with the above goals in mind?

Used Timmydean's method, it is pretty easy as long as you follow his instructions with in the zip file he has made with all the tools you need inside of hat zip file. You root, install super user and busybox then download Acer recover installer and that will install cwm...
http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
Good luck and thanks again timmydean for this method.
Sent from my A500 using xda premium

Thanks, that sounds like the way to go. I'll head over to the link you provided.

I've got a couple of questions about the zip file at that post. I want to download that to my PC, and will be using ADB from there, right? I have the choice of doing so from either Windows XP SP3, or Windows 7 Home Premium. I read in older threads that many of the problems people had were only when they used XP, but were avoided by using Windows 7 (which was exactly opposite of what people experienced rooting the LG Ally), so it seems that in this case it is desirable to use Win7?
I presume I'll need to install a driver so the PC can 'see' the tablet. Is one provided in the tools, or do I need to download that somewhere?

I used windows 7. Yes the driver is in the zip file. I unzipped the file to a folder on my desktop and went from there.
In the zip there is a folder called usbpcdriver. Run the set up from within the fooder to get your driver... please read the instructions that say read me..
Sent from my A500 using xda premium

Thanks. I intend to read everything I can get my hands on before I actually start this. I definitely don't want any trouble or, heaven forbid, to brick the tablet.

pretty easy i think... good luck and let us know when you get rooted

I'm not finding any actual instructions on the steps to take for this procedure. The readme file in version 3 zip file only talks about "changes" from whatever the original procedure was.
Where can I get the actual instructions for the entire procedure?
Edit: I just downloaded version 2 of the zip file. In that one there is an additional PDF called "Steps". It is a little more detailed, and says at step 20 that "you should now have 3.2 with a SU shell installed". Does the DotNetDetector step actually ROOT the device? That seems simple enough, but it still has no mention of things like installing ADB and the PC driver. I located the actual thread from which the single post was derived (the target of the URL above, where it is suggested I use TimmyDean's procedure). I am now looking through that entire thread to try to sort out where the instructions are.
AHA! Post 119 of that main thread says "Also the instructions and everything you need are in earlier posts.".
It appears this procedure needs an instruction manual written to consolidate all the gathered information. Having a link to only the download zip files isn't telling me the whole picture. I'll try gleaning the thread and see if I can put together all the steps needed from start to finish to make this work. Looks like ROOT ain't happening tonight.

http://www.multiupload.com/SLR6XSV841
---------- Post added at 05:14 AM ---------- Previous post was at 05:11 AM ----------
thats the link to read me file.. I about to jail break an Iphone 4... Wish me luck

I edited the above post while you were replying. I'll check out that link, thanks.
Good luck on jailbreaking the DemonSpawn 4.

http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken

OK, so it looks like the file you just sent me a link to is the same one as the "Steps.PDF" file that was released in Version 2. It appears to me that what I need to do is blend the changes (detailed in version 3's readme file) into that original Steps file, to make a single contiguous set of instructions, and then start at the top. I notice it does mention installing the PC driver and ADB.
Do I have this right so far?

rdnkchevy said:
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
Click to expand...
Click to collapse
That was fast! Wanna do my tablet?
The link you sent just now is to the version 3 zip file posted on 12/25, which is what I had initially downloaded. It does appear he streamlined the procedure, but it is that readme file which leaves out the part about installing the PC driver and ADB in the beginning, and also leaves out the part at the end telling you that you should now have 3.2 with a SU shell installed.
Please understand that I want to be "fully" rooted, not just have the ability to gain an SU prompt in terminal. Will this procedure "fully root" the tablet? I'm confused by what he means saying "SU shell installed".

Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...

rdnkchevy said:
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
Click to expand...
Click to collapse
OK, thanks!! Rooting went well without incident. I just installed Root Explorer and Titanium Backup, and made a backup to SD of my apps and data. Then installed Acer Recovery Installer, and let it install CWM Recovery. But what is considered the "home" button on the tablet?? Is it the reset button? The only buttons on this thing are the Volume rocker and the Power button. ( I got brave and found out it is the POWER button ).
Edit: To clarify, I meant to ask which button serves as the Home button while you are IN the CWM Recovery environment, not while in the Android OS home screen.

[Q] (HELP) Rooting 4.2.2 Nexus 7

Hi, now most people here are smart with this type of thing soooo i wanted to ask you how i can root the nexus 7 running 4.2.2. I tried to use the wugfresh NRT but when I was installing drivers a problem occurred. Instead of having ADB drivers or something like that I had ADB Composite drivers installed even though i followed the guide completely and I have tried several times to correct this but i havent found a solution. Also i attempted to carry on the rooting process but it said i did not have the correct drivers installed and etc. So can someone give me a fool proof way of getting the right drivers for this thing so i can root so i can finally install some kernels and use the sixaxis controller app! sorry for the essay and all help is appreciated

hrsedJe Something
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.

How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.

phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.

Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
Dude, most commands for doing stuff on the N7 manually are four words. It really isn't a lot to remember. Also I don't think you understand the purpose of this site/forum.
..That being said.
Use Wug's toolkit and update the adb files in its install directory. Then just use the 4.2.1 settings if 4.2.2 doesn't show.
Here is a post with the files: http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650

sucks that the toolkit is only for windows, sucky windows

Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2019519

had the same problems
Just google fastboot files for n7, get sdk and pack files AND the recovery into the sdk tool folder.
Shift+right click -> start command here
Fastboot flash recovery recovery.img
Start tab abd sideload the SU.zip (google superuser)
Flash
Done ))
Did it yesterday no issues!

phonic said:
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
Click to expand...
Click to collapse
Well said phonic. I prefer the manual way as well. It is always good to know what you are doing, but knowing how it works and learning something is always better.
I would much rather learn something than to have someone do it for me. If ever I need help and ask someone, they say I'll do it for you I say no, please show me how to do it!
Sent from my Nexus 7 using Tapatalk 2

kidujp said:
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
Click to expand...
Click to collapse
You may receive an error message "ABD" is offline, in this case download the latest Android SDK manager and upgrade all USB drivers before using the toolkit again.
Sent from my Nexus 7 using xda app-developers app

phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Never ceases to amaze me how many pretentious pricks use XDA.... Reminds me of Apple snobs.

command line is the way to go
command line is the way to go m8!!
cheers,
geek endangered

[Q] KitKat on a rooted Note 3.

Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU

Dardwizzle said:
Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU
Click to expand...
Click to collapse
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.

antique_sonic said:
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
>USB debugging off? turn it on. <--- It is and has been turned on in an effort to try to sideload KitKat, but that was a hug fail. But I will leave it on for this discussion.
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU

Dardwizzle said:
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
Click to expand...
Click to collapse
do check, is it running in background ? check your task manager. if so, kill the process. Kies should not run together with ODIN. Otherwise sometimes will give problem to your ODIN process.
I normally only install the USB driver only, as this is the only thing needed to connect your phone to comp (as MTP, or as ODIN connection).
Dardwizzle said:
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
Click to expand...
Click to collapse
ok, in a very simple word. download mode is basically a state whereby your phone is ready to download system files and install the system files on your device.
This is the only state possible to get a connection to your ODIN PC to flash stock firmware, recovery (in .tar/.md5 format).
How to get the KK ROM ?
1) identify your device. which model it is. N9005? N900T? N900A? N900 blablabla?
2) goto samfirmware.com (register there if you don't have account. it is free). after that you can just find your firmware by typing on the search device textbox your device model (e.g N9005), and it will come out the list of your device firmware (normally they will show for the latest firmware list)
3) choose the firmware that you want to download (if your device N9005 international 32 gb, try to avoid the Hongkong / Taiwan firmware, as they have different PIT partition).
4) once you have the downloaded zip file from samfirmware, extract the zip, and then you will get the (.tar/.md5) file. Now you can use to flash this one over ODIN.
Dardwizzle said:
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Click to expand...
Click to collapse
no. no. no.
This is how to go into download mode in your device
Not yet talking about factory reset.
But yes, you have to backup your internal storage, as sometimes upgrading will cost you to do factory reset, and your internal storage will be gone.
Dardwizzle said:
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Click to expand...
Click to collapse
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
Dardwizzle said:
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU
Click to expand...
Click to collapse
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.

antique_sonic said:
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.
Click to expand...
Click to collapse
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!

Dardwizzle said:
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!
Click to expand...
Click to collapse
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
http://www.droidviews.com/install-android-4-4-2-kitkat-ota-on-att-galaxy-note-3-sm-900a/
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.

antique_sonic said:
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
(I had to remove the link as the website thought I was adding it and gave me a no no warning that I can't post outside links cause I be a newbie!) BAH!!!
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding. It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight. I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me. I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!

Dardwizzle said:
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding.
Click to expand...
Click to collapse
No worries and yeah you should try to find first. by this way, you will learn faster, compare if someone do the spoonfeed.
Dardwizzle said:
It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight.
Click to expand...
Click to collapse
My pleasure to help. And no worries for late reply, as I will do the same when I busy with my real life job.
Dardwizzle said:
I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me.
Click to expand...
Click to collapse
you are welcome mate. I'm sorry to read the news about your conditions. I can't say anything about this, but wish you all the best. Don't ever feel down in whichever state you are, just do the best in life, and we will never regret that 1 more day has passed.
Dardwizzle said:
I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!
Click to expand...
Click to collapse
GOOD !!!
go and grab sales, rather than you brick the phone.
Once again, u r welcome mate.

Can you ADB push build.prop from a stock recovery? If not I'm in trouble.

Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.

taboo_ said:
Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.
Click to expand...
Click to collapse
I would flash a stock rom to get the phone running again, and next time make a nandroid backup that you can restore with a custom recovery before you mess with system files.

I'm currently downloading a stock rom from a very slow source. In the 3hrs or so it's going to take to download I thought I would absolutely confirm I was buggered as it would be nice if a few ADB commands could save me.
gee2012 said:
next time make a nandroid backup with a custom recovery before you mess with system files.
Click to expand...
Click to collapse
I do certainly know better. But Samsung in their power have decided to Knox flag your device if you install a custom recovery. As such creating a nandroid backup was not an option for as long as I want my warranty. I do have Titanium backups, and I thought I was doing the right thing by making a copy of build.prop before doing anything... turns out I was wrong. But really, thanks for your concern and advice.

..

fffft said:
Three hours huh? You should talk to Santa about a faster net connection.
Click to expand...
Click to collapse
I live in Australia. We asked our government and they said yes.... then we got a new government. But in this case it's the speed of the host that was hindering. It's all elementary now anyway as the download finished. No one had replied. I flashed it. It failed. And the long and short of it is adb is now useless to me.
fffft said:
You should know this already though as a five minute search on how to use ADB would have pulled up numerous tutorials.
Click to expand...
Click to collapse
I appreciate the help. But I'd spent all day reading tutorials. Trying commands. Failing. Googling the error. Trying new commands. Failing. Googling those errors. After doing that for some time I thought it would just be more sensible to ask people that have actually had experience.
fffft said:
You're also on the wrong site if you are obsessing over the Knox flag. Yeah, it might affect your warranty. Probably not, but I'll grant that it could. So simply decide up front it you want to modify your phone or wait out your risk free warranty period.
Click to expand...
Click to collapse
So here's the thing. I don't want my cake and eat it. I will absolutely be blowing away knox. I just didn't see a point in doing it preemptively. The phone is only a couple weeks old so I decide it would be wise to at least keep my warranty until I'm happy it's rock solid and I have a good reason to lose it - nice stable Cyanogenmod I'm looking at you. Plus anything I wanted to do up to now I was able to with Towelroot and xposed. I just couldn't Nandroid.
Really. Thanks for listing the commands. As of this morning I hadn't needed to use ADB at all. I appreciate you spelling it out. I just wish I had of seen it mere minutes earlier as I would have been able to let you know if it worked. Unfortunately I didn't. But I appreciate the effort.

..

fffft said:
And you say that your firmware download speed was host limited. I just did a search for half a dozen S5 firmware builds. Found all of them widely disseminated. And as one might expect, not all of the hosts were slow..
Click to expand...
Click to collapse
I was using sammobile.com on a free account. I'm sure I could have found a faster host but I've used sammobile.com many times in the past and they've always been reliable. I'd rather wait longer and get something I trust when I'm not in a hurry than download a file that has the right name but is just from a random "megaupload" link or something.
Now regarding adb I got a lot of the information I needed through google searches. I also watched a number of videos. But here's the thing. If I were just taking the opportunity to learn about adb google-ing around would have been fine. But as the circumstances were a little dire in this situation and I've expressed that I've never used adb before and was not confident. I didn't know what I was doing or have the experience to know the implications of what I was doing. As such 1) I didn't want to take the chances of getting it wrong and screwing myself over further and 2) I seemed to have a fairly unique issue (can't boot, stock recovery, "error: close" issue).
It wasn't just about knowing the commands to use, it was about finding out whether I was even able to do what I was hoping to do from a stock recovery on an S5 (hence the title of the thread).
You're getting a little judgey, which is fine you're entitled to your opinions. But I'd ask you read my title and first post again. It wasn't about just getting the commands outright coz I was too lazy to look, it was about getting a number of questions that I didn't know the answer to due to lack of experience, and that I hadn't had directly answered through google searches. Also I never implied an urgency, it was simply a case of "I had a contingency plan in place (downloading a stock rom) but I thought I may as well ask for some advice in the time I had while waiting for it to download".
It's not as though my case was a dime-a-dozen, "answered directly a million times". It was a little more unique and I had answered many of the general questions myself and decided that my remaining hesitations are best answered by those with experience. I'm sorry that bothers you.

Plus the reason you were able to have so much success is because you have experience and knew what to look for and understood the compounding factors. I had figured your first and third command out for myself. I was missing your second and I don't know if that was my problem, but the error I was getting "error: closed" seems to have a massive lack of documentation on the internet. Not many people are talking about it and those that are pretty much just say "update abd" - I was running the latest version. That is where I was coming undone.
But if you're STILL feeling disconcerted at my efforts here is my session from yesterday right before I made this thread. This is literally only a few of the tabs I had gone through: http://i.imgur.com/WDB3qIg.png

..

I just can not understand why you're being like this man. I've been nothing but polite. But I came on here to learn. If I was doing something blatantly against the community I'd expect to hear about it, but I just wanted help. You gave me help which was awesome but every time I took it or added something to explain my reasoning for my actions you added a lecture with it.
All I was trying to put across to you was that you don't know what I did or my reasoning for asking questions. I was just hoping you could see that your initial assumption about my laziness may not have been correct. Again, I'm not trying to be a **** about this and I really was thankful for the help you gave. But it seems you're more than willing to dish out the criticism but as soon as I defend myself or talk back you in turn get your back up. But I just don't understand why you seemed so interested in making assumptions about my efforts, my internet speeds and then telling me how I should be doing everything differently.