Related
Hey guys just wanted to share this with you. I am working with Team Win to get a touch recovery on the A500. So far is still inop, but progress is bring made. We are gonna give another go tomorrow so wish us luck. Will keep you all posted.
Updates
1-5-12: So we are finding the using the tablet interface makes the recovery too large for our recovery partition. Team Win is probably going to have to build the recovery without an interface and then I will create a flashable zip that will flash the recovery as well as place a ui.zip on the external sdcard under twrp/theme(we can then just replace that ui.zip for different themes that come out, got a cool ICS one in mind already). The battery precentage is working but we are still working on the touch screen. New test build coming today and will have active logging enabled so that we can see more of what is happening, if touch is being recongnized but TWRP 2.0 is just not reacting to it. It's coming along though.
1-6-12: SO we got TWRP 2.0 up and running for the most part. Touch screen works and most all functions work. Get backup failures and is not sized properly but we are really, really close. Did install a rom and booted just fine. Release will be real soon, possible monday. Still have to get the resolution figured out as well, but what we have so far is very usable.
2-17.. So work on this has slowed way down due to dev on teamwin side has other projects that he is working on that is more important to him(which there is no problem with that, would just like to get this project completely going). But TWRP 2.0 has gone completely opensource. So just wondering if we can tackle this and get it up and running. We are on #twrp on freenode irc usually everyday M-F around 11am-1pm Mountain Time. If you are able and willing to help, please come and give us some fresh ideas.
3-8. Everything is working and is ready for release very soon. Some final testing and will be release. Data/media fixed and flexrom fixed. PLEASE HOLD!!
3-13. New features being added. We will have the ability to toggle back and forth between internal and external for backup location. Doing some code clean up and making sure all features are working properly. Have used it to install many roms/flashes and have yet to have any issues. It's coming along nicely. Huge thanks to Dees_Troy on TeamWin for his work on this. You da man!
I run TWRP 2.0 on my Evo 3D. Would love to see it on my A500. So much better then all the button presses to navigate through the recovery menu.
I would love to see TWRP 2.0 on the A500. I have it on my Sensation and think it is some of the absolute best development to come out of the Android development community recently. Best of luck guys.
Muahahaha. Can't wait!!!
Sent from my HTC EVO 3D using Tapatalk
Updated OP with some status update.
I used a steam recovry on my captivate that was full touch and really liked it. I dont remember any sort of oddities to get it running. Maybe talk to one of them and see how they got theirs set up.
if i can make one request i sed it on my phone and it was awesome. One thing the when selecting ROMS the font is small and often hard to hit the right one
IIRC you need to have the "itsmagic" script run at boot. When I came to the A500 scene it was already figured out so I'm not 100% sure on what it was or what exactly it does but I would recommend looking in to it. I'm sure some more senior A500 developers could help with its purpose.
Sooooooo close!
Updated OP, she is almost ready!
That is looking sweet, I like that 2nd gui alot better than the first one. A lot cleaner. rstuckmaier brought up an important point, are you including the "Its Magic" script in the recovery. I thought that was needed to fix the checksum values.
I don't see where any of the new recoveries do anything with "itsmagic" during the install process. The new GPL complient does nothing with itsmagic. Nor do thors.
Here are some screens of the boot up screen and a ICS theme.
pimpmaneaton said:
Here are some screens of the boot up screen and a ICS theme.
Click to expand...
Click to collapse
Great job!
cruise350 said:
That is looking sweet, I like that 2nd gui alot better than the first one. A lot cleaner. rstuckmaier brought up an important point, are you including the "Its Magic" script in the recovery. I thought that was needed to fix the checksum values.
Click to expand...
Click to collapse
Yeah the first shot we were running the phone layout, Second is a tab layout but not correct res. We should get it all figured out monday.
pimpmaneaton said:
Yeah the first shot we were running the phone layout, Second is a tab layout but not correct res. We should get it all figured out monday.
Click to expand...
Click to collapse
I'm certain you'll post it up in the DEV sections as soon as it's ready for "prime time"!
Thanks again for your dedication and hard work!
kjy2010 said:
I'm certain you'll post it up in the DEV sections as soon as it's ready for "prime time"!
Thanks again for your dedication and hard work!
Click to expand...
Click to collapse
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
pimpmaneaton said:
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
Click to expand...
Click to collapse
We need a good new Galaxy ROM! Back when these tabs first came out, M-Deejay's Galaxy port was my favorite ROM. Of course that was back when I was flash crazed, and looking for a fit to my preferences. Can't wait for it!
pimpmaneaton said:
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
Click to expand...
Click to collapse
Thanks for this. Read up on TWRP and it sounds and looks great. Definitely looking forward to your Galaxy offering.
Great job spear-heading these efforts. They are appreciated.
pimpmaneaton said:
I don't see where any of the new recoveries do anything with "itsmagic" during the install process. The new GPL complient does nothing with itsmagic. Nor do thors.
Click to expand...
Click to collapse
"itsmagic" is needed to recalculate the ROM checksum for the encrypted bootloader, which is verified every time you boot. Either you need to execute it (and Thors DOES do that, just read the install instructions for his 1.6 V2 recovery), or you need to incorporate its code into your recovery.
If you flash a new rom without recalculating the checksum afterwards, the checksum verification will fail and you won't be able to boot, essentially bricking the device.
FloatingFatMan said:
"itsmagic" is needed to recalculate the ROM checksum for the encrypted bootloader, which is verified every time you boot. Either you need to execute it (and Thors DOES do that, just read the install instructions for his 1.6 V2 recovery), or you need to incorporate its code into your recovery.
If you flash a new rom without recalculating the checksum afterwards, the checksum verification will fail and you won't be able to boot, essentially bricking the device.
Click to expand...
Click to collapse
If you manually install thors kernels then yes you do use itsmagic. But his flash script does not use it nor is it included in the flash zip either. I ensure you it will be tested thoroughly before its release. I have flashed virtuous galaxy with it and it booted fine.
Sent from my Sensation Rockin MIUI 1.12.16!
Hello everyone,
I am new to the Nexus 4 community however not new to XDA. I have survived an HD2 and also a T989 GSII. I have had so much success with XDA and I am looking forward to working with community of folks over here. I got a Nexus 4 (being delivered Monday) to enjoy the Android experience. However the more I look over it the more I feel it lacks some of the features that I enjoyed with previous custom roms like Toggles on the notification panel for example. I know there are many apps that will accomplish the same thing but why use all these 3rd party apps when you can flash a decent rom and get a better experience with often better battery life. I am coming from an All Star Developer ROM that is a compilation ROM ( CM10, AOKP & PA )
I apologize for the rambling. I need to know:
1: What is the difference between Original Android Dev and Android Development forums? GSII did not have two forums so I was a little confused.
2: For a genuine NEXUS device, are there still bugs in ROMS? RR, SOD, GPS not working, etc? This is not a huge issue with most GSII roms I just wondered if you guys experience this at all with this phone being stock Android already. I wouldn't think this would be the case.
3: I have done my research and I am ready to move on with rooting and probably Romming. Is there anything else maybe that would be noteworthy that is specific to the Nexus line of devices. This is a vague question so don't worry with it too much. I am just curious.
Thanks everyone! I can't wait till Monday!
jcnbama said:
Hello everyone,
I am new to the Nexus 4 community however not new to XDA. I have survived an HD2 and also a T989 GSII. I have had so much success with XDA and I am looking forward to working with community of folks over here. I got a Nexus 4 (being delivered Monday) to enjoy the Android experience. However the more I look over it the more I feel it lacks some of the features that I enjoyed with previous custom roms like Toggles on the notification panel for example. I know there are many apps that will accomplish the same thing but why use all these 3rd party apps when you can flash a decent rom and get a better experience with often better battery life. I am coming from an All Star Developer ROM that is a compilation ROM ( CM10, AOKP & PA )
I apologize for the rambling. I need to know:
1: What is the difference between Original Android Dev and Android Development forums? GSII did not have two forums so I was a little confused.
2: For a genuine NEXUS device, are there still bugs in ROMS? RR, SOD, GPS not working, etc? This is not a huge issue with most GSII roms I just wondered if you guys experience this at all with this phone being stock Android already. I wouldn't think this would be the case.
3: I have done my research and I am ready to move on with rooting and probably Romming. Is there anything else maybe that would be noteworthy that is specific to the Nexus line of devices. This is a vague question so don't worry with it too much. I am just curious.
Thanks everyone! I can't wait till Monday!
Click to expand...
Click to collapse
1. "Development is classified as original work and/or documented edits and changes made to others work (with their permission) that makes it your own.
Stock ROM dumps that are modified (deodexed, etc.) from the manufacturer's original intent and then repackaged together classifies as development.
Kernel's and Recovery obviously classify as development as they are modified and compiled from source""
2. Minor bugs here & there, nothing like the ones you're used of. Read the OP & last 20 posts in the thread.
3. follow the link in my signature, do not use toolkits!!
Good luck, it's an amazing phone!
Vangelis13 said:
1. "Development is classified as original work and/or documented edits and changes made to others work (with their permission) that makes it your own.
Stock ROM dumps that are modified (deodexed, etc.) from the manufacturer's original intent and then repackaged together classifies as development.
Kernel's and Recovery obviously classify as development as they are modified and compiled from source""
2. Minor bugs here & there, nothing like the ones you're used of. Read the OP & last 20 posts in the thread.
3. follow the link in my signature, do not use toolkits!!
Good luck, it's an amazing phone!
Click to expand...
Click to collapse
Thanks for the info! I guess more specifically I need to know the difference between the "Original" Development thread and just the "Development" thread. Should I refer to one more than another?
Also, in reference to toolkits. I am just curious where the issue lies with that? Because honestly that is exactly what I was going to do. I am not lazy, just efficient lol. I figure why do alot of manual driver installs and command prompts if someone created a program that would do it for you? (I reference links below) Is it faulty software? Badly written programs etc? I would think there would be more room for human error when doing it yourself vs. something automated. What are your thoughts on this? Has anyone else had luck using the toolkits in the links? or any other rooting toolkits? Thanks again!
http://lifehacker.com/5979763/how-to-root-the-lg-nexus-4#13634416619583&{"type":"iframeUpdated","height":640}
http://www.wugfresh.com/nrt/
jcnbama said:
Thanks for the info! I guess more specifically I need to know the difference between the "Original" Development thread and just the "Development" thread. Should I refer to one more than another?
Also, in reference to toolkits. I am just curious where the issue lies with that? Because honestly that is exactly what I was going to do. I am not lazy, just efficient lol. I figure why do alot of manual driver installs and command prompts if someone created a program that would do it for you? (I reference links below) Is it faulty software? Badly written programs etc? I would think there would be more room for human error when doing it yourself vs. something automated. What are your thoughts on this? Has anyone else had luck using the toolkits in the links? or any other rooting toolkits? Thanks again!
http://lifehacker.com/5979763/how-to-root-the-lg-nexus-4#13634416619583&{"type":"iframeUpdated","height":640}
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Because, you learn something very important while rooting & unlocking your phone. Human error is covered for by the step by step guide. Human error while using the toolkit, you're stuck trying to understand what the fck happened. Learn fastboot mate. Learn to control your device to a 100%, learn to fix it if it's stuck. Understand what happens with "fastboot OEM unlock". Do you know what that means btw..?
The difference between Original Development & Development is in the quote I posted above. Paranoid Android = Original.
TWRP Recovery = Original
"XYZ" Rom based on cm 10.1 + abcd theme = Development.
Vangelis13 said:
Because, you learn something very important while rooting & unlocking your phone. Human error is covered for by the step by step guide. Human error while using the toolkit, you're stuck trying to understand what the fck happened. Learn fastboot mate. Learn to control your device to a 100%, learn to fix it if it's stuck. Understand what happens with "fastboot OEM unlock". Do you know what that means btw..?
The difference between Original Development & Development is in the quote I posted above. Paranoid Android = Original.
TWRP Recovery = Original
"XYZ" Rom based on cm 10.1 + abcd theme = Development.
Click to expand...
Click to collapse
Hey thanks again. I appreciate the input. I have more to learn in the NEXUS forum. I am used to ODIN and other forms of Samsung software so I will certainly read over the tutorial and absorb information. It will also help me to share my knowledge with others.
jcnbama said:
Hey thanks again. I appreciate the input. I have more to learn in the NEXUS forum. I am used to ODIN and other forms of Samsung software so I will certainly read over the tutorial and absorb information. It will also help me to share my knowledge with others.
Click to expand...
Click to collapse
If nothing else, you owe it to yourself as a proud n4 owner!!
Yesterday i saw CyanogenMod Installer app for android...
It is quite helpful for those who are flashing roms first time on their device after rooting...
This app also tells them whether a Cyanogen rom is available for their device or not...
I m currently working on paranoid if this feature is added to PA source itself then it will cause pain for other roms...
This will be a arsenal for paranoidsss...
Have a look at CM installer
https://play.google.com/store/apps/details?id=org.cyanogenmod.oneclick
I m not promoting CM but giving u all idea atleast...
It won't cause pain for other roms. People are not exactly lined up waiting for an installer for PA before they can flash it. Not to mention CM devs are quite open to using roms other than CM after using their installer. Its about more than just flashing your favorite rom. its about having a choice other than what your carrier forces you into. And since devs often borrow features from other ROMs, this would hardly be pain for other roms. As tools make developement easier, i think we will see more roms or at least modified roms that have peoples own touch added to them.
Installer will be great for newbies...
theroadrunner said:
It won't cause pain for other roms. People are not exactly lined up waiting for an installer for PA before they can flash it. Not to mention CM devs are quite open to using roms other than CM after using their installer. Its about more than just flashing your favorite rom. its about having a choice other than what your carrier forces you into. And since devs often borrow features from other ROMs, this would hardly be pain for other roms. As tools make developement easier, i think we will see more roms or at least modified roms that have peoples own touch added to them.
Click to expand...
Click to collapse
if a rom offers an installer app then it will attract new users who havent flashed custom roms yet...this what i meant..
Custom ROM Installer
I think that an Automatic Installer for the first flashers would be indeed "comforting" Because I've started to flash custom roms recently and my first one was a pain, not because of the steps....The steps for installing the recovery tool and all are pretty easy and all. But we have the feeling we are going to brick the device at the first flash! hehe Maybe an automatic installer that detects your device model would be kinda safe for unexperienced users...
But nowadays I find it nice to manually flash roms, keep backups, etc...
Oh well...not a bad idea at all in my opinion ;}
That CM Installer is stupid. I used and thought when it said, it will delete your things. I processed that as the normal factory reset in TWRP for a clean flash. Apparently it was a full freaking wipe. Lost everything. I think that process they used it unnessesary.
moneyolo said:
That CM Installer is stupid. I used and thought when it said, it will delete your things. I processed that as the normal factory reset in TWRP for a clean flash. Apparently it was a full freaking wipe. Lost everything. I think that process they used it unnessesary.
Click to expand...
Click to collapse
I don't understand why they needed to wipe the SD card, but you should have read the instructions and backed up your data before installing...
Just as an FYI, the still-in-progress Omni installer is going to be designed such that it can be used by any project. (And cooperation with other projects for inputs is welcome!)
I'm not working on it myself, it's xplodwild's baby - but as an example, there's serious consideration of hooking it into XDA's devdb, although I think it'll require some dependencies metadata to be added to devdb for it to work. (e.g. automagically handle gapps).
stephendt0 said:
I don't understand why they needed to wipe the SD card, but you should have read the instructions and backed up your data before installing...
Click to expand...
Click to collapse
Yeah, that was my fault aswell.
Now it will help..
Entropy512 said:
Just as an FYI, the still-in-progress Omni installer is going to be designed such that it can be used by any project. (And cooperation with other projects for inputs is welcome!)
I'm not working on it myself, it's xplodwild's baby - but as an example, there's serious consideration of hooking it into XDA's devdb, although I think it'll require some dependencies metadata to be added to devdb for it to work. (e.g. automagically handle gapps).
Click to expand...
Click to collapse
Now CyanogenMod team made their Installer Open to all https://github.com/cyngn/OneClickAndroid
this will surely give ideas to other rom developers how to do it in a better way... thnxxx to CyanogenMod
anurag.dev1512 said:
Now CyanogenMod team made their Installer Open to all https://github.com/cyngn/OneClickAndroid
this will surely give ideas to other rom developers how to do it in a better way... thnxxx to CyanogenMod
Click to expand...
Click to collapse
FYI, don't go thanking CM just yet....that source they shared is just for the app which all it does is enable USB debugging hahaha
Is not the source for the installer which I believe is a msi or exe
wait i will check ...
Mazda said:
FYI, don't go thanking CM just yet....that source they shared is just for the app which all it does is enable USB debugging hahaha
Is not the source for the installer which I believe is a msi or exe
Click to expand...
Click to collapse
thnxxx for notifying me... i havent checked the source but i will check now...
nice!
MOTOROLA UTILITY BY THEREALDUFF1
View https://www.youtube.com/watch?v=6DdZhVae_p0 to see how I created this program !
Please like and subscribe to my youtube channel to encourage me to create more tools for the members of xda ! I really really appreciate it
This is a GUI based program, which I have started programming in python.
Unlike other tools, this one is specifically made for the Motorola G3.
This entire tool is foolproof, so if you think you may brick your device when flashing TWRP, or stock rom by typing the wrong command, this is the place to be!
All of the tools are included in the program, including the TWRP.img file, and ADB and Fastboot tools. The Motorola drivers are inside the zip, so you don't have to go searching for them !
I have updated Motorola Utility, to be able to work with marshmallow perfectly. V6.2 is uploaded now and is avalible at http://forum.xda-developers.com/devdb/project/dl/?id=17073
Lollipop Version Available In Downloads Section !
Features
-- Marshmallow Compatible
-- Moto G 2015 Specific
-- Roots Your Device
-- Flash TWRP
-- Flash Custom Roms ( Coming Soon !)
-- Flash Stock Rom
-- Safely Upgrade Your Device To Marshmallow (Coming From Lollipop Or Marshmallow Custom Rom)
-- Push Modded Zips To The Device(Coming soon to Motorola Utility Marshmallow !)
-- Lock The Bootloader
-- Troubleshoot Your Device For Problems (Currently In My Beta Version Of The Tool)
Information
This program is currently stable, and only finished and beta features are in the program.
If you would like to contribute to this project, feel free to drop me a message, or email me at [email protected]
In one of the comments, I have posted a screenshot of the program, if anyone would like to see it running
Prerequisites
-- Python 3.4
DOWNLOAD
V6.3: http://forum.xda-developers.com/devdb/project/dl/?id=17180
XDA:DevDB Information
[UTILITY][6.0][5.0]Motorola Utility, Tool/Utility for the Moto G 2015
Contributors
therealduff1
Version Information
Status: Stable
Stable Release Date: 2016-02-22
Created 2015-12-15
Last Updated 2016-03-12
This seems to be amazing. Congratulations!
Where is download link?
Yousvel said:
This seems to be amazing. Congratulations!
Where is download link?
Click to expand...
Click to collapse
Thanks so much !
Sorry, i uploaded the file , but it is not currently showing.
Il put the link in the description
therealduff1 said:
Thanks so much !
Sorry, i uploaded the file , but it is not currently showing.
Il put the link in the description
Click to expand...
Click to collapse
No problem. As you know, xda doesn't accept place holder.
Yousvel said:
No problem. As you know, xda doesn't accept place holder.
Click to expand...
Click to collapse
Does the link show now on your side?
If it does , please to reply with your opinions on the program, as i would greatly appreciate your opinion. Open toolkit.py first, as that is the main program
Please take into account that this is a very early version of the program , and does not include all of the features in the description. This is a start point !
I am also 15 yrs old, so I have alot of time on my hands to work on this
therealduff1 said:
Does the link show now on your side?
If it does , please to reply with your opinions on the program, as i would greatly appreciate your opinion. Open toolkit.py first, as that is the main program
Please take into account that this is a very early version of the program , and does not include all of the features in the description. This is a start point !
I am also 15 yrs old, so I have alot of time on my hands to work on this
Click to expand...
Click to collapse
The download link is up. Good job bro!
Very nice job dude... This was the application I eas waiting for... But does it unlocks bootloader?
Will you be able to root by booting to TWRP vice flashing boot to the G3?
Congrats with an end product. ?
I understand the handiness of such tools, but I've never been a fan of these GUI tools. Ultimately, the tool ends up coddling the new user and allows the lazy, support leech-type users to remain lazy and not learn what they're really doing.
Look at the support threads for Wug's Nexus toolkit as a great example.
Sent from my MotoG3 using Tapatalk
mkmandar123 said:
Very nice job dude... This was the application I eas waiting for... But does it unlocks bootloader?
Click to expand...
Click to collapse
Not yet, but it will be able to in the very near future
Please click thanks to show you like the program
therealduff1 said:
Not yet, but it will be able to in the very near future
Please click thanks to show you like the program
Click to expand...
Click to collapse
Waiting eagerly for it.....
nikon120 said:
Congrats with an end product.
I understand the handiness of such tools, but I've never been a fan of these GUI tools. Ultimately, the tool ends up coddling the new user and allows the lazy, support leech-type users to remain lazy and not learn what they're really doing.
Look at the support threads for Wug's Nexus toolkit as a great example.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I understand where you are coming from completely about lazy tech people , but this tool is intended for people who don't really know what they are doing , or don't want to risk bricking their phone in the flash progress.
therealduff1 said:
I understand where you are coming from completely about lazy tech people , but this tool is intended for people who don't really know what they are doing , or don't want to risk bricking their phone in the flash progress.
Click to expand...
Click to collapse
A don't a disagree a think it is a good tool and people who are using it might not know what a computer is me personally try to do stuff my own but we all need help from time to time.
nikon120 said:
Congrats with an end product. ?
I understand the handiness of such tools, but I've never been a fan of these GUI tools. Ultimately, the tool ends up coddling the new user and allows the lazy, support leech-type users to remain lazy and not learn what they're really doing.
Look at the support threads for Wug's Nexus toolkit as a great example.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I mostly agree, I appreciate that someone makes a tool like this, especially a 15 year old, but a certain niche of people are going to require being spoon fed even if the answer is in front of their face. I've said all along that a large majority of the people that have to get the latest Android and root it are doing it because everyone else is.
Screenshot
I have attached a screenshot of my program
therealduff1 said:
MOTOROLA UTILITY BY THEREALDUFF1
This is a GUI based program, which I have started programming in python.
Unlike other tools, this one is specifically made for the Motorola G3.
This entire tool is foolproof, so if you think you may brick your device when flashing TWRP, or stock rom by typing the wrong command, this is the place to be!
All of the tools are included in the program, including the TWRP.img file, and ADB and Fastboot tools.
Features
-- Moto G 2015 Specific
-- Roots Your Device
-- Flash TWRP
-- Flash Custom Roms
-- Flash Stock Rom
-- Push Modded Zips To The Device
-- Lock The Bootloader
-- Troubleshoot Your Device For Problems
Information
This program is not entirely finished, and some of the features above are not currently functional.
If you would like to contribute to this project, feel free to drop me a message, or email me at [email protected]
In one of the comments, I have posted a screenshot of the program, if anyone would like to see it running
Prerequisites
-- Python 3.4
XDA:DevDB Information
Motorola Utility, Tool/Utility for the Moto G 2015
Contributors
therealduff1
Version Information
Status: Testing
Created 2015-12-15
Last Updated 2015-12-16
Click to expand...
Click to collapse
If anyone thinks of a feature that could be added, please do 'feature request' it, and Il be happy to do my best to add it for you
What would people think about mobile custom rom installers , which would wipe dalvik and cache , factory reset etc. ,and then install the rom for you ?
Maybe even make a backup on the job
therealduff1 said:
What would people think about mobile custom rom installers , which would wipe dalvik and cache , factory reset etc. ,and then install the rom for you ?
Maybe even make a backup on the job
Click to expand...
Click to collapse
Good idea! That would help some noobs not to brick their phone.
By the way , you might want to put the adb and fastboot tools from version 1 of my program into version 2 , if version 2 is what you want to use . sorry about the problem , I just forgot to adb and fastboot in the zip
A think it's great what you are doing m8t am going to wait till u have a working sample then a will test it for u
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
therealduff1 said:
What would people think about mobile custom rom installers , which would wipe dalvik and cache , factory reset etc. ,and then install the rom for you ?
Maybe even make a backup on the job
Click to expand...
Click to collapse
Excellent idea!!
I have a Moto G6 device that I need to build a ROM for and I am pretty much stuck at the point where I need to include the proprietary device drivers so that I can compile the ROM. I guess my main issue is knowing where to get the proprietary files and how to incorporate them into my ROM. The device has a separate "/vendor" partition (for Treble compliance) that I was able to use TWRP and ADB to copy the files to my PC by running TWRP and then using ADB PULL command "adb pull /vendor D:\ALI\vendor" to get the files into a folder on my PC and was successful in doing that, but now what? What do I do with them? I downloaded from git the AOSP source for the last build of Oreo (8.0.0_36), so I hope that in itself is correct.
In the past, I have built a custom ROM for the Moto G4 via LineageOS 14.1, so I had a lot of info on how to grab the drivers from a device that was already running LineageOS 14.1, but this Moto G6 is running stock Oreo (8.0.0), so I am at a loss on whether or not I grabbed them from the device properly and now that I have them in folders on my PC what do I do with them and how do I set up the device tree so that I can get AOSP to compile.
So what do I do next and how?
I dont know if you've seen this and sorry if it doesn't help you at all. https://source.android.com/setup/develop/new-device
meatwad0222 said:
I dont know if you've seen this and sorry if it doesn't help you at all. https://source.android.com/setup/develop/new-device
Click to expand...
Click to collapse
I will look it over and see if I can hit the ground running with the info it provides. If not, I'll report back here for more help if needed. Thank you!
hawleytronics said:
I will look it over and see if I can hit the ground running with the info it provides. If not, I'll report back here for more help if needed. Thank you!
Click to expand...
Click to collapse
Honestly, this should have been posted in the Q&A Section, and the title is a little misleading. Just saying.
Anyway, as far as building goes, you have a lot of reading and learning to do. It'll take a lot more than that link the other user provided above as that's more for OEM's (but will give you somewhat of an understanding of what it's gonna take to put together a device, kernel, and vendor trees).
There is a lot of info regarding building ROMs for devices here on xda. I'd recommend reading thru those threads/posts for some insight.
Jleeblanch said:
Honestly, this should have been posted in the Q&A Section, and the title is a little misleading. Just saying.
Anyway, as far as building goes, you have a lot of reading and learning to do. It'll take a lot more than that link the other user provided above as that's more for OEM's (but will give you somewhat of an understanding of what it's gonna take to put together a device, kernel, and vendor trees).
There is a lot of info regarding building ROMs for devices here on xda. I'd recommend reading thru those threads/posts for some insight.
Click to expand...
Click to collapse
OK, thank you, and sorry for posting in the wrong area. It appears that I need to know more in-depth about the actual hardware and what drivers are needed and where they need to go. So more research it is.