I was going through the process of patching a kernel for EBI1 and I got to looking at the code for the patch.
To summarize.
Its the addition of an offset
Code:
* physical offset of RAM */
+#if defined(CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1)
+#define PHYS_OFFSET UL(0x19200000)
+#else
#define PHYS_OFFSET UL(0x10000000)
+#endif
2 Memory maps decided upon by an IF statement in board-troat.h
Code:
#if defined(CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1)
3. Changes to board-troat.c to work with new memory map values.
Shouldnt we be able to:
1. Add a little list to the header file defining which radios are EBI0/1.
2. Read the command line from the SPL for "androidboot.baseband=".
3. Alter the memory map accordingly, possibly having all Dreams use an offset?
4. Be a one kernel community
Ive been doing more reading and see how my comment about all dreams using the same offset is.. wrong. My current cobbled understanding is that, the radio sends commands to the cpu setting up hardware addresses for the sdram. Im open to correction though.
I put together these maps using the board-troat.h files. I'll post them to see if anyone finds them useful/interesting. If they're incorrect let me know and I'll fix them or take them down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why does an EBI1 phone have double the camera memory? and that extra memory on a EBI0 phone is unmapped? Why would an EBI1 framebuffer be shrunk down? Cam anyone shed some light on the situation. Ram Hackers Maybe.
More importantly though, can any logic or command line be applied to zreladdr-y, params_phys-y and initrd_phys-y so the kernel can know off the hop where to start in ram?
OR
Can we use enough SMI to boot a kernel since the addressing seems unified?
I've been continuing my reading in my bits of spare time and heres where im at.
-The SPL Reads the boot Image from nand.
-Examines its base address from the header and copies the image to that location.
-The Decompressor runs and extracts to zreladdr
-?? ram drive is extracted (by arch/arm/boot/bootp/init.S ?)
-kernel is executed at zreladdr
Is the Base address that mkbootimg puts into the boot image header pass to the decompressor? It seems to me it must to function.
If it is than this patch seems like it is close to what would be needed, accept I dont think it would handle the initial ramdrive.
This bases on work done earlier by Lennert Buytenhek and Mark A. Greer.
Compared to their approach zreladdr isn't guessed based on the pc
register but the bootloader is expected to pass PHYS_OFFSET in r3. If
that value doesn't look right (e.g. isn't aligned) it is guessed based
on the value of sp. This should work for CONFIG_ZBOOT_ROM, too.
To use it for your machine removing the definition of PHYS_OFFSET from
<mach/memory.h> and selecting CONFIG_RUNTIME_PHYS_OFFSET should be
enough.
Click to expand...
Click to collapse
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-January/008994.html
Im not even sure whether posting as I go is the right approach. I dont know if I havent gotten a comment because the concept is just flawed, in a way that im not realizing, or its just such large amount of work noone has found it worth while. I Do realize that my comments show that I don't have the skills to complete this on my own but as I read more and more It just keeps looking like it should be possible. So I will continue to conceptualize this idea until I'm told why its not possible/practical, and hopefully someone with coding skills sees the value and takes the lead.
There's not a whole lot of interest for some reason. I'm on a Rogers Dream with EBI1 kernel so this does affect me. But most xda user are American and don't care about EBI1 since they only have the mt3g1.2
xaueious said:
There's not a whole lot of interest for some reason. I'm on a Rogers Dream with EBI1 kernel so this does affect me. But most xda user are American and don't care about EBI1 since they only have the mt3g1.2
Click to expand...
Click to collapse
Your phone is perfectly compatible with EBI0 radios. Why not just fix it?
lbcoder said:
Your phone is perfectly compatible with EBI0 radios. Why not just fix it?
Click to expand...
Click to collapse
as I have.
Related
Hi, this is my first post so please if I make some mistakes be patient (I'm really dummy and sorry for mistakes) ..... I've been trying to solve the problem for lots of time but no success for now. Ok let's focus on details:
What I want to do: to be able to rotate the screen.
The device: non standard bought in Poland, based on centrality atlas, win core 5.0; There is no way to flash rom, have only soft reset restoring windows folder to original state, this is a gps device which was unlocked and able to run lots of apps. but the problem still remain the same - no rotation gained.
Not working: trying lots of stuff like nydiot but none worked and even caused problems with synchronization via activesync
Recently I've focused on ace_ddi.dll and found an app. called ace_ddi.dll rotator. Guess what? it started to work but partly. If I change the screen from 320x240 (default) to 240x320 the rest of the window is beyond the display. If I restore 320x240 I've got two taskbars one at top (not default) and one at bottom (default), but this one is not working.
The package I am using consitis of:
ace_ddi.dll
rotator.exe
screenrotateservice.dll
srswrapper.dll
vsd_setup.dll
srs.cpl
Here's what going on the screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Btw. one more question If I overwrite for example ddi.dll in windows directory does the system use new ddi.dll or the old one was preloded into the memory ?
Now I am really stuck what to do. Ive asked for help in Microsoft and others forums but no one is able to answer my questions or give a hint what to do.
If You have any ideas, please, help it's really cheap but worth working device and it would be grateful to change the orientation of the screen.
If the topic is miplaced, please, move it to the appropriate place.
Thanks for all help.
Hello and welcome to the forum.
Though usually questions like this would be better off in General forum I will not move it because that forum gets too much traffic as it is.
As for your question:
There is no way to rotate the screen. Screen rotation is part of the display driver and only the OEM (the maker of the device) can provide that.
Windows CE (which is what your device is running - its different from Windows Mobile) is a very modular system - like Lego.
Most manufacturers of navigation device strip out any unnecessary components, sometimes even the shell and file explorer to conserve memory.
So though some functionality can be restored to these devices via 3rd party apps they can never do everything regular PDAs do.
As for replacing the dll: if the file you overwrite it with is compatible with the device (processor / OS) it should function but you may need a reset (the kind that does not delete files).
Thank You for your reply. It's really hard to believe that it's not possible to rotate the screen but I'll have to accept this. Not to found another topic I intend to ask some more question here (mainly it's also connected with display and rotation) I'll be grateful for your answers:
1. Is there any software that can change the orientation of the screen and is worth installing ? We have to remember that the windows folder is back to original state after restart or reset.
2. There's possibility of changing shell-folders in registry like MyDocuments and so on what I've already done, but one entry I leave unchanged it's "windows" I am afraid of changing that and hanging my device. Question is: if I change this entry the new path provided in this section will make another path for windows or it will change the current ? Is it safe to change the value of this key ? I would like to force the system to load from normal \windows directory and force to load some additional files from my new \windows directory placed on sd-card.
3. I've got problems with forcing apps to display eastern fonts - mainly polish, could give me a hint ?
Thank You very much for your help and looking forward to hearing from You.
Some guys over in the g1-hackers list managed to code a kernel hack that allows you to dump the nand flash.
So here is the nand flash file...
http://www.2shared.com/file/4394944/b791a62e/nand.html
Have Fun!
-Nikropht
Thanks for sharing this. You are lightning fast in spreading the word...
The trick was actually simple. The linux kernel on the G1 uses the nand flash as partitioned mtd device. As partitioned device only the separate partitions are readable easily from userland. The "hack" was to double-register the whole device next to the partitions and voila we where able to dump the first pages of the nand containing the boot loader.
In case anything got corrupted on it's way here is another link to the file: http://www.mediafire.com/?akjmuueyiii
Well I'm eager to facilitate hacking this device. I'm not totally in love with java and would love to see the G1 run X.
-Nikropht
the possible implications of this..?
Im no coder but I do some electronics modding (fones,tivo,consoles,smartcards,hardware hacking) but doesn't this mean that the damn thing is owned/pwned?
So now the bootloader and all the stuff that goog didnt open source is in the wild to be picked apart by the powers that be?
Im just making some assumptions and asking some questions to see just what this does for the g1 and its modding community...
bhang
bhang said:
Im no coder but I do some electronics modding (fones,tivo,consoles,smartcards,hardware hacking) but doesn't this mean that the damn thing is owned/pwned?
So now the bootloader and all the stuff that goog didnt open source is in the wild to be picked apart by the powers that be?
Im just making some assumptions and asking some questions to see just what this does for the g1 and its modding community...
bhang
Click to expand...
Click to collapse
bhang, this is the low level code that runs before the android os launches. What this does is open the door for a hack that will re-root G1's running Rev30.
-Nik
I noticed something very interesting while looking at the nand dump in my hex editor...
Not only did i see some bits about factory test mode, but at i was scrolling through what seemed to bee all FF's I ran across letters, numbers and symbols made up of the absence of the FF's. This starts at 0x02466B10.
See pic attached.
-Nikropht
so again for slowly me...
there is a chance that I got a modded RC30 even if I am on OTA RC30, now?
That are fantastic news.
can i make a small smile on my face ?
sputnik99 said:
so again for slowly me...
there is a chance that I got a modded RC30 even if I am on OTA RC30, now?
That are fantastic news.
Click to expand...
Click to collapse
OK.. we dumped the boot loader for the G1. (The most common linux boot loader is LILO)
This means that after some crazy disassembly, we could write/hack a replacement boot loader.
This would allow us unlimited access to the hardware and then we can run whatever OS the cpu can run.
-Nik
Actually there is a lot of plain text in the dump file starting from:
0x0246EE6E
Nikropht said:
OK.. we dumped the boot loader for the G1. (The most common linux boot loader is LILO)
This means that after some crazy disassembly, we could write/hack a replacement boot loader.
This would allow us unlimited access to the hardware and then we can run whatever OS the cpu can run.
-Nik
Click to expand...
Click to collapse
So you can flash back onto the boot loader partition as well?
so..to quote bhang......
PWNED, then TEABAGGED . thats cool news, I am no programmer, but the door seems to be wide open now......cool.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is great news!
alansj said:
So you can flash back onto the boot loader partition as well?
Click to expand...
Click to collapse
This will be possible, yes.
Great news guys! I bought a G1 that already had RC30 installed so I was screwed from the beginning.
RC30
........at Least You Still Have Your Sense Of Humor.......root?, No......humor.......bingo!
LvDisturbed1 said:
Great news guys! I bought a G1 that already had RC30 installed so I was screwed from the beginning.
Click to expand...
Click to collapse
damn - my G1 is waiting for me at home (just arrived today), and I was hoping it woudl still have rc29 on it. Guess they're shipping rc30 in box now. Damn!
Thanks for the update, and great job on the nand dump. Looking forward to seeing the inevitable awesomeness coming soon
Awesome news, this phone has been a huge disappointment for many including myself. I cant wait to see what she can do in the hands of the right people
awesome news....this combined with the release in europe, expect to see great things =)...them europeans have some insane talent.
I am in love again !!!
Thanks and keep it up!
Click here and help us getting to the XDA main page.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an official thread about AndrOINC - BOINC project created by Sesef and OxyOne from Polish National Team.
Informations
Official name: AndrOINC
Motto: For Motorola Milestone freedom
Website:
Creators: Sesef and OxyOne from Polish National Team(BOINC.pl)
Special thanks to:
pontomedon - for creating the MilestoneRSA project and putting everybody one step closer to Milestone freedom
Platforms:
Windows x86 - supported
Windows x64 - supported(with app from x86)
Linux x32 - currently working on
Linux x64 - currently working on
GPU application ATI + nVidia - very soon
What is it?
AndrOINC is a BOINC project trying to break a 1024 bit RSA key used by Motorola to sign the boot and recovery partitions on the Motorola Milestone. If this key could be broken, we would be able to sign our own boot/recovery images, which would enable us to run custom kernels and recovery images on the Milestone.
//Will be updated later
Reserved for future use.
Let's get started, I'm sure all of us together can achieve it.
What about the possibility of searching not just the milestone key but also the ones from other moto models to increase the audience ?
It's already going to take till the end of time to find the Milestone without adding extra verables to the mix.
DannyDroid said:
That would length the time on all they keys.
Click to expand...
Click to collapse
My skill on symmetric encryption is almost zero, so sorry for the dumb questions.
This mean that every motorola phone has a different pair of public and private keys ? There isn't a single public motorola key, right ?
I have joined this project
Team Canada ready for joining.
Thanks for the project hosting
just a sec - AndrOINC? nobody told me there'd be pigs involved!
seriously, though: congratulations and thanks for the effort. count me in.
registered
what happened to previous boinc project?
bijixda said:
registered
what happened to previous boinc project?
Click to expand...
Click to collapse
Unfortunately, the MilestoneRSA has been aborted and we have to start from scratch....
However the good news is that we are going to use optimized worker from PNT and they are goin to provide GPU support as well.. so we'll cover up the wasted work sooner than later.
joined in (tough its just a laptop). can't wait for the bootloader to be cracked.
source code of the worker so we would actually know what are we computing?
Alternative Quicker Method?
Started helping you guys out with some computing cycles.
I know nothing about encryption, but a team from Univ. of Michigan broke 1024-bit encryption quickly by altering voltage to cause CPU faults. We can easily control voltage on Milestone and DX...anyone looked into their paper and its application to unlocking the boot loader faster than a brute force method?
engadget.com/2010/03/09/1024-bit-rsa-encryption-cracked-by-carefully-starving-cpu-of-ele/
ns.umich.edu/htdocs/releases/story.php?id=7551
I'll join as soon as the linux client will be available .. Can i use it first and then switch to the one with CUDA support?
yes, I think BOINC will just have to update the worker itself to support CUDA, not the whole client
However, since they mention Nvidia and ATI support, they won't be using CUDA (nvidia only)
man these WUs are fast. I'm doing 6 minutes compared to 12 hours on my x86 Win7 VM with 2Gb on my MacPro.
DigiK said:
Started helping you guys out with some computing cycles.
I know nothing about encryption, but a team from Univ. of Michigan broke 1024-bit encryption quickly by altering voltage to cause CPU faults. We can easily control voltage on Milestone and DX...anyone looked into their paper and its application to unlocking the boot loader faster than a brute force method?
engadget.com/2010/03/09/1024-bit-rsa-encryption-cracked-by-carefully-starving-cpu-of-ele/
ns.umich.edu/htdocs/releases/story.php?id=7551
Click to expand...
Click to collapse
They way I see it, you would have to alter the voltage at boottime since that is when the keys are being checked.. this is not the same as tweaking the vsel if this is what you refer to with "we can easily control the voltage"
So I don't know if would be that easy to do.. But hey, I'm not an expert or something
SophT said:
man these WUs are fast. I'm doing 6 minutes compared to 12 hours on my x86 Win7 VM with 2Gb on my MacPro.
Click to expand...
Click to collapse
or the workunits are very small...
Joined. Hopefully we will win
Long time no see.
Any way there is a new build this one is based on the latest and greatest from CM 7.1. the download link is below.
Spoofed permissions:
READ_PHONE_STATE - You can now make your device return spoofed data from the methods protected with READ_PHONE_STATE permission. There is a demo app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you can use to see the effect of spoofing and revoking READ_PHONE_STATE permission. Run the app revoke or spoof run the app again.
Since majority of time spend on READ_PHONE_STATE spoofing was about laying the needed infrastructure for spoofing in general, expect new spoofed permissions shortly.
ROM info:
This is a preview build bases on CM7 nightly builds. Some things may not work some features may be missing.
Some applications may not work properly with revoked permissions.
You can revoke permission of SYSTEM applications!!! DON'T DO IT UNLESS YOU KNOW WHAT YOU ARE DOING.. However reboot resets the permissions of the system applications so you probably can recover.
If an application is running changing some permissions like say INTERNET will not be fully applied until the application is restarted.
If you come from CM7 nightly or CM7 RCx you probably don't need to wipe. I something is not working do a wipe.
Google apps are not included. You need to download them separately and flash them right after the ROM.
It will probably require ClockworkMod 3.x to flash properly.
You uses it at your own risk and I cannot be held responsible for the consequences.
Some technical stuff:
If an application checks for its permissions it will appear that all required permissions are granted. This is done to keep some ad networks code happy. As far as I've tested this is safe since the permission check is done at the remote end of the call when protected method is invoked. Please report your findings.
Screen shot:
This is the extended Manage application screen.
Download:
update-pffmod-7.1.0-Desire-KANG-signed.zip
old builds:
direct link: update-pffmod-0.9.1-Desire-DEV-20110418-signed.zip storage provided by: http://onlinestoragesolution.com
direct link: update-pffmod-0.9.0-DESIRE-DEV-20110328-signed.zip storage provided by: http://onlinestoragesolution.com
Wow, This is so quick, I read about it in Reddit day back. Thanks! Still there are lot of discussion about this between developers.
Details here
http://www.androidpolice.com/2011/0...rmissions-cue-mass-force-closing-as-a-result/
ukanth said:
Wow, This is so quick, I read about it in Reddit day back. Thanks! Still there are lot of discussion about this between developers.
Details here
http://www.androidpolice.com/2011/0...rmissions-cue-mass-force-closing-as-a-result/
Click to expand...
Click to collapse
Actually I've submitted this to CM
here is the original thread for Desire HD http://forum.xda-developers.com/showthread.php?p=12161601#post12161601
Great patch though Personally I feel this is great addition.Thanks for this! I'll try this and let you know.
new build with data spoofing see the first post.
Neat!
Is this based on something close to nightly 41? There's been a major bug recently, which caused many issues, it's fixen in #41.
http://cm-nightlies.appspot.com/?device=bravo
p.s.
Please add this to the CM branch...
JDima said:
Neat!
Is this based on something close to nightly 41? There's been a major bug recently, which caused many issues, it's fixen in #41.
http://cm-nightlies.appspot.com/?device=bravo
p.s.
Please add this to the CM branch...
Click to expand...
Click to collapse
This is like current git
Swapping real IDs for the word "spoofed" is quite obvious, and, IMHO, might cause problems if an application stores it as an integer value. Why don't you just return random numbers?
I'm working on something that will generate plausible data from the calling app package name. I'm just too impatient and decided to release it early.
The other thing is that it's bean too long since the last release
And a final request. Please do something with the usability Maybe a dropbox underneath each of the permissions. Best if colored - red for "revoked", yellow for "spoofed" and "granted" without highlighting. Currently, a brief view at the list of permissions totally misses their states.
Yes, I do understand the engine is far more important than bells&whistles, but as for me, the mod is quite ready for everyday use, and I'd be happy to see it more user-faced.
JDima said:
And a final request. Please do something with the usability Maybe a dropbox underneath each of the permissions. Best if colored - red for "revoked", yellow for "spoofed" and "granted" without highlighting. Currently, a brief view at the list of permissions totally misses their states.
Yes, I do understand the engine is far more important than bells&whistles, but as for me, the mod is quite ready for everyday use, and I'd be happy to see it more user-faced.
Click to expand...
Click to collapse
Interested in helping with that?
Just grab AppSecurityEditablePermissions.java, app_editable_permission.xml and app_editable_permission_item.xml from http://review.cyanogenmod.com/4055 and start hacking
New build... Link in the first post.
I have'nt seen this on the forum,so i thought i would post this,i think this is a cool mod,i use it to add custom to my rom,anyway this is not my guide,it was originally posted by Sam Sarsten.
It may not be the coolest thing you could mod on your rooted HTC EVO, but the build and software version numbers can be changed very easily. Whether you want to see your name, feel cool and have it say "Ice Cream Sandwich," or just want to screw with your friends and have it say "iOS 5," changing version numbers is fast and fun.
Normally on the stock ROM, when you go to Settings > About phone > Software information, things looks pretty boring. You might see the word "Shooter" or "Supersonic" with some numbers and periods after it. If you're rooted, your ROM dev has most likely changed this to the name of the ROM.
And now you can change it too.
To get started, you will need several items:
•Rooted HTC EVO (I'll be doing this with a 4G, but a 3D should work just fine)
•Root Explorer ($3.99) or other root file manager app
•What you want your new version numbers to be
This is really easy and only takes a few steps. So, let's get going!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first step to any modification is creating a Nandroid backup. Once this is complete, we can start the process, which is demonstrated in the video above and spelled out below.
Open up Root Explorer (or similar app) and go into the system folder. Make sure you hit the Mount R/W button in the upper right hand corner of the app and locate the build.prop.
Long press the build.prop file and then hit Open in Text Editor.
We want to edit one or two lines (you choose which files you want to edit):
1.ro.build.description edits the Build number
2.ro.product.version edits the Software number
I will change mine to say Good and EVO and Ice Cream Sandwich (v4.0.1), respectively.
When you are done editing the build.prop file, hit MENU and then Save changes.
Now, just reboot your HTC EVO (a hot restart is not enough).
Voila! You have a custom version number!
If you ever want to go back to stock, Root Explorer automatically adds a build.prop.bak (backup of your original file) that just needs to be renamed.
But, who would want to do that? I've added a new thread in the forums, so let's see what crazy version numbers you guys can come up with!
Heres a video.... http://www.youtube.com/watch?feature=player_embedded&v=PN4KlUik5_w
This might come in handy for someone starting out BUT I can already see the wheels turning on those trying to kang people's roms....hahahaha
mazdarider23 said:
This might come in handy for someone starting out BUT I can already see the wheels turning on those trying to kang people's roms....hahahaha
Click to expand...
Click to collapse
Lol,too funny.Yea i was thinking of putting something like...
Build Number:Cherry Pie OS
Software Number:6.1 Android
I like to mess with people,lol.
Diablo67 said:
Lol,too funny.Yea i was thinking of putting something like...
Build Number:Cherry Pie OS
Software Number:6.1 Android
I like to mess with people,lol.
Click to expand...
Click to collapse
The sad part about that is that someone MIGHT believe that you're actually running Android 6.1...hahahaa
i am running android revision 7.0.4. you;re a bit behind bro
tommytomatoe said:
i am running android revision 7.0.4. you;re a bit behind bro
Click to expand...
Click to collapse
I knew you were the man but Cot Damn... Leaving us all in the dust...
Sent from my PG8610000 using xda premium
Help
Can you please please tell me how to change tha image we see after sevral clicks on our android version number
Cool thanks