Hello everyone..
I want to learn about starting development,
so for the first step I'd like to try compiling a fresh froyo and
I've followed the instruction from Fresh froyo thread
But, I have a problem,
each time I do "repo sync", the process is never successfully finished.
I always get these error mesages :
Code:
remote: Counting objects: 1405995, done.
remote: Compressing objects: 100% (265573/265573), done.
fatal: The remote end hung up unexpectedly352.01 MiB | 46 KiB/s
fatal: early EOF
fatal: index-pack failed
error: Cannot fetch kernel
I've tried again several times but the remote always hung up unexpectedly when the download process is around 350~390MB.
Is this because of my internet connection or do I missed something?
what can I do to make this works?
Please help me
Thank you..
I've never seen exactly that, but sometimes I get network failures. Try again?
When it says "Fetching projects: xx% (yy/154)", how far does it get?
To the kernel, presumably, based on the error message. That's like 102/154 or something around there.
Related
I have a rooted HTC Desire, running Cron Mod-1.0.7.
Ever since I rooted it whatever OS I install there is no bluetooth, I even tried reflashing the stock RUU for it but that didn't work.
I did some research on this page, and decided to update the radio to 32.49.00.32U_5.11.01.27, and have tried a few different RIL versions. All have done nothing.
So I ran a log while trying to enable bt, and discovered that this happens:
"E/bluedroid( 1010): bt_enable: Timeout waiting for HCI device to come up"
So i then ran this:
"$su
# bluetoothd -n
bluetoothd[4428]: Bluetooth deamon 4.69
bluetoothd[4428]: Starting SDP server
bluetoothd[4428]: opening L2CAP socket: Operation not permitted
bluetoothd[4428]: Server initialization failed
bluetoothd[4428]: Can't open HCI socket: Operation not permitted (1)
bluetoothd[4428]: adapter_ops_setup failed
#"
I then ran "#strace bluetoothd -nd" and have a very large output file. I can post if it would be helpful.
But basically the output was that permission was denied opening a few files (/ect/bluetooth/main.conf; /dev/kmsg; /dev/socket/dbus).
Does anyone have any ideas about what the problem is and how to fix it?
Any help will be appreciated!
I need some help,
I am trying to install CM11 on my Galaxy Tab Pro. I have a macbook pro running yosemite and I cannot get heimdall to work. I followed the guide on the CM's wiki page and I get this error message: (See bold at bottom of screenshot)
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send data!Releasing device interface...
after sending the command through to push a new recovery. On CM's wiki page it says that if you encounter the error message you have to enter in these commands to disable the default usb drivers:
"On Mac OS X you may see this message: "ERROR: Claiming interface failed!". If so, you need to disable the default USB drivers with the following commands:
sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;-"
But when I enter these commands into Terminal it just comes up with this error message for all three of them:
(kernel) Kext com.apple.driver.AppleUSBCDCACMData not found for unload request.
Failed to unload com.apple.driver.AppleUSBCDCACMData - (libkern/kext) not found.
Does anyone have any insight as to why this isn't working for me. Would really like to get CM up and running on tabpro but with option currently not working and there being no other solution that works on mac's, Im kind of SOL right now. Any help would be greatly appreciated
-Thanks
I got this error while building
build/core/base_rules.mk:238: error: vendor/qcom/opensource/dataservices/rmnetctl/src: MODULE.TARGET.SHARED_LIBRARIES.librmnetctl already defined by device/motorola/addis
on/rmnetctl/src.
04:27:57 ckati failed with: exit status 1
Help me if you know how to fix this
Edit: Issue has been fixed.
Hello,
My tablet had a battery drain problem so I changed the motherboard and tried to install lineageos 14.1 again.
After replacing the motherboard, I turned on the tablet to activate usb debugging. The rom installed wasn't "complete", it looked like an interface for professionals to copy data from the old motherboard to the new... Maybe one of you knows what I'm talking about.
I flashed twrp and booted in recovery mode. Then I tried to wipe data but got errors (for instance "cache partition not found" or "hidden partition not found" or something like this. I'm sorry I didn't copy the error message :/
I tried to reboot anyway but I'm now unable to boot on the rom nor on recovery mode. I have a message : "POWER RESET or UNKNOWN UPLOAD MODE" and "ATconsole=ram loglevel=4 sec_debug. Level=1 cluster_power=1 androidboot. debug_level=0x494d sec_"
Only download mode is working.
So I'm trying to install the stock rom, downloaded from sammobile. On linux via Heimdall I got this error when flashing system.img and hidden.img :
Code:
Uploading SYSTEM
0%
1%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
On windows via Odin, I cannot flash the tar.md5 file either, it fails.
Someone could help ?
Or at least explain why I got these errors in twrp?
Thank you very much !!!!!!
Update :
I found a way to boot in recovery mode (twrp 3.3.1-klimtwifi) : unplug the battery, replug it and home + vol up + power.
So here is the error when I try to wipe data : "Failed to mound '/hidden' (Invalid argument)"
I installed the old motherboard and I'm doing a full backup on my sd card on TWRP, including EFS partition.
On the new motherboard I can't restore the backup because in twrp > restore > sd card : "No partitions selected to restore".
So here's where I am now :
I can boot into twrp but have an error message when trying to wipe data.
I have a full backup of the old motherboard with lineageos installed and working but i'm not able to restore it
Any help appreciated
And also, when I try to sideload the lineageos zip file I get this :
Code:
Starting ADB sideload feature ...
Installing zip file '/sideload/package.zip'
Target: samsung/klimtwifixx/klimtwifi:6.0.1/MMB29K/T700XXU1CRF1:user/release-keys
detected filesystem ext4 for /dev/block/platform/dw_mmc.0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Ok, I fixed the restore issue by moving the backup files to : sd_external/twrp/BACKUP/[myserialnumber]
So now I can restore all partition except System, System Image and Hidden.
Error : extractTarFork() process ended with ERROR: 255
I still can't sideload the custom rom. But the error message "Failed to mound '/hidden' (Invalid argument)" disapeared
I fixed/unbricked the tablet by using SamFirm to download a 3 files stock firmware.
I installed it with Odin and it worked like a charm.
Then I could install a custom rom
I'm following these instructions: https://wiki.lineageos.org/devices/starlte/install
But the first step fails: From within the Developer options menu, enable OEM unlock.
I don't have this option. Ok, doing this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Fine, OEM unlock appears in the menu. But I have to erase everything after enabling it - done. Now I have a completely new installed android 10. Yippie, I can start an endless loop
I try to continue without OEM unlock.
1. Installing a custom recovery using heimdall
Code:
heimdall flash --RECOVERY lineage-17.1-20200501-recovery-starlte.img --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
On the phone it's written Only official released binaries are allowed to be flashed(RECOVERY) in red letters.
2. Installing LineageOS from recovery
Code:
adb sideload lineage-17.1-20200501-nightly-starlte-signed.zip
Total xfer: 1.00x
Errors on the phone:
Code:
...
E: failed to verify whole-file signature
Update package verification took 47.2 s (result 1).
E: Signature verification failed
E: error: 21
Install from ADB completed with status 2.
Installation aborted.#1
Solved: The second try was successful.
Hi hukd, I understand that this is kind of necromancy, but do you have any idea what you did the second time? Was it perhaps 7 days after you launched into development mode? I'm having this issue, and am wondering if being in prenormal state is an issue, even after unlocking OEM.
Hey waveBidder, I would really like to help you, but I have absolutely no glue why it has worked the second time. If I did something different, it was accidental.