Hello. I used to have cm13+radon kernel. For some time after, I flashed a newer version of cm13, then when speaking on the phone, I experience call drops. I call someone, it accepts the call, but after some seconds (sometimes it's 2 secs and sometimes it's 30 secs) the call drops. But
Then I flashed an older version of cm13 + flashed radon again. But same thing! Then I flashed the rom again (no custom kernel this time) and no problem with calls. Fast forward, yesterday I flashed RR 5.8.0 + agni kernel+cam libs. Same thing happened again. I tried some cm14 firmware, but nothing changed. (actually I bricked the phone.)
Anyway now I am on RR 5.7.4 (nougat roms are buggy without kernels) and no custom kernel. What might be the problem? I can't flash custom kernels.
First thing i would suggest is installing the complete stock MIUI ROM through fastboot, and running that a few days to see if you still get the same issues.
If you don't, then you know it is something that is being done when you install the CM roms. Could be a firmware that you need to flash, could be something with CM or the rom's themselves, or the custom kernels.
You have to do process of elimination here.
goofball2k said:
First thing i would suggest is installing the complete stock MIUI ROM through fastboot, and running that a few days to see if you still get the same issues.
If you don't, then you know it is something that is being done when you install the CM roms. Could be a firmware that you need to flash, could be something with CM or the rom's themselves, or the custom kernels.
You have to do process of elimination here.
Click to expand...
Click to collapse
Without flashing kernel, there wont be a problem i guess because, right now I dont have the issue. (rr 5.7.4 no custom kernel). It shouldnt be kernel end, because i havent heard anyone beside me experiences this.
I have now worked with 4 Thor devices - two I've owned for quite a while and 2 I've purchased used as media streamers for friends. Every one of them reboots itself with screen autorotation on when using either the kk-fire-nexus-rom or the CM-11 for Safestrap ROM. It doesn't always happen immediately, but always within a few minutes of use. None of the LP, MM, or N-based custom ROMs I've tried have ever done this. I'd ideally like to load one of those KK-based ROMs for bluetooth support.
I've prepared each tablet the same way, every time (starting point was always FireOS 4.5.5.1):
1. Root the device and then copy the custom ROM to it
2. Grab the serial/manfid
3. Flash TWRP (either 3.0.2.0 or 3.0.0.1) and the vulnerable bootloader with the dd command
4. Successfully unlock the bootloader
5. From TWRP, wipe everything except internal storage, then install the ROM
6. Wipe cache/dalvik, reboot
This is driving me nuts, since I see users so satisfied with these KK ROMs and little mention of this as an issue. Can anyone see what I'm missing? Thanks.
Bawdy George said:
I have now worked with 4 Thor devices - two I've owned for quite a while and 2 I've purchased used as media streamers for friends. Every one of them reboots itself with screen autorotation on when using either the kk-fire-nexus-rom or the CM-11 for Safestrap ROM. It doesn't always happen immediately, but always within a few minutes of use. None of the LP, MM, or N-based custom ROMs I've tried have ever done this. I'd ideally like to load one of those KK-based ROMs for bluetooth support.
I've prepared each tablet the same way, every time (starting point was always FireOS 4.5.5.1):
1. Root the device and then copy the custom ROM to it
2. Grab the serial/manfid
3. Flash TWRP (either 3.0.2.0 or 3.0.0.1) and the vulnerable bootloader with the dd command
4. Successfully unlock the bootloader
5. From TWRP, wipe everything except internal storage, then install the ROM
6. Wipe cache/dalvik, reboot
This is driving me nuts, since I see users so satisfied with these KK ROMs and little mention of this as an issue. Can anyone see what I'm missing? Thanks.
Click to expand...
Click to collapse
Intriguing - I used this ROM for nearly a year as my daily driver; rock solid with frequent rotations over hundreds of hours. That device (and all other HDXs in my portfolio) never saw FireOS v4; bootloader unlock occured while still on v3. Will be giving this some thought over the next few days.
Davey126 said:
Intriguing - I used this ROM for nearly a year as my daily driver; rock solid with frequent rotations over hundreds of hours. That device (and all other HDXs in my portfolio) never saw FireOS v4; bootloader unlock occured while still on v3. Will be giving this some thought over the next few days.
Click to expand...
Click to collapse
Thanks for the reply. Odd, huh? Though... I did just try ggow's 4.05 ROM and that one autorotates just fine on the Thor I'm currently working on. I'll probably just go with that one or the newer with locked rotation. They're both solid, support Xposed, and app compatibility isn't an issue for my use cases... yet. If only BT wasn't such a challenge on later versions, as that LineageOS ROM is looking really really good...
Never seen that error myself , 5 hdx's unlocked either 4.5.5.1 or 4.5.5.2 all with Nexus KK on them. Another two ready to be unlocked when I've time.
Maybe you've been unlucky and downloaded slightly corrupted files that appear to flash ok. Maybe check the hash value of them ?
Suggestion of a stable custom ROM and additional info how to "cleanly" install it.
Hello to the community.
I need your help in choosing a stable custom ROM and some info on the steps on how to make a clean install.
I was using a galaxy S3 i9300 with CM11 and TWRP 2.7, 2 years ago. I bought a used htc m8 and put the S3 on the drawer. Last year i turned it on again and used it some time. I checked for updates and without thinking it, i installed cm 13(snapshot). After restarting it, i had the problem with the " trebuchet stopped" and "google play services stopped".After that, i did sth that i don't remember and had the flashing(boot loop?) twrp logo and not being able to boot to the phone. And i put it again in the drawer. Now i want to give it to my little brother and today i took it out again.
Through terminal and adb i booted the phone with the "reboot" command but had the "trebuchet + google play stopped" message again. After some time fiddling around, i flashed the latest version of TWRP with Odin, thinking that i could solve the problem like that but the phone is stuck on the CM logo trying to boot. Even if it boots i think it will show these 2 messages all the time(but it doesn't boot) .
So i want your advice on choosing a good and stable custom ROM to flash, possibly with Odin. The language will be in english and i don't care if it's Android 6 or 7 or 5 as long as it's stable. He will use the phone for basic stuff and not sth too extreme. I remember using CM11 without issues but i know that now there are lots of others roms. Also i want to make the cleanest install to minimise the possibilities of crashes and to give him a clean from everything, phone. But i have forgotten some steps in TWRP.
Thank you in advance and i'm waiting for your suggestions and advice.
The last official stock firmware is probably best as it is the most stable and he won't be able to break it unlike with custom roms.
Beamed in by telepathy.
Hi,
I am running RR 5.8.3, v. from 23-04-17.
I was forced to set fluencetype for the past few flashes to null or something, because otherwise I did not have sound during calls.
Right now the call quality is unbearably bad. It was not THAT bad on older ROMs, before I had to disable this fluence-thingie.
I want to upgrade the ROM, but what else am I supposed to improve the voice quality? I could not find a decent source.
Factory reset -> VoLTE patch -> RR ROM -> GAPPS?
Anything else? Some people wrote "updade your firmware" - how am I supposed to interpret it? Install MIUI Rom? So, like flash it from TWRP and replace it with RR 2 minutes later? I am alergic to MIUI.
This topic kind of explains it, but links are down and content might be outdated:
https://forum.xda-developers.com/redmi-note-3/how-to/android-n-permanent-volte-fix-10000-t3541922
Up
Up.
Right now I am stuck on a bootloop with rom's logo. I can access TWRP and flash stuff just fine, but I cannot load the system. Restoring from backup has failed.
I have installed 7.7.7 firmware - https://www.androidfilehost.com/?fid=673368273298969813
and booted to the system. It did not recognize my PIN and locked my card. Unlocked it with PUK on another device, but still the same.
Flashed newest RR with GAPPS and reflashed the firmware. Bootlooping begun.
Tried different ROMs, tried a different firmware - https://www.androidfilehost.com/?fid=673368273298969055
What should be the "next step"?
I was able to fix it, but man this was my last flash of this device. My next step was to brick the device, had to start from stratch after that. Never had so many different issues... I will rot on current ROM till Pixel 2 arrives.
Hey guys,
Newbie here. I am very excited about my new yet to be received phone - X829 using EUI 5.8.016S (Stable).
I care about call quality, camera quality, sound quality using the CDLA technology headphones (in this order).
I don't consider myself a heavy user - I talk maybe 30 mins per day maximum, light web browsing, no gaming...
Should I stick to the stock rom supplied EUI 5.8.016S or is it worth upgrading to something else? Like, will a custom ROM yield better call quality, camera quality and sound quality than the stock rom?
Thanks!
Andrei
Hi, i am also a X829 user and i would suggest you to try recently released EUI 6.0.030s, which has great battery life and network receiving, of course quite stable.Camera quality is also good.
This one is the same rom modified by CrisBallGreece that includes system adblocker by default and preinstalled magisk manager, removed unnecessary leeco apps and chinese garbage apps.
Here is the link:https://drive.google.com/file/d/17dVqqd_kRZol6ORhvs_Ubri7xNldRLvw/view
Google apps : https://drive.google.com/file/d/1bcmKY1yaoVAnLViL0aSabAdpjK6jpn9x/view
Hi,
Thanks for the reply. How do I get the 'cleaned-up' version installed? Not familiar with either super su or magisk. What is the easiest way to go about doing this? The threads I found make reference to super su but can't download it from the official website. Sorry if this was already addressed in a different thread...
Thanks a lot!
Follow this link :
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
First of all, you should unlock your bootloader and flash twrp (a custom recovery mode, allows you flash rom).
Download rom and gapps then put them to your device, backup your data.Reboot to recovery mode.Press wipe - wipe data, go back and press install - find the rom you copied and flash it.Once the phone booted, go back to recovery and flash gapps in the same way then reboot.That's it.
This is the only way to flash any type of rom.
Btw, magisk is a root manager like the supersu, gives you root access of the system.
Hi,
Thanks for the very informative post. I got my phone yesterday and started to play with it As expected, I had some hard time installing the EUI 6 CBG version. I think it's because I installed a very recent (if not the most recent) version of TWRP...From memory, the one I installed is 3.2.2...Anyhow, EUI seemed to install fine and I got the success message displayed in TWRP along with the note 'phone will reboot in 5 seconds' or something like that - which never happened.
I then installed Lineage OS 15 Oreo because I didn't know how to downgrade TWRP.
So do you think that the problem I had was because of the TWRP version I used? how does one downgrade that?
Also, I installed the Gapps (https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577) but Google services gives an error message...'Google stopped working'. Is there a workaround for that?
Thanks!
Andrei
Hi mate,
Right after that " phone will reboot ..." note, you should have rebooted the device by pressing and holding the power button for 8-9 secs and it would be fine.
No, latest twrp version works fine and is compatible with this firmware.
Hmm, you can try to delete the app data of google play services.Have you flashed the los 15 with full wipe ?
Btw los 15 is not mature enough.It still has some battery consumption problems and the battery life lasts not as long as EUI's. + I don't know if it has CDLA sound mod but it doesn't contain dolby digital sound.
Hi,
I believe I did a full wipe (dalvik, cache, system, data).
I will try again to flash EUI 6 by CBG tonight.
The workaround for gapps was to flash them at the same time with LOS 15. Previously I flashed LOS 15, rebooted into the system, went back to recovery twrp and then flashed the gapps.
Thanks!
Yeah, flashing the gapps with rom in a row is not a workaround, its a must-to-do.Unfortunately i forgot to mention this to you.Apologises..
Great, thanks a lot! it worked. I'm getting used to it right now. Will play with this ROM for a couple of weeks and then try something else...I was thinking SLIM7...any thoughts on it? have you tried it? any red flags?
Thanks!
I am also thinking to move that rom, but later.Well its the final version so no bugs.But i don't know if it supports cdla sound mod, do you know ?
Drollach Gûntar said:
I am also thinking to move that rom, but later.Well its the final version so no bugs.But i don't know if it supports cdla sound mod, do you know ?
Click to expand...
Click to collapse
Not sure if it supports CDLA...I tried this rom briefly the other day and I had a hard time with the camera...battery seemed to deplete quite fast, but I'm sure it can improved with different settings, greenify, etc...try it and let me know if you like it.
Which other roms have you tried?
Thanks!
Most non-eui roms will have slightly worse battery life making greenify an absolute must.
But if you want a non-eui rom (like me, I just hate eui) I recommend lineage 15.1 or du12 by infrag(my current rom).
Hi man, after a long time, I had a change to try different rom, named mokee 7.1.2 (nougat).Well, it's not bad, performance is excellent, not a single lag at all. Also the battery backup is good, not perfect as EUI but acceptable.
Pros of this rom are, it's being updated in a nightly period and Android security patch is dated as august 5 2018 !
You may check it out if you are interested..
Regards.
I am also on DU12 thinking to try 1 of Android P roms, is it time or to wait ?
Milanche78 said:
I am also on DU12 thinking to try 1 of Android P roms, is it time or to wait ?
Click to expand...
Click to collapse
Try Aex Treble Pie, you will be satisfied.