Related
I just upgraded my X10 mini to Eclair by editing my build.prop and letting SEUS do the rest. However, I wonder how long we SE-Users must wait for Froyo and upcoming.
My idea now: did anyone think of compiling Froyo for X10 mini or other phones? I am interested in starting a project for this if none exists right now, provided the most relevant issues can be solved.
So, I'd like to know
- if there's a way to make all hardware (WLAN,3G,USB...) running without proprietary drivers (don't know yet if e.g. SE uses publically undocumented hardware)
- if its' legal to extract drivers from the proprietary image - if possible anyway (should be technically)
- what about encrypted device storage, meaning parts of bootcode and so on?
- what about testing a potentially self-compiled android on a real phone without the risk to cause unwanted behaviour in the public, meaning, e.g. paralyzing parts of the GSM network...
Always keeping in mind that staying legal is directive #1.
And yes, I can hardly assume how much work this could become. But there are other open source project showing that interesting projects can become a good thing. (writing this on a debian-powered machine...) ;-)
Any chance?
Yours
dkn8
Thread moved to x10 General
This is a good place to start and gather required information -
http://forum.xda-developers.com/showthread.php?t=726813
Yes, thats a long thread, but invaluable if you want to make custom ROMs
I'm curious, but what is the difference between bootloader cracking on an x10 and say jailbreaking on an iphone. i see that iphone ios gets crack month after month and yet till this day we all are still struggling with a bootader on an old school xperia x10 since day one.
perhaps by the time the bootloader is crack there isn't much sense in keeping this old school phone anymore, because better stuff are out there and will perform better stock out of the box than a heavily tweaked xperia x10.
Jailbreak on iPhone = root on Android... Bootlader cracking = loading custom anything (recovery, kernel) on Android phone with locked bootloader.
Sent from my E15i using XDA App
i think we getting closer to bypass SE boot loader and that will b good new
Does iphone have bootloader like android? because i dont see many post about this, or perhaps i'm not understanding their lingo and acronym.
I dont own any apple product, but i'm very tempted to get the ipad 2 to play with and i have been doing a lot of reading on various forums and following up on their discusions. but i don't see anymention about bootloader cracking on an iphone. perhaps they dont need to because they dont have a need to since they got nothing else but what is offered by apple. so they only have to battle with keeping up with ways to crack newer patched firmware.
xxcysxx said:
Does iphone have bootloader like android? because i dont see many post about this, or perhaps i'm not understanding their lingo and acronym.
I dont own any apple product, but i'm very tempted to get the ipad 2 to play with and i have been doing a lot of reading on various forums and following up on their discusions. but i don't see anymention about bootloader cracking on an iphone. perhaps they dont need to because they dont have a need to since they got nothing else but what is offered by apple. so they only have to battle with keeping up with ways to crack newer patched firmware.
Click to expand...
Click to collapse
It's not the same with apple stuff at all.. The most you can do is jailbreak, and maybe change themes. You can't customize even close to like you can on android..
the bootloader is software wich is loaded/startet by the Firmware(on IBM PCs the firmware is a BIOS).It loads the Kernel.
the iphone has a bootloader too an it gives information about that google to:
iphone Linux
or
iphone android
it uses a custom bootloader.
bypassing (what bin4ry hat done) means that we let the bootöpader do is thing and doesnt modify it but wen the kernel is loaded, we overwrite him in the memory and "reboot"
>>>> 22Jan2012: linboothkvc v1.0 source released in my linboothkvc thread. It works successfully on Omap3 and Omap4 based devices including NookTab. And with minimal changes/love can work with any rooted arm based linux device <<<<
>>>> 17Jan2012: Kernel module SUCCEEDS on NookTab to reboot into NIRVANA - NO NEED to BREAK the default SECURE BOOT CHAIN and NOTE THAT EVEN THIS CAN WORK ON ANY ROOTED DEVICE and not just NT, with minimal love so ENJOY <<<<
>>>> 16Jan2012: My kernel module based path (linboothkvc) to running custom kernels and roms is almost done, except for a __small part__ to get it running on NT now - IF ONLY PEOPLE HAD WAITED ...., we could have reaped the potential benefit in future, Why not !!!! why not ....WHY NOT !?!?. NOTE that it can allow one to run custom kernel/roms WITH OUT MODIFYING ANY CRITICAL PARTITIONS provided one sets it up properly/appropriately. Source for beta version available in my linboothkvc thread, for the interested developers/experimenters for now ... <<<<
>>>> I may not respond to the posts on this thread currently, because I am trying to get a alternate option called linboothkvc using kernel modules up and running (which will occupy my free time), which AVOIDS the NEED for this flaw in the first place for most of the people out there (i.e Custom ROMS with different kernels). However over the weekends, I will go thro all the posts on this thread <<<<
>>>> 14Jan2012: Initial pre-alpha version of kernel module path based source code uploaded to my linboothkvc thread for those still interested to experiment
http://forum.xda-developers.com/showthread.php?t=1427610
<<<<
Hi All,
If you have been following my posts over the last few days
NOTE: To people frustrated with UART requirement - I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then do note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all. AND THAT By holding off now, we can _potentially_(Risk is always there) reap the benifit with next years NEXT GEN Nook Tab+ or what ever they call it.
a) I have implemented 2ndihkvc, which follows the same fundamental concept as 2nd-init, but achieves it in a simpler way (Needed because some of the calls used in original 2nd-init doesn't work on NookTab, or have unnecessary dependencies (in this given context, otherwise they are good in them selves) which can be avoided with my simpler method)
b) I have provided the NOP Bypass method of running a modified Ramdisk and also 90% a modified kernel, provided UART access is there.
c) There is still the power of linux KERNEL MODULES to EXPLOIT. (Haven't had time on that yet).
If you ask me, this should cover all category of people. Be it people who want to run custom Roms, or people who want to experiment with Kernel and or other low level stuff for the fun of it.
There is a 4th method which will allow one to achieve (b) above with out requiring UART access or even uSD (potentially . If one reads between the lines from all my posts till date, the answer is hidden in there. Only that I haven't spelt it out directly or in the face. The reason is because It is a fundament flaw (rather there are potentially two at two different levels - one relatively simple and one relatively bit more involved - One I know for sure, another I have to dig bit more) in the way things are done currently in the secure boot chain on this device as well as potentially other devices with same or similar SOC (and or different SOC but with similar boot chain s/w components.
SHOULD WE BE WASTING i.e providing a solution which uses it, when there is already 2ndihkvc and NOP Bypass over UART and also the Linux KERNLE MODULE ROUTE to cater to most peoples needs.
Because if we do, then even the Device manufacturers and their partners will come to know about it and can easily fix it in their Newer/NextGen devices. While if we withhold it for now, we may be able to get access to it on their Next generation Devices with hopefully Arm A15 core or .... (NOTE: Depending on the boot sequence ROOT access may or may not be required for this).
The reason I am asking now is because, few people are asking my help on certain things and the reality is I know that the concept for which they want my inputs/guidance, can be applied at a more fundamental level here (or even at the same level), but that I have not ventured into it because of my delimma above.
NOTE: People who wanted my inputs/guidance wrt uSD, you all know who you are, I know the flaw to achieve what you want to achieve, but it is more powerful than what you all are currently thinking of doing/ ristricting yourselves to (You all have one input/... in there wrt devices . Unless let me think thro further and see if something can be done differently, with out exposing the flaw I have in mind to help you achieve what you want, otherwise i.e if there is nothing else I can come up with, and in turn if you people experiment further and are able to come up with the solution on your own, I would suggest that hold off on it for few days, think thro all the implications keeping what I have mentioned in this thread, and then take a call one way or the other.
Please provide your thoughts on this after thinking thro the options already available on NookTab (root access, kernel modules, UART UBoot access and inturn 2ndihkvc and NOP Bypass or equivalents)
Based on all the feedbacks as well as bit more thinking from my side, I will take a call on this.
Forum moderators I know this is the development portion of the forum, but I wanted feedback from Developers also that is the reason why I have posted here. But beyond that I leave it to you, whether you want this to continue here or move it out.
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
cfoesch said:
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
Click to expand...
Click to collapse
Hi
I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all.
By holding off now, we can potentially reap the benifit with next years Nook Tab+ or what ever they call it.
Im not a Developer but I've got a few questions. NOP requires to open up your device, so I think probably 95% won't open their device for ICS and I think since the device had a dual core CPU we should get ICS roms. Now my actual question how does your 2init work or how do you install it on our device? But great work so far keep on.
Sent from my SGH-T989
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
PM me about the flaw, I'll see if we should have it outed yet or not (sorry guys, but if it's a decent exploitable flaw and we have other methods, I'm pretty sure I'm with hkvc on it.)
xdahgary said:
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
Click to expand...
Click to collapse
Not worried for 2 reasons,
a) It doesn't bother if my name comes or not. I am exploring just for the fun of exploring.
AND MORE IMPORTANTLY,
b) Actually I have already revealed the flaw in my NOP Bypass thread, indirectly, if only, one reads carefully all my lines as well as between them. Only that I have just replaced one or two of the steps with a different steps thats all for now.
If someone else find the same flaw, he will realise the same, if he reads my posts once again with his new knowledge.
What an awesome idea, we can have a root for the Nook Tablet+ or whatever else in a years time!
...
So, um... what do I do now with my Nook Tablet? It's a piece of garbage now, I guess, so, I'll just return it since it's still within the Holiday return period? I suppose I'll just have to wait for the Nook Tablet+ to have a custom ROM running on my Nook... ("But you can UART hack it!" ... *sigh* I've already explain that that is not sufficient. The UART hack is a stop gap, and should only be stopped at if that is the absolute only option available.)
And I mean no disrespect to xIndirect, but why should he be the lone gatekeeper of what exploits and hacks are out there for the Nook Tablet? I would rather see this exploit before making a decision as well, but I don't think it fair that someone should have privileged access to the exploit. Either release it to everyone or DON'T SAY ANYTHING IN THE FIRST PLACE.
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Indirect said:
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Click to expand...
Click to collapse
If you buy a plot of land and the seller has accidentally left seeds there and isn't coming back for them, do you grow a garden on your current plot of land, or do you decide not to plant them and hope that the next time you buy a plot of land they might forget some seeds again?
I would rather tend the garden I own than hope for a better plot of land with seeds I may never have.
Cheers!
-M
XDA member since 2007
Sorry if my post is offtopic, I just want to help with development.
My SE Xperia x10 came worh a locked bootloader and devs figured out how to make a bootable recovery (xrecovery) based on CWM, may be with an adaptation for the NT we can get the world of custom roms, even with locked bootloader this crappy phone got cuatom kernels by bypassing the bootloader, hope this give little ligth to you guys the real Developers.
If this post is garbage mods please delate it.
Sent from my BNTV250 using xda premium
Hello, I beleive if there is a software way to get ICS + maybe overclocking it should be tried first as this IS what most people are waiting for. That's the big dream they got. If someone knows how to implement that, then please by all means do so ..
P.S. you said so much where to look for the flaw in your posts that if I was a programmer from B&N I'd know where to look like everybody else. Assuming they are not complete morons they can already figure it out too. Can they plug the hole or not? Is it oversight or permanent design flaw ? We'll see. Best way to keep a secret is to " keep it secret " , ie not talk about it at all. Especially if soft mod ICS, hw acceleration and overclocking already available.
Sent from my LG-P500 using Much Love
First of all hkvc +1 for your efforts.
I voted yes, the NT developers can read between the lines in your posts as well.
Whats life without risks once in a while
Hi All,
I understand very well that even BN devs will be looking and potentially can figure out and fix it. That is the risk, but at one level I don't mind taking the risk and see if it works out to my/our advantage (i.e the bug being still open in a new device (From BN or any other Vendor)) or disadvantage(the bug is either way fixed).
Also the flaw can affect ANY DEVICE (Not just NOOK TAB) using similar secure boot chain not just NookTab, that is also one reason why I am bit wary of releasing the info or a implementation which uses it just like that.
I will share my finding with few people on the forum/outside in few days time so that even If I loose interest in this, there will be few people with the required knowledge (i.e if they haven't already figured out on their own by then (and released something or not ...)).
Also I haven't taken a final call on this yet. I am in a delima, so getting all your opinions also before I decide.
Time permitting I will also attack/explore the KERNEL MODULE PATH in a few days time, so that people don't have to depend on this flaw in the first place, but use the wonderful world of Linux Kernel Modules to achieve what they want.
LexS007 said:
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Click to expand...
Click to collapse
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
absolutely YES, we r all xdaers, right hehehe. Thanks all devs especially hkvc for the efforts
hkvc said:
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
Click to expand...
Click to collapse
It's very good. Thanks!!!
First off, not a dev but read religiously.
2nd, release it if the people who would take advantage of it agree. The rest of us say "great,woohoo!" But I must admit, I can't take advantage of it. But I certainly don't want to make a hardware uart to boot custom roms.
That being said, if its more complicated to install with a different method, that's fine. As long as it doesn't include a soldering iron.
But if it were easier to make a custom rom, or open up more capabilities of the kernal or whathaveyou, well that would attract more developers to make roms, etc. and so on and so forth.
Btw. Yes, exploit may exist if outedin a later tablet, but you found this one.... I have faith the next flaw will be found in the next one too.
A bird in the hand is worth two in the bush.
Posted from my B&N Nook Tablet... rooted of course!
jotekman said:
A bird in the hand is worth two in the bush.
Click to expand...
Click to collapse
I would say this summarizes everything I want to say on the topic.
Hey people, how are you?
I was wondering out of nowhere: wait a minute, is this Rom legal?, replacing an Official Rom from the Provider for an Unofficial one that required Unlocking the Bootloader/Rooting the Phone/Flash the Rom is the same as saying that the Phone Protection was broken and it was an Hacking thing, and for making the Rom maybe there was some softwares that were illegally made or stolen from Official Android Version or stolen from Google or from someone.
So with this said, what do you think people? Having a Custom Rom on the Phone, is this Illegal?.
Please don't answer things like: you only void warranty.
Good answers i will give a 'Thanks' button press.
Cheers :good:
Crazy Seed said:
Hey people, how are you?
I was wondering out of nowhere: wait a minute, is this Rom legal?, replacing an Official Rom from the Provider for an Unofficial one that required Unlocking the Bootloader/Rooting the Phone/Flash the Rom is the same as saying that the Phone Protection was broken and it was an Hacking thing, and for making the Rom maybe there was some softwares that were illegally made or stolen from Official Android Version or stolen from Google or from someone.
So with this said, what do you think people? Having a Custom Rom on the Phone, is this Illegal?.
Please don't answer things like: you only void warranty.
Good answers i will give a 'Thanks' button press.
Cheers :good:
Click to expand...
Click to collapse
Android is open source and royalty free software, so anyone is allowed to 'fork' it and do their own thing with it, so that is not illegal, and does not involve stealing or anything else. Amazon uses it on their Kindle Fire in a heavily modified form and MIUI (which just made custom ROMS at first) now also makes phones with their version installed as standard.
The rules on XDA are very strict when it comes to using other people's work without permission and if a ROM contains software which should be paid for or is used without permission that ROM will be removed.
The protection the manufacturers build into their phone is to insure their phones operate the same for everyone and so they can guarantee they can fix it when there is a problem with it.
Apple used to claim that 'jailbreaking' the Iphone was illegal according to their terms and conditions, but a Judge in the United States ruled that when a user buys a device, the user owns it and is allowed to do with that device whatever he wants, essentially meaning that jailbreaking (getting around the phone's factory installed protection mechanisms) is legal.
However, the manufacturer cannot be held responsible if a user does something with that device that the manufacturer did not intend.
That is why you void your warranty when you get around the inbuilt protections.
So, in short: Not illegal in any way, but it is at your own risk and for your own responsibility.
So does that mean that also The GB roms for this phone have legal apk's in it? Confused because of the apk's like: Latinime.apk 'keyboard from xperia x10 mini pro original, i don't know if that is considered stolen from original Firmware' and Gapps 'there are option to flash gapps, and somewhere it says that gapps are illegal on roms unless there is permission.
So breaking the phone protection is not considered a hacking thing right?.
There are country's where unlocking phones are obligatory on the store without charging more from it, so i guess that phones should always be unlocked everywhere, but if someone unlocks a phone not in a store is it legal? Well apparently it is.
That's why i asked also on another thread about the original android that came with the phone, because if the phone went to repair they could know that it was my fault since the firmware isn't the original that came with the phone, or am i wrong?.
So, in short: We're all on our own risk and responsibility, and nothing's illegal unless there was a paid apk on the rom.
Thanks for your answer here and on the other thread mate Cheers :good:
Crazy Seed said:
somewhere it says that gapps are illegal on roms unless there is permission.
Click to expand...
Click to collapse
As far as I understand it, Gapps can't be distributed with a custom ROM, e.g. bundled with it. It's a licensing issue. That doesn't make using them illegal, you just need to flash them separately.
However, the whole thing about what's legal and what's not can sometimes take some bizarre turns that defy logic... For example, take the recent decision of the US Library of Congress to make a cellphone unlocking a violation of the DMCA, and therefore, illegal. First off, the DMCA itself is a bull$h!t, if you ask me, but that's just my opinion. But what the hell does the Library of Congress have to do with it? What kind of authority they have over the matter, anyway? Well, the real lawmakers passed the bill that actually allows the unlocking, so common sense prevails this time, but you never know...
kt-Froggy said:
As far as I understand it, Gapps can't be distributed with a custom ROM, e.g. bundled with it. It's a licensing issue. That doesn't make using them illegal, you just need to flash them separately.
However, the whole thing about what's legal and what's not can sometimes take some bizarre turns that defy logic... For example, take the recent decision of the US Library of Congress to make a cellphone unlocking a violation of the DMCA, and therefore, illegal. First off, the DMCA itself is a bull$h!t, if you ask me, but that's just my opinion. But what the hell does the Library of Congress have to do with it? What kind of authority they have over the matter, anyway? Well, the real lawmakers passed the bill that actually allows the unlocking, so common sense prevails this time, but you never know...
Click to expand...
Click to collapse
I think there were some roms with the gapps inside, but without them bundled it's all legal then .
Luckily i unlocked my phone on the store so i don't have problems with these stuff, i was more concerned about if the roms use Illegal software in it, gapps you tell me now that it isn't legal if we flash them separately, so i guess that what remains on my question is if the keyboard LatinIme.apk is legal since it seems to be like the original used on the Stock Android version that came with the phone, i don't know if there's any other software that i can ask if it's legal or not. In logic, Rooting and flashing would be illegal because it's like 'Hacking', but in the Law and stuff if it's legal then it's ok by me.
Thanks
Cheers :good:
Crazy Seed said:
I think there were some roms with the gapps inside, but without them bundled it's all legal then .
Luckily i unlocked my phone on the store so i don't have problems with these stuff, i was more concerned about if the roms use Illegal software in it, gapps you tell me now that it isn't legal if we flash them separately, so i guess that what remains on my question is if the keyboard LatinIme.apk is legal since it seems to be like the original used on the Stock Android version that came with the phone, i don't know if there's any other software that i can ask if it's legal or not. In logic, Rooting and flashing would be illegal because it's like 'Hacking', but in the Law and stuff if it's legal then it's ok by me.
Thanks
Cheers :good:
Click to expand...
Click to collapse
I think the LatinIME is the google keyboard, the one that came with the phone was the suqashiinput.apk, and I don't think Sony is too concerned if you use the programs that came with the phone on that same phone.
Sony would be in it's right to take down any ROMS that infringe on it's copyrights, but they don't, they have even taken steps to make it easier to use custom roms on their phones, so I don't think you need to worry about that.
SmG67 said:
I think the LatinIME is the google keyboard, the one that came with the phone was the suqashiinput.apk, and I don't think Sony is too concerned if you use the programs that came with the phone on that same phone.
Sony would be in it's right to take down any ROMS that infringe on it's copyrights, but they don't, they have even taken steps to make it easier to use custom roms on their phones, so I don't think you need to worry about that.
Click to expand...
Click to collapse
Lol you're right i switched the name of the keyboards xD, but none of them is illegal apparently
So with all of this said, custom roms doesn't mean 'hacking' and therefore not illegal, right? I think my question is fully answered now then, thanks mate
Cheers :good:
let me jump in and share my thoughts. hacking has 2 categories (i think), developmental and the other one i call destructive (i dont need to explain the difference, do i?) like previously stated, any licensed and paid apk if bundled with the rom is illegal including the gapps. thats why gapps is flash seperately (see the bold thing is what makes the difference). i dont know about manufacturers allowing their default apks to be used and distributed by cookers but maybe they see its a good thing rather than being pestered by consumers about having an upgrade of the old phones. i have an htc and xperia and both offers bootloader unlocking feature/tutorials, which i think they know why we are unlocking it. they are aware and support it. maybe they are looking for apks that could help their brand soar. who knows, when you develop one and they buy them.
:laugh:
demoniacs said:
let me jump in and share my thoughts. hacking has 2 categories (i think), developmental and the other one i call destructive (i dont need to explain the difference, do i?) like previously stated, any licensed and paid apk if bundled with the rom is illegal including the gapps. thats why gapps is flash seperately (see the bold thing is what makes the difference). i dont know about manufacturers allowing their default apks to be used and distributed by cookers but maybe they see its a good thing rather than being pestered by consumers about having an upgrade of the old phones. i have an htc and xperia and both offers bootloader unlocking feature/tutorials, which i think they know why we are unlocking it. they are aware and support it. maybe they are looking for apks that could help their brand soar. who knows, when you develop one and they buy them.
:laugh:
Click to expand...
Click to collapse
Be my guest then xD. As long as the Hacking type isn't the Bad One/Illegal One then that's fine xD.
I don't know about that one either, because it's true that the keyboard apk came with the phone, but that keyboard is being used in a 'Unofficial' Android Version not created by them but yes by someone else, i don't know if they allow it like that even if it is for the same phone.
Yes in reality they know everything we do, and everyone knows about hacking and cracking but No One does a damn thing about it xD.
I think Sony should buy Android 2.3 from this website and perfect it for our phone, but i don't see that happening xD, i would say Android 4+ but it's too much for this phone xD.
:laugh:
Crazy Seed said:
Be my guest then xD. As long as the Hacking type isn't the Bad One/Illegal One then that's fine xD.
I don't know about that one either, because it's true that the keyboard apk came with the phone, but that keyboard is being used in a 'Unofficial' Android Version not created by them but yes by someone else, i don't know if they allow it like that even if it is for the same phone.
Yes in reality they know everything we do, and everyone knows about hacking and cracking but No One does a damn thing about it xD.
I think Sony should buy Android 2.3 from this website and perfect it for our phone, but i don't see that happening xD, i would say Android 4+ but it's too much for this phone xD.
:laugh:
Click to expand...
Click to collapse
In the end, Sony would rather sell us a new phone, but they (or anyone else for that matter) don't make phones like ours anymore.
But I think, with the work Google has put into KitKat, it should run better on our phones then ICS or JellyBean, so it's kind of a shame we don't have developers capable of porting it anymore.
That said, I still think it's very cool we've got Jellybean ROMS that run ok, and I'm very grateful for all the effort that has gone into development in that respect, even if it's not as fast as Gingerbread ROMS or even the original firrmware.
Let's just finish by this: If it was all illegal, then XDA wouldn't exist anymore, it would have been litigated out of existence by any of the big phone-manufacturers or phone-operating-systems-producers.
SmG67 said:
In the end, Sony would rather sell us a new phone, but they (or anyone else for that matter) don't make phones like ours anymore.
But I think, with the work Google has put into KitKat, it should run better on our phones then ICS or JellyBean, so it's kind of a shame we don't have developers capable of porting it anymore.
That said, I still think it's very cool we've got Jellybean ROMS that run ok, and I'm very grateful for all the effort that has gone into development in that respect, even if it's not as fast as Gingerbread ROMS or even the original firrmware.
Let's just finish by this: If it was all illegal, then XDA wouldn't exist anymore, it would have been litigated out of existence by any of the big phone-manufacturers or phone-operating-systems-producers.
Click to expand...
Click to collapse
Or we could always buy Xperia Mini Pro 'difference is not very big beetween them', but it's a little expensive and the benefits are almost nothing since Xperia Mini Pro x10 has great quality in Music, Image, Video with the only letdown being the Android Version + CPU capacity.
Yes Kit Kat should run better on our phones, but it's also true that right now there's nobody capable of porting it to our phone :S.
Respect and Thanks for the efforts on the ICS Jelly Roms, and call me crazy but i think that if someone could fix some bugs from the ICS version then it could be perfect since almost everything is working, Jellybean is more difficult because of the Audio drivers for Sound quality making it almost impossible.
Yes they could finish this website if they had the rights to do so, apparently there's nothing wrong with custom roms so it's all ok, but it's also true that sometimes even if something is illegal people just close their eyes 'just like in piracy, everyone downloads songs movies etc and nobody does a damn thing about it because they know it's a fight they can't ever win'.
So with all said, everything is apparently legal and ok to go .
No, they're not illegal. Android is an open source community, as long as you conform with legal policies, you will be good to go!
Hi everyone
I have an LG Optimus Vu device and due to LG's tremendous support for this phone, the operating system is still ICS and the kernel version is 2.6.39 (even the I/O scheduler for this phone is set to noop, and there aren't any alternatives :| ). It could be all good and well if there aren't hundreds of crashes appearing every day about different applications, which is driving me crazy. I've searched and searched and it seems that there are no custom ROMs for this phone, nor is there any custom recovery application. I could barely find an application to root this phone.
To get to the point; I'm considering to make a custom ROM for this phone, but I am a noob in these kind of stuff.
I have the kernel source and the original ROM zip file. Since the original OS version is 4.0.4, is it possible to bring the required proprietary drivers from the original and use it in a newer Android version like 4.4.x?
Can I use Google's recent Tegra 3 kernel (3.10) and port those LG specific drivers from the older kernel?
Am I even starting this process in the correct way?
Any help is appreciated.
set-0 said:
Hi everyone
I have an LG Optimus Vu device and due to LG's tremendous support for this phone, the operating system is still ICS and the kernel version is 2.6.39 (even the I/O scheduler for this phone is set to noop, and there aren't any alternatives :| ). It could be all good and well if there aren't hundreds of crashes appearing every day about different applications, which is driving me crazy. I've searched and searched and it seems that there are no custom ROMs for this phone, nor is there any custom recovery application. I could barely find an application to root this phone.
To get to the point; I'm considering to make a custom ROM for this phone, but I am a noob in these kind of stuff.
I have the kernel source and the original ROM zip file. Since the original OS version is 4.0.4, is it possible to bring the required proprietary drivers from the original and use it in a newer Android version like 4.4.x?
Can I use Google's recent Tegra 3 kernel (3.10) and port those LG specific drivers from the older kernel?
Am I even starting this process in the correct way?
Any help is appreciated.
Click to expand...
Click to collapse
Hate to be the bearer of bad news, but you're pretty much stuck. LG has locked the bootloader on it and has said they have no plans on unlocking it. Since the phone is around a year and a half old or older, I'd imagine they aren't going to change their minds all of a sudden for the relatively small amount of people still using the phone.
http://forum.xda-developers.com/showthread.php?t=2055272 - discussion about your phone here
FYI
What is a bootloader?
The bootloader is the first thing that starts up when a phone is turned on. At its most basic level, a bootloader is the low-level software on your phone that keeps you from breaking it. It is used to check and verify the software running on your phone before it loads. Think of it like a security guard scanning all the code to make sure everything is in order. If you were to try to load software onto the phone that was not properly signed by the device vendor, the bootloader would detect that and refuse to install it on the device.
When we speak about locked bootloaders, the context is often used to give meaning to the term “locked.” Almost all phones ship from the factory with locked bootloaders, but some are encrypted as well. It is this encryption that most reports are referring to when using the term “locked.” If a bootloader is encrypted, users can’t unlock it to load custom software of any sort. The device will be restricted to running software ROMs provided by the manufacturer.
Now, there are ways to unlock or circumvent bootloaders in special situations, but with ones that have no dev support like yours, it's pretty much a lost cause and most likely way beyond your capabilities to figure out without spending 100s of hours of learning about Android stuff. This is not a knock on you or anything of the sort, but it is what it is. It is a very difficult thing to figure out encrypted bootloaders even for the most experienced android developers and hackers and depending on how they are encrypted, there just might not be a way (ask the older Moto phones, especially from VZW).
es0tericcha0s said:
Hate to be the bearer of bad news, but you're pretty much stuck. LG has locked the bootloader on it and has said they have no plans on unlocking it. Since the phone is around a year and a half old or older, I'd imagine they aren't going to change their minds all of a sudden for the relatively small amount of people still using the phone.
...
Now, there are ways to unlock or circumvent bootloaders in special situations, but with ones that have no dev support like yours, it's pretty much a lost cause and most likely way beyond your capabilities to figure out without spending 100s of hours of learning about Android stuff. This is not a knock on you or anything of the sort, but it is what it is. It is a very difficult thing to figure out encrypted bootloaders even for the most experienced android developers and hackers and depending on how they are encrypted, there just might not be a way (ask the older Moto phones, especially from VZW).
Click to expand...
Click to collapse
Two thumbs up for the detailed reply.
Shame really. The phone was released in November 2012 but there wasn't a single OS update...
I guess I would have to give up on that, but I'm interested in system level developments for both Android and desktop systems. Any idea where to start?
set-0 said:
Two thumbs up for the detailed reply.
Shame really. The phone was released in November 2012 but there wasn't a single OS update...
I guess I would have to give up on that, but I'm interested in system level developments for both Android and desktop systems. Any idea where to start?
Click to expand...
Click to collapse
Yea, it does suck. That's one of the downfalls to making 8 million different phones. You have no incentive ($$$), no interest, and no manpower to be able to update them all in a reasonable fashion. But it's not like LG is alone. All of the manufacturers have had decent phones just...disappear in regards to updates or anything of the sort.
As far as getting started, there is a ton of info right here on XDA:
http://xda-university.com/
Modify hashes?
Hi!
Sorry for digging out a dead thread, but for the p895 probably all threads are more or less dead...
I wonder if it is really necessary to decrypt the bootloader. Since it must be able to boot different versions of the stock roms, it would probably only calculate a hash value of some files and compare that to a value stored elsewhere.
By comparing different versions of stock roms it might be possible to get some information about what files are hashed. If it is a standard hash algorithm and the comparison value the bootloader uses is stored in plain text (hope....!) there might be an atack vector in
comparing several known plain texts.
I also noticed, that the p895 has a "software integrity check" in the hidden menu that shows has values for some (a lot) of files. these hash values are likely already calculated when entering that menu option (i am pretty certain because they show immediately), so they might belong to the files checked at boot time and also hint to the hash algorith used.
The idea is to calculate a hash value for the custom rom and put it in the appropriate place so the bootloader thinks of the rom as an update.
These are just vage ideas, but i have no intention whatsoever to buy a new phone anytime soon and I guess I could as well spend "some" time tinkering and learning the tech details...
thank you!