Related
Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app
the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.
thorrules said:
Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!
tobdaryl said:
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!
Click to expand...
Click to collapse
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
mike-y said:
the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.
Click to expand...
Click to collapse
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.
thorrules said:
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.
Click to expand...
Click to collapse
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.
tobdaryl said:
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.
Click to expand...
Click to collapse
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).
thorrules said:
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).
Click to expand...
Click to collapse
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.
tobdaryl said:
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.
Click to expand...
Click to collapse
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.
thorrules said:
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.
Click to expand...
Click to collapse
OK, that is the reason I mentioned 4.2 and multi-user.
Good Luck!
This is MIUI For the ONE S C2, It is based on bilal_liberty's CM10 Rom so expect similar performance and bugs. You will be running Android 4.1.2 With MIUI For Jelly Bean. It is currently not tested so make a full backup before you flash it, also do a logcat and post it if you can so we fix the issue if you have one.
Notice - This Rom has currently not been tested so use at your own risk, this is why it is labelled TEST.
Download - Soon
How To - To install this ROM just follow the usual way, Back up, Flash Rom, Clear Cache and everything and then boot.img.
V1.3 - Flashes, Boots but force closes and not stable, will release soon.
V1.2 - Re worked Port added, Not sure if issue has been fixed, you tell me.
V1.1 Test - Flashable .ZIP available but issues with flashing.
V1 Test - Launch
[removed]
clewis said:
Hmmm so there is already a miui rom....
But about my rom, i got an error on flash, it did start booting with the boot animation but got stuck.
Click to expand...
Click to collapse
use logcat to see whats going wrong
adb logcat > logcat.txt
http://forum.xda-developers.com/showthread.php?t=1726238 for more info
bilal_liberty said:
use logcat to see whats going wrong
adb logcat > logcat.txt
http://forum.xda-developers.com/showthread.php?t=1726238 for more info
Click to expand...
Click to collapse
I am doing a new build at this time i think i did something wrong the first time, so im going to add another unsigned file in a minute if you or someone else could make it a flashable zip and do a logcat when you do to save time would be good help, ill edit this page when it goes live on dropbox.
BTW this is how im trying to port it if anyone else wants a go - http://forum.xda-developers.com/showthread.php?t=1994503
For making flashable zip just select meta-inf folder system folder and boot.img and add them archieve, there is nothing extra to do.
bilal_liberty said:
For making flashable zip just select meta-inf folder system folder and boot.img and add them archieve, there is nothing extra to do.
Click to expand...
Click to collapse
Alright mate i have taken other one down and put a flashable zip on dropbox its going up now i can't try it myself as i dont have a usb cable that works to flash the boot.img so could someone else test it when it is uploaded.
clewis said:
Alright mate i have taken other one down and put a flashable zip on dropbox its going up now i can't try it myself as i dont have a usb cable that works to flash the boot.img so could someone else test it when it is uploaded.
Click to expand...
Click to collapse
Updated Flashable .Zip - https://www.dropbox.com/s/umsohpgmn1hh2z2/miui_unsigned.zip
Again use at your own risk, this has not been tested also everyone that does give it a try do a logcat so we can see if there is any problems.
Installation failed.
"set_perm: some changes failed"
"E:Error in /sdcard/miui_unsigned.zip"
work for old hboot??
DeanderDean said:
Installation failed.
"set_perm: some changes failed"
"E:Error in /sdcard/miui_unsigned.zip"
Click to expand...
Click to collapse
There is problem in updater script.try fixing permissions in updater script
u can use updater script from this to solve flash problems:
http://pan.baidu.com/share/link?shareid=341288&uk=4112589721 by jswei521
Great Work Man!!
Thanks for the port. I will test soon.
Sent from my HTC One S using xda app-developers app
bilal_liberty said:
u can use updater script from this to solve flash problems:
http://pan.baidu.com/share/link?shareid=341288&uk=4112589721 by jswei521
Click to expand...
Click to collapse
This rom from the above links works well, ive tried it.
Is old hboot 2.09 supported ?
can we flash this over 4.0.3 or do we need 4.0.4 as base ?
Paint in more detail information on ROM.
From what device port that was done, lay out screenshots, competently issue a post, write the detailed instruction. That works that doesn't work.
Thanks.
bilal_liberty said:
This rom from the above links works well, ive tried it.
Click to expand...
Click to collapse
Im getting an error?type=1 link when i go to that page, if you could attach the updater script so i could just switch them would be a big help.
Paint in more detail information on ROM.
From what device port that was done, lay out screenshots, competently issue a post, write the detailed instruction. That works that doesn't work.
Thanks.
Click to expand...
Click to collapse
Dont worry i will when i get it all up and running, its only a test version at this time. I have never made a ROM before and i have only published it this earlier because i need help in development which i am getting .
clewis said:
Im getting an error?type=1 link when i go to that page, if you could attach the updater script so i could just switch them would be a big help.
Dont worry i will when i get it all up and running, its only a test version at this time. I have never made a ROM before and i have only published it this earlier because i need help in development which i am getting .
Click to expand...
Click to collapse
Well, we wait for registration and the instruction, it will exclude many questions.
LeiManPRO said:
Well, we wait for registration and the instruction, it will exclude many questions.
Click to expand...
Click to collapse
I have registered and replied to a the original thread, got the download link and when i go to it i get an error, it's not there for me, if anyone has it please send the update script to me, i can't fix anything without that file.
clewis said:
Im getting an error?type=1 link when i go to that page, if you could attach the updater script so i could just switch them would be a big help.
Click to expand...
Click to collapse
Here u go best of luck
Edit: if you want some files from that rom here it is: http://www.mediafire.com/?mb04ljce767sd8m
bilal_liberty said:
Here u go best of luck
Edit: if you want some files from that rom here it is: http://www.mediafire.com/?mb04ljce767sd8m
Click to expand...
Click to collapse
Awesome mate, doing edits tonight will upload later.
This should probably go in some general Q&A forum, but this is by far the most helpful community I've come across so I wanted to try here first. I've finally got my Ubuntu box up and running again (upgrading to 14.04 wasn't pretty) and was able to build for both my 700t and my n5 without error, but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen? I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible. Any insight you may have would be most appreciated.
Thanks in advance!
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
psudeke said:
but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen?
Click to expand...
Click to collapse
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
psudeke said:
I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible.
Click to expand...
Click to collapse
That's normal - ARM devices are just too different, and the emulator is just another different device.
psudeke said:
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Click to expand...
Click to collapse
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
_that said:
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
That's normal - ARM devices are just too different, and the emulator is just another different device.
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
Click to expand...
Click to collapse
Thanks _That, I appreciate your help! After reading your post and the f2fs post, i thought i was in the clear, but i still managed to screw something up. i'm unable to get the tablet to boot off of external, regardless of whether its my ROM or CROMBi. I see a "segmentation error" listed in the output from the the preinit, and then it always boots to internal. I thought maybe i got the mount points reversed in recovered, so i reflashed recovery, but no luck. i also tried deleting the preinit script and then reinstalling CROMBi, but i still get the same error. any thoughts?
psudeke said:
I see a "segmentation error" listed in the output from the the preinit
Click to expand...
Click to collapse
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
You still get that fault with a static busybox but it seems to copy files fine.
@psudeke you can compile the static busybox yourself simply with make static-busybox in your build folder - or just steal mine from /system/boot
sbdags said:
You still get that fault with a static busybox but it seems to copy files fine.
Click to expand...
Click to collapse
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
it comes from the ls -l /init* which indeed doesn't have the busybox prefix but if I do it gives some other error I forget now
Anyway it doesn't harm the boot process - just an error message
_that said:
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
Click to expand...
Click to collapse
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
psudeke said:
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
Click to expand...
Click to collapse
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
sbdags said:
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
Click to expand...
Click to collapse
Ahh, thanks sbdags! that fixed the issue with ROM2SD. i got that impression when i pulled the preinit and saw it only had an entry for internal. but, i'm still very much in a learning phase so i didn't want to jump to a conclusion.
and after getting crombi to boot on external, i swapped sd cards and my build of CM11 actually booted! now the real learning process begins as i figure out how to customize it.
Thanks again to both you and @_that, you guys are the best:good:
@sbdags and @_that
Just wanted to thank you both again for your help. After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
https://www.dropbox.com/s/khq17h04b715eyd/C11%20Benchmark%20ART.png
Hats off to both of you! :good:
--- Guess I can't insert an image directly from my DropBox, link is to a screenshot of my score ---
psudeke said:
After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
Click to expand...
Click to collapse
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
_that said:
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
Click to expand...
Click to collapse
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
psudeke said:
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
Click to expand...
Click to collapse
Just ask away and congrats! :good:
sbdags said:
Just ask away and congrats! :good:
Click to expand...
Click to collapse
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
psudeke said:
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes your unwanted apps
note apps can be installed into 2 folders /system/app or /system/priv-app
similarly you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
sbdags said:
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes you unwanted apps
note apps can be installed into 2 folders /system/app or /systempriv-app
similar you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
Click to expand...
Click to collapse
Thanks again! i can see how this becomes addicting fast :fingers-crossed:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
psudeke said:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
Click to expand...
Click to collapse
just zip the /meta-inf folder, and flash that to test. obviously comment out any format commands as they will fail. That is what I do.
Hey @psudeke you ever need any help with anything to do with source or git let me know
I am also willing to help out
and just a FYI be careful of @sbdags :cyclops: LOL
Just kidding....
Let me know thx Josh
Please I need help..
After installing Movees Rom v6 (clean install) and reinstalling all the SAME apps that I had before I noticed that in my sdcard are autowriting a lot of files with the name XXXXX_beforeNS.pcm and XXXXX_afterNS.pcm (where Xxxxx are a serie of random numbers i.e. 547900132224_beforeNS.pcm ).
There are a lot of this files (with random dimensions) and even if I delete them they keep on appearing.
I can't really understand what is causing this and is driving me crazy.
Could you please help me?
Thank you very much
numero5 said:
Please I need help..
After installing Movees Rom v6 (clean install) and reinstalling all the SAME apps that I had before I noticed that in my sdcard are autowriting a lot of files with the name XXXXX_beforeNS.pcm and XXXXX_afterNS.pcm (where Xxxxx are a serie of random numbers i.e. 547900132224_beforeNS.pcm ).
There are a lot of this files (with random dimensions) and even if I delete them they keep on appearing.
I can't really understand what is causing this and is driving me crazy.
Could you please help me?
Thank you very much
Click to expand...
Click to collapse
Not really used that rom before but .pcm files are audio files, it might be files used by default by the rom which is why may reappear, have you queries this issue on the rom thread at all?
sofir786 said:
Not really used that rom before but .pcm files are audio files, it might be files used by default by the rom which is why may reappear, have you queries this issue on the rom thread at all?
Click to expand...
Click to collapse
Thank you for your reply, yes I've tried to ask also in the rom's thread but no one answered me
I upgraded from previous version of the same rom and reinstalled all the same apps, never had this issue before.
I don't know ... Why the rom should create audio files multiple times in the same day?
numero5 said:
Thank you for your reply, yes I've tried to ask also in the rom's thread but no one answered me
I upgraded from previous version of the same rom and reinstalled all the same apps, never had this issue before.
I don't know ... Why the rom should create audio files multiple times in the same day?
Click to expand...
Click to collapse
Hmm may be changes with the new rom version, only thing I can think of is to do a back up in twrp, do a clean wipe and reinstall rom and see if these files come back, I'd they do then it's defo something with the rom
sofir786 said:
Hmm may be changes with the new rom version, only thing I can think of is to do a back up in twrp, do a clean wipe and reinstall rom and see if these files come back, I'd they do then it's defo something with the rom
Click to expand...
Click to collapse
Ok I'll try this thank you!
Sorry if I write again but I didn't solve my problem...
These damned files keep going on appear!
Is there a way to log everything my phone is writing on the sdcard for trying to know at least which app is causing this issue?
Please this is driving me nut
Thank you very much
https://androidfilehost.com/?w=search&s=dreamlte
i flash this but cant boot stuck in s8 splash screen
That's interesting
Can't find any Github links of it
EDIT: This might use Albe96XDA's sources, but can't confirm
Do not have any videos?
manousos1 said:
i flash this but cant boot stuck in s8 splash screen
Click to expand...
Click to collapse
same here
https://www.cyanogenmods.org/forums/topic/lineage-os-15-1-for-galaxy-s8-android-oreo-8-1/
The latest unofficial doesn't seem to boot, seems there is a problem with the bootloader. I will try the first unofficial and see if it works. The uploader of the Rom has made previous roms for other devices so there is hope finally for our Galaxy S8
Omg this is real? Pls work on g955f too
Crossing my fingers !!!
Can any dev check the validity of this rom?
GeorgeChilian said:
The latest unofficial doesn't seem to boot, seems there is a problem with the bootloader. I will try the first unofficial and see if it works. The uploader of the Rom has made previous roms for other devices so there is hope finally for our Galaxy S8
Click to expand...
Click to collapse
test done with both rom unsuccessful - that of 21/11/2018 gives a black screen - that of 22/11/2018 gives a problem with the bootloader.
And you ?
tboguizmo said:
test done with both rom unsuccessful - that of 21/11/2018 gives a black screen - that of 22/11/2018 gives a problem with the bootloader.
And you ?
Click to expand...
Click to collapse
I have the same issue. The problem seems to be with the bootloader, i might be completely wrong. Is there any dev that can check the rom?
---------- Post added at 03:41 PM ---------- Previous post was at 03:33 PM ----------
The same dev also uploaded 2 AICP nightlies for our device. Or the developer confused code names for devices and this is not meant for our device
This is indeed for our device because dev has mentioned it is for "Galaxy S8" but highly doubt it is any different from the ROMs we already have that are not in a condition for daily use
I kept playing around with the rom for the past couple days and I pulled a tombstone file and it seems there is an openGL error. I have attached the tombstone file below. I'm not experienced enough to know what all of that stuff means lol
https://drive.google.com/open?id=1RZRV94t4UuZhcCDMCJuaFNe78DUNtVnN
GeorgeChilian said:
I kept playing around with the rom for the past couple days and I pulled a tombstone file and it seems there is an openGL error. I have attached the tombstone file below. I'm not experienced enough to know what all of that stuff means lol
https://drive.google.com/open?id=1RZRV94t4UuZhcCDMCJuaFNe78DUNtVnN
Click to expand...
Click to collapse
It seems there are other problems with the ROM, not just the OpenGL thing
"dlopen failed: library "/vendor/lib64/egl/get_process_name.so" not found"
You can try finding that file and placing it into the .zip file manually, unfortunately I can't test it because I have S8 plus, but no guarantee that it'll work
Kizoky said:
It seems there are other problems with the ROM, not just the OpenGL thing
"dlopen failed: library "/vendor/lib64/egl/get_process_name.so" not found"
You can try finding that file and placing it into the .zip file manually, unfortunately I can't test it because I have S8 plus, but no guarantee that it'll work
Click to expand...
Click to collapse
What about copying the whole of the vendor folder?
And placing them in the rom after the installation through the Twrp file manager?
GeorgeChilian said:
What about copying the whole of the vendor folder?
And placing them in the rom after the installation through the Twrp file manager?
Click to expand...
Click to collapse
That would work too.
Kizoky said:
That would work too.
Click to expand...
Click to collapse
So I just tried it and nothing changed which was weird. Then I go back to twrp and check the files and they're gone. They seem to get deleted every time the phone reboots for some reason I believe
GeorgeChilian said:
So I just tried it and nothing changed which was weird. Then I go back to twrp and check the files and they're gone. They seem to get deleted every time the phone reboots for some reason I believe
Click to expand...
Click to collapse
Yeah, that's why I usually like to replace/add something from/to the .zip file itself, nothing like that will happen
Kizoky said:
Yeah, that's why I usually like to replace/add something from/to the .zip file itself, nothing like that will happen
Click to expand...
Click to collapse
The zip has inside it a system.new.dat.br where all the system stuff are and I can't open it. Would I be able to just place the vendor files in the root of the zip and just update the updater-script?