Hey everybody! I've spent the last few months developing a custom ROM for my Samsung Galaxy S7 (SM-G930W8 Unlocked) and I've been running into the strangest issue.
So I have the ROM all up and working. It's great. Accomplished all I am looking for it to do. Debloated, Magisk Hide, MigiskSU, BusyBox, working without Xposed framework (waiting to update it to Xposed when Xposed for the S7 is a bit more stable), easy to flash with TWRP or CWM. Can also be manually flashed with Odin.
The cool thing about this ROM is that once I am finished making sure the ROM is bootable and all working 110% without major flaws I will be making it guest bootable. What I mean by that is allowing a "Light" version of the ROM to be loaded onto a external SD and bootable for basic functionality. The reason for this is to keep the custom image and the stock image separate so that should something happen with the custom image the stock image remains untouched. The secondary reason would be that I am hoping this will open the door for a way to utilize a custom ROM without tripping Knox.
Those are all semantics however and I am not even sure it's possible to do.
On to my problem.
The ROM runs flawlessly (as close to flawless as software gets) about 90% of the time. The major problem is it seems I have stumbled across a huge crash error. The ROM completely crashed and bootlooped. The funny thing with this is I wasn't even doing a stress test or anything. It has passed stress tests with flying colours actually!
However, during typical consumer use (watching videos and texting etc. Using it just like a regular user would) it started making a horrendous noise. Like the noise a computer makes when the disk in the tray starts skipping and sputtering. Like a fire truck horn.
I couldn't find any cause of this issue. I don't know if it was the browser (Samsung Internet) or the ROM or the hardware. My question is this:
Have any of you experienced this in the past and have you figured out the cause and the solution?
Any help would be awesome so I can fix a critical error in my project here.
EDIT
My Project is based of the stock Herolte Exynos ROM and Kernel. Nothing special quite yet. Once I solve all the major problems I will start tweaking a bit more but for now I am keeping it as simple as I can. Device info follows:
Samsung Galaxy S7 (SM-G930W8 Herolte Exynos)
Android Nougat (7.0)
Carrier: Koodo (Unlocked but bought from Koodo)
Changes made to the system noted above.
Related
Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter
Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.
Basically I bought Samsung Galaxy A5 2017, which was branded. Whilst I was using it the phone had all the operators’ apps and themes which I didn’t want. Also the whole phone was even crashing sometimes and was slow. I found a YouTube video showing how to de-brand my phone, and I’ve managed to de-brand it following some steps, after I have successfully de-branded my phone it automatically installed 7.0 Nougat and it got rid of all the crap inside, and then the phone was faster and smoother. Keep in mind I only de-brand it I did NOT root my phone, I also checked whether it is rooted or not from the root checker.
However as I was playing around with it and I found that I can’t access two apps ‘S Health’ and ‘Secure Folder’, for both of these there is some error message coming up, it says this:
S Health: Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices (0x100030522830)
Secure Folder: Secure Folder cannot be set up because unauthorised software was installed on the device.
I know this is the result of my phone being de-branded and maybe the current software is not compatible, I don’t really know, I have check all around the internet to find if someone has this problem and a lot of people have this issue but the way how to fix it is not clear, I couldn’t find a video which would explain clearly how to fix it and there isn’t much on forums either.
Please if anyone could help me solve this problem, my phone is new and I haven’t got much stuff there so if this problem would be fixed by erasing data like a factory reset then I don’t’ have problem with it, I also don’t mind rooting my phone, but I would prefer to have it unroot at least for now but if there is no other way then I’m fine to root it, it’s just that I need to know how to root it and I have to be sure it’s going to work, because I’ve seen that there are several roots and ways you can do it. Therefore I need to know which one is the most appropriate for this matter. And can I go back to the unroot state after I've rooted my phone?
And also can someone tell me. What if I wait for software update for example new Nougat 7.2 maybe it will fix this problem, or is it better just to fix it now whether or not it has to be rooted and don’t bother waiting. If the new software update can get it fixed and it’s guaranteed that it will. I can wait a bit, it’s not a big deal, but I would like to really use those two apps really soon.
If you have any questions or something wasn’t mentioned please ask.
Thank you for your time
Hey all,
I admit, I'm new to this whole android os thing, and this is only the second smart phone I've ever had. so far I gotta say, I'm not impressed with these things.
I've been banging my head against various bricks in this wall for the past three nights, and could really use some help before I decide to incinerate this Xperia.
Im trying to load and run Aosp 10 for this thing, but the few times I've had it stable, I've found It was really rather barren and honestly useless beyond strictly phone calls and texting.
over the course of these past three days, I've encountered; mounting errors (failed to mount oem/system/vendor,) issues with twrp becoming inaccessible (requiring a re-flash) after any successful operation of the Aosp 10 rom, at which point I may or may not be able to get the rom to boot again. Perhaps my assumption that they can coexist (basically a dual boot) is incorrect.
I've tried both the most recent & relevant standard twrp, and the Kagura version of twrp, to no avail. I'm still currently fighting "failed to mount /OEM". this has only ever resolved randomly (seemingly) in the past, only to crop back up again. I've formatted everything (short of the sd-card) 6 ways from sunday (getting the "failed to mount /OEM" the whole while during this operation).
I've tried older versions of roms, twrp, etc..
I'm burnt out on this trouble, and perhaps my choice of rom or phone was a mistake. All I'm after here is a rom (or phone, or hell, maybe a PDA) that works reliably, doesn't glitch a ton, have its screen adhesive fail, or suffer encryption so deep and aggravating its useless for simple and plain operations (looking at you APPLE). A "set it and forget it for a while, works when I need it and doesn't glitch out when needed,
well thought out and designed device.
Point me in the right direction here guys. My programming days are years behind me and the rest of the world, and I've not got the time or patience to learn & write a new rom/os from scratch.
sincerely-Psykora
Hi,
I got "new" phone, model as per title. It appeared it's been previously rooted and has Magisk installed. Poor creature selling this to me has no idea about those things and he got it like that from his friend in different country.
As this is replacement of my personal phone, after I sunk S9+ and decided to break up with "S", I have not much eagerness to experiment.
Current firmware (as what phone shows) is V30c-KOR-XX seems based on Android 11.
I'd leave as it is but... Google Pay doesn't like the fact phone is rooted. I have no issue with that phone is rooted but with that I can't use Google Pay.
Additionally, despite setting EN-US as language I see lots of Chinese or Korean or Japanese "letters" here and there - not causing any more issues than esthetic. I'd prefer to not have it so probably to load phone with some different firmware. Would be lovely if that could actually have "Polish" (as I am).
Also, I tried to get to "recovery" and phone does not react to Power+Vol Up - please correct me if that's not the right combination. When I used Magisk to reboot into Recovery then I see "No command" message...
Magisk is current - 24.1 and same "app".
So my options would be:
- fixing what is currently (ignore not having Polish on it) and making GPay works
- loading some factory firmware and unrooting it
- loading something different which would also allow to make GPay to work
I'm not complete noob, and got years of Linux exp as this is my only OS I work on. Also I was playing with rooting, firmwares and kernels but that was age of Samsung S2 and S4 when I did it last time, therefore I know many things changed and some might be easier some harder to do. Additionally, this is my first LG as somehow I always had "S's".
What I'd like to ask community here is to help me determine exact (versions, links) software I possibly could use and provide some guidance on how to do this "these days".
So to make things easier, I will ask questions:
1. What firmware should I load and how (preferably using Linux)?
2. How to fix (if necessary) "missing" recovery ?
3. How to make GPay running if suggested firmware is not factory one?
To be clear, I don't mind using current firmware loaded on phone if I can make things work. Less work is better for me as I can't be left without phone for longer than a day.
hi everyone! I just wanted to explain my situation here so that maybe someone can help me understand what is happening.
I own the Exynos variant of this phone 12/256.
Being a huge fan of debloating my entire life, i got the phone and after some time, seeing that the battery life won't improve, I started digging.
At first, i have removed MANY apps that are useless, but have never touched system related apps, maybe bixby or smth. Nothing happened. Then the OneUi 5.0 came, beta, installed it, then the stable came, installed it, had a factory reset done to start fresh and i got to debloating again. And for about two weeks everything worked smoothly. Then i was at work one evening and i started seeing my phone acting weird, mobile data going on and off(kinda always on 4g+ at work) so i decided to restart the phone. Clicked restart, put it in my pocket and after 5 mins i felt it warm in my pocket. Checked it and saw it was restarting in a loop and after a few more restarts it said " rescue party/ etc/etc, your phone failed to restart multiple times bla bla". The only way to get it up and running was to delete all apps inside that menu then the phone would boot in safe mode so i could backup my data, then i had to factory reset it again. This happened 3 times, in a 1.5 week period. Last time i debloated, i only uninstalled youtube, youtube music, microsoft onedrive, etc etc. Haven't even touched anything related to a system app, because in that menu it would say some system files are missing or smth like that. This evening I ve got the update with the November security patch, downloaded it, installed it and now it's looping again.
Does anyone know what might be the cause? Because obviously i didnt get rid of any system app this time.
Contact Samsung support. Possibly to be replaced under warranty
Maybe just download a firmware that doesn't have much bloat then see if the issue keeps happening without you debloating. If it doesn't happen anymore and then you start debloating things and it happens, then you know your problem.
More than likely you've de-bloated something you shouldn't have.
Back up all your data (if you're still able to), then factory reset & flash clean stock ROM.
Thereafter, flash a de-bloated custom ROM or do a very careful de-bloat yourself (plenty of guides on XDA).
Everything I've debloated was done side by side to a parallel xda thread for samsung debloating, it's not like it was 100% out of my head. Disabling bixby, microsoft onedrive, samsung free, upday, ar core elements inside and out of the camera, live messages from the s pen doesnt look to me like it should make the phone go bootlooping.
I've flashed the first stable firmware last night after the incident, updated it to the latest november update and I'm keeping an eye on it. If it randomly goes bootlooping and to rescue party, I'm taking it to samsung in my city.
stefancrisxd98 said:
Everything I've debloated was done side by side to a parallel xda thread for samsung debloating, it's not like it was 100% out of my head. Disabling bixby, microsoft onedrive, samsung free, upday, ar core elements inside and out of the camera, live messages from the s pen doesnt look to me like it should make the phone go bootlooping.
I've flashed the first stable firmware last night after the incident, updated it to the latest november update and I'm keeping an eye on it. If it randomly goes bootlooping and to rescue party, I'm taking it to samsung in my city.
Click to expand...
Click to collapse
dont root your phone, you might lose your warranty.
i see you flashed the firmware so keep an eye one the phone, debloating shouldnt have to do anything with this issue, a lot of us debload and have not faced this kind of issues.
i did debloat mine, i bought my phone with A12 and it took me 2 days to set it up including the date transfer and debloat, then i received A13 which i installed and kept using it without a reset which i should have done but i was very busy.
I haven't rooted this one, not yet because it's new and I don't need anything root acces can give me at this popoint. Although I have rooted many phones before, including samsung, I've never encountered this before, even though I've seen it was introduced by google in A11 or smth. I dont know.
What variant is your phone? Maybe you can give me a file with what you've debloated so far to compare.