• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Building CyanogenMod for Samsung Galaxy Note 10.1 N8000 (GSM)

Search This thread

Red Planet

Member
Nov 18, 2011
15
0
I am building CyanogenMod for my Samsung Galaxy Note 10.1 N8000. Here is the guide.
When I typed
Code:
breakfast n8000
, the output was as follows.

Code:
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/n8000/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_n8000".  Stop.
Device n8000 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
  File "build/tools/roomservice.py", line 76, in <module>
    result = json.loads(urllib.request.urlopen(githubreq).read().decode())
  File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
    return _opener.open(url, data, timeout)
  File "/usr/lib/python2.7/urllib2.py", line 406, in open
    response = meth(req, response)
  File "/usr/lib/python2.7/urllib2.py", line 519, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.7/urllib2.py", line 444, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 527, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
ls: cannot access device/*/n8000/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_n8000".  Stop.

** Don't have a product spec for: 'cm_n8000'
** Do you have the right repo manifest?

I executed breakfast without a device as the guide suggests.

If you do not put a device, the script will output a list of available devices to build for (limited to those CM builds nightlies for, which isn't necessarily complete), and you can then choose yours.

And there was nothing containing n8000

Code:
including vendor/cm/vendorsetup.sh

You're building on Linux

Breakfast menu... pick a combo:
 1. full-eng 			 19. cm_e980-userdebug 		 37. cm_jfltexx-userdebug 	 55. cm_serranoltexx-userdebug 
 2. cm_apexqtmo-userdebug 	 20. cm_evita-userdebug 	 38. cm_m7att-userdebug 	 56. cm_skyrocket-userdebug 
 3. cm_captivatemtd-userdebug 	 21. cm_exhilarate-userdebug 	 39. cm_m7spr-userdebug 	 57. cm_superior-userdebug 
 4. cm_crespo-userdebug 	 22. cm_flo-userdebug 		 40. cm_m7tmo-userdebug 	 58. cm_t0lte-userdebug 
 5. cm_d2att-userdebug 		 23. cm_galaxysbmtd-userdebug 	 41. cm_m7ul-userdebug 		 59. cm_tilapia-userdebug 
 6. cm_d2cri-userdebug 		 24. cm_galaxysmtd-userdebug 	 42. cm_m7vzw-userdebug 	 60. cm_toroplus-userdebug 
 7. cm_d2mtr-userdebug 		 25. cm_grouper-userdebug 	 43. cm_maguro-userdebug 	 61. cm_toro-userdebug 
 8. cm_d2spr-userdebug 		 26. cm_hammerhead-userdebug 	 44. cm_mako-userdebug 		 62. cm_tsubasa-userdebug 
 9. cm_d2tmo-userdebug 		 27. cm_hercules-userdebug 	 45. cm_manta-userdebug 	 63. cm_ville-userdebug 
 10. cm_d2usc-userdebug 	 28. cm_i9300-userdebug 	 46. cm_mb886-userdebug 	 64. cm_vs980-userdebug 
 11. cm_d2vzw-userdebug 	 29. cm_jflteatt-userdebug 	 47. cm_mint-userdebug 		 65. cm_xt897-userdebug 
 12. cm_d800-userdebug 		 30. cm_jfltecan-userdebug 	 48. cm_odin-userdebug 		 66. cm_xt897c-userdebug 
 13. cm_d801-userdebug 		 31. cm_jfltecri-userdebug 	 49. cm_otter-userdebug 	 67. cm_xt907-userdebug 
 14. cm_d802-userdebug 		 32. cm_jfltecsp-userdebug 	 50. cm_otter2-userdebug 	 68. cm_xt925-userdebug 
 15. cm_deb-userdebug 		 33. cm_jfltespr-userdebug 	 51. cm_p1-userdebug 		 69. cm_xt926-userdebug 
 16. cm_dlx-userdebug 		 34. cm_jfltetmo-userdebug 	 52. cm_pollux-userdebug 	 70. cm_yuga-userdebug 
 17. cm_dogo-userdebug 		 35. cm_jflteusc-userdebug 	 53. cm_pollux_windy-userdebug 
 18. cm_e975-userdebug 		 36. cm_jfltevzw-userdebug 	 54. cm_serrano3gxx-userdebug 
... and don't forget the bacon!

Which would you like? [aosp_arm-eng]

Then I tried lunch

It’s used EXACTLY like breakfast, the only difference being the choices you have to build with it, and how it configures the device. Using lunch, you can choose non-official or non-standard builds for your device

The output was the same.

There is nothing about N8000 again.
Has anybody built CyanogenMod Android for Samsung Galaxy Note 10.1 N8000 successfully?
 
Last edited:

theatomizer90

Senior Member
Dec 21, 2012
71
12
Have you included the 8013 as well I believe the only difference is the cellular radio file which I believe can be added for your device?

tubas..... tubas everywhere....