... to the latest nightly 02/12, it has a broken kernel / recovery mode!!
If you did, flashing via Odin will be necessary.
;( can u help me? i've flashing via Odin but it doesn't start boot loop
I tried the version of today : 20140213 and also that one seems to fail.
Was this via OpenDelta, or a complete ZIP downloaded from dl.omnirom.org?
None of the developers can reproduce issues with locally-build ZIPs, and I think xplodwild flashed a nightly ZIP with no issues too.
My 20140212 got flashed via opendelta
Entropy512 said:
Was this via OpenDelta, or a complete ZIP downloaded from dl.omnirom.org?
None of the developers can reproduce issues with locally-build ZIPs, and I think xplodwild flashed a nightly ZIP with no issues too.
Click to expand...
Click to collapse
It came with OpenDelta.
my post here can help :
http://forum.xda-developers.com/showthread.php?t=2647218
Entropy, I can make test with my spare i9100 if it can help ! Just tell me what do you need
Entropy512 said:
Was this via OpenDelta, or a complete ZIP downloaded from dl.omnirom.org?
None of the developers can reproduce issues with locally-build ZIPs, and I think xplodwild flashed a nightly ZIP with no issues too.
Click to expand...
Click to collapse
I had the issue with a locally build zip. And also with an OpenDelta update.
It gets fixed (the bootloop that is, there are other issues) by just replacing the kernel. Between the previous nightly and the broken one, there's only one commit in the kernel project: https://gerrit.omnirom.org/#/c/5019/.
But here's the mystery: most people, including me, seem to be able to solve the problem by installing the latest gustavo's kernel. But that one also seems to have that code... However, even though I saw no one reporting problems with the latest gustavo's, I did in one of my many trials have issues with it dumping back into TWRP instead of booting. I never had issues with older omni or gustavo's kernels and the 0212 rom.
Because of the other issues (Settings.apk not being loaded starting from 0212) I'm still on pre-0212 and experimenting...
Update: build a current zip, with 5019 reverted to its PS2, which I think didn't have trouble yet. However, it still bootloops. (Of course I may be doing something wrong however; I'm not very experienced with this sort of thing).
Update 2: build a zip with 5019 fully reverted: no boot loop! I am currently verifying whether including 5019 again will break stuff again.
Update 3: yes, it does. I took great care to follow the exact same install procedure. So this confirms https://gerrit.omnirom.org/#/c/5019/ as the culprit.
The 2014-02-12 update for OpenDelta has also caused my i9100 to boot loop.
Hoping the post by -Furion- will fix it.
will test after work.
Edit:
Works fine when done with odin ver3.04
GidiK said:
I had the issue with a locally build zip. And also with an OpenDelta update.
It gets fixed (the bootloop that is, there are other issues) by just replacing the kernel. Between the previous nightly and the broken one, there's only one commit in the kernel project: https://gerrit.omnirom.org/#/c/5019/.
But here's the mystery: most people, including me, seem to be able to solve the problem by installing the latest gustavo's kernel. But that one also seems to have that code... However, even though I saw no one reporting problems with the latest gustavo's, I did in one of my many trials have issues with it dumping back into TWRP instead of booting. I never had issues with older omni or gustavo's kernels and the 0212 rom.
Because of the other issues (Settings.apk not being loaded starting from 0212) I'm still on pre-0212 and experimenting...
Update: build a current zip, with 5019 reverted to its PS2, which I think didn't have trouble yet. However, it still bootloops. (Of course I may be doing something wrong however; I'm not very experienced with this sort of thing).
Update 2: build a zip with 5019 fully reverted: no boot loop! I am currently verifying whether including 5019 again will break stuff again.
Update 3: yes, it does. I took great care to follow the exact same install procedure. So this confirms https://gerrit.omnirom.org/#/c/5019/ as the culprit.
Click to expand...
Click to collapse
OK this is really weird. I9100 and I777 have 100% identical displays (the only differences between these two devices are the touchkeys, call audio, and NFC. In fact I9100 kernels will boot on i777 although the above items will not work correctly of course...) and my i777 is booting fine even with that patch.
wtf?
Entropy512 said:
OK this is really weird. I9100 and I777 have 100% identical displays (the only differences between these two devices are the touchkeys, call audio, and NFC. In fact I9100 kernels will boot on i777 although the above items will not work correctly of course...) and my i777 is booting fine even with that patch.
wtf?
Click to expand...
Click to collapse
We're definitely in the land of weirdness here. Judging by the SII I9100 thread, some people with i9100 also have no problem...
I don't know what I'm talking about, but could it be an issue unrelated to the code? The way it's build? The resulting kernel size? Maybe any other change would also have caused problems?
GidiK said:
We're definitely in the land of weirdness here. Judging by the SII I9100 thread, some people with i9100 also have no problem...
I don't know what I'm talking about, but could it be an issue unrelated to the code? The way it's build? The resulting kernel size? Maybe any other change would also have caused problems?
Click to expand...
Click to collapse
OK that's REALLY weird if not all I9100 users have problems. Great. I'll check when I get home if xplodwild has tried this on his device, hopefully he can reproduce the problem.
stupid unified kernel/recovery approach, makes it damn near impossible to get a last_kmsg of a failure.
OK, here's a question: Can one person who is having issues with the newer kernels and one person who isn't please run the following command and put the output here, including whether or not you're having problems with the newer kernels on your device. (People who are having issues with the new kernels need to flash an older kernel to do this, people who are not having issues can get this from a newer kernel.)
Code:
cat /proc/cmdline
Please only post this information if you have results that differ from results already posted, specifically:
Look at the lcdtype variable (if present) or (if present) the ld9040.get_lcdtype variable
If you have the same lcdtype as someone who has already posted results AND you are getting the same results, don't post your results as they are unnecessary
If you have the same lcdtype as someone who has already posted results AND you have different results with new kernels, quote the other person and post that you're getting different results
Issues: yes. ld9040.get_lcdtype=0x0.
Not exactly from an older kernel, but with the patch reverted so effectively the same; I hope that isn't a problem. Redacted the serialno just in case:
Code:
console=ttySAC2,115200 consoleblank=0 androidboot.selinux=permissive loglevel=4 console=ram androidboot.serialno=*** sec_debug.enable=0 sec_debug.enable_user=0 c1_watchdog.sec_pet=5 [email protected] s3cfb.bootloaderfb=0x5ec00000 ld9040.get_lcdtype=0x0 consoleblank=0 lpj=3981312 vmalloc=144m
Issues: no. ld9040.get_lcdtype=0x2
running 20140212 nightly
GidiK said:
Issues: yes. ld9040.get_lcdtype=0x0.
Not exactly from an older kernel, but with the patch reverted so effectively the same; I hope that isn't a problem. Redacted the serialno just in case:
Code:
console=ttySAC2,115200 consoleblank=0 androidboot.selinux=permissive loglevel=4 console=ram androidboot.serialno=*** sec_debug.enable=0 sec_debug.enable_user=0 c1_watchdog.sec_pet=5 [email protected] s3cfb.bootloaderfb=0x5ec00000 ld9040.get_lcdtype=0x0 consoleblank=0 lpj=3981312 vmalloc=144m
Click to expand...
Click to collapse
Not a problem. I pretty much meant "any working kernel"
_mikey_ said:
Issues: no. ld9040.get_lcdtype=0x2
running 20140212 nightly
Click to expand...
Click to collapse
Thanks.
So, so far:
People with 0x0 have failures
People with 0x2 do not have failures
No need to post results if you have results that match the above.
Entropy512 said:
So, so far:
People with 0x0 have failures
People with 0x2 do not have failures
No need to post results if you have results that match the above.
Click to expand...
Click to collapse
I don't pretend to understand anything about the code, but the patch moves initialization code from one file to another, and this initializes equally for lcdtypes 1 and 2, but differently for lcdtype 0. Was "&u1_panel_data", is now "&s2plus_panel_data" for lcdtype "LCDTYPE_SM2_A1", i.e. 0. No idea what this means, but I don't have an S2plus.
GidiK said:
I don't pretend to understand anything about the code, but the patch moves initialization code from one file to another, and this initializes equally for lcdtypes 1 and 2, but differently for lcdtype 0. Was "&u1_panel_data", is now "&s2plus_panel_data" for lcdtype "LCDTYPE_SM2_A1", i.e. 0. No idea what this means, but I don't have an S2plus.
Click to expand...
Click to collapse
Yup, got it, found the same thing. Also, s2plus_panel_data was an uninitialized struct.
https://gerrit.omnirom.org/5569
I've had no issues, and my results matches those posted.
Works on 20140215 NIGHTLY
Thank you,
The issue was resolved for me with nightly build 20140215
For me, too! Thx for tracking this down!!
Related
I am attempting to install the latest Omni rom nightly (Omni -4.4.4-20141110 - find7-NIGHTLY.zip) on my Oppo find7. Each time I try to flash the zip file the following error occurs.
"This package is for "find7a, FIND7" devices
this is a "find7".
I am assuming the error is due to the upper case letters in the binary and my device is showing find7 in lower case. How can I fix this problem?
rgreene1971 said:
I am attempting to install the latest Omni rom nightly (Omni -4.4.4-20141110 - find7-NIGHTLY.zip) on my Oppo find7. Each time I try to flash the zip file the following error occurs.
"This package is for "find7a, FIND7" devices
this is a "find7".
I am assuming the error is due to the upper case letters in the binary and my device is showing find7 in lower case. How can I fix this problem?
Click to expand...
Click to collapse
Please do research before posting. Also, in general, do not post device-specific issues in the general forums. The solution to this issue (short answer: stop using broken recoveries) has been covered over and over again in the find7 forums.
Thanks for the quick answer, I think!
I will go over to the CM forums and ask the question since the rom I was using that flashed nightlies every night without an issue is the latest CM.
rgreene1971 said:
Thanks for the quick answer, I think!
I will go over to the CM forums and ask the question since the rom I was using that flashed nightlies every night without an issue is the latest CM.
Click to expand...
Click to collapse
CM has chosen to allow flashing on broken recoveries that have been obsolete for months. We don't, since a recovery reporting as "find7a" is either vastly outdated or released by someone who doesn't know what they're doing (since such a recovery will also be unable to flash official Oppo releases), which means that we have no idea what it's going to do.
Oppo's recovery reports as FIND7 on all units (7a and 7s), as a result proper recoveries (such as official TWRP) report as FIND7.
The appropriate place to go for things like this is the device-specific forums on XDA, since as I have previously stated, this issue has been documented over and over again there.
THIS ROM BOOTLOOPS. NO NEED TO CONFIRM OR POST SUCH ANYMORE
Basically this ROM is an experiment at building LineageOS 14.1 (Nougat) specifically for an xt907 KKBL
How I built it:
Set up a virtual Box (on Win7 64b) to build Lineage OS 14.1 (followed their instructions)
Source: https://github.com/LineageOS/
I used an existing xt907 KKBL device tree (https://github.com/LineageOS/android_device_motorola_xt907) it looks old, but I built a JBBL device tree based from this project, and that booted. I also built TWRP using this device tree, and I have been told that it works
Basically, I have done no "magic" here. If this ROM works, I may also be able to build crDroid & ResurrectionRemix Nougat as well. Actually, my JBBL from this device tree worked better for crDoid and RR than LOS
This is an experimental build of LineageOS 14.1, Android version 7.1.2, an experimental build for a non-official device (ie xt907 KKBL).
I personally do not have an xt907 with KKBL, but an xt905 with JBBL, so I can't easily test this KKBL ROM. PLEASE tell me if it works or not.
The good
It's LineageOS
It's Nougat!
It's for KKBL
It's built from a device tree that I hacked into JBBL, and that booted
A TWRP for KKBL was built using the same device tree, and I am told that that works
It Builds
The bad
I have no idea if it boots as I don't have a KKBL installed
Since I do not own an xt907 KKBL, I cannot test this zip personaly, and hope someone with an xt907 KKBL will try the zip and let me (and others) know if it works?
What I hope is that if this boots and runs, I will try building crDroid Nougat (and maybe ResurrectionRemix) for the xt907 KKBL. If they also work, I personally will up[grade to the KKBL (my JBBL version of crDroid has numerous FC's)
Credits: All credits go to LOS contributors and CM maintainers before them.
Almost forgot, Flash this ZIP at your own risk, the responsibility is all yours, it is provided as-is, with no garantees or whatever and I will not be held resonsible for any damage to your device or its data etc etc etc
Installation:
1) Download the ZIP
2) Boot into TWRP recovery (I wou;d recomend updating to TWRP 3.x (see myh othere thread I have been told trhat it works)
3) Make a nandroid (you should definitely be going back) And remember, a nandroid is NOT 100%! if you don't understand this, maybe trying this is not for you.
4) Wipe system/data/cache/dalvik
5) Flash update package (ie install the zip)
6) Flash GApps (probably Open GApps pico...) if it doesnt work, try a wipe and not flashing GApps (it helps with crDroid for JBBL)
6) Reboot to system
If it falls over, please get some logcats and post them on hastebin/pastebin etc etc NOT HERE, only the links. Hopefully we can fix it and have some highly customisable nougat ROM's for your device. And the steps to make it work may also be helpful for the next Android iteration.
Download Link: https://clicknupload.org/uvu9uknep9ku
And please post how you go with this ROM, either way, I would like to know if it works or not to decide if to build crDroid and/or RR. If it does work and crDroid does not, I may get around to building a non experimental build, with Overclocking enabled.
Cant download from that link
Shmaks said:
Cant download from that link
Click to expand...
Click to collapse
what exactly is the problem? have you tried a different browser? I can directly through chrome and also using TOR browser.
DiamondJohn said:
what exactly is the problem? have you tried a different browser? I can directly through chrome and also using TOR browser.
Click to expand...
Click to collapse
Tried two browsers - chrome and firefox. Click free download - create download link - click here for download - have Error The requested URL could not be retrieved
Fix: downloading with TOR works))
Shmaks said:
Tried two browsers - chrome and firefox. Click free download - create download link - click here for download - have Error The requested URL could not be retrieved
Fix: downloading with TOR works))
Click to expand...
Click to collapse
It may of been a timing thing. I posted the link right after the upload finished.
Just flash it (with and without gapps) - neverended boot animation, bootloop
Shmaks said:
Just flash it (with and without gapps) - neverended boot animation, bootloop
Click to expand...
Click to collapse
how much time did you give it? I have found 8-10 minutes is the norm for the first boot, and I allow 15 before I concede its not going anywhere.
Never mind, I am also just preparing to build crDroid (Nougat) (source is a big and slow download). I found that with the KKBL code altered to JBBL, crDroid booted while LineageOS 14.1 did not. And maybe LOS13 will boot. The fact that LOS14.1 at least showed the animation is a big positive.
Out of interest, did you flash it using TWRP 3.1.1?
DiamondJohn said:
Out of interest, did you flash it using TWRP 3.1.1?
Click to expand...
Click to collapse
Yes, TWRP 2.8.6 didnt flash it
Shmaks said:
Just flash it (with and without gapps) - never ended boot animation, bootloop
Click to expand...
Click to collapse
DiamondJohn said:
how much time did you give it? I have found 8-10 minutes is the norm for the first boot, and I allow 15 before I concede its not going anywhere.?
Click to expand...
Click to collapse
One difference I have noted between MM and Nougat is that MM will play the boot animation for much shorter a time and go into the "Optimizing app 1 of XX", while Nougat will continue to play the boot animation all through the optimisation (ie a LOOOOONnng time), until it actually loads and displays the launcher. Just a thought, maybe a little hope...
Endless boot screen for me, both with and without GApps. Waited 20 minutes both times. Installed via KKBL TWRP 3.1.1.
I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.
DiamondJohn said:
I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.
Click to expand...
Click to collapse
Is this still an issue?
DiamondJohn said:
I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.
Click to expand...
Click to collapse
Willing to test and post logs. Just not sure how to retrieve the logs.
Not happening
See https://forum.xda-developers.com/showpost.php?p=73567002&postcount=19
Although I would be interested in seeing the last_kmsg log on a KKBL, if anyone has some free time.
As with others, I entered endless bootloop as well. Thank you for making the build to try.
mr3p said:
As with others, I entered endless bootloop as well. Thank you for making the build to try.
Click to expand...
Click to collapse
I am guessing you dont have a log of the last_kmsg :fingers-crossed:?
DiamondJohn said:
I am guessing you dont have a log of the last_kmsg :fingers-crossed:?
Click to expand...
Click to collapse
I apologize for not remembering to save the log. It wouldn't be the end of the world to revert back to KKBL and reload this build to get a log but I'll to find some time to play which is always the challenge.
This wouldn't be a problem so much if Lineage didn't delete perfectly good builds/ROMs for this device when they took over. Why would they do that for this device and not others? That seems a bit too coincidental.
DragonFire1024 said:
This wouldn't be a problem so much if Lineage didn't delete perfectly good builds/ROMs for this device when they took over. Why would they do that for this device and not others? That seems a bit too coincidental.
Click to expand...
Click to collapse
Just curious but if someone wants to run LineageOS, whats the downside of just switching over the to JBBL when builds exist?
mr3p said:
Just curious but if someone wants to run LineageOS, whats the downside of just switching over the to JBBL when builds exist?
Click to expand...
Click to collapse
I can't find working links to downgrade to JBBL
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom. so I decided to go back to stock. I noticed when I went to download mode the
"carrier id" is now blank whereas it was PAK before it was gone, also I went to settings it displayed XTC/XTC/ .
I did backup my efs
How do I restore my original product code?
Please help
Excuse me, off topic, but what font are you using?
winol said:
Excuse me, off topic, but what font are you using?
Click to expand...
Click to collapse
I'm using Googlesans
upbeatwrench said:
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom. so I decided to go back to stock. I noticed when I went to download mode the
"carrier id" is now blank whereas it was PAK before it was gone, also I went to settings it displayed XTC/XTC/ .
I did backup my efs
How do I restore my original product code?
Please help
Click to expand...
Click to collapse
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
_alexndr said:
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
Click to expand...
Click to collapse
also, after flashing stock firmware, I had the data erased (didn't used the HOME_CSC), after I enable developer options, OEM Unlock is already there and the option is ticked
_alexndr said:
This minor issue is NOT related to my ROM and has been disscussed in my thread long time ago
See below disscussion (#252 - #256), especially @dr.ketan's statement (#256):
https://forum.xda-developers.com/showthread.php?p=76121821&postcount=256
Click to expand...
Click to collapse
I have later more studied and found this code is in bootloader and strongly believe this specifically happens when you flash BL and modem with TWRP instead of odin. I request users to check this. Though this seems purely a cosmetic glitch and yet haven't found any ill effect practically.
dr.ketan said:
I have later more studied and found this code is in bootloader and strongly believe this specifically happens when you flash BL and modem with TWRP instead of odin. I request users to check this. Though this seems purely a cosmetic glitch and yet haven't found any ill effect practically.
Click to expand...
Click to collapse
Is this because of some ROMs with such options to update BL/CP before installing the rom may have cause the issue?
upbeatwrench said:
Is this because of some ROMs with such options to update BL/CP before installing the rom may have cause the issue?
Click to expand...
Click to collapse
This is what is my speculation, if someone don't have this issue and flash BL and Modem with TWRP and if he/she get this error, we can confirm it.
But this code is simply a cosmetic and I haven't seen any issue related to this.
upbeatwrench said:
I have installed a couple of roms to test, but last night I got screwed up, I don't know what I did wrong why the product code went missing. I installed @_alexndr's [ROM][N950F/DS/N][ALEXNDR] * U5CRHA * DevBase v5.9 * Encryption support [Sep-16] rom. After it booted up, i noticed that it as so sluggish, I did wipe everything before installing the rom [...]
Click to expand...
Click to collapse
BTW: Side note - my ROM is NOT sluggish but you just experienced latest Magisk's issue after clean install. More info you will find in similar S8's thread (post #280):
https://forum.xda-developers.com/showthread.php?p=77657344&postcount=280
... I just forgot to put same info in N8 thread
dr.ketan said:
This is what is my speculation, if someone don't have this issue and flash BL and Modem with TWRP and if he/she get this error, we can confirm it.
But this code is simply a cosmetic and I haven't seen any issue related to this.
Click to expand...
Click to collapse
I see, if that's the case, I did tick those options cause I thought it would be better to update BL/CP
anyways, I thought missing the product code or the 3rd csc was a huge problem because as I was installing different roms after I lost it and reinstall the stock FW, there was a lot of lag and every rom that I install, I did wipe/format data,cache before installing a new one.
Another one problem I encountered was everytime I download root explorer app and try to modify some cscfeatures, the SystemUI stops, sometimes even after a few minutes after it restarted, the SystemUI stops.
anyway, I thought these problems was related to the product code being missing, but it's all good now, everything is working just fine :good:
I have had this problem for ages, over 6 months, had flashed a number of roms and different country stock files before I noticed it had changed.
I had not used Dev-Base at the point of realising the change though.
I have never had any issues in functionality despite this. Not seeing anyone else with it, I assumed Samsung maybe updated something for unlocked phones.
_alexndr said:
BTW: Side note - my ROM is NOT sluggish but you just experienced latest Magisk's issue after clean install. More info you will find in similar S8's thread (post #280):
https://forum.xda-developers.com/showthread.php?p=77657344&postcount=280
... I just forgot to put same info in N8 thread
Click to expand...
Click to collapse
Yup, sorry about that, I thought it was only yours,
thanks for letting me know that Magisk was responsible for that extreme lag
upbeatwrench said:
I see, if that's the case, I did tick those options cause I thought it would be better to update BL/CP
anyways, I thought missing the product code or the 3rd csc was a huge problem because as I was installing different roms after I lost it and reinstall the stock FW, there was a lot of lag and every rom that I install, I did wipe/format data,cache before installing a new one.
Another one problem I encountered was everytime I download root explorer app and try to modify some cscfeatures, the SystemUI stops, sometimes even after a few minutes after it restarted, the SystemUI stops.
anyway, I thought these problems was related to the product code being missing, but it's all good now, everything is working just fine :good:
Click to expand...
Click to collapse
Nope, None of such issue is related to missing code.
this error I have on my N8 and I remember once I had flashed BL and modem via TWRP , though at that time I have no idea otherwise I can confirm it. I have made small tool to restore missing code too but never shared (Nor I am using) because t requires to patch on every boot. So my suggestion is just forget it.
Hello everyone
Some might know me from the V30... Also got my hands on a V40 now (which I will also give my best to develop for).
I'm currently searching for people who are capable AND willing to test different things.
With that I mean:
- You know how to take logs (logcat, dmesg)
- You know how to recover from a soft brick (either how to get into TWRP for example, or in really bad cases fastboot or flashing a kdz)
- You know how to follow orders
I currently have a (somewhat decendly) working TWRP build (cant decrypt stock encryption atm).
GSIs are a complicated thing, because of not only vbmeta but also because of our 8.1 vendor (Pie GSIs work, if you remove some sepolicies from their system, Oreo GSIs dont have that issue)
What I would need more people to test for:
- stock decryption
- trying out different ways when something (doesnt) boot (e.g. need to flash magisk for xy to not crash to fastboot)
and so on
After everything is somewhat stable (I had to reflash a kdz today, as somehow nothing, no twrp in either slot, or restored stock rom didnt wanna render anything anymore, even though usb/adb worked just fine)
Also working on LOS for this device btw (but thats far more work in progress)
If you wanna be part of this upbringing, reply here, and I'll message you via PM the details.
PS: Having Telegram would be very beneficial.
I volunteer for this. Happy to see you step up for our forgotten device.
How did you reflash the KDZ?
I`m also interested in testing.
onslaught86 said:
How did you reflash the KDZ?
Click to expand...
Click to collapse
In my case i used LG Bridge, at first it complained that MTP wasnt running, but after clicking a few times ok it was fine with that lol
but i read in another thread that a lgup_cmd is able to flash kdzs to the v40
I think I can participate in the test, I have a V405US ROOT phone。
Please forgive me for my bad English. :）
In +1
Hi, how you rooted LG V40?
Any movement on this?
Evilmonstertruck said:
Any movement on this?
Click to expand...
Click to collapse
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.
SGCMarkus said:
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.
Click to expand...
Click to collapse
Any update is a good update. I appreciate all the work your doing. I know it's not easy. Thanks again
I can test out twrp and or ROM! Best regards.
Hello everyone. I am opening this thread for the sake of convenience of us users of this ROM so that we stop hijacking the Oreo version thread and have a "clean" place where we can discuss about our experience with this great ROM. So I suggest anything regarding this ROM to be posted here!
You can find the official builds here: https://get.resurrectionremix.com/?dir=hammerhead
DISCLAIMER: I am by no means a developer or maintainer of this ROM, so this cannot be considered an official support thread, just conversation, plain and simple! Moderators can close this thread as soon as an official support thread opens.
Cheers!
I just installed the rom,came from stock. My first impressions are:
-It took 2 reboots to get the camera working. Installed google camera app since the integrated one doesnt show up on app drawer(you can access it from lockscreen though) and it seems to work kinda bad(picture goes black on it sometimes).
-It runs a bit hotter than stock rom. It might be just me though,I have opened the phone a few times to fix the power button which seems to get stuck for me once in a while.
-The default DPI doesn't seem right,everything looks a little bit smaller than it does on stock rom. There is an option to change it though, I set mine to 380 and it looks about right.
I haven't found any other issues yet.
Another note,I think the rom fixed my notification led lol. It didn't work for me on stock rom for some reason.
Pretty good rom overall,I haven't faced any stability issues yet.
edit: Is there any way to lower the resolution?
I upgraded from RR's Oreo build. Before flashing I repartitioned the phone using the method described here and the even more detailed instructions posted by douguluskaien on page 12 of that thread. The flash went very smoothly and although the phone initially ran hot it cooled back to normal after a few hours of what was probably background processing. With the 1.5G system partition I was able to install the micro version of GAPPS. I've had that experience after flashing new ROMs on other phones as well. I also discovered the bundled camera doesn't work and installed Google Camera. After starting up Google Camera, the original camera worked also. I tried connecting bluetooth headphones, and even though I could pair the headset I couldn't get the phone to send audio - it just kept playing through the phone speaker. I also found the default font size a little small, but changing it to Large in the Font Size menu got it back to what seems like normal.
I have one major issue which I realize is not directly related to the ROM. A custom version of TWRP is required to support the non-standard partitions, and that version is based on TWRP 3.2.3 and doesn't support device encryption. Does anyone know if an updated TWRP will be available that will allow me to encrypt the phone and still do recovery-related stuff?
In summary, this is impressively well along for a build that's only been live for a couple of weeks. This isn't my daily driver so I don't need absolute stability, so this is plenty for me for now. I just won't leave the house with it until I can encrypt.
I've been using this ROM for about a month now as a daily driver, so here's my feedback:
ROM is very nice and smooth and feature rich (as expected for RR). I installed it with Opengapps nano, rooted with Magisk. It works very well with the Pixel launcher I grabbed from here.
Some drawbacks I noticed:
Battery life is rather bad. I get 1h30m SOT at best with very mild usage (mostly site browsing and a little bit of social apps and YT video watching) . Then again I am still using the 5yr old battery that came with the phone...
The phone runs very hot (too hot to hold!) after using it for some time. It cools down rather fast if you let it be for a while, though.
Sometimes the camera is crashing (the notorious "can't connect to camera" error). usually a reboot fixes this.
Sometimes it takes a while for the device to wake up after pressing the power button.
I got some soft reboots under device heavy load. Mostly I get them when using the Rocket player music app, and it tries to load a large music folder. Phone freezes, then soft reboots.
SElinux is set to permissive and the build is signed with test keys. Maybe the first thing is caused by the latter, I don't know really....
Overall, it is a good ROM with room for improvement. However, I am concerned about its maintenance status. No update since May 14, so I keep my fingers crossed.
New build (28/07) uploaded!
hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
I am not able to install it giving me ERROR 7
hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
Do you know about change log??
What features added?
I want to update it tonight
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
m.morcielago said:
Do you know about change log??
What features added?
I want to update it tonight
Click to expand...
Click to collapse
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
I flashed this build this morning by dirty way
Unfortunately Bluetooth is not working
It can find the other devices but can not connect to them
1- How can I fix it?
2-How can I downgrade to previous build?
hammerheadache said:
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
Click to expand...
Click to collapse
Thanks for the idea, I had just repartitioned, so I had format my entire phone, (before that i had taken the backup ), and I had successfully installed the rom, I got an strange issue of WIFI connectivity, as I am not able to connect to my wifi which is having Hidden SSID, but i am successfully connected with the hotspot from my another primary phone. i haven't tested the bluetooth yet.
I dirty flashed the new build this morning. Haven't tried bluetooth or camera yet, but Wifi is working fine. As usual, the phone heated up for about a half hour after the flash and then the temp dropped and stabilized. Battery life is not great, like the May build, and there is often a long delay responding to the power button, especially shortly after power-up, but the build seems pretty solid.
Casting isn't finding anything to cast to in the most recent build. Camera worked fine.
New build available (Aug 4) as seen at ROM's dl page.
Bluetooth pairing now working for me on last release
Hi installed this ROM in clean maner but i got intermitent issue with sim card. Not sure if it is only sim issue or reboot but phone ask my pin code.
Looks like @voidz777 is the maintainer for RR Pie as well:
https://github.com/ResurrectionRemix-Devices/api/commit/8388c5df5069cf04df04facbdc22a2bfd8890185
New build (09/08) in case someone missed it... Link in OP
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
New build (Sep 16) available! Link in OP.
princeknockouts said:
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
Click to expand...
Click to collapse
Thank you for the tip, I followed the thread and was able to install RR 7 without any trouble. This might not be the right place to ask, but would you have any info on how to install SuperSU on RR 7, or is there perhaps another root method that we must use? Thanks in advance, I can't seem to find information on it anywhere and rather than continuing to bang my head against the wall I thought I'd ask.