I am the proud owner of the SM-G970F
bit of backstory: about 2 weeks ago I had my ideal setup, I was rooted with magisk (using John sun's guild) and I had twrp Installed. Everything was going well until my phone started to run so slow, I did a geekbench test and I was getting 4000 on the multi score (I should get 10000 for my phone,) I wiped cache and my data NOT my os. As I was booting my phone back up It took a while to restore like 2 hours just sat on the Samsung logo, I was getting worried but then it changes to starting android and that's where I went to sleep, the next morning I unplug my phone from the charger and it's still on starting android it's been about 9 hours on this screen. I boot into twrp and do another wipe of cache and my data, and still the same thing, so I boot it into download mode and flash the stock firmware again (BL, CP, AP and CSC). The flash was successful I am now in my phone on stock recovery now I try to root again and start it all again by downloading the firmware from sammobile and patching the AP file, I continue on with the routing steps carefully following all of them, once done and booted into the os I setup my phone without restoring my data. I look for magisk manager and it's not there... I press on the settings app and it says app not found my phone starts to freeze until none of the buttons are doing anything the screen wasn't responding. I had no choice but to go back to stock where I am now
I have tried to root again following John wu's steps very carefully about 5 times and every time the same happens, last time I tried it was getting slow again so I tried to reboot and as it was turning on this came up in red in the corner of the screen it said something like "can not flash custom binaries now" then turned off and it did the same about 5 times until I managed to get it into download mode to flash stock AGAIN
I think it may be something to do with the way magisk patches the firmware I believe it's that my phone had corrupted files or something in the boot sector so when magisk tries to patch the AP file something goes wrong... I have also noticed that when magisk patches the file it is about 500mb less than the original AP file not sure if that's normal cant remember
anyways thank you if you read all that and please give me some tips and share it with John wu or something to try and get some help!!!
have a nice day
Hi,
check this manual:
https://www.the***********.com/samsung-galaxy-s10-twrp-magisk-root-guide/
*** are custom droid(without space between)
Did you do all steps? Maybe you forgot something (like me).
Leg1ndd said:
I am the proud owner of the SM-G970F
bit of backstory: about 2 weeks ago I had my ideal setup, I was rooted with magisk (using John sun's guild) and I had twrp Installed. Everything was going well until my phone started to run so slow, I did a geekbench test and I was getting 4000 on the multi score (I should get 10000 for my phone,) I wiped cache and my data NOT my os. As I was booting my phone back up It took a while to restore like 2 hours just sat on the Samsung logo, I was getting worried but then it changes to starting android and that's where I went to sleep, the next morning I unplug my phone from the charger and it's still on starting android it's been about 9 hours on this screen. I boot into twrp and do another wipe of cache and my data, and still the same thing, so I boot it into download mode and flash the stock firmware again (BL, CP, AP and CSC). The flash was successful I am now in my phone on stock recovery now I try to root again and start it all again by downloading the firmware from sammobile and patching the AP file, I continue on with the routing steps carefully following all of them, once done and booted into the os I setup my phone without restoring my data. I look for magisk manager and it's not there... I press on the settings app and it says app not found my phone starts to freeze until none of the buttons are doing anything the screen wasn't responding. I had no choice but to go back to stock where I am now
I have tried to root again following John wu's steps very carefully about 5 times and every time the same happens, last time I tried it was getting slow again so I tried to reboot and as it was turning on this came up in red in the corner of the screen it said something like "can not flash custom binaries now" then turned off and it did the same about 5 times until I managed to get it into download mode to flash stock AGAIN
I think it may be something to do with the way magisk patches the firmware I believe it's that my phone had corrupted files or something in the boot sector so when magisk tries to patch the AP file something goes wrong... I have also noticed that when magisk patches the file it is about 500mb less than the original AP file not sure if that's normal cant remember
anyways thank you if you read all that and please give me some tips and share it with John wu or something to try and get some help!!!
have a nice day
Click to expand...
Click to collapse
Hi,go to download mode and check if your KG is prenormal.
If it isnt,use Magisk 19.3 Stable dont use Canary.
Hope this helps
ExtremeGrief said:
Hi,go to download mode and check if your KG is prenormal.
If it isnt,use Magisk 19.3 Stable dont use Canary.
Hope this helps
Click to expand...
Click to collapse
thank you I will give it a look now ))
ExtremeGrief said:
Hi,go to download mode and check if your KG is prenormal.
If it isnt,use Magisk 19.3 Stable dont use Canary.
Hope this helps
Click to expand...
Click to collapse
Hii my kg state is prenormal. Any fix for this i tried flashing stock and everything but nothing works
Related
As the description, silly me flashed TWRP and in bootloop AQF5 for my G955F, can't enter TWRP or start normally.
Read through a few threads and tried the flash TWRP twice and instantly attempted vol up, Bixby & power button after restarting in from odin mode but it just sits in bootloop, boots into odin fine, tried so many time, with no lucks.
I have a Smartswitch backup but my phone isnt being recognised, so I try the emergency firmware route, the download & initialization gets to 83% and I get an error message, so my back up is useless until I manage to reboot or at least flash a new rom in TWRP (if I can get into it)
Just to I'm stock no root, TWRP flash knocked my Knox to 1 which i'm not bothered anyway
Been trying the past 2 days to download from samfirmware, samsung-firmware.org & updato to which my download gets to 40%, 73% and 80% before it decides to start pending then fail when I retry, been on phone to ISP and no problem on my line so I'm strumped and in need of AQF7 BL and CP please....
good thing I have an S7 as a spare
iamsloany said:
As the description, silly me flashed TWRP and in bootloop AQF5 for my G955F, can't enter TWRP or start normally.
Read through a few threads and tried the flash TWRP twice and instantly attempted vol up, Bixby & power button after restarting in from odin mode but it just sits in bootloop, boots into odin fine, tried so many time, with no lucks.
I have a Smartswitch backup but my phone isnt being recognised, so I try the emergency firmware route, the download & initialization gets to 83% and I get an error message, so my back up is useless until I manage to reboot or at least flash a new rom in TWRP (if I can get into it)
Just to I'm stock no root, TWRP flash knocked my Knox to 1 which i'm not bothered anyway
Been trying the past 2 days to download from samfirmware, samsung-firmware.org & updato to which my download gets to 40%, 73% and 80% before it decides to start pending then fail when I retry, been on phone to ISP and no problem on my line so I'm strumped and in need of AQF7 BL and CP please....
good thing I have an S7 as a spare
Click to expand...
Click to collapse
I think you only need to flash the bootloader:
https://drive.google.com/file/d/0B0pBZnf22V4qUEVsWTUwOWJwdkE/view?usp=sharing
samteeee said:
I think you only need to flash the bootloader:
https://drive.google.com/file/d/0B0pBZnf22V4qUEVsWTUwOWJwdkE/view?usp=sharing
Click to expand...
Click to collapse
Thanks pal, I ended up downloading AFQ7 after my ISP called me to say they have identified and fixed a fault on my line, my S8+ is back to normal and I've refused to install to AFQ5 update haha think I'll root it tomorrow seeing as I have a way of bringing myself back to stock now
Much appreciated
Can admin close the thread please, problem solved
Help Help Help :
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got TWRP cant install.Because. OEM locked.
It flashed. Great. But now IT STILL DOESNT BOOT. I'm stuck at NO COMMAND, it keeps restarting after 20-30 seconds of showing no command. and it's looping all over.*
i flashed stock firmware.It is flashed.Then reboot.Then install system update.Then Erasing.Then rebooting.Then NO COMMAND.Then reboot itselve recovery mode.Then i wiped factoory and cache.Then press rwboot to system.Then Samsung Galaxy S8 Plus.Then install system update.Erasing.No Command. etc. Keeps rebooting. its on NO command screen. It just restarts. Doesnt boot. I want to enable OEM Unlock. I installed combination binary. But not appear in Developer Mode.
i flash atock with Kies emergency.I flash different stock firmware from updato.com. But nothing happend.
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
JeffDC said:
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
Click to expand...
Click to collapse
KIES says that. (THR) Stock. i downloaded it and flashed with Odin. Then reboot. Then system install update. Then Erasing. Then reboot and No Command! 30 seconds keeps rebooting itself 30 seconds interval Random.
I did factory format, cache clear. then the same problem. i want to install twrp recovery with oden. It says Oem Lock. Not allowed. But i flashed Combinary file. I can get into system and i to developer mode but dosnt seem OEM UNLOCK that ll do enable it.
Ok mate, but if you press Vol- + Bixby + power for couple of seconds, can you access to download mode? If you can, I think you'll have to install the firmware all over again.
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Did OP find a fix to this problem?
I am experiencing a similar issue. Picked my phone up to find had randomly gone into a boot loop. Tried soft reset, cache wipe, factory reset - all successful but the phone would still reboot and be stuck on device model screen. Next I decided to flash the device with stock firmware. The flash passed in Odin, the phone then rebooted, loaded to device model screen, then a screen appeared saying "installing updates" which would make it to 25% then crash. After this the phone keeps booting, shows a screen with a dead android icon and says "no command" or "error". I have tried to flash the device using Oreo and Nougat firmware but have failed every time (although the flash did pass in Odin)
Any help would be greatly appreciated as I would rather not buy a new phone due to a random hardware fault which is out of my control.
southsideswaggar said:
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Click to expand...
Click to collapse
This is perfect if you have soft bricked your phone!
follow this video maybe it help you
https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395
https://www.youtube.com/watch?v=VTi3uBkpJic&t=155s
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
J727P
Nupid Stoob said:
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
Click to expand...
Click to collapse
ok you have an older phone the J700P you can start by downloading odin an twrp recovery an superSU zip you can get twrp from here !https://twrp.me/devices/samsunggalaxyj72015qcomsprint.html
an odin from here
https://mega.nz/#!nYVDXBAC!_cTWbW4_Ow8sZMWcZvO7bVwEEBFlD1DQsB5NeFhj1EY
An just google latest superSU zip to find that !
good luck !
step 1 enable oem in development settings !
step 2 put phone into download mod an flash twrp then boot into twrp recovery an flash superSU zip !
Thank you for the info. I'm presently confused. Here's what I've done:
I ran Odin and flashed with twrp-3.2.1-0-j7ltespr.img.tar. It went through successfully going off odin's message.
Vol. up + home + power. It'll eventually show a yellow triangle with the white trash can guy on it's side stating "No Command". Power + up gets the Android Recovery screen.
At this point, am I supposed to choose the Wipe Data/factory reset option? I see tuts that seem suggest I should already be in the twrp UI or something. I've tried watching vids and looking at a handful of tuts, but either they are the wrong phone, too old, the button combos show something else entirely, etc.
Thanks!
Anyone? Videos show the buttons vol. up + home + power as booting right into twrp recovery gui. For me, it's going into "Android Recovery" screen. Is there an extra step with Odin or something that I missed? Or am I supposed to wipe/boot in the Android Recovery screen and it'll boot the twrp recovery gui? If bricking something I'm not familiar with wasn't a concern, I'd be courageous with it.
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
J700P
Nupid Stoob said:
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
Click to expand...
Click to collapse
Ok when flashing twrp with Odin first uncheck auto reboot in options flash twrp pull battery replace battery an boot into twrp an flash superSU zip then reboot system !
Thank you so much Peter! That did the trick THANK YOU :good:
For posterity to anyone else w/limited root knowledge with a SM-J700P Virgin variant running 7.1.1 (and what was most recent factory updates until this point); Flashed the twrp-3.2.1-0-j7ltespr.img.tar again w/o auto reboot in options of Odin, pulled battery once safe (i.e. you get the "Pass" message from Odin confirming everything went as planned) to get out of the downloading screen, replaced battery, booted the recovery (vol up + power + home) and it finally booted into the twrp recovery gui. Selected the "Install" option, then went to where the supersu.zip was stored on the SD (I created a separate "supersu" folder via PC connection for easy locating; internal phone memory card looks to now be unlocked, so can most likely use that if you don't have a SD card). Checked the "reboot once installed option" in the gui box and swiped to install supersu,zip and verified it was rooted via app after phone fully booted back up.
BTW, If anyone gets a hang/crash in Odin immediately after trying to select a twrp tar image in the "AP" box, try downloading the twrp image via PC instead of the through the phone (the legit twrp site that has the repository of past/current .tar), and just put it somewhere like Odin folder on desktop. Somehow, mine were getting corrupted via phone download through the twrp app, and Odin would NOT recognize the file was bad/corrupt when trying to select it via the AP box and hangs instead of giving a warning message. I ran into this earlier on then noticed the file was too small for some reason after viewing it on my PC, hence the Odin hang that needed a task manager kill.
I hate to necro an old thread but I still do not want to create an entire new topic for a single question. If I was to follow this info will it wipe the phone or will it simply root it while keeping all data on the phone? I ask as it is my wife's old phone and she would be pissed if I wiped her apps and everything on accident since she wont be able to remember what she had.
Edit: also when I add the TWRP file to odin it immediately hang/crashes like OP mentions but I am already DLing via pc. any thoughts?
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
philipp-h said:
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
Click to expand...
Click to collapse
Philip, it helps if you let us know what country your in.
Anyway the solution to your problem is pretty straight forward, you just need to flash the latest firmware for your region with Odin. No need to mess about with TWRP at this point.
Official firmware will contain a copy of the stock kernal which will also be installed when you flash with Odin 99% of the time. If for some reason the kernal is not flashed (it happens) and you continue to get the reboot issue then you will need to flash the kernal seperately first with Odin then the firmware afterwards.
The issue with the FRP lock will remain after this but should allow you to unlock with google email and password.
So we're talking, downlaod mode, flash official fimrware and go from there.
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
philipp-h said:
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
Click to expand...
Click to collapse
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
cooltt said:
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
Click to expand...
Click to collapse
Hi cooltt and thanks for your help!
Unfortunately the BTU-ROM did not solve the freeze-reboot-problem but led to another: After flashing the phone gets stuck with a blue screen "Erasing". After several hours I force rebooted and now it is showing a similar screen with "Error!" and a percentage which is increasing to a random number from 0% to 12% on each boot. On first boot it shows the boot screen ("Galaxy S7"), then "Installing system update" shortly and then "Erasing". After force-reboot it shows boot screen, "Erasing" then "Installing system update", both for a very short time (sometimes misses "Installing...")
As suggested I used SamFirm to download the newest BTU-ROM (SM-G930F_1_20191218140415_dgobhw6g3v_fac; G930FXXS7ESL5/G930FOXA7ESL5/G930FXXS7ESL5/G930FXXS7ESL5). I just ticked F. Reset Time and Reboot. Re-Partitioning did not change anything. Using Odin v3.13.1 does not make a difference. The other ROMs, like SM-G930F_1_20191226131628_8ds2p6kf0v (G930FXXS7ESL9/G930FDBT7ESL9/G930FXXS7ESLA/G930FXXS7ESL9) which I downloaded with Frija (should do the same: download enc4-files from Samsung and decrypt) make the phone going to the initial setup fine, but with the reboot-problem. Tried also with Odin 3B patched.
At this point I was going to write, that I could not access the recovery mode with the BTU-ROM but just now I started it unintentionally when looking for the sequence of screens showed on boot. So I used my chance, made a full wipe and screenshot. After this the phone booted until the glowing "Samsung"-logo appeared. Then rebooted and went to initial setup (after "Androi"Installing applications") in German. The freeze-reboot-issue appears as with all the other ROMs.
The phone is certainly an original SM-930F as it was bought directly from a big, trustworthy dealer and then just used by my aunt. The only one touching it when problems appeared was me. There is SM-G930F printed on the backside and showed in download mode.
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
philipp-h said:
Hi cooltt and thanks for your help!
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
Click to expand...
Click to collapse
Hi Phill
The only options checked in Odin should be F-Reset and Auto reboot. Don't check any others.
The blue screen erasing and updating is normal after a flash with Odin, the phone will restart a couple of times, just leave it do it's thing for a bout 10 minutes or so. If it's any longer than that as you have mentioned then it's stuck as you've said.
So we're going to start from the begining again but do something slightly different.
1. Place the phone into download mode
2. Run Odin but uncheck "Auto Reboot" so the only option checked is F-Reset Time.
3. Use whatever firmware you want, BTU or DBT the latest version. Make sure files are in the correct boxes.
4. Connect phone and flash with Odin, wait until Odin says "succeed 1" and "dissconnected" . It may even say "pass" in green, not important but "succeed 1" is important.
5. Your phone will show the bar and do not disconnect. So....disconnect from laptop / PC. The screen should remain "do not disconnect".
6. Hold volume down+home+power (in that sequence).
7. As soon as the screen goes black move your finger to volume up, while still holding down home + power. You are trying to get the phone into Recovery mode as you said earlier.
8. The option to choose in the recovery menu is "wipe cache partition" NOT "wipe/factory reset". I can see from your pictures that this option has failed because the FRP lock is still on!!
9. When you've chosen "wipe cache partition" then choose "reboot system now"
The phone should go through it's normal set up routine, erasing, update, installing apps etc, just leave it do this and hopefully the phone will boot then ask for the Google email and password which was used on the phone.
There are very few reasons for the phone to get stuck on boot....
1. Incorrect firmware,
2. Water damage
3. The phone has been Rooted with FRP lock on. It is very rare to be a hardware issue.
You should always turn FRP lock off and enable OEM unlock in settings before flashing to a phone. I know it's a little late for that but something to remember.
To check for water damage.
1. Remove SIM card and holder
2. Shine a light in the hole, you will see a WHITE sticker which turns PINK if water has ever got inside the phone.
Thanks a lot again for your great efforts!
I tried as you wrote but did not manage to start recovery immediately after flashing (tried >10 times). But after some while the BTU-ROM started and now keeps doing so even after new flash without wiping cache afterwards. Wiping data worked for me in past when I sometimes had enough time to enter Wi-Fi-password. It was saved even after reboot and away when I did data wipe in recovery. With the newest ROMs I never got beyond typing Wi-Fi credentials.
I cannot see a water damage. A root was never tried before (and OEM-lock and FRP were always on because stock, which is very bad now ). Would be absolutely no problem if this !#@*#% stock ROMs would work... TWRP installation was directly blocked when I tried my luck as last resort. I did not try other images.
Thanks nevertheless for your time and patience!
So I decided to manually update my galaxy s8+ since samsung oficially stopped suporting it for future feature updates and my phone started to get too slow, so my idea was to put the lighter lineage os on it.
To do that, first, I first had to get root.
To do that, I followed an step by step guide and I finished it (im new so i cant put the link to the guide, but it's form androidinfotech/.com and the title is "Root Samsung Galaxy S8 Plus SM-G955F Pie 9.0 using TWRP"). Then I finally rebooted my phone to see if I had root installed, and an error popped up: Verification failed, unable to restart your device, that after a little of research I realized it was quite a common error on samsung devices.
After that I checked threads of people that this had happened to and it said to reboot in twrp, which of course, I installed before rooting my phone, and wipe the data and some other steps.
But the problem is that after hitting reset and inmediately hitting the button combination for recovery mode, it just launched recovery mode for a few seconds and then the screen goes black inmediately after, and sends me back to the verification failed error. So basically I can't initiate in recovery mode.
I've tried other keys combinations and they either don't work or aren't of any use. Also, I can acces download mode, if that is of any use.
Does anyone know what to do here or something?
Figured it out
turns out i hadn't wipe the data properly. from that verification failed screen i turned my phone off like you normally do it, with the power button. then accessed the recovery mode after the phone was off. that was why i couldn't access the recovery mode before. after that, i found a fix for the error that showed while wiping data and then i re installed everything i had installed before and rebooted and now everything works. hope this helps someone...?
Guy this quite helped me but my trial for s8+ exynos 9.0 at first I successfully flashed twrp via Odin but the files (magical zip,mmstate zip ,some security patch zip with noverity zip ) allowed me to root well only to end up with 1gb internal storage, I then reflashed stock how ever after that I can't flash recovery via Odin as its always shows failed official binary allowed only. I'm sure its possible to root but am missing something important. Hope to gain some enlightment as a newbie. Thanks in advance
Abdul-Hanan. B. Jonathan said:
Guy this quite helped me but my trial for s8+ exynos 9.0 at first I successfully flashed twrp via Odin but the files (magical zip,mmstate zip ,some security patch zip with noverity zip ) allowed me to root well only to end up with 1gb internal storage, I then reflashed stock how ever after that I can't flash recovery via Odin as its always shows failed official binary allowed only. I'm sure its possible to root but am missing something important. Hope to gain some enlightment as a newbie. Thanks in advance
Click to expand...
Click to collapse
homie, youre best off posting up an entirely new thread with your issue as most folks will likely miss a post like this on a year old thread. the 1gb of storage is usually fixed with a factory reset done in recovery. If not, youre going to have to flash the stock FW on it again via Odin to tell its storage table how much storage it actually has