Related
This is DesignGear's aRoot script, edited to run on Mac OS X
Link to his original script: http://forum.xda-developers.com/showthread.php?t=981866
This has the same features as the Windows script.
- Root
- Installs tethering apn(enable the apn AFTER you enable mobile hotspot)
- Unlocks all APN's for editing
- Enables init.d support (on the android side, sample script mounts /system rw)
- Installs Superuser.apk
- Enables Non-market apps (sideloading)
- Installs su and sqlite3 binaries to /system/bin
- Removes oneclickroot busybox mess (if it exists)
- unRoot script
Instructions:
1) Download aRootMac.zip, then double click to decompress
2) Plug your Atrix in, with USB debugging enabled
3) run the aRoot program in the folder
Downloads:
http://www.mediafire.com/?gi2qpmj2j9uum9x (I have edited my script so that it will look for adb in whatever folder the script is in, rather than relying on the path)
http://www.mediafire.com/?o6ipy3e7rncncnn (tical2k's version of the script using tcsh rather than bash)
Notes:
- This script should hypothetically work on a Linux machine, but you may need to copy in adb from the Linux SDK
(I make no promises though, I have NOT tested this)
- When running this script during debugging, I noticed that unrooting and rerooting was creating duplicates of the tethering APN. If this causes issues, I can try and fix this in the script
Thank you's
To DG for the original aRoot script which is the base of this one, and also to everyone involved in Atrix development. I'm one of the many who have moved on, but I am cheering for you just as hard as ever!
Thanks man! I've been waiting on this.. I have Windows on my Mac but this makes life much easier
u my friend just made those of us with mac's life a little easier heh =)
Is it possible rooting will cause any updates from Moto to ATT to fail? Looks like we're getting some kind of update soon.
Sent from my non-rooted Atrix using XDA App.
jjm3175 said:
Is it possible rooting will cause any updates from Moto to ATT to fail? Looks like we're getting some kind of update soon.
Sent from my non-rooted Atrix using XDA App.
Click to expand...
Click to collapse
From what I understand it will only fail if you use root to remove certain apps (See this thread:http://forum.xda-developers.com/showthread.php?t=972459)
If it does turn out to be a problem there is an unroot script which will undo everything done by the aRoot script (minus remove the created tethering APN). If that fails, you can flash the retail SBF from here: http://forum.xda-developers.com/showthread.php?t=1003903, except note that this does need a windows machine as far as I know.
this ist working for me. I unzipped and plugged in the phone and put the USB debugging on. I started aroot and it says that everything installed fine, but my phone didnt reboot. Am i doing something wrong? This is on a Macbook pro intel
http://dev.gitbrew.org/~dasmoover/android/atrix/aRootMac.zip - mirror
Was this meant for me? Still the same problem
tomlee337 said:
this ist working for me. I unzipped and plugged in the phone and put the USB debugging on. I started aroot and it says that everything installed fine, but my phone didnt reboot. Am i doing something wrong? This is on a Macbook pro intel
Click to expand...
Click to collapse
I'm attaching a debug version of the script (prints out everything it does). Decompress the executable, copy it into the aRootMac folder, then run it. If it still doesn't work, PM me whatever the output from this script is, and I should be able to figure out what isn't working.
Let me know if anything's unclear
phoneixx said:
I'm attaching a debug version of the script (prints out everything it does). Decompress the executable, copy it into the aRootMac folder, then run it. If it still doesn't work, PM me whatever the output from this script is, and I should be able to figure out what isn't working.
Let me know if anything's unclear
Click to expand...
Click to collapse
Do you mean i have to run the whole this in a terminal window?
phoneixx said:
I'm attaching a debug version of the script (prints out everything it does). Decompress the executable, copy it into the aRootMac folder, then run it. If it still doesn't work, PM me whatever the output from this script is, and I should be able to figure out what isn't working.
Let me know if anything's unclear
Click to expand...
Click to collapse
Here is what it says when I run the arootdebug
Getting temporary root access...
./arootdebug: line 4: adb: command not found
./arootdebug: line 5: adb: command not found
./arootdebug: line 6: adb: command not found
Mounting /system as read/write ...
./arootdebug: line 10: adb: command not found
Cleaning up onclickroot mess ...
./arootdebug: line 13: adb: command not found
./arootdebug: line 14: adb: command not found
Rooting your device ...
./arootdebug: line 17: adb: command not found
./arootdebug: line 18: adb: command not found
Installing Superuser app ...
./arootdebug: line 21: adb: command not found
Installing sqlite3 ...
./arootdebug: line 24: adb: command not found
./arootdebug: line 25: adb: command not found
Enabling sideloading ...
./arootdebug: line 28: adb: command not found
Enabling tethering ...
./arootdebug: line 31: adb: command not found
./arootdebug: line 33: adb: command not found
Enabling init.d support ...
./arootdebug: line 36: adb: command not found
./arootdebug: line 37: adb: command not found
./arootdebug: line 38: adb: command not found
./arootdebug: line 39: adb: command not found
./arootdebug: line 40: adb: command not found
Rebooting ...
./arootdebug: line 43: adb: command not found
Press any key to continue...
Nevermind. Just used a PC. I'm not a experienced MAC user. I just use it for editing my photos.
Hay thanks for this even though i a linux guy, i still much perfer to windows
Sent from my GT-P1000
tomlee337 said:
Here is what it says when I run the arootdebug
Getting temporary root access...
./arootdebug: line 4: adb: command not found
./arootdebug: line 5: adb: command not found
./arootdebug: line 6: adb: command not found
""
""
""
Rebooting ...
./arootdebug: line 43: adb: command not found
Press any key to continue...
Click to expand...
Click to collapse
I get the same here... I really hope there's an easy solution to this as I'm looking forward to root. Does the storage settings have anything to do with this? I'm on motorola portal right now and when I connect I get "Motorola" disc icon with some .exe in there. Thanks for the help
Do you mean i have to run the whole this in a terminal window?
Click to expand...
Click to collapse
This shouldn't need to be run in a terminal, just copy it to the folder from the post on the first page, and click on it in finder.
Getting temporary root access...
./arootdebug: line 4: adb: command not found
./arootdebug: line 5: adb: command not found
./arootdebug: line 6: adb: command not found
""
""
""
Rebooting ...
./arootdebug: line 43: adb: command not found
Click to expand...
Click to collapse
Are you guys moving the debug executable into the folder original folder? It won't work correctly unless you run it in the same folder that you download from the first post.
phoneixx said:
This shouldn't need to be run in a terminal, just copy it to the folder from the post on the first page, and click on it in finder.
Are you guys moving the debug executable into the folder original folder? It won't work correctly unless you run it in the same folder that you download from the first post.
Click to expand...
Click to collapse
I was running it from the same folder that i unzipped it to.
tomlee337 said:
I was running it from the same folder that i unzipped it to.
Click to expand...
Click to collapse
Copy the unzipped file to the aRootMac folder, otherwise it won't be able to find the adb, hence the output your getting
Sent from my Liberty using XDA App
phoneixx said:
Copy the unzipped file to the aRootMac folder, otherwise it won't be able to find the adb, hence the output your getting
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
I know my way around adb fairly well... so I was kinda surprised by this. If this makes any difference I'm on a Bell Atrix and I have it unlocked to Fido. I unzip aroot and unzip the debug and then take the debug file and drop it in the aroot folder... then I ran the aroot again it comes up with all the lines properly except much too fast and then says rebooting but the phone is unaffected. I then run the debug file and it came up with those "adb command not found" so I'm pretty much stumped. Thanks for the help guys.
ChongoDroid said:
I know my way around adb fairly well... so I was kinda surprised by this. If this makes any difference I'm on a Bell Atrix and I have it unlocked to Fido. I unzip aroot and unzip the debug and then take the debug file and drop it in the aroot folder... then I ran the aroot again it comes up with all the lines properly except much too fast and then says rebooting but the phone is unaffected. I then run the debug file and it came up with those "adb command not found" so I'm pretty much stumped. Thanks for the help guys.
Click to expand...
Click to collapse
Yeah, I don't think this works presently. I lost my finger print reader functionality after using this (which ran really fast as noted). I fixed it by running aRoot on windows.
OK... so everything was good as bash EXCEPT there is NO idea how Mac's bash shell gets it's relative path (thought it was a $0 or $1 but nope). So here is a converted csh environment script (tcsh more specifically) where $0 gives the full script name and path.
Anyway the scripts have changed the name of the aRoot file to run_aRoot. This is important. DO NOT CHANGE THIS NAME! This is a hackish way to resolve the relative path with sed. I have NO IDEA why the `pwd` is not returning the correct path, but anyway, it is what it is.
Currently the scripts don't mask any output (for better debugging). This HAS been tested unroot/root works. I bet there'll be a new one out to convert soon. Oh well give it a whirl. All work is DG and OP's, just a different implementation here. The usual disclaimer's apply. Attempt at your for own risk, I have no responsibility for damages mental or physical, et al. A side note, right click either run_aRoot or unRoot and open with TextEditor if you want to see what's going on.
http://www.mediafire.com/?o6ipy3e7rncncnn
Solved:
thanks to a good friend of mine he directed me to this file on GRP dev-site
http://greenromproject.com/showthread.php?269-ADB-The-Easier-Way
open this file in ubuntu software manager, let the package install and reboot system, then adb should work in any directory
Original Post:
ok guys i really didn't want to do this... i followed over 6 different guides now and am getting confused.. there too many methods and they all do not work.... i keep getting .../adb no such file or directory
i spent the last 2 days trying to set up adb on my 10.10 ubuntu, 64-bit system... i edited the bashrc file with the correct path, even typed it in myself because of known issues with ' " ' those things.. i also made the 71-android.rules file with about 3 different variations of this
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
reboot the system, i ran adb kill-server and sudo adb start-server and im still getting message saying .../adb no such file or directory...
only thing i can think of to cause an issue is i updated the system, (not upgrade to 11.04) only update!! installed java jdk and all the needed parts for compiling roms... but just cant seem to get adb working
has anyone else had this type of issue or know how to solve it...? sdk version r12
please someone help
Click to expand...
Click to collapse
...
i keep getting .../adb no such file or directory
...
Click to expand...
Click to collapse
If you get this message, there is no need to look for autoconfig rules or something else, you need to check your path. Try to type
Code:
which adb
if adb cannot be found, you should do a
Code:
export PATH=$PATH:<path to your adb directory>
after that you should be fine for starting adb. If you would like to have it in your path permanently, you shoud add the line above to you .profile file in your home directory.
yeah i already did all that... added the correct path and everything... i tried all these diff methods and none worked, and none were even close to the same as far as what to add to bashrc and the rules.. but i got the issue solved thanks to a file i installed via update manager... rebooted system and adb worked fine
Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
Its stable & works 100%
I personally have not lost root with this method in over 48 hours.
Zero com.noshufou.android.su crashes.
Before Using!!
HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
Restart your phone!
Lastly, if you're getting com.noshufou.android.su force close errors
Uninstall superuser prior to running scripts.
If you Lose Root, all you have to do is open Terminal Emulator & type fixsu
No More Rebooting & running the exploit again for R/W on system to get Root back in place!
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal and type fixsu to get root back.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot.
Q. Can I push & remove items to system and will it work?
A. Yes, but all changes are reset on a reboot.
~~~~~~~~~
For Mac/Linux users
Once downloaded, extract vividtemproot.zip to your home/root folder.
(Typically named after your login, has a house icon in Finder's sidebar of places)
Open folder vividtemproot, double-click run_me_mac (or run_me_linux)
and thats is all!
Click here to download for Mac/Linux
(Updated 11/14 - 23:50)
~~~~~~~~~
For Windows Users
Once downloaded, extract where ever you please.
Double click _RUN_ME
and enjoy!
Click here to download for Windows
(Updated 11/14 - 23:50)
Link for Windows is the Mac file...
CharlieMurphyIVXX said:
Link for Windows is the Mac file...
Click to expand...
Click to collapse
Thank you :]
Fixed
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
thecubed said:
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
Click to expand...
Click to collapse
I haven't lost root in going on ~60 hours, as as a newbie here, you definitely know far more than I do!
As you'll see in the fixsu, I redundantly copy su from /vendor/bin
to /system/xbin/ from which I hardlink (as you'd know is virtually the same as bind mounting in this case) to /system/bin
I added the fixsu, as a last resort, in case the something would dissolve, but unless someone really fudges something up, the fixsu shouldn't be needed
As my programming teacher once told me: the code doesn't need to be pretty as long as it works.
And through that philosophy I've used a lot of redundancies, that may or may not need to be there,
but they'll definitely keep anyone from having any sort of issues using the scripts!
P.S. Thank you :]
Thanks, I'll try this out and report back.
Sent from my HTC PH39100 using xda premium
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
The device rebooted itself -- the "root" is lost
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
rinnycoop121 said:
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
Click to expand...
Click to collapse
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
drewdatrip said:
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
Click to expand...
Click to collapse
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
3f62011 said:
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
Click to expand...
Click to collapse
I don't own a Windows box, an had to write the Windows bat file
without giving it a test run for errors.
I'm sure I did mess up the syntax, an probably left some command that isn't windows relavent at the end of the script.
No worries, you've got root, and shouldn't loose it.
bjg222 said:
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
Click to expand...
Click to collapse
I tried to pipe all errors out to null, as I took a mash up of your code, my code, and and another guys code, and left a lot of "in case it exists" type of lines in the code, to make sure no one would have any issues.
Apparently I didn't pipe it all to null well enough
The mac/linux version you only see 'starting' and 'finished' haha
rpendrick said:
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
Click to expand...
Click to collapse
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
drewdatrip said:
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
rpendrick said:
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
Click to expand...
Click to collapse
Yes, works much better with something in the folder.
Scrog said:
Yes, works much better with something in the folder.
Click to expand...
Click to collapse
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I was able to update superuser, but titanium back up doesn't see either SD card.
drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Superuser crashes when it is the lastest versions.
Do a google search for superuser.apk 3.0
I thought I included it in the package, but perhaps, once again in a rush
fudged that up too...
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
RealBorg said:
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
Click to expand...
Click to collapse
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Sorry for bad English
johnnybr said:
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Click to expand...
Click to collapse
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
/bin/su is the location of the su binary on every Unix system and Superuser also installs the su binary to /system/bin/su. I wonder if it would make a difference (avoid instability) to place it in /system/xbin/su.
Tom
RealBorg said:
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
Click to expand...
Click to collapse
I really suspected that, like you said, part of all that stuff was unnecessary.
About the place of su binary, well, I just wanna to help. I don't know nothing about linux and less of unix. But normally, while you are dealing with this kind of stuff, you should try. Cause things sometimes work when they shouldn't and don't work like they should. I can only say: God knows why...:silly:
Thread moved to General section, post in the relevant section next time.
Why use Heimdall to flash ? Odin3 works better
"None forget the bite.....of Viper...."
CallMeVentus said:
Why use Heimdall to flash ? Odin3 works better
Click to expand...
Click to collapse
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
RealBorg said:
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
Click to expand...
Click to collapse
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
johnnybr said:
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
Click to expand...
Click to collapse
Seriously?
How can hemidall work on windows when its designed for linux!
Sent from my GT-I9070 using xda premium
Shaaan said:
Seriously?
How can hemidall work on windows when its designed for linux!
Click to expand...
Click to collapse
Actually it has a windows version. Even Mac has a version of Heimdall. Take a look: http://www.glassechidna.com.au/products/heimdall/
Indeed I can't make it work... Perhaps on windows x86 it can work...
Hello folks!
Its been a while since i posted here - i havent been flashing roms for an age (kids etc got in the way!)
Anyway, i've picked up a Pixel 4 XL, and it was running a custom ROM, i'm trying to move back to stock and have been able to follow all the guides i've found up to using the 'fastboot flashall' in shell.
The command works and delivers the
Bootloader Version...:
Baseband Version.....:
Serial Number........:
values, but then errors out with the following error "fastboot: error: ANDROID_PRODUCT_OUT not set"
I'm stumped what that means and how to fix. I'm doing all of this on my Pixelbook, and have updated fastboot and adb as per the initial steps for flashing.
Can anyone shed any light on what i still need to do to get flashall to work as expected?
Thanks in advance if you are able to help out!
ptm
Welcome Back
Could you post the exact command you are using for fastboot flash please? It sounds like fastboot is not finding the files to flash. Usually, depending on the configuration of the fastboot install, it's easier to place the firmware in the same directory as the fastboot binary.
Thanks! It turns out i've missed this place!
So the firmware files are all on the chromebook and I've used 'shell' to navigate to where I've unzipped. Here's the command line with the command i'm using: "[email protected] ~/Downloads/ota_file $ fastboot flashall"
Before trying a full flash, i was trying to sideload the OTA as per instructions here https://developers.google.com/android/ota#instructions but moving the file from my pixelbook to the 4XL fails at 47% every time.
So i reverted to a full flash as per these instructions - https://developers.google.com/android/images and that is where i'm coming a cropper with the 'not set' error.
Thanks for your help!
ktmom said:
Welcome Back
Could you post the exact command you are using for fastboot flash please? It sounds like fastboot is not finding the files to flash. Usually, depending on the configuration of the fastboot install, it's easier to place the firmware in the same directory as the fastboot binary.
Click to expand...
Click to collapse
I thinnk you may be merging several approaches.
You are using the full factory image downloaded from the https://developers.google.com/android/images page, right? Then, once downloaded, you are unzipping the file and cd into the new directory (from the unzip). The command then should be
Code:
./flash-all.sh
As far as the OTA install is concerned, you are using the command
Code:
adb sideload "ota_file.zip"
, and at 47%, what happens that it appears to fail? My memory on my P3XL is at that point it takes awhile.
If you are using a C to C switch to an A to C cable and try it. You'll want to remove the wipe from the flash-all before you flash the full image and it's the flash all you should be using to flash.
Yeah i think you're right - so now just concentrating on the Full Flash method shown on the Google Developers page, and yes doing it exactly as you'd described.
Ok - using
Code:
./flash-all.sh
now returns the error
Code:
bash: ./flash-all.sh: Permission denied
I have tried to prefix './flash-all.sh' with 'Fastboot' but no dice here either. Is that required at all?
ktmom said:
I thinnk you may be merging several approaches.
You are using the full factory image downloaded from the https://developers.google.com/android/images page, right? Then, once downloaded, you are unzipping the file and cd into the new directory (from the unzip). The command then should be
Code:
./flash-all.sh
As far as the OTA install is concerned, you are using the command
Code:
adb sideload "ota_file.zip"
, and at 47%, what happens that it appears to fail? My memory on my P3XL is at that point it takes awhile.
Click to expand...
Click to collapse
ptm said:
Yeah i think you're right - so now just concentrating on the Full Flash method shown on the Google Developers page, and yes doing it exactly as you'd described.
Ok - using
Code:
./flash-all.sh
now returns the error
Code:
bash: ./flash-all.sh: Permission denied
I have tried to prefix './flash-all.sh' with 'Fastboot' but no dice here either. Is that required at all?
Click to expand...
Click to collapse
You need to give the "flash-all.sh" script execution rights (that is why the permission denied error). Use this code:
Code:
chmod +x ./flash-all.sh
You may need super user/root rights:
Code:
sudo chmod +x ./flash-all.sh
The "flash-all.sh" script is a stand-alone script that sequentially flashes the entire factory package. As was mentioned in another repsonse in this thread, in cases where you want to update, but not lose your installed user apps and data, you would edit the script and remove the "-w" augment. In this case, you are returning to stock and you should perform the wipe (-w).
The dot slash (./) that preceeds the flash-all.sh tells the bash interpreter (what runs commands you give) that the file is right here, in this directory.
The flash-all.sh is a standalone script (series of written instructions) and calls fastboot from within it.
Thanks for sticking with me on this ktmom!
OK, i've used both
Code:
chmod +x ./flash-all.sh
and
Code:
sudo chmod +x ./flash-all.sh
but still getting the permission denied error when i launch ./flash-all.sh
I'll do a screencast vid walking through the entire process i'm following, so that you can see what i'm up too and in case it gives any further clues for a solution.
Thanks again!
ktmom said:
You need to give the "flash-all.sh" script execution rights (that is why the permission denied error). Use this code:
Code:
chmod +x ./flash-all.sh
You may need super user/root rights:
Code:
sudo chmod +x ./flash-all.sh
The "flash-all.sh" script is a stand-alone script that sequentially flashes the entire factory package. As was mentioned in another repsonse in this thread, in cases where you want to update, but not lose your installed user apps and data, you would edit the script and remove the "-w" augment. In this case, you are returning to stock and you should perform the wipe (-w).
The dot slash (./) that preceeds the flash-all.sh tells the bash interpreter (what runs commands you give) that the file is right here, in this directory.
The flash-all.sh is a standalone script (series of written instructions) and calls fastboot from within it.
Click to expand...
Click to collapse
@ptm, No worries, I'll do my best to help. I'm typing this on a chromebook that I also use to fastboot to a P3XL.
Edit 1:
Just to make sure:
1) The bootloader is unlocked?
2) "fastboot devices" returns the serial number of your device?
3) you are running ./flash-all.sh command as root or as the default user? In other words, the same way that fastboot devices returns the serial number. Either sudo fastboot devices or just fastboot devices.
4) if you enter the linux command: ls -al flash-all.sh do you get something like:
-rwxr-xr-x. 1 chronos chronos 957 Jul 18 2019 flash-all.sh
In this example -rwxr-xr-x is depicting the file permissions where there are three groupings; owner group everyone else. The first rwx means read, write and execute permissions for the file owner. Others in the same group and everyone else has read and execute permissions. Execute (x) is required in order for a script to run. If your file does not have three x so that all three groups have permission to execute it, then we need to revisit that.
Edit 2:
Another thought that could be affecting you is ADB and Fastboot are old. in your crosh shell, type:
Code:
[email protected] ~ $ adb --version
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
[email protected] ~ $ fastboot --version
fastboot version 29.0.5-5949299
Installed as /usr/local/bin/fastboot
If either returns a version older than the output above, then the easy way to update these is to use the script on Nathan Chance's Githuib. This might look a little overwhelming but it's pretty easy. I suggest you read the page, but the operative information is in section 4. Run the setup script:
To install, run
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
in your shell prompt.
This script very nicely updates your ADB/Fastboot to the newest version which will be required for your P4XL
Are you guys sure you aren't making it too hard? You don't have to give any commands to install the full image. Download the full image and put it into an empty folder, go ahead and extract it in that folder. Create another new folder, Copy everything into it so you still have the full image in the first folder. Now download the tools and put those into a folder and extract them in that folder. Take the entire contents of that folder and add it to the folder you copied the extracted image into. What you should have now is one folder that still has the full extracted image, one that has the full extracted tools, and one that has both. If you have not already done so the phone should have debugging enabled and oem should be on. Go ahead and put it into bootloader mode and plug it in, type cmd in the path bar of the folder with both tools and image and check devices which will tell you if the tools can see the phone. If you get your serial the tools can see the phone. If you're going to wipe you can go ahead and click the flash-all and it will start the process, you do not give any commands. If you don't want to wipe the edit the flash-all to remove the-w, save it, and click on it. Again, no command is given, you just click and the flash-all does the rest.
Edit... And dont forget, A to C, not the provided C to C.
krabman said:
Are you guys sure you aren't making it too hard? You don't have to give any commands to install the full image. Download the full image and put it into an empty folder, go ahead and extract it in that folder. Create another new folder, Copy everything into it so you still have the full image in the first folder. Now download the tools and put those into a folder and extract them in that folder. Take the entire contents of that folder and add it to the folder you copied the extracted image into. What you should have now is one folder that still has the full extracted image, one that has the full extracted tools, and one that has both. If you have not already done so the phone should have debugging enabled and oem should be on. Go ahead and put it into bootloader mode and plug it in, type cmd in the path bar of the folder with both tools and image and check devices which will tell you if the tools can see the phone. If you get your serial the tools can see the phone. If you're going to wipe you can go ahead and click the flash-all and it will start the process, you do not give any commands. If you don't want to wipe the edit the flash-all to remove the-w, save it, and click on it. Again, no command is given, you just click and the flash-all does the rest.
Edit... And dont forget, A to C, not the provided C to C.
Click to expand...
Click to collapse
What Tools do you need to do this?
Same page as the images, scroll up from them and in the description of the process they have a link to the platform tools.
@krabman, Since this is using a chromebook, not a PC, things are flakier than normal. I just replicated the problems experienced by @ptm and some of it is due to old ADB/Fastboot as described in my previous post. Some is because ChromeOS made a change in an update that mounts nearly all of the partitions noexec, which means scripts can not execute and give the reported, "no permissions" error. There is a workaround since /usr/local is mounted executable. It's also possible to remount a partition with exec permissions.
@ptm, as the easiest route, I suggest making sure the ABD is current using the script I linked yesterday, and then going back to the OTA sideload method. I tanked my phone for a few hours yesterday trying to make fastboot get through the entire system image. I finally resorted to my full ubuntu install on my chromebook.
airmaxx23 said:
What Tools do you need to do this?
Click to expand...
Click to collapse
A general Fastboot/ADB tutorial is available here. If you are not using a chromebook, this thread's discussion will just add confusion.
If you are using a chromebook, then you need to enter a crosh shell, make sure adb and fastboot are updated as described in an earlier post and read the rest of the information I posted about the associated problems.
My understanding is the sh should flash on chrome with the latest tools as I described and you use the bat for PC. If the device is down he would have nothing to lose trying, if not I'd be leery of trying it since a partial flash will definitely result in a softie. Of course the possibility that I don't fully understand it may explain my puzzlement.
ktmom said:
A general Fastboot/ADB tutorial is available here. If you are not using a chromebook, this thread's discussion will just add confusion.
If you are using a chromebook, then you need to enter a crosh shell, make sure adb and fastboot are updated as described in an earlier post and read the rest of the information I posted about the associated problems.
Click to expand...
Click to collapse
Thanks, I know how to use ADB on the PC but I have a ChromeBook that I'd like to use as well. I already have it in Developer Mode.
I got it working, I just to run the script to update ADB and Fastboot.
airmaxx23 said:
Thanks, I know how to use ADB on the PC but I have a ChromeBook that I'd like to use as well. I already have it in Developer Mode.
When I open a Crosh Window, type shell, then adb devices my Pixel 4 XL shows up but I get: no permissions; see [http://developer.android.com/tools/device.html]
Click to expand...
Click to collapse
My bet is your ADB/fastboot are to old. Go back to post 9 and read the lower portion under edit2. You should also read forward from that point as there are additional issues that ChromeOS introduced with the noexec mounting of partitions. It will mean that without a workaround, you can not execute the flash-all.sh.
ktmom said:
My bet is your ADB/fastboot are to old. Go back to post 9 and read the lower portion under edit2. You should also read forward from that point as there are additional issues that ChromeOS introduced with the noexec mounting of partitions. It will mean that without a workaround, you can not execute the flash-all.sh.
Click to expand...
Click to collapse
Hey there,
SO i decided to try the OTA sideload method on a friends PC - i got the following response through CMD prompt
Code:
C:\Users\LYALL\Downloads>adb sideload ota-file.zip
Total xfer: 1.00x 1
However the phone is reporting a failure verifying the file signature and giving
Code:
E: Error code: 21
What do you think is causing that? I saw that Google has a new browser based flash tool to allow for AOSP builds to flash - would using that work better for me do you think?
ptm
ptm said:
Hey there,
SO i decided to try the OTA sideload method on a friends PC - i got the following response through CMD prompt
Code:
C:\Users\LYALL\Downloads>adb sideload ota-file.zip
Total xfer: 1.00x 1
However the phone is reporting a failure verifying the file signature and giving
Code:
E: Error code: 21
What do you think is causing that? I saw that Google has a new browser based flash tool to allow for AOSP builds to flash - would using that work better for me do you think?
ptm
Click to expand...
Click to collapse
Make sure you have downloaded the correct OTA and for crosshatch coral. Use the sha256 checksum provided in the download page and ensure the file is not corrupted. I check the integrity of the file before using it especially if I've moved it since the last verification.
You are rebooting to recovery (not rescue mode) and using the OTA sideload action from *within* recovery, before using the adb command, right?
The Google update and repair tool is an option.
ktmom said:
Make sure you have downloaded the correct OTA and for crosshatch. Use the sha256 checksum provided in the download page and ensure the file is not corrupted. I check the integrity of the file before using it especially if I've moved it since the last verification.
You are rebooting to recovery (not rescue mode) and using the OTA sideload action from *within* recovery, before using the adb command, right?
The Google update and repair tool is an option.
Click to expand...
Click to collapse
I think Pixel 4 XL is Coral, not Crosshatch.
I have downloaded the OTA file thats third from the bottom on this page (https://developers.google.com/android/ota) which is the rom number - 10.0.0 (QQ1B.200105.004, Jan 2020).
Yes, followed the instructions and booted to recovery, selected 'update from adb' from within recovery and then checked
Code:
adb devices
to ensure it showed 'sideload'. I then ran the command
Code:
adb sideload ota_file.zip
The transfer seemed to work fine, but then i got the error above showing on the device.
I cant seem to use the Google update and repair tool, as I'm in the UK and it says its not supported.
I can get it working with a VPN but the carrier i'm on doesnt show, although i do have the option of selecting 'other' as the carrier - I'm happy to give that a go, but wanted to get your thoughts on it first. Will selecting carrier as 'other' work ok for a UK based phone?
ptm