Related
Hello and thank you for viewing my thread!
To start, my device is the OnePlus One, and i am running the latest Release of CyanogenMod 13 with the Latest Lightning Kernel for it's kexec/hardboot patch
I have tried multiple times, installing the multirom files, as well as flashing a factory image and flashing from a fresh install. Nothing seems to work.
The exact problem would be, even after performing the inject boot sector action, multiboot or the boot menu fails to appear.
I have no idea how to view kernel logs or anything of the sort. However i will gladly provide any logs or files if needed! Ill just have to figure them out is all.
Any help is greatly appreciated. Thank you in advance!
Edit:
1. I think i have the kernel ruled out as the problem as i have already tried a modified stock kernel, as well as bouffla's kernel.
2. The rom also doesnt seem to be the problem as i have tried both COS 12.1 and CM 13
3. The recovery seems to be ruled out as well. I rolled back to a previous version of TWRP and still have the same issue, no multiboot menu after proper installation.
4. This is really confusing. I even tried using the files built into the multirom manager application and that fails as well.
P.S. (on a semi-unrelated note)
I currently have a strong feeling it is a very low level issue (at least for my experience) due to the fact that kali nethunter is also failing to install and causing my device to brick every time i attempt an install.
Disclaimer
I'm am not responsible for bricked devices, flashing custom ROM's/Recovery's is done so at YOUR OWN RISK!
Information
This is a standard Lineage build without any extras & compiled with stock SU6 6.0.1 kernel
Download
http://www.mediafire.com/file/n55eth5yidbos5c/lineage-13.0-20171007-UNOFFICIAL-p839v55.zip
Installation
I recommend doing a full wipe before flashing!
Flash ROM using TWRP
Flash GAPPS 6.0 arm package of your choice
Reboot & wait for Android to boot
Version Information
Status Beta
ROM OS 6.0.1 Marshmallow
ROM Kernel 3.10.49
Created 2017-08-24
Updated 2017-10-07
Thanks goes out to @wbrambley for his involvement in testing & helping to solve / fix bugs!
I noticed that "mm-pp-daemon" was stopping the CPU from going in to sleep state and keeping it at full clocks but after killing the process it reloaded and was fine.
@nutsda, I've tried to pm this but its not working. Probably some spell check safety net
You should post a link here. http://www.modaco.com/forums/forum/796-vodafone-smart-ultra-6/
the SU6 has its own device forum on Modaco and I'm sure it would create some interest.
I've pushed(?) a change that enables the NFC and also put up my overlay folders. There's some stuff in there you might like.
The sensors (Accelerometer, Magnetic field and Rotation vector) are still causing grief.
How fast is your phone to "wake up" from sleep? My buttons light up but screen on takes about 5 seconds. (could be the sensor hal cal firing up but im not 100% sure.)
wbrambley said:
@nutsda, I've tried to pm this but its not working. Probably some spell check safety net
You should post a link here. http://www.modaco.com/forums/forum/796-vodafone-smart-ultra-6/
the SU6 has its own device forum on Modaco and I'm sure it would create some interest.
I've pushed(?) a change that enables the NFC and also put up my overlay folders. There's some stuff in there you might like.
The sensors (Accelerometer, Magnetic field and Rotation vector) are still causing grief.
How fast is your phone to "wake up" from sleep? My buttons light up but screen on takes about 5 seconds. (could be the sensor hal cal firing up but im not 100% sure.)
Click to expand...
Click to collapse
I have merged the commit you made to github & can confirm NFC now enables for me.
Update has been uploaded http://www.mediafire.com/file/7bjnwaaupm4ejf0/lineage-13.0-20170903-UNOFFICIAL-p839v55.zip, first post link also updated.
Camera now working & NFC now enables thanks to @wbrambley
How do I get this rom installed? I already failed rooting my phone to install TWRP. I tried to get temporary Root with KingRoot but that doesn´t work. I´ve Stock Marshmallow Rom on my phone. Can someone help me?
coolbook1 said:
How do I get this rom installed? I already failed rooting my phone to install TWRP. I tried to get temporary Root with KingRoot but that doesn´t work. I´ve Stock Marshmallow Rom on my phone. Can someone help me?
Click to expand...
Click to collapse
Use recovery to flash a 5.1 stock ROM, then you can get temporary root. I'm guessing you've found a guide for this. After that I recommend flashing stock MM from TWRP. There's one with edited uodater-script around that will work.
Hint: look at the forum I posted earlier.
Sent from my HUAWEI GRA-L09
Thanks for your rom
I Wonder when will sensors be fixed?
Update uploaded http://www.mediafire.com/file/v5m8keoadkwkaz2/lineage-13.0-20170906-UNOFFICIAL-p839v55.zip
Sensors now working properly, also improved boot up time.
Waiting For Your Stable Version
Sensors now working properly, also improved boot up time.[/QUOTE]
thanks Nutsda I'm Waiting For Your Stable Version...
lineage-13.0-20170906
Auto rotate screen is broken in this build.
thanks
When will we see an update of your work? Keep it up.
Okay here is an updated build http://www.mediafire.com/file/wedlnkhzk4e5o81/lineage-13.0-20170925-UNOFFICIAL-p839v55.zip, playstore should now work properly & improvements to sensors (but probably still require more work).
Thank you. Market now works. Still can't install nova but overall very good. Looking forward for the first stable release
New update uploaded http://www.mediafire.com/file/n55eth5yidbos5c/lineage-13.0-20171007-UNOFFICIAL-p839v55.zip
Improved audio volume,
All sensors now working - thanks to @wbrambley,
Lineage updated to 6.0.1_r80.
i didn't tried this rom but
can u tell me why any custom rom for this phone is laggy as hell...?
DR.iTACHi said:
i didn't tried this rom but
can u tell me why any custom rom for this phone is laggy as hell...?
Click to expand...
Click to collapse
I haven't tried the other custom roms but I believe it will be because most of them are ported from another phone rather than specifically built for this phone.
nutsda said:
I haven't tried the other custom roms but I believe it will be because most of them are ported from another phone rather than specifically built for this phone.
Click to expand...
Click to collapse
i tried your cm 12.1
that built specially for this phone laggy as hell too!
is this rom is laggy too?
i flashed your rom it's stable and not laggy like others but how to root it?
DR.iTACHi said:
i flashed your rom it's stable and not laggy like others but how to root it?
Click to expand...
Click to collapse
You have to download SuperSU to get root access as Lineage doesn't have root access built in.
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.
So, i have an LG K11 Plus (LM-X410BCW), released in 2018, the hardware of this phone is pretty good but, for some reason, while its CPU does supports 64-Bits, LGE installed an 32-Bits kernel on it (thank you for mistakes like that you always do, LGE.... ugh)
I searched for another root and custom kernel for this phone, and i could not find any. No rooting, no custom bootloader, and no custom kernel. Simply, nothing.
And for the most unfortunate, this phone is now completely abandoned by the manufacturer. Their official ROM and kernel are so bad, so glitched, so awful. The phone does not use the maximum power of its hardware, it keeps rebooting, it's stuck in Android 7.0 and even its camera app is glitched (my BACK flash doesn't work on the back camera, the app recognizes it as a "frontal" flash)
I know for rooting and installing custom kernel, i need another bootloader first
So i plan to make an unofficial bootloader for this model.
But i don't know where to begin, i know nothing about Android deep-modding and developing mobile custom kernels and bootloaders, i've no clues how to do that
I only know the basics of Android app developing, Android shell scripting and i'm more advanced in J2ME applications (completely useless for today's Android standards)
So, ¿where do i begin to do that?
My initial plans is making a unofficial TWRP bootloader for this model, but i don't know how i'll do that
I'd really help you if i knew how to, i also have this phone. I got it for a realtively high price and must say that it's absolutely unworthy of it's existance in our planet and modern society. The absolute maximum of modifications it allowed me to do was to remove bloatware packages using ADB, so i removed almost everything Google/Android related and now i'm working on a list of what you can/can't remove.
I removed the included launchers to only use Evie launcher, installed XDA's Navigation Gestures app (tho it made my phone lag a bit, as any overlay/draw-over-screen app will do), replaced Play Store by F-Droid, and etc... The phone is still bad, sub-entry level hardware even for it's time, has a Vulkan-capable GPU without Vulkan drivers included in the OS, and a 64-bit CPU running a 32-bit Kernel/OS, like you mentioned. But after that, the experience became a little bit smoother, at least!
I don't know nothing about this, but maybe you can get this phone's stock ROM in KDZ format, and start doing brute-force modifications to it, to flash it with LGUp, or LGFlashTool as if it was a stock ROM, but your modified version, because i don't think this phone checks the integrity of the ROM being flashed, or at least not in a way that can't be easily bypassed.
I have found its firmware on the internet, but i don't know how to modify it yet... But maybe i'll not delay much to learn it if i begin to. But i think i'll not be able to change its kernel nor the bootloader, as i want, from the firmware only, only the ROM... So it would be a bit useless as the LG's negligency was most on its software, with that lack of Vulkan and 64-bit support stuff
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that