Related
[Review & How-to] Use ADB Wirelessly and How to Remove Carrier Bloatware from Android
I think this could go in a few of the different forums, but I'll stick it in here and the mods can decide.
I’m getting excited about all the apps that are letting me do things wirelessly on Android. SwiFTP made things a lot easier with its ability to set up your phone as a server that you can connect to from your PC. Today, we’ll take a look at adbWireless, which in essence does the same thing, but adds the ability to use adb wirelessly. The most important thing, for many, that this will allow you to do is remove carrier bloatware, that is, get rid of preinstalled apps. In today’s video, I’ll show you how to use adbWireless and how to remove preinstalled apps so that you can have your phone running in tip top shape.
How to Remove Carrier Bloatware from Android
"How to use an app" and promoting of great app finds belongs in the "themes and apps" forum. Hacking the phone outside of just using an app is what belongs here.
Sent from my PC36100 using XDA App
sombdy said:
"How to use an app" and promoting of great app finds belongs in the "themes and apps" forum. Hacking the phone outside of just using an app is what belongs here.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Exactly, which is part of the video. Did you watch it. There's a whole hacking section about removing bloatware. Thats part of development, no?
I don't know if I'd consider remounting the fs to be development. Nevertheless, good job showing the newbs.
I'll make one small addition though - if you can't delete anything from /system/app, exit the adb shell and run:
adb remount -ro
That mounts the filesystem as read / write so that you can make changes. I'd suggest doing:
adb remount -r when finished.
ALSO - Why the hell do you mention Terminal for Mac, and Command Line for Windows, but leave the Linux crew out???
Doward said:
I don't know if I'd consider remounting the fs to be development. Nevertheless, good job showing the newbs.
I'll make one small addition though - if you can't delete anything from /system/app, exit the adb shell and run:
adb remount -ro
That mounts the filesystem as read / write so that you can make changes. I'd suggest doing:
adb remount -r when finished.
ALSO - Why the hell do you mention Terminal for Mac, and Command Line for Windows, but leave the Linux crew out???
Click to expand...
Click to collapse
touche my friend my bad lol.
and yeah its not development per se, but definitely not any of the other topics.
and good point. now that i think of it, i'm not sure why it let me do it since i didnt remount as read/write
Very nice app. I will be trying it soon.
There is actually another very simple way to remove bloatware that doesn't require a computer.
First off, you must have a rooted phone.
Then install titanium backup and allow superuser permissions.
Go into settings and enable chuck Norris mode.
Then just find any app you want gone, click it and press uninstall.
Just offering another way to solve the same problem. Great app tho. It will definitely be worth trying.
Clay333 said:
Very nice app. I will be trying it soon.
There is actually another very simple way to remove bloatware that doesn't require a computer.
First off, you must have a rooted phone.
Then install titanium backup and allow superuser permissions.
Go into settings and enable chuck Norris mode.
Then just find any app you want gone, click it and press uninstall.
Just offering another way to solve the same problem. Great app tho. It will definitely be worth trying.
Click to expand...
Click to collapse
Yeah Chuck Norris mode for TB came out after I made this vid. Definitely gonna include it in my TB review
@ OP, nice find!! i got tired of that having to plug in just to run ADB, using this from now on. Do you know if it breaks anything by removing required apk's?
djR3Z said:
Yeah Chuck Norris mode for TB came out after I made this vid. Definitely gonna include it in my TB review
Click to expand...
Click to collapse
sombdy said:
"How to use an app" and promoting of great app finds belongs in the "themes and apps" forum. Hacking the phone outside of just using an app is what belongs here.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
dude, let the mods be mods. Why does everyone try and be the forum police?
djR3Z said:
Yeah Chuck Norris mode for TB came out after I made this vid. Definitely gonna include it in my TB review
Click to expand...
Click to collapse
Oh Ok, I didn't realize it had been updated to include it. Either way I was not trying to down your thead/video, the wireless ADB is nice. I have actually used it a few times since I was the video and really like it. Great find!!
System apps can also be deleted through root explorer. JUST BE CAREFUL and have a backup before you start playing around in the system folder.
djR3Z said:
I think this could go in a few of the different forums, but I'll stick it in here and the mods can decide.
I’m getting excited about all the apps that are letting me do things wirelessly on Android. SwiFTP made things a lot easier with its ability to set up your phone as a server that you can connect to from your PC. Today, we’ll take a look at adbWireless, which in essence does the same thing, but adds the ability to use adb wirelessly. The most important thing, for many, that this will allow you to do is remove carrier bloatware, that is, get rid of preinstalled apps. In today’s video, I’ll show you how to use adbWireless and how to remove preinstalled apps so that you can have your phone running in tip top shape.
How to Remove Carrier Bloatware from Android
Click to expand...
Click to collapse
Why is the wireless connection required?
Do the phone and the adb computer need to be on the same subnet?
Can this be done over ip?
I saw adbwireless on a blog this morning. The obvious use for me was to put the android-sdk folder on a USB drive that I keep on my keyring so that if I need to do something from another PC, I don't have to download and find the sdk. I can then connect the phone wirelessly after launching a cmd prompt from the USB drive. Makes it great for my work laptop, where I don't want those files sitting around to be scanned.
Thanks for the info on the app it works great. The only problem I had was in the adb command. Could never use it on my macbook pro always had to go the darkside to do adb commands. After watching your video noticed that you placed a ./adb connect ip: port. I was missing the ./ to get the adb commands to work. So not only did this show me a great app but also taught me how to use adb in terminal.
Andy S said:
I saw adbwireless on a blog this morning. The obvious use for me was to put the android-sdk folder on a USB drive that I keep on my keyring so that if I need to do something from another PC, I don't have to download and find the sdk. I can then connect the phone wirelessly after launching a cmd prompt from the USB drive. Makes it great for my work laptop, where I don't want those files sitting around to be scanned.
Click to expand...
Click to collapse
I LOVE your use of this. Great tip!!! I'm gonna set this up asap
islandreamer said:
Thanks for the info on the app it works great. The only problem I had was in the adb command. Could never use it on my macbook pro always had to go the darkside to do adb commands. After watching your video noticed that you placed a ./adb connect ip: port. I was missing the ./ to get the adb commands to work. So not only did this show me a great app but also taught me how to use adb in terminal.
Click to expand...
Click to collapse
I'm glad I could help! Yeah its a minor little thing, but it makes everything work
genius! Loading this up as we speak as well
Andy S said:
I saw adbwireless on a blog this morning. The obvious use for me was to put the android-sdk folder on a USB drive that I keep on my keyring so that if I need to do something from another PC, I don't have to download and find the sdk. I can then connect the phone wirelessly after launching a cmd prompt from the USB drive. Makes it great for my work laptop, where I don't want those files sitting around to be scanned.
Click to expand...
Click to collapse
I have a galaxy s 4g, had a week now. Installed a new loader, and app screen switcher, and was having problems with each wanting to run when pressing home. I did set launcher pro as default, but still had issues, so I uninstalled touchwiz launcher, just the launcher. Now my flipclock wont start. I've been told that touchwiz laucher has to be running for it to work. Ok.. phone is rooted, I have the touchwiz30 apk file (says no install when i see it with super user), it of course isnt installing when I try with super user. How do I get touchwiz launcher installed back to my phone?
I did search through posts here for the 4g and couldnt find this question elsewhere, please forgive if it is a replicated question, please include link to that thread!
I'm pretty sure you need to push the TouchWiz apk to /system/app... not install it.
Search the Vibrant forums too. I used to frequent that section and I think I remember people asking about that.
TouchWiz shouldn't be removed; As you have discovered, things rely on it.
ahorriblemess said:
I'm pretty sure you need to push the TouchWiz apk to /system/app... not install it.
Search the Vibrant forums too. I used to frequent that section and I think I remember people asking about that.
TouchWiz shouldn't be removed; As you have discovered, things rely on it.
Click to expand...
Click to collapse
Understood. (Android newb here). Ok.. so to get this back over I've had to install a ton of crap.. java sdk development.. then the android adk, I now have complete access to the phone, through terminal emulator on the phone itself, and through adb. All that works fine. however when trying to do the 'push' to the phone, I get permission denied.. I've tried various things.. using terminal to set /system/app to rw from there.. no go, tried opening two dos windows.. starting adb shell, tried remounting /system/app rw, then open using other dos window to do the push, i know the system is mounted rw, regardless of what I do I'm getting permission denied on the push. I *can* and have copied the apk through the shell, from the SD card to /system/app, however it doesn't actually install, just copies the file there... any ideas?
<still a newb but learning fast>
I haven't done it in a while. I haven't rooted my Galaxy S 4G yet (had it for a few days) and I sold my Vibrant several months ago. But I think once the apk is in /system/app, after a reboot it should be working... but I really don't know. Someone else is going to have to chime in here.
As for the "permission denied" errors, if your phone is rooted, the first time you're in the shell via PC and enter "su", the Superuser app should prompt you to give it permissions. From then on, every time you use adb through your PC, it should have super user permissions.
As a last resort, you might need to restore with ODIN if people have figured that out yet.
Honestly, I just got my phone like, two days ago and haven't done anything with it. I want to make sure I'm keeping it first. But the Vibrant wasn't much different so...
headway made, but not working yet
Ok, so here's what I've tried now. I've been using 2 dos windows to run adb with, the first I open a shell with, then set the /system/app directory to rw. I would leave that shell running. I switch over to the second dos window and try to do the push but get the (I'm finding now all too familiar "permission denied" error. So what I did next was to go back to the shell screen, and did a chmod 777 on the app directory. (Imma old SCO unix admin) Success!, I was able to push the file to the phone. I'm assuming that even though I have su with the first window, I don't with the second. So in doing that I allowed anyone to write to the app directory. However, the app still doesn't work. Nothing happens, I rebooted the phone, removed defaults for my current laucncher program, hit home, and the orginal twiz launcher doesnt appear in the list to set default to. God, what am I missing now?? Oh, after done I did reset app to 755. Do I need another file? Do I have the right file? (when browsing files it still says "no install" on it. I'm trying guys.. any help would be appreciated.
[email protected] email
sonny_in_az yahoo messenger
hell I'll put my phone number here if neccassary.....
<still a droid newb but learning fast>
BTW, since you just got your phone, I love mine. first smart phone tho so I cant compare to others, but here's what I've found. Get another battery. The factory one, when pushed hard, dies in 3.5 hours or so. I got an aftermarket battery 3000mh, awesome now.. ran multiple apps, games, wifi connections.. etc.. hammered it 7 straight hours and still had 38% left. Huge diff. Comes with a new back as the 3200 is a lot bigger than the factory, if you can live with that. I don't care about slim.. it's gotta work.. ; )
OK.... Ive been an HTC Desire owner for a year and regularly flash ROMs but ive managed to be able to distance myself from the whole adb 'thing' thanks to Unrevoked (ie a 1-click-root).
Being an owner of a Transformer now Id love to be able to root the beast and carry on with Flashing and tweaking but the whole rooting thing now scares me a little
ive done a fair amount of googling and I believe it requires install of software and drivers but most guides are for Android 2.1/2.2 etc and I know 3.0 is a different ballgame ..... Im also running windows 7 64 bit which seems to make things more complex. I fo have a dual boot to ubuntu but ive only really been using that to play around - im no Linux expert !!
Anyone know if there is likely to be a one-click-root developed for Honeycomb ?
adb - or the initial setup of adb - scares me
ADB setup isn't that hard, there are loads of guides on the internet already. I'm running W7 x64 and I didn't really run into any problems getting ADB up and running.
ADB isnt as hard as it sounds, its worth it to learn since there so much you can do with it. its just a matter of knowing what code to use and most of the time its posted and you just have to copy and paste. i prefer to use ADB sometimes instead to scripts that way you know exactly whats going on.
but im sure there will be easier ways to root if you just wait, there's still a huge shortage and im sure lots of people that want to develop for the TF are still waiting to get their hands on one.
ADB isn't all that daunting and besides, learning new things is enjoyable My hesitancy to root rests in some of the issues that folks are having. My screen wouldn't wake up once, I had to reboot to get my TF going again. I'm waiting now
to make sure the unit is solid and stable running the stock configuration. I don't want to root only to have the thing decide to become a paperweight 3 days later.
Using ADB should not be beyond anyone who has rooted and installed bits before. I think it is the lack of GUI and reassuring responses and prompts that people miss and are used to.
if you are following this guide and ADB is responding well, you can even cut and paste the commands into your command window (on PC you can) and this helps prevents missing spaces and syntax problems.
Bottom line though - if you are not comfortable doing it, don't risk it.
lol.... OK.... ive had a go ..... and i think it has worked
didnt help that my 'installing archives' in the Android SDK Manager is now hanging due to the washing machine in the garage catching fire and blowing the fuses therefore causing my connection to the web to break halfway through downloading
... and now im having problems downloading blob5 as it says im running concurrent downloads ....
Its always the unexpected stuff that causes problems
I love the smell of an electrical washing machine fire in the morning
Yep, had problem getting blob5 too. Didn't like my IP address? Got it from work instead - Don't tell the 'IT Police' (Although I am sure their logs will grass me up)
can anyone provide an alternative link to blob5? won't let me download
You could try resetting your ADSL modem to obtain a new IP address - that might work. As I mentioned above the site decided I had abused my download limit (at my first attempt!) and blocked my current IP.
Assuming you are not on a static address?
I'm on static
wilbur-force said:
can anyone provide an alternative link to blob5? won't let me download
Click to expand...
Click to collapse
Try this http://dl.dropbox.com/u/3387763/CWM_BLOB_V5
cheers
that's done the trick
You're welcome.
I've just ordered myself a Transformer and will no doubt want to root it after a while, if there any particular ROM that's considered the 'best so far'?
from what I gather most of the roms are still very early days. at this point I'm after root for nandroid and some of the root apps.
ok... very noob question
the root guide says to copy the blob/files to your 'adb directory' ... which directory is that ? the android-sdk directory ? or a sub folder of that ???
wilbur-force said:
ok... very noob question
the root guide says to copy the blob/files to your 'adb directory' ... which directory is that ? the android-sdk directory ? or a sub folder of that ???
Click to expand...
Click to collapse
copy it to platform-tools
android-sdk-windows/platform-tools/blob (all files + blob should be here)
also you can hold shift + right click platform-tools and choose open cmd window here.
I have looked, and searched and looked and searched and looked some more... and I cant fine one ****ing sure fire way to root my Samsung Galaxy S 4g. There are so many links to this and that with no explanation and its killing me. and before I get flamed, I'd like to say I have a mac, so obviously if I had a windows phone I would have had this all done lickedy split already.
So if someone could walk me through the steps to rooting my phone and getting power user on my t-mobile samsung galaxy s 4g for mac that would be wonderful. please and thank you!
jowings18 said:
I have looked, and searched and looked and searched and looked some more... and I cant fine one ****ing sure fire way to root my Samsung Galaxy S 4g. There are so many links to this and that with no explanation and its killing me. and before I get flamed, I'd like to say I have a mac, so obviously if I had a windows phone I would have had this all done lickedy split already.
So if someone could walk me through the steps to rooting my phone and getting power user on my t-mobile samsung galaxy s 4g for mac that would be wonderful. please and thank you!
Click to expand...
Click to collapse
I'm no Mac user, but this should help....
http://forum.xda-developers.com/showthread.php?t=997475
--Quote from Papermakesplanes:--
1. Install Mono
2. Install the thing you're trying to run under Mono, like SuperOneClick
3. Open Terminal in your Mac
4. In Terminal, type: cd /Applications/SuperOneClickFolder or whatever your folder is
5. In Terminal, type mono SuperOneClick.exe or whatever the name of your executable is. As you can see, this is super similar to doing the Run... commands in Windows, except it's mono instead of run
6. Your file should open now. But, you really don't want to be opening terminal and opening software by command line, do you?
7. Right click on SuperOneClick.exe and go to More -> Automator -> Create Workflow. If this doesn't work for you (it didn't for me...), then open up Automator, Create New Workflow, and drag in the .exe you want to run into the Workflow area
8. Add a "Run Shell Script" to this workflow. In the Shell Script area, type exactly what you typed into the Terminal earlier:
cd /Applications/ApplicationFolder
mono Application.exe
--End of Quote--
im 19 now... I was a techy nerd when i was like 14. I built all my computers and new everything and anything. As I grew older i got into cars and kinda forgot all the techy stuff... so this doesnt help me at all
why can't I just plug in my my and do a oneclick root or a z4 root. I feel like it shoukd be easy but it seems like galaxy s 4g userd are either hella complicated or hella pro pc and dont have a lot of support for mac
jowings18 said:
im 19 now... I was a techy nerd when i was like 14. I built all my computers and new everything and anything. As I grew older i got into cars and kinda forgot all the techy stuff... so this doesnt help me at all
why can't I just plug in my my and do a oneclick root or a z4 root. I feel like it shoukd be easy but it seems like galaxy s 4g userd are either hella complicated or hella pro pc and dont have a lot of support for mac
Click to expand...
Click to collapse
-All you really have to do is install mono, then download SuperOneClick (make sure the file is named that too) and put it in Applications/SuperOneClickfolder.
-Open terminal, and type in cd /Applications/SuperOneClickFolder, and then mono SuperOneClick.exe
-"Right click on SuperOneClick.exe and go to More -> Automator -> Create Workflow. If this doesn't work for you (it didn't for me...), then open up Automator, Create New Workflow, and drag in the .exe you want to run into the Workflow area."
-"Add a "Run Shell Script" to this workflow. In the Shell Script area, type exactly what you typed into the Terminal earlier:
cd /Applications/ApplicationFolder
mono Application.exe"
I don't know how to simplify it any further, sorry.
Just to let ppl know the old way to flash did not work for me if you use the command at fastboot menu fastboot flash init_boot path/to/magisk_patched.img and it didn't work, you have to specify the partition your flashing to, you can see this from the fastboot menu if your on partition "a" then the command is fastboot flash init_boot_a path/to/magisk_patched.img and switch "a" for "b" if your on b. hope this helps
You don't need to specify the partition slot, because it always goes to the "Active slot".
*Fastboot flash init_boot init_boot.img*
ekin_strops said:
You don't need to specify the partition slot, because it always goes to the "Active slot".
*Fastboot flash init_boot init_boot.img*
Click to expand...
Click to collapse
This.
Also, it's easier to opened CMD in the directory you have the patched image so you don't have to type out the path to it.
I've found that a lot of people who find it necessary to specify which slot to flash (fastboot flash init_boot_a... or fastboot flash init_boot_b...) use Windows PowerShell instead of classic good ol' CMD. I'm unsure why PowerShell has little issues like this (I've seen some people are required to include the "./" in the command line or it doesn't work), but that's why I exclusively use CMD & suggest using that instead when giving advice...You don't really run into any issues using that (although, sometimes it's tricky to try and explain someone on how to run it with Administrator privileges...)
simplepinoi177 said:
(although, sometimes it's tricky to try and explain someone on how to run it with Administrator privileges...)
Click to expand...
Click to collapse
It's not that difficult.
Hit the Windows key to bring up the Start Menu, type cmd, right-click command prompt, run as administrator. Even my grandma could follow those instructions.
Honestly if people don't know how to do something that basic, they really shouldn't be messing with their phones in the first place.
EtherealRemnant said:
It's not that difficult.
Hit the Windows key to bring up the Start Menu, type cmd, right-click command prompt, run as administrator. Even my grandma could follow those instructions.
Honestly if people don't know how to do something that basic, they really shouldn't be messing with their phones in the first place.
Click to expand...
Click to collapse
Good advice...I'm a bit old school and normally advise using the Run command...I forget Windows after 7 implemented that way of doing it...
And then sometimes in certain cases using the Run command doesn't give the option to run as administrator...
But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...
And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...
simplepinoi177 said:
Good advice...I'm a bit old school and normally advise using the Run command...I forget Windows after 7 implemented that way of doing it...
And then sometimes in certain cases using the Run command doesn't give the option to run as administrator...
But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...
And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...
Click to expand...
Click to collapse
I used to work tech support so I got in the habit of finding the absolute easiest way to tell people to do things. Windows key shortcuts are a godsend for tech calls. They're obscure enough that if you get a techie on the line who would normally be offended by you holding their hand through things they might actually thank you for learning something new but easy enough that someone who can barely turn on a computer can key peck their way through it lol.
I also specifically like using this shortcut because it's so easy to run in admin mode. It's how I personally launch basically everything on my computer that I haven't pinned to the taskbar.
simplepinoi177 said:
But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...
Click to expand...
Click to collapse
Yeah, I've never had to use elevated command prompt when flashing.
I just put whatever I'm flashing in the Platform Tools folder, type "cmd" in the address bar of the Platform Tools folder to open command prompt from that folder and away I go.
Curiousn00b said:
Also, it's easier to opened CMD in the directory you have the patched image so you don't have to type out the path to it.
Click to expand...
Click to collapse
You can also just copy and paste the path - which is presumably what OP was doing.
NippleSauce said:
You can also just copy and paste the path - which is presumably what OP was doing.
Click to expand...
Click to collapse
That too. I'm so use to installing ADB/fastboot into my system's path that I forgot if you have it in one location, you need to do paths.
I be having one open in my downloads, the desktop, and a folder where I keep stuff when I mess with my phone's, lol.
ekin_strops said:
You don't need to specify the partition slot, because it always goes to the "Active slot".
*Fastboot flash init_boot init_boot.img*
Click to expand...
Click to collapse
i wrote this post because when i did not specify a partition it failed. its literally in my post that the normal way to do it failed for me. I used cmd to not powereshell.
simplepinoi177 said:
I've found that a lot of people who find it necessary to specify which slot to flash (fastboot flash init_boot_a... or fastboot flash init_boot_b...) use Windows PowerShell instead of classic good ol' CMD. I'm unsure why PowerShell has little issues like this (I've seen some people are required to include the "./" in the command line or it doesn't work), but that's why I exclusively use CMD & suggest using that instead when giving advice...You don't really run into any issues using that (although, sometimes it's tricky to try and explain someone on how to run it with Administrator privileges...)
Click to expand...
Click to collapse
i used cmd and not specifying a partition made it fail.
EtherealRemnant said:
It's not that difficult.
Hit the Windows key to bring up the Start Menu, type cmd, right-click command prompt, run as administrator. Even my grandma could follow those instructions.
Honestly if people don't know how to do something that basic, they really shouldn't be messing with their phones in the first place.
Click to expand...
Click to collapse
What are you talking bout? I did exactly that and it FAILED for me unless i specified a partition. The only thing i did a lil funky is i didnt open cmd in the folder the patched image was in so i had to drag and drop file to add path.
simplepinoi177 said:
Good advice...I'm a bit old school and normally advise using the Run command...I forget Windows after 7 implemented that way of doing it...
And then sometimes in certain cases using the Run command doesn't give the option to run as administrator...
But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...
And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...
Click to expand...
Click to collapse
novice? yes. and this post is for other novices who want full control of their phones. im a specialized mechanic that rebuilds transmissions for a living, not a techie but i love to dabble. i dont put others down because they cant install an overdrive sprag or a rear case bearing with race, or intermediate and overdrive servos cause im not fffing 12 years old. and please explain what im doing wrong then cause everything you guys say is basic i did. I installed adb and fastboot drivers i patched the init image, opened admin cmd and tryed to flash and it didnt work until i specified a partition. the only thing i did a lil diff is i didnt open cmd in the folder the patched img was in i had to drag and drop,,, its jus sad how ppl can type like there some tough sh*t but if this was face to face youd have nothing to say, in prison we called you guys window warriors lol.
Linxy420 said:
novice? yes. and this post is for other novices who want full control of their phones. im a specialized mechanic that rebuilds transmissions for a living, not a techie but i love to dabble. i dont put others down because they cant install an overdrive sprag or a rear case bearing with race, or intermediate and overdrive servos cause im not fffing 12 years old. and please explain what im doing wrong then cause everything you guys say is basic i did. I installed adb and fastboot drivers i patched the init image, opened admin cmd and tryed to flash and it didnt work until i specified a partition. the only thing i did a lil diff is i didnt open cmd in the folder the patched img was in i had to drag and drop,,, its jus sad how ppl can type like there some tough sh*t but if this was face to face youd have nothing to say, in prison we called you guys window warriors lol.
Click to expand...
Click to collapse
whoa whoa whoa... someone's pretty touchy...
how was I putting others down? I said I found it surprising that some "novice" users skip some steps to achieve more advanced stuff without understanding basics and can get themselves into trouble and/or not be able to properly backtrack because they skipped through the basics -- it was simply based off of a ironic situation of how if someone couldn't even run an elevated cmd yet they are trying to mod their device. Never did I say you, or anyone specifically, were these novice users. It was a general comment on that type of situation.
How am I typing "like they're some tough sh*t"? And I find it hypocritical that you make assumptions about me "talking down" and generalizing you as a novice, when you make assumptions of me that I just "type like they're some tough sh*t" but face to face I'd have nothing to say and generalizing me as "window warriors". Interesting that you're so insulted, yet sling the same type of remarks...
Linxy420 said:
... please explain what im doing wrong then ...
Click to expand...
Click to collapse
and in an attempt to posit an idea that might've been wrong, I did mention that, in many cases I found, a lot of people were required to do what you did because they were using powershell instead of cmd and powershell is iffy in its execution, so it might've been that...
I know in the end you clarified that you use an elevated cmd, not powershell, and still had to specify what slot to apply it to. Sometimes it just goes that way, I guess. None of us are Google software engineers, so we can only guess and probably can't give you a complete straight answer. Most of us don't need to specify the slot; applying it to the active slot usually is enough.
So, I hope you consider all this and re-evaluate some things....
Linxy420 said:
What are you talking bout? I did exactly that and it FAILED for me unless i specified a partition. The only thing i did a lil funky is i didnt open cmd in the folder the patched image was in so i had to drag and drop file to add path.
Click to expand...
Click to collapse
If you go back and re-read what I wrote, I wasn't talking about you, just giving @simplepinoi177 an easy way to tell people how to run command prompt and other things in administrator mode...
Strange, I've never had to specify the partition....
Two thoughts: first make sure you use the latest platform tools as available from Google and second it may be an idea to use --slot=all as parameter for flashing, this way you can make sure all slots are flashed......
simplepinoi177 said:
whoa whoa whoa... someone's pretty touchy...
how was I putting others down? I said I found it surprising that some "novice" users skip some steps to achieve more advanced stuff without understanding basics and can get themselves into trouble and/or not be able to properly backtrack because they skipped through the basics. Never did I say you, or anyone specifically, were these novice users. It was a general comment on that type of situation.
How am am I typing "like they're some tough sh*t"? And I find it hypocritical that you make assumptions about me "talking down" and generalizing you as a novice, when you make assumptions of me that I just "type like they're some tough sh*t" but face to face I'd have nothing to say and generalizing me as "window warriors". Interesting that you're so insulted, yet sling the same remarks...
and in an attempt to posit an idea that might've been wrong, I did mention that, in many cases I found, a lot of people were required to do what you did because they were using powershell instead of cmd...
I know in the end you clarified that you use an elevated cmd, not powershell, and still had to specify what slot to apply it to. Sometimes it just goes that way, I guess. None of us are Google software engineers, so we can only guess and probably can't give you a complete straight answer. Most of us don't need to specify the slot; applying it to the active slot usually is enough.
So, there is all that....
Click to expand...
Click to collapse
I posted of what i had to do to get my pixel to gain root access. your answer made it sound like only advanced users should ever have root access to their phones and a "novice" shouldn't even try, you might not have meant it but you made it sound like that and yea it ticked me off a lil but i do apologize, I might have taken it a lil far rereading my post. I try to help when I can even with my meager tech savvy and if i can help a couple people having the same issue as me im quite happy. and im sry but saying being a novice and getting it done jus instills confidence for them to mess up later is a put down, i dont know bout others but i do know my limits i toyed with many phones in my past and even bricked a couple and through a bunch of trial and error got em unbricked.
simplepinoi177 said:
And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...
Click to expand...
Click to collapse
Linxy420 said:
... and im sry but saying being a novice and getting it done jus instills confidence for them to mess up later is a put down, i dont know bout others but i do know my limits i toyed with many phones in my past and even bricked a couple and through a bunch of trial and error got em unbricked.
Click to expand...
Click to collapse
I was going to leave this all well enough alone, but I wanted to give some clarification and leave a word of warning/caution for any novice users (*not anyone in particular*) that just might be perusing this, and since this is a thread about "root issues" I hope its considered still be on topic -- although being an I.T. tech I have numerous other examples, the particular situation that came to mind in my original quoted remark is on novice users who nonchalantly attempt to manually relock their bootloader on Pixels (I'm sure experts here who have assisted others in the subject are already groaning and can sense where I'm going with this...). It's pretty much always the case where there are seemingly countless users who have found themselves in this situation where they skipped through past the basics (merely unticking the OEM unlock button, unlocking the bootloader), modified partitions (whether just to root or to apply custom ROM), and because they achieved this they had become overconfident without understanding how running the unlock bootloader command is severely a lot less riskier than the locking bootloader command (without proper preparations and considerations), how to flash a Full Factory image, or why it's important to keep (or even just have remain) the OEM unlock button unticked until the end; and ultimately, hard-brick their device where no amount of trial and error will get it unbricked in the end.
As in this case, speaking on novice users who were successfully able to go straight to modifying partitions and/or applying a custom ROM (advanced goals) and had become overconfident that they didn't properly research the basics (flashing Full Factory images) or heed warnings of re-locking bootloaders and ended up hard-bricking their devices -- basically "being a novice and getting it done jus instills confidence for them to mess up later" -- is not, and was not meant to be, a "put down", but merely stating what happens from time to time. And, I did state that it is "for better or worse" that it "compels and instills confidence to be messing with their phones/devices more" -- "better" if it leads to careful experience, "worse" if it leads to overconfidence and brazen irreparable but avoidable damage. But, I'm sure, that all experienced users, both experts and not, had been led to their success due to them messing with their devices, so it's not to say one shouldn't do it and me trying to gatekeep, it's more me saying; sometimes you have to crawl before you walk before you run, it always surprises me when some people run after just learning to crawl (let alone walk), and people who do that should brace themselves for faceplanting -- but it should not be considered putting them down saying this.
In the end, don't skip the basics, thoroughly research, it is not a put down when speaking on those who do not do these things but attempt advanced scenarios anyways, and do not relock the bootloader on Pixels (unless very particular, exceptional circumstances).