Related
I have a Sprint HTC Hero which until yesterday had never been rooted. Software version was 2.31.651.7. I'm trying to install CM6 using these instructions.
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Sprint_Hero_with_Android_2.1
I have rolled it back to 2.27.651.5, as suggested in the above article and I used the universal root method, which seems to have worked. Then when I started the Flashing Radio step I realized that they left out how to install a custom recovery image. I searched and found these instructions:
http://forum.xda-developers.com/showpost.php?p=4898505
After figuring out what adb and fastboot are, I was able to run 'adb devices' which shows:
List of devices attached
HT99RHF03843 device
I then ran 'adb shell reboot bootloader' which gave me the screen with the three androids riding skateboards. Info from that screen:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
MICORP-0110
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010,16:02:39
When I try to run 'fastboot boot recovery-RA-heroc-v1.6.2.img' I get:
downloading 'boot.img'... FAILED (remote: not allow)
This is were I'm stuck. 'fastboot devices' shows:
HT99RHF03843 fastboot
I've tried searching and most of what I found is over a year old and says something about a perfect SPL, but I gotta believe there is some way around this. I do believe the root worked because I can do an 'adb shell' then 'su' and I get the # prompt. If I can't get a custom image on I'm just going to buy a new phone so I'm willing to risk bricking the phone to get this to work. If anyone knows a way around this I would greatly appreciate some assistance. Thanks.
-Iz-
1. I think you have the latest radio - might not need to flash a new one.
2. About flashing recovery, it's pretty easy -
a. Download the recovery image you want and put it on the SD card (not in any folder)
b. Goto ADB shell and run following commands:
- "flash_image recovery </sdcard/image name>" without quotes and "<>" - replacing image name with the actual file name with extension that you saved to the SD card
- reboot recovery
I am assuming once rooted, you can get to adb shell from your computer.
Let me know if you have further questions.
Thanks for the suggestion here is where I'm at now.
adb shell puts me at the $ prompt, when I type 'flash_image recovery recovery-RA-heroc-v1.6.2.img' from there I get 'flash_image: permission denied'. I also get that if I type gibberish for example if I type 'djherjn' i get 'djherjn: permission denied'. If I use 'su' to get to a # prompt, then run the command I get 'flash_image: not found', If I type gibberish at the # prompt I get 'djherjn: not found'. So it looks like it does not recognize the command flash_image. I checked path using 'echo $PATH' on both prompts it returns '/sbin:/system/sbin:/system/bin:/system/xbin'. Odd thing is there is no /system/sbin directory and flash_image is not located in any other directory. I'm starting to think the phone isn't really rooted. But when I run the universal root again it says phone is already rooted.
You are missing some words on the flashing I think...try this instead.
Connect your USB from the phone to PC choose Charge only.
Now open up Command Prompt(CMD) and type adb shell. Then just to be safe type SU...if SuperUser asks for permission on your phone, give it permission. Should give a # sign instead of $.
Then type ---- flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
You forgot the /sdcard/ from what I read from your post.
With the device set to charge only, adb does not see it. I've been having to set it to HTC Sync, just tried again to make sure. I'm still getting 'flash_image: not found' when I type the command 'flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img' from the # prompt. I also tried 'cd sdcard' and then 'flash_image recovery recovery-RA-heroc-v1.6.2.img' still same error. 'ls sdcard' does show the image in that directory and I'm using copy and paste to avoid typos. I'm still thinking it is complaining that there is no flash_image command. I'm going to re-flash it with the HTC software and start over just in case I screwed something up.
I had the same problem.
Before you go ahead with flashing HTC software, try the ROM manager app from the market. You could flash the ClockWorkMod recovery from ROM manager.
If that does not work, don't waste any more time - go the RUU route (preferbaly using the 2.27.651.5 release) and root using: http://forum.xda-developers.com/showthread.php?t=694572.
I just went through a bunch of issues with recovery/backup/restore and such, so consider this fresh advice ;-).
izard said:
With the device set to charge only, adb does not see it. I've been having to set it to HTC Sync, just tried again to make sure. I'm still getting 'flash_image: not found' when I type the command 'flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img' from the # prompt. I also tried 'cd sdcard' and then 'flash_image recovery recovery-RA-heroc-v1.6.2.img' still same error. 'ls sdcard' does show the image in that directory and I'm using copy and paste to avoid typos. I'm still thinking it is complaining that there is no flash_image command. I'm going to re-flash it with the HTC software and start over just in case I screwed something up.
Click to expand...
Click to collapse
EDIT: Andy beat me to it!
If you want Amon-Ra you have to choose Flash Alternate Recovery.
Finally got it! I used the ROM manger app. I swear last night when I was considering it, I only saw the paid version. That was so much easier then what I was doing. Thanks everyone for your help. It is highly appreciated.
-Iz-
Hey all
Trying to install a stable/snapshot version of cyanogen mod for my xperia V (more specifically: http://download.cyanogenmod.org/?type=snapshot&device=tsubasa) and im following their guide to do it: http://wiki.cyanogenmod.org/w/Install_CM_for_tsubasa
However, when i get to 5th step on the "Installing Cyanogenmod on Sony Devices" telling me to "Open a terminal on the PC and enter the following: fastboot -i 0xfce flash boot boot.img ", it doesn't work because fastboot simply replies Access is denied and i have no idea why, i'm running my command promt (CMD) as administrator and i'm 100% sure that i own all the files and folders on my computer... anyone know why and have a solution?
And Yes my Bootloader is unlocked, however, my phone is NOT rooted, because of what i can see according to guide its not necessary to do so, or at least not yet, and if this is the case, please tell me and i will root my phone and try again.. aswell as writing to the authors of the wiki article and piss a bit on them for not saying that its required.
Hawake said:
Hey all
Trying to install a stable/snapshot version of cyanogen mod for my xperia V (more specifically: http://download.cyanogenmod.org/?type=snapshot&device=tsubasa) and im following their guide to do it: http://wiki.cyanogenmod.org/w/Install_CM_for_tsubasa
However, when i get to 5th step on the "Installing Cyanogenmod on Sony Devices" telling me to "Open a terminal on the PC and enter the following: fastboot -i 0xfce flash boot boot.img ", it doesn't work because fastboot simply replies Access is denied and i have no idea why, i'm running my command promt (CMD) as administrator and i'm 100% sure that i own all the files and folders on my computer... anyone know why and have a solution?
And Yes my Bootloader is unlocked, however, my phone is NOT rooted, because of what i can see according to guide its not necessary to do so, or at least not yet, and if this is the case, please tell me and i will root my phone and try again.. aswell as writing to the authors of the wiki article and piss a bit on them for not saying that its required.
Click to expand...
Click to collapse
Are you sure you're in fastboot mode? Try with flashtool and see if you get the same error.
Hello guys i need help regarding my htc one m7.
I tried to go back to stock rom with a HTC ONE m7 fw 1.29.401.12 and did not know that ruu version have to match exactly the fw version since i have s-on.
I locked the bootloader and therefore all data were deleted on my phone so all my backups and cyanogenmod installation files.
My bootloader still works this goes also for twrp.
I researched for hours and found a solution with adb sideload but i am just not able to properly transfer the file.
I have htc sync installed and also sdk tools adb etc.
When i go into recovery and open cmd command in platform tools and type "adb devices " i get this : List of devices attached
name of device device
so everything is good till now.
Now i go to twrp and put the one into adb sideload then i get the following result when i type adb devices :
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
name of the device sideload
So this is my problem guys i need to transfer the file but i dont know what is causing the problem would be awesome if you can help somehow.
Have a nice weekend all!
See Question (2 in this faq post to fix your drivers http://forum.xda-developers.com/showthread.php?p=52135024 :good:
ioakimakos93 said:
Hello guys i need help regarding my htc one m7.
I tried to go back to stock rom with a HTC ONE m7 fw 1.29.401.12 and did not know that ruu version have to match exactly the fw version since i have s-on.
I locked the bootloader and therefore all data were deleted on my phone so all my backups and cyanogenmod installation files.
My bootloader still works this goes also for twrp.
I researched for hours and found a solution with adb sideload but i am just not able to properly transfer the file.
I have htc sync installed and also sdk tools adb etc.
When i go into recovery and open cmd command in platform tools and type "adb devices " i get this : List of devices attached
name of device device
so everything is good till now.
Now i go to twrp and put the one into adb sideload then i get the following result when i type adb devices :
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
name of the device sideload
So this is my problem guys i need to transfer the file but i dont know what is causing the problem would be awesome if you can help somehow.
Have a nice weekend all!
Click to expand...
Click to collapse
Danny201281 said:
See Question (2 in this faq post to fix your drivers http://forum.xda-developers.com/showthread.php?p=52135024 :good:
Click to expand...
Click to collapse
Ok I read your post again and think I misunderstood your problem. Your drivers are working as adb see's the device so what exactly is the problem? The sideload does not complete?
You should uninstall HTC Sync for starters it will do you no favours while using adb/fastboot commands it has the potential to cause hangs. if
Code:
adb sideload name-of-zip
is not working for you.
Try adb push instead with the one on the TWRP home screen (Not in Sideload mode)
Code:
adb push name-of-zip.zip /sdcard
The command window will appear unresponsive until the push completes. (several minutes) When it's done select Install from the TWRP menu and select the rom zip file.
If you still get problems copy and paste the error from your command window here :good:
Or flash TWRP 2.8.5.0 it has the ability to use MTP in recovery so you can see your phones Internal Storage while in recovery and just drag and drop the rom to your phone :good:
Does anyone know where I can find step by step instructions for rooting my mini on a Mac? Online i've found very little info on rooting the HTC One Mini 2, and where I have found guides, they have been using a PC.
I would appreciate greatly if someone could direct me to a step by step guide for rooting the Mini 2 from scratch using a Mac, or can tell me how to do it, as I have very little experience in this and don't want to risk doing something wrong:/
Thanks, Tzveti.
tzveti said:
Does anyone know where I can find step by step instructions for rooting my mini on a Mac? Online i've found very little info on rooting the HTC One Mini 2, and where I have found guides, they have been using a PC.
I would appreciate greatly if someone could direct me to a step by step guide for rooting the Mini 2 from scratch using a Mac, or can tell me how to do it, as I have very little experience in this and don't want to risk doing something wrong:/
Thanks, Tzveti.
Click to expand...
Click to collapse
1-Download HTC drivers/root files Win/Mac unzip to downloads/HTCRootMac.
2-open terminal
3-type: (after connecting your phone, make sure is recognized)
cd downloads
cd HTCRootMac
chmod 755 * (this will change permitions)
(dot) ./adb-mac backup -apk -all -f backup.ab (this will backup your phone)
4- turn phone into bootloader mode
5- type in terminal and following htc dev instructions until get token
(dot) ./fastboot-mac oem get_identifier_token
6- paste Unlock_code.bin into downloads/HTCRootMac folder
7- terminal type
(dot) ./fastboot-mac flash unlocktoken Unlock_code.bin
8- check phone and follow instructions (choose yes, this will erase your phone)
8.1 finish setup and send super user to somewhere in phone or sdcard keep as .zip file
9- put phone back into bootloader (should say at the top "tempered / unlocked")
10- download TWRP and put same folder in mac (downloads/HTCRootMac)
11- terminal type:
(dot) ./fastboot-mac flash recovery twrp-2.8.1.0-20142812-memul.img
(dot) ./fastboot-mac erase cache
12-in phone try to enter recovery (you should get into TWRP
13- inside TWRP install super user
14- turn phone on and inside settings tick USB debugging
15- (dot) ./adb-mac restore backup.ab (this will restore your phone (optional))
DONE.
let us know how it go.
Oh my god thank you so much)) I'll try this tomorrow and hopefully it will go well, there aren't any chances of me hard bricking my phone in this procedure right?
Again thank you so much this is very useful
kativiti said:
1-Download HTC drivers/root files Win/Mac unzip to downloads/HTCRootMac.
2-open terminal
3-type: (after connecting your phone, make sure is recognized)
cd downloads
cd HTCRootMac
chmod 755 * (this will change permitions)
(dot) ./adb-mac backup -apk -all -f backup.ab (this will backup your phone)
4- turn phone into bootloader mode
5- type in terminal and following htc dev instructions until get token
(dot) ./fastboot-mac oem get_identifier_token
6- paste Unlock_code.bin into downloads/HTCRootMac folder
7- terminal type
(dot) ./fastboot-mac flash unlocktoken Unlock_code.bin
8- check phone and follow instructions (choose yes, this will erase your phone)
8.1 finish setup and send super user to phone
9- put phone back into bootloader (should say at the top "tempered / unlocked")
10- download TWRP and put same folder
11- terminal type:
(dot) ./fastboot-mac flash recovery twrp-2.8.1.0-20142812-memul.img
(dot) ./fastboot-mac erase cache
12-in phone try to enter recovery (you should get into TWRP
13- inside TWRP install super user
14- turn phone on and inside settings tick USB debugging
15- (dot) ./adb-mac restore backup.ab (this will restore your phone (optional))
DONE.
let us know how it go.
Click to expand...
Click to collapse
Should I unzip the SuperSU and TWRP files before placing them on my phone?
Also, I haven't yet done this step but when you say this: "8.1 finish setup and send super user to phone", where do I send this file? as later on I also notice that you mention "10- download TWRP and put same folder", which folder is this? Is it the same folder as the Super user has been sent to? And if so where is this folder?
Sorry for all the questions
tzveti said:
Should I unzip the SuperSU and TWRP files before placing them on my phone?
Also, I haven't yet done this step but when you say this: "8.1 finish setup and send super user to phone", where do I send this file? as later on I also notice that you mention "10- download TWRP and put same folder", which folder is this? Is it the same folder as the Super user has been sent to? And if so where is this folder?
Sorry for all the questions
Click to expand...
Click to collapse
keep super user as .zip. and put it anywhere in phone where you can find easily .you gonna use TWRP to install it.
10- will be same folder you been using in mac (downloads/HTCRootMac) where adb files are.
instructions updated for this...
I got this message after trying step 3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb: unable to connect for backup
tzveti said:
I got this message after trying step 3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb: unable to connect for backup
Click to expand...
Click to collapse
did you install htc drivers? is the phone showing/mounted?
I downloaded all the stuff in the link provided, i'm not sure if there are other HTC drivers I should have downloaded.
Whether or not the phone is mounted i'm not sure of, as I can access it through Android File Transfer and can move files around, however it does not show as a device on my finder window.
tzveti said:
I downloaded all the stuff in the link provided, i'm not sure if there are other HTC drivers I should have downloaded.
Whether or not the phone is mounted i'm not sure of, as I can access it through Android File Transfer and can move files around, however it does not show as a device on my finder window.
Click to expand...
Click to collapse
install htc sync manager for latest drivers
kativiti said:
install htc sync manager for latest drivers
Click to expand...
Click to collapse
I now get this message:
adb server is out of date. killing...
* daemon started successfully *
adb: unable to connect for backup
In addition, now that I have installed HTC Sync Manager I can no longer use Android File Transfer, I'm not sure whether this is causing some kind of problem.
kativiti said:
install htc sync manager for latest drivers
Click to expand...
Click to collapse
I now get this message:
adb server is out of date. killing...
* daemon started successfully *
adb: unable to connect for backup
In addition, now that I have installed HTC Sync Manager I can no longer use Android File Transfer, I'm not sure whether this is causing some kind of problem.
tzveti said:
I now get this message:
adb server is out of date. killing...
* daemon started successfully *
adb: unable to connect for backup
In addition, now that I have installed HTC Sync Manager I can no longer use Android File Transfer, I'm not sure whether this is causing some kind of problem.
Click to expand...
Click to collapse
did you run this command " chmod 755 * " to change permitions?
kativiti said:
did you run this command " chmod 755 * " to change permitions?
Click to expand...
Click to collapse
Yes, however when I write the command nothing happens. When using the android file transfer application some text had appeared though.
tzveti said:
Yes, however when I write the command nothing happens. When using the android file transfer application some text had appeared though.
Click to expand...
Click to collapse
you can skip the backup. or do a backup using htc manager.
you must use a OTG cable (original htc cable)
I'm backing up the phone now using manager, and I am using the original cable however it is still not working:/
Done, fantastic, thanks a bunch mate
tzveti said:
Done, fantastic, thanks a bunch mate
Click to expand...
Click to collapse
glad i could help. change thread title to "Step by step MAC Rooting instructions" so others can find it too
kativiti said:
glad i could help. change thread title to "Step by step MAC Rooting instructions" so others can find it too
Click to expand...
Click to collapse
Thanks for the clear instructions,
i also have a question abut HTC ONE REMIX can you help me change modelid: 0P8B10000 to any european MID ?
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