Going to try to find all the roms I can and get them in one place before it gets real messy, Please let me know if I missed your rom or if you added a new one so I can add it even if im not at my computer you can do this by e-mail to [email protected] or to my phone! 906-430-1564 please dont call me for no reason, that will just make me mad but if you have a sweet forward that Id like to send to my friends. Send it, Im paying for unlimited messaging might as well use it, I have a sick and twisted and sarcastic sense of humor and that should help.
READ THIS FIRST!!!!!
SAVE THE POOR PEOPLE WORKING ALL OF THE QUESTIONS THAT ARE ANSWERED HERE!!!!!
thanks goes to seraph1024 for making this. http://forum.xda-developers.com/showthread.php?t=619153
Stock-Leaked Roms
Leaked:
EPE76 image format download MD5: 31a7944d2af0ecdaa06f4bf8f1558a10
http://www.mediafire.com/file/ynznmyxkiiz/EPE76-stock-images.zip
Leaked:
EPE54B update zip download MD5: 0cfa033d58509b9bdf5d9ae09d976a38
http://www.mediafire.com/file/amrjmuzj1ho/Leaked-EPE54B-stock-image-update.zip
Second Update:
ERE27 update zip download MD5: 90700607c04279716b505aa203e9c684
http://www.mediafire.com/file/vomqomnwndi/2nd Update-ERE27-stock-image-update.zip
ERE36B update zip download MD5: MD5 070e47f96d7c14e682232155e86a8f4b
http://www.mediafire.com/file/ntztctz20ly/Leaked-ERE36B-stock-image-update.zip
Original Stock:
ERD79 update zip download MD5: 5e17b0351024c8fb1a2020f1fd55210e
http://www.mediafire.com/file/2mjozawirom/Original-ERD79-stock-image-update.zip
http://www.mediafire.com/?sharekey=a1e428ed720bdf41ab1eab3e9fa335ca03f7573b24953fcd Here are some files thankfully posted by Moderator Mikey1022 for general use until there is another repository for stock roms
ROMS
Ok Rom list starting with the newest:
Cyanogen
CyanogenMod-5: Kang Central Station (STABLE) [03/23/2010 / 5.0.5.3]
http://n0rp.chemlab.org/android/nexus/update-cm-5.0.5.3-N1-signed.zip
Cyanogenmod:
http://forum.xda-developers.com/showthread.php?t=623496
Chef: cyanogen
GrimmsMod based on CyanogenMod 5.0.5.3(All in one) Advanced overclock and undercurrent cooked in use if you know what this means or read about it and understand it! :
http://forum.xda-developers.com/showthread.php?t=654958
Chef: Grimms
[CyanogenMod-5 based] Core CM w/Exchange Apps:
http://forum.xda-developers.com/showthread.php?t=651448
Chef: lpasq
CyanogenMOD BakedGoods 1.1:
http://forum.xda-developers.com/showthread.php?t=639637
Chef: Herver
MoDaCo
21/Jan 1.3 - MoDaCo Custom ROM:
http://forum.xda-developers.com/showthread.php?t=614186
23/Mar 2.1 - MoDaCo Custom ROM for Nexus One with online kitchen:
http://forum.xda-developers.com/showthread.php?t=630529
01/Apr Alpha r21 - MoDaCo Custom ROM Desire Port with Online Kitchen (+HTC_CIME!):
http://forum.xda-developers.com/showthread.php?t=636048
Chef: paulobrien
TheOfficial Nexus1
Enomther's TheOfficial Nexus1:
http://forum.xda-developers.com/showthread.php?t=614427
Chef:enomther
NexDESIRE
NexDESIRE_v1.2_REMIX!!! Looking Better:
http://forum.xda-developers.com/showthread.php?t=637325
Chef: manup456
Snack Pack
SnackPack v0.2.1 [CM5+Extra Snacks] - New A2SD Method:
http://forum.xda-developers.com/showthread.php?t=638301
Chef: ctso
Passion Google
[ROM]Passion_Google_WWE_1.09.1700.1_EPE54B:
http://forum.xda-developers.com/showthread.php?t=642811
Chef: Football
OK I think that covers them if I made a mistake please let me know I will come back and update as much as I possibly can, and fix any errors. Nexus one will be here soon!!!
Ok did Roms and now Im gonna do Kernels Hopefully people find this usefull, Again if you add one please pm me or message me here or at [email protected] or use the device in your hand 906-430-1564
Kernels
Diet Kernel for Nexus One (based on CM 5.0.5.3), incl. undervolting and overclocking!:
http://forum.xda-developers.com/showthread.php?t=654416
Coder: Ivan Dimkovic
Direct Link: Attachments on first post of thread.
:
[Kernel - .32 & .33]Conservative Power Governor Kernel (with several tweaks): http://forum.xda-developers.com/showthread.php?t=653598
Coder: intersectRaven
Direct Links:
20100329_2221:
http://www.mediafire.com/?ya2tdzbdjiz
http://www.mediafire.com/?wqtigvyg0du
20100329_0835:
http://www.mediafire.com/?njjnjjqwltz <= 2.6.32
http://www.mediafire.com/?ttdz0cj0z0m <= 2.6.33
:
[Kernel-.33.2!] OCed - UVed: -1.113Ghz Stable - 4/05 -8MB extra ram!: http://forum.xda-developers.com/showthread.php?t=633238
Direct Link:
boot-cm_2633.2-oc-uv-ram.zip
http://droidbasement.com/nexus/kernels/ram/boot-cm_2633.2-oc-uv-ram.zip
boot-cm_2633.2-oc-uv-xtra-ram.zip
http://droidbasement.com/nexus/kernels/ram/boot-cm_2633.2-oc-uv-xtra-ram.zip
<><><>
zImage-cm_2633.2-oc-uv-ram
http://droidbasement.com/nexus/kernels/ram/zImage-cm_2633.2-oc-uv-ram
zImage-cm_2633.2-oc-uv-xtra-ram
http://droidbasement.com/nexus/kernels/ram/zImage-cm_2633.2-oc-uv-xtra-ram
lib-2633.2.tar.gz
http://droidbasement.com/nexus/kernels/ram/lib-2633.2.tar.gz
.
[Kernel-.33.2!] Undervolted @ Stock Speeds-4/04 - CM5.0.6src - #teamdouche:http://forum.xda-developers.com/showthread.php?t=634587
Coder: persiansown
Dircet Link:
http://kmobs.scepterr.info/kernels/zImage33UV.zip
:
[KERNEL] [CM-Source] [BFS-315] KiNgxKxernel 2.6.33 1.113Ghz Capable!: http://forum.xda-developers.com/showthread.php?t=635806
Coder: kingklick
Direct Link:
http://www.4shared.com/file/233881708/2a7fa596/KiNgxKxernel-2633-5.html
Radios
Stock
32.24.00.22U_4.03.00.21_2 download MD5: 28a6aabf2f756806c5eb5e99a9626ca4
Direct link:
http://www.androidspin.com/download...Official_Nexus1_Radio_Update_4.03.00.21_2.zip
32.26.00.24U_4.04.00.03_2 download MD5: c55116d119e9e30cffc86875dce1a560
Uploader: enomther
Direct Link:
http://www.androidspin.com/download...Official_Nexus1_Radio_Update_4.04.00.03_2.zip
Original (older) Radio image 4.02.02.14 (from ERD79) in an update.zip.
http://www.androidspin.com/download...heOfficial_Nexus1_Radio_Update_4.02.02.14.zip
If anyone wants to be helpful point me in the direction of radios that are not listed here, if you upload on please notify me.
reserved111111111111111
good effort!
Please everyone keep the chatter to a minimum so we can maximize the usefulness of this thread. If you have a rom or kernel that needs to be added to the list let the OP know.
This a very good idea! a one stop shop for all of us. especially to all newbie user. keep up the good work thanks..
Good job Justin. I actually thought bout doing this as well, makes people's lives much easier.
Thanks man Someone still need to go do themes in the other thread so it doesnt get so cluttered we cant find anything I wont be able to keep up with all three when more people get the device.
Well for now there aren't many themes available, no need for a sticky at the moment.
Good sticky. Maybe a post linking to all the different radios? When I first rooted my phone I found it harder to find info, and links, to the different radios and whether they were just for US users.
In one of the two reserved spots, would it be a good idea to link to all the versions of radios and RILs? I've been trying to find some older ones, but this could make it nice and simple.
Will get on it as soon as the little one goes to sleep, Shes dancing around to spongebob right now, not good for me concentrating on anything.
Check Enomthers rom link for radio links
Any chance at getting links to stock roms?
Sure will do my best to get them up. Daughter is kinda freakin' She is teething like crazy.....
Here is a mediafire link...except roms and kernels
http://www.mediafire.com/?sharekey=a1e428ed720bdf41ab1eab3e9fa335ca03f7573b24953fcd
This is not a Q&A section, only post here if you have a rom, radio or kernal to contribute to the list.
Nexus One 1.11 ROM, Maybe you can get some use out of it.
Also the 1.10 is uploades has well.
http://conflipper.com/shipped/Passion (Nexus One)/
hi justin.
please don't post direct dload links from droidbasement on to this thread (please link to the actual blog post). i want people to fully read what is written prior to downloading.
thx
Related
Without the inclusion of proper documentation included with an Android Rom or an Android Build users will start filling up the HD2 Android Development Forum with why this wont work when it does on someone elses Rom. To stop this from happening there will be a requirement when creating a Thread for a Rom with Android included, or an Android Build.
------------------------------------------
------------------------------------------
If you are making a Rom with Android built in or an Android Build that is run from haret then please INCLUDE with your file a readme.txt file in the ROOT of your release archive with the following information:
*What BUILD version?
An internal version # that can be used to identify the authors exact release (e.g. my-rom-v0.5.zip) for easier reference for the users and fellow developers benefiting from the release.
*Which kernel image and kernel modules are used?
Where are zImage and modules.ko originally downloaded (in case the chef didn't compile on their own) and where is the kernel source code for the kernel and modules.
In case the chef did not compile on his own, he should still be able find out where the source code is.
(The license under which the Linux kernel is released requires the distribution of the source code that was used when distributing builds.)
*What rootfilesystems are used?
Where was it taken from, what does it include (android version it's based on etc) and in case of self compilation, where is the source code.
(In case of most windows mobile shipped devices that's often some rootfs file e.g. named android.ext2 and an initial ram filesystem often named initrd.cpio.gz).
*ChangeLog*
A ChangeLog is really an essential addition in every build as it informs the end user what modifications have been made from the last build. This will save you ALOT of questions as to what has been added, deleted or modified and therefore is a requirement for everyones benefit.
*WindowsMobile version your Android Build was tested on*
Please include your WinMo Build version, HTC OemDrivers (if known), XIP (if known) and Radio version so that users know what the Android Build was tested on and can replicate if neccessary for fault finding purposes.
------------------------------------------
------------------------------------------
If you are unable to obtain any of this information and thus can't make it available through an included readme.txt you should not distribute your rom and keep it for personal use only.
If you are using an exact copy of a present release (e.g. in case of a WinCE rom that has an android 'dual boot' option) you must include the readme.txt from the original rom chef.
If you release a Rom and do not have the required information then you will be asked to either create and include a readme.txt file with your Rom or ask for the thread to be deleted.
If you have any comments or questions on this please feel free to post.
Mark.
** reserved **
Thanks a lot for the quick action, Mark. I am glad to see a first positive response.
If this will establish I hope that
*users are informed about what they get
=>less unneeded questions and thus more room for constructive feedback
*developers have an easier time to benefit from present releases
*new developers must try to get an understanding of what they are doing
=>more quality releases
The original post can be found here.
I think it would be nice to hammer out the readme.txt requirements together with chefs so we can get some convention that satisfies everybody.
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
dcordes said:
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
Click to expand...
Click to collapse
Edited the 1st post to include this
Mark.
Will be following this convention for any future releases
DarkStone1337 said:
Will be following this convention for any future releases
Click to expand...
Click to collapse
Thank you
Future releases soon I hope lol
Mark.
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Excellent rules! We need to improve stability of ports and eliminate all unnecessary questions !
P.S. Hope there won't be any "bogus", or "copy-paste-claim" ROM-s.
dcordes an mskip +1
ahbad said:
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
Click to expand...
Click to collapse
Very good idea. I think we should at least add the rom release date to minimum required readme.txt information.
For the rootfs release date I think we should leave it up to the chefs because I think it will be hard to find out in many cases. Reason is rootfilesystems get passed on 20 times...
In case of the kernel release date it might be a good idea to add it. should be easy to find out. When you grab the kernel e.g. from the two sources I link to in the thread
http://oe.netripper.com/files/htcleo_autobuild/
http://cotulla.pp.ru/leo/Android/
you can just copy paste the date from filename or information on the site. This would be very useful assuming the kernel images will be removed at some point.
On a side note: For both kernel examples the source code repository to add in readme.txt is
git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git htc-msm-2.6.32
gitweb: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
So currently in every leo rom readme.txt this must be linked to as kernel source reference. netripper autobuild zImages using this exact source code and cotulla zImages share same codebase (although currently the latest changes are unavailable but will be added in git soon)
shufflez said:
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Click to expand...
Click to collapse
To me that seems over exaggerated. Rom version in file name should be enough. Rest can be looked up in readme.txt
So what does everybody think? If we add the release date of kernel and completed rom, do we have an agreement ? In that case we should compile an example and add it in the first post.
best regards
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
David Balfour said:
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
Click to expand...
Click to collapse
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Install to folder
May be a good idea install all files to appropriate folder, not directly root of SDcard as in last darkstone FROYO. Greatly simplify process of testing and changes between several images and don't messy root. Switching between different versions is than as easy as renaming directory.
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
dcordes said:
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Click to expand...
Click to collapse
I agree with you on this theres no need to make things more complicated than they need to be. Although there does need to be some sort of standard for the thread title.
And no I cant think of anything else right now that needs to go in.
dcordes said:
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
Click to expand...
Click to collapse
Also agree that its upto the chef how they want their files set up as long as its clearly stated in the readme.txt what to do to get it working.
Everything sounds fine What needs adding to the first post to make it complete?
Sorry I have been working on my Loader but its all finished now (I hope).
Mark.
HD2 Android Image & Instructions
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
youdaler said:
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
Click to expand...
Click to collapse
I will just give you a friendly warning this time as it is your first post. This thread is for the discussion of information to be included by Android builders.
If you look in the Android forum then you will see working builds by DarkStone and by Dan1j3l. Look at their threads for how to load Android. to answer your question yes Android does work (95%) on the HD2.
Please confirm you have read this so I can delete these posts and keep the thread clean. In futured please only post in the correct thread and if you arent sure then post in the Q&A thread at the top of the Android forum.
Mark.
Understand. Thanks for clarifying.
I think we should extend the readme.txt items with some section like 'expected issues' or 'known problems' .
And in the readme.txt , could help too:
Tested with:
-WinMo rom x.xx.xx
-Radio rom 2.xx.xx
Sent from my HTC Desire using XDA App
If you've ever visited the Evo 3D development section, you may have seen my stickied thread there with a complete list of News, Roms, Recoveries, etc, all in one thread. (Link)
I plan on doing the same here once we getting some progress. If you enjoyed my last thread, please check this as well.
----------
One place for everything. To reduce clutter.
*Note to Devs*
If I have missed your ROM/Guide/Mod, please PM me with the Title and link so I can add it to this thread.
News:
-No development yet.
-HTC is having [Apple] issues trying to release the phone on time. According to some websites, the date has been pushed back from 5/18 to 5/23.
Recoveries:
Radios:
Kernels:
Custom Roms: [*Note* All newer ROMS will be at the bottom.]
[ROM] Stock 1.12.651.2 - with Root/Busybox -- by regaw_leinad
http://forum.xda-developers.com/showthread.php?t=1654709
Mods:
Guides:
Unroot:
More to come..
This thread already exists. Please look before posting.
http://forum.xda-developers.com/showthread.php?t=1645890
arozer said:
If you've ever visited the Evo 3D development section, you may have seen my stickied thread there with a complete list of News, Roms, Recoveries, etc, all in one thread. (Link)
I plan on doing the same here once we getting some progress. If you enjoyed my last thread, please check this as well.
----------
One place for everything. To reduce clutter.
*Note to Devs*
If I have missed your ROM/Guide/Mod, please PM me with the Title and link so I can add it to this thread.
News:
-No development yet.
-HTC is having [Apple] issues trying to release the phone on time. According to some websites, the date has been pushed back from 5/18 to 5/23.
Recoveries:
Radios:
Kernels:
Custom Roms: [*Note* All newer ROMS will be at the bottom.]
[ROM] Stock 1.12.651.2 - with Root/Busybox -- by regaw_leinad
http://forum.xda-developers.com/showthread.php?t=1654709
Mods:
Guides:
Unroot:
More to come..
Click to expand...
Click to collapse
?? Sir, I am not trying to be rude, but isn't this clutter when a "Post" something twice, and inside an original post you will be link's after links but not information on "How to's"
Think the idea of having it all in one spot is awesome, but "How to's" not links(Ur3Dpost) to redirect? Then it would be, 2 stops instead of one..
Closed....OP you could of looked at the already made thread for this...
though the need for either right now imho is pretty questionable...
Are you learning about rom development?
You have made a your own rom and want to share it?
Its your first rom thread?
Yes?!?!
Then this is right guide for you which will help you make a good, clean, nice looking rom thread
ROM TITLE:
-- your rom should have simple name
-- in rom title only use [ROM][BASE][SUPPORTED DEVICES]--TITLE[LOCKED/UNLOCKED BOOTLOADER][LATESTUPDATE]
-- in base i mean ICS, GB, JB, AOKP, PA, AOSP, CM7, CM9, CM10
-- dont add any other words in title for example: extreme battery durance, smooth as hell and such
ROM THREAD:
-- mention rom base, and for what you have made this rom (xperia looks, speed, battery, stability and such)
-- make sure that you list every change that is made in rom. It doesnt matter if you had made it or the original developer from who you took base rom. But make sure to give credits
-- dont forget changelog once you update rom
-- screenshots are important.
-- if you want you can mention which apps you deleted and upload them for others so they can install them
-- if there are any bug fixes you posted later dont forget to post it in #1,2,3 post
-- use different size (and color if you want) for title of section (changelog, features , download) and other size for text of it
EXAMPLES:
-- here is one of my rom threads. Im not saying its best rom thread (it isnt for sure) but it will give you an good example.
Check this
-- you can find manny other great rom threads in bigger forums like galaxy s 3, htc one x and such
Dear All
Ever heard or read of/about PDroid? Ever thought about securing your data, addresses, locations and SIM information from being (mis-) used by downloaded apps, games and other things?
Time to read about...
PDroid is a ROM-hooked privacy protection of your personal information & data. It let's you set per-app access rights to your private informations. No more hidden address ore phone-book misuse or GPS-based advertisement "enhancement".
Read more about PDroid/OpenPDroid: http://forum.xda-developers.com/showthread.php?t=2098156
What is this thread about?
This shall be a pure SERVICE thread to all users and friends of Android that care about their privacy.
We (users & friends of xda-developers, PDroid & AutoPatcher) help you patching your ROM so that you can use your apps and games under privacy protection.
Patching these ROMs provides some hurdles and hooks - some of us are very experienced and built & installed an environment to enable "simple patching". Many users stand back from this effort and have few experience with command-based or GUI-based patching - these are the addressees that we want to enable to have ALSO privacy protection on their tablets and smartphones.
Especially when you're not a very frequent "ROM-hopper"
What IS this service?
You drop us a link & we patch & upload this patch - that's it.
Please grant us some time, the response time depends on the supporters - and they all spend their free time for this.
(Please thank the helpers and providers by hitting the Thanks button!) ... maybe also rating the thread?
How to USE the service?
You install your ROM and post us the download link. You'll get back an upload with the patch. Usually you can simply flash it to your device, you should not have any problem, installing it "over" your installation. Even no data loss.
To set the rights for each app and get a warning if rights are changed, install "PDroid Manager" from App Store and launch it.
Nevertheless - make sure to have a backup
- of your (unpatched) ROM install
- of your data & installation
before your first trial.
Further Information:
OpenPDroid / PDroid information: http://forum.xda-developers.com/showthread.php?t=2098156
PDroid Manager - the access rights managing software: https://play.google.com/store/apps/details?id=net.digitalfeed.pdroidalternative
AutoPatcher - the tool if you also want to start patching...: http://forum.xda-developers.com/showthread.php?t=1719408
We'll elaborate this thread and post more and more and add links and further information - subscribe it to get familiar with PDroid!
One last notice: these patches do NOT induct any backdoor, trojan nor any other virus ar any advertisement to your device - rather enable you to set rights to achieve the opposite.
Special thanks to all contributors here, to the PDroid and OpenPDroid Team and especially to mateorod and his AutoPatcher's team.
With kind regards from Switzerland - Chris
Please thank the helpers and providers of patches by hitting the Thanks button!
How to install / proceed with my patch?
Flashing ROMs or ROM updates is unfortunately quite device-dependent.
Please make sure you have a copy of your flashed (unpatched) ROM to restore
Please make sure you backed up all of your data
A GENERIC guidance could be the following steps: How to update your installation to the PDroid-enabled one:
Download [yourROM] (unpatched version)
Download the attached patch-update from the appropriate post - the answer of one of the "helpers" (hit THANKS! )
Put both on your SD-Card
Enter Recovery of your device
(If not yet installed) Install (ZIP from SD-Card) the full fletched non-patched [yourROM] (usually no need to re-boot after that, simply go on with...)
Make sure you installed the appropriate GApps
Install (ZIP from SD-Card) the patched update from this thread's answer post "over it"
IF you changed a major Android version (e.g. 4.2.2 -> 4.3), perform a full wipe
Reboot the device
Go to Play Store and download "PDroid Manager" and start it to configure your privacy settings per every single App - You're done.
After you set up the permissions, you don't need the Android's (very limited; since 4.2.2) privacy protection anymore - deactivate it
Greetz - Chris
#3 - reserved
Req: Patch for cm-10.2-20130918-NIGHTLY-p3100.zip
EXAMPLE of a Request:
Hi
can you patch CM 10.2. Nightly as per 2013-09-18 for P3100 device for me?
Device details:
Manufacturer: Samsung
Device: GT 2 7.0 P3100
ROM's download link: http://www.get.cm/get/jenkins/41935/cm-10.2-20130918-NIGHTLY-p3100.zip
Christoph21x said:
EXAMPLE of a Request:
Hi
can you patch CM 10.2. Nightly as per 2013-09-18 for P3100 device for me?
Device details:
Manufacturer: Samsung
Device: GT 2 7.0 P3100
ROM's download link: http://www.get.cm/get/jenkins/41935/cm-10.2-20130918-NIGHTLY-p3100.zip
Click to expand...
Click to collapse
EXAMPLE Answer:
Hi pls find attached the patch
Nice idea, hopefully it'll get approved and added to the development threads op.
I might join in by writing a short explanation about VM's and how to use the patcher there (since I was doing it this way until a few weeks back, where I got (nearly) rid of win)
Being on Linux actually makes the whole thing a hell of a lot easier.
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
Here it is!
IRKONIK said:
Nice idea, hopefully it'll get approved and added to the development threads op.
I might join in by writing a short explanation about VM's and how to use the patcher there (since I was doing it this way until a few weeks back, where I got (nearly) rid of win)
Being on Linux actually makes the whole thing a hell of a lot easier.
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
Click to expand...
Click to collapse
THANKS, IRKONIK!
You know, PDroid is a great service protecting us, the work of the developers is great - including mateorod and others who're working all day and night, as it seems.
And if we can, we should try to make this protection available also (and especially!?) to all non- or semi-enthousiastic users that do not neededly flash ROMs frequently..
Thanks for your support - highly appreciated!
Greetz - Chris
GT-N7000, Krueger CM10.2
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
ralphm2004 said:
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
Click to expand...
Click to collapse
Hi ralph
You posted in the wrong thread - patch DEVELOPMENT is under http://forum.xda-developers.com/showthread.php?t=1719408 who add support for non-patchable ROMs, we just build it for users...
greetz - Chris
Christoph21x said:
Hi ralph
You posted in the wrong thread - patch DEVELOPMENT is under http://forum.xda-developers.com/showthread.php?t=1719408 who add support for non-patchable ROMs, we just build it for users...
greetz - Chris
Click to expand...
Click to collapse
Hi Chris,
thanks for the information, i misunderstood the sense of this thread.
As a junior member i can't post in development-threads. Can someone please post it there?
I posted a link, so you'll be fine (hopefully)
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
ralphm2004 said:
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
Click to expand...
Click to collapse
Thanks for the thread, Christophe!
I can add support, but I need the rom's source code. You will have to ask the dev for a link to their github page. But then I can add support.
mateorod said:
Thanks for the thread, Christophe!
I can add support, but I need the rom's source code. You will have to ask the dev for a link to their github page. But then I can add support.
Click to expand...
Click to collapse
hi mateorod,
i cant post to that thread to. there doesn't seem to be a link to the right source.
but with v3.1.78 the patch has worked.
i try to contact bangsti and ask for the source, maybe it is helpful for the future.
ralphm2004
--- edit ---
got the information from bangsti:
Is the CM10.2 Source and crdroid Source.
github.com/cristianomatos
github.com/CyanogenMod
Krueger is a Mix from this Sourcen.
Well, I said it, so here it is (yeah, I deliver )
How to use the Auto-Patcher on Linux (debian based (!!)) in a virtual machine.
This "tutorial" does not take you by your hand. No, I DEMAND :silly: that you do stuff by yourself. It helps you! (Trust me. The easy way is not always the best)
First of all: You need a virtual machine with your favorite distro. (I like Mint Cinnamon)
How this step works? Well, google/youtube it. There is so much info about it, there is no need in writing another tutorial. Especially when other people have done it waaaay better
So, you have linux running. What now?
Second step: Getting all the stuff the patcher relies on.
Code:
sudo apt-get update
Code:
sudo apt-get install git git-core cpio patch unzip tar openjdk-7-jdk openjdk-7-jre
Third step: Getting all the files from github and build the patcher
Code:
git clone https://github.com/mateor/auto-patcher
Code:
cd auto-patcher
Code:
./batch.sh
Fourth step: Copy the rom you want to have patched into the auto-patcher folder.
Code:
./auto_patcher rom.zip
!! With this method, the patcher will use the rom detector and will build OpenPDroid patches. If you DO NOT want them, read the first page of the dev-thread. !!
Fifth step: Getting the files "out of" the VM.
- Easy way: Upload it into the/your cloud.
- Nearly as easy way: Use some filehost. (Since the files are about 6MB big, it's not even a hassle). Fast filehost: zippyshare
When your files finished the uploading, just use the link to the file in a qr-code generator, scan it with your device and download it. Easy!
Sixth step: BEFORE you flash the file, check the md5sum (in the VM and on your device!) how-to
If they match, you are good to go. Don't forget to make a nandroid backup! It's not needed, but hey, better safe than sorry!
I hope this helps If something is missing, tell me!
Cheers! :highfive:
PS: Due to lack of time, this "tutorial" is as short as possible and might lack a few explanations. (Hopefully not steps)
PPS: The only "tip" I have: use the tab-key for auto-complete So instead of writing "auto-patcher" just type "au" and then press tab. Saves you lots of time.
Edit1: Props to Mateorod and everybody over at the dev thread!
PDroid Patches for Samsung Galaxy Tab, HTC Desire & Desire S
Dear All
please find below some already PDroid-patched ROM links
Samsung Galaxy Tab 2 7.0 P3100, P3110 & P3113 (JB 4.3 Nightly & JB 4.2.2 CM 10.1.3 RELEASE)
[PDROID][GT-P31XX][2013-09-21][JB][4.3/4.2.2]PDroid: CM 10.2 Nightly & CM10.1.3 Rel. - see http://forum.xda-developers.com/showthread.php?t=2357514
HTC Desire
[ROM][Sept03][CM10.1] Chromium ROM | Build 10 | bravo - see http://forum.xda-developers.com/showthread.php?p=45441296#post45441296
[ROM/4.2.2] [June 03 2013] VJ CM10.1 | Jelly Bean 4.2.2 - v6.3 Stock/Sense/Data++ - see http://forum.xda-developers.com/showthread.php?p=43710438#post43710438
HTC Desire S
[ROM][08 AUG 13][4.2.2][UNOFFICIAL] CyanogenMod 10.1 - see http://forum.xda-developers.com/showthread.php?p=45441957#post45441957
With kind regards - Chris
http://pio-masaki.com/?dir=DroidDNA/Carbon
I'm in need of the 2nd from the bottom
9/22 for CDMA.
Awesome
Æaa°\,,/
takota6 said:
http://pio-masaki.com/?dir=DroidDNA/Carbon
I'm in need of the 2nd from the bottom
9/22 for CDMA.
Awesome
Æaa°\,,/
Click to expand...
Click to collapse
Since you did not specify which patch you want, you get OpenPDroid. All zip's are zipped with md5sum-files and the patch log.
Download link
Yeah I know, MEGA is pretty ****ty (down- and upstreams are crap) BUT it's more stable than other services.
Cheers!
PS: Please report back, if it works, and if it does, hit the thanks button, so a) I know and b) the thread doesn't get spammed. If something does not work as expected, please post a logcat in the dev thread, so it can get fixed.
Thank you
Well it didn't work, not with your doing but rather the Dev that built didn't put some vendor tree and so everyone is not able to boot that build.. I'll post back when I'm sure there a good build up.. Thanks
Æaa°\,,/
I'm back.. Heres a stable crAosp/ Cyanogen open pdroid please
http://forum.xda-developers.com/showthread.php?t=2417275
Direct Iink
http://www.mediafire.com/?6hblh4leblfc0lh
Thanks
Æaa°\,,/
Here's your patch takota6
takota6 said:
I'm back.. Heres a stable crAosp/ Cyanogen open pdroid please
http://forum.xda-developers.com/showthread.php?t=2417275
Direct Iink
http://www.mediafire.com/?6hblh4leblfc0lh
Thanks
Æaa°\,,/
Click to expand...
Click to collapse
Hi takota6!
Thanks for this clarification.
Please find attached the update file (patch) you need.
To restore to original (if you want to) you may use the attached "restore" file.
Kind regards from Switzerland - Chris
Hi guys !
As I'm still using my P769, and more and more old ROMs link are now dying (expiring), I find it very difficult to download ROM and tools for my phone.
So after spending a long time downloading all the currently still available ROMs and utilities, I've collected many ROMs and tools that you'll need if your old phone ever gone wrong and can't get support anywhere due to dead link.
I'm now reuploading all of it for longer storage time. Just in case someone might want to reuse the old phone for some other purposes.
Some ROMs and tools included :
AntonX's cm11 ROMS (most stable ROM I've used so far)
EdwinMoq CM12.1
EdwinMoq CM13.0
NAMELESS KITKAT 4.4.4
Bobz CWM Recovery Image (4.4.2)
TWRP 3.0.2.0
dsixda's Android Kitchen (Windows Version)
Phone's Driver, Source,...
(and many more).
[P769][ROMS and tools collection] Download Here (Update 24/11/2018) !
P/s : If anyone has some other ROMs or Tools for P769 that aren't here, feel free to send them to me and I'll add to the collection.
All credits go to their (ROMs and tools) respective owner. I do not own any thing/file etc. I just merely reuploaded it to different mirror.
If you're the owner of any file(s) here and don't like it being mirrored, please send me a PM for removal.
This is my first post, although I've read the rules thoroughly before posting, some might have slipped through. So if my post goes against the rules, please kindly let me know.
Thank you this is awesome!