i want to know that how can i get the assembly codes passed to the arm processor.. or you can say i want to make a software where the the the assembly (opcodes) will be passed to a software.. thanks you
Related
So reading the SE product launch blog the latest post is a q & a and one of the questions was:
Q: Why do you lock the boot loader of your devices? Isn’t Android supposed to be open source?
and the answer they gave was:
A: Yes, Android is an open source platform. Anyone can download it, modify it to their liking and install it on hardware they have designed. A mobile device is much more than the operating system. In our phones there are functionality that have to be secure such as SIM-lock and DRM. We currently don’t have a solution in place to secure that while opening the bootloader and therefore it would break legal agreements with many of our partners if we do.”
so, what do you think, could all the pain be due to sim-lock and drm or is this just a lame excuse?
source:
http://blogs.sonyericsson.com/products/
SIM-Lock removed without unlock bootloader.
Is this just a lame excuse.
System cracked and root rights already obtained.
There is no reason to hold a bootloader closed. 4 bilds a cracked and next builds will be hacked...
this is just a lame excuse. the new xperia series, of course needs to be marketed, and who would buy them if the x10s are even better than the Arc?
SE intentionally locked the bootloader for business purposes, not to secure something. legal contracts with their partners? come on, they might be talking about the company's shareholders.
OK, so I've had Android since the G1, then the Vibrant and now the SGS2 so I'm familiar with flashing and rooting and all that good stuff but some of the basics elude me...
I'm not a coder, programmer or modder in any way, shape or form. Nor do I claim to be.
Here's my question. Google writes the source code for the Android OS, then releases it to manufacturers to add their bloat/spin (TouchWiz, Sense, etc). If the underlying code is the same, why is it not easier to take the original source code and flash it on any phone?
I'll use Windows as an example here:
If I buy a PC with Windows Home Premium on it from HP, I'll get all of the extra bloat that HP puts on the machine to "enhance" my experience. However, if I decide to, I can format (or flash) my PC and install a "clean" version of Windows (direct from Microsoft) on it direct from CD or DVD. Doesn't matter if I format and install on an HP, Dell, Gateway, Acer, etc. because the source code is same. Aside from a couple of driver issues, on first boot, everything works.
Why is it not the same for Android on the phones? Is getting the code for the drivers what holds us back?
The other bonus is that even if something goes wrong, since I essentially rooted my PC (I removed what was originally installed on the PC and put the original source code on it) I can still send it in to get repaired to HP or Gateway or Dell. I can't do that with a phone. If I root my phone, my warranty is void. Even if the hardware is defective.
Windows has a "minimum hardware requirements" that a PC must meet in order to run Windows.
Why would Google not have a similar requirement? "A phone must have these specs to run Android."
I understand that Sense, TouchWiz, etc will add bloat to the interface but (and maybe I'm naive here) it shouldn't be that hard to get back to the source code on the phones, should it?
Help me. I don't understand. Again, I'm not a coder, programmer or modder in any way, shape or form. I root my phone(s) and try to get as close to the original source code as I can but I rely on smarter people to get me there. Granted I could buy a Nexus device and not have to worry about it. However, that just goes to further emphasis my question; Google pushes original source code out to the Galaxy Nexus, Nexus One, Nexus S. So why is it not easier to get that same source code on other phones?
Thanks in advance...
-Steve
The reason you void your warranty with rooting is simply because that's what you agree to when you purchase it. Just something that carriers/manufacturers have gone with and we as consumers haven't fought it. Realistically it might be something that could be addressed in court or through the FCC. If you buy a car and modify it, if something fails unless the dealership can prove that your modification caused the failure they still have to cover the repair under warranty. That said, for now the majority accept it and the majority still do not root and such so it's accepted. Perhaps as more people become aware of what can be done with their phones, especially if companies start using apps like Tasker to increase efficiency of their corporate devices, there's the possibility that this will change.
Buying an Android device, the warranty covers the system installation. Buying a PC, it does not.
The reason you void your warranty with rooting is simply because that's what you agree to when you purchase it. Just something that carriers/manufacturers have gone with and we as consumers haven't fought it. Realistically it might be something that could be addressed in court or through the FCC. If you buy a car and modify it, if something fails unless the dealership can prove that your modification caused the failure they still have to cover the repair under warranty. That said, for now the majority accept it and the majority still do not root and such so it's accepted. Perhaps as more people become aware of what can be done with their phones, especially if companies start using apps like Tasker to increase efficiency of their corporate devices, there's the possibility that this will change.
kuisma said:
Buying an Android device, the warranty covers the system installation. Buying a PC, it does not.
Click to expand...
Click to collapse
I appreciate the feedback and I get the analogies, however, my original question remains unanswered:
Why is it so difficult to get the original source code onto any android device? Is it drivers? Manufacturer incompatibility?
I'd be interested to learn the process (just a general overview and hopefully in English) it takes to port the original source code onto multiple devices.
Thanks again...
-Steve
brisseau said:
Why is it so difficult to get the original source code onto any android device? Is it drivers? Manufacturer incompatibility?
Click to expand...
Click to collapse
Hardware manufacturers develops specific hardware suitable for their devices, requiring special drivers and/or kernel modifications.
The radio code is not a part of the Android OS, and only the Radio Interface Layer (RIL) must conform to the Android API specs.
Hardware manufacturers are free to vary installation parameters such as what disk types to use (mmc, mtd), sizing of partitions to best utilise the available space, etc.
As in the subject - is possible to rebuild unit who is now RK3188 - 800X480 to RK3188 with 1024X600?
Which hardware parts need to be changed, display only? What else?
I have Klyde unit.
the screen resolution has nothing to do with RK3188
it depends on your screen.
So if I would buy new screen 1024X600 and just replace with old, it will be working? And also just update ROM form old to ROM 1024X600?
I have done it on my Klyde. I contacted them and requested for a screen with TP (make sure they send them glued together, not separate as they did in my case ) and the corresponding firmware.
Very easy modification. Took me 5 minutes to do it.
ga!nusha said:
I have done it on my Klyde. I contacted them and requested for a screen with TP (make sure they send them glued together, not separate as they did in my case ) and the corresponding firmware.
Very easy modification. Took me 5 minutes to do it.
Click to expand...
Click to collapse
Could you give us some details? Where can we order this 1024x600 screen?
I have a KLD unit too, and I want to make this modification.
Thanks
Balazs
Hey, interested in this also. How much did the screen cost if you dont mind me asking? A link would be great?
ga!nusha said:
I have done it on my Klyde. I contacted them and requested for a screen with TP (make sure they send them glued together, not separate as they did in my case ) and the corresponding firmware.
Very easy modification. Took me 5 minutes to do it.
Click to expand...
Click to collapse
I need this upgrade too, how I know whats my unit is KLD or whatever the model is from?
and please let us know where u get the screen from
ga!nusha said:
I have done it on my Klyde. I contacted them and requested for a screen with TP (make sure they send them glued together, not separate as they did in my case ) and the corresponding firmware.
Very easy modification. Took me 5 minutes to do it.
Click to expand...
Click to collapse
Hello
THANKS you for your feedback could you please provide us more detail and link tout buy it?
Thanks in advance for your help
any news?
based on your head unit model the screen, touch screen and the digital board that powers the screen need to be changed to switch to 1024x600 resolution.
parts you can resue are basically the SoM and the motherboard.
I repair many head units daily.
doctorman said:
based on your head unit model the screen, touch screen and the digital board that powers the screen need to be changed to switch to 1024x600 resolution.
parts you can resue are basically the SoM and the motherboard.
I repair many head units daily.
Click to expand...
Click to collapse
so, is there any possible way to do it?
Sorry, I lost this discussion. I just found it again.
As doctorman said, i had to change the LCD and touchpanel, and the digital board that powers the screen as the connector is different.
I don't know the exact price as i also upgraded the PCBA with the processor to pass to quad core and it was around 100usd in total
ga!nusha said:
Sorry, I lost this discussion. I just found it again.
As doctorman said, i had to change the LCD and touchpanel, and the digital board that powers the screen as the connector is different.
I don't know the exact price as i also upgraded the PCBA with the processor to pass to quad core and it was around 100usd in total
Click to expand...
Click to collapse
Thank you for the explanation however where you found thé part?
A link will be very appreciate ?
I have contacted Klyde directly on alibaba. After a few hours of negotiation they agreed to send me the spare parts.
I searched for the parts on ebay but i could not find them.
thank you for your feedback
Hello dear, as they are, I introduce myself, I'm Martin from ARGENTINA.
I have an S7 Edge that I could take out of the negative band by changing the IMEI. It broke my brother and after a while without using it could not register more in the NET .....
I was able to perfectly do it myself to all the work while I had Nougat 7 .....
I updated it to OREO 8 and I could not re-patch the certificate ..... looking and searching to find that it can only be done with versions 31.1 or higher of SamsungTool Z3X .... the version I have is 29.5 with crack Without Box ....
What I had to do was take the phone to a Service and patch the certificate with the BOX ....
After that, at the time, I blocked the Bynary for security frp ...... as I was getting the new phone (MiA1) I flashed it back and left there without using the S7 ....
someone has some crack version of Z3X higher than 31 to use without box ??? It hurts me that such a phone is there in disuse.
Greetings.
that "crack" you`re looking for will bypass the paid feature of that tool so no, you won`t receive any help here on XDA for such cracks
Forum Rules
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
thread closed
Hi,
I was thinking about LG and their bootloader .bin files.
I have a non-european version of the H870 and thus due to LGs bad decision to withhold unlock codes to certain regions I am completely unable to root this device.
Now, when I want to crack a AMD64 architecture unlock code, you run it through a debugger and inspect the assembly code to find the algorithm. a Good reverse engineer doesn't just crack the application, he makes a keygen. So using assembly you can completely dissect the algorithm used cuz the devices/software still has to compare it to the correct code, and it has to run the algorithm for that.
So my question is: How come I can't just clone the LGs partitions, run it in an emulator and dissassemble it to find the algorithm used?
Would the algorithm not be in the fastboot partition? Cuz that is a tiny partition and finding the needle in that hypothetical haystack seems not that difficult.
It seems to me that if it was possible someone else would have done it already, so why haven't they? What am I missing?
Post by aac_j
Trying to crack the algorithm by inspecting unlock.bin files to try and devise the algorithm used is a waste of time, I mean you might even get lucky and find it but the probability of that is so tiny that I think it's a completely futile endeavour.
Brute forcing it is also not feasible.
So the only way would be to inspect the assembly, no?