Related
hello.
i have run into some problems when trying to install the stable mod described in the guide from the sticky post at the top of this category. well more or less, i referenced other guides as well but they were all effectively the same.
after rebooting post installing the cyanogenmod image my phone seemed to be functioning fine. i noticed that the google apps were not available (despite having used the backup and restore proprietary google apps from the recovery menu) so i restarted the phone in recovery mode and flashed the google addon and rebooted again. as soon as the phone came up this time it started throwing up error messages:
"Sorry! The process com.android.phone has stopped unexpectedly. Please try again."
i can dismiss the error dialog but another replaces it. sometimes the process named is different. i cannot recall the other examples right now. i have tried to turn the phone off with the power button, the confirm dialog does appear but is buried under the error messages mentioned above and i cannot get to it to confirm. i have tried holding the power button down hoping there is some hardware shut down. no dice. i am getting ready to pull the battery but thought i better throw this out to the masses before i did so.
huh interesting. it just stopped doing the above. it chimed and then displayed the boot screen in a frozen state.
the only way i deviated from the general directions in the above mentioned post were to flash the google addon package after a reboot as mentioned before.
how safe is it to pull the battery and what would the next steps be? if i wipe the "data/factory reset " and then reinstall the cyanogen img will i be back where i was before the google addon install? i am not really sure what command eliminates the android installation. perhaps i need to do a more extreme wipe of the device. alternatively i can execute a nandroid restore.
now it is back to the dialogs again.
i am mostly concerned that pulling the battery may brick the phone. am i being irrational?
the phone is a nexus one. i am in the uk on vodafone if that is relevant. the packages i installed are the ones listed on posting above.
i did not flash the radio.
any help would be greatly appreciated.
e
edit- i have fixed the issue. i was able to use the adb reboot utility to boot to recovery mode. from there i was able to restore my backup image. i then retried installing the cm and addon packages and kept having the same issue. finally i tried to download a new version of the addon img and that worked. for some reason i had to unmount and remount my sd card after i got everything working again.
correction
sorry the packages i installed were not the ones listed in the post above. they were the ar recovery img (that was the same) the cyanogenmod 5.0.6 image and the google addon.
Does anyone have a definitive guide to fixing private mode? I hid some pictures before rooting and installing xposed (which broke private mode). I have Wanam's xsecurity module installed but it didn't fix private mode. If there is no way to fix it, where can I access the hidden files. Any help would be greatly appreciated.
Narekrocks said:
Does anyone have a definitive guide to fixing private mode? I hid some pictures before rooting and installing xposed (which broke private mode). I have Wanam's xsecurity module installed but it didn't fix private mode. If there is no way to fix it, where can I access the hidden files. Any help would be greatly appreciated.
Click to expand...
Click to collapse
found this in tmoble section... should work for the phone also check it out...
http://forum.xda-developers.com/note-4-tmobile/general/private-mode-try-test-t2922671
Narekrocks said:
Does anyone have a definitive guide to fixing private mode? I hid some pictures before rooting and installing xposed (which broke private mode). I have Wanam's xsecurity module installed but it didn't fix private mode. If there is no way to fix it, where can I access the hidden files. Any help would be greatly appreciated.
Click to expand...
Click to collapse
hi ,
OK , as far as i know Private mode is broken when you root .(my experience )
i have N910F device( Snap and rooted ,etc .)
I followed this post # 22 and # 32 @ angelky ,
yes it fixes S health, but also fixes Private mode ( link ) and it fixed my "lag " caused by Xposed
http://forum.xda-developers.com/note-4/help/xposed-t2904937/page3
I have seen other "fixes " Wanam thread/ fix
http://forum.xda-developers.com/xposed/modules/app-xshealth-bypass-secure-storage-t2878708
There is other threads with "fixes "also ..just choose which one to follow ?
good luck
I have tried pretty much everything I could find on XDA. Including wiping the phone, freezing the apps and then installing xposed. I guess there really isn't a proper fix
If you have previously configured Private Mode without Xposed Installed, then you can not access it anymore after installing this framework. But there is a method to make it work again without wiping all data.... Check this tutorial:
http://www.mobilecentre.pl/how-to-fix-private-mode-in-samsung-galaxy/
Hi,
Sorry but personally, the private mode was broken when I restored the data of system app with titanium backup. To solve it, I must factory reset and restore ONLY THE DATA OF USER APP.
Hi,
I've recently updated my N910F to Marshmallow (official). It's not the latest version but I wasn't able to download that one yet.
I made a fresh install with it (factory reset via TWRP, flashed it through ODIN, rooted via CF Autoroot, installed TWRP 3.0.2-0 and XPosed v84, restored Apps trough Titanium) and even reflashed it with a wipe of system, cache and dalvik cache before because of problems with auto rotate.
But the Fingerprint API or something like that seems to be not working how it should. I can't set screen lock to Fingerprint (I get asked "Enter a backup password.", wenn I enter one, it just says "Sorry, try again" without saying why it failed), even after going to security settings and deleting the credeintially, which fixed such problems on 5.1.1 it doesn't work.
I also had read, that you could use your Fingerprint for authentication in PlayStore, but at least in version 6.7.12.E I can't see that option.
PlayStore should use the API of Nexus Imprint for that and I thought that this is required by any OEM that want's to get a license for M, so I don't really see why it doesn't show up.
The sensor itself seems to be working, I was able to register my fingers and with FingerLock, an app locker designed for Samsungs proprietary Fingerprint API form earlier versions, I also have no problems.
I think, Samsungs own implementation is working (accept for Lock screen but they´could have changed it here for the official one), only apps for Googles standardized one are failing. But I can't really prove it. An app, that should be using the official API in M is failing, but the developer says it's a problem only with the Note 4 and he hopes he can publish a fix later this month.
The app locker MaxLock, which I thought would use fingerprint authentication with the official API doesn't show up an option for that but maybe through problems with the implementation.
Is there any way to test what's going wrong?
PS: sorry for the long text
I now have this..... Any solution?
Get a (non-TW based) custom ROM. It's the only thing that's works since Samsung most have screwed up the whole API. Their own is only useable partially and the standard one by Marshmallow is completely messed up and not worrying at all.
I was so pissed off of Samsung's incompetence that I switched to emotion ROM. It's a bit tricky to set up the fingerprint reader, but once it's done, everything using the official API is writing flawlessly. Never gonna switch back.
Hi!
I rooted my galaxy s7 edge that had stock version of android 7 (nougat) on it using this tutorial: http://www.droidviews.com/install-twrp-root-galaxy-s7-and-s7-edge-on-nougat-g935fxxu1dplt/. Now when I open built-in camera app it shows me a black screen for few seconds and then it says "Camera has stopped" and it offers me to "Open app again" and "send feedback" And it keeps happening over and over again.
Lemma: The reason is rooting.
Proof: Camera app worked perfectly. After I rooted my phone it started to crash like I described above. Then I tried to force quit camera app and delete it's cache/data. It did not help. After that I wiped entire cache partition. Still no help. After that I wiped all partitions except system. That did not work either. Then I re-flashed unmodified original stock ROM. Then camera worked perfectly again. Then again I rooted my phone the using tutorial I linked above. And again exactly the same issue. Camera app show black screen for few seconds and then crashes with exact same error message. ∎
Does anyone know fix for that? And why it happens? Is it some kind of samsung's anti-root thing that prevent camera fromworking on rooted phones or what?
Update [SOLUTION]:
In case someone else has same problem.
My solution was to skip restarts in TWRP steps. No restart between format and installing packages. Restart once when everything in TWRP part is done.
Root doesn't break your camera
I just Rooted my G935F that had Nougat as official firmware and had zero problems with the camera.
Sent from my SM-G935F using Tapatalk
I have international version of samsug with exynos CPU. Maybe this changes anything?
Root doesn't break your camera
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
I downloaded original firmware from here: https://www.sammobile.com/firmwares/database/SM-G935F/ (I chose baltic (only 1 occurrence in the table))
Maybe that specific tutorial I linked is bad one? Could anyone check that?
Rooted my G935F and no problems here for me.
I suggest you follow the tutorial here on xda and try again.
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
sysctl said:
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
Click to expand...
Click to collapse
A simple search here you'll find all you need. You are the only person I've ever read of that had camera problems like you've stated after Root. Again rooting won't break your camera.
I've Odin to stock literally hundreds of times testing Rom/Mods/themes as a tester for several teams from my s3 up to and including my G935F.
I've also flashed every Rom available for the G935F and the only ones with camera problems are the Lineage or AOSP Roms which more than likely are kernel related. Start here https://forum.xda-developers.com/announcement.php?a=81
Then this
Here's one
https://forum.xda-developers.com/showthread.php?t=3489011
sysctl said:
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Again rooting won't break your camera.
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Ok here is what you need to do.
Download a logcat app and get a logcat of it forceclosing.
I can't magically look in your device and see what, if anything is wrong.
As far as you saying you've searched well if you really did you would've found several tutorials.
How do I know?? Because I've used them myself.
It took me less than 5 minutes to root my new G935F using the TWRP Guide here on XDA
You seem to be the only one in hundreds that's claiming root broke your camera.
Provide a logcat in the Q&A and maybe a dev can help you.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Sent from my SM-G935F using Tapatalk
You could try to reset your settings
Same issue on smg935w8 lost camera and screen brightness. Also can't mount micro sd... we're you able to fix? I thought it was a bad root then I re flashed and the issue came back...twrp 3.1.0 supersu 2.79 and no verity 5.1
---------- Post added at 10:15 PM ---------- Previous post was at 09:50 PM ----------
im re flashing stock and tomorrow ill redo twrp and super su and skip dm verity patch think that might be the issue as it worked before for me last week and i then messed up by turning dev mode off and disabling oem and when i reflashed after that i have been flashing the dm verity patch....
give that a try if your still having issues
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Gray.Fox said:
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Click to expand...
Click to collapse
Thanks I've tried clearing cache for everything no luck. I originally thought it was because I might have deleted a system app with titanium but when I reflashed it all (firmware,tarp,supersu,no small verity disable 5.1) I still had the issue.
Lastnight I wiped and flashed the entire firmware. Everything works. Tonight I'm goi g to try and only flash twrp then supersu as I only want root. Hopefully that fixes my issues.
OP have your issues been resolved?
I'll let you know once I get it working on mine and we'll get you sorted out. I believe it's something with the steps or order as I had root fine for a day then had to reflash due to messing around and didn't do it my original way and that caused my issues.
flashed twrp 3.1.0 from odin with auto reboot off.
then booted to twrp. swiped right to mount system,
wipe data(format data) type yes.
mount microsd as mtp copy supersu 2.79 over if its not already on you microsd card.
else just install it from zip
cleared cache/delvik
rebooted to system
log in and setup everything and restore
camera and auto brightness...stilll doesnt work.
ok so after multiple tries to fix this (flash stock) everything works,, root and it breaks tried clearing all cache in system and twrp no difference... then i loaded phone info and used the secret codes to find out that my camera firmware is not installed....so im trying Flashfire to reflash the AP only while injecting supersu and maintaining root.... it is just booting up.....and OMG!!!!it works!!!!
so....for some reason...firmware was corrupting..... no clue why tired multiple methods and nothing... and im not a noob either.....
what finallllllllly worked was.... flash your rom and get root how you would normally. camera/auto brightness/and mounting usb doesnt work....boot to twrp. get your ap md5 file on your internal storage
reboot to system,. get flashfire from playstore or chainfires website
install and then click the + select firmware and select the tar file
only install system....uncheck boot and cp
then in the everroot select injject supersu, preserve recovery
and flash.... it will start flshing and boot to syteem once done..
everything is working nice
finalllyyyy!!!!
hope this can atleast help OP
no clue why i was losing firmware on the flashes
@unit68 Tnx for sharing. This time I got camera and brightness adjustment work out of box. But if in any point of time I happen to need your tutorial, I'll give it a try and let you know.
I am not sure if it is by chance or not but what I did differently this time was:
1) I paid attention to step where it asked to disable auto reboot (can anyone explain why?)
Previously I thought it shouldnt matter so I kept auto reboot for convenience.
2) I did format data, install no-verity-opt-encrypt-5.0 and SuperSU-v2.79-201612051815 and wipe dalvik cache with out rebooting between (Anyone know if that matters?).
Previously I had done it: format - reboot - install no enc - wipe dalvik cache- reboot - install super su - wipe dalvik cache - reboot .
Now I did it format - intall no enc - install super su - wipe dalvik cache - reboot.
I'll see for few days if anything else comes up or if camera breaks down again. Btw @unit68 what happens when you try some bloatware remover that run with root access? Do you get rid of bloatware or not? I tried few of them such as no bloat for example. Some complain that uninstall failed some seem to uninstall the app but when they reload app the app is still there and it's also still in app menu. Just curious if you have the same same issue. And is it safe to delete apk file manually? Or would it cause phone to crash/boot loop? When I ran supersu it complained about knox and asked me to disable it but it never managed to (however root checker tells me I am root). Maybe knox is protecting bloatware? Any ideas?
Flash your able too get it working! It was soooo frustrating. So for Knox supersu asks to disable then seems to hang so I go about my business reopen supersu it'll ask again and then is successful.
To remove bloat I normally just go to titanium and remove the ones I don't want
No issues on that and all my apps that require root work fine (titanium,adaway, flashfire)
This time disabling knox worked too... It turned out that all 3 apps that I used were note able to remove bloatware. App you named worked and also ROM toolbox lite works.
Btw when I google bloatware, the lists are incomplete.... Do you happen to know list of apps that must not be uninstalled? I guess white list would be better idea than black list.
Is installing/uninstalling app same as removing/adding apk files? So that I could cut and paste everything expect file manager and launcher to usb memory stick and then start adding required apps back one by one?
ive seen some samsung debloating software around. i honestly just remove stuff based on manually debloating for last fewyears. if i dont know what theapp is for i google it to see if its ok to remove. normally i remove samsung knox, few other samsung apps, some google apps (music, games, videio), briefings some edge panels, live wallpaper, and carrier branding apps(for me rogers) stuff like that. if you are going to i recommend you do a backup first as it ccan mess up your phone if you uninstall an important app. . also once your do uninstall you need to reboot ... the paid version of titanium allows you to freeze applications so you can try that first before removing it.
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
ScreAmeR01 said:
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
Click to expand...
Click to collapse
Interesting..ill check that if I need to to Flash. I have 2.79 but maybe I grabbed an old version or a beta. Mine says 20161205 I think it may have been sr3
Edit _ just checked I grabbed sr0 the stable release from 20161215 not the sr3 beta
Maybe it was corrupt when I flashed
hello, i have a new problem found few days ago and been trying to fix it but to no avail.
here is how it started.
i tried to install an app called fsecure vpn network from google play. then the phone when into a bootloop. then i did a clean wipe (reset, wipe cache and dalvik from recovery) but somehow my files were not gone. that is some kinda miracle i have no idea how it happened.
since then my phone have issue whenever i installed mihome:
-. google play services, trebuchet, package installer, and some other has stopped.
-. cannot open apps list in settings when mihome is present. the settings just stopped and crashed.
-. if i try to open the mihome, the phone goes reboot.
-. even uninstalling mihome from application list is not working, the package installer stopped. have to uninstall from google play.
-. i tried to make a bluetooth printer app, but when i put the app-debug.apk into my phone. file manager would crash whenever it tried to read the file. even by just scrolling down. example: file manager work fine if the file is not copied inside (meaning we can scroll around and not crash). but once the file is copied in then the file manager will work if we dont scroll down to find the file, but when we scrolled down to find the file then the app crash.
things i've tried:
-. clean wipe then reflashing rom and gapps.
-. manually update google play store, download google package installer and reinstall it.
-. tried to download google play services apk but was unable to install it.
-. tried the idea of clearing cache of google play service but still no luck (force stop was disabled anyway so i cant try that)
i have no idea how this all happen just because i tried to install that fsecure app. its not even fully installed yet. it was just starting to install after download then this hell happened.
im desperate for some help as i've tried for 3 days in fixing it but to no luck. any helps would be very appreciated.
thanks and regards,
hendry
yohhendry said:
hello, i have a new problem found few days ago and been trying to fix it but to no avail.
here is how it started.
i tried to install an app called fsecure vpn network from google play. then the phone when into a bootloop. then i did a clean wipe (reset, wipe cache and dalvik from recovery) but somehow my files were not gone. that is some kinda miracle i have no idea how it happened.
since then my phone have issue whenever i installed mihome:
-. google play services, trebuchet, package installer, and some other has stopped.
-. cannot open apps list in settings when mihome is present. the settings just stopped and crashed.
-. if i try to open the mihome, the phone goes reboot.
-. even uninstalling mihome from application list is not working, the package installer stopped. have to uninstall from google play.
-. i tried to make a bluetooth printer app, but when i put the app-debug.apk into my phone. file manager would crash whenever it tried to read the file. even by just scrolling down. example: file manager work fine if the file is not copied inside (meaning we can scroll around and not crash). but once the file is copied in then the file manager will work if we dont scroll down to find the file, but when we scrolled down to find the file then the app crash.
things i've tried:
-. clean wipe then reflashing rom and gapps.
-. manually update google play store, download google package installer and reinstall it.
-. tried to download google play services apk but was unable to install it.
-. tried the idea of clearing cache of google play service but still no luck (force stop was disabled anyway so i cant try that)
i have no idea how this all happen just because i tried to install that fsecure app. its not even fully installed yet. it was just starting to install after download then this hell happened.
im desperate for some help as i've tried for 3 days in fixing it but to no luck. any helps would be very appreciated.
thanks and regards,
hendry
Click to expand...
Click to collapse
Hello,
Did you try to reinstall Stock ROM ?
https://www.sammobile.com/firmwares/galaxy-grand2/SM-G7102/
It happened to me that sometimes, apps or rom just run into a bug and maybe it corrupt the firmware but after a Stock ROM flash (via Odin) + custom recovery (via Odin) to wipe Cache + Data, everything was fix.
Hai, could u possible post me a tutorial on how to do those thing via odin? Coz i usually only do it via cwm. Thanks
yohhendry said:
Hai, could u possible post me a tutorial on how to do those thing via odin? Coz i usually only do it via cwm. Thanks
Click to expand...
Click to collapse
Hey, maybe this one ? https://forum.xda-developers.com/showthread.php?t=1372414.
yumi14 said:
Hey, maybe this one ? https://forum.xda-developers.com/showthread.php?t=1372414.
Click to expand...
Click to collapse
hello, im currently trying to download the stock rom however i couldnt seems to be able to find any working download link for indonesia version of firmware.
can i use other country firmware for flashing then later flash to RR back?
yohhendry said:
hello, im currently trying to download the stock rom however i couldnt seems to be able to find any working download link for indonesia version of firmware.
can i use other country firmware for flashing then later flash to RR back?
Click to expand...
Click to collapse
Did you try to flash a recovery only ?
Maybe your firmware/system is not corrupted and then you could just reflash a clean rom ?
In Odin, Select AP and load your recovery.tar
I am having the very same issue. The difference is that it's happening with Spotify, Xposed and Relay for Reddit. So yeah it's been much worse for me. I will try to flash stock rom + reinstall another recovery and see if it fixes. By the way, I got a couple of questions:
1 - Does the country that I select when downloading the stock ROM matters?
2 - Which Recovery can you guys recommend? There's a bunch here but not sure if all them are worthy
Okay so I flashed an Indian stock ROM (I'm not indian nor live in the country), then I wiped all data, so I could boot. This is the default procedure to revert back to a Stock ROM.
After that, I noticed the Wifi wasn't working, probably due to the Stock rom I've downloaded. Anyway, I installed a custom Recovery (even an updated version of what I used before, then I reinstalled Ressurection Remix, and tried again.
....It didn't work. Relay for Reddit crashes everything, Spotify puts my phone into a bootloot. Same with Xposed. I have no idea what to do anymore. Someone, please help. I really can't afford to buy another phone right now and I really need those apps. Expecially Spotify.
Wagnelles said:
Okay so I flashed an Indian stock ROM (I'm not indian nor live in the country), then I wiped all data, so I could boot. This is the default procedure to revert back to a Stock ROM.
After that, I noticed the Wifi wasn't working, probably due to the Stock rom I've downloaded. Anyway, I installed a custom Recovery (even an updated version of what I used before, then I reinstalled Ressurection Remix, and tried again.
....It didn't work. Relay for Reddit crashes everything, Spotify puts my phone into a bootloot. Same with Xposed. I have no idea what to do anymore. Someone, please help. I really can't afford to buy another phone right now and I really need those apps. Expecially Spotify.
Click to expand...
Click to collapse
Ok try to flash 4 files firmware repair but do it at your own risk.
you must know you how to do it with no mistake
Just do a search on Google about (4 file firmware repair for grand 2) the way is easy but have to do not a mistake.
Then good luck
mahmmoud1231 said:
Ok try to flash 4 files firmware repair but do it at your own risk.
you must know you how to do it with no mistake
Just do a search on Google about (4 file firmware repair for grand 2) the way is easy but have to do not a mistake.
Then good luck
Click to expand...
Click to collapse
Okay, so I guess there won't be any need for that. I've redownloaded the stock ROM, but this time, I checked my phone Serial Number so I could download the right stock ROM for my phone. Now everything seems to be working again. Spotify and Relay installed without any issue. I will now try to reflash recovery and then another ROM and see if the problem persists.
For those who don't know how to check your Serial number, it's right above your android version, at the "About phone" section on Settings.
I still need advice on which Recovery I should use.
Anyway, thank you guys. I probably would't be able to solve this without your help.
UPDATE: I've installed TWRP 3.1.0.0, and also rooted the phone using it. Still on stock ROM. Everything seems to be still working without problems. I think I'll stick with it for now. Maybe later I'll try to lash a Custom ROM and see if it still works.
Wagnelles said:
Okay, so I guess there won't be any need for that. I've redownloaded the stock ROM, but this time, I checked my phone Serial Number so I could download the right stock ROM for my phone. Now everything seems to be working again. Spotify and Relay installed without any issue. I will now try to reflash recovery and then another ROM and see if the problem persists.
For those who don't know how to check your Serial number, it's right above your android version, at the "About phone" section on Settings.
I still need advice on which Recovery I should use.
Anyway, thank you guys. I probably would't be able to solve this without your help.
UPDATE: I've installed TWRP 3.1.0.0, and also rooted the phone using it. Still on stock ROM. Everything seems to be still working without problems. I think I'll stick with it for now. Maybe later I'll try to lash a Custom ROM and see if it still works.
Click to expand...
Click to collapse
Hi,
I'm glad you fixed you're problem. Sticking on Stock ROM is the best thing you can do if you need your phone as every functionnality is checked and working.
I personnaly use TWRP as recovery, its good you got usb, root and everything you need to backup/restore your phone + reset your phone.