Hey guys I got crdroid working, and after a month of work I got it to work.
Everything so far is working.
Report if you see any problems and upload your logcat file
By the way this is a ported ROM from the Honor 5x, hence you can see the model number there on the screenshot, I will have to take a look at the build prop to fix that.
So to install it here are the steps:
- Make sure you're running a proper working Recovery TWRP)
- Copy GApps and crDroid zip to your internal SDCard
- Boot into Recovery
-Wipe system,data,cache,dalvik cache
- Flash crDroid zip
- Flash GApps zip
- DO A DATA WIPE / FACTORY RESET
- Reboot
By the way its still uploading, and its going to take a while, because my internet is pretty bad at the moment.
Rom source code: https://github.com/crdroidandroid/android/tree/7.1
Special Thanks to @madvane20
For helping me out through this whole process.
must be ur april fools joke xd
Why does it say 6.0.1 if it's a Nougat ROM?
No link, so I call April fools as well
powerserge1 said:
No link, so I call April fools as well
Click to expand...
Click to collapse
Well it was obvious that it was April fools...
XD
Nachitoo said:
Hey guys I got crdroid working, and after a month of work I got it to work.
Everything so far is working.
Report if you see any problems and upload your logcat file
By the way this is a ported ROM from the Honor 5x, hence you can see the model number there on the screenshot, I will have to take a look at the build prop to fix that.
So to install it here are the steps:
- Make sure you're running a proper working Recovery TWRP)
- Copy GApps and crDroid zip to your internal SDCard
- Boot into Recovery
-Wipe system,data,cache,dalvik cache
- Flash crDroid zip
- Flash GApps zip
- DO A DATA WIPE / FACTORY RESET
- Reboot
By the way its still uploading, and its going to take a while, because my internet is pretty bad at the moment.
Rom source code: https://github.com/crdroidandroid/android/tree/7.1
Special Thanks to @madvane20
For helping me out through this whole process.
Click to expand...
Click to collapse
Don't know if its a April fool or not but I've closed the thread for now. If you drop me a line or use the RP button with a working download link we will reopen the thread for you
Regards
Sawdoctor
Related
Is Samsung Galaxy S5 G900T a KLTE handset? cannot seem to find anything related to T-mobile S5
nht48823 said:
Is Samsung Galaxy S5 G900T a KLTE handset? cannot seem to find anything related to T-mobile S5
Click to expand...
Click to collapse
Yes it is
from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.1.1 DOB1 with Resurrection Remix ROM v5.5.6
jt1998 said:
Yes it is
from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.1.1 DOB1 with Resurrection Remix ROM v5.5.6
Click to expand...
Click to collapse
I'm trying to flash cyanogenmod from twrp but getting error 7 , can't flash over incompatible system data. I'm on t mobile sm-g900t and downloaded the latest klte snapshot...
Help please.
Dorsant said:
I'm trying to flash cyanogenmod from twrp but getting error 7 , can't flash over incompatible system data. I'm on t mobile sm-g900t and downloaded the latest klte snapshot...
Help please.
Click to expand...
Click to collapse
Trying to flash cm 12 rom right? It's a zip? Checked md5 to ensure good download?
I'd update to latest twrp 3.0 first. Make a backup of current rom/setup.
Are you trying clean or dirty flash?
Sent from my SM-G900T using Tapatalk
jt1998 said:
Trying to flash cm 12 rom right? It's a zip? Checked md5 to ensure good download?
I'd update to latest twrp 3.0 first. Make a backup of current rom/setup.
Are you trying clean or dirty flash?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Not sure how to check if md5 download was good, but there were no interruptions so I believe it was.
And what is clean vs dirty flash? I downloaded the only "snapshot" version that was on the klte downloads page directly to my phone. Rebooted into twrp recovery, selected zip file, swipe to flash. Then I get the error. Looks like file name says CM 12.1-20115007....
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Thanks
Dorsant said:
And what is clean vs dirty flash?
Click to expand...
Click to collapse
Make a backup, then wipe system, data, cache, and dalvik before flashing the ROM. It helps prevent bugs
Dorsant said:
Thanks for the reply. Not sure how to check if md5 download was good, but there were no interruptions so I believe it was.
And what is clean vs dirty flash? I downloaded the only "snapshot" version that was on the klte downloads page directly to my phone. Rebooted into twrp recovery, selected zip file, swipe to flash. Then I get the error. Looks like file name says CM 12.1-20115007....
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Thanks
Click to expand...
Click to collapse
This is the Cm 12.1 ROM I'd use for your device https://download.cyanogenmod.org/get/jenkins/129251/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
You'll need an android 5.0 lollipop gapps also which allows you to use your ROM with google apps, play store functionality, etc. This is the one I'd use for your device. https://basketbuild.com/filedl/devs...gapps-modular-micro-5.1.1-20150927-signed.zip
Once both are downloaded onto your phone storage, make sure you backup 1st in TWRP so if anything goes wrong you're ok.
Clean flash means you're wiping system, data, dalvik, and cache before installing new ROM/Gapps - always reccommended if you're coming from stock touchwiz a different non CM rom.
Dirty flash means you only wipe dalvik and cache typically b/c you're just updating your current ROM with a newer version of same ROM so no need to wipe data/system but it is the first thing to evaluate if your device has errors like force closures, bugginess, etc.
Also, after you've wiped your device and now are ready to install your ROM and gapps, do both zip installs in one step. so add the ROM, then add another zip which will be your gapps, then swipe to flash having 2 zips in your queue. Then when all is done, reboot and let your device install. Sign in setup your accounts and profit.
Let me know how it goes ok! Hit thanks for me please!!
jt1998 said:
This is the Cm 12.1 ROM I'd use for your device https://download.cyanogenmod.org/get/jenkins/129251/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
You'll need an android 5.0 lollipop gapps also which allows you to use your ROM with google apps, play store functionality, etc. This is the one I'd use for your device. https://basketbuild.com/filedl/devs...gapps-modular-micro-5.1.1-20150927-signed.zip
Once both are downloaded onto your phone storage, make sure you backup 1st in TWRP so if anything goes wrong you're ok.
Clean flash means you're wiping system, data, dalvik, and cache before installing new ROM/Gapps - always reccommended if you're coming from stock touchwiz a different non CM rom.
Dirty flash means you only wipe dalvik and cache typically b/c you're just updating your current ROM with a newer version of same ROM so no need to wipe data/system but it is the first thing to evaluate if your device has errors like force closures, bugginess, etc.
Also, after you've wiped your device and now are ready to install your ROM and gapps, do both zip installs in one step. so add the ROM, then add another zip which will be your gapps, then swipe to flash having 2 zips in your queue. Then when all is done, reboot and let your device install. Sign in setup your accounts and profit.
Let me know how it goes ok! Hit thanks for me please!!
Click to expand...
Click to collapse
Perfect! Great explanation, worked perfectly!
Dorsant said:
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Click to expand...
Click to collapse
there's little reason to use an old & insecure version at this point, i've ONLY used a few nightlies, the bugs were usually minor & you can get the fixes pretty much as soon as they come out rather than waiting months
deep sleep battery use & the camera app are greatly improved in CM13
http://www.cmxlog.com/13/klte/ changelogs
Hey guys I got crdroid working, and after a month of work I got it to work.
Everything so far is working.
Report if you see any problems and upload your logcat file
By the way this is a ported ROM from the Honor 5x, hence you can see the model number there on the screenshot, I will have to take a look at the build prop to fix that.
So to install it here are the steps:
- Make sure you're running a proper working Recovery TWRP)
- Copy GApps and crDroid zip to your internal SDCard
- Boot into Recovery
-Wipe system,data,cache,dalvik cache
- Flash crDroid zip
- Flash GApps zip
- DO A DATA WIPE / FACTORY RESET
- Reboot
By the way its still uploading, and its going to take a while, because my internet is pretty bad at the moment.
Rom source code: https://github.com/crdroidandroid/android/tree/7.1
Special Thanks to @madvane20
For helping me out through this whole process.
I hope this isn't an April fools joke!
Sent from my H1611 using Tapatalk
The thread got closed since placeholder threads aren't allowed on xda.
@Nachitoo: Please PM me or report your opening post as soon as you can provide a download link. The mod team will re-open your thread then.
I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
deloj said:
I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
Click to expand...
Click to collapse
Restored a backup of what? Data is no compatible across roms. Lineage 15 is also not stable. 14.1 is recommended.
deloj said:
I installed lineageos 15.1 oreo on my nexus 9. I recently restored a backup through twrp on it. Everything was restored except for data on an email client. I cant access mail. When I try to, I get a refresh icon (see image link below). I tried reinstalling, clearing cache and data but that doesnt work. Is there a file I need to tweak for my nexus to be able to access mail again?
Click to expand...
Click to collapse
madbat99 said:
Restored a backup of what? Data is no compatible across roms. Lineage 15 is also not stable. 14.1 is recommended.
Click to expand...
Click to collapse
I restored a backup of my nexus 9 as in nandroid. If you say data isnt compatible across roms. But I was able to make a nandroid of 2 of my phones that I restored successfully before.
You also suggested 14.1 for a stable rom. But if I install it and make a nandroid then restore if something goes wrong will I get the same issue I'm having now?
Since I got lineagos 15.1 how do I install 14.1?
.
deloj said:
I restored a backup of my nexus 9 as in nandroid. If you say data isnt compatible across roms. But I was able to make a nandroid of 2 of my phones that I restored successfully before.
You also suggested 14.1 for a stable rom. But if I install it and make a nandroid then restore if something goes wrong will I get the same issue I'm having now?
Since I got lineagos 15.1 how do I install 14.1?
.
Click to expand...
Click to collapse
When I said backup of what, I meant what rom is it a backup of.
I meant data from 1 ROM is not always going to restore correctly on another rom. If it's a backup of the same ROM, it should restore. If it's from another ROM, well, that's hit or miss. And usually not a good idea.
I always start fresh. Maybe restore some apps that I backed up previously with titanium backup. But not usually the whole data partition.
madbat99 said:
When I said backup of what, I meant what rom is it a backup of.
I meant data from 1 ROM is not always going to restore correctly on another rom. If it's a backup of the same ROM, it should restore. If it's from another ROM, well, that's hit or miss. And usually not a good idea.
I always start fresh. Maybe restore some apps that I backed up previously with titanium backup. But not usually the whole data partition.
Click to expand...
Click to collapse
Hi madbat,
I tried to downgrade/ install lineagos 14.1 Nougat on my nexus 9 from lineagos 15.1 Oreo. But after I reboot to system, the word google stays stuck on screen. It doesn’t boot to the rom. These are the steps I took and the zips with it:
1) First wipe : TWRP > swipe to factory reset > adv.wipe cache/data/system/dalvik > Format data > Reboot to Recovery
2) TWRP > Install > Slim Rom 7.12 / open_gapps-arm64-7.1-nano-20190529.zip / > Reboot on Recovery >
3) TWRP > Install > dm verity FED > SR5-SuperSU-v2.82-SR5-20171001224502.zip > wipe cache & dalvik (ONLY!) & Reboot system
I even tried flashing in this order:
slim rom > fire ice custom kernel > dm verity FED zip > SR5-SuperSU-v2.82-SR5-20171001224502.zip > gapps
These are the files I’m trying to install:
Slim-flounder-7.1.2.build.2.0-STABLE-20180124-0018.zip
open_gapps-arm64-7.1-nano-20190529.zip
FIRE-ICE N K10.7 06-01-2018 21-31-18.zip
Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
What am I doing wrong??????
deloj said:
Hi madbat,
I tried to downgrade/ install lineagos 14.1 Nougat on my nexus 9 from lineagos 15.1 Oreo. But after I reboot to system, the word google stays stuck on screen. It doesn’t boot to the rom. These are the steps I took and the zips with it:
1) First wipe : TWRP > swipe to factory reset > adv.wipe cache/data/system/dalvik > Format data > Reboot to Recovery
2) TWRP > Install > Slim Rom 7.12 / open_gapps-arm64-7.1-nano-20190529.zip / > Reboot on Recovery >
3) TWRP > Install > dm verity FED > SR5-SuperSU-v2.82-SR5-20171001224502.zip > wipe cache & dalvik (ONLY!) & Reboot system
I even tried flashing in this order:
slim rom > fire ice custom kernel > dm verity FED zip > SR5-SuperSU-v2.82-SR5-20171001224502.zip > gapps
These are the files I’m trying to install:
Slim-flounder-7.1.2.build.2.0-STABLE-20180124-0018.zip
open_gapps-arm64-7.1-nano-20190529.zip
FIRE-ICE N K10.7 06-01-2018 21-31-18.zip
Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
What am I doing wrong??????
Click to expand...
Click to collapse
Try wiping system too. And if it gets stuck, I usually force a reboot by holding power till it reboots. Usually works.
Wait.... SuperSU? There's your problem. Magisk dude.
You see it says 2017? Old.
Why not the latest lineage and magisk?
madbat99 said:
Try wiping system too. And if it gets stuck, I usually force a reboot by holding power till it reboots. Usually works.
Wait.... SuperSU? There's your problem. Magisk dude.
You see it says 2017? Old.
Why not the latest lineage and magisk?
Click to expand...
Click to collapse
You said supersu is my problem. But I tried flashing with only slim rom and gapps, no supersu. Still doesnt work.
Also I'm confused by your last question about why I should install the latest lineage. The latest official lineage is 15.1 and you know I'm having an issue with it. Thats why I want to downgrade to lineage 14.1.
I read that the way to downgrade from lineageos 15.1 to lineagos 14.2 is through ADB. But I'm not sure. What do you suggest?
deloj said:
You said supersu is my problem. But I tried flashing with only slim rom and gapps, no supersu. Still doesnt work.
Also I'm confused by your last question about why I should install the latest lineage. The latest official lineage is 15.1 and you know I'm having an issue with it. Thats why I want to downgrade to lineage 14.1.
I read that the way to downgrade from lineageos 15.1 to lineagos 14.2 is through ADB. But I'm not sure. What do you suggest?
Click to expand...
Click to collapse
Official lineage 15.1? Where? I meant 14.1. that's the last official. Still being built unofficially by the official maintainer. In the official thread.
Running it on my Nexus 9. No problems. No issues. Security patches.
I just don't have the update addiction on my n9. My Moto phone has official pie. So I'm good. My tablet is for media consumption.
I have no idea what is happening with your email. No logs, no nothing. I don't even know what email client you're using. Did you log in to it? Instead of restoring a backup.
All sounds flawed. Experimental ROM, data restore, no original log in.... All suspect.
I'm sure you know why it all causes problems, but don't want to start over.
Sometimes, ya just gotta start over. Flashy flashy, kaboom. We all been there. Data restore is an imperfect process. Sometimes you get to the end of your luck and just have to start over.
madbat99 said:
Official lineage 15.1? Where? I meant 14.1. that's the last official. Still being built unofficially by the official maintainer. In the official thread.
Running it on my Nexus 9. No problems. No issues. Security patches.
I just don't have the update addiction on my n9. My Moto phone has official pie. So I'm good. My tablet is for media consumption.
I have no idea what is happening with your email. No logs, no nothing. I don't even know what email client you're using. Did you log in to it? Instead of restoring a backup.
All sounds flawed. Experimental ROM, data restore, no original log in.... All suspect.
I'm sure you know why it all causes problems, but don't want to start over.
Sometimes, ya just gotta start over. Flashy flashy, kaboom. We all been there. Data restore is an imperfect process. Sometimes you get to the end of your luck and just have to start over.
Click to expand...
Click to collapse
Hi madbat,
I answered your question in this link. Please read it bro. Thanks man:
https://forum.xda-developers.com/ne...e-lineagos-15-1-to-14-1-t3934751#post79642010
.
This is a security patch Feb/01/2020 has note 10 wallpaper camera has been completley redone has a whole bunch of tweaks and mods done to it based of bootloader u7 XXU
Big thanks to @Gollo99 for all his hard work on camera
Enjoy more too come as we work on it
But here's a preview
https://drive.google.com/file/d/1piQr7j-jLXEGmYgoxlnp6ot3PRM9hcRj/view?usp=drivesdk
@hooooossamq here you go test away
I'll try it out
Does it work in binary 3 or is it mandatory to upgrade to binary 4?
It should work on u3
I will try it these days and inform if it works
what different this rom with stock? can you list out?
Didn't work for me(U2)
Edit
Forgot to flash my boot.img
Great work @shumway66.
This Rom is ruining very smoothly.
This is how I installed it.
1. Start with existing OneUI.
2. Reboot into TWRP
3. Backup boot, data, system
4. Install this ROM (don't wipe anything)
5. Wipe both caches
6. Restore boot only from the backup from step 3
7. Reboot.
Brilliant result. Thanks
I will let you know more as I go on.
michael13Alv said:
Does it work in binary 3 or is it mandatory to upgrade to binary 4?
Click to expand...
Click to collapse
You might need to flash your patched boot.img after you flash the rom zip
Seems to be working well.
I flashed it over my existing data and then restored my boot sector.
View attachment 4964703
Smart capture is working.
I deleted a few more apps.
View attachment 4964727
physwizz said:
Seems to be working well.
I flashed it over my existing data and then restored my boot sector.
View attachment 4964703
Smart capture is working.
Click to expand...
Click to collapse
yeah still a work in progress lol
excellent
excellent job brother
New camera looks good
L
@shumway66
Will this work with OneUI 2.0?
Solved
[Flash the zip and then my boot.img started and everything but at the time of restarting it appeared to me that only official binaries can be flashed
Returning to stock waiting for a solution for this problem
B3 Patch 1 octuber
]
michael13Alv said:
Flash the zip and then my boot.img started and everything but at the time of restarting it appeared to me that only official binaries can be flashed
Returning to stock waiting for a solution for this problem
B3 Patch 1 octuber
Click to expand...
Click to collapse
This is how I installed it.
1. Start with existing OneUI.
2. Reboot into TWRP
3. Backup boot, data, system
4. Install this ROM (don't wipe anything)
5. Wipe both caches
6. Restore boot only from the backup from step 3
7. Reboot.
Use that method
michael13Alv said:
Use that method
Click to expand...
Click to collapse
That method worked for me.
I'm on U2 June 2019
My patch is October 1/2 I don't remember what it is exactly but it is one of those and my binary is 3
Hi. This is my ROM #4.
It's stable as LOS 14.1.
Tested:
Camera;
USB-OTG;
NFC;
FMRadio;
etc.
Bugs:
- The same as LOS14;
- NFC-HCE(in LOS14.1 that doesn't work either);
- something I haven't found.
How to install:
1) use TWRP 3.5.0.
2) wipe all except internal storage
3) Flash the gapps , magisk.
4) You may also need to reformat sdcard.
5) If gaaps taking too much time for checking for updates, just reboot the tablet.
Change log:
20210316 - initial build.
20210317 - build for karin windy.
Last builds (mirror) are here.
I'm also very grateful to sabar_op for guiding me to build me ROMs in the right way.
If you want to get stock back use Emma than flashtool.
Sources
https://github.com/ResurrectionRemix
https://github.com/LineageOS/android_device_sony_karin_windy
https://github.com/LineageOS/android_device_sony_karin
https://github.com/LineageOS/android_device_sony_kitakami-common
https://github.com/LineageOS/android_kernel_sony_msm8994
The next ROMs I'm gonna build is dotos, viperos and crdroid. If no own wish to test it on karin windy I will build it only for on my own karin.
I got some error when I try use "adb push" to push the ROM file into my SGP712 with TWRP 3.5.
I use TWRP 3.4 instead and installed the ROM successfully.
But after I boot in the system, it will show the error message "Process system isn't responding".
It seems work fine after I reboot.
I usually got device shutdown and reboot issue when I use LineageOS before.
I will test this ROM and see if it would happened.
Thanks for your sharing.
aaa646123 said:
I got some error when I try use "adb push" to push the ROM file into my SGP712 with TWRP 3.5.
I use TWRP 3.4 instead and installed the ROM successfully.
But after I boot in the system, it will show the error message "Process system isn't responding".
It seems work fine after I reboot.
I usually got device shutdown and reboot issue when I use LineageOS before.
I will test this ROM and see if it would happened.
Thanks for your sharing.
Click to expand...
Click to collapse
Have you wiped system dalvik cashe user data? I don't use adb push.
alex009988 said:
Have you wiped system dalvik cashe user data? I don't use adb push.
Click to expand...
Click to collapse
yes, I wiped them before I push the file.
Anyways I tried the ROM but shutdown and reboot issue still exist.
aaa646123 said:
yes, I wiped them before I push the file.
Anyways I tried the ROM but shutdown and reboot issue still exist.
Click to expand...
Click to collapse
And you 100% sure that there are problems with shut down and reboot with my ROM and the lineage 14.1? It doesn't work completely? Can you log issue? I don't have ones with karin.
alex009988 said:
And you 100% sure that there are problems with shut down and reboot with my ROM and the lineage 14.1? It doesn't work completely? Can you log issue? I don't have ones with karin.
Click to expand...
Click to collapse
It shut down and reboot after I used the ROM about 20 minutes.
Just the same as I used LingeageOS18/17.
I send the log to @sabar_op before, but seems not fix issue after.
aaa646123 said:
It shut down and reboot after I used the ROM about 20 minutes.
Just the same as I used LingeageOS18/17.
I send the log to @sabar_op before, but seems not fix issue after.
Click to expand...
Click to collapse
What about los15? My advice to you is to restore the latest stock with Emma(not flashtool) than try again custom ROM. Perhaps you have something broken with mounting partitions. I have another problem with Karin(downloading big game call of duty).
I need someone else to confirm your problem on sgp712.
alex009988 said:
What about los15? My advice to you is to restore the latest stock with Emma(not flashtool) than try again custom ROM. Perhaps you have something broken with mounting partitions. I have another problem with Karin(downloading big game call of duty).
I need someone else to confirm your problem on sgp712.
Click to expand...
Click to collapse
I restore with Emma every time. I don't remember if I tried the los15, is there any special with los15?
aaa646123 said:
I restore with Emma every time. I don't remember if I tried the los15, is there any special with los15?
Click to expand...
Click to collapse
I saw your messages you have that problem since 2018.
Nougat ROMs are the most stable roms for our tablet, based on my experiance with karin at least. I can say that kernelpanics are possible everywhere where root is, both stock and custom. I also faced it on los14 but it happens so rarely, usually when many apps are lunched.
If you have that problem on los14, you'll have it with any my noutgat rom too as I use the same los kernel and edit device and vendor and other stuff if neccessary.
The problem is that I haven't found another sgp712 user who has 20 minute reboot problem on sgp712. I don't know maybe something in the sources are broken for your device or it's hardware problem.
So do you have that problem without gapps installed?
Do you have that problem without root?
Did you try different versions of magisk/supersu?
It's better you to try los15, maybe this one is without the issue for you.
If all above-listed you tried you should take adb log by pc with kernel panic. At least we can identify what cause the problem.