Finally here it is Official Cm13 is up on cyanogenmod blog.Who is ready to test it out
Via:http://www.gammerson.com/2015/11/download-official-cm13-rom-for-nexus-6p.html
meeee ?
Sent from my Nexus 6P using Tapatalk
Someone knows how to update the Vendor and stuff? Right now it is under unknown Vendor and no information about the phone at all
Out of plain curiosity is there a new boot animation as of yet?
Roxas598 said:
Out of plain curiosity is there a new boot animation as of yet?
Click to expand...
Click to collapse
No, there isn't.
---------- Post added at 12:13 AM ---------- Previous post was at 12:13 AM ----------
maurizze said:
Someone knows how to update the Vendor and stuff? Right now it is under unknown Vendor and no information about the phone at all
Click to expand...
Click to collapse
This will get fixed. Give it a day or two.
sam3000 said:
No, there isn't.
---------- Post added at 12:13 AM ---------- Previous post was at 12:13 AM ----------
This will get fixed. Give it a day or two.
Click to expand...
Click to collapse
Thanks for maintaining 6p, are you gonna open any official thread for this ?
I would love to see double tap wake by default with proximity check.
I saw d2w commits, but no commits for proximity check.
please make it soon.
thanks.
Runs great so far, but a few bugs seen:
There is a security related prompt at boot
Initial install crashes if you try to add a screen lock (works fine afterwards)
Lock screen shortcut setting crashes
Anyone get adaway running? i get a "copying of hosts file failed" even though it has root. Or a "s-off needed" if i try the symlink variant.
This is working over the latest stock ROM (MDB08M)
only had to wipe data partition (it asked to do so when trying to install the cm13 zip)
used the latest opengapps pico as the gapps.
I'm coming from Samsung devices where the camera quality suffered on CM ROMs because tge drivers were proprietary. Do the Nexus devices have the same problem on CM or are the drivers more open so the CM devs can get the same camera quality?
21cdb said:
I'm coming from Samsung devices where the camera quality suffered on CM ROMs because tge drivers were proprietary. Do the Nexus devices have the same problem on CM or are the drivers more open so the CM devs can get the same camera quality?
Click to expand...
Click to collapse
The Google camera drivers are totally open source so it's exactly the same camera as stock.
Sent from my Nexus 6P using Tapatalk
Yea I want to try it out but I'll wait a month or so to try it out.
RohanAJoshi said:
Thanks for maintaining 6p, are you gonna open any official thread for this ?
I would love to see double tap wake by default with proximity check.
I saw d2w commits, but no commits for proximity check.
please make it soon.
thanks.
Click to expand...
Click to collapse
Appreciate the thanks but, really, I'm just a cm contributor.
CM settings code was refactored (internally) for 13.0 so settings config is incomplete. This is why, for eg, buttons settings section shows hardware keys that don't exist and why color LED notification management is not enabled. It should get fixed / updated within the coming weeks.
what are you guys flashing for Google Apps?
edit: Just found this:
https://wiki.cyanogenmod.org/w/Google_Apps
boxcar8028 said:
what are you guys flashing for Google Apps?
edit: Just found this:
https://wiki.cyanogenmod.org/w/Google_Apps
Click to expand...
Click to collapse
I used the Opengapps the super package
How are you getting this to flash and boot? How long until it boots to the setup screen? I'm having one hell of a time getting this to boot. I'm stuck on the 'google' logo five minutes straight. I go into twrp and wipe cache, dalvik, data, and sytem and then flash the rom.zip and then gapps and it freezes at 'google' as it is booting Is there a trick here to get it to boot? Do I need to flash their recovery.img that they supply to get it to work?
tdamocles said:
How are you getting this to flash and boot? How long until it boots to the setup screen? I'm having one hell of a time getting this to boot. I'm stuck on the 'google' logo five minutes straight. I go into twrp and wipe cache, dalvik, data, and sytem and then flash the rom.zip and then gapps and it freezes at 'google' as it is booting Is there a trick here to get it to boot? Do I need to flash their recovery.img that they supply to get it to work?
Click to expand...
Click to collapse
It should work after that, I don't know
tdamocles said:
How are you getting this to flash and boot? How long until it boots to the setup screen? I'm having one hell of a time getting this to boot. I'm stuck on the 'google' logo five minutes straight. I go into twrp and wipe cache, dalvik, data, and sytem and then flash the rom.zip and then gapps and it freezes at 'google' as it is booting Is there a trick here to get it to boot? Do I need to flash their recovery.img that they supply to get it to work?
Click to expand...
Click to collapse
i'm having the exact same problem.. i've tried a couple times, and it seems to not want to boot after i've installed gapps.. kind of a bummer.
tdamocles said:
How are you getting this to flash and boot? How long until it boots to the setup screen? I'm having one hell of a time getting this to boot. I'm stuck on the 'google' logo five minutes straight. I go into twrp and wipe cache, dalvik, data, and sytem and then flash the rom.zip and then gapps and it freezes at 'google' as it is booting Is there a trick here to get it to boot? Do I need to flash their recovery.img that they supply to get it to work?
Click to expand...
Click to collapse
Here's a rather intrusive method (in that it will wipe all your storage) but it should work for everyone:
1) Backup any existing data you want to keep and copy it off the device (pictures etc).
2) Download the stock google image for build MDB08M https://developers.google.com/android/nexus/images?hl=en#angler
3) Unpack the google image and run flash-all with the device in fastboot mode. This will nuke everything on your device. However, it will also ensure you have a vanilla /vendor partition and that /data is formatted correctly (I don't think TWRP is currently formatting internal storage correctly with respect to encryption parameters).
4) Reflash TWRP (whilst still in fastboot) and then boot into recovery.
5) Now install the latest cm nightly and then one of the arm64 variants of android 6.0 opengapps:
http://opengapps.org/?api=6.0&variant=mini&arch=arm64
(I personally think mini is a good choice but it doesn't really matter.)
I find using adb sideload is easier than copying zips onto the device and then installing.
6) Factory reset (in TWRP). (Don't tick any other options - just plain factory reset.)
7) Reboot.
CM splash screen ought to last no longer than around 5 mins.
Just flashed CM13. Install went fine. Getting an error when booting " There's an internal problem with your device. Contact your manufacturer for details". Set up crashes when trying to set up fingerprint screen lock but works when adding it via settings. will update after using it for a few days.
mo123456789 said:
Just flashed CM13. Install went fine. Getting an error when booting " There's an internal problem with your device. Contact your manufacturer for details". Set up crashes when trying to set up fingerprint screen lock but works when adding it via settings. will update after using it for a few days.
Click to expand...
Click to collapse
Common problem. Just flash the latest vendor image which should be M
Sent from my Nexus 6P using Tapatalk
Related
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
Make sure to use Joker's Clockworkmod recovery, named cwm-v3, here.
Thanks gollyzila, I am using the Jokersax CWMv3 recovery image at this time. I meant to mention that earlier in my first post.
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
try pulling the battery and then booting again. if that doesn't work flash 0.4.0 first like ccallahan suggested
CCallahan said:
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
Click to expand...
Click to collapse
wala! that worked. thank you very much CCallahan. much appreciated.
i was having the same problem heres what i did i factory reset cleared cache/dalvic installed 3.1 then reboot wipe cache/dalvic then i flashed 4.4 over it
when you first flash any cm9 fresh, not over a backup, you must flash twice. Joker has mentioned this many times that the scripts he has for the install have to run twice in order to fully install.
1. Flash cm9 (whatever beta you want)
2. Reboot recovery (in advanced in cwm)
3. Flash rom again
4. Flash gapps
5. Boot to system
You should be good to go now
sent from my Kick Ass MIUI MoPho using XDA premium
Hi,
I was running BeanStalk-4.4.270 03/18/14 by zymphad. Im not sure what the kernel was.
I tried flashing the ROM by ronasimi in this thread.
The ROM that i picked was cm-11-20140817-UNOFFICIAL-geeb & the kernel was gbx-kernel-lights-CM11.0-CAF.zip. Apart from this i picked the Google Stock package of PA GApps from here.
For flashing i did the following :-
1. backed up all my apps using TB from BeanStalk.
2. loaded the ROM, the kernel & GApps zip files into a folder on my sdcard.
3. rebooted into recovery(TWRP 2.6.xx), backed up my original ROM and lined up all the three flashable zips and flashed them. (The flash was successful)
4. Then i rebooted into system. But after reaching the home screen, i was getting errors "Unfortunately, the process com.android.systemui has stopped" & "Unfortunately, the process com.android.phone has stopped". I remembered it might be because i forgot to wipe dalvik & cache.
5. I again rebooted into recovery, wiped dalvik & system cache and tried booting into system. It was still giving the same issues.
6. I tried restoring my old ROM's backup. Surprisingly even that wouldn't solve the issue.
7. So i again flashed the CM11 ROMs. But this time, the boot process is getting stuck at the boot animation.
My Qs are as follows:-
1. Did i miss anything or do something that is not recommended (or maybe even dangerous)?
2. What should be my next step in resolving this issue?
Any help appreciated.
gautam_k said:
Hi,
I was running BeanStalk-4.4.270 03/18/14 by zymphad. Im not sure what the kernel was.
I tried flashing the ROM by ronasimi in this thread.
The ROM that i picked was cm-11-20140817-UNOFFICIAL-geeb & the kernel was gbx-kernel-lights-CM11.0-CAF.zip. Apart from this i picked the Google Stock package of PA GApps from here.
For flashing i did the following :-
1. backed up all my apps using TB from BeanStalk.
2. loaded the ROM, the kernel & GApps zip files into a folder on my sdcard.
3. rebooted into recovery(TWRP 2.6.xx), backed up my original ROM and lined up all the three flashable zips and flashed them. (The flash was successful)
4. Then i rebooted into system. But after reaching the home screen, i was getting errors "Unfortunately, the process com.android.systemui has stopped" & "Unfortunately, the process com.android.phone has stopped". I remembered it might be because i forgot to wipe dalvik & cache.
5. I again rebooted into recovery, wiped dalvik & system cache and tried booting into system. It was still giving the same issues.
6. I tried restoring my old ROM's backup. Surprisingly even that wouldn't solve the issue.
7. So i again flashed the CM11 ROMs. But this time, the boot process is getting stuck at the boot animation.
My Qs are as follows:-
1. Did i miss anything or do something that is not recommended (or maybe even dangerous)?
2. What should be my next step in resolving this issue?
Any help appreciated.
Click to expand...
Click to collapse
Flash TWRP 2.7.1 or Philz's touch CWM
than do a clean install
Wipe data and Format system
Flash any ROM (here CM 11 ) and Gapps
Flash proper kernel ( for CM 11 old Gprij-X kernel or neighborhood kernel)
Wipe cache and delvick cache
reboot profit
For more info :
ShoaibAhmed said:
Flash TWRP 2.7.1 or Philz's touch CWM
than do a clean install
Wipe data and Format system
Flash any ROM (here CM 11 ) and Gapps
Flash proper kernel ( for CM 11 old Gprij-X kernel or neighborhood kernel)
Wipe cache and delvick cache
reboot profit
For more info :
Click to expand...
Click to collapse
I tried flashing using TWRP but the flash failed. then I saw the video and thought of giving philz touch cwm a try. it worked like a charm. Thanks a lot for the help. For kernel I flashed gprojx-kernel-lights-CM11.0-CAF-20140414.zip. Everything seems to be working now. Only thing is that I can't seem to turn off NFC. Every time I deselect the check box, go somewhere else and come back, the NFC check box is already checked.
Any tips on that? It's eating up my battery
gautam_k said:
I tried flashing using TWRP but the flash failed. then I saw the video and thought of giving philz touch cwm a try. it worked like a charm. Thanks a lot for the help. For kernel I flashed gprojx-kernel-lights-CM11.0-CAF-20140414.zip. Everything seems to be working now. Only thing is that I can't seem to turn off NFC. Every time I deselect the check box, go somewhere else and come back, the NFC check box is already checked.
Any tips on that? It's eating up my battery
Click to expand...
Click to collapse
Reboot once and then try to turn off NFC , it will work.
ShoaibAhmed said:
Reboot once and then try to turn off NFC , it will work.
Click to expand...
Click to collapse
Awesome! Thanks a lot man.
One last Q p)- I spent almost 30mins combing through settings but I couldn't find a 3G/2G switch. Is it hidden somewhere or it doesn't exist yet in CM11?
gautam_k said:
Awesome! Thanks a lot man.
One last Q p)- I spent almost 30mins combing through settings but I couldn't find a 3G/2G switch. Is it hidden somewhere or it doesn't exist yet in CM11?
Click to expand...
Click to collapse
Settings--->Mobile networks--->Prefered network type--> change it from "LTE" to 2G/3G
ShoaibAhmed said:
Settings--->Mobile networks--->Prefered network type--> change it from "LTE" to 2G/3G
Click to expand...
Click to collapse
i am actually looking for a shortcut for the same in notification draweer or quick settings pulldown...apologies for not making it clear before.
gautam_k said:
i am actually looking for a shortcut for the same in notification draweer or quick settings pulldown...apologies for not making it clear before.
Click to expand...
Click to collapse
Found the shortcut in Settings> Notification Drawer> Quick settings panel> Tiles & layout> Network mode
For some reason i was thinking that this will lead me to the GSM/WCDMA switch.
Flash this recovery on the community build: http://forum.xda-developers.com/devdb/project/dl/?id=20236
And then flash the super SU file via recovery:
https://www.androidfilehost.com/?fid=24591000424944601
Let me know if this works or you need any help ?
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
From other posts in other topics it seams that it's the only twrp version that installs OOS 3.1.1
Sent from my ONE E1001
trendchanger said:
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
yes this is working
Jab_ said:
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
Click to expand...
Click to collapse
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Exodusche said:
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Click to expand...
Click to collapse
Maybe the problem is not xposed itself, maybe the issue is related to an specific module. I'll try one by one tomorrow and see what happens, thank you!
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Exodusche said:
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Click to expand...
Click to collapse
I know what the problem was. My xposed zip was correct. As I thought, it was because of a module. "Android N-fy", in recents, I just had to uncheck quick switch and change no recent image and that was it. I don't know if that module is optimized for this oos especific build, because in settings of the phone, the module does not change as much as in lollipop oos. Thank you tho
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Worked fine. Thanks OP.
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
TarushS said:
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
Click to expand...
Click to collapse
Oh lol, glad this helped
StraightEdgeKid said:
Worked fine. Thanks OP.
Click to expand...
Click to collapse
Np?
Sachin7843 said:
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Click to expand...
Click to collapse
What exactly are you looking to do?
marwan2704 said:
What exactly are you looking to do?
Click to expand...
Click to collapse
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Sachin7843 said:
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Click to expand...
Click to collapse
Make sure you have both .zip files on your phone, clean flash 3.1.1 then boot it up. If you don't like it, you can go back to 2.2.2 via stock recovery anytime. You don't even need twrp unless you want to root, install Xposed or backup.
might be a bit off-topic but...
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
error23 said:
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
Click to expand...
Click to collapse
Sounds like you forgot to wipe data. Wipe system, data, cache and just flash 3.1.1. As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Exodusche said:
As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Click to expand...
Click to collapse
It's not the place, but I can confirm that it didn't work for me. I still have the drain from time to time.
And if I don't have the Wifi drain I have a service Google Play service drain (33% for today's charge for example...).
And sometimes, I even had the wifi drain with Wifi completly switched off...
I am on miui 8.1.4.0 rooted rn3p. So my question is can i use dual boot patcher and dual boot lineage os 14.1
Anyone ??
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots, go back into TWRP and check your log again.
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
Thanks buddy trying it now
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
One more thing its a bit off topic but still i am using radon kernel and i am seeing that when i sweep on the black screen it unlocks how to turn this off as its consuming a lot of battery
Androbots said:
One more thing its a bit off topic but still i am using radon kernel and i am seeing that when i sweep on the black screen it unlocks how to turn this off as its consuming a lot of battery
Click to expand...
Click to collapse
Umm... not sure what you're talking about. Maybe DT2W? I tried out Radon, but I haven't tried that feature. I think you just need to reflash Radon and choose default options. If that doesn't work for you, just reflash MIUI, it will get rid of Radon.
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
Filip013 said:
Umm... not sure what you're talking about. Maybe DT2W? I tried our Radon, but I haven't tried that feature. I think you just need to reflash Radon and choose default options. If that doesn't work for you, just reflash MIUI, it will get rid of Radon.
Click to expand...
Click to collapse
Yes d2tw I was talking about that only and now i have disabled it using kernel audiutor as it was consumping a lot of abttery thanks anyway
Androbots said:
Yes d2tw I was talking about that only and now i have disabled it using kernel audiutor as it was consumping a lot of abttery thanks anyway
Click to expand...
Click to collapse
OK. Let me know if you manage to get DBP to work.
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Yup
Edit: i forgot that i checked twrp log (my bad)unfortunately it is encrypted so can't use dbp as of now but next month i might factory reset on miui and then use super su to stop encryption. Hope it works...
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Ok so here is what i got in the results of this experiment :
I was able to patch minz1 lineage os and gapps pico 7.0 and then booted to zcx and flashed both files i removed the fingerprint and any kind security measures on miui and i flashed both files and it was successful!!!
But now i am not able to boot to either miui or lineage os!!!
Conclusion: DO NOT TRY THIS!!!
Androbots said:
Ok so here is what i got in the results of this experiment :
I was able to patch minz1 lineage os and gapps pico 7.0 and then booted to zcx and flashed both files i removed the fingerprint and any kind security measures on miui and i flashed both files and it was successful!!!
But now i am not able to boot to either miui or lineage os!!!
Conclusion: DO NOT TRY THIS!!!
Click to expand...
Click to collapse
Weird... It seems to me that you are still encrypted. Have you tried flashing DualBootUtilities and switching to MIUI that way? It is possible that you messed up your primary ROM boot image, I think that happened to me once. Whatever the case, reflashing MIUI should allow you to boot into MIUI.
---------- Post added at 04:08 PM ---------- Previous post was at 04:03 PM ----------
Androbots said:
Yup
Edit: i forgot that i checked twrp log (my bad)unfortunately it is encrypted so can't use dbp as of now but next month i might factory reset on miui and then use super su to stop encryption. Hope it works...
Click to expand...
Click to collapse
I didn't see this post until now. Well, of course you can't use DBP when you're encrypted. If you want to try DPB, you have to format data.
Filip013 said:
Weird... It seems to me that you are still encrypted. Have you tried flashing DualBootUtilities and switching to MIUI that way? It is possible that you messed up your primary ROM boot image, I think that happened to me once. Whatever the case, reflashing MIUI should allow you to boot into MIUI.
Click to expand...
Click to collapse
Flashing back miui kicked me out of the situation and btw i backed up the boot.img as well as tried switching roms none worked and also it was glitching zcx a bit.
Its quite irritating seeing xiaomi and miui enforcing so many security measures a bad day for people who like to customize things a lot!
Androbots said:
Flashing back miui kicked me out of the situation and btw i backed up the boot.img as well as tried switching roms none worked and also it was glitching zcx a bit.
Its quite irritating seeing xiaomi and miui enforcing so many security measures a bad day for people who like to customize things a lot!
Click to expand...
Click to collapse
OK. Good to know that at least you have a working system now. I only experienced issues with booting MIUI after I flashed a custom kernel on MIUI and forgot to update the kernel in DBP app, but like we established flashing MIUI solves the problem.
But again, there's no use in experimenting with DBP until you format data. So please report back when you get around to doing that.
As for Xiaomi policies, I don't know the details, but I don't think it's their fault. It seems that Google can be very strict when certifying devices and allowing the OEMs to include Gapps. Google forces OEMs to ship phones with locked bootloaders and forced encryption.
Filip013 said:
OK. Good to know that at least you have a working system now. I only experienced issues with booting MIUI after I flashed a custom kernel on MIUI and forgot to update the kernel in DBP app, but like we established flashing MIUI solves the problem.
But again, there's no use in experimenting with DBP until you format data. So please report back when you get around to doing that.
As for Xiaomi policies, I don't know the details, but I don't think it's their fault. It seems that Google can be very strict when certifying devices and allowing the OEMs to include Gapps. Google forces OEMs to ship phones with locked bootloaders and forced encryption.
Click to expand...
Click to collapse
Anyways I will be resting my device next month maybe and then I can try and let u know
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Ok so i installed epic rim today and i erased data 3times here are results:
Data erase#1 reboot recovery data is is still encrypted
Installing epic rim did not help either flashed super su 3 times still data is encrypted!!!!
What to do???
Androbots said:
Ok so i installed epic rim today and i erased data 3times here are results:
Data erase#1 reboot recovery data is is still encrypted
Installing epic rim did not help either flashed super su 3 times still data is encrypted!!!!
What to do???
Click to expand...
Click to collapse
The order of steps is very important.
1st step: Boot to recovery.
2nd step: Format data (not wipe and I don't know what you mean by erase).
3rd step: Flash ROM (Epic ROM should be good, but it also works for Global Stable and others).
4th step: Flash SuperSU.
5th step: Reboot system.
Filip013 said:
The order of steps is very important.
1st step: Boot to recovery.
2nd step: Format data (not wipe and I don't know what you mean by erase).
3rd step: Flash ROM (Epic ROM should be good, but it also works for Global Stable and others).
4th step: Flash SuperSU.
5th step: Reboot system.
Click to expand...
Click to collapse
Gotcha that means in wipe section i have to go to format data right??
Androbots said:
Gotcha that means in wipe section i have to go to format data right??
Click to expand...
Click to collapse
Yes. Good luck.
Filip013 said:
Yes. Good luck.
Click to expand...
Click to collapse
See I have setup everything on epic rom deleting everything again will be tough I will try it next month when I am bored with epic rom
Androbots said:
See I have setup everything on epic rom deleting everything again will be tough I will try it next month when I am bored with epic rom
Click to expand...
Click to collapse
LOL. Fine. Next month then.
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.