Related
:crying::crying: Upgraded to 4.2 using sp flash tools, flashed custom roms, was very satisfied but then a problem occured and i flashed stock 4.1 which created all sorts of problems like flash not working, music and images not being read from the phone,etc. Tried something else flashed custom roms, stock rom etc and got the music and images to be displayed but no luck in flash . Was on Melting Rocks custom rom(credits rmuntazir) and just now flashed jb,still no luck with the camera flash. It was working absolutely fine before. I dont remember when the problem started. Please help me and could you tell me what went wrong?
P.S. Even flash light apps are unable to access it. When I open the app and switch on light there is no change but the app tells that it has switched on flash
Back camera hangs most of the time; it works sometimes but most of the time it freezes and FC itself saying "Unfortunately, Camera has stopped." Front camera always works fine.
The back camera wont FC itself all the time, sometimes it just stays black (with all the buttons and interface working), and sometimes it stays with a freezed image of what the camera sees (also with the interface ok).
I've tried full wipes, I've flashed different roms, with different kernels; cleaned the camera's cache and data; tried the "Restart Camera" solution/workaround; I've even tried to "tap the camera hard" as some people has suggested.
What I haven't done is flashing stock rom, since I consider it won't be of any help (But if you advise me to, I'll do it). And I haven't tried Roms that are not 4.4.4
I'm currently using AICP Rom (4.4.4)
Sorry for any typo.
JCNouel said:
Back camera hangs most of the time; it works sometimes but most of the time it freezes and FC itself saying "Unfortunately, Camera has stopped." Front camera always works fine.
The back camera wont FC itself all the time, sometimes it just stays black (with all the buttons and interface working), and sometimes it stays with a freezed image of what the camera sees (also with the interface ok).
I've tried full wipes, I've flashed different roms, with different kernels; cleaned the camera's cache and data; tried the "Restart Camera" solution/workaround; I've even tried to "tap the camera hard" as some people has suggested.
What I haven't done is flashing stock rom, since I consider it won't be of any help (But if you advise me to, I'll do it). And I haven't tried Roms that are not 4.4.4
I'm currently using AICP Rom (4.4.4)
Sorry for any typo.
Click to expand...
Click to collapse
What roms have you tried? Maybe flashing stock rom will solve your problem. When this this problem start occurring?
gsstudios said:
What roms have you tried? Maybe flashing stock rom will solve your problem. When this this problem start occurring?
Click to expand...
Click to collapse
Hi, thanks for replying. I've lost count of how many, but as I remember, they all were KK Custom Roms, the ones I remember I've tried are AOKP, CM11, and AICP.
It started since... I don't even remember, it has been so long, I just hadn't been able to try to fix it, untill now.
I flashed the stock JB ROM and it fixed it. So I thought that there were corrupted files and since I have them now, I was going to work again if I flashed the AICP ROM back... but nope, it has the same issue.
I'll flash a JB Custom Rom (Probably CM10.2) to see what happens.
Update: I flashed a JB Custom Rom (Fusion Rom) and the camera is working good so far.
But still not working in KK.
I just rooted my phone (Samsung S6 Edge [SM-G925P] running Android 6.0.1) this Friday and I have a couple of questions about using the CyanogenMod ROM and installing Xposed. To note, I am pretty, pretty new (I literally just rooted 2 days ago.
So my question about CyanogenMod is will it run on my rooted Samsung and is it dedoxed? I already have TWRP and SuperSU flashed and installed on my phone.
And my question about Xposed is will it run on my phone, as well with CyanogenMod, TWRP and SuperSU? I tried installing it with the original ROM on my phone, but that provided to be disasterous since it soft-bricked my phone, but I heard that was because my ROM was deodexed.
Hi NovaViper ! It depends. Cyanogenmod and other ROMS can come in two flavors: odexed or deodexed. The one on the official Cyanogenmod Website is deodexed. If you go on Cyanogemod's official website they don't have a ROM for Samsung Galaxy S6 / Edge. Check it out: http://download.cyanogenmod.org/ Look at the left to see supported devices. Unfortunately, it's not there. Some Galaxy S6 / Edge models do support Cyanogenmod but as for your model the SM-G925P there is still no official support for CM ROM. Check this link out: http://forum.xda-developers.com/gal...development/cyanogenmod-13-galaxy-s6-t3269984 Just out of curiosity, why do you want to install CM on your device?
I want to try CM because I heard it offers full customization.. I really would like to customize the lockscreen and colors of the UI especially and because it is deodexed, so I can also add Xposed. I have another ROM atm called Mostly Stock (its based on ROM but its deodexed and have a few changes to the stock UI, BUT it still has the parts I hate about the stock ROM). I specifically want CM because I haven't found any other ROM that offers full customization, deodxed for Xposed, and most importantly, is not like the stock ROM.
Oh, also with CM, I tried to install it but it said my device isn't support.. I tried the one from the link
If you want a full stable ROM for Samsung Galaxy S6 Edge and XPosed on it I would recommend this ROM: http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519. My friend has it on his ROOTED S6 Edge and it offers even more customization's then Cyanogenmod plus you can install XPosed on it. Give it a try.
Thanks I already flashed it but I notice that it isn't responsive to touch. I can interact with the buttons but no response to touch whatsoever. Seems like there isn't a ROM that works with my SM-G925P, the edge that rom works with is a G925F
Hmm, I thought it would work on your model. Try this: http://androidfreeroms.com/renegade-android-m-6-0-1-aroma-rom-sprint-samsung-s6-g925p/
I got the rom flashed and running.. but i cant seem to restore my messages from the samsung backup.. i can only get them from Textra (which doesnt export them). Also, i cant receieve text messages either.
Well, I finally got my messages backed up but.. I notice something else now. I had installed Xposed, which ended up giving me a bootloop and I had to factory and data reset, and reflash my stock rom. then I installed TWRP and then Renegade, but the mobile data isn't working anymore. Its just black the black bars.. I can't even find the Mobile Data enable button anywhere. (It works on stock rom though). To point out, mobile data WAS working before I installed Xposed. Right now, I'm reflashing my stock rom and seeing if it works.
--UPDATE 1--
Yeah, the stock mobile data works.. although I do have a theory on what could be going on
Theory 1: It could be I have to install my ROMS a certain way, initally, I had stock ROM, then I added the "Mostly Stock ROM" THEN I added Rengeade when you suggested it to me
Theory 2: Possibily signal strength/proxies (I'm doing this at on my school's wifi)
Theory 3: Something that Xposed has modified and its still there
--UPDATE 2--
I did the first theory and it worked successfully BUT.. I did remember that I had installed SuperSU soon after flashing twrp (which came after i flashed the stock rom).. Now I'm trying to see if that made a difference.
--UPDATE 3--
Ok, so it seems that it is a certain install order (tried with both superSU installed first and without). But I'm worried now about installing Xposed.. as I'm now nervous that it may end up messing up my phone again (It took a while for me to figure out how to get it back working.. as it ended up bricking with continuous looping and even factory resetting/clearing data off didn't work. I had to flash the stock rom for it to work again)
Interesting. My friends all have the International version which is G925F. Yours is Sprint ? Or some other cell phone provider ?
If your model goes haywire with simple custom rom installations and other apps than I wouldn't risk installing XPosed BUT if you do then try to follow these instructions... they work for your model:
https://xtremetricks.net/install-xposed-framework-android-6-0-6-0-1-marshmallow/
My phone is Sprint and I downloaded Xposed from the Magitsk app and it worked without bricking my phone.. I wonder why it was acting up
Strange thing, I seems I HAVE to install the 'Mostly Stock ROM' BEFORE I add Renegade.. the mobile data works to not work at all without installing Mostly Stock first.. How any idea how to fix this?
Well, I tried installing Magisk and it bricked my phone once again.. I'm really confused with whats going on. I have a backup of the stock ROM from SamMobile. What I want to do now is completely clear off ALL data from all of the roms and just start over, is that even possible? Also, if I delete the system files, do I HAVE to install the Stock ROM first, or can I just add the custom ROM and it will add the OS?
Well normally for rooted phones, you only add the custom ROM and it will automatically add the OS. I have no idea why you having so much problem with it. Did you unluck the bootloader ??
Yeah.. (I think), I made sure OEM Unlock is enabled and USB debugging is on.. Not sure what could be causing such problems with my phone.. I honestly wish I knew
What method did you use to root your phone and unlock the bootloader ?
I used the systemless method (installed TWRP, then installed the latest SuperSU which used the systemless method by itself) and I think I did.. there was an option where I had to enable (it was called OEM Unlocking, it was preventing me from flashing)
And I forgot to ask another question.. should I (and if such thing is possible) wipe the system/ folder and then install the custom ROM onto my phone without having to add the stock one at all?
What I would do if I were in your shoes is I would unroot and re-lock your bootloader again... see this article for unrooting: http://howunroot.com/unroot-supersu/samsung/galaxy+s6+edge+sm-g925p/5.0/ Now... once you unroot your phone... I don't think re-locking your bootloader will have any effect... but you can try to relock your bootloader and bring it to the original state meaning factory... once there just follow these instructions step by step: http://www.ibtimes.co.uk/skipsoft-toolkit-galaxy-s6-edge-root-unlock-restore-flash-stock-firmware-drivers-more-1517879 Once you root it and unlock your bootloader again, and after your install TWRP, go into TWPR, wipe dalvik cache, wipe system, wipe everything ... and then instlal the custom ROM that I gave you in the link, and it should be working find without problems. Try that and get back to me and update me... if you have any questions then just post it here and I will help you as much as i can.
I don't think I unlocked the bootloader because I looked up the instructions to how to unlock the bootloader and I didn't do that.. all I did was enable OEM unlock, is that the same thing as unlocking the bootloader? If not, how do I unlock the bootloader?
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
Newbie to flashing - to my surprise successful first attempt recently with Oreo - lineage-15.1-20200313-UNOFFICIAL-flounder - worked quite well and much perkier than before. Then realised none of my six screen recorders would work, so decided to try downgrading to Nougat - lineage-14.1-20200217-UNOFFICIAL-flounder - but got stuck on the Google screen on first boot.
So tried a few other Nougat ROMs: Slim-flounder, aokp_flounder, purenexus_flounder, Fire-Hound and FIRE-ICE - all getting stuck on Google. I must be doing something wrong. Reflashed Oreo, without problem!
Used the same procedure for all Nougat and Oreo ROMs: twrp-3.3.1-0-flounder to wipe everything, installing the ROM, open_gapps-arm64-7.1-pico-20200325 and SuperSU-v2.82-SR5. (For Oreo I instead used open_gapps-arm64-8.1-pico-20200325). What am I doing wrong?
Install stock Nougat firmware or install stock Nougat vendor. After that, install the firmware you want.
Thank you, will do!
Need more help pls! Downloaded the factory rom - "wrong zip version" when trying to install. Downloaded vendor and bootloader img-files. How install?
Figured it out! Thanks Vartom! Remains to be seen if I can get any screen recorder app to work.
Installed lineage-14.1-20200217-UNOFFICIAL-flounder and tested my usual screen recorders. Mobizen did not work, but all others did: Recordable, SCR, DU Recorder and AZ screen recorder. Am very happy with that and with my "flounder" being much perkier than with Marshmallow.