Related
I'm writing this becuase i recently had trouble following other guides rooting my Bell and Virgin (canada) htc Legend with 2.1 on it (2.2 is out here yet)
First follow this guide
[HOWTO] DOWNGRADE to 1.31 which you can then root for Legend 2.1
http://forum.xda-developers.com/showthread.php?t=725430
Click to expand...
Click to collapse
(By now your should have adb set up and your gold card)
If it dosnt downgrade and shows that it fails its okay just move on
After following downgrade guide and it failing install temp root
the best way is to get the apk is to go to this link in the android browser
goo.gl/TcP1o <---Download link to visionary apk
In the web browser open downloads and install the visionary apk
Then connect your phone to your computer open cmd.exe and via adb get root
with cmd.exe
go
Code:
cd c:\AndroidSDK\platform-tools\
for me adb is under platform tools, if you dont update the sdk it is under just tools
then
Code:
adb shell
a # should be at the bottom line, then type in
Code:
su
This gets you root, if it says denied run the visionary app and try again, then
Code:
/data/local/flash_image misc /data/local/misc1-2.img
Then for the actual root
Flash the Rooted ROM1. Download the Rooting Tools
Legend Rooting Tools:
2. Unzip them to the C: drive on your computer (so the file path is C:\r4-legend-root\)
3. Turn off your phone and turn it back on by holding down Back and Power until you see Fastboot come up on the screen. Push the Power button while highlighting Fastboot on the phone and Fastboot should show up in red now on the phone (if it doesn’t push Power again until it does).
4. Plug the phone in via USB cable to the computer.
5. Open the folder you extracted to the C drive and double click “step1-windows.bat” and wait for it to finish.
6. Once you see the menu on the phone come back up, navigate to BOOTLOADER and push power, then navigate to RECOVERY using the volume buttons to navigate and the power button to select and the phone should boot to the ! screen.
7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish. (UPDATE 12.13.10 – You MUST have HTC Sync version 2.0.33 not a newer version for step2 to work. Please uninstall HTC Sync and download and install this version instead, unplug then plug your phone back in, then rerun step2-windows.bat).
8. Now you should see a custom recovery screen, using the optical trackpad navigate to Wipe and push on the trackpad to select it. Then navigate to Wipe data/factory reset and select that.
9. Once that is done, push volume down to go back to the main menu and select Flash zip from sdcard and select the rootedupdate.zip file and wait for it to flash. All done, you have root access and can use any root required app! Enjoy!
Click to expand...
Click to collapse
This worked when all else did not ill try and help others just ask
i got all this info from the links below and reading all the response's i hope this info helps some one
http://forum.xda-developers.com/showthread.php?t=725430
http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/
This deserves a sticky
mike998 said:
This deserves a sticky
Click to expand...
Click to collapse
What's wrong with the current sticky?
TheGrammarFreak said:
What's wrong with the current sticky?
Click to expand...
Click to collapse
i think maybe just the first post of the sticky needs to be updated to include something along these lines
Hello, Having some trouble here.
I got to the step where you run the Step1 batch file from windows. The cmd prompt comes up and says "erasing cache....." then sits. a few minutes later. i get
"FAILED <status read failed <unknown error>>
< Waiting for device>
During the erasing cache part, my phone had the boot menu on screen with no response from the controls. Also, a little green status bar was at 90%. (Second thought, that may be battery level. not sure. Confirm?)
Yeah, so, can't get step1 to work.
EDIT: ok. got step 1 and 2 to work. I basically just kept trying over and over and it went through.
So, i got to the custom boot menu. But i try to install update.zip from sd. But i get an error.
It says.
Installation aborted.
--wiping data...
formatting data...
formatting cache...
data wipe complete.
--install from sdcard
finding update package
opening update packing verifying update package.
E: failed to open /sdcard/update.
zip (No such file or directory)
E:signature verification failed
installation aborted.
So, wtf did i do wrong? now my phone is completely wiped, so.... now what?
sig ver
FourForty said:
Hello, Having some trouble here.
I got to the step where you run the Step1 batch file from windows. The cmd prompt comes up and says "erasing cache....." then sits. a few minutes later. i get
"FAILED <status read failed <unknown error>>
< Waiting for device>
During the erasing cache part, my phone had the boot menu on screen with no response from the controls. Also, a little green status bar was at 90%. (Second thought, that may be battery level. not sure. Confirm?)
Yeah, so, can't get step1 to work.
EDIT: ok. got step 1 and 2 to work. I basically just kept trying over and over and it went through.
So, i got to the custom boot menu. But i try to install update.zip from sd. But i get an error.
It says.
Installation aborted.
--wiping data...
formatting data...
formatting cache...
data wipe complete.
--install from sdcard
finding update package
opening update packing verifying update package.
E: failed to open /sdcard/update.
zip (No such file or directory)
E:signature verification failed
installation aborted.
So, wtf did i do wrong? now my phone is completely wiped, so.... now what?
Click to expand...
Click to collapse
okay when your in the recovery menu the one with green text and you go to flash the file theres an option to "toggle signature verification " or something along those lines
then when the verification is off flash it
k after i finally succeeded to downgrade (thinkin that the hard part is done!!!!), but i cant get past step 1, i keep gettin either "waiting for device", or htc black screen, or nothing happens. step 2 is even worse, all i get is "device not found", or loads of "FAILED". ive reinstalled htc sync 2, uninstalled htc drivers.
i think it seems that my computer is not recognising the phone as an android device, cos everytime i connect it, win7 seems to automatically install drivers (nd i cant stop that) and recognises it as HTC ANdroid Device (it appears as a "Disk Drive")..... tried to use htc sync, phone keeps searching nd it fails.. help please i cant use my phone
saifbunni said:
k after i finally succeeded to downgrade (thinkin that the hard part is done!!!!), but i cant get past step 1, i keep gettin either "waiting for device", or htc black screen, or nothing happens. step 2 is even worse, all i get is "device not found", or loads of "FAILED". ive reinstalled htc sync 2, uninstalled htc drivers.
i think it seems that my computer is not recognising the phone as an android device, cos everytime i connect it, win7 seems to automatically install drivers (nd i cant stop that) and recognises it as HTC ANdroid Device (it appears as a "Disk Drive")..... tried to use htc sync, phone keeps searching nd it fails.. help please i cant use my phone
Click to expand...
Click to collapse
You should install the old version of HTC Sync until you're rooted, have you done that?
saifbunni said:
k after i finally succeeded to downgrade (thinkin that the hard part is done!!!!), but i cant get past step 1, i keep gettin either "waiting for device", or htc black screen, or nothing happens. step 2 is even worse, all i get is "device not found", or loads of "FAILED". ive reinstalled htc sync 2, uninstalled htc drivers.
i think it seems that my computer is not recognising the phone as an android device, cos everytime i connect it, win7 seems to automatically install drivers (nd i cant stop that) and recognises it as HTC ANdroid Device (it appears as a "Disk Drive")..... tried to use htc sync, phone keeps searching nd it fails.. help please i cant use my phone
Click to expand...
Click to collapse
You need HTCsync 2 only for step2, to step1 you need the most updated HTCsync.
And you need step1, don't ignore that step just because it's not working.
Install the latest HTCsync, connect your phone to the computer, and put the phone on fastboot mode (should be written "fastboot usb" on phone)
now on the computer, in the folder of the rooting tools, write:
fastboot-windows.exe devices
Does it recognize your phone? (Should output details bout the phone including serial I think)
wel ive done step 1 now. i created a thread for this here..
http://forum.xda-developers.com/showthread.php?t=1095017
step 1 worked without htc sync, computer is good wen phone is in fastboot, it recognises it straight away, but wen i got into recovery is wher it messes up still even with htc sync. sum1 suggested another way, hav a look at the link, but im gettin signature verification failed or sumthin like that
help
saifbunni said:
wel ive done step 1 now. i created a thread for this here..
http://forum.xda-developers.com/showthread.php?t=1095017
step 1 worked without htc sync, computer is good wen phone is in fastboot, it recognises it straight away, but wen i got into recovery is wher it messes up still even with htc sync. sum1 suggested another way, hav a look at the link, but im gettin signature verification failed or sumthin like that
Click to expand...
Click to collapse
what hboot do you have on/ do you have android 2.2 on it?
Hi all.
I am hoping someone out there can help me.
I recently bought a used Dell Streak S7.
I tried to restore the DS& back to a factory out of the box state and no luck.
Tried the follwoing three
menu ->setting-> Privacy->Factory Data reset
pin hole by sd card\
Volume + and power -> 1. and 3.
I have added info for Wi-fi and everytime DS7 is turned off and turned on the wi-fi settings are lost.
I was able to root it with One Click Superoot but when i turn DS7 off and turn it off the SU dissapears.
I read http://forum.xda-developers.com/showthread.php?t=1011654 and i can't access CWM thorugh Goggle market.
The original owner account info still remains regardless of reboot and etc.....
I don't have a SD card for it and i am not sure what impact that has.
Android Version 2.2
Baseband Version 11.809.05.03.00
OEM version GLUNB1A132233
Build Number 14291
ANy information or any ideas would greatly help.
Thanks,
Dennis
Dennis,
Did you every resolve your issues?
I am having nearly the same issues as you were.
I bought a used Dell Streak that had been updated to Froyo. When I try to reset the device to factory settings to remove the original owners email address it acts like it works but each time the device boots back up all the original owners info is still there. Their wallpaper, email accounts, facebook accounts, twitter acounts, etc.
I have tried to use the Settings>Privacy>Factory Data Rest, it seems to work but doesn't clear the system all data remains.
I have tried turning off the unit and holding the volume up and power and using the restore option from there but each time it boots back with all the original owners info.
I can not get it to do a factory reset thus I can not associate my gmail account with the device.
Does anyone have a solution?
Thanks,
Frankie4life
No luck yet.
Still waiting and hoping.
Have you guys tried restoring with NVFlash? this procedure works great and helped me a bunch. http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
If you are successful but your streak still wont get past the dell logo on boot, boot back into recovery (Vol+ and Power) and do a factory restore.
warning, this will erase EVERYTHING on your streak
Same thing here
I am having the same exact issue. I have tried restoring using nvflash... No luck
I have tried using the Fastboot method... No Luck
I even found an Update.pkg to try and update it using the built in recovery... No luck, It ends with an error of "Modem Error" says it completed successfully and then reboots to its previos state.
I have tried flashing the clockwork recovery via Fastboot and also.... No Luck
I am not a Noob and I have the the proper ADB and fastboot drivers installed, I am very familiar with using the android sdk and adb command from the SDK folder location.
I beleive at this point either due to an error or something the previous owner did the Streak is now "write protected" is this possible?
My biggest problem is when I root the devices using super one click it gives me root access and when launching the ADB SHELL i receive the "#" indicating that the shell has root, If I try and run ADB remount i receive and error
"c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>"
this indicates to me that I cannot mount any memory from the device as read/write.
Any info would be helpful
Tom
wikedbubble said:
I am having the same exact issue. I have tried restoring using nvflash... No luck
I have tried using the Fastboot method... No Luck
I even found an Update.pkg to try and update it using the built in recovery... No luck, It ends with an error of "Modem Error" says it completed successfully and then reboots to its previos state.
I have tried flashing the clockwork recovery via Fastboot and also.... No Luck
I am not a Noob and I have the the proper ADB and fastboot drivers installed, I am very familiar with using the android sdk and adb command from the SDK folder location.
I beleive at this point either due to an error or something the previous owner did the Streak is now "write protected" is this possible?
My biggest problem is when I root the devices using super one click it gives me root access and when launching the ADB SHELL i receive the "#" indicating that the shell has root, If I try and run ADB remount i receive and error
"c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>"
this indicates to me that I cannot mount any memory from the device as read/write.
Any info would be helpful
Tom
Click to expand...
Click to collapse
hi, i'm going through something similar, where did you find the update.pkg? i've been looking for it everywhere, thank you
the answer i would suggest is use nvflash like navycow suggested you have 2 choices with that you can install unrooted 2.2.2 or honeycomb, search the thread for it and if you can't find it let me know i will post a link.
It seems that alot of people are having this problem I found the link for the OTA update here.
http://www.streaksmart.com/updates/page/2/
From there you can download the update.pkg manually or OTA
Make sure you don't use the O2 update because that is for the Streak released in EU. It took a little browsing but I found it in there somewhere
Preface:
I was performing a nandroid restore and then accidentally removed the battery at some point.
Situation:
Phone does not boot past black and white galaxy S screen.
Going into Clockwork Recovery, I am unable to factory reset, or start a restore because it seemingly is not able to detect any of the storage of the device....
(sample messages below):
Code:
E:unknown volume for path [/data]
E:unknown volume for path [/cache]
E:unknown volume for path [/sdcard]
E:unknown volume "/data"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
Furthermore, I can't just re-flash in download mode because the computer refuses to detect it in windows. At first I thought it was a driver problem, because i've had difficulty with my computer detecting the phone at times, but now I suspect download mode is broken somehow (after trying to reinstall the drivers and installing kies, and various combinations therein). When the phone is plugged into a different computer ( laptop ) running linux, I get messages like these on the command line:
Code:
usb 1-1: device not accepting address 2, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/8, error -71
hub-1.0:1.0: unable to enumerate USB device on port 1
On another note assuming I can't resolve this in a more delicate manner, can someone tell me if it is possible to use a jtag programmer to flash the phone?
Would using a jig to get into download mode make a difference?
Thank you very much for your assistance.
Wich Rom where you trying to restore to?
and what Rom were you on before you hit the Restore button?
pzayx said:
Wich Rom where you trying to restore to?
and what Rom were you on before you hit the Restore button?
Click to expand...
Click to collapse
I was trying to restore to stock JVR (rooted, no lagfix, semaphore kernel I think), from the ice cream sandwich port.
okey, i see, you might need to download android sdk and download the latest usb package or search around for the drivers for Nexus, since the usb drivers for galaxy s doesnt work with cm7/ics builds.
if you manage to make your pc recognise your phone you could check out this thread:
http://forum.xda-developers.com/showthread.php?t=1134975
btw, if you want to restore from ICS to stock gingerbread i think you will have to install a stock gingerbread ROM before you restore.
Hope this helps you!
(edit: if you find the driver or download it from SDK you can head here http://www.dkszone.net/setup-install-adb-android-debug-bridge-windows-7 to see a guide for how to set the driver manually)
Hm, Well I had already had the SDK and the drivers on my computer, but do I need to do anything special to install them? I recall previously trying the [right-click inf > Install] method, for some reason, but that didn't work
zeco said:
Hm, Well I had already had the SDK and the drivers on my computer, but do I need to do anything special to install them? I recall previously trying the [right-click inf > Install] method, for some reason, but that didn't work
Click to expand...
Click to collapse
i had to manually set the drivers,
i used this thread to do it:
http://www.dkszone.net/setup-install-adb-android-debug-bridge-windows-7
Just jump straight to step #7 if you have the drivers
Upon selecting the driver, windows immediately complains:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Agh, And I thought this might actually work too.
EDIT:
Unknown if this is a success or not... but i've been alternating computers trying various permutations of fixes, and this time my laptop actually says the word samsung in the device manager....
EDIT2: Odin Sees it! I am going to try to flash JVR now... then retry restore from there....
P.S. I hope to god this is not related, but I actually just dropped my phone in between switching to attempt on laptop....
EDIT3: Detection, but immediate failure open attempting to flash. Then rebooted phone and now upon pressing start again it seems to be flashing.........
P.P.S: I've got to say, the most stable thing about this series of phone has got to be the bootloaders :#, Like seriously, this thing is boss.
EDIT4: Well. Managed to flash, Now I just get stock recovery with the same problem of it not finding the storage... I guess I will try flashing with repartion and a PIT?
I had to manually choose the folder where i store the Android SDK.
like c:\sdk\sdk\
it sucks when things dosent work like they should do!
So Yeah... Despite not really changing very much at all, download mode connects, and My phone now boots, Which is a lot better than where I was at previously So thanks for your help.
yw, happy i could help you!
The next mystery to solve is why Recovery is still screwed, and why I can boot my device anyway....
Hmm
So youre still getting the E:\ unknown volume *****?
Wich odin version do u use?
I had to use Ezodin last time to get it to flash,
then i flashed full stock JVH (with pda, phone & csc)
but i guess you could try to flash a stock Gingerbread bootloader too,
http://forum.xda-developers.com/showthread.php?t=1089989 Here is both Froyo and Gingerbread bootloaders.
And i have Atached EZodin for you.
Hey guys
I did a terrible mistake. Instead of just normally resetting the phone to factory settings in CWM after unlocking it, my finger slipped to the "format /system" option.
This happened before, but then I just sideloaded the rom and everything was ok. Oddly enough, this doesnt work anymore.
Whenever I want to push something to my phone using adb, I get the error that the device was not found and I cannot do anything to access the phone (when entering the command "adb devices" for example, no device shows up). I installed every driver I can think of, I installed all the packages in the sdk manager and now I dont know what to do.
I know that the debug mode is required, but since theres no OS anymore, I really ran out of ideas.
Please help me! :crying:
PS: additional information:
- HTC One m7 (unlocked)
- Clockwerkmod Recovery
- Windows 8
- Hasoon2000's all in one kit
EDIT: I found this site that recommends flashing via fastboot. (blog.syedgakbar.com/2013/02/01/android-installing-system-images-using-flashboot/)
where do I find these images?
TL;DR- I'm trying to get back to Android 11 but I only have access to the fastboot menu since my phone is bootlooping. I'm fairly certain I hadn't enabled USB debugging when the phone was fully functional so I'm not sure if I can use ADB to do so. I also don't have the bootloader unlocked
I downloaded the 12 beta preview last week to try the new features, some UI bugs understandably but was mostly fine. A couple days ago while the screen was off and I just had the phone in my hand it randomly activated SOS mode so after a brief panic and cancelation of the 911 call I opted out of the beta immediately. The next morning after using my phone a bit I picked it up and noticed it was rebooting and was a little warm, and it's been bootlooping since then. I still remember the Andoid 12 UI being active so I'm pretty sure it hadn't reverted to the "new" 11 firmware yet.
I'm trying to revert back to 11 using the ADB on my PC, but I realized that I'm pretty sure I hadn't enabled USB debugging when my phone was still functional, so I'm not sure how to bypass that if I can at all. The web firmware flasher tool does detect my phone, but can't properly connect and I assume it's because the USB debugging isn't enabled.
Before I tried using the ADB I had attempted to perform a factory reset to fix the bootloop and the log messages said it was successfully done, but that didn't get it out of the loop.
@jet flyer
I didn't see the word "locked" or "recovery" anywhere in your post. If you are bootloader unlocked, you use fastboot to flash a full image. If you are BL locked, that should have been in your TL;DR. If you are BL locked, you can still flash a full OTA without having usb debug enabled. You just need to have the latest fastboot/adb binaries installed. Download the rescue OTA, put it in your adb folder and then from recovery mode, use the update via adb option. You do NOT need usb debug enabled to do this. You do however need a working Recovery mode. If you are BL locked and cannot access recovery that is the end of the road.
Sorry for the delayed response wanted a day off so I had enough time to properly deal with this. No it's not unlocked, edited OP to indicate that.
I only downloaded adb last week so that should be the most recent, are the fastboot binaries included in that install or is that something separate?
Using this video for help on how to run adb
I get the device connected sound on my PC when I select install from ADB on the recovery menu and I have ADB running at the C:\adb folder location. when I do the adb devices command I get this
'adb' is not recognized as an internal or external command,
operable program or batch file.
using the powershell I got the long list of text that's mentioned in the video after typing \adb but I still get a similar, but different, error when doing the devices command trying to confirm it's connected
Since this is probably just an error on my part not doing the right commands or something I'm hopping on the xda discord, I'll post here if I get it figured out
Download platform tools from here https://developer.android.com/studio/releases/platform-tools. Unzip it and then put the file that you want to side load in the same folder. I prefer PowerShell. Type adb sideload "file name.zip. That might not work if USB debugging isn't checked. If it doesn't try this.
Transfer the download OTA file to your device’s internal or external storage. Don’t put it inside any folder as the system won’t be able to find it.
Next up, boot your device to recovery.
From recovery, navigate to the Apply Update from SD Card option using Volume Keys. Press the Power key to confirm your selection.
Similarly, use the Volume keys to highlight the OTA.zip file and the Power key to install it. Once the process finishes, you could then use the Reboot system now option to boot your device back to OS
ok finally got something to run on my phone but got an error, here's the file paths and what I typed just in case
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's what the phone says, sorry about the marginal focus my backup pixel 2XL is doing it's best with the reflective screen. The relevant messages start right after the purple of the IR focusing laser reflection
one of the first errors is E: footer is wrong
and Error 21: signature verification failed
I recall hearing on one of those videos or guides I read that something has to be digitally signed, but this is a direct download from the Android website, wouldn't be already be signed?
jet flyer said:
ok finally got something to run on my phone but got an error, here's the file paths and what I typed just in case
View attachment 5333167
And here's what the phone says, sorry about the marginal focus my backup pixel 2XL is doing it's best with the reflective screen. The relevant messages start right after the purple of the IR focusing laser reflection
View attachment 5333175
one of the first errors is E: footer is wrong
and Error 21: signature verification failed
I recall hearing on one of those videos or guides I read that something has to be digitally signed, but this is a direct download from the Android website, wouldn't be already be signed?
Click to expand...
Click to collapse
Sorry for the delayed response, but If you use "reply" to a post the user will get an email notification and so respond more quickly. I normally check this board once a week. Yes, there is one zip file from Google that contains all the binaries you need for adb/fastboot. Yes the image coming from Google is signed. They even include the file hash so you can verify the file is a mirror image and un-corrupted. I'm going to continue down the adb method because it is fool proof and you may not be able to "push" the file to your device and use the sdcard method.
I'm not sure you have added your adb folder to your PC's path statement and this could be causing an issue. If you add this folder to the path, you can call up adb from any folder. However if you have the ota image in the same adb folder, and you navigate to that same folder before typing commands it will still work. I'm not seeing any of your inputs on your photo, so I can't check that. You can easily copy/paste text from the command window so we can clearly see what you are typing and the response back. What response are you getting to "adb devices" and "adb version" ? Until you get back your phone's serial number as a response, you are not connected properly. You can PM me for more assistance or use the reply button on this note. Best of luck.
v12xke said:
Sorry for the delayed response, but If you use "reply" to a post the user will get an email notification and so respond more quickly. I normally check this board once a week. Yes, there is one zip file from Google that contains all the binaries you need for adb/fastboot. Yes the image coming from Google is signed. They even include the file hash so you can verify the file is a mirror image and un-corrupted. I'm going to continue down the adb method because it is fool proof and you may not be able to "push" the file to your device and use the sdcard method.
I'm not sure you have added your adb folder to your PC's path statement and this could be causing an issue. If you add this folder to the path, you can call up adb from any folder. However if you have the ota image in the same adb folder, and you navigate to that same folder before typing commands it will still work. I'm not seeing any of your inputs on your photo, so I can't check that. You can easily copy/paste text from the command window so we can clearly see what you are typing and the response back. What response are you getting to "adb devices" and "adb version" ? Until you get back your phone's serial number as a response, you are not connected properly. You can PM me for more assistance or use the reply button on this note. Best of luck.
Click to expand...
Click to collapse
Ah sorry, still getting used to the specifics of this forum. Thanks for checking though.
I do get the serial number back as a response to verify I'm properly connected, I just didn't do it in that specific instance to avoid posting that online. And yes I did add it to the path(as far as I understand, that's just a convenience thing though?) but I'm still running it from the ADB folder just to be sure.
I'll go ahead and type here what commands I did and what the phone log says, since it's not in focus in the picture.
on adb I typed .\adb sideload coral-[specific file version].zip
adb response: Total xfer: 0.00x
on my phone which was on the load from adb screen it said this:
Now send the package you wan to apply
to the device with "adb sideload <filename> . . .
Supported API: 3
Finding update package. . .
Verifying update package. . .
E:footer is wrong
Update package verification took 0.5 s (result 1).
E:Signiture verification failed
Error: 21
Install from ADB completed with status 2.
Installation aborted.
Then it tried one more time automatically with the exact same text except taking 0.6 seconds but still failing and the same error messages. Should I just download the latest package (now the June update) and try again, or did I do something wrong? The file explorer window is where I opened the powershell from and where the file was extracted to. What does error 21 mean?
jet flyer said:
Ah sorry, still getting used to the specifics of this forum. Thanks for checking though.
I do get the serial number back as a response to verify I'm properly connected, I just didn't do it in that specific instance to avoid posting that online. And yes I did add it to the path(as far as I understand, that's just a convenience thing though?) but I'm still running it from the ADB folder just to be sure.
I'll go ahead and type here what commands I did and what the phone log says, since it's not in focus in the picture.
on adb I typed .\adb sideload coral-[specific file version].zip
adb response: Total xfer: 0.00x
on my phone which was on the load from adb screen it said this:
Now send the package you wan to apply
to the device with "adb sideload <filename> . . .
Supported API: 3
Finding update package. . .
Verifying update package. . .
E:footer is wrong
Update package verification took 0.5 s (result 1).
E:Signiture verification failed
Error: 21
Install from ADB completed with status 2.
Installation aborted.
Then it tried one more time automatically with the exact same text except taking 0.6 seconds but still failing and the same error messages. Should I just download the latest package (now the June update) and try again, or did I do something wrong? The file explorer window is where I opened the powershell from and where the file was extracted to. What does error 21 mean?
Click to expand...
Click to collapse
Sorry, I don't know what error 21 means. Trying the latest image is not going to hurt at this point. Make sure you post the complete file name of the image you are trying to flash. I think there may be bootloader version mismatch that is causing the errors. Verify and post your bootloader version (fastboot menu) and OS version (recovery menu). Have you tried doing a factory reset from recovery and retrying? At this point I would keep searching "rescue ota" for tips and hints. Pasting your screen would be best, rather than retyping. Best of luck!
v12xke said:
@jet flyer
I didn't see the word "locked" or "recovery" anywhere in your post. If you are bootloader unlocked, you use fastboot to flash a full image. If you are BL locked, that should have been in your TL;DR. If you are BL locked, you can still flash a full OTA without having usb debug enabled. You just need to have the latest fastboot/adb binaries installed. Download the rescue OTA, put it in your adb folder and then from recovery mode, use the update via adb option. You do NOT need usb debug enabled to do this. You do however need a working Recovery mode. If you are BL locked and cannot access recovery that is the end of the road.
Click to expand...
Click to collapse
So I read up and Error 21 is because the bootloader is locked. I have the latest bianaries installed like you mentioned, is there something else I was missing in my process?
jet flyer said:
So I read up and Error 21 is because the bootloader is locked. I have the latest bianaries installed like you mentioned, is there something else I was missing in my process?
Click to expand...
Click to collapse
Because your bootloader is locked, you cannot flash a full image . You have to flash an OTA instead.
Secondly, the OTA you choose has to match your current bootloader version or it won't work.
Read the instructions again for flashing a rescue OTA via recovery.
1. Have you accessed the phone's recovery menu and used the update via adb option?
2. What is your current bootloader version? (recovery menu)
3. What is the full name of the file you are attempting to flash? (OTA)
https://developers.google.com/android/ota
v12xke said:
Because your bootloader is locked, you cannot flash a full image . You have to flash an OTA instead.
Secondly, the OTA you choose has to match your current bootloader version or it won't work.
Read the instructions again for flashing a rescue OTA via recovery.
1. Have you accessed the phone's recovery menu and used the update via adb option?
2. What is your current bootloader version? (recovery menu)
3. What is the full name of the file you are attempting to flash? (OTA)
https://developers.google.com/android/ota
Click to expand...
Click to collapse
ohh, I never noticed that tab at the top that says OTA, I get it now that those are needed for non-unlocked bootloaders. I see all the different versions, what does my bootloader version have to do with one of those? I only see the dates pertaining to the monthly updates, how do I know which one is for my bootloader version? I found the section specific to the Pixel 4XL
That worked!!! Thanks for the help, kinda annoyed it was as simple as that tab at the top left of the page saying OTA updated, but glad to have my phone back after 6 weeks. My Pixel 2XL did it's best but a lot of the apps I use for my action camera or drone stuff didn't even work with it haha
jet flyer said:
That worked!!! Thanks for the help, kinda annoyed it was as simple as that tab at the top left of the page saying OTA updated, but glad to have my phone back after 6 weeks. My Pixel 2XL did it's best but a lot of the apps I use for my action camera or drone stuff didn't even work with it haha
Click to expand...
Click to collapse
Happy to hear you are back up and running! Cheers.