The following is a reasonable format that is suggested when posting a ROM. We expect your ROM post to look somewhat professional and easy to understand.
1. Requirements (bootloader version, radio version etc)
2. State that it's from an official manufacturer or source base (stock ROM or AOSP-like source).
3. Thread shows a clear overview of changes made, in a way that users can see what has changed when new versions are updated.
4. Explicit installation instructions.
5. ROMs need to identify what kernel they are using. If 100% stock then they must state that.
6. If custom kernel you must provide a link to the kernel source. This is required by GPL. Stock (untouched) kernels can link to the manufacturers source (if available). If you use somebody's kernel, link to their source.
7. At least 2-4 images (screen-shots) 1 of which must be of system/device info. Do not use photo hosts thay deluge users with ads and popups when they select the image. You can either attach the images, or use a hosting service such as photo-bucket for example.
8. Links to downloads. A link to a direct download is preferred. Linking to external website home pages are not allowed, it must be linked to the Downloads page. Also use of "ad-driven" (adfly for example) or "commercial" sites are mostly not allowed. Registration on some sites "may" be allowed, but is subject to XDA Moderation approval.
9. Credits for sources used. Very important.
10. Keep your "asking for donations to a limit. You already have a "Donate" button.
Simply posting a link to some download site "here it is, download it", is not allowed.
Any questions, please feel free to contact any moderator.
Thank You
Moderation Team
Related
Why use a crappy website to host your ROM when you can create a .torrent from it instead and allow it to be seeded by numerous sources so it stays active?
Here is how I create .torrent files with Windows...
1) Download and install the 2.0.3 version of uTorrent.
2) Open uTorrent after it installs and set it up. I would recommend NOT updating to the latest version.
3) Click the icon with the magic wand on it to create a .torrent.
4) I would suggest creating a folder with the name of your ROM then place the ROM .zip into that folder.
5) Click on the ADD DIRECTORY button and select the folder you created with the ROM .zip in it.
6) Use these trackers with line breaks between them...
udp://tracker.ccc.de:80
udp://tracker.istole.it:80
udp://tracker.openbittorrent.com:80
udp://tracker.publicbt.com:80
7) Click the CREATE AND SAVE AS... button and name the .torrent preferably with the folder name you used.
8) Leave your uTorrent on so you (Seed) can share your ROM with people (Peers). It is nice if those peers leave their .torrent program on so they can seed as well. The more seeders the better!
9) Upload the .torrent file of your ROM to some website and post the link to the .torrent in your ROM post.
Now people can download it with whatever .torrent program they use and get it on their phone.
Attached are a couple of .torrents to get either Liquid or RedHead for the Droid Bionic...
..
MarkTee said:
I think the main reason is that it's a lot easier to edit a post for updates than create a new torrent each time. Torrents would lead to even greater fragmentation; tons of users would start contacting devs for help with outdated versions.
Click to expand...
Click to collapse
I think torrents are a great options they really are!
The developers would only have to post the torrent for the newest version, it would take no more work then uploading it to a site and posting
MarkTee said:
I think the main reason is that it's a lot easier to edit a post for updates than create a new torrent each time. Torrents would lead to even greater fragmentation; tons of users would start contacting devs for help with outdated versions.
Click to expand...
Click to collapse
Fragmentation is not an issue especially when the user's torrent client is set to pre-allocate space. Users with older versions of the ROM would hopefully be wise enough to figure out the developer has released a newer version especially if the user is smart enough to check the official ROM thread for updates and the developer takes the few seconds of time needed to update the link/attachment for the torrent.
zacthespack said:
I think torrents are a great options they really are!
The developers would only have to post the torrent for the newest version, it would take no more work then uploading it to a site and posting
Click to expand...
Click to collapse
EXACTLY! And with hopefully hundreds of users sharing the ROM via torrent, the ROM will never be unavailable due to website problems.
Having the ROM on torrent would be so much more helpful in downloading. Everyone would be able to seed it =P
I've been banging my head about this one for a couple of years across several Windows installations including 7, 8, 8.1 and 10 at home on two PCs and Windows XP (I think) and 7 at work, on multiple laptops, and taking place in both Chrome and Internet Explorer 9, 10 and 11. I have Edge uninstalled in Windows 10 so I can't test that at the moment. I forget what result I had with Firefox, but I'll probably reinstall it to find out.
It's most annoying when editing an OP but whether with an OP or regular post, I've occasionally worked around the problem by keeping a "master" copy of the post in Notepad++ on Windows, editing that, then copying and pasting that to my post edit. This only works when I either already have a current master copy in Notepad++, or can manage to retrieve an uncorrupted copy which is sometimes difficult when the problem happens in all my currently installed programs.
The problem also occurs when editing a DevDB project in both Chrome and Internet Explorer.
The problem happens most frequently in Chrome so my most common solution was to temporarily switch to Internet Explorer, but right now even IE is giving the same result.
I'm very good at searching and I've tried searching both Google and XDA with different sets of search terms and I don't find anything even remotely similar.
For example, the following correct text:
Code:
First, the thanks:
[user=2645378]@AndroidFileHost[/user] for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
[user=5418208]@KyPbP[/user] for [URL="http://forum.xda-developers.com/showpost.php?p=60851710&postcount=108"]letting us know it's availability and giving the link to download the VK810 35A_08 KDZ[/URL].
[user=5868929]@hsbadr[/user] for giving me permission to kang his [URL="http://forum.xda-developers.com/showpost.php?p=56005236&postcount=1"]Verizon G3 VS985 JasmineROM 7.0[/URL] update script for this use.
[user=229404]@rant[/user] for giving a [URL="http://forum.xda-developers.com/showpost.php?p=60857092&postcount=1"]link to the official Verizon PDF detailing this release[/URL].
[user=631273]@Chainfire[/user] for [URL="http://forum.xda-developers.com/showthread.php?t=1538053"]SuperSU[/URL]!
[user=5022682]@Hnk1[/user] for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading. His two updated guides:[INDENT][URL="http://forum.xda-developers.com/lg-g-pad-83/general/vk810-altev-complete-root-recovery-t3108260"][VK810][Altev][Guides][Information] Root Recovery Repair [4.4.2][5.02][/URL]
[URL="http://forum.xda-developers.com/lg-g-pad-83/general/vk810-downgrade-required-t3116336"][VK810][ROOT][Lollipop][5.02] No downgrade required[/URL][/INDENT]
[SIZE=5][COLOR=Red]Debloat scripts that you can flash in CWM (ClockworkMod Recovery) after flashing the ROM and SuperSU.zip are located in the [URL=http://forum.xda-developers.com/showpost.php?p=60861201&postcount=2]second post[/URL].[/COLOR][/SIZE]
after clicking the Edit button becomes:
Code:
First, the thanks:
[user=2645378]@AndroidFileHost[/user] for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
[user=5418208]@KyPbP[/user] for [URL=" us know it's availability and giving the link to download the VK810 35A_08 KDZ[/URL].
[user=5868929]@hsbadr[/user] for giving me permission to kang his [URL=" G3 VS985 JasmineROM 7.0[/URL] update script for this use.
[user=229404]@rant[/user] for giving a [URL=" to the official Verizon PDF detailing this release[/URL].
[user=631273]@Chainfire[/user] for [URL="[/URL]!
[user=5022682]@Hnk1[/user] for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading. His two updated guides:[INDENT][URL="] Root Recovery Repair [4.4.2][5.02][/URL]
[URL="] No downgrade required[/URL][/INDENT]
[SIZE=5][COLOR=Red]Debloat scripts that you can flash in TWRP after flashing the ROM and SuperSU.zip are located in the [URL= post[/URL].[/COLOR][/SIZE]
Notice the URLs are missing, plus some other words after the URL such as specifically:
Code:
[user=5418208]@KyPbP[/user] for [URL="http://forum.xda-developers.com/showpost.php?p=60851710&postcount=108"]letting us know it's availability and giving the link to download the VK810 35A_08 KDZ[/URL]
becoming:
Code:
[user=5418208]@KyPbP[/user] for [URL=" us know it's availability and giving the link to download the VK810 35A_08 KDZ[/URL].
If this were only happening in Chrome, I would suspect an extension. I've had the problem happen on completely new and clean installations of Windows as well.
Thanks in advance for any advice.
FYI now really weird, even this post didn't come out right on the initial posting. The information attempts to be there when I edit it (additional CODE boxes, there are clearly four total CODE boxes with both beginning and ending CODE tags when I posted and when I edit the post), but as usual, URLs and other information is missing from my examples. I'll probably be forced to give screenshots when I have time later.
MOD EDIT: removed
Features :
* Nearly 94 Languages and they won't be removed after factory reset.
* Hotspot fixed (other apps can now enable hotspot).
* Network fixed (GSM - CDMA - LTE).
* USSD fixed.
* Removed most of Verizon bloatwares .
* Phone will automatically read contacts from SIM.
* Mobile Data icon added to Statues Bar.
* Removed Verizon Logo.
* Fingerprint is 100% working fine.
* FlashFire flashable
Instructions :
1. Flash G920VVRU4BOK7 Firmware
2. Download the Link given above and doube click to extract
3. Copy SM-G920V_7.0_RD2_Multi-Language_FlashFire.tar to Phone's Storage
4. There is SM-G920V_5.1.1_Automated_Root Folder, Inside it run SM-G920V_5.1.1_OK7_Root.cmd
4. Phone will be rooted and FlashFire will be installed open it and grant permission, Press + button and select the SM-G920V_7.0_RD2_Multi-Language_FlashFire.tar file
5. In EverRoot option utick all and in Reboot option select Download
6. After everything is finished phone will reboot into download mode and flash SM-G920V_7.0_RD2_Protected_Partitions_Odin.tar in AP slot in Odin. And do a factory reset.
Wait for about 5 minutes and it should boot and there you go,
Have a nice day
FAQs :
Where is root ?
Idk, I think there is already a post about SM-G920V 7.0 Root on XDA, search and you might find interesting stuffs .
Why there are some Verizon apps still remain ?
I used some clumsy ways to patch the system and removed as many Verizon apps as possible and decided to share it with XDA.
Self-promotion is forbidden on XDA:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Thread closed, links removed. If you will be ready to provide proper download links, feel free to write me a PM and I will reopen your thread.
OxygenOS Open Beta 17 (OnePlus 7)
Changelog:
System
Newly added user assistance feature to help user master usage skills quickly(Route: Settings>OnePlus Tips&Help)
Fixed the abnormal error occured in Lockbox
Fixed the auto-start issue with QXDM logs after reboot
Optimized user experience with long screenshot in some scenarios
Updated Android security patch to 2020.08
Messages
Optimized the categorization, messages of the same contact now merged in one card（India only）
File Manager
Fixed the issue that File Manager did not display some downloaded documents of apps
Network
Improved the stability of Wi-Fi transfers
OxygenOS Open Beta 17 (OnePlus 7)
2.2 GB official download link:
https://otafsg1.h2os.com/patch/amazone2/GLO/OnePlus7Oxygen/OnePlus7Oxygen_13.W.41_GLO_041_2007291632/OnePlus7Oxygen_13.W.41_OTA_041_all_2007291632_938c0a4f529d725.zip
Local Upgrade OnePlus 7
1.) Download zip file OxygenOS Open Beta 17 2.2 GB from Official server
and copy it to the root of the internal memory
(i.e., not in a folder such as Downloads, for example).
2.) Go to Settings> System> System Updates> Click the gear at the top right>
Local Upgrade> Click on the appropriate installation package> Update
3.) After the update is completed, click Restart
4.) The update was successful.
Note If you do not see the firmware file, then check the file extension should be .zip
(if you have .zip.jar just rename it by deleting .jar)
laikexpert said:
...
Click to expand...
Click to collapse
@laikexpert THREAD CLOSED as a subject matter related thread already exists, which covers every update: https://forum.xda-developers.com/oneplus-7/how-to/oneplus-7-repo-oxygen-os-builds-t3937152
In this post the OpenBeta 17 has been reported before you created your thread.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
OK, so you messed up your device real bad trying to do something and it needs a full flash of the original firmware. Well, lucky you I am here to help you in your journey back to your device's roots, the good old days where everything worked just as it should.
Now, I am gonna be very honest with you about some stuff:
- This is my first XDA post and I really wish it were better formatted;
- English is not my first language, so I really hope this is understandable to everyone; (feel free to correct me)
- I have 0 responsability for whatever you do to your device, so if you f*ck your device up so bad it doesn't even turns on anymore, its not my fault.
!!!!!!! IMPORTANT !!!!!!!
The firmware provided here works ONLY for MOTO E6 PLAY, it WONT WORK with ANY variation. DONT try to install it in any device other than the bali, and if you do, DO NOT BLAME YOUR DEVICE LOSS IN ANYBODY BUT YOURSELF.
Well, that said, the procedure:
Edit:
Apparently, the Bali itself comes in more than one version (not impressive, a detail I definitely should have paid more attention to). There are the
XT2029-1, XT2029-2 and XT2029-3. In the device's configuration app, under System, in Regulatory Information, you can find which one is yours.
First, download the file correspondent to your version from here: https://motostockrom.com/?s=XT2029
Notice that the files that appear for download first aren't the most recent ones. To be certain that you downloaded the most recent build to your version, check it in the ZIP's filename, e.g.: Motorola_Moto_E6_Play_XT2029-3_MT6739_POA29.550-81_2003_20200311_9.0.zip (date is in the YYYY/MM/DD format)
From now on, I'll be making a lot of references to the downloaded file's directory structure. To mitigate any possibility of confusion, I'll be referencing the root of the directory as / and any sub-folder as /Folder/
After that, extract the files from the ZIP. Looking inside /, you'll find the firmware files under /Firmware/ and links to pretty much all you need to flash the original firmware, bootloader, recovery, and even instructions to recover the device's IMEI.
Our device has a MediaTek chipset, so SP Flash Tool is almost the sole thing that is needed to recover a soft broken device (Only problem would be if the devices scatter file weren't available, but fortunately this isn't the case).
Inside the /Driver/ folder, you'll see links to necessary drivers for the computer to correctly identify the device. Follow the links, download and install the drivers.
Refer to the /SP Flash Tool/ directory. Follow the link inside it, download the latest version of the tool for your computer's OS (Windows/Linux);
Now refer to the How To Flash link in /, be it the (Tutorial) or (Video) one, which suits you better. Follow the instructions very carefully and thoroughly and you shouldn't have any major issues flashing the firmware. After the flash is done and the device reboots, congratulations! You've made it! :victory::highfive:
DISCLAIMER:
I like to give credit where its due. Inside /, you'll find a credits file. That website isn't mine, and the development of the file and the tutorial was completely made by them, so all the credits go to the proper owners of the website. I am just sharing it here for the benefit of the community.
Well, if you have any questions, feel free to post a response. I am no Android OS developer myself (though I do develop some other stuff - Java and Python mainly - and am a OS administration and troubleshooting geek, Android is still very shady and very out of my league for me), but I'll be happy to help with anything I can.
Happy Hacking!