phhusson / treble_experimentations

Notes about tinkering with Android Project Treble
3.32k stars 655 forks source link

Android pie aosp bootloop on cubot j3 #609

Open nonyonah opened 5 years ago

nonyonah commented 5 years ago

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 commented 5 years ago

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

nonyonah commented 5 years ago

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 commented 5 years ago

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

nonyonah commented 5 years ago

mylogfile.txt

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

nonyonah commented 5 years ago

How do I fix it?

proganime1200 commented 5 years ago

https://forum.xda-developers.com/attachment.php?attachmentid=4778117&d=1560748164 try to flash this on twrp

nonyonah commented 5 years ago

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

nonyonah commented 4 years ago

Still not working

phhusson commented 4 years ago

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 commented 4 years ago

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

nonyonah commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

Wait, issue is just boot time?

nonyonah commented 4 years ago

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

nonyonah commented 4 years ago

Any fix for that?

nonyonah commented 4 years ago

Any fix?

Pey-crypto commented 4 years ago

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 commented 4 years ago

So how do you fix it?

Pey-crypto commented 4 years ago

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.. https://github.com/phhusson/treble_experimentations/issues/576 saw it here

Pey-crypto commented 4 years ago

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 commented 4 years ago

Ok