Phone app unfortunately Crashed. - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Hi All,
I use SM-A510FD Galaxy A5 2016 as my daily Driver.
I rooted my phone and installed Xposed in it. Then i uninstalled some Stock Apps like Opera Max and all. After few days of usage(2 days to be particular), I am seeing that some of my apps crash suddenly and that the following error popps up: Unfortunately Phone has Stopped, Unfortunately ES File Explorer Has Stopped.
After I click OK it pops up again.
So in a wonderfully foolish step I uninstalled the Phone App and now the phone will not reboot.
I uninstalled Xposed but nothing helped. Finally after lots of research on XDA and otherwise I flashed The Stock Firmware for my Phone SM-A510FD.
It rebooted just as fine but now the same problem is there and is not resolved. Moreover if i Open some app like Play Books while i am getting the error, the popup of the error stops until i open the Phone app again. I opened my phone in Safe MOde and saw that the same problem is also there which means it is not caused by some third party apps. PLease help

deepray said:
Hi All,
I use SM-A510FD Galaxy A5 2016 as my daily Driver.
I rooted my phone and installed Xposed in it. Then i uninstalled some Stock Apps like Opera Max and all. After few days of usage(2 days to be particular), I am seeing that some of my apps crash suddenly and that the following error popps up: Unfortunately Phone has Stopped, Unfortunately ES File Explorer Has Stopped.
After I click OK it pops up again.
So in a wonderfully foolish step I uninstalled the Phone App and now the phone will not reboot.
I uninstalled Xposed but nothing helped. Finally after lots of research on XDA and otherwise I flashed The Stock Firmware for my Phone SM-A510FD.
It rebooted just as fine but now the same problem is there and is not resolved. Moreover if i Open some app like Play Books while i am getting the error, the popup of the error stops until i open the Phone app again. I opened my phone in Safe MOde and saw that the same problem is also there which means it is not caused by some third party apps. PLease help
Click to expand...
Click to collapse
from my point of view you only need to wipe to factory settings, flashing stock firmware doesn't wipe user data.. just try these scenarios based on your recovery type
If you're on TWRP
1. boot to recovery and just go to WIPE > Advanced Wipe, select all EXCEPT internal & external storage then wipe it
2. reboot to download mode
3. flash stock firmware
if you're on stock recovery
1. boot to recovery
2. wipe to factory format
3. reboot to system, if it does not boot go back to download mode & reflash stock firmware

Twiq said:
from my point of view you only need to wipe to factory settings, flashing stock firmware doesn't wipe user data.. just try these scenarios based on your recovery type
If you're on TWRP
1. boot to recovery and just go to WIPE > Advanced Wipe, select all EXCEPT internal & external storage then wipe it
2. reboot to download mode
3. flash stock firmware
if you're on stock recovery
1. boot to recovery
2. wipe to factory format
3. reboot to system, if it does not boot go back to download mode & reflash stock firmware
Click to expand...
Click to collapse
Thanks for the help sir. But as mentioned i have already wiped the cache and dalvik plus i had also flashed the stock ROM. But the problem did not go away as it is not related to it.
Actually while giving some app access to storage or camera, i had to switch off screen overlays for all apps including the phone app. But the Phone app needs to have this as it requires this to ask for SIM 1/2. So after i gave the Phone app the screen overlay it is workinh just as fine.
Anyway thanks a lot.

Related

[Q] Stuck at boot screen after TWRP asking if I want to install SuperSU

I have to think I'm not the first to be in this situation but my searches didn't turn up anything that looked familiar.
I rooted the stock phone and installed TWRP 2.6xx a month or two ago with no issues. Everything's been running great and I decided it was time to make another backup using TWRP.
After a successful backup I wiped dalvik and cache out of habit and went to reboot -- TWRP said I was not rooted and wanted to know if I wanted to install SuperSU? This question was unexpected since I'd been rooted for a long time, and I decided to just say yes. The phone rebooted and stopped at the Samsung Galaxy S4 boot screen. I did up-volume reboot to recovery, but it seemed to hang at the TWRP blue screen -- I later discovered it will eventually get to the menu after a minute or two of the blue screen. I tried wiping cache and dalvik again and rebooting -- every time I try to reboot now it asks if I want to install SuperSU -- whether I say yes or no seems to make no difference -- I've tried both several times. Every time it hangs at the Samsung boot screen, or it takes forever to get to TWRP if I'm booting to recovery.
I've tried wiping cache, dalvik and data with no improvement. I finally tried formatting data, but again no improvement. I also tried restoring my backup several times and wiping cache and dalvik but still stuck.
I prior to today's problems I'd used TWRP a number of times and I don't recall it asking the SuperSU question, so I am thinking that is the key to this problem, and I'm wondering if anyone knows what it means?
You need to go to 2502 twrp, 26+ has hanging problems and possible Partition issues, also what rom are you on? Do you need to flash super su along with the rom /gapps?
Here's the twrp forum for us SPH-L720
The last page has a download link for the most stable build for us good luck!
http://forum.xda-developers.com/showthread.php?t=2262999
I'm running what came on the phone, just unlocked, rooted, and installed TWRP.
I ran CM10.1 on my previous phone and currently on my tablet, but my impression from running it previously is CM is a downgrade in voicemail functionality (you get these annoying text messages and have to call the voicemail), and I'm assuming it doesn't support the special GS4 hardware features like being able to hover your finger.
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Nerva said:
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Click to expand...
Click to collapse
How did you root? CF auto root also installs SuperSU
Do you have a back up from when you were rooted? IF twrp keeps giving you problems, use cwm, are you able to get past the Samsung boot..
Yeah that's what I did back when I rooted it months ago. I tried running CF auto root again today and it didn't work, so I ran it from Odin and it did work that time, but there was no change -- still hangs on the Samsung boot screen, although now I'm back to the stock recovery. So I tried installing the stock MF9 firmware from Odin -- still hangs on the boot screen. I don't know what to do at this point...
After mf9 install avd stock recovery did you factory reset
Yes, I did a factory reset -- followed the video instructions by qbking77. Still hangs on the boot screen.
Take out battery.. Put back in. Go to stock recovery, holding all 3 buttons volume up factory reset.. If you used odin abd flashed mf9 it should fix you?
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Well I guess I tried man, someone who has more knowledge should chime in now
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
This
http://forum.xda-developers.com/showthread.php?t=2400192
Im also stucked with the same problem!! After flashing my rom succesfully it just ask ur device is not rooted swipe to install!! I tried all the posiblities!! but i stuck with the boot image!! pls help me!!
From experience it sounds like you should head over to sammobile and Odin back to stock and start fresh.
1. Odin to stock
2. Root phone
3. Put desired recovery
4. Flash ROM (be sure to read dev install instructions some require reboot of recovery after wipe)
5.try to restore backup (best if you flash ROM that is backup then restore backup)
6.if you went into nae or ng2 you cannot downgrade to me
7.google has many solutions
Sent from my SCH-I545 using XDA Free mobile app
Sorry for necro, but did anyone figure out a solution to this? This just happened to me.
Just Reflash it
We have the same issue, tried to install supersu binary, after installing through twrp recover, my phone went bootloop, as i've tried to search the internet, the issue doesn't fix by by most of the users unless they reflash their device. though its a bit hassle starting from zero, but atleast, you got ur device back
This helps me:
1. Run Odin on your computer and, after entering download mode on your phone, establish a connection between your devices with the help of the USB cable.
2.Note: for download mode – power off your smartphone and then press and hold, at the same time, the Power, Volume Down and Home buttons.
3.Odin will try to recognize your device; if everything works as expected, on the program the “added” message will be displayed and the ID:COM field will be turned yellow, or blue. (Note: if that’s not happening, unplug the USB connection, close Odin, force restart your phone and reinstall the USB drivers on your computer before retrying the steps from above)
4.From the program click on the “PA” button and load the custom recovery image; don’t check Re Partition and Auto Reboot options.
5.When done, click on “start” and wait while TWRP recovery is being added on your phone
6.In the end, Odin will display the “pass” message and the ID:COM filed will be turned green (or other color) with message - RESTART; you can then remove the USB cord and reboot your smartphone.
I have had this prob on a few things , if you have a backup,flash any mod that will go to the device will do then run the backup and reflash should work .and if you have twrp try to reformat all but the system and see if that helps.
Good luck.
Hi to everyone.
Today, I installed the TWRP and the ROM and both were installed correctly on a Le Pro3 X722. The problem started when the Google services were updating. Suddenly, the phone restarted and entered in a bootloop. I was not even able to enter the TWRP. The page freeze on LE-Recovery logo and then crashed (fill full of lines). I disconnected the battery for a while and then, I was able to enter the TWRP for 2 time but recovery crashes in few seconds. I wanted to wipe and install a clean rom but I cannot enter TWRP anymore.
Please, Is there someone that could help me?
Thank you very much in advance
PS. My phone is not recognized via ADB. I tried with the AIO Tool but my device is not detected.
Hi, I followed the whole process for Qfil explained here:
Leeco Le Pro3 x720 Hard Brick
So the phone was running lineageos 15.1 nightly from 22.08 which i guess was kind of really unstable (even opening twitter in the morning could turn off the device. It could be turned back on right away though), xposed framework v90 w/yt...
forum.xda-developers.com
Installation was correct but nothing change in my phone:
- same start page and bootloop
- Same problem trying to access the recovery.
Now, i can connect via fastboot and I would like to install a fastboot rom (preferable EUI stock 20) but I cannot find one. All links are dead.
Thank you very much in advance

TouchWiz Home has stopped - can't use phone

My i9505 originally had I9505XXUFNB8 BTU firmware on it and was rooted using Chainfire's Auto Root.
The phone kept asking me to update the firmware so I decided to flash the stock firmware back on it using ODIN so that I could do so (I have read that you should never update via OTA if rooted).
When I flashed it using ODIN, upon boot up, the phone said that "Unfortunately, Touchwiz Home has stopped." I press OK but then I get another error message this time for Google Play Music (infinite loop).
I keep toggling between these two error messages, however they don't go away.
If I press the lock screen button, I can see the welcome message, the status bar etc. But soon as I swipe, the above error messages appear.
If I receive a phone call, the phone rings and goes to the answer / reject screen but I can't accept the call as the error message is in the way.
I have already tried factory reset via the recovery options boot menu, but to no avail.
I have flashed a new version of the ROM, I9505XXUFNB9 but still the same error. I then even tried rooting it again, but still the same issue.
Please help me.
Flash stock rom via odin go to recovery wipe data, cache can solve your problem. Or try before put your phone airplane mode it may help your stopped after that delete play music and clear systemui data.
No Luck
VoLTaqe said:
Flash stock rom via odin go to recovery wipe data, cache can solve your problem. Or try before put your phone airplane mode it may help your stopped after that delete play music and clear systemui data.
Click to expand...
Click to collapse
I have already tried the above, but I tried it again as per your instructions.
I flashed the stock rom via Odin (normal options selected just reset time and auto reboot). The device restarts and upgrades the system as per normal.
Before I even get to set the language a dialogue box appears saying that Google+ has stopped.
The Google+ dialogue box is now in an infinite loop.
Also, every time when I now turn it off and back on again, it goes through the upgrade screen but only for a few seconds.
I think my phone needs some sort of master reset.
You are saying wrong steps.
1- Flash stock firmware
2- Wait until phone boot
3- After boot volume up + home + power button and go in stock recovery mode ( not cwm or twrp )
4- Wipe data / cache
5- Done.
Will Try Now
VoLTaqe said:
You are saying wrong steps.
1- Flash stock firmware
2- Wait until phone boot
3- After boot volume up + home + power button and go in stock recovery mode ( not cwm or twrp )
4- Wipe data / cache
5- Done.
Click to expand...
Click to collapse
I will do this now.
I have got stock recovery mode.
So I have to clear the data / cache before it boots up with the stock firmware?
Still not working
jdhot1 said:
I will do this now.
I have got stock recovery mode.
So I have to clear the data / cache before it boots up with the stock firmware?
Click to expand...
Click to collapse
Ok, so firmware was successfully uploading using ODIN.
Phone rebooted, I did the data and cache wipe (factory reset does them both at the same time).
I have now entered the setup screen, I waited for around 15 seconds, then the message appeared again "unfortunately, Google+ has stopped."
I press OK on this dialogue box, then I get another error "unfortunately, Google Play Music has stopped."
Then after pressing OK on this one, I get the Google+ one in a loop.
Should I try Philz Touch Recovery?
jdhot1 said:
Ok, so firmware was successfully uploading using ODIN.
Phone rebooted, I did the data and cache wipe (factory reset does them both at the same time).
I have now entered the setup screen, I waited for around 15 seconds, then the message appeared again "unfortunately, Google+ has stopped."
I press OK on this dialogue box, then I get another error "unfortunately, Google Play Music has stopped."
Then after pressing OK on this one, I get the Google+ one in a loop.
Click to expand...
Click to collapse
I found this thread http://forum.xda-developers.com/showthread.php?t=2480473 but I am unsure if I should try it.
jdhot1 said:
I found this thread http://forum.xda-developers.com/showthread.php?t=2480473 but I am unsure if I should try it.
Click to expand...
Click to collapse
Wipe data factory and try again. If not success flash twrp and wipe cache, data, preload, system, internal sdcard after that flash any custom rom
Need Root for Custom Recovery
VoLTaqe said:
Wipe data factory and try again. If not success flash twrp and wipe cache, data, preload, system, internal sdcard after that flash any custom rom
Click to expand...
Click to collapse
Thanks for your attempts to help me however after reading around, it appears that the phone needs to be rooted first before any custom recovery can be put on.
I have now created a new thread in the Questions section.

Strange Wifi Problem

Background: So i bought this used S5 900f from someone and it gave me "recovery is not seandroid enforcing" error while rooting and installing recovery. i found a workaround for this error by immediately pulling the battery trick after root. I have installed TWRP and root and they work but this "Recovery is not seandroid enforcing error" still displays when i try to enter recovery for about 2-3 seconds and then the recovery boots.
Now the Problem is : My s5 900f is not saving Wifi password on any of the lollipop builds i have tried Many UK 5.0 (BTU) Builds from Sammobile , and Nordic Countries 5.0 as soon as i restart or shutdown m phone Wifi password is reset and i have to enter it again after turning my phone on again. Surprisingly When i downgrade to any of the kitkat Builds Wifi starts saving passwords just fine?
Things i have tried
Format, Clear dalvik cache, cache, data, system, internal Storage and install different 5.0 builds.
Enabling disabling Google backup, it doesn't help.
Kindly Help me out does Wifi not saving password has anything to do with this "Seandroid not enforcing Error" . And how to fix this issue i am at verge of smashing this phone. .....:angel:
http://forum.xda-developers.com/galaxy-s5/general/s5-forget-wifi-passwords-reboot-fix-t3105976
Thanks alot buddy, you just saved my phone....Phewwww do you know why it happened in the first place?
Buggy ROM is all I can think, it happened to me with a clean install of the latest LP ROM so I went looking for a fix for myself
I tweeted to Samsung UK about it, and they just talked to me like I was stupid, I guess they don't want to admit to it being their fault
UPDATE NOW after the build prop fix, i rebooted fine once... After installing TWRP the phone is crashing on boot up....touchwiz crashes along with all other programs it wont let me boot up. Maybe TWRP messed something up.
Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it
*Detection* said:
Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it
Click to expand...
Click to collapse
does your phone display "recovery is not seandroid enforcing" just before entering twrp? i tried clearing cache and battery pulling didnt work....now flashing earlier 5.O btu.
Yea, just means it's a custom recovery
*Detection* said:
Yea, just means it's a custom recovery
Click to expand...
Click to collapse
Some folks are able to flash any 5.0 build and they don't get the Build.Prop issue. i just reflashed and the issue came back...will re edit the build.prop till now i have rooted + installed TWRP no issues so far only build.prop left to be edited..... could you please tell me why is it persistent on some phones that even reflashing, formating doesn't help.
Unfortunately Nothing works....I have been more than patient with this device...been flashing and trying different things for 18 hours now. It works fine but after going to recovery (Just by entering it) and then rebooting will freeze my phone with "Unfortunately Media storage has stopped working...and everything else like touchwiz also crashes".......i was so...so wrong to move to a samsung This Definitely is my last samsung phone...for now i will keep trying different things.
Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are
*Detection* said:
Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are
Click to expand...
Click to collapse
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks
dork997 said:
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks
Click to expand...
Click to collapse
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted
*Detection* said:
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted
Click to expand...
Click to collapse
Thanks for your Help, i guess this problem is too complicated. Anyway this time i installed Philz recovery > formatted everything > remove user content and data > custom formatted everything > flashed 5.0 BTU. and surprisingly its saving WiFi passwords without any build prop changes. So i am going to leave it here . 5.0 Unrooted with stock recovery everything working (FOR NOW) . This time i used Odin 3.10 instead of 3.07. I hope it does not get stuck at boot logo and start crashing. Only one problem it kept connecting to "update server" evem tho i had disabled the auto update option from settings>about >updates . i restarted immediately hopefully it wont try to update again. Thanks again for your help.

Screen stuck on preparing to start.. starting app.. after flashing crdroid 6.0.1

I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
khushboop said:
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
Click to expand...
Click to collapse
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
sk.shehbaz said:
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
Click to expand...
Click to collapse
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
khushboop said:
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
Click to expand...
Click to collapse
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
khushboop said:
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
Click to expand...
Click to collapse
I still have no idea why it got bricked. So after searching on google and youtube I came across this: https://androidmtk.com/download-yu-stock-rom-for-all-models . I followed the steps and now KitKat is running except launcher is not working, instead play store open's every time I try to go to home screen. So tried the nova launcher but that still doesn't work with home button, have to open through playstore->my apps, every time. But rest is working.
sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
dude!! i tried the above method and thankfully my phone is working now the only major problem now is whatsapp is not opening...when clicked opens for 0.01 sec and returns back to previous screen (flashes) ....please somebody help me with this. Anybody can help me, Thanks in Advance.

Custoom ROM installation failed (stuck on pre-boot screen)

So I've installed TWRP onto my S8 and have wiped it completely, though I did have to change and then change back the file formats so that TWRP would register them correctly
I downloaded renovate ice 1.1, copied it onto my sd card and then flashed it everything installed well
When I then reboot it doesnt get past the first screen as in showing (not sure if it freezes at this point but have left it for 2 hours so Im guessing so)
Samsung Galaxy S8 POWERED BY android
Then the only thing I can do is get the phone back into recovery mode (then when I go to reboot it says there is no OS)
Before I installed the custom ROM I had an error message stating that the integrity verification had failed, I pressed on believing that this would be fixed once I had installed renovate
I know that my phone is a exynos variant, is there any way to check exactly what variant withing TWRP
The download mode is still working
Extra Information
and also when I go into TWRP it asks me about if it should be only system read each time it starts up
it also prompts for me to install the app when I try to reboot through TWRP though I believe that is normal
thegasovi said:
So I've installed TWRP onto my S8 and have wiped it completely, though I did have to change and then change back the file formats so that TWRP would register them correctly
I downloaded renovate ice 1.1, copied it onto my sd card and then flashed it everything installed well
When I then reboot it doesnt get past the first screen as in showing (not sure if it freezes at this point but have left it for 2 hours so Im guessing so)
Samsung Galaxy S8 POWERED BY android
Then the only thing I can do is get the phone back into recovery mode (then when I go to reboot it says there is no OS)
Before I installed the custom ROM I had an error message stating that the integrity verification had failed, I pressed on believing that this would be fixed once I had installed renovate
I know that my phone is a exynos variant, is there any way to check exactly what variant withing TWRP
The download mode is still working
Click to expand...
Click to collapse
should I try to reinstall TWRP and see what happens
thegasovi said:
should I try to reinstall TWRP and see what happens
Click to expand...
Click to collapse
I've tried to install the Batman ROM but to the same avail,
still prompting me to install the TWRP official app (but not always)
am going to try reinstalling twrp using odin
could it have anything to do with knox values changing (need to research)
installed batman rom after using Odin to BL some new firmware(think that's what its called) onto the device
now am stuck on the next boot loading screen
will wait for some time to see if its my phone
-so 1 problem was due to the previous stuff on the device hopefully this means that the integrity verification thing is fixed (not sure how to check
-still havent re-'downloaded' a new twrp via odin, may try next
-could also try reinstalling batman as it was installed before the firmware, may be worth it
-could try to use default rom (need to find download page)
not sure about next step
reinstalled renovate and booted up and got back to the verification failed screen, may have something to do with me selecting knox when I installed it
-niw will try to solve integrity verification problem as when I try to reset it wont work w/ twrp
Maybe too many little things that are causing issues, maybe rather just use Samsung Switch and do a recovery and it will reinstall as per stock, then try the rooting, custom ROM thing from scratch. I know I battled with mine, got TWRP installed but coult get passed samsung boot screen. So i did used Samsung Switch recovery function and got phone back to stock, now I just use package disablers to kill stuff and all is well.
at first, why did you choose renovate 1.1 when 2.2 is availiable?
i would start from scratch again...
flash stock rom via odin. boot and test device. there should be no problem, after this, flash twrp again and put latest renovate rom on memory or external usb device.
with aroma installation you can choose to full wipe your phone. this should make no problems.
Tim Niklas said:
at first, why did you choose renovate 1.1 when 2.2 is availiable?
i would start from scratch again...
flash stock rom via odin. boot and test device. there should be no problem, after this, flash twrp again and put latest renovate rom on memory or external usb device.
with aroma installation you can choose to full wipe your phone. this should make no problems.
Click to expand...
Click to collapse
looking back on it I guess I just didnt realise that that version was available
could you give me a link to where I can download the stock rom from, that would be great
Jostian said:
Maybe too many little things that are causing issues, maybe rather just use Samsung Switch and do a recovery and it will reinstall as per stock, then try the rooting, custom ROM thing from scratch. I know I battled with mine, got TWRP installed but coult get passed samsung boot screen. So i did used Samsung Switch recovery function and got phone back to stock, now I just use package disablers to kill stuff and all is well.
Click to expand...
Click to collapse
I tried to open samsung switch earlier but it believed that my phone was no longer supported and I guessed that this was due to the rooting, what mode where you in to be able to connect to samsung switch
not sure now but atm I cant get into TWRP anymore
Put phone into download mode, then use recovery option on switch.
thegasovi said:
looking back on it I guess I just didnt realise that that version was available
could you give me a link to where I can download the stock rom from, that would be great
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/how-to/official-stock-firmware-update-odin-t3598172
take a look here,
there is described, how you can download stock rom with the tool samfirm.
keep this rom safe you may need it once or twice again.
---------- Post added at 11:05 AM ---------- Previous post was at 11:04 AM ----------
thegasovi said:
not sure now but atm I cant get into TWRP anymore
Click to expand...
Click to collapse
and again...
as long as you are abel to go into download mode, everything is fine.
flash stock again -> twrp -> custom rom with full wipe in aroma installer
reverted back to stock os using odin
checked that all is well and there was no lasting damage (knox was still working fine)
reinstalled twrp, same problem happened again with twrp not recognising the internal storage so had to reset the file format
flashed the batman rom, now am back at the second boot screen and cannot get past
thegasovi said:
reverted back to stock os using odin
checked that all is well and there was no lasting damage (knox was still working fine)
reinstalled twrp, same problem happened again with twrp not recognising the internal storage so had to reset the file format
flashed the batman rom, now am back at the second boot screen and cannot get past
Click to expand...
Click to collapse
with internal storage you mean data partition?
sorry, i forgot. thats a common known issue with twrp , wipe data partition in twrp menu, after that you are able to install custom roms

Categories

Resources