I ran into this article yesterday, How to Flash CyanogenMod 7 ROM Samsung Captivate AT&T, and felt it was about time to learn about this. Plenty of you have already ROOTED your phones, and know from experience, what to do. But, I don't. Right now, I'm stuck with the options of accepting things don't work right, because of AT'T's unwillingness, or inabilility, to correct the issues I have, or reinsiall new, and lose all I've put on, or send back to Samsung for repair, and have them lose all I have on it, or try Rooting and adding a ROM, that may solve my issues. But to do that, I need a little help in understanding it.
First, if I try and run a program, like CyanogenMod 7, and it doesn't work correctly, snd screws up my phone, is there a way I can reinstall Android, and start over, or is that the proverbial kiss of death for my Captivate, and I'm stuck with it like that?
Second, is this the right ROM to try? AT&T can't fix my BLOCKS, of UNKNOWN APPS. The Settings change is easy, you click on activating Unknown, in Application settings..., unless you have no UNKNOWN, to choose. Also, in MMS settings, AT&T shows in a tutorial, that you have the option, of activating Delivery Report and Read Report. It shows this as plain as day, on that tutorial for the Captivate, yet mine, has NEITHER OF THOSE OPTIONS. Also, to TURN ON EDGE, the setting is missing, so I can't activate EDGE, which I guess is no big thing, since the towers AT&T has for us to connect with, THAT ARE 2G, are in such poor condition, no one can connect to them. Thank you, WIFI, for helping me get, ONLINE. Will this, or other ROM's, solve this for me?
If there are any suggestions of how to do this, and what to use, I'd appreciate hearing it from you. Again, I thank any effort, to help me.
1.cm 7 would not be the best rom to flash for your first time.
2. All roms are android, you are running at&t/samsung version of an android rom...
3. Yes you can get back to your stock rom if you don't like/something goes wrong (other than a bad bootloader flash)
4.all custom roms have all the blocking done by at&t removed so switching to 2g(edge) is possible and also faster 3g speeds known as hspa. And unknown sources is in the settings so you can install apps from outside the market.
5.the threads at the top of every section with a little thumb tacks are called stickies, give those a read through.
Like he said above. If you want the pretty much stock experience that your used to but want it fixed then I would suggest starting off with Cognition 4.4 or whatever it is now.
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
From newbie to a newbie, I took the advice of others and read threads for atleast a month before I flashed my first rom. My choice was Andromeda3, It has a written tutorial and a video on how to from start to finish. From what tools or apps you will need and how to use them , I watched that atleast 6 times and also while I was flashing the kernel and the rom. It may have been overkill but my flash was perfect and I'm real happy with my phone now. You may not go with the same rom I did but do your self a favor and do what I did to prepare for your first flash.
Hi there,
I believe I'm not the only one who tried to connect a bluetooth keyboard to the moto x. After a lot of research I found that it is just as easy as connecting a bluetooth device. The problem is that the Apple Keyboard doesn't work.
(since it is my first time, xda doesn't allow me to put images, so here are the links
imgur. com/v0Py8CR,5uCefZo
imgur. com/v0Py8CR,5uCefZo#1
Here you can see that the keyboard is seen by the phone, and I can pair it by typing the numbers on the keyboard. But after it is paired, and even though it is checked as input device I get no answer from the keyboard when I try to type.
I'd be really happy if anyone had a solution for this.
this is my first time posting here, so I hope that I am posting in the right section.
alexluz said:
after it is paired, and even though it is checked as input device I get no answer from the keyboard when I try to type.
Click to expand...
Click to collapse
Ooh it looks like you might have walked into a hornet's nest, a touchy issue that has been around a while and is yet to be resolved. See here: https://code.google.com/p/android/issues/detail?id=58202 and here: http://code.google.com/p/android/issues/detail?id=62740 and here: http://android.stackexchange.com/qu...ple-bluetooth-keyboard-paired-but-not-working
Be sure to search for a better solution, and I hope someone else can shed some light on the issue, but I see only these options currently:
1) wait for Android 5.0 Lollipop, it might fix the issue. Shouldn't be too long a wait either.
2) if you have root or you can root, you can try using this app, no idea if it does anything: https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en
3) the answer presented in the stackexchange link i mentioned above. unfortunately the solution there is getting a different version Apple keyboard hardware.
good luck.
dtg7 said:
Be sure to search for a better solution, and I hope someone else can shed some light on the issue, but I see only these options currently:
1) wait for Android 5.0 Lollipop, it might fix the issue. Shouldn't be too long a wait either.
2) if you have root or you can root, you can try using this app, no idea if it does anything:
3) the answer presented in the stackexchange link i mentioned above. unfortunately the solution there is getting a different version Apple keyboard hardware.
good luck.
Click to expand...
Click to collapse
Yes, I saw that and it made me really sad. I tried here already knowing about that with hope that someone had a solution.
But thank you anyway.
TLDR: only the 2011 Apple Wireless Keyboard has this problem, and without a solution (until now).
Hey guys, I have successfully modified the firmware 1.03 for NEX4100 in order to flash on my NEX4000. Long story short it worked! however the ONLY feature that does not work is the BT Audio connection. I can't stream audio or mic with this firmware.
Android Auto works though. My original thread on AVIC411 is here.
http://avic411.com/index.php?/topic/80945-upgrading-nex4000-to-nex4100-work-in-progress/
I am wondering if there is anyone here that is willing to dive into the firmware with me to see if we can't fix this one last problem. If someone is interested in helping me complete this transition it would be much appreciated and would make a TON of people happy as I am so close to having it 100% functional. Also please feel free to discuss this here as well as I feel the conversation might move faster here at XDA.
Man, you deserve a cookie Awesome job, for sure there are a lot of peoples that will appreciate it
brainscollector said:
Man, you deserve a cookie Awesome job, for sure there are a lot of peoples that will appreciate it
Click to expand...
Click to collapse
Thanks, it was easier than I thought at first, I over did it the first time around. I went ahead and posted my method on the forum above since its relatively straight forward however the ONLY problem at the moment is BT Audio. It seems the BT Audio toggle option in the NEX menu is locked in the "off" position and this setting is apart of the USERDATA folder of the FW update and I can't / don't know how to read this file (its a .prj format).
If anyone here with a smarter brain than I is willing to take a look at that file and see if there is anything that indicates we can fix this please let me know!
Android Auto Conversation
I have the pioneer AVH-X4700BS if it's any way you could make it work on that unit as well I'll be glad to try and help figure out some things as far as bugs or kinks that need to be ironed out. I've looked for the firmware update online but it's no where to be found and pioneer has no logical explanation as to why they didn't update at 2014/2015 models(I've called and asked) so I'll definitely contribute any way that I can.
Yeah get it to work on AVIC models while you're at too please ?
Hi, I have a 4000NEX and would love to try this out. Where can your firmware be downloaded?
iphonedaddy said:
Hi, I have a 4000NEX and would love to try this out. Where can your firmware be downloaded?
Click to expand...
Click to collapse
http://avic411.com/index.php?/topic/80945-upgrading-nex4000-to-nex4100-work-in-progress/
http://avic411.com/index.php?/topic/81468-the-avic-development-mod/?p=334365
Covert_Death said:
Hey guys, I have successfully modified the firmware 1.03 for NEX4100 in order to flash on my NEX4000. Long story short it worked! however the ONLY feature that does not work is the BT Audio connection. I can't stream audio or mic with this firmware.
Android Auto works though. My original thread on AVIC411 is here.
http://avic411.com/index.php?/topic/80945-upgrading-nex4000-to-nex4100-work-in-progress/
I am wondering if there is anyone here that is willing to dive into the firmware with me to see if we can't fix this one last problem. If someone is interested in helping me complete this transition it would be much appreciated and would make a TON of people happy as I am so close to having it 100% functional. Also please feel free to discuss this here as well as I feel the conversation might move faster here at XDA.
Click to expand...
Click to collapse
Any chance you or someone else can reupload the firmware for the 4000/4100 update?
I ended up trying this myself by downloading both sets of firmware and renaming the files via a bash shell script. The update went fine on my head unit, but like everyone else, I had no Bluetooth audio. This is so frustrating. Out of desperation, I even tried the "150" files renamed to "140" while leaving Bluetooth firmware files out of the update completely. Still the same result.
Hi all, I'm certain this info can be found in tons of places on this forum, but I'm brand-new (first post, woo!) and that amount of info here is a little overwhelming.
So, first thing's first: Pumpkin's forum is crap, the one moderator there either doesn't allow posts about android upgrades or flatly denies it isn't possible (I know they're lying).
I have a Pumpkin RQ0248, using an RK3188 cpu and still running Android 4.4.4. I've learned here that it's also known as "MTCB-KLD6-v2.85". It seems like my car radio CAN be upgraded to Android 5.1 (which is awesome), but I'd just like to check some facts with the experienced folks here:
- I download an "Update.img" file to a... microSD card? USB? (Does it even matter? Pumpkin's site says microSD in the maps slot).
- I run the System update button (or whatever it's called) and select the above image file. Let it do it's thing. It'll reboot, at which point I do a factory setting reset? I believe so.
- The file I've downloaded is "KLD_LP_rk3188_p_2016_05_11", I think it's the right one, but I want to be certain. Perhaps there's an even newer one?
- While poking around (and getting confused) I saw some people claim their radio app sometimes would stop working? Is that a regular thing? I know how to enter the "factory" settings (using PW 126) and saw that some people just had to change their radio chip version? Is that trial and error or is there a specific one I should use for mine?
Thanks for all the help in advance! And sorry for the newbie questions!
Anyone? Please lend a hand... I'm very nervous about flashing (and possibly bricking) my car radio...
cmetaphor said:
Anyone? Please lend a hand... I'm very nervous about flashing (and possibly bricking) my car radio...
Click to expand...
Click to collapse
You need to take pictures of the pages in factory settings for later use. e.g radio and other settings.
What you have given so far concerning MCU it should be possible to upgrade. Don't touch MCU, only
ROM needs to be upgraded.
Also be sure you can get in to recovery. Important is also the screen size 800 or 1024. You have to pick the right one. If you don't
know go to play store and install an app that tells your screen size. It doesn't matter in which SD-slot you're upgrading from.
Normally we use the GPS-slot (left one).
halloj said:
You need to take pictures of the pages in factory settings for later use. e.g radio and other settings.
What you have given so far concerning MCU it should be possible to upgrade. Don't touch MCU, only
ROM needs to be upgraded.
Also be sure you can get in to recovery. Important is also the screen size 800 or 1024. You have to pick the right one. If you don't
know go to play store and install an app that tells your screen size. It doesn't matter in which SD-slot you're upgrading from.
Normally we use the GPS-slot (left one).
Click to expand...
Click to collapse
ROM? I thought MCU was the important part that needed to be "flashed".
Can't post links to photos... not enough posts yet... Just tell me other info is required beyond what I posted originally?
I know my screen size is 480x800. Recovery mode, I don't know right now how to get enter it, but I know it exists (button combination held when booting).
Was the file I mentioned in my first post not the correct one to use?
The "official" response from the Pumpkin trash "tech" is that there is no real upgrade for my unit, but he provided a link for me to try it (aka removing any responsibility for bricking the radio). So full of crap, I've already seen RQ0248's being sold online with Android 5.1
If you haven't figured this out yet...here you go. I believe you and I have exactly the same unit. I actually read your thread with Jammy and his responses. HAHA. He isn't much help. I actually flashed what he provided to you and it booted, but the resolution was all off. I think that was for a 800X480 unit.
Pretty simple:
Download the latest V2.97 MCU image file for KLD6: http://forum.xda-developers.com/showthread.php?t=3246386
and download the latest Malaysk Rom: http://forum.xda-developers.com/showpost.php?p=69366390&postcount=860
I just put them both onto a USB flash drive, booted into recovery, and flashed them. After flashing I wiped data again and flashed them again, and wiped data one more time. First boot can take some time, but it's working flawlessly now.
dmband64 said:
If you haven't figured this out yet...here you go. I believe you and I have exactly the same unit. I actually read your thread with Jammy and his responses. HAHA. He isn't much help. I actually flashed what he provided to you and it booted, but the resolution was all off. I think that was for a 800X480 unit.
Pretty simple:
Download the latest V2.97 MCU image file for KLD6: http://forum.xda-developers.com/showthread.php?t=3246386
and download the latest Malaysk Rom: http://forum.xda-developers.com/showpost.php?p=69366390&postcount=860
I just put them both onto a USB flash drive, booted into recovery, and flashed them. After flashing I wiped data again and flashed them again, and wiped data one more time. First boot can take some time, but it's working flawlessly now.
Click to expand...
Click to collapse
Yeah, don't get me started with that forum over there... I shiver in disdain with my entire experience there.
TBH, Im like 99% certain my radio is 800x480 (we ARE talking about the RQ0248 right?). I'm still running the v2.91 MCU with the stock image "that person" gave me. And at very least, most of my issues with the radio have improved since doing so: My FM radio reception seems a little clearer, and the Bluetooth audio quality (streaming from spotify on my phone) is also quite a bit better.
That being said, everything about the 5.1.1 OS i'm running is HIDEOUS. The home screen and radio app particularly are just so ugly, aesthetically-speaking. I wasn't about to push my luck on the other forum though: it was hard enough to get an official response to fix my software bugs in the first place.
So, question time!
1) What does MCU v2.96 offer vs v2.91?
2) What does the Malaysk ROM offer vs the stock 5.1.1?
3) Does the Malaysk offer different skins? Customization?
4) Is there some way to improve the functionality of the built-in radio/music apps? (ex: no ID3 tags from MP3s... I'm pretty sure my MP3 player from 2002 has ID3 tags, this radio does not).
Thanks for answering! I had almost given up hope for this forum, it seems very popular in some areas, but this section seems to have much less in the way of activity.
Looking forward to hearing back!
cmetaphor said:
Yeah, don't get me started with that forum over there... I shiver in disdain with my entire experience there.
TBH, Im like 99% certain my radio is 800x480 (we ARE talking about the RQ0248 right?). I'm still running the v2.91 MCU with the stock image "that person" gave me. And at very least, most of my issues with the radio have improved since doing so: My FM radio reception seems a little clearer, and the Bluetooth audio quality (streaming from spotify on my phone) is also quite a bit better.
That being said, everything about the 5.1.1 OS i'm running is HIDEOUS. The home screen and radio app particularly are just so ugly, aesthetically-speaking. I wasn't about to push my luck on the other forum though: it was hard enough to get an official response to fix my software bugs in the first place.
So, question time!
1) What does MCU v2.96 offer vs v2.91?
2) What does the Malaysk ROM offer vs the stock 5.1.1?
3) Does the Malaysk offer different skins? Customization?
4) Is there some way to improve the functionality of the built-in radio/music apps? (ex: no ID3 tags from MP3s... I'm pretty sure my MP3 player from 2002 has ID3 tags, this radio does not).
Thanks for answering! I had almost given up hope for this forum, it seems very popular in some areas, but this section seems to have much less in the way of activity.
Looking forward to hearing back!
Click to expand...
Click to collapse
I'm not sure what the benefit is of the 2.96, but it's newer so it must be better! That was just the latest so that's what I used. THere are a ton of benefits so you should read the thread....but here are a few: Malaysk offers quite a few optimizations, built in root, customization including skinned apps and radios, and MOST importantly in my opinion is the FUSE support...which means the full 16gb of system space are available to use for apps. You won't run out of space again. Yes there are other music apps included in his ROM as well, but I haven't used them much so I can't really speak to their functionality...but I'm sure it's better than the stock app.
But, do the new music apps work with the steering wheel controls?
That pumpkin forum is ridiculous lol yes im after a factory looking stable rom with fuse the origional firmware that came with the 2.85 mcu worked flawlessly but it double booted so i tried custom firmware when he sent me the original firmware again, it wasnt the same it didnt even boot properly with 2.85 i had to update the mcu to 2.91 for the firware to even become useable
cmetaphor said:
But, do the new music apps work with the steering wheel controls?
Click to expand...
Click to collapse
Can I get an answer to this? The music app is terrible in terms of supporting things like ID3 tags and the like.
Don't even get me started on the 5.1.1 radio app, never seen something so hideous.
So I really want to know if there are alternative apps out there, or at very least better skins, for the garbage apps that Pumpkin dishes out.
Side Note: How good is the android auto integration in these head units? I've never tried it myself.... But Android auto is quite pretty to look at, and I really wouldn't mind tethering my phone via USB cable to my car radio if it meant a better overall experience. That being said though, things like the steering wheel control absolutely MUST function with android auto tether/mirror link/whatever it's called too.
Thanks in advance for anyone that replies! It's unfortunate that so few people do reply here, and this forum has been far more helpful than any other I've used so far.
cmetaphor said:
Can I get an answer to this? The music app is terrible in terms of supporting things like ID3 tags and the like.
Don't even get me started on the 5.1.1 radio app, never seen something so hideous.
So I really want to know if there are alternative apps out there, or at very least better skins, for the garbage apps that Pumpkin dishes out.
Side Note: How good is the android auto integration in these head units? I've never tried it myself.... But Android auto is quite pretty to look at, and I really wouldn't mind tethering my phone via USB cable to my car radio if it meant a better overall experience. That being said though, things like the steering wheel control absolutely MUST function with android auto tether/mirror link/whatever it's called too.
Thanks in advance for anyone that replies! It's unfortunate that so few people do reply here, and this forum has been far more helpful than any other I've used so far.
Click to expand...
Click to collapse
Pumpkin is a seller only, there is no such thing as a "Pumpkin RQ0248", its a Klyde unit. I m guessing you havent bothered to read the wiki, if you did youd find a load more info and realise that that your unit is the same as any other Klyde unit no matter what it looks like on the outside or who you buy it from (Eonon, Pumpkin, Erisin ) and that its also so similar to any other MTCB or MTCC head unit made by the 10 odd manufacturers who produce these units, that it can use the same software as all of them.
I m also guessing that you dont read or look in the main threads in the 4 MTCB/C forums either, cos youd know all about the custom ROMs and modified apps that are available.
I m guessing neither did the OP or he wouldnt have opened the thread in the first place, we cant have a thread open for every made up model number by every seller of all 10 manufacturers, there would be literally 1000s of thread all with the same content. All the info for this unit is the same for any other MTCB/C unit.
cmetaphor said:
But, do the new music apps work with the steering wheel controls?
Click to expand...
Click to collapse
typos1 said:
Pumpkin is a seller only, there is no such thing as a "Pumpkin RQ0248", its a Klyde unit. I m guessing you haven t bothered to read the wiki, if you did youd find a load more info and realise that that your unit is the same as any other Klyde unit no matter what it looks like on the outside or who you buy it from (Eonon, Pumpkin, Erisin ) and that its also so similar to any other MTCB or MTCC head unit made by the 10 odd manufacturers who produce these units, that it can use the same software as all of them.
I m also guessing that you dont read or look in the main threads in the 4 MTCB/C forums either, cos youd know all about the custom ROMs and modified apps that are available.
Edit: Yay! This forum had an ignore button! Just learned that today too.
I m guessing neither did the OP or he wouldnt have opened the thread in the first place, we cant have a thread open for every made up model number by every seller of all 10 manufacturers, there would be literally 1000s of thread all with the same content. All the info for this unit is the same for any other MTCB/C unit.
Click to expand...
Click to collapse
Oh look everyone! I've found the @#$%.
Kind replies are far more helpful than sarcastic, snide, rude and jerk replies. Instead of replying next time, I'd prefer you not reply at all.
There are actual helpful people here that could explain these to me nicely, and have been doing so thus far. These forums are MASSIVE - I don't have the time to read for hours and possibly put myself on the Wrong track if I happen to miss some important details. Also, unless I somehow was able to magically learn what a Klyde radio is on my own, I had never heard of that detail before. Maybe a nice person could've explained it to me.
But kind isn't you. So please go away and allow the nice people to speak.
cmetaphor said:
Oh look everyone! I've found the @#$%.
Kind replies are far more helpful than sarcastic, snide, rude and jerk replies. Instead of replying next time, I'd prefer you not reply at all.
There are actual helpful people here that could explain these to me nicely, and have been doing so thus far. These forums are MASSIVE - I don't have the time to read for hours and possibly put myself on the Wrong track if I happen to miss some important details. Also, unless I somehow was able to magically learn what a Klyde radio is on my own, I had never heard of that detail before. Maybe a nice person could've explained it to me.
But kind isn't you. So please go away and allow the nice people to speak.
Click to expand...
Click to collapse
I didnt write anything that was unkind, snide, sarcastic rude or jerk, I simply gave you some information about where to look to avail yourself of some basic info about your headunit, I didnt have to, I wasnt paid for it, yet I did, in my book, thats "kind". What you require, it seems is someone to spend their time re-typing out whats already been written in other threads into this thread, because you cant be bothered to either look for it/read it yourself (known on xda as "spoon feeding").
It seems that you also havent bothered to read the post I just made properly either, because if you had, you would have seen me refer to "the wiki" (also linked to in the sticky in the very first post of this forum AND in my signature !) and would realise that you dont need any "magic" to learn what a "Klyde" is, you just need to read something mentioned TWICE on the screen in front of you !
In your previous post you also complained that "so few people reply here", if you read what I wrote in my reply, you ll realise why that is - theyve all read the basic info and are replying in threads that apply to ALL MTCB/C headunits.
On xda youre supposed to read stuff and find out for yourself and if you cant find the info you need or dont understand something or need help with something then there are loads of people (including me - look at my thanks meter) who will happily help you. But its clear that you havent read a thing, nothing, not one bit, not the sticky in the general section, not the Q&A section's first thread, not the wiki, nothing, diddly squat. So to help you in the way you want, I would have to write whats already been written and I aint doin that - you read at least the basics of it and ask questions if you dont understand something or cant find it.
Curtusz said:
That pumpkin forum is ridiculous lol yes im after a factory looking stable rom with fuse the origional firmware that came with the 2.85 mcu worked flawlessly but it double booted so i tried custom firmware when he sent me the original firmware again, it wasnt the same it didnt even boot properly with 2.85 i had to update the mcu to 2.91 for the firware to even become useable
Click to expand...
Click to collapse
Sounds like the ROM you were given was more up to date ROM - new features often have to be enabled by updating the MCU too, as that controls a lot of functions. Its also because you now have an MTCC MCU - 2.85 is MTCB, 2.91 is MTCC and older ROMs dont work with older MTCB MCUs.
Yup it is now a mtcc unit ... im actually using kld9 2.98 i think, i found now my new rom is also double booting after an app install , so its certain apps that cause double booting. Just outa interest what rom are you using? (if you have a kylde unit)
Curtusz said:
Yup it is now a mtcc unit ... im actually using kld9 2.98 i think, i found now my new rom is also double booting after an app install , so its certain apps that cause double booting. Just outa interest what rom are you using? (if you have a kylde unit)
Click to expand...
Click to collapse
I m using booroondook's ROM. When you say double booting do you mean it boots, shuts down then reboots ?
Basically boots up as it should , then after about 5 seconds boot logo appears then boots again doesnt shut/power down , it started after i downloaded an app called virtual dyno mobile, i will try the rom your using
Curtusz said:
Basically boots up as it should , then after about 5 seconds boot logo appears then boots again doesnt shut/power down , it started after i downloaded an app called virtual dyno mobile, i will try the rom your using
Click to expand...
Click to collapse
Thought so, not heard of that before, strange.
Yeah its common across the pumpkin forum. I dont know where they are getting their roms from but they are terrible.
Curtusz said:
Yeah its common across the pumpkin forum. I dont know where they are getting their roms from but they are terrible.
Click to expand...
Click to collapse
They get their ROMs from Klyde, the manufacturers of the units !