Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android pie aosp bootloop on cubot j3 #609

Open
nonyonah opened this issue Jul 18, 2019 · 21 comments
Open

Android pie aosp bootloop on cubot j3 #609

nonyonah opened this issue Jul 18, 2019 · 21 comments

Comments

@nonyonah
Copy link

I have a cubot j3 with android Oreo go edition . I installed the latest aosp pie version from here but it seems that it's been on the android logo for a long time till I have a switch it off. I installed the 8.1 version and it booted but the Google certification is an issue. I really wanna try the pie rom, I don't know if it's cause of the RAM or something, help support it. It's an mtk 6580m device

@proganime1200
Copy link

https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/

@nonyonah
Copy link
Author

What about the "being stuck on the android logo part" when I install aosp 9. How do I fix that?
Besides the Oreo rom is actually Oreo go with the original Google apps installed, I wanted the main one

@proganime1200
Copy link

proganime1200 commented Jul 19, 2019

post the the report log the only way to grab them is with the command I gave :

  • from a computer : adb shell cat /proc/last_kmsg > log.txt
  • inside TWRP, in terminal, cat /proc/last_kmsg > /sdcard/log.txt (maybe sdcard should be changed to another location)

@nonyonah
Copy link
Author

nonyonah commented Jul 19, 2019

mylogfile.txt

this is it
sorry its coming late, i was at work

@nonyonah
Copy link
Author

How do I fix it?

@proganime1200
Copy link

@nonyonah
Copy link
Author

What does it do?
I'll check it out later

@nonyonah
Copy link
Author

nonyonah commented Aug 2, 2019

Still not working

@phhusson
Copy link
Owner

phhusson commented Aug 4, 2019

You need to do a proper factory reset when switching ROM, with stock recovery if needed.
The logs shows that you didn't properly factory reset (I'm not totally sure it's the issue though, but logs are noisy because of it anyway)

@phhusson
Copy link
Owner

phhusson commented Aug 4, 2019

Also, you cut the log when adb stopped, you should have re-run adb after it to another logfile to have both logs.

@nonyonah
Copy link
Author

nonyonah commented Aug 4, 2019

So how do I properly factory reset? I followed all the steps and besides I managed to boot up descendant os and your rom too but that long boot up time is always the issue there

@nonyonah
Copy link
Author

nonyonah commented Aug 4, 2019

I'll try to run another log when I have the time, thanks for your ROMs though. It gives hope to many unsupported devices like mine

@phhusson
Copy link
Owner

phhusson commented Aug 4, 2019

Wait, issue is just boot time?

@nonyonah
Copy link
Author

nonyonah commented Aug 5, 2019

Yes! It takes up to at least 10 mins before booting up

@nonyonah
Copy link
Author

nonyonah commented Aug 5, 2019

Any fix for that?

@nonyonah
Copy link
Author

nonyonah commented Aug 7, 2019

Any fix?

@Pey-crypto
Copy link

I have an alcatel 1x ,This also takes more than 10 -15 mins to boot up..Also sometimes it never boots up.
Looking through the logs I think the mtk audio hal service is extending the boot time.

@nonyonah
Copy link
Author

So how do you fix it?

@Pey-crypto
Copy link

Pey-crypto commented Sep 19, 2019

reboot to the custom recovery and enable adb.....
then pull the build prop file from the system folder and add the this line.
ro.audio.ignore_effects=true
fixes the long boot time..
#576
saw it here

@Pey-crypto
Copy link

I read the log file and looks like mtk audio hal service is not the problem.... run adb logcat after the device reports it has booted in the log.Post that log

@nonyonah
Copy link
Author

Ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants