Related
Model: GT-I9000 | Code: TEN | Version: I9000XWJPA/I9000TENJP3/I9000XXJPP | Date: 30.10.2010 17:35 | Size: 184,83 MB
http://fus.samsungmobile.com/Phone_...00TENJP3_I9000XXJPP_I9000XWJPA_XW_TEN.zip.enc
is a new thread rly needed? but anyways, theres a second one.
Model: GT-I9000 | Code: NEE | Version: I9000XWJPA/I9000NEEJP4/I9000XXJPP | Date: 30.10.2010 17:14 | Size: 184,83 MB | ID: 3860414066
http://fus.samsungmobile.com/Phone_...00NEEJP4_I9000XXJPP_I9000XWJPA_XW_NEE.zip.enc
TEN...as in Norway?
So are these actually newer and better than the ones with Oct 25 and Oct 26 build dates, or are they basically the same thing? If they are newer/better, that's got to be a record between releases on Samsung!
how do we know?
I trust the chefs like DocRambone to figure out these builds and base their magic off of the best ones available. It sure is like a leaky faucet with all this stuff coming out.
Overall the quality of these Froyo builds has improved a lot, with the browser actually usable now. Still, compared to the perfect clean Froyo on the Nexus One, it's still a sad story. Hopefully CyanogenMod will come and save the day at some point.
I think at this point RAM management/availability and sporadic GPS are the worst issues right now, with browsing having been mediated. Hopefully CM will eventually fix the aformentioned.
For now, we are fortunate to have this new stuff coming out all the time.
-----Waiting for someone to try it out share their insigts =P -----
How do I root this version? there are so many ways to root but i don't find the right one because i can't use update.zip files. When I install this rom it as recovery 3e and it doesn't allow me to use update.zip files.
help please
nCoder said:
Model: GT-I9000 | Code: TEN | Version: I9000XWJPA/I9000TENJP3/I9000XXJPP | Date: 30.10.2010 17:35 | Size: 184,83 MB
http://fus.samsungmobile.com/Phone_...00TENJP3_I9000XXJPP_I9000XWJPA_XW_TEN.zip.enc
Click to expand...
Click to collapse
build date 2010.10.26 11:06:57 KST, release keys
http://www.multiupload.com/TIQP14WVBK
Pjuuder said:
is a new thread rly needed? but anyways, theres a second one.
Model: GT-I9000 | Code: NEE | Version: I9000XWJPA/I9000NEEJP4/I9000XXJPP | Date: 30.10.2010 17:14 | Size: 184,83 MB | ID: 3860414066
http://fus.samsungmobile.com/Phone_...00NEEJP4_I9000XXJPP_I9000XWJPA_XW_NEE.zip.enc
Click to expand...
Click to collapse
build date 2010.10.26 11:06:57 KST, release keys
http://www.multiupload.com/BN9T4TIZ1G
(yes build date and time are exactly the same)
so just different CSC?
So these are from Oct 26 not Oct 30?
Are they basically same as the other couple builds that we just had come out?
That is quite likely, yes.
Since these have the same PDA and Phone codes (XWJPA and XXJPP) as the XEE rom released my guess is that these are just regionalized versions of high packages.
The United Kingdom XEU and CPW have a different PDA code though (XXJPO), might be more differences there.
Now available for many regions. Directly from the source. Enjoy.
Edit: link added.. sorry I forgot.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
MZ600 - XOOM with Wi-Fi + Verizon 3G
Build Size Date Posted Documents Action
Build HRI39 117 MB N/A MZ600 Product Specs Download
Build HRI66 121 MB N/A MZ600 Product Specs Download
MZ601 - XOOM with Wi-Fi + UMTS
Build Size Date Posted Documents Action
Build H.6.1-38-1 for Retail Europe 118 MB Jun. 2, 2011 MZ601 Product Specs Download
Build H.6.1-38-1 for Retail France 118 MB Jun. 2, 2011 MZ601 Product Specs Download
Build H.6.1-38-9 for Retail Other International 118 MB Jun. 2, 2011 MZ601 Product Specs Download
Build H.6.1-38-11 for Retail Turkey 117 MB Jun. 2, 2011 MZ601 Product Specs Download
Build H.6.1-38-5 for T-Mobile Germany 115 MB Jun. 2, 2011 MZ601 Product Specs Download
Build H.6.1-38-9 for Telstra Australia 121 MB Jun. 2, 2011 MZ601 Product Specs Download
Build H.6.1-37-1 for Korea SKT 128 MB Jun. 1, 2011 MZ601 Product Specs Download
MZ604 - XOOM with Wi-Fi
Build Size Date Posted Documents Action
Build H.6.2-20 for KDDI Japan 125 MB Jun. 2, 2011 MZ604 Product Specs Download
Build H.6.2-24 for Retail France 118 MB Jun. 2, 2011 MZ604 Product Specs Download
Build H.6.2-24 for Retail Europe 118 MB Jun. 2, 2011 MZ604 Product Specs Download
Build H.6.2-24 for Retail Other International 118 MB Jun. 2, 2011 MZ604 Product Specs Download
Build H.6.2-21 for Canada 119 MB Jun. 1, 2011 MZ604 Product Specs Download
Build H.6.2-21 for Brazil 119 MB Jun. 1, 2011 MZ604 Product Specs Download
Build H.6.2-21 for Spanish-speaking countries in Latin America 125 MB Jun. 1, 2011 MZ604 Product Specs Download
Build HWI69 for US Retail 122 MB N/A MZ604 Product Specs Download
MZ605 - XOOM with Wi-Fi + UMTS
Build Size Date Posted Documents Action
Build H.6.1-38.4 for Spanish-speaking countries in Latin America 125 MB Jun. 2, 2011 MZ605 Product Specs Download
Build H.6.1-38.4 for Brazil 125 MB Jun. 1, 2011 MZ605 Product Specs Download
MZ606 - XOOM with Wi-Fi
Build Size Date Posted Documents Action
Build H.6.2-9_CN-18 for China Retail 141 MB Jun. 1, 2011 MZ606 Product Specs Download
Can you post link here?
And no 3.1 firmware?
keunhuvac said:
Can you post link here?
And no 3.1 firmware?
Click to expand...
Click to collapse
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
Enjoy
awsome now we can flash back to eu when/if needed
H-6.1-38-4 is that 3.1?
Sent from my GT-I9000 using XDA App
Link added, and no 3.1. But you can always upgrade on the official way using these images, assumed 3.1 is available via OTA yet. The main purpose of these images is helping people with semi bricks and/or those who have flashed firmwares from other regions.
keunhuvac said:
Can you post link here?
And no 3.1 firmware?
Click to expand...
Click to collapse
3.1 would be 6.3-XX and I doubt they will ever be made available there. The sole purpose of these images is to recover XOOMs, not to distribute updates.
sqx said:
H-6.1-38-4 is that 3.1?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
How would you know if oyu where semi bricked with no way back? I ask cause I think I may be semi bricked. I'm stuck in the boot loop, and, I'm stuck in the 'starting fastboot protocol....' after trying rebooting with adb fastbootloader.
What would be the command to use these with adb?
Thanks.
You need to use fastboot to flash these images. If you've installed the android sdk then the fastboot tool should have been included with it (It's a command line tool)
Once you've located fastboot (it's in TOOLS inside the android sdk directory.) Follow the instructions posted on the site
The commands to flash and re-lock your device are as follows:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If I can still boot into CWR, does that mean I may still be semi bricked? I managed to flash BRD's boot and tiamat off his thread, and it worked well, until reboot. I'm still stuck in this boot loop, and it's making me loopy!
This whole thing happened because I stuffed with the build.prop file in the system folder and downloaded market enabler.
Can you relock a wifi only xoom?
It's about bloody time! Thanks for the update!
maybe a stupid question.
i got my xoom from amazon with the t-mobile rom (altough there is no visual branding). does the xoom have something like CID or CSC or would "unbranding" just be that simple than flashing the stock eu image?
If you check my sticky, link is in signature I have already put all these up without logins.
Sent From My Evo
**** thaaaat, where is 3.1 ?
I can't seem to connect to the PC now, go figure. I want to try and just restore to factory, is this possible without my PC recognising my Xoom via USB now? Is there a way to flash the official Moto images if I can't connect my usb to my PC? I can force a reboot via adb, but that's it.
Is there any possibility to have the SBFs?
Ifiuse said:
Is there any possibility to have the SBFs?
Click to expand...
Click to collapse
Sent From My Evo
bwcorvus said:
Tomorrow...
Sent From My Evo
Click to expand...
Click to collapse
Really?
10 characters....
Ifiuse said:
Really?
10 characters....
Click to expand...
Click to collapse
Lol...
etc etc
Sent from my HTC Desire using Tapatalk
Hai people, I'm here because I have my Galaxy Gio with CyanogenMod 10.1 and I want to install themes. When I install a theme, it goes well, but when I apply, it displays the following: "This theme was improperly incompiled and can't be applied. Please report this incident to the theme's author." What am I doing wrong?!
Phone Specs:
Model: GT-S5660
Android Version: 4.2.1 Jelly Bean
BaseBand Version: S5660XXKT6
Kernel Version: [email protected]#1 Sun Jan 6 10:38:58 PST 2013
CPU: ARMv6-compatible processor rev 5 (v6l)
RAM: 276Mb
CyanogenMod Version: 10.1-20130106-UNOFFICIAL-gio
Compilation Date: Sun Jan 6 09:57:45 PST 2013
Compilation Number: cm_gio-userdebug 4.2.1 JOP40D eng.olddroid.20130106.095610 test-keys
Rooted: Yes
ClockWorkMod Recovery: Yes
Any info you need I'll present
MetroxGamer said:
Hai people, I'm here because I have my Galaxy Gio with CyanogenMod 10.1 and I want to install themes. When I install a theme, it goes well, but when I apply, it displays the following: "This theme was improperly incompiled and can't be applied. Please report this incident to the theme's author." What am I doing wrong?!
Phone Specs:
Model: GT-S5660
Android Version: 4.2.1 Jelly Bean
BaseBand Version: S5660XXKT6
Kernel Version: [email protected]#1 Sun Jan 6 10:38:58 PST 2013
CPU: ARMv6-compatible processor rev 5 (v6l)
RAM: 276Mb
CyanogenMod Version: 10.1-20130106-UNOFFICIAL-gio
Compilation Date: Sun Jan 6 09:57:45 PST 2013
Compilation Number: cm_gio-userdebug 4.2.1 JOP40D eng.olddroid.20130106.095610 test-keys
Rooted: Yes
ClockWorkMod Recovery: Yes
Any info you need I'll present
Click to expand...
Click to collapse
Go in your build.prop and search for something like screen.dpi or whatever anyway it should be 160 from the start change it to something like 140 and reboot then apply the theme
Desmaize38 said:
Go in your build.prop and search for something like screen.dpi or whatever anyway it should be 160 from the start change it to something like 140 and reboot then apply the theme
Click to expand...
Click to collapse
I have HVGA, do I really need to do that?? (I have no problems in that but just asking)
BTW where can I find that?
~180ppi Pixel Density
MetroxGamer said:
I have HVGA, do I really need to do that?? (I have no problems in that but just asking)
BTW where can I find that?
~180ppi Pixel Density
Click to expand...
Click to collapse
Do you know how to use root explorer? If not then:
Download root browser lite and go to the root folder (contains system, sys, sbin and some other silly folders).
Go in system and at ther botton there should be a file named build.prop, open it with a text editor. Then start looking for a line like this "ro.sf.lcd_density=160" change the 160 to 140 save && reboot. after you can apply your theme. If you dont like the layout you can always change back to 160 and your theme should be still applied.
Desmaize38 said:
Do you know how to use root explorer? If not then:
Download root browser lite and go to the root folder (contains system, sys, sbin and some other silly folders).
Go in system and at ther botton there should be a file named build.prop, open it with a text editor. Then start looking for a line like this "ro.sf.lcd_density=160" change the 160 to 140 save && reboot. after you can apply your theme. If you dont like the layout you can always change back to 160 and your theme should be still applied.
Click to expand...
Click to collapse
I changed it to 140, applied and rebooted; BlackScreen.... Had to reinstall CM10.1 :s
MetroxGamer said:
I changed it to 140, applied and rebooted; BlackScreen.... Had to reinstall CM10.1 :s
Click to expand...
Click to collapse
That's weird.. which CM 10.1 version do you use? (I'll check it myself)
Desmaize38 said:
That's weird.. which CM 10.1 version do you use? (I'll check it myself)
Click to expand...
Click to collapse
Yeah, if you could solve this I would be very appreciated
Important Notice:
The original poster and creator of this thread is JustSueMe. His original work was one of the main contributors for me to work on this topic.
As proof of the above, his original message is kept in this main post, just below - and the people thanking this thread are there due to his efforts.
Along with JustSueMe's work, I would also like to refer Simon Van der Veldt for his work on this topic as well - particularly on Github, the porters at #[email protected], especially mal- for his patience and support helping me out with this and the users here like Alecsandru also trying to making this work.
So a Big Thank You to all!
2016-07-07 Update:
Haven't had a lot of time lately to work on this, but still some new information on current status:
* The mer wiki page below now includes the notes I used on my port, by addressing each chapter of the SailfishOS HADK Porting Guide - so for those willing to work on this, go have a look and let me know how it goes!
* About the outgoing call issue: this seems to be a more delicate matter than initially thought. There isn't much information available out there, but based on JustSueMe's early work found here and also chatting with some very knowledgeable people down at #sailfishos-porters, it seems that we're dealing with an old RIL (radio interface layer) which is closed source and may have some issues in itself, and at this point, if assuming that if by working on cm-12.1 stable, then it should also work on SOFS, then perhaps something can be done either at ofono/audio routing level - relevant reading here about the architecture
* WLAN hotspot: this is not working on v0.0.9 and may be made to work perhaps on 0.0.10, will have to look a it
* Cameras: still no progress worth mentioning
2016-06-20 Update:
Mer Wiki Page
Latest SailfishOS Release
Youtube Video Gallery
2016-06-18 - version 0.0.8 - based on cyanogenmod 12.1 / android 5.0.1
2016-06-26 - version 0.0.9 - Bluetooth: now working, but with quirks. Details in the Release Notes
Things that don't work
Jolla Store (Harbour) doesn't work. Do not sign in with Jolla account.
Bluetooth: yet to be set up.
Voicecall: receiving calls works properly (along with Speaker, Pad and Mic buttons) / making calls fails with 3 tone signal.
Camera: only front camera photo works. back camera photo + any camera video fails.
Mobile Internet: intermittent feature, between reboots:
setting PIN code for the SIM card seems to help;
additionally, try giving it 10-15sec pause once the SIM inserted screen shows up, and then enter the PIN to unlock.
Home key not working.
Headphone jack.
Screen going to suspend mode not working.
Things that work
Sensors
GPS
SMS
Audio
Original Post from JustSueMe below:
Only You Are Responsible For Your Device. Dont Do Anything If You Dont Understand
Code:
[SIZE="2"]
88 ad88888ba 88b d88
88 ,d d8" "8b 888b d888
88 88 Y8, 88`8b d8'88
88 88 88 ,adPPYba, MM88MMM `Y8aaaaa, 88 88 ,adPPYba, 88 `8b d8' 88 ,adPPYba,
88 88 88 I8[ "" 88 `"""""8b, 88 88 a8P_____88 88 `8b d8' 88 a8P_____88
88 88 88 `"Y8ba, 88 `8b 88 88 8PP""""""" 88 `8b d8' 88 8PP"""""""
88, ,d88 "8a, ,a88 aa ]8I 88, Y8a a8P "8a, ,a88 "8b, ,aa 88 `888' 88 "8b, ,aa
"Y8888P" `"YbbdP'Y8 `"YbbdP"' "Y888 "Y88888P" `"YbbdP'Y8 `"Ybbd8"' 88 `8' 88 `"Ybbd8"'
[/SIZE]
This is Sailfish OS for I9505 only
only tested on int version.
Instructions:
Full wipe is needed.
Flash the relavent parts :
--
CM can be obtained from: CM-website
Hybris can be downloaded from here : Dropbox
--
Onces rebooted you will be presented with ONLY the samsung galaxy boot screen
Plug in a usb cable and login via telnet on port 23
--commands will show via telnets welcome screen
so move the file for enabling root and run the echo 'continue' command stated.
now login to telnet via port 2323
congrats you are now logged into SailfishOS and can do some debugging/modifications.
--
BUT ITS NOT USEABLE AS DAILY !!!?
Not to worry ! You have two options:
1. Ignore this thread, this rom isnt for you
2. or you can Dual boot:
---
Dual Booting:
I have made 2 .zips to enable easy dual boot via Custopm recovery
so place these .zips on your sdcard and flash one everytime u want to switch OS.
Boot back into Android (CM) - Dropbox
Book back into SailfishOS - Dropbox
----
Current problems:
Lib Error
Code:
.~))>>
.~)>>
.~))))>>>
.~))>> ___
.~))>>)))>> .-~))>>
.~)))))>> .-~))>>)>
.~)))>>))))>> .-~)>>)>
) .~))>>))))>> .-~)))))>>)>
( )@@*) //)>)))))) .-~))))>>)>
)[email protected](@@ //))>>))) .-~))>>)))))>>)>
(( @[email protected]). //))))) .-~)>>)))))>>)>
)) )@@*[email protected]@ ) //)>))) //))))))>>))))>>)>
(( ((@@@[email protected]@ |/))))) //)))))>>)))>>)>
)) @@*. )@@ ) (_(-b |))>)) //)))>>)))))))>>)>
(( @@@([email protected](@ . _/`-` ~|b |>))) //)>>)))))))>>)>
)* @@@ )@* (@) (@) /b|))) //))))))>>))))>>
(( @. )@( @ . _/ / / b)) //))>>)))))>>>_._
)@@ (@@*)@@. (6///6)- / ^ b)//))))))>>)))>> ~~-.
( @[email protected]@. @@@.*@_ VvvvvV// ^ b/)>>))))>> _. `bb
((@@ @@@*.(@@ . - | o |' ( ^ b)))>> .' b`,
((@@).*@@ )@ ) ^^^/ (( ^ ~)_ / b `,
(@@. (@@ ). `-' ((( ^ ` | b `
(*[email protected]* / (((( | | | . b `.
/ / ((((( / _.-~ Y, b ;
/ / / (((((( .-~ _.`" _.-~`, b ;
/ / `(((((() ) (((((~ `, b ;
_/ _/ `"""/ /' ; b ;
_.-~_.-~ / /' _.'~bb _.'
((((~~ / /' _.'~bb.--~
(((( __.-~bb.-~
.' b .~~
:bb ,'
~~~~
Updates:
XDA:DevDB Information
i9505- Sailfish OS, ROM for the Samsung Galaxy S 4
Contributors
JustSueMe
ROM OS Version: 4.4.x KitKat
Based On: CM, Hybris
Version Information
Status: Alpha
Created 2014-09-27
Last Updated 2014-09-27
R
R.
Nice! Although I'm no hero with adb and commands, I do like to see a new ROM in the i9505 forum!
Me Gusta!
this is so great
how is it performing ? can you use playstore on that os? or install any apk? does root and f2fs work?
thx
Thank you - subscribed and watching with interest
Screenshots plz?
I Think you guys have the wrong idea about this ROM as is.
we have no gui so its debug / developers only at this point
JustSueMe said:
we have no gui so its debug / developers only at this point
Click to expand...
Click to collapse
Nope, I understand totally, like I said, watching with interest what happens to this. Thank you for your work @JustSueMe :highfive:
Very nice! I'll give it a shot as soon as I have the time.
finally
No more news?
santya95 said:
No more news?
Click to expand...
Click to collapse
Just the lib errors, cant find libs but as far as I can see the strings are there and files exist. :/ just a little bump on the road
Sent from my GT-I9505 using XDA Free mobile app
subscribed
Bump. Is there any hope left?
zAo_ said:
Bump. Is there any hope left?
Click to expand...
Click to collapse
Dead like bread.
Nah just kidding.
i was waiting for this OS also to come up lol still waiting.:highfive:
xDroidZz said:
Dead like bread.
Nah just kidding.
i was waiting for this OS also to come up lol still waiting.:highfive:
Click to expand...
Click to collapse
I will confirm that it is dead... well as far as this thread goes. Unfortunately, part of my s4 died, so even tho it will boot any rom, daily use features can't be tested anyway, :banghead: , my next phone will be the new Ubuntu device as off late this month
JustSueMe said:
I will confirm that it is dead... well as far as this thread goes. Unfortunately, part of my s4 died, so even tho it will boot any rom, daily use features can't be tested anyway, :banghead: , my next phone will be the new Ubuntu device as off late this month
Click to expand...
Click to collapse
How did your s4 died? Dropped it or bricked it by software?
Sent from my GT-I9505 using XDA Free mobile app
xDroidZz said:
How did your s4 died? Dropped it or bricked it by software?
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
well its not dead but everyday functions don't work, video. audio/calls. camera.
Camera did one of them auto firmware updates and I can no longer access these functions. I've tried every suggestion to fix it nothing is working.
Sent from my MB860 using XDA Free mobile app
JustSueMe said:
well its not dead but everyday functions don't work, video. audio/calls. camera.
Camera did one of them auto firmware updates and I can no longer access these functions. I've tried every suggestion to fix it nothing is working.
Sent from my MB860 using XDA Free mobile app
Click to expand...
Click to collapse
wow and you are stuck with a Motorola ATRIX 4G MB860 ? Bad luck mate ! Thanks for the contribution that you made :good:
1I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Download and install a compatible recovery
4. Full wipe all
5. Flash firmware and gapps
6. Starting from 20150101 build - if you need root - you can enable developer options and activate root from here.
Also you can use old way: install SuperSu from recovery http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
Warning
If you make stock firmware backup and install any cm11\12 or omni - you can get problems with restore backup of stock firmware. It can be problems with apps - like not supported os. To fix it - after restore backup in twrp - flash stock firmware using odin without any erase - you will restore all functionality or you can try repair permissions in twrp.
Known Issues
---
Links
CyanogenMod Build:
50: 20151104 - first 5.1.1_r26 https://drive.google.com/file/d/0B-6nm7Jks0W5UzJnckRhRnNfbkU/view?usp=sharing (md5: 156985a81a84d373b11796b72623f96b)
49: 20151029: https://drive.google.com/file/d/0B-6nm7Jks0W5SlRXc29vSkFkV2s/view?usp=sharing (md5: e2eb464b235cb56eca1728aa65e06c43)
48: 20151006 - first 5.1.1_r24 https://drive.google.com/file/d/0B-6nm7Jks0W5eDlDVzkzRkg4d28/view?usp=sharing (md5: b43e02ddf0a5660aebd928c41e098924)
47: 20150923 - first 5.1.1_r18 https://drive.google.com/file/d/0B-6nm7Jks0W5aWxqbVl5MkZuZUU/view?usp=sharing (md5: 90ef4c212971e9cb0c3f1d721fbb1a71)
46: 20150910 - first 5.1.1_r13: https://drive.google.com/file/d/0B-6nm7Jks0W5SGZoUHNPaVRXcU0/view?usp=sharing (md5: bb30f44fead1397a05526a6dd04fdbbb)
45: 20150823: https://drive.google.com/file/d/0B-6nm7Jks0W5dXhpNkQzSkh4Tm8/view?usp=sharing (md5: ed11f20d90627c9649533538cfe4646e)
44: 20150810: https://drive.google.com/file/d/0B-6nm7Jks0W5UWRGdDRaYmRRelk/view?usp=sharing (md5: 928d2649135f7942dd085a7ee4ff5cda)
43: 20150805: https://drive.google.com/file/d/0B-6nm7Jks0W5Z21uclZGQ1Z3bms/view?usp=sharing (md5: 314c2a17cb5fe355d54ca524c542dd0e)
42: 20150731: https://drive.google.com/file/d/0B-6nm7Jks0W5cW1Sdjh0RGh5NHM/view?usp=sharing (md5: cbf64228449bfce55708542a3a4453a5)
41: 20150722: https://drive.google.com/file/d/0B-6nm7Jks0W5eXNidTViWkdta2c/view?usp=sharing (md5: a335999f932b5b856112e2e9af5e4840)
40: 20150716: https://drive.google.com/file/d/0B-6nm7Jks0W5NUJMeTNJangyNDA/view?usp=sharing (md5: 514147308c075701563cf5db77b6f1b2)
39: 20150712: https://drive.google.com/file/d/0B-6nm7Jks0W5OXZhcml5MGtTRXc/view?usp=sharing (md5: 362c58782924bf23a1de2a6f94b3fb0b)
38: 20150707 - first 5.1.1_r6: https://drive.google.com/file/d/0B-6nm7Jks0W5U1NmWFQweWhUdms/view?usp=sharing (md5: 698664b4f1015f990768acecdc0ec91f)
37: 20150703: https://drive.google.com/file/d/0B-6nm7Jks0W5dF9xSFIyNkwzaFE/view?usp=sharing (md5: 5cf011f480bd9a87238f7b3f50326813)
36: 20150614: https://drive.google.com/file/d/0B-6nm7Jks0W5SnJPc0ZDMUJ0Wlk/view?usp=sharing (md5: aa1675cc82edfaeb1585597ccda405cc)
35: 20150606: https://drive.google.com/file/d/0B-6nm7Jks0W5M0hwMHRlS2E2b0U/view?usp=sharing (md5: a64a367f150472a08024b6dae6d44074)
34: 20150528: https://drive.google.com/file/d/0B-6nm7Jks0W5RkM4VFFpN2IyMGc/view?usp=sharing (md5: 17fd3c06d7eb7375224ecde8535e63b6)
33: 20150523 - first 5.1.1_r3: https://drive.google.com/file/d/0B-6nm7Jks0W5bGx0MXV5NXYyYnM/view?usp=sharing
https://mega.co.nz/#!ZwgmFSxa!7RUAdNWfl6GYGDTi8HQeaYtOGYJZMPBh-gIEYfTzhp4
(md5: 52253b24547e007b697d88b779cc8d2e)
32: 20150516: https://drive.google.com/file/d/0B-6nm7Jks0W5ZmtpVFRRUkRxc0E/view?usp=sharing (md5: b72effa0fa9bb53ae21ba900214ae3b2)
31: 20150510: https://drive.google.com/file/d/0B-6nm7Jks0W5RzdDdExuaEc5N2M/view?usp=sharing (md5: 6c49be1f7bb065796be4d7afa3a1ecba)
30: 20150506: https://drive.google.com/file/d/0B-6nm7Jks0W5VkdtaUZuanMtVWM/view?usp=sharing (md5: 69f4459f8e61d30fc8dd9ddcc0951f59)
29: 20150504: https://drive.google.com/file/d/0B-6nm7Jks0W5a2IyYzVhbV9Rekk/view?usp=sharing (md5: 81872fb9fece5dba904b9c64c36edbb0)
28: 20150423: https://drive.google.com/file/d/0B-6nm7Jks0W5dU1SRU9kRmFfN2c/view?usp=sharing (md5: 5bb91efaaaa73273147feb3634b0de75)
27: 20150422: first 5.1.1: https://drive.google.com/file/d/0B-6nm7Jks0W5U1VFX181UXJuWkU/view?usp=sharing (md5: 4f8c8cb6f157fdee66bde06bcdff098b)
26: 20150421: https://drive.google.com/file/d/0B-6nm7Jks0W5QzFfeW91MkpqY3c/view?usp=sharing (md5: 640e767593f65d79ab7ad941552b60c0)
25: 20150415 - first build on new android-5.1.0_r5: https://drive.google.com/file/d/0B-6nm7Jks0W5VTdRcmNHUnNoMnM/view?usp=sharing (md5: a8b818c8922ec9ddc47e58e64b53aca1)
24: 20150411: https://drive.google.com/file/d/0B-6nm7Jks0W5c3BJYk1CUmozTjA/view?usp=sharing (md5: f7d26ba7d7035bd31b8aac1a8817cf4e)
23: 20150408: https://drive.google.com/file/d/0B-6nm7Jks0W5QWdVM24tS2pKZUE/view?usp=sharing (md5: 4efc947bdf2648a82efdffd9a98f45dc)
22: 20150405: sound settings now working: https://drive.google.com/file/d/0B-6nm7Jks0W5MzFlRWo3SXBfTFE/view?usp=sharing (md5: d13412fa39f5fb490fc33293ef1c4f41)
21: 20150404: finally new version, based on new android 5.1: https://drive.google.com/file/d/0B-6nm7Jks0W5clRnUlZKMTJ0YW8/view?usp=sharing (md5: 461545173f848bfef1f3e35a3addc98f)
20: build 20150319: wizard work: https://drive.google.com/file/d/0B-6nm7Jks0W5a2lXTEdrZ1BsQTA/view?usp=sharing (md5: ad7582d50c26e7e868a8025d4919bce7)
19: build 20150314:
- enable the stylus options (thanks apascual89) - settings\Language&input\Stlylus guestures:
- still crash at the start, removed the wizard (thanks ReasonablyRooted). Look like CyanogenMod prepare for 5.1 and now is a lot of changes.
https://drive.google.com/file/d/0B-6nm7Jks0W5bDBCN1pqQUotczA/view?usp=sharing (md5: b3c4df897a1992923042ec9c0c18183e)
18: build 20150308: https://drive.google.com/file/d/0B-6nm7Jks0W5eFo5ZTl1aUs2V2M/view?usp=sharing (md5: 4e426e9f5f5383912b6dcec0bc7d5eca)
17: build 20150301 - move to sd-card now working, latest code: https://drive.google.com/file/d/0B-6nm7Jks0W5TUJDWVFLRkkyZlU/view?usp=sharing (md5: 87cb05514598f056cb89a117684060e9)
16: build 20150220: https://drive.google.com/file/d/0B-6nm7Jks0W5aEFqUWV3U2RwQ1k/view?usp=sharing (md5: c6059618aa6e1fcd5ead39575f3c5d6b)
15: build 20150217: https://drive.google.com/file/d/0B-6nm7Jks0W5WjVSZHpEcG51ZTg/view?usp=sharing (md5: bd491e6bad0577504b27e7556ed1b34f)
14: build 20150207 - link updated, latest code, but cm12 still on 5.0.2, hope upgrade to 5.1 will be soon: https://drive.google.com/file/d/0B-6nm7Jks0W5YXZiaWRaNnEydlU/view?usp=sharing (md5: b3185f5d1501f15a8bdf5ffea71e51e6)
13: build 20150131 - start wizard working (only one error on start wizard - "Unfortunately, the process com.android.phone has stopped." - just ok and continue, this problem will check tomorrow), merge with latest changes: https://drive.google.com/file/d/0B-6nm7Jks0W5TTVaVFFrNUJMcmc/view?usp=sharing (md5: f6c3fa4b9a3a45becba930443e6acce7)
12: build 20150129 - Now at the end of an error running the wizard, this version only place on top of existing CM12. Checking this problem right now: https://drive.google.com/file/d/0B-6nm7Jks0W5YklLRWQ4MTVyM28/view?usp=sharing (md5: fa2b8fad7e029718ae53c2f88a74ce2a)
11: build 20150104 - root absent, performance page work (you can change cpu freq and governor), change cursor for s-pen (thank Dreamer7050): https://drive.google.com/file/d/0B-6nm7Jks0W5OTVHbzVZaDRPU1E/view?usp=sharing (md5: ba357fdec7590ef109d6e2a24bca5cd8)
10: build 20150101 https://drive.google.com/file/d/0B-6nm7Jks0W5dEdtRndMczl2U2s/view?usp=sharing (md5: fb79fc67de62f980d441372db25abde9)
9: build 20141224 -fix mouse cursor (thank bonuzzz): https://docs.google.com/uc?export=download&confirm=HsrO&id=0B-6nm7Jks0W5UlhwUXhlZkJZcGs (md5: b39415d0e5169a20e132bd4d55e3cbd7)
8: build 20141221 - latest code + turn on sepolicy, experimental change keyboard height (now about 70% of original): https://docs.google.com/uc?export=download&confirm=ubXT&id=0B-6nm7Jks0W5eW84OUo5MThiNG8 (md5: 778552b5480c4780fb4a3d7ae17c57b5)
7: build 20141219 - latest code + change wifi region from GB to All (thank to arcadia2uk): https://docs.google.com/uc?export=download&confirm=YlMi&id=0B-6nm7Jks0W5QXppRWNQTjR0ckk (md5: 37cf6a1c5d349f499f7e894b17f7133d)
6: build 20141217 - remove s-pen cursor: https://docs.google.com/uc?export=download&confirm=WymH&id=0B-6nm7Jks0W5WmY3ZnVBOFdieVk (md5: 62bdb528a8e73e7601c2b17bbe2632b2)
5: build 20141216: https://docs.google.com/uc?export=download&confirm=YlMi&id=0B-6nm7Jks0W5UzJrRF85SHZvRFU (md5: d33a4d0045b0b23d69806d74bfc825f4)
4: build 20141215 with change cursor for s-pen: https://docs.google.com/uc?export=download&confirm=YlMi&id=0B-6nm7Jks0W5bHhMMkpYVjZuekE (md5: 968d7140a7b3452e19a07fc80c45b2f7)
3: fist build 20141214: https://docs.google.com/uc?export=download&confirm=YlMi&id=0B-6nm7Jks0W5ajdDa3kwR09GU3M (md5: 771381e1990dc02ce25356b5c0d52f1f)
CyanogenMod Port:
2: clean-up https://docs.google.com/uc?export=download&confirm=YlMi&id=0B-6nm7Jks0W5SkVjZkgwTW13VzA
1: first very draft version https://docs.google.com/uc?export=download&confirm=YlMi&id=0B-6nm7Jks0W5dHV4RW9HUVFjRms
Gapps:
It need special version for lollipop, take it from:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Recovery:
Official TWRP: http://www.techerrata.com/browse/twrp2/v1awifi
Sources:
cm12 branch, in readme file (see device tree) all instructions for build.
Device: https://github.com/Valera1978/android_device_samsung_v1awifi
Kernel: https://github.com/Valera1978/android_kernel_samsung_v1awifi
Vendor: https://github.com/Valera1978/android_vendor_samsung_v1awifi
Thanks
Thanks to CyanogenMod team and special thank to crpalmer, his hard work on fix all problems for original SM-T520 finally allow create build for SM-P900.
Special thank for bonuzzz.
XDA:DevDB Information
CyanogenMod 12, ROM for the SM-P900, ROM for the Samsung Galaxy Note Pro 12.2
Contributors
Valera1978, bonuzzz
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 20150408
Stable Release Date: 2015-04-08
Created 2014-12-13
Last Updated 2015-04-08
Nice will flash it when I get home
Looks awesome! Will load tomorrow and post results!
One request along the way ... any chance you could include an MD5 checksum when you link the ROM? It's probably a leftover reflex from my early Internet days when Wildcat BBS would randomly drop or insert noise into a download, but it makes me feel better about hitting "Wipe".
So much fun.....
Sent from my SM-P900 using Tapatalk
Ok, I gotta say that this is one of the smoothest & fastest ROMs out there for the SM-P900 Wifi. Hands down, ABSOLUTELY ALMOST PERFECT. A lot of the samsung functionality is not there, but this is CyanogenMod 12 not TouchCrap, lol, I mean TouchWiz. I personally installed this ROM and am currently running it on several of my devices and I must say it is better than any other mentioned daily driver. It does not include the Samsung properties. However, if the developers and or the OP would allow me, I'm about 99% sure I could strip off all of the Spen(s) functionality from the TouchWiz Stock ROM, and have it fully implemented, installed, and completely working with this beast of a ROM. And yes I'm pretty sure that it can be done. That is of course if the developers and or the OP ALLOWED me the opportunity to assist. As of for this ROM. I have bench tested it several times and the numbers are better than any other ROM out there today for this model. Please don't anticipate that I'm implying other developers ROM's are not all there or are not good ROM's. It's just my honest opinion, from some 25+ years of advanced software and hardware development that this ROM is the most stable, best battery consumption, has a better and far superior benchmark, clears the RAM faster, reads and writes better with this particular hardware, produce better results, even without the Spen functionality, than anything else currently available. If you were to add the Spen full functions and missing software. This would devastate anything else out there, and would totally show the full power capabilities of what this hardware can properly do with the right provisioned software and or ROM.
Basically put. I've developed for 3 of the top companies in the US and this would absolutely be my daily driver, if the missing Spens functions were to be added. Without the functions added. It is by far the most stable and rock solid ROM out there.
If you're looking to fix that crack flashing addiction, one time and for all, then look no further, this is it. PERIOD.
Android.Ninja
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
she's a beauty
Thank you so much!!! Coming from stock this rom is a huge improvement. I will be donating when I figure out how. The ROM installed without issue. I'm a software engineer so I use my tabby for uml diagramming, taking notes at meetings, android development, and surfing the web. First thing I tested was the spen in papyrus and it works great(installed the spen app recommended from the kitkat rom.) The cover works great, on/ off just like before. Chrome on the stock rom would pause all the time in the middle of page loads. It was so annoying that i was considering pulling out the profiler to looking for a solution. Its now so smooth that i feel i couldnt make any further improvement. Overall, the performance versus the stock, well there is no comparison, your ROM smokes it by a mile. I am currently developing a USB accessory. I could not access this tablet over a Bluetooth PAN because Samsung didn't let me use the blue tooth to connect to my PC. Now I finally have bluetooth PAN, can't wait to try it on Monday. Oh yeah, I'm a super geek and I just had to have lollipop on my tabby, thank you for the early Christmas present!
To anyone who is wondering if they should give it a go.....do it!!
PS. Not sure how much of a trade secret your build process is but I would love to know the process. As I said earlier I'm developing a USB accessory and to test I must plug and unplug the USB cable all day long. Every time I do this adb disconnects the debugger. I have looked at the code and think I can make the needed changes to avoid the disconnect. All I need to do is build adb from source and test the change. having a working build would really help.
Thanks again,
Ologn
I'm actually very impressed at how well this has been ported over. This actually is the best CM Lollipop ROM I've ran thus far (and that's across 9 different devices..).
Great work. Shoot me a message if you come by any issues you can't figure out.
I had a few issues with the setup.
1. I could not sign in to Google during setup. It would say it had trouble connecting and to try again later. I push next button and same message comes up over and over. Had to use back button.
I could sign in to Google from the browser but still couldn't get Play Store for recognize me.
2. In the About device, all the info was from the previous rom and kernel. I did full wipe of delvic, cache, data, and system.
So, I restored back to previous rom since I couldn't install any of my apps.
---------- Post added at 05:29 AM ---------- Previous post was at 05:16 AM ----------
Also, I tried installing clean up: cm-12-port_working_last.zip, in twrp but it error ed saying that it was for that it was for xxxwifi (sorry, don't remember exactly ) but I had xxxxaxx, as if I was running at the rom or something so couldn't install it. Was I supposed to run it first? It is listed first but has 2 by it so I'm a little confused.
Recovery
Hello guys! Thanks for the rom!
I have a question, You need a different recovery to that used for CM 11? Thanks
dadecamp said:
I had a few issues with the setup.
1. I could not sign in to Google during setup. It would say it had trouble connecting and to try again later. I push next button and same message comes up over and over. Had to use back button.
I could sign in to Google from the browser but still couldn't get Play Store for recognize me.
2. In the About device, all the info was from the previous rom and kernel. I did full wipe of delvic, cache, data, and system.
So, I restored back to previous rom since I couldn't install any of my apps.
---------- Post added at 05:29 AM ---------- Previous post was at 05:16 AM ----------
Also, I tried installing clean up: cm-12-port_working_last.zip, in twrp but it error ed saying that it was for that it was for xxxwifi (sorry, don't remember exactly ) but I had xxxxaxx, as if I was running at the rom or something so couldn't install it. Was I supposed to run it first? It is listed first but has 2 by it so I'm a little confused.
Click to expand...
Click to collapse
This firmware for SM-P900 only (code name: v1awifi). It's always detect as v1awifi for any custom firmware.
You can make small modify to run this firmware: open cm-12-port_working_last.zip, find META-INF\com\google\android\updater-script and remove first line from it.
Wow, very interesting! Спасибо, Валера!
I am curious about S-Pen here and all that handwriting stuff.
Anybody could share his experience?
Aurondios said:
Hello guys! Thanks for the rom!
I have a question, You need a different recovery to that used for CM 11? Thanks
Click to expand...
Click to collapse
No, you can use the same recovery. I use TWRP 2.8.1.1.
I can put cwm from cm11.
when using the s-pen an arrow appear as using a mouse Can I remove it? its annoying
---------- Post added at 04:24 PM ---------- Previous post was at 04:07 PM ----------
tatuk said:
Wow, very interesting! Спасибо, Валера!
I am curious about S-Pen here and all that handwriting stuff.
Anybody could share his experience?
Click to expand...
Click to collapse
The S-pen works veeery nice! Beter than stock and CM11 but there is a little problem. When u use the s-pen an arrow appear in the screen like when you use a mouse.
Which of the 3 links in the initial post should we use - just want to make sure thanks
golfinggino said:
Which of the 3 links in the initial post should we use - just want to make sure thanks
Click to expand...
Click to collapse
The one with number "3." is the latest.
---------- Post added at 08:41 PM ---------- Previous post was at 07:51 PM ----------
wiped all.. still have this problem..
add http ://shrani.si/f/h/12d/4tZld3cF/20141214203353.jpg
it says my device is not v1awifi..but i have sm-p900 wifi version...
Aurondios said:
when using the s-pen an arrow appear as using a mouse Can I remove it? its annoying
---------- Post added at 04:24 PM ---------- Previous post was at 04:07 PM ----------
The S-pen works veeery nice! Beter than stock and CM11 but there is a little problem. When u use the s-pen an arrow appear in the screen like when you use a mouse.
Click to expand...
Click to collapse
You cant turn off mouse pointer.
There are very early builds. They dont pretend to any stability and usability. Use them as is.
Valera1978 said:
This firmware for SM-P900 only (code name: v1awifi). It's always detect as v1awifi for any custom firmware.
You can make small modify to run this firmware: open cm-12-port_working_last.zip, find META-INF\com\google\android\updater-script and remove first line from it.
Click to expand...
Click to collapse
I tried newest build and still get the error. Says my device is v1a3gxx. I am on SM-P900 and using Civato's rom
I am now trying to delete that line but don't know where the line ends, because the text continues on in windows notepad.
assert(getprop("ro.product.device") == "v1awifi" || getprop("ro.build.product") == "v1awifi" || abort("This package is for device: v1awifi; this device is " + getprop("ro.product.device") + ".");
Thanks for your help.
dadecamp said:
I tried newest build and still get the error. Says my device is v1a3gxx. I am on SM-P900 and using Civato's rom
Click to expand...
Click to collapse
Sounds like you installed a "wrong" CWM or TWRP. I guess Civato's ROM did not check this during the installation. Go ahead and reflash your Recovery. Make sure it's for P900, not P905 or anything else.
dadecamp said:
I tried newest build and still get the error. Says my device is v1a3gxx. I am on SM-P900 and using Civato's rom
I am now trying to delete that line but don't know where the line ends, because the text continues on in windows notepad.
assert(getprop("ro.product.device") == "v1awifi" || getprop("ro.build.product") == "v1awifi" || abort("This package is for device: v1awifi; this device is " + getprop("ro.product.device") + ".");
Thanks for your help.
Click to expand...
Click to collapse
You have P901 model
so you have to extract zip archive, replace in updater-script "v1awifi" to "v1a3gxx", make new zip archive and flash it.
Dont edit it in windows notepad. download notepad++ for example.
Great ROM just flashed and testing it out now everything seems to be working as it is should thanks for another great ROM option