I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
NickDeveloper said:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
Click to expand...
Click to collapse
So, we don't know when will be fixed
NickDeveloper said:
I see that TWRP users have experienced a touchscreen issue, so they need to use an OTG cable with wireless mouse. Does anyone know when will the touch issue be fixed?
Click to expand...
Click to collapse
But you can use the OTG touch twrp
Arobase40 said:
I experimented this no touch TWRP but it is mostly buggy excluding the non touch issue there is a bigger issue which is that once installed you can't get out from it as it bootloops into this recovery mode. Flashing a stock recovery won't change anything.
You will have to totally restock your phone from scratch and then re root it and restore all your apps and data !!! ^^
I found out the twrp tree for A52 4G and was able to build a TWRP but obviously I can't test it.
I'm not able to build a twrp for A52S 5G for now as there are missing many kernel modules and other stuffs so I have to build them from kernel source code. So for now I'm working on the device and vendor config files...
Click to expand...
Click to collapse
But how can I fix my phone if I get a bootloop?
Arobase40 said:
You can't that is why I don't recommend you to use this no touch TWRP !
I was told to use a multidisabler but doesn't seem to work...
Click to expand...
Click to collapse
But it is only a soft brick, there is no need to change the motherboard. Would there be a way to reinstall stock firmware with Odin?
Arobase40 said:
I didn't say it will break your motherboard but if you want to waste your time in restocking your phone it's up to you.
Click to expand...
Click to collapse
Can I reinstall stock firmware with Odin? Will it work?
NickDeveloper said:
Can I reinstall stock firmware with Odin? Will it work?
Click to expand...
Click to collapse
Yes.
Arobase40 said:
As I said if you want to waste your time, YES you can reinstall stock firmware but of course you will lose your no touch twrp...
You will have to choose one or the other but not both...
Click to expand...
Click to collapse
Unfortunately, I have tried to reinstall stock firmware, but it failed. Looks like my bootloader became locked. Odin software showed "FAIL". There was a message that I could barely read, so that was the reason it failed to reinstall the firmware.
What should I do now?
Arobase40 said:
You can't that is why I don't recommend you to use this no touch TWRP !
I was told to use a multidisabler but doesn't seem to work...
Click to expand...
Click to collapse
So you got stuck in a bootloop after installing twrp. Have you tried just extracting the stock boot.img from firmware AP file and flashing it with odin? I really don't get it why you had to reinstall everything to stock. It's not necessary to reflash every partition if you only messed up one
Arm1nas said:
So you got stuck in a bootloop after installing twrp. Have you tried just extracting the stock boot.img from firmware AP file and flashing it with odin? I really don't get it why you had to reinstall everything to stock. It's not necessary to reflash every partition if you only messed up one
Click to expand...
Click to collapse
Nope, I did not make the backup of anything. Unfortunately, my bootloader is now locked and I cannot reinstall stock firmware. What now??
NickDeveloper said:
Nope, I did not make the backup of anything. Unfortunately, my bootloader is now locked and I cannot reinstall stock firmware. What now??
Click to expand...
Click to collapse
While the phone is completely off, press vol up and vol down buttons at the same time and then plug in the usb cable to the computer. I had that happen too, when the device fails to boot it automatically puts you into download mode and it says that the OEM LOCK is on. You just have to reboot to download mode manually.
Arm1nas said:
While the phone is completely off, press vol up and vol down buttons at the same time and then plug in the usb cable to the computer. I had that happen too, when the device fails to boot it automatically puts you into download mode and it says that the OEM LOCK is on. You just have to reboot to download mode manually.
Click to expand...
Click to collapse
But how can I reinstall stock firmware when the OEM is locked? I tried to reinstall with all required binaries, including HOME_CSC and it showed "FAIL".
NickDeveloper said:
But how can I reinstall stock firmware when the OEM is locked? I tried to reinstall with all required binaries, including HOME_CSC and it showed "FAIL".
Click to expand...
Click to collapse
You don't need to unlock bootloader to flash stock fw with Odin.
Your problem is most likely related to something else.
Where did you download your fw?
Have you tried different cables?
What Odin version are you trying?
ShaDisNX255 said:
You don't need to unlock bootloader to flash stock fw with Odin.
Your problem is most likely related to something else.
Where did you download your fw?
Have you tried different cables?
What Odin version are you trying?
Click to expand...
Click to collapse
I don't understand why would it be possible to flash stock firmware with locked bootloader, I thought that locked bootloader won't allow the OS to be reinstalled.
NickDeveloper said:
I don't understand why would it be possible to flash stock firmware with locked bootloader, I thought that locked bootloader won't allow the OS to be reinstalled.
Click to expand...
Click to collapse
A Locked bootloader will prevent you from installing any custom things, like recovery or custom roms. It will allow you to install stock firmware via odin. Use Odin 3.14 to install firmware downloaded from here. Use the AP, Bl, Cp, and CSC_OXM files. That will get you started from scratch, all previous data and stuff will be deleted.
Related
Hello, my dumb ass decided to root using CFRoot, then it said it failed so I tried to flash the CFAutoRoot in Odin. Well, I tried booting my phone, after saying f*** it, and now I'm greeted with 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.' what can I do? I just bought this phone, so if I screwed it up, I'm in trouble.
What phone and what rom is it running?
audit13 said:
What phone and what rom is it running?
Click to expand...
Click to collapse
SGH-I747(AT&T Samsung Galaxy 3), and the stock 4.3 rom
Unfortunately, there is no way to flash a stock AT&T 4.3 ROM to this phone as AT&T never released a full ROM, only an update.
Did you try reconnecting it to Kies to try and re-flash?
audit13 said:
What phone and what rom is it running?
Click to expand...
Click to collapse
audit13 said:
Unfortunately, there is no way to flash a stock AT&T 4.3 ROM to this phone as AT&T never released a full ROM, only an update.
Did you try reconnecting it to Kies to try and re-flash?
Click to expand...
Click to collapse
I'm on 4.3 update I meant, and how can I reflash? I'm in Kies now.
Wesley. said:
I'm on 4.3 update I meant, and how can I reflash? I'm in Kies now.
Click to expand...
Click to collapse
Does Kies detect your phone at all? Is there a recover option? Sorry, I haven't used Kies for a long time so I don't remember what options are available.
Maybe this will help: http://www.samsung.com/us/support/faq/FAQ00052703/61329
audit13 said:
Does Kies detect your phone at all? Is there a recover option? Sorry, I haven't used Kies for a long time so I don't remember what options are available.
Click to expand...
Click to collapse
I went to tools -> Firmware upgrade and initialization, entered my model # & S/N, and it's 'Downloading file for firmware emergency recovery of 'GALAXY S III '(SGH-I747)' from the server...' so it says, which I got to from Kies. Should I let it run its course?
Wesley. said:
I went to tools -> Firmware upgrade and initialization, entered my model # & S/N, and it's 'Downloading file for firmware emergency recovery of 'GALAXY S III '(SGH-I747)' from the server...' so it says, which I got to from Kies. Should I let it run its course?
Click to expand...
Click to collapse
I'm not sure as I have never used this Kies option. I have always re-flashed via Odin. Your case is different because there is no full 4.3 AT&T Rom that can be flashed via Odin.
Is there any warranty on your phone?
audit13 said:
I'm not sure as I have never used this Kies option. I have always re-flashed via Odin. Your case is different because there is no full 4.3 AT&T Rom that can be flashed via Odin.
Is there any warranty on your phone?
Click to expand...
Click to collapse
It says Warranty Bit: 1 on Download mode
Wesley. said:
It says Warranty Bit: 1
Click to expand...
Click to collapse
Looks like you tripped the Knox counter when you tried to root the phone. Did you get it from AT&T? Maybe you could take it back and get it exchanged for another one since it got pooched while running Kies?
audit13 said:
Looks like you tripped the Knox counter when you tried to root the phone. Did you get it from AT&T? Maybe you could take it back and get it exchanged for another one since it got pooched while running Kies?
Click to expand...
Click to collapse
I got it from Walmart because AT&T was going to take two hours, lol. And, how would I go about doing that? I'm not a good liar, and I don't know how I pooched it lol
Wesley. said:
I got it from Walmart because AT&T was going to take two hours, lol. And, how would I go about doing that? I'm not a good liar, and I don't know how I pooched it lol
Click to expand...
Click to collapse
Well, if you take it to an AT&T or Walmart store, they may not care that you tripped the counter. If they send it in to Samsung for repair, they may not care either. However, there's always the chance that AT&T/Walmart/Samsung would allow repairing the phone at no charge.
audit13 said:
Well, if you take it to an AT&T or Walmart store, they may not care that you tripped the counter. If they send it in to Samsung for repair, they may not care either. However, there's always the chance that AT&T/Walmart/Samsung would allow repairing the phone at no charge.
Click to expand...
Click to collapse
Is there any way I could try flashing a rom?
Wesley. said:
Is there any way I could try flashing a rom?
Click to expand...
Click to collapse
You would need to install a custom recovery in order to flash a custom ROM. A custom recovery can be installed via Odin if you find the right file.
Do not flash any stock Samsung 4.3 ROM or a custom rom unless Knox has been removed.
audit13 said:
You would need to install a custom recovery in order to flash a custom ROM. A custom recovery can be installed via Odin if you find the right file.
Do not flash any stock Samsung 4.3 ROM or a custom rom unless Knox has been removed.
Click to expand...
Click to collapse
I have CWM Recovery, what can I do now? I am rooted, however Knox isn't disabled. Any way I can disable it? I'm unable to boot my phone up, when I try it says 'Firmware upgrade encountered an issue. Please select blah blah..', and I'm in the Download mode now.
Wesley. said:
I have CWM Recovery, what can I do now? I am rooted, however Knox isn't disabled. Any way I can disable it? I'm unable to boot my phone up, when I try it says 'Firmware upgrade encountered an issue. Please select blah blah..', and I'm in the Download mode now.
Click to expand...
Click to collapse
Are you running the latest version of CWM? If you can't boot into your OS, how do you know you are rooted?
Flashing another ROM will remove knox.
Copy a custom rom to a microSD card (do not unzip the ROM which is a single zip file), boot into recovery mode, wipe cache, wipe data, wipe Dalvik, and install the ROM from SDcard1.
I have the latest experimental Cyanfox on my i747m from here: http://cyanfox-rom.com/downloads/?folder=d2att/
audit13 said:
Are you running the latest version of CWM? If you can't boot into your OS, how do you know you are rooted?
Flashing another ROM will remove knox.
Copy a custom rom to a microSD card (do not unzip the ROM which is a single zip file), boot into recovery mode, wipe cache, wipe data, wipe Dalvik, and install the ROM from SDcard1.
I have the latest experimental Cyanfox on my i747m from here: http://cyanfox-rom.com/downloads/?folder=d2att/
Click to expand...
Click to collapse
I was able to before, however in Odin I was trying to flash something(a root file), and it said failed, so i rebooted and now i'm stuck. D:
Wesley. said:
I was able to before, however in Odin I was trying to flash something(a root file), and it said failed, so i rebooted and now i'm stuck. D:
Click to expand...
Click to collapse
When did you flash CWM? Is it 6.0.4.5? How did you flash it? Via Odin?
I can't boot into recovery, I get the firmware upgrade thing again. i have no idea what version it is, and yes via odin
Wesley. said:
I can't boot into recovery, I get the firmware upgrade thing again. i have no idea what version it is, and yes via odin
Click to expand...
Click to collapse
For recovery, are you holding the home button, volume up, and then pressing and holding power? You need to hold all 3 until you see some blue text appear on the screen, then let go of the power button.
Hello, is there any way to get full Odin flashable custom ROM for sm-p605. I need bootloader, boot.img, cache.img etc. My device cannot boot, it stucks on samsung-galaxy-note-10.1-2014 edition logo, except in one of the ROM's it boots only once and gets error like - com.system... stopped working.... Thankyou.
Tautvaldas said:
Hello, is there any way to get full Odin flashable custom ROM for sm-p605. I need bootloader, boot.img, cache.img etc. My device cannot boot, it stucks on samsung-galaxy-note-10.1-2014 edition logo, except in one of the ROM's it boots only once and gets error like - com.system... stopped working.... Thankyou.
Click to expand...
Click to collapse
Just flash a stock firmware and you should be fine.
nickwarn said:
Just flash a stock firmware and you should be fine.
Click to expand...
Click to collapse
Stock firmware does not flashes via Odin, doesn't works.
Tautvaldas said:
Stock firmware does not flashes via Odin, doesn't works.
Click to expand...
Click to collapse
Make sure you have exited Kies before you flash as this will screw up the flash...
I'm assuming your tablet isn't rooted? If so a custom rom won't flash anyway as the signature verification will stop it...
If you have got root then flash TWRP, load a custom rom onto your sd card and flash that....
ultramag69 said:
Make sure you have exited Kies before you flash as this will screw up the flash...
I'm assuming your tablet isn't rooted? If so a custom rom won't flash anyway as the signature verification will stop it...
If you have got root then flash TWRP, load a custom rom onto your sd card and flash that....
Click to expand...
Click to collapse
I can flash anything except official firmware, Custom ROM's does not work, I think it is MMC damage or bootloader, I dont know what it is.
Tautvaldas said:
I can flash anything except official firmware, Custom ROM's does not work, I think it is MMC damage or bootloader, I dont know what it is.
Click to expand...
Click to collapse
You need to know what firmware you were on and what the highest firmware you tried to flash was as this will affect what you can and can't flash...
Again, make sure you have exited Kies as this will affect the flash...
okay so i was trying to install bootloader through twrp , it failed (tried clearing dalvik and cache but it still failed) so i gave up on it and pressed reboot, once that happened, the device name appeared for a split second then dissapeared then appeared then dissapeared (keeps appearing and dissapearing) I CANT ACCCESS TWRP MENU , OR BOOT ONLY DOWNLOAD MODE, WHAT DO I DO D:
OmarKnows said:
okay so i was trying to install bootloader through twrp , it failed (tried clearing dalvik and cache but it still failed) so i gave up on it and pressed reboot, once that happened, the device name appeared for a split second then dissapeared then appeared then dissapeared (keeps appearing and dissapearing) I CANT ACCCESS TWRP MENU , OR BOOT ONLY DOWNLOAD MODE, WHAT DO I DO D:
Click to expand...
Click to collapse
Generally speaking: Install bootloader only with Odin.
You should now flash firmware using Odin to save your device. Maybe Kies could restore also.
Androidwizzard said:
Generally speaking: Install bootloader only with Odin.
You should now flash firmware using Odin to save your device. Maybe Kies could restore also.
Click to expand...
Click to collapse
how exactly do i do that? can you provide any links?
OmarKnows said:
how exactly do i do that? can you provide any links?
Click to expand...
Click to collapse
HERE you may find firmware for your country/device, download.
Start Odin, connect your phone in download mode to pc, see if Odin shows up com-port and flash firmware in tab PDA/AP.
There are several guides on youtube/google
Cant Find my carrier
my carrier is international, only countries are on that list, I dont know which one to choose, also if im gonna flash firmware is it possible to flash 4.1.2? or 4.2.2/4.3?
OmarKnows said:
my carrier is international, only countries are on that list, I dont know which one to choose, also if im gonna flash firmware is it possible to flash 4.1.2? or 4.2.2/4.3?
Click to expand...
Click to collapse
Depends on your last firmware. What was the bootloader version? If above MJ5, you can't downgrade so you are free to flash eg latest 4.4.2
Androidwizzard said:
Depends on your last firmware. What was the bootloader version? If above MJ5, you can't downgrade so you are free to flash eg latest 4.4.2
Click to expand...
Click to collapse
I have no idea what bootloader i have
OmarKnows said:
I have no idea what bootloader i have
Click to expand...
Click to collapse
Great, and which one didya try to flash through TWRP?
Androidwizzard said:
Great, and which one didya try to flash through TWRP?
Click to expand...
Click to collapse
The MJ5 bootloader, i found one that said it would be flashable through a recovery menu
OmarKnows said:
The MJ5 bootloader, i found one that said it would be flashable through a recovery menu
Click to expand...
Click to collapse
1. Never flash bootloader through recovery
2. I assume that you have had newer bootloader than MJ5 before flash, so you soft bricked your device
3. To regain full funtional device follow post #4
Androidwizzard said:
1. Never flash bootloader through recovery
2. I assume that you have had newer bootloader than MJ5 before flash, so you soft bricked your device
3. To regain full funtional device follow post #4
Click to expand...
Click to collapse
im having trouble , check my post here : http://forum.xda-developers.com/gal...m-via-odin-t2868125/post55256421#post55256421
After updating my bootloader to NE2 using odin, by phone just keeps and booting up to the Samsung Galaxy logo and restarting. The logo appears for a second or so before restarting. I can access download mode, but receive the following:
ODIN MODE
PRODUCT NAME: GT-N7100
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A2
RPMB: INVALID RPMB DATA
( the last three lines have appeared, and were not there previously before updating the bootloader). The phone was working fine with stock 4.4.2, before installing the bootloader. I cannot access recovery mode, and have flashed TWRP with odin (reported success in odin), but cannot access the TWRP recovery menu on my phone. I have tried to flash stock 4.4.2 again with odin, I do not receive any errors and receive a success 1 in odin where a blue bar is visible (when flashing) on the screen of my phone. But after the phone restarts, i experience the same bootloop problem. Help would be greatly appreciated.
Open Odin, uncheck everything, flash latest stock ROM from sammobile (https://www.sammobile.com/firmwares/database/GT-N7100/), you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
audit13 said:
Open Odin, uncheck everything, flash latest stock ROM from sammobile, you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
Click to expand...
Click to collapse
Before proceeding, I'd like to ask:
1 - I have a motherboard that I've obtained from China. Would it be ok for me to flash as you've recommended with this motherboard, taking into account the "RPMB: INVALID RPMB DATA" message that appears in download mode ?
2 - Can I install any of the latest firmwares available on sammobile for my galaxy note 2 ?
3 - Would I be able to install TWRP and custom roms after ?
Thanks
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
audit13 said:
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
Click to expand...
Click to collapse
After flashing the N7100XXUFOC2 firmware with all boxes unchecked in odin, i still receive a bootloop, and the phone is not entering recovery :-/. The messages that appear in download mode have remained unchanged.
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
audit13 said:
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
Click to expand...
Click to collapse
Yes it flashes with no errors. When turning the phone on, the samsung galaxy note 2 logo appears for just under a second, and the phone restarts and repeats until i remove the battery. Nothing happens when I try to enter the recovery menu, the same behaviour is observed (phone restarting constantly after showing SGnote2 logo). I have been reading around, and i suspect (just a guess, not sure) that the "RPMB: INVALID RPMB DATA" message that I observe in download mode may have something to do with this.
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
audit13 said:
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
Click to expand...
Click to collapse
Is there anything else that i could try ? I used an app to check the bootloader version when it was working on stock 4.4.2, and it stated that it was at LJ7. After updating the bootloader to NE1, I've experienced this problem. Would it be possible to revert back to the previous bootloader ( and would this help ?). I've flashed custom roms with no problems, beforehand using TWRP.
How did you update the bootloader? Did you update the bootlaoder without updating anything else?
audit13 said:
How did you update the bootloader?
Click to expand...
Click to collapse
I downloaded the NE1 bootloader from a user here who has a list of bootloaders on his profile (user: Androidwizzard), and flashed it using Odin v3.09 with the default boxes checked. I did not update anything else ( just clicked the "BL" field and selected the bootloader, then flashed).
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
audit13 said:
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
Click to expand...
Click to collapse
Yeah. Would it be possible to revert the bootloader back to what it was previously ? Also, is there anything else that you may suggest that i could do ? I'm still not sure what is causing this issue exactly. It seems strange that I can flash all files with no errors using Odin. By flashing a later firmware, is the bootloader automatically updated ? ( if yes, then I'm not sure why the app stated that my bootloader version was at LJ7, given that I've flashed stock 4.4.2 with odin beforehand.)
Do you have a link for the bootloader?
Did the phone work properly before flashing the new NE1 bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
audit13 said:
Do you have a link for the bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
Click to expand...
Click to collapse
I have not tried flashing the latest rom ( I could try, if that may help). I can not provide the direct link to the bootloader, since i will have to produce 10 posts ( new user here lol ). You can find the bootloader by searching google: [bootloader/modem/rom][tw kitkat][4.4.2][pf1 + pc1 + oe1 + od4 + nl1 +], then going to Androidwizzard second post.
The phone was working great before flashing the NE1 bootloader. As mentioned previously, I've flashed the N7100XXUFOC2 firmware resulting in no change.
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
audit13 said:
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
Click to expand...
Click to collapse
I will give it a go right now. Would you be able to guide me to where I could obtain the appropriate pit file for the phone ? The firmwares with PF1 have (orange) carrier. Would this affect things ?
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
audit13 said:
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
Click to expand...
Click to collapse
16 GB model. Alright, I'll try to flash the latest rom.
Hey Community,
Im new here and got a big problem with my s9.
I rooted it today with magisk, just recovered my backup.
Then i noticed that always when the phone is looking to locked screen it just crash and i cant start it (only with Volume up + Bixby + Power Button and then there choose the reboot function)
Would be great if someone know the reason why this happens.
Regards
bump
Probably something to do with restoring your backup
No talk about lucky patcher on XDA as it is classed as Warez
*Detection* said:
Probably something to do with restoring your backup
No talk about lucky patcher on XDA as it is classed as Warez
Click to expand...
Click to collapse
If i Factory Reset with my rooted phone now, will there be issues ?
Regards
EaZy21 said:
If i Factory Reset with my rooted phone now, will there be issues ?
Regards
Click to expand...
Click to collapse
No, it should just return to stock
I Factory reseted now, root is gone but the problem is still there ...
it definitly came after i root the phone, someone have ideas ?
Regards
EaZy21 said:
I Factory reseted now, root is gone but the problem is still there ...
it definitly came after i root the phone, someone have ideas ?
Regards
Click to expand...
Click to collapse
Try flashing stock 100% with CSC instead, do not restore any backup
*Detection* said:
Try flashing stock 100% with CSC instead, do not restore any backup
Click to expand...
Click to collapse
You mean flashing stock firmware?
what you mean with CSC ?
Im now download firmware from sammobile and then i flash with odin ?
Regards
EaZy21 said:
You mean flashing stock firmware?
what you mean with CSC ?
Im now download firmware from sammobile and then i flash with odin ?
Regards
Click to expand...
Click to collapse
You rooted your phone without knowing how to flash stock back?
Download the stock firmware, extract it, add all 4 sections to ODIN 3.13.1, do not use HOME_CSC, use CSC instead, put phone in download mode, flash
*Detection* said:
You rooted your phone without knowing how to flash stock back?
Download the stock firmware, extract it, add all 4 sections to ODIN 3.13.1, do not use HOME_CSC, use CSC instead, put phone in download mode, flash
Click to expand...
Click to collapse
Thank you.
This slow download on sammobile sucks btw. ^^
Regards
So i rooted again, and the problem is there again ...
i dont know what could be the problem, in stock firmware the crash in locking screen isnt there.
Regards
EaZy21 said:
So i rooted again, and the problem is there again ...
i dont know what could be the problem, in stock firmware the crash in locking screen isnt there.
Regards
Click to expand...
Click to collapse
Have you found a Fix to this? What software did you use for rooting? Did you install a custom recovery?
For me this exact thing happens with TWRP and magisk. On the TWRP Thread jesec pointed out that rooting without flashing a custom kernel will most likely cause issues.
Was hoping you may have found a solution