Got an OTA update notice this morning--my device is a developer seed from Verizon and I get OTA updates earlier than anyone else. Flashed the build and I now have an official, fully functional version of ICS!
System Version: 6.7.246.XT875.Verizon.en.US
Android Version: 4.0.4
Baseband Version: CDMA_N_05.13.01R LTEDC_U_09.14.00
Webtop Version: wt-3.0.0
Kernel Version: 3.0.8-g4328f8b [email protected] #1 SMP PREEMPT Thu Sep 20 17:31:11 CDT 2012
Build Number: 6.7.2-223_DBN_M4-23
Build Date: Thu Sep 20 17:14:54 CDT 2012
Awesome.
Sent from my DROID BIONIC using Tapatalk 2
Hans5849 said:
Awesome.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
Some skepticism on other forums. Hope it is significant but I do not have the expertise to know.
Lew
Good. Now they can move on to bring out JB. #GIT R DUN!!!
jakesteed said:
Got an OTA update notice this morning--my device is a developer seed from Verizon and I get OTA updates earlier than anyone else. Flashed the build and I now have an official, fully functional version of ICS!
System Version: 6.7.246.XT875.Verizon.en.US
Android Version: 4.0.4
Baseband Version: CDMA_N_05.13.01R LTEDC_U_09.14.00
Webtop Version: wt-3.0.0
Kernel Version: 3.0.8-g4328f8b [email protected] #1 SMP PREEMPT Thu Sep 20 17:31:11 CDT 2012
Build Number: 6.7.2-223_DBN_M4-23
Build Date: Thu Sep 20 17:14:54 CDT 2012
Click to expand...
Click to collapse
Calling BS on you getting it via OTAThis has been out since last week and many people have it.
Dougau said:
Calling BS on you getting it via OTA This has been out since last week and many people have it.
Click to expand...
Click to collapse
Not BS. Not sure if this is going to be the official FINAL build, but the fact I got it via OTA means that Motorola submitted this build as an official regression build for Verizon, and Verizon has accepted it internally.
Now, Motorola also went on record to say the Bionic update has been delayed, so they may be submitting another build at some point that will also have to go through Verizon's acceptance process. However, none of the previous builds were seeded to test devices via OTA, so that tells me this particular build is closer to final than anything else.
jakesteed said:
Not BS. Not sure if this is going to be the official FINAL build, but the fact I got it via OTA means that Motorola submitted this build as an official regression build for Verizon, and Verizon has accepted it internally.
Now, Motorola also went on record to say the Bionic update has been delayed, so they may be submitting another build at some point that will also have to go through Verizon's acceptance process. However, none of the previous builds were seeded to test devices via OTA, so that tells me this particular build is closer to final than anything else.
Click to expand...
Click to collapse
Okay, if Verizon did in fact push this to you, and now your saying there might be another build, how are you going to install it over .246?
Good for you! Perhaps the official OTA will come out in s month.
Where can I download it?
requesting obligatory screenshots that don't seem to be posted yet...
I mean really, make such a claim and then not back it up with some(what) hard evidence of any kind? Come on... you can do better than that.
I would hope nobody would play such a horrid trick on anxious bionic owners...
Sent from my DROID BIONIC using xda premium
Bionic owners have been getting the short end of the stick from Moto for the entire time.
JB_Da_Greatest said:
I would hope nobody would play such a horrid trick on anxious bionic owners...
The forums are filled with children with nothing to do. May their faces become covered with zits and their phones turn into bricks. Too bad they cannot find something constructive to do.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Lew
jakesteed said:
Got an OTA update notice this morning--my device is a developer seed from Verizon and I get OTA updates earlier than anyone else. Flashed the build and I now have an official, fully functional version of ICS!
System Version: 6.7.246.XT875.Verizon.en.US
Android Version: 4.0.4
Baseband Version: CDMA_N_05.13.01R LTEDC_U_09.14.00
Webtop Version: wt-3.0.0
Kernel Version: 3.0.8-g4328f8b [email protected] #1 SMP PREEMPT Thu Sep 20 17:31:11 CDT 2012
Build Number: 6.7.2-223_DBN_M4-23
Build Date: Thu Sep 20 17:14:54 CDT 2012
Click to expand...
Click to collapse
What part of the country are u in? I'm in central Texas and no OTA is available yet..
br0adband said:
requesting obligatory screenshots that don't seem to be posted yet...
I mean really, make such a claim and then not back it up with some(what) hard evidence of any kind? Come on... you can do better than that.
Click to expand...
Click to collapse
Oh it's real alright, just questioning if anyone really had it pushed out OTA. Every one can check away but your not going to see this pushed to your phone anytime in the next week or two I don't believe.
{
"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"
}
I hope to god that .246 is the final release version.
Stories said:
I hope to god that .246 is the final release version.
Click to expand...
Click to collapse
That's why it's important to have proof that some "Developer" for Verizon actually had it pushed via OTA and it's just not someone who is BSing on here. Motorola, not Verizon will be the ones who actually push it out.
Moto should just skip ICS and fast track JB to make up for all the delays.
I have had this for a while already. Let me know when some real OTA comes out.
Ics been out for almost a year and bionics get gifted by getting it soon. While some other devices get jelly bean
Sent from my DROID BIONIC using Tapatalk 2
Related
I saw something like this and thought it would be useful for us Droid 4 users since we have Android 4.0.4 leaks too.
Credit goes to CaptainKn0tz for giving me the idea.
Last Updated: July 15, 2012 -- 6:55 pm EDT
ALL LEAKS ARE NOT FASTBOOTABLE!!! DO NOT TRY TO FLASH 6.13.219 OVER AN ICS LEAK OR YOU WILL BRICK. I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE.
Current Motorola Ice Cream Sandwich Leaks for the DROID 4
System Versions
6.16.200.XT894.Verizon.en.US
6.16.206.XT894.Verizon.en.US
6.16.208.XT894.Verizon.en.US
6.16.211.XT894.Verizon.en.US
6.16.212.XT894.Verizon.en.US
6.16.213.XT894.Verizon.en.US
6.16.214.XT894.Verizon.en.US
6.16.215.XT894.Verizon.en.US -- Not to be confused with 6.13.215, which was the original version of GB the phone shipped with.
Latest Known Leak:
6.16.215
{
"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"
}
Android Versions:
.200/.206/.208/.211/.212/.213/.214/.215 = Android 4.0.4
Kernel Versions:
.200 =
3.0.8-gf93cec0
[email protected] #1
SMP PREEMPT Thu May 10 00:10:36 CDT 2012
.206 =
3.0.8-g4141d4c
[email protected] #1
SMP PREEMPT Sat May 19 20:38:32 CDT 2012
.208 =
3.0.8-gf863077
[email protected] #1
SMP PREEMPT Wed May 30 01:30:01 CDT 2012
.211 =
3.0.8-g29cf5e7
[email protected] #1
SMP PREEMPT Thu Jun 14 13:59:07 CDT 2012
.212 =
3.0.8-g29cf5e7
[email protected] #1
SMP PREEMPT Tue Jun 19 01:52:28 CDT 2012
.213 =
3.0.8-g29cf5e7
[email protected] 50 #1
SMP PREEMPT Wed Jun 20 18:44:39 CDT 2012
.215 =
3.0.8-g19a118c
[email protected] #1
SMP PREEMPT Wed Jul 11 21:01:15 CDT 2012
Webtop Versions:
.200 = wt-3.0.0
.206 = wt-3.0.0
.208 = wt-3.0.0
.211 = wt-3.0.0
.212 = wt-3.0.0
.213 = wt-3.0.0
.215 = wt-3.0.0
Build Dates:
.200 = Wed May 6 23:45:22 CDT 2012
.206 = Sat May 19 20:31:14 CDT 2012
.208 = Wed May 30 01:19:32 CDT 2012
.211 = Thu Jun 14 13:48:28 CDT 2012
.212 = Tue Jun 19 01:28:00 CDT 2012
.213 = Wed Jun 20 18:20:16 CDT 2012
.215 = Wed Jul 11 20:43:51 CDT 2012
Baseband Versions:
.200 = CDMA_N_05.0E.00R LTEDC_U_09.10.00
.206 = CDMA_N_05.10.00R LTEDC_U_09.11.00
.208 = CDMA_N_05.11.00R LTEDC_U_09.11.00
.211, .212 and .213 = CDMA_N_05.11.01P LTEDC_U_09.11.00
.215 = CDMA_N_05.11.01P LTEDC_U_09.14.00
Build Numbers:
.200 = 6.7.2-180_DR4-16_M2-20
.206 = 6.7.2-180_DR4-16_M2-26
.208 = 6.7.2-180_DR4-16_M2-28
.211 = 6.7.2-180_DR4-16_M2-31
.212 = 6.7.2-180_DR4-16_M2-32
.213 = 6.7.2-180_DR4-16_M2-33
.215 = 6.7.2-180_DR4-16_M2-35
___________________________________________________________________
Useful Links
Instructions to flash 6.16.206 if you are running 6.16.200 (this also should work going from any leak to a newer leak)Get Unstuck from ICS Leak 200 (AKA Upgrading from 200 to 206) INSTRUCTIONS
NOTE: THE INSTRUCTIONS ABOVE ALSO WORK IF GOING FROM 6.16.206 to 6.16.208. YOU HAVE TO FLASH THE KERNEL FROM 6.16.208, and more information is in the thread above and to download the kernel, get the download here. The process from above involved wiping your data.
How to flash the leaks if you are on 6.13.219 (LATEST Gingerbread OTA)
[HOW-TO] Install the leaked Android 4.0.4 ICS build on the Droid 4 (XT894)
Download the 6.16.206 LEAK HERE
DOWNLOAD THE 6.16.208 LEAK HERE
DOWNLOAD THE 6.16.211 LEAK AND KERNEL IN THIS THREAD
DOWNLOAD THE 6.16.212 LEAK AND KERNEL IN THIS THREAD
Note: Yes the two links above to the threads for 211 and 212 Are the same. There are links to 211 and 212 in the same post!
DOWNLOAD THE 6.16.213 LEAK, KERNEL and CRC FILE IN THIS THREAD
Note: This is a different thread from the 211 and 212 thread above. The crc file is available for 213 now as well.
___________________________________________________________________
Again, thanks to CaptainKn0tz for giving me the idea to create the thread for us.
Thanks to tcrews for providing the information for the 6.16.208 and 6.16.211 leak. Also thanks to nullx for the 211 information as well.
Thanks to danifunker for the 212 information.
I found most of this information from my use, if anybody has any more information or any questions please comment below!
Thanks!
--Sam
6.16.208 is available, I will post its information and download link in a few minutes.
Sent from my DROID4 using Tapatalk 2
I know initially people will say no, but i am wondering if there is someway to slip root in here since a few of us have lost it.
I am on 206 and missing my superuser.
we cant disect the package because of the signature stuff, but I am still wondering....
nowell29 said:
I know initially people will say no, but i am wondering if there is someway to slip root in here since a few of us have lost it.
I am on 206 and missing my superuser.
we cant disect the package because of the signature stuff, but I am still wondering....
Click to expand...
Click to collapse
Did you make an su backup using OTA rootkeeper?
yeah, if you look over on droidforums you can see a few of us talking about it. The su backup is outdated and is looking for a function or something called _maketemp but is not found, so the su that it restores cannot execute. If there was someway to inject a newer or unfaulty su binary into this update that would be awesome! but doing so would break the signature and it will not install
ironically it could be done for anything in safestrap, but the catch 22 is that you need root to begin with to have safestrap!
hey, FYI, it failed for me 3 times. I am debating on doing a reset and then trying, but i dont want to start over (again) if I can avoid it
any possibility yet to get root on 206 ics leak?
backuped root from gb an restored in 206 ics leak and backup again with rootkeeper..should work?
Works install 208 directly over 219Gingerbread? And keeps root with ota rootkeeper?
...Tapatalk
How is this new leak .208 working, has anyone had the opportunity to test it?
Sent from my DROID4 using XDA
wheels01 said:
How is this new leak .208 working, has anyone had the opportunity to test it?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
If I could install .208 over .206 I would tell ya how it would run. Ugh.
nowell29 said:
yeah, if you look over on droidforums you can see a few of us talking about it. The su backup is outdated and is looking for a function or something called _maketemp but is not found, so the su that it restores cannot execute. If there was someway to inject a newer or unfaulty su binary into this update that would be awesome! but doing so would break the signature and it will not install
ironically it could be done for anything in safestrap, but the catch 22 is that you need root to begin with to have safestrap!
hey, FYI, it failed for me 3 times. I am debating on doing a reset and then trying, but i dont want to start over (again) if I can avoid it
Click to expand...
Click to collapse
Sounds like you're done.
I could not get 208 to install last night, tried four times. The only thing i havent done yet is wipe, and I think i will hold off on that.
nowell29 said:
I could not get 208 to install last night, tried four times. The only thing i havent done yet is wipe, and I think i will hold off on that.
Click to expand...
Click to collapse
Did you install from internal or external storage?
I thought I had read elsewhere that to install from internal storage you need the .crc file along with the .zip.
I tried fallowing the tutorial from .200 to .206 to get to .208, it did not work at all. I just ended up re flashing .206. I was also only willing to try three times b/c this is the only phone I have so I stopped trying.
I don't think its the tutorial, I'm just too much of a noob
I like the way.206 works, only thing I can't do is add facebook (my gallery) to my accounts, every time I do the gallery app crashes with the error that friendfeed has stopped working.
I'm glad I took the leap to the leak!
Thanks
Sent from my DROID4 using XDA
You'll have to wait until the process is updated with the newer files.
The process fastboots the latest kernel (.206) but the current system (.219) giving you a non-bootable mix up. Since the OTA updates will update the current version (.219) and itself (.206) it works.
The new .208 required files will need to be used to replace what is in the current "recover .200 to .206" procedure.
That way you'll have the .208 kernel and .219 /system and the OTA should update itself (.208) and current official .219.
Can somebody post a link to the latest leak? Link in OP not working.
Here's the info to add to the OP..
System Version:
6.16.208.XT894.Verizon.en.US
Baseband Version:
CDMA_N_05.11.00RLTEDC_U_09.11.00
Webtop Version:
wt-3.0.0
Kernel Version:
3.0.8-gf863077
[email protected] #1
SMP PREEMPT Wed May 30 01:30:01 CDT 2012
Build number:
6.7.2-180_DR4-16_M2-28
Build Date
Wed May 30 01:19:32 CDT 2012
Well if it's because it's looking for 219 and not 206 to upgrade from, why not have find someone who's installed it, and is rooted and can back up their "factory wiped" 208 install, and post it. If we did that, couldn't we just do an advanced restore from safe strap and only restore the system? Or is it because the kernel change from 206 to 208 that it might not work?
I'm rooted on 206, any info that I can provide that would help?
Sent from my DROID4 using XDA
Curiosity, with anyone on 208, do you have better or better signal? I noticed that 206, my 4g signal is now much poorer than with GB. Also my other wonder is if if I use a previous flash(219) if 208 will install.
A new download link for the 6.16.208 leak has been posted. Also have posted a new link for users on 6.16.206 to get to 6.16.208.
I have sold my 7510 to a friend in need of a good tablet...anyone who may still be running this ROM, I'm happy to answer questions but am no longer building for this device.
{
"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"
}
Android Open Kang Project - 4.2.2 - jb-mr1
Hey all, here is a build I compiled of AOKP 4.2.2 for our beloved P7510. It's taken a good chunk of time for me to get this working, I hope you enjoy it as much as I do and I'm happy to be able to bring it to you. This is COMPLETELY UNOFFICIAL, so don't go looking for help on official AOKP threads if your tablet turns into a hot plate!
The ROM is built from a CM device tree (big thanks to pershoot for his work and dedication to our device!) and as such employs a CM 4.2.2 kernel.
I have made no changes whatsoever to this code...this is as pure AOKP as it gets, fresh off their github. None of this ROM is my doing, although I may inject a few goodies of my own as time goes on. All I did was mod pershoot's CM10 device trees as necessary to inherit the right stuff and get the build to compile and work.
For now, I just want to get this thing out to you guys so we can finally have a few OG Tabs bleeding cutting-edge AOKP goodness. Make sure you show love to AOKP and donate to them if you are happy with the ROM!
Not that I should have to clarify, but of course I must also state...
I will not be held responsible for anything that happens to your device if you flash this ROM. You assume all responsibility for modifying and tweaking your tablet/device, and your warranty is instantly voided by doing so. If you come on this thread and yell at me about how your tablet started smoking from the Sammie port after you flashed this ROM, you may get laughed at. (But that won't happen if you read closely, set your expectations accordingly, and follow the instructions.
KNOWN ISSUES
- Any current issues that are known to AOKP - make sure you do your research
- Any of the same issues that are affecting CM10.1 for our device
- The theme chooser may be wonky
INSTALLATION INSTRUCTIONS
- FULL AND COMPLETE WIPE IS A MUST (IMHO)
- Boot into recovery of choice
- Take a backup
- Wipe Cache
- Wipe Dalvik
- Wipe Data/Factory Reset
- Wipe /System (or, in CWM, "format /system" under Mounts and Storage menu)
- Flash ROM
- Flash gapps (see below)
- Reboot, and wait 10 minutes before touching it at ALL
- Reboot and enjoy
- IMPORTANT NOTE: CM10.1 will, in addition to installing the ROM, automatically move the contents of your /sdcard into /sdcard/0 for multiuser purposes. THIS ROM DOESN'T DO THAT RIGHT NOW - the result, it may look like your whole device has been wiped. FEAR NOT, that is not the case. All you need to do is move your stuff into that /0 folder after you flash the ROM. That can be done with a shell command via adb. OR, you can back up all your files to Cloud (Carbon, db, whatever) and bring them back down after, whichever.[/B]
DOWNLOADS AND OTHER LINKS
DOWNLOAD THE ROM HERE.
March 16 Nightly: HERE
March 18 Nightly: HERE
March 20 Nightly: HERE
March 29 Nightly (Build 6!): HERE
MIRROR if Goo is being dumb for any reason. Not currently using Goo OTA - maybe later.
March 16 Mirror: HERE
March 18 Mirror: HERE
March 20 Mirror: HERE
March 29 Mirror: HERE
GAPPS: Check out nakedninja's CM10.1 Discussion Thead here. There is a link to a gapps package for our tabs on this thread that handles the Google Now force closes and AOSP keyboard freezing that the official gapps (03/01) package can introduce.
THANKS GO TO:
- Team Infamous
- AOKP
- CyanogenMod and pershoot, for way more than obvious reasons
- The users! I fight for the users.
Again, ENJOY you guys! Hit up my other stuff here in the GTab forum (GSII is next ) and check out the Infamous ROM INDEX (in my sig below) to see what the rest of Team Infamous is up to these days!
SCREENSHOTS
My setup. I like to keep it simple
More to be added later on
CHANGE LOG
Code:
3/29/2013
Just updated to Build 6 Mar 29 latest. Nothing fancy other than new AOKP goodies :)
3/22/2013
- Updated code to Mar 20
- Added Team Infamous boot animation
3/20/2013
- Updated code to Mar 18 - everything that comes with it per AOKP gerrit should be there
- Still working on that /0 issue so that hasn't changed yet...if you're already on my build a dirty flash should be fine
- Added build.prop tweaks for WiFi buffer, better sleep, and improved scroll response
3/17/2013
- Initial Release. AOKP source current a/o 3/16.
Downloading and testing...
[noob][Q] bootloader question
I have seen some 4.2.x threads stating something about the need to have 'ics bootloader' in order to properly install the ROM.
Is this also required here? For example, I am currently using the previous AOKP 4.1.2 ROM, and I'm clueless on how to verify what's my bootloader version. Do I need to flash some bootloader or just go ahead following OP instructions?
Another noobishQ: any expected problems if using TWRP instead of CWM?
Cheers for continuing with this ROM branch!
Sent from my GT-I9300 using Tapatalk 2
Glad to see this ROM.
Nice! Awesome job bro.
Thanks for this will install later ..........:good:
Great to see you got this far with this very interesting project!
Re: [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 5 :: MR1 :: Mar 16
Way to go man!! Thanks for taking over! :thumbup:
Ill b flashing this as soon as my life/wife lets me play again. Once this baby girl comes out, maybe u and I can collaborate on a rom. Let me know what u think. :beer:
Sent from my Motorola Electrify using xda app-developers app
Re: [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 5 :: MR1 :: Mar 16
jaibar said:
I have seen some 4.2.x threads stating something about the need to have 'ics bootloader' in order to properly install the ROM.
Is this also required here? For example, I am currently using the previous AOKP 4.1.2 ROM, and I'm clueless on how to verify what's my bootloader version. Do I need to flash some bootloader or just go ahead following OP instructions?
Another noobishQ: any expected problems if using TWRP instead of CWM?
Cheers for continuing with this ROM branch!
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
If you're already on 4.1.2 and have no issues with a rolling ROM or recovery screen you shouldn't need a bootloader flash.
TWRP is actually recommended. I swear by TWRP myself.
Make sure you don't forget about Tue multiuser piece and moving your files by hand too!! I know that's a nuisance and I hate it so I'll be figuring out a way around that plus rolling up the codebase in the next build.
Sent from my 4.2.GSII
Re: [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 5 :: MR1 :: Mar 16
triptosyll said:
Way to go man!! Thanks for taking over! :thumbup:
Ill b flashing this as soon as my life/wife lets me play again. Once this baby girl comes out, maybe u and I can collaborate on a rom. Let me know what u think. :beer:
Sent from my Motorola Electrify using xda app-developers app
Click to expand...
Click to collapse
Right on man, for sure!!
Yeah really wanted to get this out so ppl could have a chance to see 4.2.2 AOKP on the Tab. Once I have the multiuser piece done out it'll be sweet. I may also throw together a quick script to move files back when you revert to a non 4.2.2 ROM
Sent from my 4.2.GSII
Oh haha, finally the OG Tab got some AOKP's 4.2.2 love! Thx!
P4 user here ready to be a tester
Any plans on trying to get SCH-I905 working? I would be happy to be a tester if needed!
Re: [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 5 :: MR1 :: Mar 16 Nightly
jittusm said:
P4 user here ready to be a tester
Click to expand...
Click to collapse
Here's the thing lol...
I can build for the 7500 but don't own the device. If I do that in the coming days and it doesn't fly my ability to support is extremely limited. I can only test and release confidently for the WiFi tab. That said if you are willing to take the plunge I will definitely try.
Sent from my 4.2.GSII
djmatt604 said:
Here's the thing lol...
I can build for the 7500 but don't own the device. If I do that in the coming days and it doesn't fly my ability to support is extremely limited. I can only test and release confidently for the WiFi tab. That said if you are willing to take the plunge I will definitely try.
Sent from my 4.2.GSII
Click to expand...
Click to collapse
I am definitely willing to try cos aokp features are far more than the existing roms. just compile and throw it our way. there are a lot of crazy folk here ready to test it out. Thanks in advance )
I am currently on the latest CM10.1 nightly, how does that affect the files that need to be moved?
Re: [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 5 :: MR1 :: Mar 16 Nightly
Dreameagl said:
I am currently on the latest CM10.1 nightly, how does that affect the files that need to be moved?
Click to expand...
Click to collapse
I don't believe it would be a problem in that case as your files should already be in the right place. Give it a go and let me know!
Sent from my 4.2.GSII
Running great. I installed it last night and I must say, this thing is fantastic. The battery life is great as well. Thanks man.
Notice - The download link is dead.
Notice - This ROM is not for daily use. I'm sharing this because of share requests.
Keylimepie is an un-offical codename of Android Kitkat.
This ROM comes with some develoment-purpose applications from LG and Qualcomm.
Also, the Android SDK version is same as Android 4.3 Jellybean.
Special thanks to phone owner The Cherry(mycoin7) from Develoid
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MP
ro.build.display.id=aosp_hammerhead-userdebug KeyLimePie MP PDK799752 test-keys
ro.build.version.incremental=PDK799752
ro.build.version.sdk=18
ro.build.version.codename=KeyLimePie
ro.build.version.release=KeyLimePie
ro.build.date=Sat Sep 28 16:25:31 KST 2013
ro.build.date.utc=1380353131
ro.build.type=userdebug
ro.build.user=sangjoon84.lee
ro.build.host=buildgb2
ro.build.tags=test-keys
ro.product.model=AOSP on HammerHead
ro.product.brand=Android
ro.product.name=aosp_hammerhead
ro.product.device=hammerhead
ro.product.board=hammerhead
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=hammerhead
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=aosp_hammerhead-userdebug KeyLimePie MP PDK799752 test-keys
ro.build.fingerprint=Android/aosp_hammerhead/hammerhead:KeyLimePie/MP/PDK799752:userdebug/test-keys
ro.build.characteristics=nosdcard
# end build properties
Downloading and flashing this ROM is at YOUR OWN RISK!
This ROM contains system, boot and modem partition dumps from engineer verison of Nexus 5.
Flash the file I uplodaed with custom-recovery such as CWM, TWRP, then do a factory-reset (wipe data and cache partiton).
Screenshots
Download from MEGA - !DISCONTINUED!
* Known issues
Google service related apps randomly force-close.
Wallpaper rendering(?) is buggy
Android system force closes when you activate Android easter-egg.
Switch animation(s) between windows don't work.
Awesome!
This seems pretty interesting, but I can't really see the difference between this and normal KitKat?
Can someone help here lol?
What is your Android version and build number after you install this?
---------- Post added at 09:56 AM ---------- Previous post was at 09:55 AM ----------
HMZX said:
This seems pretty interesting, but I can't really see the difference between this and normal KitKat?
Can someone help here lol?
Click to expand...
Click to collapse
Did you install this or is that a general observation like what I'm seeing?
habitformer said:
What is your Android version and build number after you install this?
Click to expand...
Click to collapse
As you can see it in sceenshot, it says AOSP on hammerhead on Android version and aosp_hammerhead-userdebug KeyLimePie MP PDK799752 test-keys on build number.
Is this just a zipped up stock system dump of KLP?
orangekid said:
Is this just a zipped up stock system dump of KLP?
Click to expand...
Click to collapse
Nope. I already said that this can be flashed with custom-recovery like CWM.
YB EDISON said:
As you can see it in sceenshot, it says AOSP on hammerhead on Android version and aosp_hammerhead-userdebug KeyLimePie MP PDK799752 test-keys on build number.
Click to expand...
Click to collapse
I misread.Sorry.How long have you used this,what would you like to do with this,you went help making it fully functioning?let me know
---------- Post added at 10:09 AM ---------- Previous post was at 10:05 AM ----------
ro.build.date=Sat Sep 28 16:25:31 KST 2013
Could this be old?
@D.D.P.
Deleted. I swear this is old and just a test build for bugs/fixes before the initial kit kat was released with N5.
It's the test build that was on our phones before it does the automatic KK update when you first turned it on back in November system dump put in flashable zip. It's a 7 month old test build.
What kind of test applications are included on this build? Cannot download right now to check myself.
Sent from my Nexus 5 using Tapatalk
It seems to me that this would be for the completist... someone who needs to collect EVERYTHING related to Kitkat.
Sent from my Nexus 5 using Tapatalk
kufikugel said:
What kind of test applications are included on this build? Cannot download right now to check myself.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
1, Folder test
2. Hidden menu(LGE)
3. QSensor test
4. QXDM Logger Utility
YB EDISON said:
1, Folder test
2. Hidden menu(LGE)
3. QSensor test
4. QXDM Logger Utility
Click to expand...
Click to collapse
Thanks well 3 and 4 are available over qcom officially. Other both no idea. Whatever will download and test it. Thanks for sharing!!
Sent from my Nexus 5 using Tapatalk
(Trouble Maker)
Let's stay ON TOPIC SIR!
I was going to ask if you wanted to tear this apart and build it.I looked at it more firmly and it is old and like I stated posts ago it is a maintenance/bug/test build.So I deleted my idea.I'm going to wait till 4.4.3 to make more personal builds
This is not working.The list of things that doesn't work is very long k. Comparison to what is.This isn't current Android.To work on this is waste of time.
OK, I'll stay on topic. I messed with the script, nothing out of the norm. *EDITS*
saqib nazm said:
Thread has been cleaned up again, guys stay on topic, If you don't feel this thread to be something useful don't reply.
Click to expand...
Click to collapse
This isn't keylime pie.Heck this isn't 4.4.2.Look at the meta.Scratch that look at the screen shots.
Sim card not working & no work data
Adb is wonky
Battery port not enabled
(Can't remember either old Samsung or lg splash/boot.ani screen
Ui is J.B ALL of it.
The android version has been edited
Kernel is built by lord knows who
This should be shut down it isn't not any leak of the future, more like a lg g2 test build that works partially with n5 hammerhead.
D.D.P. said:
OK, I'll stay on topic. The topic should be closed until a real release of 4.4.3 is out. These threads cause a lot of tension. Just refer to the other 4.4.3 threads.
Click to expand...
Click to collapse
habitformer said:
This isn't keylime pie.Heck this isn't 4.4.2.Look at the meta.Scratch that look at the screen shots.
Sim card not working & no work data
Adb is wonky
Battery port not enabled
(Can't remember either old Samsung or lg splash/boot.ani screen
Ui is J.B ALL of it.
The android version has been edited
Kernel is built by lord knows who
This should be shut down it isn't not any leak of the future, more like a lg g2 test build that works partially with n5 hammerhead.
Click to expand...
Click to collapse
I really do not say that often but both of you just should stop posting about stuff you have no idea what it is or just OT for the sake off like yesterday.
Reading the 4 first sentence of this thread says clearly that it is a pre KitKat release leak (and everyone who knows the story of key lime pie knows it already from the title). Nothing from the future it was from the past. Interesting? Yes due that it has some not official developer stuff included.
Sent from my Nexus 5 using Tapatalk
Interesting.
I will play around with this and see what I can do with the test apps.
I tested it out. Interesting leak. thank you OP.
Be careful when you flash it,because it changes the misc partition. Device factory version and device factory out version becomes LGD821AT-00-V10a-NXS-XX-OCT-03-2013-KRS59B-FACTORY-16G+0 (on D820 it becomes LGD820AT-00-V10a-NXS-XX-OCT-03-2013-KRS59B-FACTORY-16G+0) which prevents you flashing factory images with lg flashtool.
Maybe flashing stock rom from google sets back the device factory version to "USER" type then you can use lg flashtool without no problem, but if that does not happen then you have to manually change device factory version to "USER".
these infos stored at on misc partition
device factory version is at 0x00008800 offset and device factory out version is at 0x00009000 offset
for me device factory version is LGD821AT-00-V10b-NXS-XX-OCT-31-2013-KRT16M-USER-16G+0 and device factory out version is LGD821AT-00-V10g-NXS-XX-NOV-14-2013-KRT01B-FACTORY-XXG+0
My phone from that batch which does not required teh 150 MB big ota update at the first start. These infos may be different depending on when was the phone manufactured
habitformer said:
@kufikugel Since I respect open forums and the debate they bring as well as opinions I hear what you are saying.Every once in while I like to stir things up and get off topic. I admit that.Now I respect the work you contribute to for slim so I'll politely bow out but request your attention via Private Message to further continue this.Thank you I'll see you shortly.
---------- Post added at 05:57 PM ---------- Previous post was at 05:54 PM ----------
@bitdomo what did the UI look and feel like?Do you remember the kernel version,did you notice being able to charge at all?
Click to expand...
Click to collapse
Wallpaper rendering is glitching, old jb icons everywhere. The phone is charging, kernel version is the same like on the screenshots. The system and boot images are from the V10a-NXS-XX-OCT-03-2013-KRS59B-FACTORY rom. The modem version is the same as the modem in KQS81M stock rom.
Flashing stock rom from google does not solve the misc problem, you have to edit your misc manually if you want to use LG flashtool in the future.
Screenshots:
{
"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"
}
Pretty simple, title explains it pretty well. I'm thinking the pie update is coming soon and I'm wondering if I'm going to have issues getting it. I feel like I did something to change it but can't remember what I did. Any help?
{
"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"
}
Sent from my SM-N950U using Tapatalk
OMG_VTEC said:
Pretty simple, title explains it pretty well. I'm thinking the pie update is coming soon and I'm wondering if I'm going to have issues getting it. I feel like I did something to change it but can't remember what I did. Any help? View attachment 4727400
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
You can tell what version of Android it is just by the build number. You can also tell if each update just contains the updated security patch, or if new features were added or updated.
The first part of the build number never changes. It will start with your model number (N950U or N950U1) followed by a region code for your model number (UE for US unlocked or SQ for US carrier models). After that, there is a 5 character build number that changes with each version.
The first character (S or U) tells you if it's a security patch or a feature update. S = Security Patch and U = Feature Update (features added or changed)
The second character (a number) tells you bootloader version. This is important to know when upgrading and downgrading OS versions. You can NOT downgrade the bootloader. 1 = Bootloader V1, 2 = Bootloader v2, etc...
The third character tells you the Android version. This is different for each Galaxy device. A is the Android version that device was released with. (For the Note 8 A=Nougat; B=Nougat with updated bootloader/carrier switching; C=Oreo, D=Pie) Z is for official Samsung BETA program builds.
The fourth character is the year of the build (R=2018, S=2019). This is the same across all Galaxy devices.
The fifth character is the month of the build. This does not indicate what security patch it contains, only what month it was built. (A=January, B=February). Again, same across all Galaxy Devices.
The sixth character is just the sequence of builds that month (1-9, then A-Z)
So, official Oreo build S5CRG9 is:
S - Security Patch
5 - Bootloader V5
C - Oreo
R - 2018
G - July build
9 - 9th build in July
and leaked Pie build U5DRL7 is:
U - Feature update
5 - Bootloader V5
D - Pie
R - 2018
L - December build
7 - 7th build in December
and official Pie beta build U5ZSAB is:
U - Feature update
5 - Bootloader v5
Z - Official Samsung BETA program build
S - 2019
A - January build
B - 11th build in January
So let's break down my current build number, N950U1UEU1ZSAB
N950U1 - Build is for the Factory unlocked U1 model
UE - Region code US Unlocked
U - Feature update
5 - Bootloader v5
Z - Official Samsung BETA program build
S - 2019
A - January build
B - 11th build in January
Always make sure you know what bootloader version comes with each build before you flash it. This is especially important with the leaked builds. If you flash a leaked Pie build, and it is already updated to bootloader V6, you will be stuck there, which will really suck if its a buggy build.
As of right now, if you update to either the leaked Pie builds, or the official beta build, you can easily downgrade back to Oreo using patched ODIN. Just repeat the steps in the OP. But once Samsung updates the bootloader to V6, most likely after the official release of Pie, you won't be able to downgrade.
Mr. Orange 645 said:
You can tell what version of Android it is just by the build number. You can also tell if each update just contains the updated security patch, or if new features were added or updated.
The first part of the build number never changes. It will start with your model number (N950U or N950U1) followed by a region code for your model number (UE for US unlocked or SQ for US carrier models). After that, there is a 5 character build number that changes with each version.
The first character (S or U) tells you if it's a security patch or a feature update. S = Security Patch and U = Feature Update (features added or changed)
The second character (a number) tells you bootloader version. This is important to know when upgrading and downgrading OS versions. You can NOT downgrade the bootloader. 1 = Bootloader V1, 2 = Bootloader v2, etc...
The third character tells you the Android version. This is different for each Galaxy device. A is the Android version that device was released with. (For the Note 8 A=Nougat; B=Nougat with updated bootloader/carrier switching; C=Oreo, D=Pie) Z is for official Samsung BETA program builds.
The fourth character is the year of the build (R=2018, S=2019). This is the same across all Galaxy devices.
The fifth character is the month of the build. This does not indicate what security patch it contains, only what month it was built. (A=January, B=February). Again, same across all Galaxy Devices.
The sixth character is just the sequence of builds that month (1-9, then A-Z)
So, official Oreo build S5CRG9 is:
S - Security Patch
5 - Bootloader V5
C - Oreo
R - 2018
G - July build
9 - 9th build in July
and leaked Pie build U5DRL7 is:
U - Feature update
5 - Bootloader V5
D - Pie
R - 2018
L - December build
7 - 7th build in December
and official Pie beta build U5ZSAB is:
U - Feature update
5 - Bootloader v5
Z - Official Samsung BETA program build
S - 2019
A - January build
B - 11th build in January
So let's break down my current build number, N950U1UEU1ZSAB
N950U1 - Build is for the Factory unlocked U1 model
UE - Region code US Unlocked
U - Feature update
5 - Bootloader v5
Z - Official Samsung BETA program build
S - 2019
A - January build
B - 11th build in January
Always make sure you know what bootloader version comes with each build before you flash it. This is especially important with the leaked builds. If you flash a leaked Pie build, and it is already updated to bootloader V6, you will be stuck there, which will really suck if its a buggy build.
As of right now, if you update to either the leaked Pie builds, or the official beta build, you can easily downgrade back to Oreo using patched ODIN. Just repeat the steps in the OP. But once Samsung updates the bootloader to V6, most likely after the official release of Pie, you won't be able to downgrade.
Click to expand...
Click to collapse
I'm wanting to get to pie but don't know if I should wait for the official or just figure out how to get a leak. I just don't know what I flashed or if what I did is still an issue. I'm assuming I have a debloated build and don't know if I will get an Ota update
Sent from my SM-N950U using Tapatalk
OMG_VTEC said:
I'm wanting to get to pie but don't know if I should wait for the official or just figure out how to get a leak. I just don't know what I flashed or if what I did is still an issue. I'm assuming I have a debloated build and don't know if I will get an Ota update
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-8/how-to/snapdragon-official-note-8-n950u1-t3893612
I recently purchased this phone for $20 on ebay. It's in pristine condition, not a scratch on it. My reasoning for purchashing it is I wanted an older phone that was easily rootable for music and other stuff. Finally got linage OS installed on it, and I am very impressed. I was worried about the battery but it seems fine. Thinking about getting an sim card adapter and trying it out as my daily. It's a breathe of fresh air compared to the unrootable bloat-infested carrier-branded phone I am currently using.
st1ll1n1t said:
I recently purchased this phone for $20 on ebay. It's in pristine condition, not a scratch on it. My reasoning for purchashing it is I wanted an older phone that was easily rootable for music and other stuff. Finally got linage OS installed on it, and I am very impressed. I was worried about the battery but it seems fine. Thinking about getting an sim card adapter and trying it out as my daily. It's a breathe of fresh air compared to the unrootable bloat-infested carrier-branded phone I am currently using.
Click to expand...
Click to collapse
As of Jan 1 2021 AT&T requires VoLTE enabled phones. This phone never had VoLTE so your sim would be deactivated by AT&T. You could try a sim from another carrier but Verizon would probably not activate either. I'm not sure about Sprint (T-Mobil). I use this phone as a learning tool for building roms.
Wheels564 said:
As of Jan 1 2021 AT&T requires VoLTE enabled phones. This phone never had VoLTE so your sim would be deactivated by AT&T. You could try a sim from another carrier but Verizon would probably not activate either. I'm not sure about Sprint (T-Mobil). I use this phone as a learning tool for building roms.
Click to expand...
Click to collapse
Ahh that's a shame. They will always find a way to force us to upgrade won't they? Guess I will have to find a newer phone that is compatible with lineage because I cannot go back to dealing with stock. I'll keep this little guy as a media device.
st1ll1n1t said:
Ahh that's a shame. They will always find a way to force us to upgrade won't they? Guess I will have to find a newer phone that is compatible with lineage because I cannot go back to dealing with stock. I'll keep this little guy as a media device.
Click to expand...
Click to collapse
Isn't it true that Atrix HD won't work in USA on AT&T network with VoLTE? I am from Canada and mine works ok here... I use custom rom (updated Android 7.1) and no issues in Canada. Any other US network can do?
st1ll1n1t said:
I recently purchased this phone for $20 on ebay. It's in pristine condition, not a scratch on it. My reasoning for purchashing it is I wanted an older phone that was easily rootable for music and other stuff. Finally got linage OS installed on it, and I am very impressed. I was worried about the battery but it seems fine. Thinking about getting an sim card adapter and trying it out as my daily. It's a breathe of fresh air compared to the unrootable bloat-infested carrier-branded phone I am currently using.
Click to expand...
Click to collapse
I use it as a car dash cam: its pretty good. Ebay had even the nice car mounts on sale for these Atrix HDs
dust_off said:
Isn't it true that Atrix HD won't work in USA on AT&T network with VoLTE? I am from Canada and mine works ok here... I use custom rom (updated Android 7.1) and no issues in Canada. Any other US network can do?
Click to expand...
Click to collapse
According to Kb8no over on the Moto X Pure thread if you do not hve VoLTE AT&T will disable you sim and you have to call them to enable it again.
BTW I successfully compiled CRDroid the the AtrixHD. If anyone is interested I will start a new thread and upload it.
Wheels564 said:
According to Kb8no over on the Moto X Pure thread if you do not hve VoLTE AT&T will disable you sim and you have to call them to enable it again.
BTW I successfully compiled CRDroid the the AtrixHD. If anyone is interested I will start a new thread and upload it.
Click to expand...
Click to collapse
Yes that will be great thank you! BTW, I have few older ROMS for Atrix HD on my computer - CyanogenMod Android 5.1.1, Bliss roms Android 6.0.1 and Chinese rom (Suda Mod) android 6.0.1 that were started by someone but not continued.. They aren't that stable (most stable is Android 5.1.1) but less and less apps compatible with Lollipop now. Where can I upload them?
dust_off said:
Yes that will be great thank you! BTW, I have few older ROMS for Atrix HD on my computer - CyanogenMod Android 5.1.1, Bliss roms Android 6.0.1 and Chinese rom (Suda Mod) android 6.0.1 that were started by someone but not continued.. They aren't that stable (most stable is Android 5.1.1) but less and less apps compatible with Lollipop now. Where can I upload them?
Click to expand...
Click to collapse
This CRDroid is based on Lineage14.1 and has many but not all of the new secuurity updated included. It's still dated 2018 because CRDroid stopped including the patches in their source code. Once I figure out how to merge the patches it will be totally up to date. It runs smooth without gapps and is pre rooted.
{
"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"
}
Wheels564 said:
This CRDroid is based on Lineage14.1 and has many but not all of the new secuurity updated included. It's still dated 2018 because CRDroid stopped including the patches in their source code. Once I figure out how to merge the patches it will be totally up to date. It runs smooth without gapps and is pre rooted.View attachment 5258793Hi Wheels564, how are you? Did you make that ROM-CRDROID for Moto Atrix HD? Thanks
Click to expand...
Click to collapse
I'll upload it when I get a chance for you to try.
Edit: Since it's a new rom I have to make a new Thread dedicated to the rom with all the information.
Edit no. 2: I'll build a new one with April updates and send you a personal link until I get the thread up.
Oh awesome, I just picked up a few off ebay because they aren't very expensive and I was going to use them more for projects instead of using more as a phone.
Wheels564 said:
This CRDroid is based on Lineage14.1 and has many but not all of the new secuurity updated included. It's still dated 2018 because CRDroid stopped including the patches in their source code. Once I figure out how to merge the patches it will be totally up to date. It runs smooth without gapps and is pre rooted.View attachment 5258793
Click to expand...
Click to collapse
How can i get the zip?
江南影客 said:
How can i get the zip?
Click to expand...
Click to collapse
[ROM] crDroid Android 3.8.9 Unnoficial (Nougat)
[RPM] crDroid Android for the Atrix HD * I am not responsible for bricked devices, loss of data, dead SD cards, You must format your Data partition as F2FS. I personally run my cache as f2fs as well, don't know if thats a requirement crDroid...
forum.xda-developers.com
Wheels564 said:
[ROM] crDroid Android 3.8.9 Unnoficial (Nougat)
[RPM] crDroid Android for the Atrix HD * I am not responsible for bricked devices, loss of data, dead SD cards, You must format your Data partition as F2FS. I personally run my cache as f2fs as well, don't know if thats a requirement crDroid...
forum.xda-developers.com
Click to expand...
Click to collapse
TKS