[Kernel 3.0.8][CM9/CM10] Info. sobre kernels para ICS/JB.

[falmarini]

No creo q sea el kernel 3 pq apenas han conseguido q "bootee" un poco. Si hillbeast hubiese conseguido completar la primera etapa estaria tan contento q lo habria gritado a los cuatro vientos.y despues de esa etapa vienen otras: drivers etc.....vamos q queda mucho camino

Enviado desde mi GT-I9003 usando Tapatalk

[Stikes]

 Cita: Originalmente Escrito por falmarini

No creo q sea el kernel 3 pq apenas han conseguido q "bootee" un poco. Si hillbeast hubiese conseguido completar la primera etapa estaria tan contento q lo habria gritado a los cuatro vientos.y despues de esa etapa vienen otras: drivers etc.....vamos q queda mucho camino

Enviado desde mi GT-I9003 usando Tapatalk

Creo recordar que Hillbeast dijo que le booteo con problemas pero le booteo

[ziento27]

Ha desmentido hillbeast lo que dijo el vishal ese.

I'm just saying there's no point releasing a test build. If I did, it would go on peoples phones, it would reboot, and then the Galaxy SL logo fades to black and it stays there, at which people have to pull the battery out, and go back into Odin and reflash their old kernel again. It's just a waste of time.

Perhaps once I get busybox shell working I can share it amongst some other developers and they can help me then, but right now the only people who can help are those with UART, or those who can make heads or tails of my logs I post

TRADUCIDO

Sólo estoy diciendo que no hay un punto para hacer una compilación de prueba. Si lo hubiera, funcionaria en los teléfonos de la gente, se reiniciaria el sistema, y luego se desvaneceria el logo de Galaxy SL en negro y se quedaría allí, en que la gente tiene que sacar la batería y volver a Odín y reflashear su kernel antiguo de nuevo . Es sólo una pérdida de tiempo.

Tal vez una vez que tenga busybox puedo compartir entre algunos otros desarrolladores y que me puedan ayudar entonces, pero ahora las únicas personas que pueden ayudar son los que tienen UART, o los que pueden hacer cara o cruz de mis registros que publico

[ale210]

Que saquen ya el putoo keneeeeeeeeeeeeeeeelllllllllllllllllllllllllllllll lllllllllllllllllll

[Mbaka]

Ya estan testeando con el?? =S

[Benguii]

hasta diciembre nada..(inventandomelo)

[Mbaka]

Pues vaya... -,-!

[Daniwoo]

:what:

Enviado desde mi GT-I9003 usando Tapatalk 2

[Joseluratm]

Hillbest ha puesto hoy esto:

This next post is off topic on kernel 3.x but it's something I think is interesting.

So yesterday I took a break from the kernel because it's confusing me a bit at the moment, and was thinking about the recovery process for this phone. I remembered ages ago that I discovered when you take the battery out and put it back in while the phone is connected to your computer, it connects as a random USB device (USB\VID_0451&PID_d00e). I knew this had to be the CPU itself showing up as it pops up so quickly after connecting power to the device, there is no way the device could possibly initialise the NAND and load the RAM up in that short amount of time, and connect a USB device.

I did a little research on this ages ago and discovered it is indeed the OMAP processors internal recovery/debug system. As suspected and much like Samsung Exynos processors the processor has an internal firmware (Samsung calls it iROM, dunno what TI call it) and this is what begins very very early initialisation of the processor and NAND so it can then load the bootloaders (Pbl/Sbl on Samsung Exynos, X-Loader/uboot on OMAP). This iROM (it's probably not what OMAP calls it but I'll call it that anyway because it's what I know) has a built in function where it will initialise the USB port as well and provide an interface for debugging purposes, and this can also be used to program the device and send information to and from it.

Basically this is a function used mainly in service centres, but it's more popularly used for development boards, like the 3630SDP or the SMDK4210 so you can program firmware onto the device even if it's completely bricked. It's a very very powerful and very very low level system which comes before even the bootloaders are loaded from the OneNAND or wherever they are kept on the device in question (in our case the OneNAND, but in other phones it would be the eMMC or something like that), so even if you went into Odin and completely wrecked it by unplugging it halfway through a flash and then were a even bigger moron and didn't bother fixing it while you had the chance while it was still on, you can then restore it using this iROM by sending a few low level commands directly to the CPU telling it to write data (ie a bootloader) directly to the NAND.

The utility for doing this on OMAP is actually open source (thanks TI) and they provide it free of charge, and I had to get my hands on it to play around a little.

Now of course I wanted to do some safe testing on it to see what exactly I could dig up, but I didn't want to dig too much into it in case I really messed it up and couldn't figure out how to get it back. I couldn't do much apart from find a few numbers that seem to be like serial numbers and such and as a result I won't post them in case it will identify the devices IMEI or something (don't want to give losers my IMEI), but I'll censor the potentially bad info instead.

Pretty much it did nothing but return a bunch of information, but it did work though in showing me information. That command however was supposed to load a bootloader into the RAM and tell it to do that. I tried various other commands like telling it to read the OneNAND but it kept spitting it out, so my guess is that because it's actually got an operating system on the device it can't accept any instructions (it's not multithreaded, it's only a bootloader), so short of bricking the device intentionally and digging further, there's not a lot that can be done from here.

Now there is no way in hell I would brick a device intentionally unless it was something I knew I can restore right back and have that system handy, and seeing I don't know if this system would work or if it needs something else I just won't take that risk. If it was say a Raspberry Pi where the operating system and bootloader are all stored on a SD card where I can reflash the firmware and everything from another system it's fine, but unfortunately we don't have that luxury here.

I will NOT and repeat NOT under ANY circumstances be giving you guys a download link or a link to where I got the utility I used. As you can see, I also censored the name of the program I used. Why? Because I don't want you guys thinking 'let's go play with it'. I know how flash happy some of you are, you are wanting me to even post links to the broken kernel 3.0 that still doesn't work yet, so I can't trust you guys enough to even tell you where you can look for this program. So why am I telling you any of this then? I'm telling you this because I thought I should let you guys know that there IS a system in place and with a few correct settings it WILL be able to restore a bricked SL. I know this because it has the configuration for the 3630SDP in the program (a very similar platform), and it has OneNAND support. It just doesn't work for me because my device isn't bricked.

Maybe someone with a broken phone could test it, but I'm not going to.


Que basicamente viene a decir, que ha descubierto que hay un firm dentro del procesador, y que cree que cualquier movil brickeado, se podria arreglar.

[ale210]

Bueno hay mas "avances" hb ha hablado de una posible forma de recuperar terminales briqueados, es decir, con bootloaders jodidos, como instalar una rom equivocada.

Entre todo el tocho que ha escrito, habla de la tecnología que puede hacerlo posible, que los procesadores llevan un firmware super interno y de bajo, nivel que aunque con el brick mas total se puede recuperar. Y que por desgracia, no lo puede probar, porque obviamente no quiere briquear su propio terminal.

Pero por ahora nada del kernel 3.x

[Billylopezbmw]

Muy parado esta esto.............

[falmarini]

Hay nueva version del kernel para JB con oc a 1300 y algunas cosas mas

Enviado desde mi GT-I9003 usando Tapatalk

[ale210]

 Cita: Originalmente Escrito por falmarini

Hay nueva version del kernel para JB con oc a 1300 y algunas cosas mas

Enviado desde mi GT-I9003 usando Tapatalk

Pero es kernel del chungo eh!

Enviado desde mi GT-I9003 usando Tapatalk 2

[falmarini]

 Cita: Originalmente Escrito por ale210

Pero es kernel del chungo eh!

Enviado desde mi GT-I9003 usando Tapatalk 2

De momento es lo que hay. Ni siquiera vurrut ha aparecido con un kernel para jb asi que....

Enviado desde mi GT-I9003 usando Tapatalk

[affair]

 Cita: Originalmente Escrito por falmarini

De momento es lo que hay. Ni siquiera vurrut ha aparecido con un kernel para jb asi que....

Enviado desde mi GT-I9003 usando Tapatalk

Vurrut esta perdiillo una pena porque es un desarrollador cojonudo ...

Enviado desde mi GT-I9003 usando Tapatalk 2

[Mbaka]

Estara liado con algo, recordar que cada uno tiene, familia, trabajo, hijos, y una vida fuera de aqui, ademas el trabaja en mas dispositivos, quiero creer que si la cosa esta parada por el hilo pues supongo que lo habra dejado de lado momentaneamente ( ojala me equivoque) pero bueno por lo que leo el kernel va muy avanzado asi que en nada podreis disfrutarlo =)

[Benguii]

lo mejor es olvidaros del kernel. hasta que salgan noticias de su salida o de su arranque total. sino nos vamos a volver locos

[Stikes]

Alguien a provado el Kernelnde que se habla, ese nuevo?

Enviado desde mi perla negra usando Tapatalk2

[affair]

 Cita: Originalmente Escrito por dj_stikes

Alguien a provado el Kernelnde que se habla, ese nuevo?

Enviado desde mi perla negra usando Tapatalk2

stikes pon el enlace que nose de que kernel hablas,el arindamkernel ese???ese es el que tu dices???

[ale210]

No hay absolutamente nada de movimiento en los hilos del kernel. Mira que me da rabia.
Pues si benguii nos vamos a volver majaras (aunque ya estamos tocaos ).

Enviado desde mi GT-I9003 usando Tapatalk 2