No matter what downloaded package I tried to open with heimdall to install on my Captivate (i896), heimdall gave me the error:
Tar header contained and invalid file size
I installed ClockworkMod, and rooted the phone, had an issue and installed the stock Rogers (Canada) firmware. Since then, heimdall isn't detecting my phone at all.
$ heimdall detect
Failed to detect compatible download-mode device.
I'm willing to work with any of the heimdall developers to resolve these two issues, or does anyone have any ideas on how to resolve?
Thanks in advance!
acanuck said:
No matter what downloaded package I tried to open with heimdall to install on my Captivate (i896), heimdall gave me the error:
Tar header contained and invalid file size
I installed ClockworkMod, and rooted the phone, had an issue and installed the stock Rogers (Canada) firmware. Since then, heimdall isn't detecting my phone at all.
$ heimdall detect
Failed to detect compatible download-mode device.
I'm willing to work with any of the heimdall developers to resolve these two issues, or does anyone have any ideas on how to resolve?
Thanks in advance!
Click to expand...
Click to collapse
Firstly, please before you do anything else make sure you're using Heimdall 1.3.1 instead of 1.3.2. 1.3.2 introduced issues for some previously well-supported devices. The issues introduced shouldn't hard-brick any devices, but it can cause flashes to fail, and that can be a daunting experience.
The error you've received seems to indicate that the type of file you're trying to flash is not a Heimdall Firmware Package. Chances are the file you have is an archive that when extracted contains 3 other archives for use with Odin. Heimdall Firmware Packages are much simpler than this but unfortunately haven't been heavily adopted by the community just yet.
Nonetheless, Heimdall is extremely flexible. If you wish to flash the files you've downloaded please refer to the README included in the Heimdall DMG (also available here). In particular please refer to the section on performing a Custom Firmware Flash.
However, before you do all that you're going to need to ensure your device is being detected. Aside from the obvious "make sure you're in download mode" there are several reasons why you device may not be detected in OS X. They are as follows:
1. Permissions/ownership are set incorrectly for the codeless kext used by Heimdall. Open a terminal and run the following in order to ensure this is not the problem:
Code:
sudo chown -R root:wheel /System/Library/Extensions/heimdall.kext/
sudo chmod 755 /System/Library/Extensions/heimdall.kext/
sudo chmod 0644 /System/Library/Extensions/heimdall.kext/Contents/Info.plist
After doing this you will need to reboot your machine.
2. There are other kexts on your system interfering with Heimdall's codeless kext. Typically this would occur if you've tried to install Kies for Mac as Samsung's kernel extensions are given higher priority. If the Samsung's kext does exist it can be removed using the following command:
Code:
sudo rm -rf /System/Library/Extensions/ssuddrv.kext/
Again, after running this command you will be required to reboot your machine.
3. Your running an old faulty bootloader...
This is a much more serious problem. Samsung originally released several devices with a secondary bootloader that included a faulty implementation of the USB protocol. Unfortunately this means OS X will be totally unable to recognise your device. As such you will have to flash your phone using either Windows or Linux. However, once you flash a working secondary bootloader onto your device you will be able to use OS X for any other flashing later on.
Once you've completed 1 and 2 from above you'll be able to ask Heimdall to detect your device again. If it doesn't work this time around chances are you're running a faulty secondary bootloader.
$ heimdall version
v1.3.2
I did have the ssuddrv.kext/, which once I deleted and rebooted also asked me about tethering upon USB connect. Also, the heimdall Info.plist from was 755 permissions for some reason. This is all resolved now.
adb is showing the device, but heimdall is still not.
I was able to flash new kernels using heimdall flash on the command line a few days ago, until I went back to a stock image. My issue is, without being able to flash the ClockworkMod recovery kernel now, using heimdall, I'm not sure how to move forward. Perhaps I can can install a zImage with adb or something else? There doesn't appear (from reading the forums) to be FASTBOOT on the Captivate.
There must be a way I can boot another zImage using osx as I've done before?
Related
I got my Cap to stock GB 2.3.5 finally, after it being in the "firmware upgrade fail" screen. I flashed the file with no bootloader, since I was already on GB before. All went well until I tried to get rooted through Super One Click, short fuse 1.9.1.0. I got everything started and tapped the Captivate tab and it went through the whole process and in the end, failed . Once more, same thing. Tried universal tab, driver check, some kind of windows pop up saying either stop now or sect continue. I continued and tapped root tab and killing adb, starting adb, daemon not running, daemon started successfully waiting for device, failed to get root. One more try, same thing. Now my battery is showing very low, like in the red low. So I left the phone plugged in the wall charger while I reinstalled the Samsung drivers, and that is when I noticed the phone went black and when I connected it to the laptop to try Super One Click with new drivers ans the laptop doesn't recognize the device. Says no drivers are installed, etc...,etc... . One click starts though recognizing the phone and starts trying the root sequence and everything is good until after daemon starts successfully, it says OK, waiting for device... - that's it. I can't get it into download mode even with with the USB jig. I had already sent this phone in and had the unbrickable mod done by Josh at Mobiletech video. So, does anyone have any suggestions or answers, as to how I get this phone working
Use this...[Utility]KK4 Easy Root to get Root.
Sent from my SAMSUNG-SGH-I777 using xda premium
Thanks for that link. I've got bigger issues than trying to get root though. My phone won't go into download, even when I use a USB jig. I have nothing but a black screen. I can't get recovery, my computer recognizes it but only as a Samsung USB device with no drivers installed. I've installed drivers from Kies, from Samsung, and from Gingerbread rom. I have unbutu installed, but I have no idea how to input commands. I have had the phone repaired and had the unbrickable mod performed on it by Josh at Mobiletechvideo back in February. I can't get unbrickable resurrector to work because I don't know how to run Linux / Unbutu. So now I'm out of ideas/options that I'm capable of implementing. If anyone that may read this has an idea of what I should do next, please let me know.
Sent from my SGH-T989 using xda premium
I did a quick google search on this unbrickable resurrector and it looks to be just a .jar file that is able to discover what mode the captivate is in and correct issues. I do not have experience with this exact program but I did find a thread with documentation / how-to. You should be able to follow those instructions + adapt for your device. If you have any specific questions pertaining to ubuntu / linux, let me know.
http://forum.xda-developers.com/showthread.php?t=1397393
broknbottle said:
I did a quick google search on this unbrickable resurrector and it looks to be just a .jar file that is able to discover what mode the captivate is in and correct issues. I do not have experience with this exact program but I did find a thread with documentation / how-to. You should be able to follow those instructions + adapt for your device. If you have any specific questions pertaining to ubuntu / linux, let me know.
http://forum.xda-developers.com/showthread.php?t=1397393
Click to expand...
Click to collapse
I appreciate you trying to help. I hit the "Thanks " button so you will have your first on your meter. LOL. I already read that post and it didn't quite get me what I needed unfortunately. I may have to send it back to Josh at MobileTechVideo and let him see what he can do. But I'm still trying to do it myself in the meantime.
khkaiser13 said:
I appreciate you trying to help. I hit the "Thanks " button so you will have your first on your meter. LOL. I already read that post and it didn't quite get me what I needed unfortunately. I may have to send it back to Josh at MobileTechVideo and let him see what he can do. But I'm still trying to do it myself in the meantime.
Click to expand...
Click to collapse
Do you have java & the .jar file downloaded? If so just open up a terminal and try these commands, substituting file for the actual filename
Code:
cd ~/Downloads
-- This is assuming you've left the .jar file in Downloads directory
Code:
chmod +x file.jar
-- This will give the file execute permissions
Code:
java -jar file.jar
-- This will run the java jar file.
You will need java installed, If you don't have it installed run these commands.
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
Code:
sudo java -version
-- will display the version of java installed.
Let me know if you need anymore help.
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
RealBorg said:
I have now successfully rooted my device by downloading the firmware, unpacking system.img.md5, adding the su binary, making an ext4 sparse image and installing that to the device using heimdall. Problem was, that on my first attempts the system became unstable, the UI restarted repeatedly, especially when manually switching WiFi and Data Mode. After double and triple checking everything I found that I could create a perfectly stable system image by following the same steps but just not adding the su binary. One further attempt placing the su binary in /system/usr/bin (does not exist) and using it as a backdoor to install the binary to /system/bin/su I now seem to have a stable and rooted system.
It appears that something has been detecting my initial and straightforward attempt to tamper with the system image and made the system to become unstable. I have seen a lot of errors from PackageManager in my logs but nothing conclusive.
Tom
Click to expand...
Click to collapse
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Sorry for bad English
johnnybr said:
Hi Tom! I managed to root my s advance with this method, but in guide that I have read, was said that I should put the su binary on "/system/xbin/". I used that steps, by Xanonus. Over here everything gone right and after flashing, I got Supersu from Play store. If help you, please thanks Xanonus.
Click to expand...
Click to collapse
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
/bin/su is the location of the su binary on every Unix system and Superuser also installs the su binary to /system/bin/su. I wonder if it would make a difference (avoid instability) to place it in /system/xbin/su.
Tom
RealBorg said:
Xanonus unnecessarily copies everything out from system to new_system, you can just add the su binary to the loop mounted image.
Click to expand...
Click to collapse
I really suspected that, like you said, part of all that stuff was unnecessary.
About the place of su binary, well, I just wanna to help. I don't know nothing about linux and less of unix. But normally, while you are dealing with this kind of stuff, you should try. Cause things sometimes work when they shouldn't and don't work like they should. I can only say: God knows why...:silly:
Thread moved to General section, post in the relevant section next time.
Why use Heimdall to flash ? Odin3 works better
"None forget the bite.....of Viper...."
CallMeVentus said:
Why use Heimdall to flash ? Odin3 works better
Click to expand...
Click to collapse
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
RealBorg said:
heimdall is the method of choice when you are on linux and works like a charm
much easier than Odin which needs the image to be put into a .tar.md5 file
Tom
Click to expand...
Click to collapse
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
johnnybr said:
I have tried heimdall but I can't make it work on Windows (7 X64, it never get to comunicate between pc and mobile). So when I was messing with my rom I have to try zillions of ways to make a image to work with Odin. In the end, make the image with ext4_utils and compress with tar on my virtual machine running ubuntu did the trick. If you don't put any md5sum verification or "md5" in the name of the file, Odin never check the file.
This was me trying to root hahhaa!!
I guess everyone that want play with Android should learn to use linux. ubuntu at least. I intend to learn linux, but I can't right now.
Sorry, crap english from google translator!
Click to expand...
Click to collapse
Seriously?
How can hemidall work on windows when its designed for linux!
Sent from my GT-I9070 using xda premium
Shaaan said:
Seriously?
How can hemidall work on windows when its designed for linux!
Click to expand...
Click to collapse
Actually it has a windows version. Even Mac has a version of Heimdall. Take a look: http://www.glassechidna.com.au/products/heimdall/
Indeed I can't make it work... Perhaps on windows x86 it can work...
Information is hard to find nowadays. Finding the info you need is one thing, but comprehending it can be difficult sometimes. Since I came from a military background, I like to do the same here and hopefully answer all your Heimdall curiosity.
HEIMDALL IN GENERAL
I consider it as Odin evil twin. Simply just 2 different operating personality. In this case, Odin uses Window, and Heimdall uses Linux
Will not work without a proper USB software. Odin uses manufacture that either achieve through your Samsung devices, Kies or Samsung. Hiemdall uses Zadig to configure it USB port channel.,
Last requirement. Correct operating system with the most compatible version for your system. (Mac-note3), (S3-win) etc.. Newer isn't always better. Check with developer website to get the correct version along with others require adds on for your system.
Extra Note: When verifying if you are using the correct Heimdall for your computer, make sure you right click on Heimdall Front End and go into properties. Just because you downloaded for Win/Mac doesn't mean the setting are set to a specific OS. Should you have to make changes, make sure you restart your computer or restart the application (advance user) for changes to take place[/B]
ATT GLX NT3 HEIMDALL
USB you need will be MSM8960. This is the Linux code for your phone download mode. If you are able to locate and install this on Zadig, then the problem is not at your USB port. *Note: There are more than one driver within MSM8960. The recommended dr is not always the working one. Don't forget to check out the others. (Libusb, winucd, etc)
Heimdall is running as device Admin. This step doesn't make much difference. If you are troubleshooting, I would consider every single possibilities.
Make sure your download mode is listing the correct firmware for your device. People do bad flash, wrong installation, all kind of mix and match. If you somehow, got the wrong version of download mode into your operating system, or viceversa. You're on your own.
Hiemdall is a Linux program, so if you're familiar with ADB and already have that setup on your OS. You won't even need to go through the USB process for detection. ADB is a better method for Heimdall, but i'm not a Linux guy. So when my device wasn't detecting. I had to try a lot of different method. And that's when I came up with the 3 basic requirement.
Along with the basic, there are a few others thing you can look at should you're still unable to connect.
1. Only one can be use between Heimdall and Odin. If your Odin com port is connected, then you need to install/re-install usb for heimdall, or it not config correctly. It's easier for ODin to detect your phone since it is working directly with phone device. Not so much with Heimdall, since you have to fetch all the right tools to get it to work.
2. Most detection issues should be fix by correcting to the proper Usb drive, and the correct Heimdall version for your phone. Also, try to get the software from the Heimdall website.
TROUBLESHOOT PERTAIN TO evilpotatoman Restore for MJ5--Doesn't trip Knox post
1. I had to run HD front end as admin
2. Change the operating system within HD front end properties to my comp OS.
3. Finally got the device to detect, but it wasn't the right driver because HD was not able to flash files to my phone.
4. Open Zadig again, and navigate to( Libusb 1.2.5) and install the driver under MSM8960.
MSM8960 has 3 driver within it. One of the is Window something, and the other 2 is the Libusb. The window driver doesn't always work, so try the others if it gives you a problem. In my case, I had to install libusb and that got me to complete the rest of the process on the tutorial.
Hopefully this help, or at least provide you with better details so you can guide your self to the solutions.
Don't forget to thank.
In the past 3 months or so I noticed that my Mi5 3GB 32GB is not recognized by my PC anymore. I didn't care too much because I hardly connect my phone to PC.
I was running the lastest xiaomi.eu Rom unrooted.
So on Thursday, I deleted my OS by mistake, therefore I do not get past the Mi Logo.
I can boot into TWRP Recovery & Fastboot however, there is not code when using CMD adb/fastboot devices such as 1cwe3f23.
Also, I read about the EOL method aka test point method, to force a connection as Qualcomm driver with no success. Different PCS dont recognize any drivers.
The battery is not an issue because I can easily charge my phone to 100% and it can hold its charge, therefore I do not think it is a battery related issue.
What i did so far :
- used 3 differenct USB C cables and PC -> phone still not recognized
- Installed all lastest driver on Drivers -> phone still not recognized
- tried to use the test points method -> phone still not recognized
- tried Miflash tool -> phone is still not recognized
- tried Mi PC Guide -> didn't work either
Then I read somewhere that I can use a OTG cable with a pen drive
- OTG storage is not recognized in TWRP recovery and cannot be selected. [OTG STORAGE 0MB even if different pen drives are connected]
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Please help me out since I really struggling with this problem for the past 7 days and I'm desperate now for any kind of help.
Greetings and thanks in advance.
amando1991 said:
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Click to expand...
Click to collapse
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Hi bro
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
goodluck
Sory bad englis
moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
I did as you recommended and used Ubuntu. However also there the system didn't recognize the phone when plugged. It may because I am not fully familiar with Ubuntu. I would appreciate if you could point me in the direction of a tutorial.
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
Click to expand...
Click to collapse
could you be more precise please? How did you overcome not having a PC conncetion?
Currently, I am not able to transfer any kind of data to the phone either by PC or OTG. Furthermore, the internal storage is completely empty after wiping everything by mistake.
I have twrp working fine, but without any data on the device, I cannot use it. Also, the device only stays in fastboot for roughly 20 secs before it turns off.
any help is welcomed. Thank you
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
amando1991 said:
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
Click to expand...
Click to collapse
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
moo113 said:
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
Click to expand...
Click to collapse
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
amando1991 said:
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
Click to expand...
Click to collapse
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
moo113 said:
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
Click to expand...
Click to collapse
OMFG!!! First of all, thank you for support and your patience. I really appreciate it.
HOWEVER, all it was is that the USB PORT was full of dust( literally tons!) which appears to have allowed to charge the phone but seemed to have cloaked up some part of the responsibile for a usb connection to a computer.
Stupid me should have known this because the usb port was kinda wobbly which I had mistaken for degradation using the phone for almost 2 years
MANY THANKS!
moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
Hey , I was researching about my issue and came up to this. I'd be really glad if you can sort me out with this. I have the same mobile , by mistakenly wiped out the phone including the internal storage , my pc does not detect the device , and whenever i go to fastboot mode to try something like miflash , it goes back to twrp after 15 seconds. Also , i tried several OTG's but none of them get detected on TWRP , and I am stuck on this thing for almost a week now . Please guide me on how to sort this out . i basically just downloaded adb files , miflash , etc from the internet and never reinstalled them. also i used several usb c cables to connect to pc and even then device manager does not detect it . thank you . i would really appreciate your reply.
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
neo_lithic3K said:
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
Click to expand...
Click to collapse
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
bignu77 said:
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
Click to expand...
Click to collapse
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
dragynbane222 said:
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
Click to expand...
Click to collapse
My bad, I worded that wrong it only happens once in the custom recovery and try to ADB sideload the rom, i get that error.
Fastboot boot.img via bootloader works fine.
My trouble starts one in custom recovery and it shows "emulator-5554". Please see attachment.
Thanks
bignu77 said:
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
Click to expand...
Click to collapse
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for clearing that up.
The only other thing connected it the cordless mouse reciever.
I also did update sdk platform. as shown in the attached. Yes i am trying to apply update from adb and then sideload command I also tried typing the specific file name instead of the whole path.
It only happens in adb mode. Flashing via fastboot works fine with no emulator error.
Ive been flashing for months using the standard adb method with no hiccups. Now im getting this error
SOLVED
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
bignu77 said:
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
Click to expand...
Click to collapse
Figured it something related to that, I'm happy you fixed it though, enjoy the ROM.:good: