Database Users

Any custom roms?

Dude said there are custom roms out, yet I can't find any?
Also doesn't seem like much support, anyone working on any?
Edit: im gonna say no, and none lol.

Have you found anything?
In all my searching haven't found anything out there specific to the Bravo (also known as Kobe).
Custom rom area of xda for this platform shows nothing either.
I see that AT&T has this platform priced way down and free as an upgrade so hopefully with more exposure it will get some development going.
Many rumors of upgrade coming. So if that happens that may also spur development. I don't expect AT&T will push it out however they are in business to sell new devices and there upgrade history is far from being even dismal.
Tried to investigate how to do it myself, but it is WAY beyond my capabilities.
Unfortunately theres no such thing as simple answers, its like pulling teeth, and very cryptic for noobs, reminds me of the early days of linux. NOt that I am an expert in hat either but help is easy and straight forward.
Now there's a thought, I'll check back later, going over to check the linux forums after all Android is a linux derivative.

Having soft-modded (in phone speak: rooted) several types of video game consoles, this seems like a boot-signature check issue. I have not made my own cracks, but I know how each one works...
Chain of trust:
hardware checks bootloader (on some systems, or at least protects it from mod)
bootloader checks rom (OS or dashboard)
rom checks user software/media
From previous experience, the highest level of trust needs to be cracked unless a signing key is found.

mirror.teamdouche.net
props to our friends cyanogenmod, they just released #7 which is a custom Gingerbread rom. and props to xda-dev member bandroidx who is finishing a port for clockworkmod recovery, to work on bravo, AND THEN we will have all the roms we want!

apples2droids said:
mirror.teamdouche.net
props to our friends cyanogenmod, they just released #7 which is a custom Gingerbread rom. and props to xda-dev member bandroidx who is finishing a port for clockworkmod recovery, to work on bravo, AND THEN we will have all the roms we want!
Click to expand...
Click to collapse
Thanks for the words of encouragement!
you do know the "Bravo" on that site is refering to a HTC device though right? CM7 isnt out of the question, I talked to CVPCS and his work on porting CM7 to the DX should be useful for porting it to the bravo, but first I am focusing on finishing CWM, I dont want to jump ahead of myself

Where are all the ROM GOODNESS!

I am new the to the GT10.1.. Just wondering why there are no custom roms or anything for it yet?!?
Sorry if I missed the thread telling me why!

jm6001 said:
I am new the to the GT10.1.. Just wondering why there are no custom roms or anything for it yet?!?
Sorry if I missed the thread telling me why!
Click to expand...
Click to collapse
Questions or Problems are not Development
Please post in the correct forums and use the search
Moving to General

So few people have the tablet at the moment, suspect that's the hold up. It still hasn't been released to the rest of the US.

How much can you do without the source code?

There's not much you can do without the source. The xoom only got it's first rom a few days ago and it does not have all that many changes. Once we get the kernel source, we should start seeing some custom kernels(for overclocking and stuff) but that's about it.

smaskell said:
There's not much you can do without the source. The xoom only got it's first rom a few days ago and it does not have all that many changes. Once we get the kernel source, we should start seeing some custom kernels(for overclocking and stuff) but that's about it.
Click to expand...
Click to collapse
That's what I figured. I'm sure you can change around a few small things, but for the most part didn't expect what I'd consider a true "custom rom."
Will probably have to wait for Ice Cream Sandwich.

I think we can thank google for that as they have chosen not to release the AOSP for honeycomb. And who knows when samsung will release the kernel source. I would have thought they would have released it by now.

xavierdylan said:
I think we can thank google for that as they have chosen not to release the AOSP for honeycomb. And who knows when samsung will release the kernel source. I would have thought they would have released it by now.
Click to expand...
Click to collapse
I'm not exactly sure what the law is but they will have to release it eventually.. The linux kernel is under the GPL, which means that any modifications to it are, without question, also under the GPL. Therefore, they have to make their version of the kernel open source at some point. Does anyone know how long they have to do so?

Does any one know if the retail version of the galaxy tab have an unlocked boot loader and if can be rooted? cant seem to find that info ne where. if it has a locked bootloader you can forget abt custom roms till the bootloader can be unlocked

I897UCKK4 Source Code is out.

I'm preparing to be flamed, but I figured I might as well create this thread. Now I know many of you know this, along with the i896 source, is out, but there wasn't a thread for it and the i896 one had issues, so here . Hopefully we can get some development going for those of us that want *shutters* Audience Chip drivers, along with the many features that are present in the i9000 roms.
Just search KK4 on here: https://opensource.samsung.com/index.jsp

nygfan760 said:
I'm preparing to be flamed, but I figured I might as well create this thread. Now I know many of you know this, along with the i896 source, is out, but there wasn't a thread for it and the i896 one had issues, so here . Hopefully we can get some development going for those of us that want *shutters* Audience Chip drivers, along with the many features that are present in the i9000 roms.
Just search KK4 on here: https://opensource.samsung.com/index.jsp
Click to expand...
Click to collapse
Doesn't bother me anymore since now ICS is doing great.
But, if really want to stick with GB(usually MIUI and CyanogenMOD).
I would like:
a.) The Audience Chip thingy.
b.) Battery life.

Fate-Silver said:
Doesn't bother me anymore since now ICS is doing great.
But, if really want to stick with GB(usually MIUI and CyanogenMOD).
I would like:
a.) The Audience Chip thingy.
b.) Battery life.
Click to expand...
Click to collapse
What? I'm not making anything. I was informing the community (those who didn't know) of the source code.

nygfan760 said:
What? I'm not making anything. I was informing the community (those who didn't know) of the source code.
Click to expand...
Click to collapse
Yea, I know.
I just want to tell AT&T/Samsung is SLOW for their firmware codes sharing... too stingy...

Fate-Silver said:
Doesn't bother me anymore since now ICS is doing great.
Click to expand...
Click to collapse
yea I been onICS for 24 hours now ,, its great , but nothing special I see very few differences in anything , except I am missing all of the features I m use to on GB .
imo dotn believe the hype , the only 2 things I like about my current ICS set up is sixstring kernel allows me to OC higher then on sammy rom (not higher then cm7 tho) and the launcher is pretty cool but still not as nice as on the gnex .
Eventho its 2.3.5 I welcome source of KK4
eventho Im 2.3.6 (i9000 base )

I'm looking forward to the more refined kernels the source code release should bring around. Those features we've been missing will now be possible.

nygfan760 said:
I'm preparing to be flamed, but I figured I might as well create this thread.
Click to expand...
Click to collapse
Why? There is already a thread created in General. This is where searching comes in handy.

Red5 said:
Why? There is already a thread created in General. This is where searching comes in handy.
Click to expand...
Click to collapse
Saw the thread. It is a discussion thread about the firmware, this thread is to alert people of the actual source code, so we can get new kernels and stuffs Also, aren't most source code threads posted in here? At least for Froyo, and i896 GB, I believe they were.

Audience chip support was already extracted from the I896 gingerbread source kernel. It is available in the i9000 captivate corn kernel. Specifically gave me thanks for being able to introduce audience tip finally.
If you would like Audience support in any other kernels just contact the developer of corn.. A few months ago

TRusselo said:
Audience chip support was already extracted from the I896 gingerbread source kernel. It is available in the i9000 captivate corn kernel. Specifically gave me thanks for being able to introduce audience tip finally.
If you would like Audience support in any other kernels just contact the developer of corn.. A few months ago
Click to expand...
Click to collapse
I know, I know, I have been running it for a while now.

but im surprised that kk4 was final release. had time-stamp issue.
but now if we can get a unbranded kernel, we can have a complete unbranded rom with the ATT removal mods i posted while back.

TRusselo said:
but im surprised that kk4 was final release. had time-stamp issue.
but now if we can get a unbranded kernel, we can have a complete unbranded rom with the ATT removal mods i posted while back.
Click to expand...
Click to collapse
I'm pretty sure that problem only happens when you put AT&T software on an i896. I can't say for sure though because both my cappy's are canadian. Anyways I don't think ts a problem with the phone per se.. I think its a network thing. There is no time stamp issue for people on the AT&T network that I know of.

KK4 Source has been available since around Christmas. Some of the I897 kernel devs have been trying to compile a kernel from source but have been running into issues with the kernel not booting which is why you haven't seen any yet.

erbsmokah said:
I'm pretty sure that problem only happens when you put AT&T software on an i896. I can't say for sure though because both my cappy's are canadian. Anyways I don't think ts a problem with the phone per se.. I think its a network thing. There is no time stamp issue for people on the AT&T network that I know of.
Click to expand...
Click to collapse
Its a network AND software issue. Either they can fix the problem though the network, (its been done before) or you can de-compile the MMS.apk and change a line of code to fix the problem.
Kyuta Syuko said:
KK4 Source has been available since around Christmas. Some of the I897 kernel devs have been trying to compile a kernel from source but have been running into issues with the kernel not booting which is why you haven't seen any yet.
Click to expand...
Click to collapse
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???

TRusselo said:
Its a network AND software issue. Either they can fix the problem though the network, (its been done before) or you can de-compile the MMS.apk and change a line of code to fix the problem.
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???
Click to expand...
Click to collapse
He is a kernel dev but yeah I hope that isn't the problem.

TRusselo said:
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???
Click to expand...
Click to collapse
Both JSmokey and I haven't been able to get a kernel compiled from the KK4 source that we had gotten around Christmas. Though JSmokey said he did have a working kernel before, but isn't certain what he did to make it not work anymore. I've even tried to compile a stock kernel per the included instructions with no luck...

Kyuta Syuko said:
Both JSmokey and I haven't been able to get a kernel compiled from the KK4 source that we had gotten around Christmas. Though JSmokey said he did have a working kernel before, but isn't certain what he did to make it not work anymore. I've even tried to compile a stock kernel per the included instructions with no luck...
Click to expand...
Click to collapse
Same here, there must be something missing. Pulling a dmsg doesn't give much help, something about wanting sh in /system/bin (I think).
I have moved over to cyanogenmod 7 for now, waiting for cm9. Lots to tinker with there.

boog said:
Same here, there must be something missing. Pulling a dmsg doesn't give much help, something about wanting sh in /system/bin (I think).
I have moved over to cyanogenmod 7 for now, waiting for cm9. Lots to tinker with there.
Click to expand...
Click to collapse
.... no our original 2.3 kernel dev has given up

Sounds like the only way to get bln is to go to 2.2 or i9000.

Wdustin1 said:
.... no our original 2.3 kernel dev has given up
Click to expand...
Click to collapse
Maybe we can ask DG for help. I know he has moved on a long time ago, but recently he came back and helped with ICS kernel development. If he could help us getting KK4 kernel compiled from source, I am sure we will see a lot more ROM development going on.

[KERNEL]Nexus 7 Compiled from Kernel.org Source

Hi All!
I have been trying to compile a Kernel for Android from Kernel.org Source. Avidly awaiting a Nexus 7 I got straight to work. I have created a zImage. I have been trying to document the process but rather than type it again I have been doing it here. If someone with a Nexus 7 wants to give this a go I would be very much grateful. This is an ongoing process. I have included the file and necessary instructions here...
It looks like I cant post external URL's .... YET! If you want to post here or PM Me I will send you the links.
If someone could test this for me it would be greatly appreciated.
Thanks

I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)

Bogdacutu said:
I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)
Click to expand...
Click to collapse
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.

JamesSawyer said:
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.
Click to expand...
Click to collapse
Okay then, I can do that. I assume you can PM links?

You might be able to state the URL address in your post for your kernel. I'd test it and I guess others may also.

Hi All,
I have someone from Neowin who is going to post the links for me.
At the moment my guide and files are all disjointed I am trying to organize it better.

Great idea! I'll look around your thread @neowin.
What supposedly differences are there from the native android kernel and one compiled using the code from kernel.org?

Personally I just like playing with Bleeding Edge code. You would get all the latest features from source as well as bug fixes most end users wouldn't see. Performance is to be determined, Battery life and CPU performance etc. Its also quite a little Niche that I like been a part of if it all works and comes off.

The kernel you're compiling most likely won't work if you don't even have the machine definitions nor the drivers for your nexus (seeing that you have taken the source directly from kernel.org)
The best of testing a new version would be to backport it but doing so takes an incredible amount of time and considerable skills.
Envoyé de mon Nexus 7 en utilisant Tapatalk

I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.

JamesSawyer said:
I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.
Click to expand...
Click to collapse
You need to have proper board files, proper drivers (device-specific ones) and tons more. I don't think it will work without those. Then chances are it's not going to compile properly; it will throw tons of errors. After you get it to compile, you have to get it to boot. After you get it to boot, you have to get it fully-functional (not necessary if this is a test kernel). So unless you have gone through it all, I don't think it'll work.
BUT I may be wrong.

It compiles no problem, That's what I am wanting people to test :good:

JamesSawyer said:
It compiles no problem, That's what I am wanting people to test :good:
Click to expand...
Click to collapse
Ready to test! Check that neowin thread, but all the links I've tried lead to 404

vrutkovs said:
Ready to test! Check that neowin thread, but all the links I've tried lead to 404
Click to expand...
Click to collapse
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.

JamesSawyer said:
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.
Click to expand...
Click to collapse
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha

poondog said:
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha
Click to expand...
Click to collapse
I am trying to ha! :highfive:

Do you have your 3.4 Kernel? Do you have notes how you built it?
Edit: Updated to include 3.13rc8

I have done some more merging from latest Mainline and Flo Kernel from Google. Its building as we speak. Time to head to Tesco.
Hopefully what I have done will get rid of a compile time error I was having.
Has anyone got the ones I made previous to boot. I have my Nexus 7 on the way as of today so I will be testing it on my own sooooon!! :good:

http://linux.jamessawyer.co.uk:8000/
A bit more easy to remember. There are some test builds and experimental stuff on there too. I might do requests if anyone wants me to make a build for their device let me know. Rather than the Nexus 7 2013. I only did that because thats the device I am getting

The link is down

3.10.33 kernel from Nvidia Shield ported to Mi Pad

Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2...nhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2...FhQTHJIa2xVems

reserved

Artemka2008 said:
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2ALf4H-2aBrZnhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2ALf4H-2aBrZFhQTHJIa2xVems
Click to expand...
Click to collapse
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).

drakonizer said:
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
Click to expand...
Click to collapse
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)

Artemka2008 said:
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Click to expand...
Click to collapse
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.

drakonizer said:
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
Click to expand...
Click to collapse
ok, I will delete this thread.

Artemka2008 said:
ok, I will delete this thread.
Click to expand...
Click to collapse
You don't have to delete the thread. It can be used for discussions. You can upload your kernel whenever you feel its appropriate to release your source code.
On a more helpful note: I can't say much without seeing the source code, but if you have ported the kernel drivers as well from shield, you can try using the blobs from Shield itself. You'll probably need to use blobs that match the version of the kernel you are trying to port.

so does that mean that there is a chance for cm12+?

Jahhhhhhh said:
so does that mean that there is a chance for cm12+?
Click to expand...
Click to collapse
Without camera and sound now. I tried to run Android 5.1.1 with our kernel. But I can't find working graphical blobs. I need help with it.
This is my last logcat https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?

Palm Trees said:
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Click to expand...
Click to collapse
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.

Artemka2008 said:
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Click to expand...
Click to collapse
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.

drakonizer said:
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
Click to expand...
Click to collapse
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.

Palm Trees said:
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Click to expand...
Click to collapse
Not the point. The shield developers will not be able to help us. Things will become very easy if this shield kernel port works. We will probably be able to use the newer blobs meant for the Shield, which makes development very easy, if this becomes bootable/stable. I really hope the OP manages to get it working. We either need newer blobs from Xiaomi or we need to write wrappers to use the current kitkat blobs (not easy, since Nvidia documentation is nowhere near as detailed as say, Qualcomm) or we need to get this port working well, which would enable us to use most of the blobs from the Shield (provided Xiaomi hasn't gone out of their way to screw with their blobs). The first two ways are practically impossible, which leads me to rest all my hope on this port. Unfortunately without the source code, we will just have to be silent spectators, waiting for some news.

Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks

rocky869 said:
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
Click to expand...
Click to collapse
I asked LuckyMeAgain to publish on the official website, so it's the same thing. I am ArtemkaVZM on 4pda and arttt on en.miui.com MiuiSmokeRom dev team.

Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia

Harrynowl said:
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Click to expand...
Click to collapse
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

Artemka2008 said:
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Click to expand...
Click to collapse
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?

drakonizer said:
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
Click to expand...
Click to collapse
All the necessary blobs were taken from Shield. More no such files, which could be replaced.