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
Related
1) I just got Ubuntu on my computer. How do I use adb on it? I have already put the file in that udev folder and debugging is on already. What files do I need and what do I run in terminal?
2) Adb&fastboot do not work for me anymore. It always says "waiting for device" but nothing happens
3) Are there any alternates to applying your nandroid backups other than fastboot?
4) I just got LucidREM's new JFv1.51 but whenever I receive a call my phone vibrates then just loses all connection and has me input my 4 digit sim card key to unlock it. Anyone else get this problem?
5) What is the latest system recovery utility build? Mine is JFv1.42
First, make sure you have set up the adb compatibility for your distribution:
http://telyas.com/wordpress2/2009/04/29/ubuntu-jaunty-and-android-adb/
Note this is for jaunty.
do you have the android SDK? you need to download it, then run adb from the tools folder, or add it to your .bashrc profile so that you can type "adb" from anywhere.
http://developer.android.com/sdk/download.html?v=android-sdk-linux_x86-1.5_r2.zip
http://developer.android.com/sdk/1.5_r2/installing.html
There are no "image all" alternates to fastboot. If you need a compiled for linux fastboot (32 bit), here:
http://yochai.dyndns.org:8888/android/fastboot
I can't help you with the last one.
yochaigal said:
First, make sure you have set up the adb compatibility for your distribution:
http://telyas.com/wordpress2/2009/04/29/ubuntu-jaunty-and-android-adb/
Note this is for jaunty.
do you have the android SDK? you need to download it, then run adb from the tools folder, or add it to your .bashrc profile so that you can type "adb" from anywhere.
http://developer.android.com/sdk/download.html?v=android-sdk-linux_x86-1.5_r2.zip
http://developer.android.com/sdk/1.5_r2/installing.html
There are no "image all" alternates to fastboot. If you need a compiled for linux fastboot (32 bit), here:
http://yochai.dyndns.org:8888/android/fastboot
I can't help you with the last one.
Click to expand...
Click to collapse
So I installed the adb. It is in /android/tools/
How do I get to it
either use
Code:
cd /android/tools
./adb devices
or
Code:
sudo cp /android/tools/adb /usr/bin/adb
adb devices
either one will work. if you use the second one you can use adb from any directory. Also the latest recovery image for the G1 is 1.43 but i still use 1.42 since i don't think there is a differnce
tubaking182 said:
either use
Code:
cd /android/tools
./adb devices
or
Code:
sudo cp /android/tools/adb /usr/bin/adb
adb devices
either one will work. if you use the second one you can use adb from any directory. Also the latest recovery image for the G1 is 1.43 but i still use 1.42 since i don't think there is a differnce
Click to expand...
Click to collapse
Thanks ill try that out later.
Also, how can I restore my boot.img, system.img, data.img without fastboot?
Abolfazl said:
Thanks ill try that out later.
Also, how can I restore my boot.img, system.img, data.img without fastboot?
Click to expand...
Click to collapse
you can't
tubaking182 said:
you can't
Click to expand...
Click to collapse
Ok I have fastboot and I put it in /android/tools
I did sudo cp /android/tools/fastboot /usr/bin/fastboot
But when I run "fastboot" I get "bash: /usr/bin/fastboot: Permission denied"
Any help?
Abolfazl said:
Ok I have fastboot and I put it in /android/tools
I did sudo cp /android/tools/fastboot /usr/bin/fastboot
But when I run "fastboot" I get "bash: /usr/bin/fastboot: Permission denied"
Any help?
Click to expand...
Click to collapse
use: sudo fastboot
korndub said:
use: sudo fastboot
Click to expand...
Click to collapse
sudo: fastboot: command not found
Fastboot is in /usr/bin :\
use the path
either try specifying the full path to fastboot in your sudo command, or ensure that sudo is installed, which should obtain, since Ubuntu installs it by default
arqueware said:
either try specifying the full path to fastboot in your sudo command, or ensure that sudo is installed, which should obtain, since Ubuntu installs it by default
Click to expand...
Click to collapse
Alright I got fastboot working.
Now my only problem is that whenever I use fastboot to restore the 3 .img's my phone just goes to the android image and it keeps on cycling the boot
Fixed the typo's in the code, thanks to Contempt4You for pointing it out for me.
Note, i had to remove the links due to the restrictions of being a new user, but the tools can be found fairly easily, you will need the revert.zip that contains flash_image and mtd0.img, the evo-root.zip from the how to root android 2.2 on the evo 4g on this forums and all you need is the rageagainstthecage-arm5.bin, and an original PB31IMG.zip from the RUU 2.1
I adapted this guide from these instructions
As always, I have no responsibility when you try this things go really foobar, and you have a nice paper weight.
I am going to copy and paste much of the instructions off of the page above, make the changes specific to the DInc, and will try to update the links for the stuff to download as I can. Everything that is needed is already hosted somewhere on the internet.
Make sure your phone is unplugged from your computer until I tell you to plug it in!
If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.40
Run the installer. Move on once installed. If reboot is required, do so and then move on.
Windows 7 Users:
Go to your start menu, then control panel. When that is open, (if you are in category view mode) click on "Uninstall a program" and then choose HTC Sync to uninstall. If you are in Icon view mode choose "Programs and Features" and then click on HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Other Windows Version Users:
Go to your start menu, then control panel. When that is open, select Add/Remove Programs, and then choose HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
next download
It contains a few files necessary to root the DInc.
Unzip the contents of the zip to your android sdk tools folder.
Also download the original 2.1 PB31IMG.zip file, or is a download link to the RUU 2.1.
Put this zip in your sdk tools folder as well, as a zip, not extracted.
After unzipping the contents of revert.zip to your android sdk tools folder and placing the PC31IMG.zip move on.
Step 4: Make sure USB Debugging is ON (checked) on your EVO. Go to Settings > Applications > Development > and make sure it is checked.
Step 5: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now.
Step 6: Open up a command promt from your android-sdk/tools folder.
Windows 7 users:
Open up the android sdk folder and hold shift and right click on the tools folder. You will see an option that says "Open command window here" Choose that one and you will be set. the command prompt should read something like C:\android-sdk-windows\tools>
Other Windows Version Users:
Go to the start menu, go to All Programs, then Accessories, and click on command prompt. Once open type
Code:
cd C:\android-sdk-windows\tools
Once ready, type these commands in cmd prompt from your adb tools directory. After every line press enter.
Code:
adb push unrevoked-forever.zip /sdcard/
adb push flash_image /data/local/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb push mtd0.img /sdcard/
adb push PB31IMG.zip /sdcard/
Note: the PB31IMG.zip will take longer than expected to transfer to the sdcard. It is a BIG file.
Now we chmod a few things. After every line press enter. It should repeat what you typed in and then return you to a blank line with an $ for everything in adb shell
Code:
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
Ok now for the root shell.
*
(still in adb shell)
Code:
cd /data/local/tmp
./rageagainstthecage-arm5.bin
You will now see some text on your cmd prompt screen explaining the exploit.
Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this:
C:\android-sdk-windows\tools>
Once that dumps you out of the shell, type
Code:
adb shell
and you will see you now have a
Code:
#
instead of a
Code:
$
now type
Code:
cd /data/local
./flash_image misc /sdcard/mtd0.img
that will flash your misc partition with Toast's mtd-eng.img.
This should return you to a blank line with #.
If you get an "Out of memory error" with a huge list of weird lines, here's how to fix it.
Reboot your phone normally.
Open a command prompt and go backwards in this guide until you see the big red * and start from there.
Once it is flashed correctly, move on:
Type
Code:
reboot bootloader
Remember how you pushed that huge PB31IMG.zip to your sdcard earlier? This is where that comes in handy. Once you booted into hboot, Select "bootloader" with your volume up/down buttons and hit the power button. Let it sit for a little bit while it loads the PB31IMG.zip. This can take up to 5 minutes. When it finally asks if you want to apply this zip, choose YES. (Remember, this is the same as running an RUU, so it will delete all of your user data).
Once it is finished, select restart. You now are on the stock 2.1 build of Android.
From here you can root your phone and do unrevoked forever and what not for the people that updated to 2.2 without being s=off
Confirmed Works.
Thank You So much
I have been tyring to find a way to do this all day...works perfectly...took a little effort to find the files but overall great right up....
If someone who has enough post wants to post the links to the files, please do.
Sent from my ADR6300 using XDA App
well really all you have to do now is flash a original PB31IMG.zip in HBOOT if you have s-off which you should if you're hacking in the first place.
borgey420 said:
well really all you have to do now is flash a original PB31IMG.zip in HBOOT if you have s-off which you should if you're hacking in the first place.
Click to expand...
Click to collapse
Don't you think the whole point of his post was for people who didn't do S-OFF and did the latest leaked RUU and are stuck now because they fail to read.
Yeah, that is what this guide is about is for the people who were not s-off. At the time I did the ruu update I didn't feel comfortable doing s-off and then I learned about it, felt better, but then it was too late, I already updated to froyo. This is how I solved that problem so I could s-off my phone after the update.
Sent from my ADR6300 using XDA App
nice man so this is for people who didn't do s-off before doing the 2.2 RUU and can now go back to 2.1 so essentially they could now s-off to get root for 2.2? great work, bro!
** would this work for new phones, or say a refurb that came with 2.2 already, and unrevoked hasn't come out with a new root method yet, so you could use this method to get back to 2.1, s-off, then ota to 2.2 and attain root. even better.
excellent post assuming it works
lots of people will want this if they need to root now.
In theory it should work, I don't see why it wouldn't. I don't have one that came with 2.2 so I don't know for sure.
Sent from my ADR6300 using XDA App
Confirmed this is working. Some typos in the writeup but that's easily fixed once you catch it.
zeiroe said:
Confirmed this is working. Some typos in the writeup but that's easily fixed once you catch it.
Click to expand...
Click to collapse
I took a quick glance at this and stopped because right away I noticed errors and didn't wanna screw anything up. Glad to see it works, thanks.
here you go!
Android SDK
HTC Sync 2.0.40
revert.zip that contains flash_image and mtd0.img
the evo-root.zip contains rageagainstthecage-arm5.bin
original PB31IMG.zip from the RUU 2.1 or if you prefer rapishare, here you go
I believe he used this guide
sorry if this is a stupid question, but to confirm, does this process downgrade the radio too? The radio is what worries me the most, and presumably because the 2.15 radio was in the RUU, this process would downgrade it back to 1.x? Is it contained in the PCI...zip file? thanks all (used the RUU and now don't have any sound from internal speaker, trying to get back)
If you will send me a PM with what typos I made, I will fix them. I am currently in AIT with the guard and don't have much time. The code should be correct, I believe the typos is where I wrote it up, and then had to remove the links because of the forums restriction of posting links when you are new.
Yes, this does downgrade the radio too. You are making your phone exactly like it came originally.
Thank you so much for posting he links.
Sent from my ADR6300 using XDA App
I'm getting permission denied errors
Code:
C:\android-sdk-windows\tools>adb push mtd0.img /sdcard/
failed to copy 'mtd0.img' to '/sdcard//mtd0.img': Permission denied
what am I doing right?
edit: nevermind....figured it out....my SD card wasn't mounted on my phone
im doing this now. i hope i do everything right. i will post
Hey smwoodward, I hope you don't mind but I posted a reiteration of your guide on my blog. I see this being needed in the future for the new DInc's that will come with flavor of 2.2 out the box.
zeiroe said:
Hey smwoodward, I hope you don't mind but I posted a reiteration of your guide on my blog. I see this being needed in the future for the new DInc's that will come with flavor of 2.2 out the box.
Click to expand...
Click to collapse
No dude, 100% cool with me.
Sent from my ADR6300 using XDA App
what am I doing wrong?
I followed directions step by step and I get it all done correct, but when it comes to loading the image off of the SDcard onto the phone in HBoot, I get error message "no image or wrong image"
HELP PLEASE!!!
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
Hey guys, it took me 3 whole days to find the right way to downgrade.
Note: This is to be done at your own risk; I am not responsible for any damage or harm caused by this process.
Note: Information in this guide is taken from the works of following Authors:
1. wag3slav3: (http://forum.xda-developers.com/showthread.php?t=725430)
2. Paul (http://android.modaco.com/content/ht...rom-froyo-ota/)
3. TheDeadCpu: (http://forum.xda-developers.com/showthread.php?t=746454)
Please Follow the Instructions Carefully; to ensure success!
Items Required:
1. HTC Legend
2. 1 MicroSD Card (Gold Card)
3. 1 Micro USB Cable
4. Full Charge Recommended
5. Windows OS (I used W7)
Other Stuff:
1. Android SDK
2. hack4legend-v5.zip
3. RUU 1.31 for Legend
Common Errors Faced in the Process:
1. c---rw---- INSTEAD OF crwxrwxrwx
2. ADB Server timed out
3. Various RUU Errors
4. Visionary Not Working/Opening
Troubleshoot:
When you attempt to root you may face ADB timed out errors, it can be very annoying – there are various reasons for this, for me it was HTC Sync that was conflicting with ADB, shutting it down allowed me to boot into the custom recovery (step2 in the root process).
If you run into various other RUU errors (such as: unable to load boot loader, which was fixed by following step 3 correctly.) while trying to downgrade, most likely you didn’t do it correctly. Try doing it again and it should work.
Visionary Not Working/Opening (Solution: Download from phone browser: http://content.modaco.net/dropzone/c...ryplus.r13.apk)
Recommended to Back up Data:
1. Contacts:
You can save you’re contacts from you’re legend by clicking contacts, menu, import/export and export to SD Card.
2. SMS:
Get the SMS Backup and Restore App form Market, Install and Save it on to the SD Card.
3. Backup Complete SD Card:
Copy all the contents of the SD Card and save it onto the PC.
We start now;
Step 1:
Install Android SDK
Extract hack4legend-v5.zip to C Drive
Step 2:
Have adb in your path, or move the files contained in hack4legend-v5.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
crackin.sh
or in Windows
Code:
crackin.bat
Your phone will reboot 5 times.
You WILL see several error messages.
it looks like this c---rw----
c---rw---- 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
You’re done with this.
Step 3:
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
Step 4:
RUN RUU to downgrade to 2.1 – it should be possible to do so now.
Hence, you will be downgraded to 2.1 and you can use the normal way to root your legend.
All I can say is that the CM7 Mod is so fast on the Legend, no lag whatsoever, it's beyond! (will post a video 4 you guys)
End.
Forgive me if i seem rude.Hasn't this been covered in many other threads before?
I searched the site but never found this same method, is a combination of 2 or more guides at one place, also touching on some of the common errors faced when downgrading.
after this command '/data/local/flash_image misc /data/local/misc1-2.img'
it says "flash_image not found"....
So? Find it and put it there via adb.
but this is what i try...
i have both files in c:/hack4/ and in c:/android-sdk-windows/tools/
i wright in command " /c/hack4/flash_image misc /c/hack4/misc1-2.img"
and i have the message "flash_image not found"
am i doing something wrong?
i have also tried "/c/android-sdk-windows/tools/flash_image misc /c/android-sdk-windows/tools/misc1-2.img" the same problem...
What hboot do you have? Look at the guide for YOUR hboot ive had different Hboots across 2 devices and needed to use the right guide for the right hboot
bonesy said:
What hboot do you have? Look at the guide for YOUR hboot ive had different Hboots across 2 devices and needed to use the right guide for the right hboot
Click to expand...
Click to collapse
i have 1.01
alfagama said:
i have 1.01
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=10217134&postcount=1
bonesy said:
http://forum.xda-developers.com/showpost.php?p=10217134&postcount=1
Click to expand...
Click to collapse
i have tried this to... the same problem
Are you sure you executed these codes from Guide 2 ?
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
Click to expand...
Click to collapse
These is supposed to upload the images required on your phone and be exventually be executed on your phone to replace the image
ps: im no expert but i just flashed mine recently and i had to read the guides several times to understand the logic behind each guide to avoid mistakes some had with their phones...
alfagama said:
i have tried this to... the same problem
Click to expand...
Click to collapse
Then you cant be followign the guide right.Have you done temproot?
yes i tried with visionairy13 and 14 both time i had su= #
a noob question...'/data/local/flash_image misc /data/local/misc1-2.img' =" /c/hack4/flash_image misc /c/hack4/misc1-2.img" where i have the 2 files...
Blay0 answered correctly...i didnt
alfagama said:
a noob question...'/data/local/flash_image misc /data/local/misc1-2.img' =" /c/hack4/flash_image misc /c/hack4/misc1-2.img" where i have the 2 files...
Click to expand...
Click to collapse
Nooooooooo dammit! You have just pushed both those files to your phone!!!!!!!!! Go to your phone shell via adb, execute su to gain root privileges and then execute flash_image on your phone not on your PC!!!!! It doesn't really matter where on the phone do you have both as long as they are both in /data dir and don't prepend anything!!!
i am very confused now , can yoy help me step by step?
i run on my phone visionairy and then i click on temproot.
then i run on my pc cmd and i give the comand "adb shell" and then i type su and it says #...
after that should i give the next command on the pc again or on my phone, and with what should i replace the /data/local/ ...?
Pay attention dude!
Open two command prompts. Name them ONE and TWO. You gonna use ONE for copying files from your PC to your phone using adb push. You gonna use TWO for connecting from your PC to your phone using adb shell and execute all commands meant to be executed on your phone there. Now use ONE to copy (adb push) a program called flash_image to your phone's directory /data/local. After you do that use TWO to connect to your phone (adb shell), execute su to gain root privileges (you get # prompt) now in the same commnd prompt (that's TWO) change permissions of program flash_image you have just copied to your phone in ONE. Then also on TWO execute flash_image program with parameters from above.
If you don't understand what I'm saying you better sell that phone and instead use phone booth. In fact sell all your hi-tech stuff including your PC. It would be much safer for you and even for us.
Sent from my HTC Legend
alfagama said:
/c/hack4/flash_image misc
Click to expand...
Click to collapse
Faaaairly sure you're gonna want to write C: and not c/ dude, regardless of what other stuff you're doing wrong.
BlaY0 said:
Pay attention dude!
Open two command prompts. Name them ONE and TWO. You gonna use ONE for copying files from your PC to your phone using adb push. You gonna use TWO for connecting from your PC to your phone using adb shell and execute all commands meant to be executed on your phone there. Now use ONE to copy (adb push) a program called flash_image to your phone's directory /data/local. After you do that use TWO to connect to your phone (adb shell), execute su to gain root privileges (you get # prompt) now in the same commnd prompt (that's TWO) change permissions of program flash_image you have just copied to your phone in ONE. Then also on TWO execute flash_image program with parameters from above.
If you don't understand what I'm saying you better sell that phone and instead use phone booth. In fact sell all your hi-tech stuff including your PC. It would be much safer for you and even for us.
Sent from my HTC Legend
Click to expand...
Click to collapse
my friend i pretty sure that you know much than i do...
but for your information i am 48 and i am the last 20 years involved with computers and mobile phones.... over that 20 years i have learned at least to follow instructions (if they are clear), so once again thanks for your help.
my problem was that after unistalling sync 3.0 and installing sync 2.033 i have not uninstalled the drivers so i had problem.
after fixing that everything went smooth.
So after 20 years in computers, you actually found out that the problem was on your side and not in the instructions. Too bad. My mom is also been using computers for more than 20 years. She knows what is monitor and that she can move cursor around with the mouse.
BTW what has version of sync to do with your confusion? You are trying to say that "flash_image not found" error had something to do with sync version? Ohh, give me a break...
And as far as clear instructions are concerned... I guess they are pretty clear if 99 ppl find them OK and one (that's you) doesn't.
Don't want to be rude but maybe 20 years was too much and it is time to start something completely different.
Hey All,
Here's how to update to the latest version of Marshmallow, finally released. I rehosted everything on Google Drive in case AT&T pulls the files. This is the PD6 version of the firmware.
I was rooted running a custom rom on 5.0.2. If you're running the previous latest build (OJ9), you can start the instructions at step 7.
1. This will wipe your phone, so be sure to backup before doing any of this
2. Download Odin and the 5.1.1 OJ9 firmware files (4 of them) from Google Drive
3. Flash in Odin by clicking all 4 buttons (AP, CSC, etc) and matching them to the 4 files from the OJ9 firmware
4. Click start
6. Once your phone reboots and you verify you're running OJ9, you can flash the 6.0.1 update through ADB
7. Make sure you’re running the latest version of ADB (windows package included in the folder worked great for me on Windows 10)
8. The file named “SS-G925AUCU3BOJ9-to-U3CPD6-UP” is the 6.0.1 update, download it and rename it to “ota.zip” and place it wherever ADB is installed
9. Power it off
10. Once it’s off, hold the power, home, and volume UP buttons until it says installing update, this is entering recovery mode
11. Once the menu is up, use the volume buttons to select install update from ADB
12. Type “adb devices” to confirm your device is ready, then “adb sideload ota.zip”
13. It’ll take quite some time, but eventually your phone will reboot and you’ll be running the official PD6 version of the AT&T 6.0.1 update for the S6 edge. Enjoy!
EDIT: If you're having problems with ADB reading the 6.0.1 update, try first launching ADB from wherever it is installed (C:\Program Files (x86)\Minimal ADB and Fastboot\ for me), type "adb kill-server" then "adb start-server," then "adb devices" to confirm you see your device (it should say sideload beside it if it is ready for the update). Then, type "adb sideload " and simply DRAG the ota.zip file from wherever you downloaded it to the CMD window. It should complete the command so that it is "adb sideload ota.zip". NOW press enter, and give it half an hour to complete or so. Good luck!! Special thanks to XDA user gmccowan1 for the tip.
https://drive.google.com/open?id=0B04l-XMi07VKdkY0ZExzeEVHcFk
Have fun!
So, no matter what I try, adb "cannot read file ". I renamed the file to ota.zip. I renamed to ota. I zipped it and ranmed to ota.zip, and then ota. Am I missing something? No luck here. Thanks for any help.
i think u should zip the file not changing the name
TXRangerXDA said:
So, no matter what I try, adb "cannot read file ". I renamed the file to ota.zip. I renamed to ota. I zipped it and ranmed to ota.zip, and then ota. Am I missing something? No luck here. Thanks for any help.
Click to expand...
Click to collapse
A couple suggestions:
1) Don't zip the file; it is already compressed. Just rename it with a zip extension.
2) Make sure that you're using ADB version 1.0.35. The Minimal ADB and Fastboot zip in the Google Drive contains the proper version.
If that doesn't work, you probably have another version of ADB installed and your system variables path is pointing to the old version . To make things simple do the following:
1) Copy OTA.zip to C:\Program Files (x86)\Minimal ADB and Fastboot
2) Open command prompt from that folder (Shift + Right Click -> Open command window here). The file name doesn't matter as long as your command is adb sideload <filename>.zip (e.g. adb sideload ota.zip).
kapooo3 said:
i think u should zip the file not changing the name
Click to expand...
Click to collapse
Yep, I tried that as well. Both with and without .zip, and with and without zipping it.
AvenidaDelGato said:
Make sure that you're using ADB version 1.0.35. The Minimal ADB and Fastboot zip in the Google Drive contains the proper version.
If that still doesn't work, you probably have another version of ADB installed and your system variables path is pointing to the old version .
To make thing simple, copy the OTA.zip file to C:\Program Files (x86)\Minimal ADB and Fastboot and open command prompt from that folder (Shift + Right Click -> Open command window here). The file name doesn't matter as long as your command is adb sideload <filename>.zip (e.g. adb sideload ota.zip).
Click to expand...
Click to collapse
I installed it to c:\adb, then put my files there and ran from there. Downloaded everything from the google drive link. It is possible I have another version installed, will check that, but I don't think so.
TXRangerXDA said:
Yep, I tried that as well. Both with and without .zip, and with and without zipping it.
I installed it to c:\adb, then put my files there and ran from there. Downloaded everything from the google drive link. It is possible I have another version installed, will check that, but I don't think so.
Click to expand...
Click to collapse
I made a revision to my post while you were replying. Check it out. BTW if your ADB version is older than 1.0.35 your phone will output a line saying something like "please use version 1.0.35".
I'm on PC2, but whenever I try to flash PD4 to get to PD6, I get a Status 7 error.
Few tips for adb and sideload
When running adb devices in the command prompt you should see a device ID number and sideload next to it
When calling a new version of adb.exe (assuming you are using the same PATH location) suggest to close and reopen the command prompt (windows cmd)
check which version of adb server is running, adb version (note you need >x.x.35)
If needed adb kill-server then adb start-server, then run adb version make sure its .35 at least (note the location of where PATH is pointing!! It could be using a different location for adb.exe)
You can also do adb help, look for sideload option, if sideload is not listed in the help menu, guess what, your version of adb server doesn't support this command, do the above
Lastly if none of that stuff is working check in the device managler (i mean manager) and see what adb device driver you are using. I have one from 2010 and it seems to be happy
AvenidaDelGato said:
A couple suggestions:
1) Don't zip the file; it is already compressed. Just rename it with a zip extension.
2) Make sure that you're using ADB version 1.0.35. The Minimal ADB and Fastboot zip in the Google Drive contains the proper version.
If that doesn't work, you probably have another version of ADB installed and your system variables path is pointing to the old version . To make things simple do the following:
1) Copy OTA.zip to C:\Program Files (x86)\Minimal ADB and Fastboot
2) Open command prompt from that folder (Shift + Right Click -> Open command window here). The file name doesn't matter as long as your command is adb sideload <filename>.zip (e.g. adb sideload ota.zip).
Click to expand...
Click to collapse
Thanks, hope others find this useful. These exact instructions should prevent any headache when using ADB.
Note that the version of minimal fastboot and ADB I included is v1.4, but if you type "adb version" it says 1.0.35. It should still work fine!
Arcen1k said:
I'm on PC2, but whenever I try to flash PD4 to get to PD6, I get a Status 7 error.
Click to expand...
Click to collapse
Hrm, why are you flashing PD4 at all? PD6 is the latest one, but the file I gave is specifically for upgrading OJ9 (5.1.1) to PD6 (latest).
No idea if downgrading through Odin will work, but if you're on OJ9 you should have no issues sideloading.
TXRangerXDA said:
Yep, I tried that as well. Both with and without .zip, and with and without zipping it.
I installed it to c:\adb, then put my files there and ran from there. Downloaded everything from the google drive link. It is possible I have another version installed, will check that, but I don't think so.
Click to expand...
Click to collapse
Keep me posted, I'm interested to know if you get this resolved.
The package itself should contain an md5 and verify before flashing it... so I doubt there's anything wrong with the files I uploaded. Has anyone else besides me successfully installed marshmallow?
Sounds like the problem is with the ADB or the PC. Have you tried different ports (like USB 2.0 instead of 3.0) or a different computer?
EDIT: Users on reddit have successfully gotten marshmallow from the files I uploaded, so they are safe.
As for the "ota.zip" error, one user tried almost everything, and in the end restarting his PC fixed it oddly enough. See here:
https://www.reddit.com/r/GalaxyS6/c...l_att_601_marshmallow_update_flashing/d2sv6d5
For anyone who flashed PC2, or I guess for future reference to return from PD6.
I flashed PC2 not realizing we could flash PD6 directly. I was able to use ODIN to get back to OJ9, then sideload PD6.
---------- Post added at 05:32 PM ---------- Previous post was at 05:31 PM ----------
[/COLOR]
CitizenInsane said:
Hrm, why are you flashing PD4 at all? PD6 is the latest one, but the file I gave is specifically for upgrading OJ9 (5.1.1) to PD6 (latest).
No idea if downgrading through Odin will work, but if you're on OJ9 you should have no issues sideloading.
Click to expand...
Click to collapse
I flashed PC2, not realizing that we could go directly to PD6. I have since used ODIN to get back to OJ9. Then I flashed PD6 directly from there. Process worked fine.
AvenidaDelGato said:
A couple suggestions:
1) Don't zip the file; it is already compressed. Just rename it with a zip extension.
2) Make sure that you're using ADB version 1.0.35. The Minimal ADB and Fastboot zip in the Google Drive contains the proper version.
If that doesn't work, you probably have another version of ADB installed and your system variables path is pointing to the old version . To make things simple do the following:
1) Copy OTA.zip to C:\Program Files (x86)\Minimal ADB and Fastboot
2) Open command prompt from that folder (Shift + Right Click -> Open command window here). The file name doesn't matter as long as your command is adb sideload <filename>.zip (e.g. adb sideload ota.zip).
Click to expand...
Click to collapse
Im not sure what to do here when I install the ADB to my system I go into the folder and it wont run from the folder. I can only get the CMD window to open from start menu. And it always fails to read the file.
Arcen1k said:
I'm on PC2, but whenever I try to flash PD4 to get to PD6, I get a Status 7 error.
Click to expand...
Click to collapse
You should be able to upgrade directly from PC2 to PC6 using the upgrade file SS-G925AUCU3CPC2-to-U3CPC6-UP available here: <https://xdmd.sl.attcompute.com/agents/48652/1488/SS-G925AUCU3CPC2-to-U3CPC6-UP>
Make sure to add a .zip extension to the filename.
---------- Post added at 01:59 AM ---------- Previous post was at 01:19 AM ----------
cws754 said:
Im not sure what to do here when I install the ADB to my system I go into the folder and it wont run from the folder. I can only get the CMD window to open from start menu. And it always fails to read the file.
Click to expand...
Click to collapse
The steps below should help you avoid any issues:
Open command prompt and enter adb version. If it outputs "Android Debug Version 1.0.35", skip to Step 3. Otherwise proceed to Step 2.
Navigate to the directory of Minimal ADB and Fastboot by entering cd c:\<path to directory>. If you installed it to the default directory enter cd C:\Program Files (x86)\Minimal ADB and Fastboot
Enter adb sideload <filename.zip> (e.g. adb sideload ota.zip). If this doesn't work proceed to Step 4.
The "cannot read file.zip" error can also be a result of an incorrect file path. Try specifying the file path by entering adb sideload <%path%\filename.zip> (e.g. adb sideload C:\Program Files (x86)\Minimal ADB and Fastboot\ota.zip). If this doesn't work, paste the content of your command prompt window in a response (to copy text in command prompt right click -> select all -> Ctrl +C).
AvenidaDelGato said:
You should be able to upgrade directly from PC2 to PC6 using the upgrade file SS-G925AUCU3CPC2-to-U3CPC6-UP available here: <https://xdmd.sl.attcompute.com/agents/48652/1488/SS-G925AUCU3CPC2-to-U3CPC6-UP>
Make sure to add a .zip extension to the filename.
---------- Post added at 01:59 AM ---------- Previous post was at 01:19 AM ----------
The steps below should help you avoid any issues:
Open command prompt and enter adb version. If it outputs "Android Debug Version 1.0.35", skip to Step 3. Otherwise proceed to Step 2.
Navigate to the directory of Minimal ADB and Fastboot by entering cd c:\<path to directory>. If you installed it to the default directory enter cd C:\Program Files (x86)\Minimal ADB and Fastboot
Enter adb sideload <filename.zip> (e.g. adb sideload ota.zip). If this doesn't work proceed to Step 4.
The "cannot read file.zip" error can also be a result of an incorrect file path. Try specifying the file path by entering adb sideload <%path%\filename.zip> (e.g. adb sideload C:\Program Files (x86)\Minimal ADB and Fastboot\ota.zip). If this doesn't work, paste the content of your command prompt window in a response (to copy text in command prompt right click -> select all -> Ctrl +C).
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb version
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
05157df5438f7a1d sideload
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ota.zip
loading: 'ota.zip'
* cannot read 'ota.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot>
This is what I got
cws754 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb version
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
05157df5438f7a1d sideload
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ota.zip
loading: 'ota.zip'
* cannot read 'ota.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot>
This is what I got
Click to expand...
Click to collapse
Try checking to make sure your zip isn't corrupted. Are you able to view the contents of ota.zip by double clicking on it? What are the contents of the zip?
AvenidaDelGato said:
Try checking to make sure your zip isn't corrupted. Are you able to view the contents of ota.zip by double clicking on it? What are the contents of the zip?
Click to expand...
Click to collapse
Yeah I can open and view everything is there I downloaded again to make sure all the same everything there. I was going to try just using original file not renaming it or anything. Is that a bad idea? I promise I'm not 100% noob just cant figure why its not working.
cws754 said:
Yeah I can open and view everything is there I downloaded again to make sure all the same everything there. I was going to try just using original file not renaming it or anything. Is that a bad idea? I promise I'm not 100% noob just cant figure why its not working.
Click to expand...
Click to collapse
This might sound dumb but try adb sideload ota.zip.zip. Sometimes Windows hides the extra .zip when you have file name extensions hidden. If that still doesn't work try opening command prompt with Run as Administrator.
AvenidaDelGato said:
This might sound dumb but try adb sideload ota.zip.zip. Sometimes Windows hides the extra .zip when you have file name extensions hidden. If that still doesn't work try opening command prompt with Run as Administrator.
Click to expand...
Click to collapse
well I guess its just not wanting to work for me even tried different computer.
cws754 said:
well I guess its just not wanting to work for me even tried different computer.
Click to expand...
Click to collapse
This is baffling - I've read other people having a similar issue and it seems like something different fixed it each time.
Have you tried stuff like restarting? Or different ports on the PC?