@ ed, deleting certain apps will trigger the error. Yer assumption may be correct considering the loki recovery bypasses the error, its a small step & a moment to loki the security error free kernel to be safe though. I dont wanna be responsible for bricking any devices. The hack works this way. If you wanna test w/o the custom stock kernel and post the results that would be great. We await for the device tree to be completed. My source is synced and jellybean will be my goal.
LG Viper roms?
- Thread starter brandonabandon
- Start date
@brandon, not sure what specific apps you mean. i eliminate nearly everything except critical apk's and no error. gapps all gone, almost all uncritical lg apks, all sprint, etc. the only mod i had at the time was the loki TWRP.
i am currently going to flash your update, then flash an oc kernel, and cwm on top to test. this should be an optimal setup to test it as a daily driver.
btw, http://androidforums.com/lg-viper-4g/844111-guide-dirty-hack-stock-update-zvk.html
i am currently going to flash your update, then flash an oc kernel, and cwm on top to test. this should be an optimal setup to test it as a daily driver.
btw, http://androidforums.com/lg-viper-4g/844111-guide-dirty-hack-stock-update-zvk.html
Got ya. Some of the commits
Threw me off. Add cyanogenmod defconfig. Merge viperdevs jb ie. I used the kernel for all of my builds. No wonder they wouldnt boot lol.
I mean prior to loki. Lol as root deleting certain apps would trigger the error. Actually there is a few threads concerning this exact issue. Whilst updating also, and updates breaking due to deleted apps. It happend to me even! Lmao anyhow, if you dont believe me, try rooting zvi w/o loki recovry and deleting all apps. When you reboot, security error. Thanks again for repost
@ ed please fix yer repost of my thread. Its the .zip im hosting which has the phone/data disabled. You can modify following my guide to yer personal likings. Basically flash as is with the new kernel and the update would be exactly the same. The difference would than be ability to reroot and avoid security error after deleting apps. My personal .zip im hosting built to my preferences. Im hosting it as an example. Anyhow please repost as modify to yer own likings. Not some features dont work. All and any features work unless you delete them lol. Thanks again ed.
should be fixed now. just woke up and have a hundred things to do. let me know if it needs further editing.
Either dding, adding the modified post.boot, or both did it (was flashing via twrp prior.)
Last edited:
think ed is right regarding loki. After flashing my zip with loki'd no security error kernel and joshs smartass kernel, reboots with all apps deleted. Proving that the no security error issue is absolved via loki recovery.
Last edited:
thenameisnigel
Well-known member
- Apr 27, 2012
- 1,446
- 148
- 63
Submit the fix to the CM Gerrit. The Jenkins instance will build the patch to see if it works for other devices. If it does, I'll +2 and merge your patch.
what location do i dd the kernel? i have the location for recovery, but not kernel
ty my friend. btw, you have a comment on your code review. Matt mentioned that they are only submitting patches to cm11.0 now.
I had thought as much, but i did it anyway considering Nigel suggested it, maybe he thought i was on the cm11 branch
useing my iproj kernel+joshs/poc device tree, cm10.1 boots to the lg splash screen. and adb recognizes the device as "List of devices attached
7be831 device" no lgsl840?lol. after flashing i noticed again i was unable to mount system or data via recovery. i will post the recovery log shortly.
nm lol from the looks of it http://pastebin.com/PP7trzh2 i just wiped the system
^confirmed
7be831 device" no lgsl840?lol. after flashing i noticed again i was unable to mount system or data via recovery. i will post the recovery log shortly.
nm lol from the looks of it http://pastebin.com/PP7trzh2 i just wiped the system
^confirmed
Last edited:
so basically you built a rom, but instead of flashing, you wiped your device instead?
anyhow, i have no quirks in testing compiled roms to save some time.
seems you are on teamwin recovery (correct me if im wrong). I am on CW recovery and can attempt a flash through there. might help out, idk.
after reviewing the log, it apprears that somehow, TWRP isnt mounting the storage during flash, rendering the flash useless. i can try with CWM recovery and see if it follows through, but it may be possible our recoveries are simply not able to flash roms. correct me if im worng and you have been able to sucessfuly flash a zip of sorts before. if that is the case, check your settings, and if all else fails, check to see if the zip was made properly. the biggest note i saw was it was missing SE_Linux which every rom i flashed in the past had such. just a thought, but that could be the main issue as well.
anyhow, i have no quirks in testing compiled roms to save some time.
seems you are on teamwin recovery (correct me if im wrong). I am on CW recovery and can attempt a flash through there. might help out, idk.
after reviewing the log, it apprears that somehow, TWRP isnt mounting the storage during flash, rendering the flash useless. i can try with CWM recovery and see if it follows through, but it may be possible our recoveries are simply not able to flash roms. correct me if im worng and you have been able to sucessfuly flash a zip of sorts before. if that is the case, check your settings, and if all else fails, check to see if the zip was made properly. the biggest note i saw was it was missing SE_Linux which every rom i flashed in the past had such. just a thought, but that could be the main issue as well.
Looking into selinux issue
@ed @flasing the custom rom the flashwiped the system i believe because the system is mounting improperly. Idk if the error is recovery, rom, or both. To answer yer question, my modified update.zip flashed just fine so im leaning toward rom issue.
@ed @flasing the custom rom the flashwiped the system i believe because the system is mounting improperly. Idk if the error is recovery, rom, or both. To answer yer question, my modified update.zip flashed just fine so im leaning toward rom issue.
thought so. btw im in irc. its easier to communicate there.
do you have a debug text from where you compiled the rom?
i see a couple of issues before the selinux error, namely these:
I:No internal storage defined.
I:No storage defined, defaulting to /sdcard.
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
ahhhh
here is a clue:
sd-ext is the external sd card. it was disabled as shown earlier during flash, which has been known to cause issues later.
sdcard is internal sd memory and unless wiped during install, is the best option for a rom flash, because after the rom installs, it sometimes can no longer read the actual sd card (sd-ext) which results in a fail. idk of a better way to explain, but i had this problem with the exhibit when i flashed to ics first then jellybean. the rom was intended to go from stock gb to jb and i had missed the note that going from ics can cause errors. i find it odd, but it legitimately happend and i solved it by pushing the rom to internal sotrage. this case may be different however, but its worth a look into.
do you have a debug text from where you compiled the rom?
i see a couple of issues before the selinux error, namely these:
I:No internal storage defined.
I:No storage defined, defaulting to /sdcard.
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
ahhhh
here is a clue:
sd-ext is the external sd card. it was disabled as shown earlier during flash, which has been known to cause issues later.
sdcard is internal sd memory and unless wiped during install, is the best option for a rom flash, because after the rom installs, it sometimes can no longer read the actual sd card (sd-ext) which results in a fail. idk of a better way to explain, but i had this problem with the exhibit when i flashed to ics first then jellybean. the rom was intended to go from stock gb to jb and i had missed the note that going from ics can cause errors. i find it odd, but it legitimately happend and i solved it by pushing the rom to internal sotrage. this case may be different however, but its worth a look into.
Last edited:
i believe i can verify that the stock kernel will not boot cm10.1. loki'd the boot.img of stock kernel on cm10.1 rom doesnt boot. same with twrp2.7 which i built with the iproj and stock doesnt boot either. back to the drawing board.
ok, so the next action should be cm9 since it is an ICS kernel after all. then we work our way up by making a custom jb capable kernel.
thenameisnigel
Well-known member
- Apr 27, 2012
- 1,446
- 148
- 63
Similar threads
Facebook
Twitter
Instagram