Related
I don't know anything about this programming. I am a complete idiot when it comes to this stuff. I rooted the phone because I wanted to be have full control over it's capabilities going forward, but I didn't realize I'd need to use these programs on my computer to do it. I thought things would be available through simple downloads.
Anyway, I've spent the last several hours attempting to become at least functional so that I could install another OS on my phone. I have no idea what rebooting in recovery or clearing caches or any of this is. I know it's probably simple, remedial stuff to practically everyone reading this but I am clueless.
I'm sure I could learn and was willing to do so. I downloaded SDK and Java update and Eclipse and painstakingly followed installation instructions several times from several sources. And I can't get the adb to function. My computer won't recognize the path. I'm pretty certain that I've installed everything completely and updated the path accurately, etc. I go through cmd, type in adb and it says it's not recognized as an internal or external command, operable program or batch file.
I've gotten to the point where I just want to set my phone back to the way it was when I bought it 2 days ago. I want to go back to being a simple lemming and just oblivious to this whole world. I don't belong over here. I'm out of my league and I know it.
Now the problem I have is that it's supposedly easy to "unroot" the phone. You just have to download 3 things and "flash" them. I don't even know what the **** that means though. And if it invloves using adb (or abd...I don't even know that), then I'm screwed.
I'm really frustrated guys. I'm tired. I should have never attempted this, but it all sounded so easy and awesome. Now I just want my normal, restricted phone back. Can anyone help me?
OK. I got the phone back to it's original state. I know some of you are probably shaking your heads at the decision, but it makes me feel a lot more comfortable.
Maybe if I could figure out how to access adb, it would be different but I just felt handcuffed without it. Well there eventually be ROMs that are more easily installed like re-installing the original was? Will there be ways to just steam it through HTC Sync?
i think one reason why u didnt manage to get adb working is because u didnt set up the environmental variables for java. Go into command prompt and type java. See what that returns.
SupremeBeaver said:
i think one reason why u didnt manage to get adb working is because u didnt set up the environmental variables for java. Go into command prompt and type java. See what that returns.
Click to expand...
Click to collapse
Thank you for the response. That command produced a long string of information. Is there something in that I should be looking for, or was this just a test to see if it would be recognized?
it was a test to see if java was working fine. By string of commands do u mean like this:
http://img682.imageshack.us/img682/8440/48798806.jpg
Otherwise the problem may be that you havent specified the environmental variables for the android sdk.
Right click on My Computer and go to properties, under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Now what u need to do is add the location of ur sdk to the end of the "Variable Value".
So if u put the adroid sdk folder in the root of ur C drive, then u would add this line
;C:\Android\tools
to the end of the Variable Value line. This depends on where u put the skd folder though. Whats important here is u dont replace whats already there! Just add the line to the end, even the ";" symbol.
Hope this helps. let me know how it goes
Thank you again for the response. Yes, that looks to be the same screen information that appears when I run java in command.
I have the SDK in a folder named AndroidSDK on the root of my C drive. I have added the line ";C:\AndroidSDK\tools" to the end of the path. One thing I just realized is that when I double click the AndroidSDK folder, the next screen contains a single folder named "android-sdk-windows". When I double click that folder I see subfolders for add-ons, platforms, tools, SDK readme, and SDK setup. I'm wondering now if I need to include that "android-sdk-windows" in the path line in order for it to find adb in the tools.
I would really like to solve this adb issue. I still want to learn enough about this stuff to root the phone again and feel comfortable working with it. I'm completely obsessed with this right now. It's driving me mad.
in that case the line you should add would be
;C:\AndroidSDK\android-sdk-windows\tools
I can't believe it was that simple!
Actually I can believe it. Thank you so much for your help. Sorry if I came off as a bit of a drama queen in the OP, but I have just spent about 6 hours messing with this if you include the rooting.
Ok. I think I'm going to give it all another shot. Thanks again. I may be back to this thread again if I end up running into another dead end though.
Glad it worked
Dont worry about it, i can understand ur frustration because this is by no means straight forward.
Hope u enjoy playing with ur soon to be rooted EVO
If you have time to answer another question, I went through the OTA Simple Root process again and everything appears to have worked. But I don't think that finishes the phone in root. I don't have a Superuser app, for instance.
Isn't there something else I need to do? (Install a custom rom maybe?)
If so, how do I accomplish it in the least technical way possible?
Im not too sure with that actually. I dont have an EVO (or any android phone for that matter). But yeah i think the superuser app should appear without flashing a custom rom.
I think you might want to create a thread in the EVO section where im sure many EVO owners will help u out with this. Or maybe a mod could move this thread?
JelloB said:
If you have time to answer another question, I went through the OTA Simple Root process again and everything appears to have worked. But I don't think that finishes the phone in root. I don't have a Superuser app, for instance.
Isn't there something else I need to do? (Install a custom rom maybe?)
If so, how do I accomplish it in the least technical way possible?
Click to expand...
Click to collapse
Disclaimer - I have not used the simple root method.
That being said I have helped a few people with this and it seems that the last img file that it flashes does not have super user access. You need to flash a custom ROM in order to fix that. I will post a link to the thread that I was helping in and that should answer some of your questions on how to do that.
Hope that helps
http://forum.xda-developers.com/showthread.php?t=722194
Sent via the Sprint HTC EVO
Just wanted to update this. I finally was able to put it all together. I was previously unaware of the "extras" tab on the OTASimpleRoot program. Just didn't read the instructions in post well enough, which is the story of my life....but I digress.
Anyway, I was able to root the phone again, flash recovery and now I have even gotten to the point where I understand a little bit how to install custom roms. In fact, I just installed my first using Baked Snacks latest update. I've also downloaded ROM manager so in the future I should I have no trouble at all (even though I'm pretty comfortable doing it the "long" way now).
Thanks again to both of the guys above who took the time to read and respond to a complete newbies questions.
I now that I have successfully loaded a custom ROM onto my EVO that it is full root and I don't have to worry about that anymore. I don't have a "superuser" app that I can tell, but I do have a "dev tools" app and folders which I don't think were on the phone before.
Alright, I do have a superuser permissions app. When I click it nothing happens though. I don't know if that's normal or not.
The issue I'm having now is that when the phone was rooted it took it back to the 1.17.651.1 software version. I went through the steps in the "How to start over: Fully rooted stock 1.47..." thread but the phone doesn't appear to be reading the PC36IMG.zip file. It doesn't ask if I want to update it. I tried it a couple times and then skipped to the second file in that thread (su-2.1-e-unsecure-signed.zip) and got a message about ....something "build". Went ahead with the install but I don't see anything different. Still says I'm on software 1.17.....
Wireless tethering app doesn't work for me, which was the impetus to dig further into this....deeper down the rabbit hole.
Ok. This will be my last update but I'm pretty excited because something has happened to correct issues I was having.
I thought I would go through the root process from start to see if I could get the 1.47 software. Once I got to the second step and did the factory reset, upon reboot it took me to the recovery screen which was different and made me a little nervous. I found the cue to install BakedSnack again from the sdcard and chose that function.
This time things were different than before. For instance, upon booting the phone I got a cool screen saver with streaming, trippy colors instead of the 4G and Sprint crystaline logos. I don't remember this happening the first time I installed this ROM. Once I got into the phone I noticed some minor changes I didn't notice the first time. The music widget wasn't on the second page, nor the nascar or football crap either. I think they were there before. Then I went into apps and saw ROM manager installed and superuser and Wifi tethering. Went straight to wifi tethering and low and behold it works like a charm.
Last but least, I went to check the software and I am now running 1.47. I don't know why it's on their now. This is all still a little mysterious to me. I could swear this Baked ROM is a little different than the first time I had it on the phone. Maybe that's my imigination. Maybe the factory wipe did something. I don't know but I'm very happy now.
Congrats
SupremeBeaver said:
Congrats
Click to expand...
Click to collapse
Thanks again man!
What a difference 24 hours can make. At this point last night I was ready to pull my hair out in frustration. By noon today I had unrooted the phone and re-installed the most recent OTA software update and was ready to just stick with that. Now I have re-rooted, somehow managed to get the updated software back on the phone, and have installed and am running an incredibly awesome custom ROM.
I love my new phone. Thanks again to both of you guys who offered help. I think I'm going to be good from here on.
This is easier than making a cup of coffee.
Pictures below as attachment couldnt figure how to put the pic here edit figured it out now im just lazy.
you dont have to do it the hard way
Everyone (edit: i thought so at the time)will want this "Fully" (note below) funtioning Ubuntu system
or you can make your own here: http://forum.xda-developers.com/showthread.php?t=913622
I will be maintaning and updating as time permits
Phone has to be rooted: http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/Guides_&_Tutorials
NEW IMAGE 3.5 gigibyte
Lucid base image (only added: lxde and tightvncserver): Zip http://www.megaupload.com/?d=GLMYVCMN User: "dad" Passwd:ffffffff
Remove app2sd and settings- applications- manage applications- sdcard "move all apps to phone" or it will not work!
I suggest you install gnome-panel
I use it and i find no speed differance!
trying to get :upstart services" to work im looking into compiling a kernel with "CONFIG_TMPFS enabled, to initiate a workaround, because "upstart" services wont work in a chroot.
Stock Maverick : http://www.megaupload.com/?d=56AT71WD
Karmic Sucks programs stop opening after some short time, so i gave up.
Tested with: CM7 http://mirror.teamdouche.net/get/supersonic/update-cm-7.0.0-RC1-Supersonic-signed.zip
CM6: http://mirror.teamdouche.net/get/supersonic/update-cm-6.1.2-Supersonic-signed.zip
myn-WarmTwoPointTwo-11-05-2010-RLS-3
Unzip
Copy the "ubuntu" folder to your sd card
Go to market download "Terminal" and android VNC Viewer
Open terminal and type: (without the quotes), "su" then "cd /sdcard/ubuntu"
then "sh ./ubuntu.sh"
then "bootubuntu"
then "vncserver :0 -geometry 1024x800"
Thats it, go to android VNC Viewer and use dad for nickname, "ffffffff" for the password, "localhost", for address, 5900 for the port, Use 24bit veiwing settings, then go.
to shutdown you will have to power off phone and power back on.
Enter in your :"Initial Command",in the settings of Android Terminal:
su
cd /sdcard/ubuntu
sh ./ubuntu.sh
bootubuntu
So everytime you want to start ubuntu just open terminal
to start VNC SERVER automaticly you will have to add to the bottom of your /home/.bashrc file this:
cd /
rm -r -f /tmp
mkdir /tmp
vncserver :0 -geometry 1024x800
Thats it, your off ENJOY
Notes: Its as fully funtioning for myself, cant speak for everyone
This is in Beta stages I am an old Visual Basic dabbler as a hobby, and am not very fluent in the lenux operating system. However this "ubuntu on mobile device" has rekindled a lost desire to program.
I will update changes as i get the time
If anyone would like to contribute their lenux expertese to iron out the bugs, i and so many others would appreciate it
Issues to work on:
:no sound
NOTE: A big kernel level problem is the lack of sound. Most of the kernels we use as a base for our ports are designed for Google Android. Android doesn't use the standard Linux sound System ALSA. An ALSA wrapper for the EVO DSP kernel system must be written.
:Setting up users and groups (used kusers but seemed to slow system a bit, needs kde-common) But is very tolorable, I actually use dolphin. (cant get nautilus to create folders or files (destination read only? u got me)).
:hacked /root/.bashrc for easy login help (when using terminal runs .bashrc. dont know anotherway to start hamachi on login and also vncserver tries to restart)
:keyboard mapping (mapping arrow keys to the abc keyboard it has arrow keys, esc,etc...)
: No way to exit or turn off ubuntu. You have to turn off phone, to turn off ubuntu.
nce in a while the programs refuse to open, it has somthing to do with ?. you have to restart ubuntu again.
I suppose a fluent ubuntu/lenux person could help change usernames and such, using the terminal,set proper permissions and such
Im using CyanogenMod Rom its the only one that works with Hamachi
your rom will most likely work, however networking wont!
Tips:
ownload VNC for your computer and modify your ubuntu desktop on your computer screen (that way i dont need my glasses) (use "ifconfig" to find ip address)
:You can even use VNC to view the build while in qemu emulation, after installing lxde and tightvncserver in the emulation. (watch out for seg faults)
:In terminal, preferances-initial command, enter the "cd /sdcard/ubuntu ...etc ," that way its a one click to login .
:Get "abc keyboard" from market it has the esc, arrow keys etc... ( extra keys only good outside chroot, the "terminal", on your android desktop)
:If your not familiar with ubuntu, you use synaptic package manager to install programs
:When u share over himachi or start smbd, programs will stop opening.
.
Trust me everything i want it use it for seems to be pretty zippy, but just give a little xtra time for programs to load the first time. (Firefox may take 90 sec. to load the first time. After that its a snap)
I Would like to check into this
The no sound issue is getting to me, I may wait for that as that is an essential to my all in one device.
THANKS FOR THE HARD WORK. I LOVE UBUNTU
you really have to try it and tell everyone about it cant believe its not one of the hottest topics
I Would like to check into this
any way to delete this post....didn't mean to submit, came back to send like i didn't send it but ending up sending twice
apologies
Sounds pretty cool, I will defiantly have to give this a try. Question though, is this installing over top of the rom I am currently using. Example I am using the MIUI 1.22, if I install this is this like dual booting or will it just uninstall every time I reboot the phone??
Is it still uploading? I really want to try this!
corybucher said:
Sounds pretty cool, I will defiantly have to give this a try. Question though, is this installing over top of the rom I am currently using. Example I am using the MIUI 1.22, if I install this is this like dual booting or will it just uninstall every time I reboot the phone??
Click to expand...
Click to collapse
This will sit on your sdcard and ride side by side with your android system (you can use your phone at the same time)
IT DOES NOT EFFECT YOUR PHONE IN ANY WAY
wasnt shouting just wanted everyone to see
ioos said:
Is it still uploading? I really want to try this!
Click to expand...
Click to collapse
Download away!
This is awesome! I can't wait to get home and give it a try.
This is gonna be a great weekend. Between this and the flashable ROMs that are starting to roll out for my nook color, I might be sprouting antennae by Monday.
So wep cracking soon...? That's about the only thing I want/need Linux for.
Sent from the void...
wuclan48 said:
So wep cracking soon...? That's about the only thing I want/need Linux for.
Sent from the void...
Click to expand...
Click to collapse
How would one go about this "wep cracking thing"
please explain further
Almost* all WEP and some** WPA wireless passwords can be cracked. IMHO its easiest to do this on a Linux machine (please take note I love all OSs equally!)
*I forget how accurate this is but some WEP keys(like crazy long ones) can cause problems l in cracking, thus being protected (though not by design)
**most wpa specifications are not crackable yet and those that are often have a very stringent set of requirements (off the top of my head: most require someone to be legitimately connected to the access point and very simple passwords with low encryption.
On topic, though, this is sweet. Hope I can get something like this on my galaxy tab too!
EDIT: If you really need to know this (please only for testing... not to mooch people's internet) Google "wep cracking on backtrack"
The short simple answer is you sniff packets that the wireless access points send out and manipulate them to decrypt the key.
EDIT 2: I just realized you are also the guy who made this. Let me answer a few questions.
1) For audio you probably need to find a way to register the hardware with a Linux Audio Mixer. I'm guessing Ubuntu uses ALSA? I'd have to look that up
2) For users, kusers is part of the KDE desktop system. Ubuntu uses GNOME. People generally only use one or the other (unless they're trying to show off). That's probably why it either a) won't work or b) not work well and take up lots of extra space
3) It's Linux, not Lenux (but that's fine I can sense English isn't your first language... it's not mine either, but that's fine ^^)
the download has a "zipx" extension.
I did a little googling and it looks like that is winzips new default compression method, and the only way to open the archive is with winzip, bitzipper, pkzip, or a couple of others. none of the compression utilities I typically use (7zip on Windows, unarchiver on mac) seem to support it.
Edit: sorry if I sound unappreciative, I just think its funny to use a proprietary closed format for distribution of software that is all about open software and formats. I'm currently trying to find something that will open this on the mac without being a scummy trial, or ill just do it on a pc.
Sorry i just used the wizard and made a zip file with winzip 12.1
Quote"Almost* all WEP and some** WPA wireless passwords can be cracked. IMHO its easiest to do this on a Linux machine (please take note I love all OSs equally!)
*I forget how accurate this is but some WEP keys(like crazy long ones) can cause problems l in cracking, thus being protected (though not by design)"
Thanks for the info
laydros said:
the download has a "zipx" extension.
I did a little googling and it looks like that is winzips new default compression method, and the only way to open the archive is with winzip, bitzipper, pkzip, or a couple of others. none of the compression utilities I typically use (7zip on Windows, unarchiver on mac) seem to support it.
Edit: sorry if I sound unappreciative, I just think its funny to use a proprietary closed format for distribution of software that is all about open software and formats. I'm currently trying to find something that will open this on the mac without being a scummy trial, or ill just do it on a pc.
Click to expand...
Click to collapse
shame on me .
Your right im a noob and really know too much about it yet i just like having ubuntu on my phone.
Ill do better next time
People talking about cracking WEP and stuff, this probably doesn't have a driver to put the wireless card to put the card in monitor mode.
laydros said:
the download has a "zipx" extension.
I did a little googling and it looks like that is winzips new default compression method, and the only way to open the archive is with winzip, bitzipper, pkzip, or a couple of others. none of the compression utilities I typically use (7zip on Windows, unarchiver on mac) seem to support it.
Edit: sorry if I sound unappreciative, I just think its funny to use a proprietary closed format for distribution of software that is all about open software and formats. I'm currently trying to find something that will open this on the mac without being a scummy trial, or ill just do it on a pc.
Click to expand...
Click to collapse
Have the same problems, did you happen to find anything to open it with? I searched a little on google myself but all I find is software that needs to be purchased.
Homefix said:
Quote"Almost* all WEP and some** WPA wireless passwords can be cracked. IMHO its easiest to do this on a Linux machine (please take note I love all OSs equally!)
*I forget how accurate this is but some WEP keys(like crazy long ones) can cause problems l in cracking, thus being protected (though not by design)"
Thanks for the info
Click to expand...
Click to collapse
AFAIK, WEP can be easily cracked. WPA or WPA2 though, will require bruteforcing, there is no way around it.
corybucher said:
Have the same problems, did you happen to find anything to open it with? I searched a little on google myself but all I find is software that needs to be purchased.
Click to expand...
Click to collapse
I will repackage it, but it might take 3-4 hrs to upload, sorry.
ill get right on it
I have recently bought an Incredible S, and it is a great device, but I would like to gain root access for certain apps. The development forum is dead, I presume anyone with the knowledge and inclination as avoided this phone (and is waiting on the dual cores) so I decided to look for myself, but I am stuck. Either the people who usually discover root on these devices don't like documenting processes and methods, or I am loking in totally the wrong place. Can anyone give me pointers on where to start looking or where I can find info on where to start looking, or am I just barking up the wrong tree and sounding really thick?
Hey people,
I need to root my phone to.
I used z4mod and universal androot, both apps failed to root my phone.
So i hope someone succeed to root his or her incredible s, and post it here.
- Bert
unrevoked.com
just enable usb debugging, plug your phone into pc via usb, start unrevoked3 and wait. It will do all the work for you
There is no support for the HTC incredible S
i think there is a difrence between the HTC droid incredible and HTC incredible S,
so im not taking any risk trying to root my phone as an HTC droid incredible
vindicat said:
unrevoked.com
just enable usb debugging, plug your phone into pc via usb, start unrevoked3 and wait. It will do all the work for you
Click to expand...
Click to collapse
UnrEVOked does not support Inc S at the moment.
Sent from my HTC Incredible S using XDA Premium App
Alright, i'll try to make this simple, because i'm betting not a lot of people know what goes into rooting these devices.
Root is not like buried treasure. No X on a map. In fact, there is no map. We're not hitting up a command prompt on windows, crawling through thousands of bits to find the access codes so we can find the root the creators left for us.
Now that we know what it isn't, it's time to explain what it is.
Finding root is a lot like finding a back door... that's been painted to look like the rest of the outside wall... and all of its cracks sealed... and its doorknob non-existant. You'd have to look from the inside to know where it is, and even THEN you don't know if you can even OPEN the door from the outside.
What devs (or aspiring devs) attempt to do is look for the telltale signs that a phone software vendor has modified from the original stock AOSP. This means that the phone will be attempting to do something unique, something that vanilla android does not. TouchWiz, MotoBlur, etc are all examples of these.
Devs look through the changes, trying to find examples where vendors have hijacked root access (or system access) to perform a task. On Droid3, for example, we found a script that reinstalls stock sample games onto the phone. We attempted to shell-inject some code into a variable to install superuser into an executable directory. Unfortunately, the attempt failed.
In short, you're looking for signs that some root access is happening outside of vanilla android. After that, you need to find a way to hijack it. Checking files for executable permissions, finding out where files can be executed, etc are all examples of searching for root.
Your eventual goal will to be to get the su binary into an executable location. On the Droid3, this was /data/tmp, a temporary filesystem with executable permissions (but no write access for apps or shell.) Our goal was to use some exploit to push su into that directory and execute it. (We still have not achieved this.)
If you really want to learn the process that goes into rooting, check this thread out: http://forum.xda-developers.com/showthread.php?t=1193893
It is 60 pages of root theory where we are still [at time of post] attempting to gain root. We wade through our ideas, our attempts, our successes and our failures. (we have lots of those. )
Good luck, though i think you might be getting in over your head... I sure am already.
I have a Viewsonic G Tab that I flashed to Cyanogen 7. Now when I plug the device into my computer, it only reads the SD card I inserted (not the phone's internal memory). Plus, I can't use any file explorer programs to copy and paste from the SD card to the phone's memory. This is making things like flashing a different rom or adding the marketplace pretty much impossible. Any help? I'm new to rooting tabs, but I've hacked quite a few phones.
If there's a dev out there that has an answer that gets me up and running, I'd be more than happy to donate.
jskrenes said:
I have a Viewsonic G Tab that I flashed to Cyanogen 7. Now when I plug the device into my computer, it only reads the SD card I inserted (not the phone's internal memory). Plus, I can't use any file explorer programs to copy and paste from the SD card to the phone's memory. This is making things like flashing a different rom or adding the marketplace pretty much impossible. Any help? I'm new to rooting tabs, but I've hacked quite a few phones.
If there's a dev out there that has an answer that gets me up and running, I'd be more than happy to donate.
Click to expand...
Click to collapse
I have read other reports of this, though i don't have a solution for this problem, you could try something else.
When you are connected over usb, use adb from the android sdk and try "adb push file_on_computer file_on_device" to get some files on there.
Crap, I am not a programmer, and haven't gotten into using adb. I don't expect a full explanation of what adb is and how to get it and other android sdk stuff on my computer, as I know there are tons of posts and resources on this and other forums that will get me there.
jskrenes said:
Crap, I am not a programmer, and haven't gotten into using adb. I don't expect a full explanation of what adb is and how to get it and other android sdk stuff on my computer, as I know there are tons of posts and resources on this and other forums that will get me there.
Click to expand...
Click to collapse
Searching is always better , but i will give you some hints:
Download the SDK here
Install it.
Open the windows command prompt. (press windows button + R, type "cmd" , press enter)
If you installed it to "C:\android" go to "C:\android\platform-tools" inside the command prompt.
Type adb -h to see all available commands.
If you have further questions, google them, if you still have questions, come here and ask .
Cool, thanks. I bought this to try and save a few (hundred) bucks over the Xoom, and got the added bonus of getting to tweak it, which I kind of enjoy, I was just hoping to not have to learn this much stuff.
On a related note, if I get the device back to factory stock, do you know if I can download an app to my Android phone's SD card, drop the card into my Viewsonic, and load the apk from there? Loading the Android market on this thing sounds complicated (though it'll be child's play if I can bring it back to life).
jskrenes said:
Cool, thanks. I bought this to try and save a few (hundred) bucks over the Xoom, and got the added bonus of getting to tweak it, which I kind of enjoy, I was just hoping to not have to learn this much stuff.
On a related note, if I get the device back to factory stock, do you know if I can download an app to my Android phone's SD card, drop the card into my Viewsonic, and load the apk from there? Loading the Android market on this thing sounds complicated (though it'll be child's play if I can bring it back to life).
Click to expand...
Click to collapse
Well if you want tweaking you will have to learn a bit .
Depends on the app. If it is copyprotected or is using the licensing service i don't think you can copy it over.
Cyanogen came with a copy of ROM manager pre-installed on boot. A lot of features were limited to the full version, but I managed to do some reformatting and stuff (I wish I knew exactly what I did) and managed to get a different ROM installed and all seems to be working well.
I don't mind learning, but I either have to do it while I'm at work, which takes me off the sales floor, or at home, and I have a new kid to take care of, so the less learning I *have* to do, the better. But the nice thing about Android is that it is for the most part fairly resilient, and I've yet to encounter a software problem I couldn't fix.
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).