[Q] CM9 souce code download error - Android Software/Hacking General [Developers Only]

Hi friends,
I am a noob to XDA, and have a question to ask for help.
I try to download CM9 souce code as steps:
1. repo init -u XXXXXXX -b ics
2. repo sync
But when run "repo sync", the download can't complete.
The error info is,
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 504, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/nick/android_project/cyanogen_ics/.repo/repo/subcmds/sync.py", line 200, in _FetchHelper
clone_bundle=not opt.no_clone_bundle)
File "/home/nick/android_project/cyanogen_ics/.repo/repo/project.py", line 978, in Sync_NetworkHalf
and self._ApplyCloneBundle(initial=is_new, quiet=quiet):
File "/home/nick/android_project/cyanogen_ics/.repo/repo/project.py", line 1519, in _ApplyCloneBundle
exist_dst = self._FetchBundle(bundle_url, bundle_tmp, bundle_dst, quiet)
File "/home/nick/android_project/cyanogen_ics/.repo/repo/project.py", line 1583, in _FetchBundle
raise DownloadError('%s: %s ' % (req.get_host(), str(e)))
DownloadError: android.googlesource.com: <urlopen error [Errno 110] Connection timed out>
How can I resovle this problem?
Thanks a lot!

Could anyone help me to resolve this problem?

Try again, this happens sometimes.
Sent from my LT26i using XDA

K900 said:
Try again, this happens sometimes.
Sent from my LT26i using XDA
Click to expand...
Click to collapse
Just try again, still doesn't work
Exception in thread Thread-1:9/60988), 4.41 MiB | 203 KiB/s /60988), 1.81 MiB | 169 KiB/s
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 504, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/nick/android_project/cyanogen_ics/.repo/repo/subcmds/sync.py", line 200, in _FetchHelper
clone_bundle=not opt.no_clone_bundle)
File "/home/nick/android_project/cyanogen_ics/.repo/repo/project.py", line 978, in Sync_NetworkHalf
and self._ApplyCloneBundle(initial=is_new, quiet=quiet):
File "/home/nick/android_project/cyanogen_ics/.repo/repo/project.py", line 1519, in _ApplyCloneBundle
exist_dst = self._FetchBundle(bundle_url, bundle_tmp, bundle_dst, quiet)
File "/home/nick/android_project/cyanogen_ics/.repo/repo/project.py", line 1583, in _FetchBundle
raise DownloadError('%s: %s ' % (req.get_host(), str(e)))
DownloadError: android.googlesource.com: <urlopen error [Errno 110] Connection timed out>

Related

Issues with setting up build environment

I'm looking at getting into rom cooking with this latest cyanogen fiasco, but i'm having errors getting repo set up, and i'm wondering if it's my configuration.
I'm running OS X 10.5.8, everything is updated, and i've followed the whole guide from source.android.com, up to a certain point.
when i run "repo init -u git://android.git.kernel.org/platform/manifest.git", i get this error:
Code:
Traceback (most recent call last):
File "/Users/aaron/bin/repo", line 595, in <module>
main(sys.argv[1:])
File "/Users/aaron/bin/repo", line 562, in main
_Init(args)
File "/Users/aaron/bin/repo", line 181, in _Init
_CheckGitVersion()
File "/Users/aaron/bin/repo", line 210, in _CheckGitVersion
proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/subprocess.py", line 593, in __init__
errread, errwrite)
File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/subprocess.py", line 1079, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
anyone else have this error or know how to correct it?
side note, I made a partition on an external hard drive for nabbing the source, i'm CDing to the /Volumes/Android/mydroid before i run the command. ( the partition is HFS journaled/case sensitive) and have all the port stuff installed onto my Mac hard drive
Nevermind, my path settings aren't sticking for some reason. resetting the path solved my problems

Git error...

This error happened after a repo sync, where I was downloading the entire AOSP source. There is no trace of the downloaded source...which is kind of lame as I just waited for a few hours...
But whatever...time to sleep I guess. Let me know if you have any ideas
Here's the error:
Code:
Fetching projects: 100% (158/158), done.
Traceback (most recent call last):
File "/Users/wdfowty/bin/mydroid/.repo/repo/main.py", line 235, in <module>
_Main(sys.argv[1:])
File "/Users/wdfowty/bin/mydroid/.repo/repo/main.py", line 217, in _Main
repo._Run(argv)
File "/Users/wdfowty/bin/mydroid/.repo/repo/main.py", line 123, in _Run
cmd.Execute(copts, cargs)
File "/Users/wdfowty/bin/mydroid/.repo/repo/subcmds/sync.py", line 338, in Execute
project.Sync_LocalHalf(syncbuf)
File "/Users/wdfowty/bin/mydroid/.repo/repo/project.py", line 712, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/Users/wdfowty/bin/mydroid/.repo/repo/project.py", line 1211, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/Users/wdfowty/bin/mydroid/.repo/repo/project.py", line 1356, in rev_list
p.stderr))
error.GitError: platform/external/opencore rev-list ('^61bf9af643abf0011dcf82ae8a436aeb7e8aae97', 'HEAD', '--'): fatal: bad object HEAD

repo Sync Failure "not a valid SHA1"

when trying to sync the source for a rom by existx, i get the following error:
Code:
$ repo sync -f
Fetching projects: 6% (17/274) Exception in thread Thread-19:
Traceback (most recent call last):
File "/usr/lib/python2.6/threading.py", line 532, in __bootstrap_inner
self.run()
File "/usr/lib/python2.6/threading.py", line 484, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/patrick/src/aospX/.repo/repo/subcmds/sync.py", line 200, in _FetchHelper
clone_bundle=not opt.no_clone_bundle)
File "/home/patrick/src/aospX/.repo/repo/project.py", line 985, in Sync_NetworkHalf
self._InitMRef()
File "/home/patrick/src/aospX/.repo/repo/project.py", line 1786, in _InitMRef
self._InitAnyMRef(R_M + self.manifest.branch)
File "/home/patrick/src/aospX/.repo/repo/project.py", line 1798, in _InitAnyMRef
self.bare_git.UpdateRef(ref, dst, message = msg, detach = True)
File "/home/patrick/src/aospX/.repo/repo/project.py", line 1972, in UpdateRef
self.update_ref(*cmdv)
File "/home/patrick/src/aospX/.repo/repo/project.py", line 2033, in runner
p.stderr))
GitError: platform/external/aac update-ref: fatal: 2bda038c163298531d47394bc2c09e1409c5d0db^0: not a valid SHA1
Fetching projects: 7% (20/274)
error: Exited sync due to fetch errors
I took at look at Google's git site and saw the the the SHA1 matches the one in the manifest file (se attachment).
Line from the manifest file:
Code:
<project name="platform/external/aac" path="external/aac" revision="2bda038c163298531d47394bc2c09e1409c5d0db"/>
I have tried resyncing, and the force option (-f), but nothing has worked thus far.
I'm running Ubuntu 10.04 x86_64, and I have all the required packages for building roms installed. Can anyone help?
after waiting for the next commit it is working now. not sure what was wrong.

[Q] Need help to resolve compile error CM-11.0

I am trying to build cm11 for the nabi big tab 20" I have already made a working TWRP for it and have it rooted I am coming across an error at the end of the compile that I have no idea to get around any insight would be much appreciated.
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 1132, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 1100, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files", line 543, in WriteFullOTAPackage
MakeRecoveryPatch(OPTIONS.input_tmp, output_zip, recovery_img, boot_img)
File "./build/tools/releasetools/ota_from_target_files", line 409, in MakeRecoveryPatch
boot_type, boot_device = common.GetTypeAndDevice("/boot", OPTIONS.info_dict)
TypeError: 'NoneType' object is not iterable
make: *** [/home/lmortal/android/out/target/product/dmtabnv20a/cm_dmtabnv20a-ota-3f1aec2841.zip] Error 1
Was able to get around the above error by adding "TARGET_NO_SEPARATE_RECOVERY := true" to the BoardConfig.mk.
but now I am getting a new error, have seen it mentioned a few times but haven't found any solutions to it as of yet.
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 1157, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 1125, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files", line 570, in WriteFullOTAPackage
common.CheckSize(boot_img.data, "boot.img", OPTIONS.info_dict)
File "/home/lmortal/android/build/tools/releasetools/common.py", line 511, in CheckSize
if not fs_type or not limit: return
UnboundLocalError: local variable 'fs_type' referenced before assignment
make: *** [/home/lmortal/android/out/target/product/dmtabnv20a/cm_dmtabnv20a-ota-155a6e9ebd.zip] Error 1
It is my understanding that the common.py is looking for a variable for boot.img fs_type but I have no idea where I need to put this variable. If some one could point me in the right direction I would appreciate it.
lmortal said:
Was able to get around the above error by adding "TARGET_NO_SEPARATE_RECOVERY := true" to the BoardConfig.mk.
but now I am getting a new error, have seen it mentioned a few times but haven't found any solutions to it as of yet.
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 1157, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 1125, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./build/tools/releasetools/ota_from_target_files", line 570, in WriteFullOTAPackage
common.CheckSize(boot_img.data, "boot.img", OPTIONS.info_dict)
File "/home/lmortal/android/build/tools/releasetools/common.py", line 511, in CheckSize
if not fs_type or not limit: return
UnboundLocalError: local variable 'fs_type' referenced before assignment
make: *** [/home/lmortal/android/out/target/product/dmtabnv20a/cm_dmtabnv20a-ota-155a6e9ebd.zip] Error 1
Click to expand...
Click to collapse
Just in case any one else runs accross this error it turns out it was due to incompatible recovery.fstab format.
lmortal said:
Just in case any one else runs accross this error it turns out it was due to incompatible recovery.fstab format.
Click to expand...
Click to collapse
i get the error . what should i do ?
thank you
vulture BIAN said:
i get the error . what should i do ?
thank you
Click to expand...
Click to collapse
If your issue is what his was, read up on the difference between fstab version 1 and 2 formatting differences.
aicjofs said:
If your issue is what his was, read up on the difference between fstab version 1 and 2 formatting differences.
Click to expand...
Click to collapse
i dont know. but i delete target no ****** recvery+ture .it is ok.
But my phone dont open. i think it is kernel source's problem.
i try again and again. but i am loser.
---------- Post added at 02:40 AM ---------- Previous post was at 02:37 AM ----------
vulture BIAN said:
i dont know. but i delete TARGET_NO_SEPARATE_RECOVERY := true it's ok
But my phone dont open. i think it is kernel source's problem.
i try again and again. but i am loser.
Click to expand...
Click to collapse
sorry. Some words wrong

CM13 build fails

Hi, I get following error every time I try to build CM13 from source:
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 53, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 49, in main
common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
File "/home/jens/CM/cm13.0/build/tools/releasetools/common.py", line 1443, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
File "/home/jens/CM/cm13.0/build/tools/releasetools/common.py", line 1131, in ComputePatch
p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/home/jens/CM/cm13.0/build/tools/releasetools/common.py", line 87, in Run
return subprocess.Popen(args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
build/core/Makefile:1047: recipe for target '/home/jens/CM/cm13.0/out/target/product/bacon/system/bin/install-recovery.sh' failed
make: *** [/home/jens/CM/cm13.0/out/target/product/bacon/system/bin/install-recovery.sh] Error 1
#### make failed to build some targets (02:48:32 (hh:mm:ss)) ####
Anyone willing to help?
zeetroman said:
Hi, I get following error every time I try to build CM13 from source:
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 53, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 49, in main
common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
File "/home/jens/CM/cm13.0/build/tools/releasetools/common.py", line 1443, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
File "/home/jens/CM/cm13.0/build/tools/releasetools/common.py", line 1131, in ComputePatch
p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/home/jens/CM/cm13.0/build/tools/releasetools/common.py", line 87, in Run
return subprocess.Popen(args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
build/core/Makefile:1047: recipe for target '/home/jens/CM/cm13.0/out/target/product/bacon/system/bin/install-recovery.sh' failed
make: *** [/home/jens/CM/cm13.0/out/target/product/bacon/system/bin/install-recovery.sh] Error 1
#### make failed to build some targets (02:48:32 (hh:mm:ss)) ####
Anyone willing to help?
Click to expand...
Click to collapse
Where to find your device tree, e.g. on github?
From cyanogenmod's github, yes.
zeetroman said:
From cyanogenmod's github, yes.
Click to expand...
Click to collapse
Here you will find the solution: http://forum.xda-developers.com/showthread.php?p=64482736
spezi77 said:
Here you will find the solution: http://forum.xda-developers.com/showthread.php?p=64482736
Click to expand...
Click to collapse
I found a solution earlier but thanks anyway ?
Sent from my A0001 using XDA Free mobile app
zeetroman said:
I found a solution earlier but thanks anyway
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
How did you solve the problem? I am getting the same error while building CM13 for Nexus 5X.
After including the vendor files for my phone the build was good ?

Categories

Resources