OK, I've been following this guide for starters.
I've got all the way to the point where you pick your build and I get this error:
Code:
Which would you like? [full-eng] 8
build/core/product_config.mk:205: *** No matches for product "cm_d2tmo". Stop.
** Don't have a product spec for: 'cm_d2tmo'
** Do you have the right repo manifest?
According to the guide, you're suppose to open up WORKING_DIRECTORY/device/samsung/d2tmo/full_d2tmo.mk and change the PRODUCT_NAME to match what the error is looking for (in this case cm_d2tmo). I've tried this. I've tried this and every variation to this as I could possibly imagine and I CANNOT get past this cursed error.
I tried changing cm.mk, I've tried changing the vendorsetup.sh itself....I've tried EVERYTHING I could think to try and I cannot get past it. I'm pulling my hair out at this point.
Any advice would be beyond appreciated.
Bump
Sent from my SGH-T999 using xda premium
To the top.
Sent from my SGH-T999 using xda premium
Related
Hi, I have searched but have not found a solution yet.
I flashed a few different roms but now want to flash back to stock which i can update through kies. I have tried several stock roms and kernals but kies keeps telling me my device cannot be updated.
Any help would be great.
See pics for my current rom.
Thank
Sent from my GT-I9100 using XDA App
Do you have the correct product code on your phone? I am from Sweden and i can type * 2767 * 438 726 4636 # in the dialer I don`t no if you can but give it a try. Look under p code and see if that code is the right for your country
I had that problem with Kies with my S8500, fixed it with some Regedit. You could try that, in Windows,
Run- Regedit- HKEY CURRENT USER- Samsung- Kies- DeviceDB- 1/2/3- There you will see Product Code on the right side window, and it must be 'XXXX' as you are having that problem, just change it to your original product code, which you will find it in your Phone Box, then DO NOT close that windows and connect to Kies, see if the problem is gone or not. There is also a Kies patch out there, which I can't remember, Google could help you.
Regards.
Thanks for ur reply,
Heres my product code how do i know if its right
cmca said:
Thanks for ur reply,
Heres my product code how do i know if its right
Click to expand...
Click to collapse
Your Product Code is written on your Box.
Cant see it on the box, my wife just got one delivered today and its not on her box either, am i being stupid should it be a sticker?
Sent from my GT-I9100 using XDA App
Yes, it's a sticker.
The only sticker on either boxes is the imei no and barcode?
Sent from my GT-I9100 using XDA App
Barcode sticker is there as well as the Product Code sticker. Don't you have a sticker which have the details like, Imported by, Manufactured place, Net Contents etc., in that sticker the top most thing written is Name of Commodity- Mobile phone and the product code right next to it, like- GT-I9100LKAINU for mine.
Regards.
No mate, no other sticker there, got it from phones 4 u unbranded when it was first launched, if that helps?
Sent from my GT-I9100 using XDA App
I have an old Milestone with CyanogenMod 7.1.
The LCD has been dead for quite a while but everything functional. I have been using androidscreencast.jnlp to control it and it has been serving me well as a test tool for my software; until today, I accidentally switch off the Developer debug mode while running the test of my software and I can't access it anymore.
If you have Milestone with CyanogenMod 7.1, I will appreciate very much if you can upload step to step images from home screen to the page of setting Developer debug so that I can follow the steps.
Thanks in advance.
I've had problems messing with things on my DX2 and the only thing that usually gets it back is sbf'ing and starting the process over. I'd say that's your best chance unless someone else can help you with this.
I sent it to have the LCD fixed and gave it to my daughter for her to learn Android programming, she had another idea, she opened up the phone with the help of iFixit, and now I am not so sure if anyone can fix it
YongkiCA said:
I sent it to have the LCD fixed and gave it to my daughter for her to learn Android programming, she had another idea, she opened up the phone with the help of iFixit, and now I am not so sure if anyone can fix it
Click to expand...
Click to collapse
Lol
Sent from my DROID X2 using xda premium
Hi Y´all.
Did a search on this but no cigar so here goes:
I´ve never had a virus. Neither desktop nor handheld.
As far as security issues go you could almost state that i am a virgin.
The other morning however when i woke up an looked at my phone screen i got this burning sensation in my..... stomach .
Apparently a terminal session was running which i am quite positive i did not start.
The attached screenshot shows the terminal window.
Readability isn´t the best but the line reads:
[email protected]:/ $ export PATH=/data/local/bin:$path
It looks like something was exported
I Googled this $path thingy and got a couple of hits about running the SDK in a Linux invironment.
Regrettably so this didn´t bring me any closer to an explanation. Much less a solution.
I now hope that on of you guys might be able to provide an explanation so i can figure out if i should be worried, and perhaps what to do about it.
EDIT: Thanks for the input. Looks like i´m worrying about nothing.
Regards
ELO
Idk, sorry, looked at the path wrong at first...
Sent from my GT-I9300 using xda premium
That is how my terminal looks and if I'm not mistaken, it said the same on my DHD. I don't think it's anything to worry about. As for the open session, maybe a chubby finger or something!
completely normal when running a terminal session.. it just sets variables so you can just type the command and don't have to type the path aswell to the command.
example:
bash
instead of:
/usr/xbin/bash
nothing to worry about
Sent from my GT-I9300 using xda premium
I've looked around xda for about 2-3 days now trying to figure out how I can read these gd .SO files in system/lib. I've came across a few different options but with no luck. I've even partioned my computer and installed Ubuntu thinking having a Linux based OS would allow me access to these files. Needless to say I'm like a fish out of water when it comes to linux. All these repositories, python, Ruby, I must of downloaded 3 gigs of [email protected]#$ and I still can't find a program that can decode these files. Could someone please at least point me in the right direction. I set out wanting to change these files but I will settle w/ simply being able to view them at this point.
sent from my ViperDNA
eriknors said:
I've looked around xda for about 2-3 days now trying to figure out how I can read these gd .SO files in system/lib. I've came across a few different options but with no luck. I've even partioned my computer and installed Ubuntu thinking having a Linux based OS would allow me access to these files. Needless to say I'm like a fish out of water when it comes to linux. All these repositories, python, Ruby, I must of downloaded 3 gigs of [email protected]#$ and I still can't find a program that can decode these files. Could someone please at least point me in the right direction. I set out wanting to change these files but I will settle w/ simply being able to view them at this point.
sent from my ViperDNA
Click to expand...
Click to collapse
You can use a hexeditor to view them
Thats pretty much it
These .so files are binaries. What are you trying to do?
Sent from my HTC6435LVW using Tapatalk 2
beaups said:
These .so files are binaries. What are you trying to do?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Im trying to get lyapotas musicmod for the one x to be fully functional on our phone. Im 75% there but I just wanted to see what's in the lib files he included in his zip file to see how they correspond with the lib files in our phone. Im finding out that changing them is damn near impossible so what ive got working will most likely be it
sent from my ViperDNA
i don't know why i can't unlock,I think L9 can't download token from lg??
OR Can unlock with boot.img backup from anyone unlocked bootloader??
sorry about my english
LG is notorious for removing fastboot, which is basically the way to access the bootloader, with an OTA update. Not only do they remove it, they encrypt the bootloader for good measure.
Sent from my LG-P769 using XDA Premium 4 mobile app
I'm still attempting this myself, current test involves proxying through Europe, thought maybe lg started filtering ip's from the us models running euro roms to prevent the token from unlocking it. No evidence of it but just a thought. I'm even seeing if a few of my coder friends can sift through the bootloader machine code after I disassembled it, but I wouldn't get your hopes up, machine code isn't exactly a specialty of theirs, wish I had that nice ida convert back to c option, c code would actually be useful in this situation.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I'm still attempting this myself, current test involves proxying through Europe, thought maybe lg started filtering ip's from the us models running euro roms to prevent the token from unlocking it. No evidence of it but just a thought. I'm even seeing if a few of my coder friends can sift through the bootloader machine code after I disassembled it, but I wouldn't get your hopes up, machine code isn't exactly a specialty of theirs, wish I had that nice ida convert back to c option, c code would actually be useful in this situation.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
How about this thing my brother just mentioned to me.... https://play.google.com/store/apps/details?id=com.vpnoneclick.android
I don't know what it does so don't ask me. At this point, this all goes over my head. :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Ah that's another form of proxying, right now I just am using proxydroid and a UK proxy server I found. I think the most interesting point made in the latest tutorial for this is that it says you must have WiFi and data on, but from what I saw, data disconnects when WiFi is connected I think. Idk, I'm trying it both ways. This whole process is a pita. And the people in the kfhd community think their bootloader exploiting process is hard...
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Ah that's another form of proxying, right now I just am using proxydroid and a UK proxy server I found.
Click to expand...
Click to collapse
I am currently in Europe with the P769, and I've tried unlocking, however, I don't believe the token gets sent when one is roaming (at least I was not able to get the unlock). Not sure, if I used the EU mirrored ROM, but I gave up after handling the glitchy screen for a while.
Let me know, if you make progress, and for confirmation purposes, I could try to sim-unlock my phone and flash EU rom and try again. Then it would not be roaming, so maybe it would work...
ramonkahn said:
I am currently in Europe with the P769, and I've tried unlocking, however, I don't believe the token gets sent when one is roaming (at least I was not able to get the unlock). Not sure, if I used the EU mirrored ROM, but I gave up after handling the glitchy screen for a while.
Let me know, if you make progress, and for confirmation purposes, I could try to sim-unlock my phone and flash EU rom and try again. Then it would not be roaming, so maybe it would work...
Click to expand...
Click to collapse
FYI, I already sim unlocked and used a prepaid sim from Puerto Rico. My friend from there let me use his sim to try and unlock the bootloader. It didn't work so there goes that idea.
Sent from my LG-P769 using XDA Premium 4 mobile app
Maybe my efforts to decompile the bootloader will get me somewhere. As is though I can only get machine code, I found a program I thought might do the trick that was just released recently called fracture but I guess a u-boot doesn't go with standard binary formats in terms of the header, or maybe its signature is getting in the way, Idk this is a bit above the kinda stuff I usually do. I might poke around and chat with some RC's about this.
Sent from my Amazon Kindle Fire HD using Tapatalk