Related
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
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
thanx a lot helping out mahn
will go with the official unlock
and official twrp
i have been waiting a lot to try cm 13
So i've been looking on the internet for some ways to port any CM to my device J100FN, i found quite a few but some of them are outdated or badly explained etc etc...
I'm gonna put it plain and simple.
I have linux, i have my stock rom J100FNXXU0AOD1, and i can surely get any CM somewhere in the internet (note that i have CM12 for Samsung S3 neo already so tell me if that's gonna do it)
Here are the tutorials that i found so far:
https://www.youtube.com/watch?v=GAyxypK7_K8 (says that i need a CM already built for my phone, which is no available)
https://forum.xda-developers.com/showthread.php?t=2545618 (same with this one)
https://forum.xda-developers.com/showthread.php?t=2245786 (and this one is kinda poorly explained at the begining)
Note that i have a rooted device and TWRP recovery up and running on it, also i read about this "Cyanogenmod compiler" thingy thing, but i couldn't manage to download it, i think the repos are down now or idk. (https://forum.xda-developers.com/showthread.php?t=1415661) (https://korben.info/cyanogenmod-compiler.html)
IDK MAN I REALLY NEED CYANOGENMOD ON MY GALAXY J1 LTE, i'm kind of a rookie when it comes to complicated roms maneuvering but i still do have basic knowledge (flashing, rooting, few terminal cmd's etc etc...)
Please help, and thank.
Putshi said:
So i've been looking on the internet for some ways to port any CM to my device J100FN, i found quite a few but some of them are outdated or badly explained etc etc...
I'm gonna put it plain and simple.
I have linux, i have my stock rom J100FNXXU0AOD1, and i can surely get any CM somewhere in the internet (note that i have CM12 for Samsung S3 neo already so tell me if that's gonna do it)
Here are the tutorials that i found so far:
https://www.youtube.com/watch?v=GAyxypK7_K8 (says that i need a CM already built for my phone, which is no available)
https://forum.xda-developers.com/showthread.php?t=2545618 (same with this one)
https://forum.xda-developers.com/showthread.php?t=2245786 (and this one is kinda poorly explained at the begining)
Note that i have a rooted device and TWRP recovery up and running on it, also i read about this "Cyanogenmod compiler" thingy thing, but i couldn't manage to download it, i think the repos are down now or idk. (https://forum.xda-developers.com/showthread.php?t=1415661) (https://korben.info/cyanogenmod-compiler.html)
IDK MAN I REALLY NEED CYANOGENMOD ON MY GALAXY J1 LTE, i'm kind of a rookie when it comes to complicated roms maneuvering but i still do have basic knowledge (flashing, rooting, few terminal cmd's etc etc...)
Please help, and thank.
Click to expand...
Click to collapse
Don't let this thread die please :/
Like come on 34 views but no replies...
How did you get the TWRP for your phone? Is there one for the J100? I haven't managed to root my J727 One thing you could do is use the google android tree with all its garbage and then copy and paste the CM tree into it. But quite frankly I hesitate to suggest this because it's a huge pain in the ass, and like I said, I haven't managed to get TWRP working for my phone doing this. I can get it compiled but... I have no idea what makes it specific to the phone. I thought it was enough just to have the kernel for the specific phone...
peterius said:
How did you get the TWRP for your phone? Is there one for the J100? I haven't managed to root my J727 One thing you could do is use the google android tree with all its garbage and then copy and paste the CM tree into it. But quite frankly I hesitate to suggest this because it's a huge pain in the ass, and like I said, I haven't managed to get TWRP working for my phone doing this. I can get it compiled but... I have no idea what makes it specific to the phone. I thought it was enough just to have the kernel for the specific phone...
Click to expand...
Click to collapse
Idk man, I just looked up a tutorial on how to root it, I had to look quite deeply but I found it and it's working just fine, it requiers you to flash the boot.img too and then root it with Kingoroot, this is the tutorial I followed www .halabtech. com/root-for-j100fn/ (I know it looks shady but it worked, also I can't post links because my account is new...)
Also I asked a dev and he asked me about the source code of the cpu or some stuff, tbh I have no idea why you would need that to make a rom out of a stock rom...
As I've been informed by twrp, the recovery image typically has it's own kernel which means its specific to the device. I'm not totally sure of the reasons for this. I ended up returning the galaxy j727u which has a locked bootloader for a xiaomi, I'll see how it goes.
I see, but that doesn't really advance in my case
Is any devs out there willing to help out a stupid newbie :^)
Come on now don't let this thread die
I am completely new to Android Engineering and want to learn it. Till now, I have tried building aosp oreo from repo. It is built successfully but I don't know about the use of all the folders that are downloaded by the repo. What is the use or importance of each folder in repo? Where can I learn more about this?
I have also modified my stock firmware (only removed some bloatware apps) and rebuilt the firmware. I haven't installed it yet. I used android kitchen which helped me with signing the zip but I am afraid the signature might be for testing and not the official vendor signature. I have phone with unlcoked bootloader but it's still on stock recovery. According to my knowledge, unlocking bootloader helps us to flash unofficial files but people at XDA say that we should also have custom recovery to flash custom ROMs. Should I flash the modified ROM built by me in device with stock ROM and unlocked bootloader?
My device doesn't have official TWRP support. How can I port recovery or build it from scratch for my phone?
Also, I have only modified stock ROM and need to learn porting ROMs like porting MIUI for my device. How can we port ROMs?
Sorry for asking all these at once but I tried getting answer one after another which confused me a lot. I am a noob in this field.
I read XDA thread of TWRP developer which included a guide on how to build TWRP for any device. But as the author said, that post wasn't for noobs. Maybe I need to learn a lot before I reach that level of understanding. But I don't know what to learn and from where. Please help..
And one last thing - What is a device tree? Or vendor tree? I saw these words many times when I was trying to understand the above things. But I still don't know what these are and Google doesn't help. Thank you everyone..
Hi
there is this section here https://forum.xda-developers.com/android/software
you`ll find some sticky threads of the top with plenty of info , have a look !
you may also use search and type XDA University , it will reveal also some useful links
Good luck !
Hello,
As the thread where I originally announced this was locked for reasons apparently unrelated to my build, and the links removed, I'm creating a new thread to keep the community aware of these builds.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
The build for the Asus Zenpad 8.0 Z380K[N]L (aka P024) is at https://lineageos.disavowed.jp/p024/. This appears to work on both the Z380KL (as reported in the locked thread) and my Z380KNL. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Hi, I have been using your build and updated my device weekly! it' s still good and awesome. (I also use your build for my nexus7)
if you find Oreo, Pie version! please let everyone know. Thank you.
Thank's keep update bro.
Hi, I don't see your weekly build for 22 Nov 2019.
Are there any issues ?
Nice update thanks friends l.
Yeap yesterday i reported, and TS promised to update.
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Question about Unofficial rom for Asus ZenPad 8.0 z380knl
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
poka_dan said:
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
Click to expand...
Click to collapse
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
As soon as I find out MTP is working I will flash the rom
wileyc said:
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
Click to expand...
Click to collapse
Gift was my pleasure
The info is most usefull. Thank you for that.
I am currently running my ZenPad 8.0 z380knl on Asus stock rom but ardently looking to upgrade to android 7.1.2 for security reasons as well as other reasons.
I was investigating if everything is working on the new rom. Also upgrade procedure from stock rom to lineage os and from lineage os 14.1 to latest 14.1 lineage os. Thankfully you cleared all that up. Thanks so much !
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
BTW, I haven't seen your new buld since last week.Will there be no update ?
Is everything working with this ROM?
Can i get confirmation from someone who is actively using it..
MTP and everything else working?
pokadan said:
Gift was my pleasure
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
Click to expand...
Click to collapse
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
androidlover2019 said:
BTW, I haven't seen your new buld since last week.Will there be no update ?
Click to expand...
Click to collapse
There should be an update (or two!) today. The build rooster hung about midway through last week's build for deb, and was actually still running after seven days. I killed off the deb build process and it's progressing to the other devices, although much slower than it should be. I'll troubleshoot this after the regularly scheduled build completes late tonight.
(I'm using Arch Linux on this build machine, and it seems that something in the filesystem layer in kernel > 5.4.10 doesn't like operating under sustained heavy load)
I saw your new build today and have installed it. Thank you
However, The latest security patch has not been applied yet. Hope it will come in next build.
Thank you so much for maintaining the device.
Thank you wileyc !
wileyc said:
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
Click to expand...
Click to collapse
I have put the latest available rom lineage-14.1-20200202-UNOFFICIAL-P024.zip on my device and works flawlessly!
Million thanks
I have installed the newest one (built on 08 Feb)
the Android security patch was updated to Jan 2020! Thank you very much.
I am worried how long you will keep sharing your build weekly.
Hope next 2 years Thanks again.
I have also installed the latest. Thanks so much!
Thankyou for the update :good:
What about selinux?