Related
hey guys im a beginner and have no clue on how to build a rom for hd2, but would like to build one. can someone please help?1?
post your question regarding cooking in chef general..
dloopy said:
hey guys im a beginner and have no clue on how to build a rom for hd2, but would like to build one. can someone please help?1?
Click to expand...
Click to collapse
It will involve a lot of reading, i believe Dutty provides a kitchen in his roms so thats a start.
heres a great starter, lots of info about the kitchen structure in post 1, great starter guide in post 2
http://forum.xda-developers.com/showthread.php?t=628948
There's a lot involved when it comes to building a fast, stable, well-working ROM.
To get you started, I would recommend you download Ervius's Visual Kitchen based on Bepe's latest tools from HERE.
Second, download the latest stock ROM for your specific device. Mine is the T-Mobile HD2 so the stock ROM for that was where I started.
Extract the RUU_LEO_......exe using WinRAR. It can be found HERE. The free version will serve you well. Now open the Kitchen executable and use the option on the left to "extract" or dump the stock ROM that you just extracted from the exe. This will create the Kitchen for you. Or rather.. It will create a solid base foundation in which you can begin your modifications.
Before you'll be able to re-cook the ROM however, you will have to "recmod" the NTFConfig.dll module in Notification Enhancement. Failure to do this will result in a non-booting ROM. Don't ask why... I just know that this has to be done.
Once you do all of this, rebuild the ROM as stock and flash it to your phone(YOU MUST HAVE HARDSPL FIRST!!!!). If all goes well and the ROM boots, runs, and works like you expect a stock ROM to work, then you're free to start making all the changes you want.
TIP>> NEVER delete any package just because you are now using an updated version. Always keep the original just in case something doesn't work and always remember, keep 2 save files. One that you know for a fact will work if you re-cook and one that you experiment with.
As you get more comfortable with cooking ROMS, then you'll be able to update the SYS/XIP components more easily and so I suggest you stay away from that right off the get go. Get a good solid ROM first then play with those "extras".
One last thing - Familiarize yourself with the initflashfiles.dat file(open it with notepad) located in \OEM\"Device name"\0409\OEM_Lang_0409(I used 0409 as an example as this is WWE - you can use whatever language you like). This file controls all files and directories. Trust me, if you don't understand what I mean by that then open the file and you will.
If you have any other questions I'm sure there are many other chefs here who can offer you help and assistance.
Finally, be persistent! Don't let a buggy or non-booting ROM get you down. It can always be fixed! Just have confidence in your "techy side" and have patience. Know that the more you do it, the better at it you will get.
Good luck and happy building!!!
on rom building
[ ive been told that you can take a standard custom rom of your choice and just load the hd2 drivers to it is this true and where can i find the drivers to check what folder would i locate the
regards
---------- Post added at 12:14 PM ---------- Previous post was at 11:59 AM ----------
ross07 said:
[ ive been told that you can take a standard custom rom of your choice and just load the hd2 drivers to it is this true and where can i find the drivers to check what folder would i locate the
regards
Click to expand...
Click to collapse
or any standard drivers of what ever phone etc
Information:
PLEASE USE THE SEARCH FUNCTION. Your question has already been answered. Use Google or the search function above. The Google link is a template for quicker searching of this site.
NC=Nook Color
stable=latest stable rom from Cyanogemmod. Your go-to ROM if you just want a good daily driver and do not want to worry about things not working.
nightly=the latest and greatest. Please only try if you are able to troubleshoot, understand basic computer concepts, are not a N00b.
N00b=A word I hate and you should never use. Please do not say I'm a noob that needs help. Simply ask can I please have some help.
rooting=This is NOT FLASHING A ROM. It is the act of taking a stock rom and installing super user privileges. Installing CM7 is NOT ROOTING.
CM=Short for Cyanogenmod. The amazing team of developers that make what you're reading and wanting to do possible. Thank them often and donate any way you can (in help, money, coding).
OP=original post (post #1 in a thread)
OC=overclocked
HC=Honeycomb
AOSP=Android Open Source Project
SD=SecureDigital storage (that little card that goes in your NC)
eMMC=internal memory (the "hard drive" of your NC)
ROM=the "operating system"
kernel="Translater" between your ROM and the NC hardware. You need the overclocked one to overclock. Flash after a rom is flashed. THERE WILL BE NO OC KERNEL FOR THE DEFAULT CM ROM, EVER. OVERVOLTAGES OF THE KERNEL WILL NOT BE INCLUDED.
FC=force close, or when an app crashes
SOD=sleep of death. When the NC will not wake from sleep. You need to hard shutdown, then reboot to fix this.
PBD=premature battery death. When the battery shows 3x-20x% battery life left, but shuts down without warning. This has been linked to people who updated their bootloader without first flashing to 1.2 stock and letting the battery drain all the way down. This is being looked into. You need to plug in your NC if you experience this.
Click to expand...
Click to collapse
Kernel Issues with CM7 stable:
Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
Which OC kernel can I use with stable? The latest test (4/24) can be used. Both need the updater-script to be changed to ext4. Look here for information.
Please ensure you are running the latest Rom Manager and Clockwork Recovery. This will also fix problems with the kernel not loading and being stuck at "_ANDROID". Open market, download Rom Manager, install it, then flash the latest recovery for the NOOK COLOR (not NOOK COLOR (OLD), if that is still there). Now update your kernel/ROM.
I want to install an OC kernel to my SD rom! Head over here, Racks has all the kernels you could want.
Click to expand...
Click to collapse
CM7 Nightly Issues:
What overclocked kernel do I need?? The latest from dalingrin should do. Please read and understand (and use the search function) if you have questions/concerns. You're looking for the 5/23 .32 based kernel. Some may have issues with wifi, however.
I want to run this off of my SD card, not internal (eMMC) memory. Look at Racks for the answer.
Is it worth my time to upgrade to the latest nightly? You can check here. Changes specific to encore (the code name for the nook color) will have a slightly darker background, and if that is an issue you've had, it may be fixed now!
I want to run netflix on the NC! Download the netflix app and follow these instructions to have it run. If you don't know what it's asking to do, ask here!
I need the new uboot everyone is talking about! Get it here.
I want to try out USB Host support (VERY EXPERIMENTAL). Look here, read EVERYTHING, understand what you are doing!
Click to expand...
Click to collapse
Common Misconceptions/Questions:
Removing system apps (phone, mms, etc) will increase battery life! It has no effect. Stop it.
Using a task manager is a good idea in Android! That's not a good idea at all!
What do all these governors do/mean in setcpu/cyanogenmod performance settings? Look here for a great explanation. Also, DO NOT use setcpu PROFILES in CM7.
How do I install all these things? Check out eyeballer's awesome thread!
Click to expand...
Click to collapse
STOCK: NOOTER Distros:
For 1.0.1 ONLY. Look here.
For 1.1 ONLY. Look here.
For 1.2 ONLY. Look Here.
Click to expand...
Click to collapse
Honeycomb (Android 3.0):
Latest SDK (NOT AOSP) based ROM: Look here.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks for the OP's that saved me from retyping all the answers (Nemith, luciferii, and dalingrin, verygreen, and fattire (and others) that have made CM into the amazing piece of work it is.
Click to expand...
Click to collapse
Reserved for future awesomeness.
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
ADude said:
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
Click to expand...
Click to collapse
Thanks for the feedback.
I'm going to keep it updated as long as I can. Since I'm on here pretty consistantly. When I can't afford the time to do so, I will pull the information.
I know no one reads these types of threads, but I just had 200+ views in under and hour, so hopefully this solved a few issues without added noise to the real threads.
I think what you're looking to do is make a FAQ or guide or something. Maybe a better place where people can all collaborate (and correct any errors you have made, and I see a few minor ones) would be set up a FAQ page on nookdevs.com or something..
Also, it may be a better idea to organize the bits of information by category so people can quickly find it. Use as few words as you can in the first sentence so that people scanning for their issue don't have to read the whole thing...
Finally, it's "dalingrin"
Geez...if I had a dollar everytime I messed up dalingrin's spelling... :S
Yeah, I figured there would be a few half-truths in there from me not totally understanding what is going on as well as you guys, but feel free to PM or post on here where I can change stuff. I'll try to simplify it as well.
I just read over the OP and holy SH*T that is confusing, no offense. Here are some tips for writing helpful FAQs/Guides:
Space it out. Everything all clumped together in one block of text helps no one. Space it out (ie like this list).
Add titles or headers in between sections (this goes along with the first point) to clearly guide people to where they need to read. People want to read what is pertinent to them; not read an entire block of text and then try to figure out which applies to their case. Help others help themselves.
For all this CM7-specific information, add version numbers in front of bullet points (for the same reason as the previous point).
Ironically, none of your "Common Questions" are actually Questions. Questions end with a "?". What you have are "Common Answers". Insert questions before them so people can quickly decide if reading that particular bullet point is pertinent to them.
[5/10] Since this is all changing at such a ridiculously fast pace, add dates in front of bullet points where necessary (like at the beginning of this bullet point), so people can clearly tell what is outdated and what is new. I really wish Dal etc did this for his threads since a TON of the info in his threads are ridiculously out of date.
Learn to use the [ list ] and [ * ] tags -- quote post #10 of this thread to see what I mean.
Just some friendly tips for writing helpful guides
Also the particular answers in the OP are very specific to the Alpha Test Builds of the last few days.
Those builds, like dalingrin's, are accompanied by FAQs right where the download link is.
The problem is that people talk about these things elsewhere, and even worse, put up mirror links without the FAQ - which just happened with the new Beta .32 build - one guy complained about not being able to download it because everyone else was hitting the same site at the same moment - so a mirror was posted later in the thread without dalingrin's FAQ.
Someone made a wise comment recently that people who cannot find the already posted detailed information, should not be installing these test builds in the first place, as they don't know what they are doing (and they never report enough detail in their bug feedback - such as exactly which build they have installed).
ADude said:
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
Click to expand...
Click to collapse
Geez, Dude, you're harshing my mellow. At least Ace is trying to be helpful and doing something positive. Your negative attitude isn't helping anyone.
I for one, would like to say "thank you" to Ace. The OP couldn't have come at a better time as I was a little confused about the new 7.1.0 ROM and "2.6.32" thread was not helping at all. Keep up the good work!
Personally, I would love to see something like this:
7.0.2
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
7.0.3
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Nightly ##
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Nightly ##
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Other Builds etc
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Miscellaneous Questions Not Specific to a Particular Build
[5/10] How do I do X?
[5/10] Where do I get Gapps?
[5/10] Additional Questions
[5/10] Additional Questions
Unfortunately, I have a very limited understanding of all the stuff that is currently happening day-to-day. I run only stables (currently on 7.0.2 flashed weeks ago) for fear that I might mess up my NC because I may have missed a key detail in post #1238 in thread X, Y, or Z. A centralized thread with all this information run by someone dedicated to updating it daily would be a great help to everyone. People like Dal and other developers are busy developing, and rightfully so
Wow...
I dig it!
I'll see if I can start up something that in depth in a bit here...
When updating from 7.0.2 to 7.0.3 are you suppose to use rom manager? Or download the file from PC then transfer it over to SD and use recovery mode to update? Also your suppose to use titanium to back up apps and data only correct just incase. But as far as updating wipe cache and dalvik.... I just want to make sure I'm doing it correct that way all my apps stay. Fyi I'm running cm7 of internal
Actually, it occurred to me that a FAQ thread like this should be in "Nook General Forum", but that your OP, with all the information about nightlies and so on, should be posted to the end of the CM7 User General Discussion thread in this Forum.
That thread is where all these questions come up.
jzibit17 said:
When updating from 7.0.2 to 7.0.3 are you suppose to use rom manager? Or download the file from PC then transfer it over to SD and use recovery mode to update? Also your suppose to use titanium to back up apps and data only correct just incase. But as far as updating wipe cache and dalvik.... I just want to make sure I'm doing it correct that way all my apps stay. Fyi I'm running cm7 of internal
Click to expand...
Click to collapse
Personally, I find that ROM manager is another program that can have bugs, so I don't use it.
I just put the file on my SD card wirelessly using "Samba Filesharing App" (free in the market), and then use Clockworkmod Recovery to install it.
It looks like with many recent changes, it helps to first do "wipe system" and "wipe cache" before installing the new file.
Since our personal stuff is in "data", then I do not wipe that.
I also find that the "nandroid backup" on Clockworkmod Recovery is more reliable than Titanium Backup (same comment as for ROM manager). If you do a complete nandroid backup and then a complete recovery, it brings back everything - all the partitions - so it is a great thing to do when everything is working nicely.
I can't seem to find the latest version of Gapps that you list. I checked throughout the site listed and only see for GB up to 03072011. Did it get deleted?
psychoace said:
I can't seem to find the latest version of Gapps that you list. I checked throughout the site listed and only see for GB up to 03072011. Did it get deleted?
Click to expand...
Click to collapse
Looks like it was just deleted. I'll keep tabs on it.
fattire said:
I think what you're looking to do is make a FAQ or guide or something. Maybe a better place where people can all collaborate (and correct any errors you have made, and I see a few minor ones) would be set up a FAQ page on nookdevs.com or something..
Also, it may be a better idea to organize the bits of information by category so people can quickly find it. Use as few words as you can in the first sentence so that people scanning for their issue don't have to read the whole thing...
Finally, it's "dalingrin"
Click to expand...
Click to collapse
Agreed. Forums for information dissemination are just ****ty beyond belief. We, the NC/xda community, need to either start taking the NC wiki seriously, or fenagle the owners of this fine establishment into upgrading to something more collaborative. No offense, but the only thing worse than forums for a large community is an email mailing list. shudder ... lol
Seriously. Forums are areas for discussion. Not Q&A.
ace7196 said:
Looks like it was just deleted. I'll keep tabs on it.
Click to expand...
Click to collapse
You can google the file name to find it hosted elsewhere
I bought my Nook last week and since then i've been trying to learn how to tinker with custom roms and kernels but this subforum is total chaotic and newbie-unfriendly.
We (new users) need a wiki to get some basic knowledge about modding.9
All that stuff is scattered and buried in subtopics, I have took a lot of time just to install CWM on eMMC.
Now I'm running 1.2 rooted on emmc and CM7 nightly on SD, I couldn't get dual boot working on EMMC nor SD.
hirano said:
I bought my Nook last week and since then i've been trying to learn how to tinker with custom roms and kernels but this subforum is total chaotic and newbie-unfriendly.
We (new users) need a wiki to get some basic knowledge about modding.9
All that stuff is scattered and buried in subtopics, I have took a lot of time just to install CWM on eMMC.
Now I'm running 1.2 rooted on emmc and CM7 nightly on SD, I couldn't get dual boot working on EMMC nor SD.
Click to expand...
Click to collapse
There is a Wiki stickied to the 1st page of the general section of the Nook Color Forum......http://forum.xda-developers.com/showthread.php?t=890549.
Ace created this thread in response to a rash of redundant questions.
Attention all rom authors:
Dell Streak Custom Rom List - XDA Wiki
I attempt to keep it as up to date as possible, but as I dont download every single rom I can only work off of what's written in the postings.
Please try and keep your own personal roms up to date,
Correct method of doing so:
Make a new entry to place your rom in, use any of the other ones as a template
Do not delete/overwrite old entries, always make a new one
Date format is always in Month-Day-Year since that's how I had originally organized them (and for no other reason)
If you're really unsure how, you can reply to this thread and i'll add it in if i havnt already
Base rom is exactly that, if it's based on SD, list that it is, and which one.
If there's an error or omission feel free to fix it, but preferably only for your own roms unless you're 100% sure that there's a mistake in someone else's rom
If there are multiple versions, only list the primary one, minor varients should remain on the forum post
If a link is broken and not expected to be fixed, go ahead and remove the link
Do not add guides or other links to it, it should only contain info on the rom itself and download links
Thanks for the reminder. I will modify the Wiki page for any of my further releases. I wasn't aware I could add to it.
It's a wiki, anyone with a forum account can use it (they use the same login info)
I'll be keeping an eye on it regardless of who adds to it (for accuracy and formatting),
But it helps everyone if the rom authors add it themselves first, I dont add things immediately, it could be up to a day or 3 late
Lol, I when I checked the title of this post I had to do a double take. I first saw "Add your *mom* to the wiki list" I was like... Nice....
nvm
Redmi note 3 ROM Uploaders please read!
I have been flashing stock roms for a few years now and I have noticed with this device that many of the uploaders are not providing all the details just some of the following:
Detailed description
Is bootloader to be unlocked first
Is a custom recovery needed
Full instructions on how to install
Screenshots
bug list
Which Gapps package to use
Please provide all (the above) the neccessary information so we can make the decision is this ROM good for us to flash on our phones.
There needs to be a template for ROM postings so it can be easy for the end users. (Forum moderators will know the formula so I ask ye guys to sticky a template)
Thank you (ordered mine 3 days ago come on gearbest I wants my precioussss)
rslatara said:
Redmi note 3 ROM Uploaders please read!
I have been flashing stock roms for a few years now and I have noticed with this device that many of the uploaders are not providing all the details just some of the following:
Detailed description
Is bootloader to be unlocked first
Is a custom recovery needed
Full instructions on how to install
Screenshots
bug list
Which Gapps package to use
Please provide all (the above) the neccessary information so we can make the decision is this ROM good for us to flash on our phones.
There needs to be a template for ROM postings so it can be easy for the end users. (Forum moderators will know the formula so I ask ye guys to sticky a template)
Thank you (ordered mine 3 days ago come on gearbest I wants my precioussss)
Click to expand...
Click to collapse
First thing, its not stock rom, its custom rom.
Second, the developers are not being paid, and thus whatever thay are doing, just accept it and ask for help, not post post like this to command them to list things that are obviously common sense.
1. CM13 Nightly, this 2 words give enough description, what more do you need. In this time, if you don't know what cm13 is then don't buy an android. Nightly means that there are still bugs, both minor and major, and sometimes it means that there are some things broken too. The devs also list whats working or whats not. They can't list every single thing.
2. You are flashing custom rom, thus you must have custom recovery like twrp, in order to install it you must first unlock your bootloader. If you have custom recovery, then it doesn't matter whether your bootloader is unlocked or not.
3. Did you really just asked if custom recovery is needed, are you a fool or what. Let me make this clear, if you want to flash a rom, how are you supports to so without a custom recovery. Stock recovery can't flash rom, neither it can make backup, restore backup and lots of things. The most basic thing to do even before rooting is to flash a custom recovery. Without custom recovery you can't even properly root. Well you can root with some apps, but custom recovery makes it easier, just download supersu and flash it with recovery.
4. Whats there to know. If you have custom recovery, then first create a backup. Almost every thread that i have ever read on xda, it is stated every where to always make a backup before doing anything, even rooting. Then, wipe data cache dalvik system, and then flash the zip file. After that if you wish flash the gapps.
5. What do you need screenshot for. Haven't you ever saw CM13 or ressurection remix. Just google it. they are not obliged to post it here for your convenience.
6. They do provide bugs, whats working or what not. And its not like they know a bug and haven't told other about it. They, in most cases don't know how many bugs there are, the other users tell them the bugs and they fix it.
7. Why would they tell you which gapps package to use. Do they work for google. Anyway, just google gapps, your rom version, ie cm12 or cm13, you mob architecture, arm64 or arm32 or whatever, and just download it. There is no geek stuff behind it that you can't do it yourself.
And finally, you are not paying them do anything, they are doing this because they like doing this. They are not even getting paid by this. So you ordering them to these things which you can do yourself after some googling and using your brain a bit, is just unjust. Just accept what they are doing, thank them, enjoy the rom, and report the bugs, etc etc, and have fun.
archit.bajpai.ab said:
First thing, its not stock rom, its custom rom.
Second, the developers are not being paid, and thus whatever thay are doing, just accept it and ask for help, not post post like this to command them to list things that are obviously common sense.
1. CM13 Nightly, this 2 words give enough description, what more do you need. In this time, if you don't know what cm13 is then don't buy an android. Nightly means that there are still bugs, both minor and major, and sometimes it means that there are some things broken too. The devs also list whats working or whats not. They can't list every single thing.
2. You are flashing custom rom, thus you must have custom recovery like twrp, in order to install it you must first unlock your bootloader. If you have custom recovery, then it doesn't matter whether your bootloader is unlocked or not.
3. Did you really just asked if custom recovery is needed, are you a fool or what. Let me make this clear, if you want to flash a rom, how are you supports to so without a custom recovery. Stock recovery can't flash rom, neither it can make backup, restore backup and lots of things. The most basic thing to do even before rooting is to flash a custom recovery. Without custom recovery you can't even properly root. Well you can root with some apps, but custom recovery makes it easier, just download supersu and flash it with recovery.
4. Whats there to know. If you have custom recovery, then first create a backup. Almost every thread that i have ever read on xda, it is stated every where to always make a backup before doing anything, even rooting. Then, wipe data cache dalvik system, and then flash the zip file. After that if you wish flash the gapps.
5. What do you need screenshot for. Haven't you ever saw CM13 or ressurection remix. Just google it. they are not obliged to post it here for your convenience.
6. They do provide bugs, whats working or what not. And its not like they know a bug and haven't told other about it. They, in most cases don't know how many bugs there are, the other users tell them the bugs and they fix it.
7. Why would they tell you which gapps package to use. Do they work for google. Anyway, just google gapps, your rom version, ie cm12 or cm13, you mob architecture, arm64 or arm32 or whatever, and just download it. There is no geek stuff behind it that you can't do it yourself.
And finally, you are not paying them do anything, they are doing this because they like doing this. They are not even getting paid by this. So you ordering them to these things which you can do yourself after some googling and using your brain a bit, is just unjust. Just accept what they are doing, thank them, enjoy the rom, and report the bugs, etc etc, and have fun.
Click to expand...
Click to collapse
1. I know what CM is this is about description not quick copy and pastes from another website.
2. Some modified roms can be ran from the stock recovery.
3. You are a fool this is information for the end user I will slap you with a fresh wet fish!
4. Information is key.
5. Screenshots show people what they are flashing very helpful to the end user
6. They don't always bub!
7. Again inofrmation helps to clarify lot's of things.
Not all the guys that post are the actual devs THAT DO IT RIGHT, some are just bad copy paste jobs coz they wanna be cool n **** and don't Fu(&ing tell me not use andorid you little pretend dev snot! :victory:
rslatara said:
1. I know what CM is this is about description not quick copy and pastes from another website.
2. Some modified roms can be ran from the stock recovery.
3. You are a fool this is information for the end user I will slap you with a fresh wet fish!
4. Information is key.
5. Screenshots show people what they are flashing very helpful to the end user
6. They don't always bub!
7. Again inofrmation helps to clarify lot's of things.
Not all the guys that post are the actual devs THAT DO IT RIGHT, some are just bad copy paste jobs coz they wanna be cool n **** and don't Fu(&ing tell me not use andorid you little pretend dev snot! :victory:
Click to expand...
Click to collapse
If you are using a 32bit windows, then do you ask others which application to install, 32bit or 64bit. Man you are a joke, it's not information, its common sense. information is which partition is used for what purpose. How to restore imei. How to unlock lte band, not which gapps to flash. And there is no stock recovery out ther which flash custom roms. The only roms you can flash with stock recovery are ota.
archit.bajpai.ab said:
If you are using a 32bit windows, then do you ask others which application to install, 32bit or 64bit. Man you are a joke, it's not information, its common sense. information is which partition is used for what purpose. How to restore imei. How to unlock lte band, not which gapps to flash. And there is no stock recovery out ther which flash custom roms. The only roms you can flash with stock recovery are ota.
Click to expand...
Click to collapse
Hey I am just a certified IT Technician working for the IT department of a mutlinational company what would I know and I spit on x86 always have..even my windows vista was x64 boi!!!!
rslatara said:
Hey I am just a certified IT Technician working for the IT department of a mutlinational company what would I know and I spit on x86 always have..even my windows vista was x64 boi!!!!
Click to expand...
Click to collapse
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
archit.bajpai.ab said:
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
Click to expand...
Click to collapse
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little and it's kinda lazy on the posters part.
That is all. I ain't a programmer (although i touched on some c++) but I ain't a noob just like details and not everyone is well informed and there a newbies to flashing roms it's to help them too not brick a device.
archit.bajpai.ab said:
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
Click to expand...
Click to collapse
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little info and it's kinda lazy on the posters part.
I ain't a programmer (although i touched on some c++) but I ain't a noob, I just like details and not everyone is well informed and there a newbies to flashing roms it's to help them to not brick a device.
From what I see it's mostly non devs just copy paste guys who are doing it.
Does it hurt to have a small guide or at least the fundemntals of requrements for the installation of each rom?
Waiting on my redmi still order prcessing, hurry gearbest hurry I am back on my g510 as my asus went for a swim in my tiolet!
rslatara said:
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little and it's kinda lazy on the posters part.
That is all. I ain't a programmer (although i touched on some c++) but I ain't a noob just like details and not everyone is well informed and there a newbies to flashing roms it's to help them too not brick a device.
Click to expand...
Click to collapse
Nice idea, looks like there's no room for a newbie on XDA anumore (in remembrance of XDA 2012).
Sent from my Redmi Note 3 using XDA Labs
Hi all,
With the risk of this being called a duplicate thread I just want to clarify that I'm in no way asking to port something for me, and I've read the 2 similar threads around, and felt like this should have it's own place.
So, straight to the point, I've been looking to get involved with android porting, and since LOS and AOKP for our device haven't quite filled my cup I was thinking of trying to port something else (trying to not get into much detail here )
Moving on, after searching around XDA and everywhere else, I've found a tuto or two where the process of porting was explained, and being an average user, I went to grab a "Base ROM", (thought the LOS/Stock ones would do, downloaded both)
To my surprise, files mentioned in the tutorials (framework-res.apk, framework.jar, ...) are nowhere to be found.
Finally the question, this just to save me from a reflash,
Am I supposed to install the "Base ROM" to dump /system to my PC?
Or am I perhaps misunderstanding something?
----
PSA: I'll probably find it difficult to get time to work on this (school stuffs) so even if I decide to go on with it, it might take a good while till something comes up.
Also, if there's someone with some experience in porting who'd be so kind to give me some pointers or show some availability to help with bug fixing/porting (not asking for labor, just explanations, in case I need 'em), please PM
Thanks, and sorry for the long post
b0taSs said:
Hi all,
With the risk of this being called a duplicate thread I just want to clarify that I'm in no way asking to port something for me, and I've read the 2 similar threads around, and felt like this should have it's own place.
So, straight to the point, I've been looking to get involved with android porting, and since LOS and AOKP for our device haven't quite filled my cup I was thinking of trying to port something else (trying to not get into much detail here )
Moving on, after searching around XDA and everywhere else, I've found a tuto or two where the process of porting was explained, and being an average user, I went to grab a "Base ROM", (thought the LOS/Stock ones would do, downloaded both)
To my surprise, files mentioned in the tutorials (framework-res.apk, framework.jar, ...) are nowhere to be found.
Finally the question, this just to save me from a reflash,
Am I supposed to install the "Base ROM" to dump /system to my PC?
Or am I perhaps misunderstanding something?
----
PSA: I'll probably find it difficult to get time to work on this (school stuffs) so even if I decide to go on with it, it might take a good while till something comes up.
Also, if there's someone with some experience in porting who'd be so kind to give me some pointers or show some availability to help with bug fixing/porting (not asking for labor, just explanations, in case I need 'em), please PM
Thanks, and sorry for the long post
Click to expand...
Click to collapse
i wouldnt even try to port, its just confusing, files missing, preloader updates which makes you think which one to use, its all really just a mess, you will have better chance of getting something if you build from source, just fork our device, kernel and vendor trees and download a custom rom source of your choosing and build it, i wont say step by step, but i recommend that to download the vendor, device and kernel sources you make the local_manifest.xml so that when you do repo sync it downloads those sources aswell
Ruben Craveiro said:
i wouldnt even try to port, its just confusing, files missing, preloader updates which makes you think which one to use, its all really just a mess, you will have better chance of getting something if you build from source, just fork our device, kernel and vendor trees and download a custom rom source of your choosing and build it, i wont say step by step, but i recommend that to download the vendor, device and kernel sources you make the local_manifest.xml so that when you do repo sync it downloads those sources aswell
Click to expand...
Click to collapse
And here I thought porting would be easier, but yeah, now that you mention that.. :silly:
Aw well, thanks mate :good: