Related
Hey Folks,
So as the title says... I'm lost and with a bootloop's fan with is a softbrick by now.
About my phone:
Verizon Samsung Galaxy S3 SCH-I535 from 2012
Acquired with Jelly 4.3 and root it with towelroot and SuperSU so I could use it abroad. Upgraded it using the Verizon Upgraded tool to Kitkat 4.4.2 and everything was fine.
The Story:
I encountered an issue with my apps (Fb, German Bahn and Whatssapp to mention the first ones). Facebook was completely wiped out on its own and I had to install it again. The other apps their icons turned into the Android Icon and although I could use whatsapp to receive calls, I couldn't open it and I had to uninstall it. Said this I lost my whatsapp ID because of my number being different and my being abroad. I got a few new apps to solve that but once resintalling Whatsapp it told me to erase a task killer app (Battery Doctor) and I did. Two to three hours after my phone restarted itself and told me I had to factory reset which freaked me out and I looked for information to avoid this. I found none but a good recovery tool for numbers and messages.
I confronted the factory reset button like a man and nothing happened. Just bloop bloops.
I've tried flashing it with Odin and I followed so many instructions with must of them failing to some spot (NAND write FAIL!, cache.img.ex2-3-4 NOT Auth, and at some point I tar(ed) and untar(ed) my tar.md5 files and remade them in certain order I found in a post here about solving the NAND Write issues. Part of it included ticking the "NAND erase all" (which I fear by now already deleted the data I so much wanted to keep) and remake them my files with extension xxx.img for all the important ones but xxx.bin and xxx.mbn.
I succesfully flashed a recovery.img from a file called "Verizon_SCH-I535-StockRecovery.tar" (you can find it online) but now it won't even let me get to the factory reset screen and automatically reboots itself.
NOTE: it never gave me the menu option in recovery mode because it would restart. But when I didn't try to go into recovery mode I would see the factory reset screen. I am not sure what happened there.
PLEASE, I've been 5 days working on this and I also encountered issues with my laptop after downloading so many ROMs and Odin versions but I was able to fix that.
Any ideas?
List of ROMs I've tried flashing to no avail.
-ROM for my phone getting into Jelly 4.3
-ROM for my phone for Kitkat 4.4.2
-BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship-tar.md5
-i535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5
-openrecovery-twrp-2.8.5.0-d2vzw.tar
-StockVerizonGalaxyS3WithRoot.zip
-stock.vzw_root66.tar --> here the issues where the cache.img.ext4 which I changed the just -.img, -.img.ext2, -.img.ex3 and nothing happened.
Did create a tar file with the recovery.img of the stock.vzw_root66.tar file and it did work for flashing on the PDA but when it restarted I am still in a bootloop after getting into recovery mode within 4-5 seconds.
NOTE about RECOVERY MODE:
I don't have any menu to work with the sequences of holding POWER button and pressing VOLUME UP once and releasing didn't work. Neither the other way around. Tried also with POWER, VOLUME UP and HOME and I get a seemingly working Android figure during one second and then turns into the dead Android one for 4-5 secs and restarts.
Succesful ones but with no change for better or for worse:
-VRALEC.bootchain.tar.md5
-Said before recovery.img from the stock.vzw_root66.tar file
AND the pitfile for my phone SCH-I535_D2VZW_16gd.pit (Which I already used and gets me the PASS word... but nothing else)
Please can any one help me fix it? I looked the the right ROM several times and still not working. Should I just turn into a different OS other than Kitkat and/or Jelly? I haven't tried upgrading to Lollipop yet but I am thinking/fearing it might be a solution.
To Sum up,
- Recovery mode doesn't give me any option
- My phone reboots itself on recovery mode - checked all the buttons and I took them off even but still does.
- I can go into ODIN mode and stays there all day!
On ODIN mode it says:
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER RP SWREV: 2
ODIN fails to flash any WHOLE ROM file and just can "flash" the PIT and two different recovery.img (the latest from the stock.vzw_roo66.tar file.
Hope this doesn't give anyone a headache after reading it!
XDA Visitor said:
Hey Folks,
So as the title says... I'm lost and with a bootloop's fan with is a softbrick by now.
About my phone:
Verizon Samsung Galaxy S3 SCH-I535 from 2012
Acquired with Jelly 4.3 and root it with towelroot and SuperSU so I could use it abroad. Upgraded it using the Verizon Upgraded tool to Kitkat 4.4.2 and everything was fine.
The Story:
I encountered an issue with my apps (Fb, German Bahn and Whatssapp to mention the first ones). Facebook was completely wiped out on its own and I had to install it again. The other apps their icons turned into the Android Icon and although I could use whatsapp to receive calls, I couldn't open it and I had to uninstall it. Said this I lost my whatsapp ID because of my number being different and my being abroad. I got a few new apps to solve that but once resintalling Whatsapp it told me to erase a task killer app (Battery Doctor) and I did. Two to three hours after my phone restarted itself and told me I had to factory reset which freaked me out and I looked for information to avoid this. I found none but a good recovery tool for numbers and messages.
I confronted the factory reset button like a man and nothing happened. Just bloop bloops.
I've tried flashing it with Odin and I followed so many instructions with must of them failing to some spot (NAND write FAIL!, cache.img.ex2-3-4 NOT Auth, and at some point I tar(ed) and untar(ed) my tar.md5 files and remade them in certain order I found in a post here about solving the NAND Write issues. Part of it included ticking the "NAND erase all" (which I fear by now already deleted the data I so much wanted to keep) and remake them my files with extension xxx.img for all the important ones but xxx.bin and xxx.mbn.
I succesfully flashed a recovery.img from a file called "Verizon_SCH-I535-StockRecovery.tar" (you can find it online) but now it won't even let me get to the factory reset screen and automatically reboots itself.
NOTE: it never gave me the menu option in recovery mode because it would restart. But when I didn't try to go into recovery mode I would see the factory reset screen. I am not sure what happened there.
PLEASE, I've been 5 days working on this and I also encountered issues with my laptop after downloading so many ROMs and Odin versions but I was able to fix that.
Any ideas?
List of ROMs I've tried flashing to no avail.
-ROM for my phone getting into Jelly 4.3
-ROM for my phone for Kitkat 4.4.2
-BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship-tar.md5
-i535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5
-openrecovery-twrp-2.8.5.0-d2vzw.tar
-StockVerizonGalaxyS3WithRoot.zip
-stock.vzw_root66.tar --> here the issues where the cache.img.ext4 which I changed the just -.img, -.img.ext2, -.img.ex3 and nothing happened.
Did create a tar file with the recovery.img of the stock.vzw_root66.tar file and it did work for flashing on the PDA but when it restarted I am still in a bootloop after getting into recovery mode within 4-5 seconds.
NOTE about RECOVERY MODE:
I don't have any menu to work with the sequences of holding POWER button and pressing VOLUME UP once and releasing didn't work. Neither the other way around. Tried also with POWER, VOLUME UP and HOME and I get a seemingly working Android figure during one second and then turns into the dead Android one for 4-5 secs and restarts.
Succesful ones but with no change for better or for worse:
-VRALEC.bootchain.tar.md5
-Said before recovery.img from the stock.vzw_root66.tar file
AND the pitfile for my phone SCH-I535_D2VZW_16gd.pit (Which I already used and gets me the PASS word... but nothing else)
Please can any one help me fix it? I looked the the right ROM several times and still not working. Should I just turn into a different OS other than Kitkat and/or Jelly? I haven't tried upgrading to Lollipop yet but I am thinking/fearing it might be a solution.
To Sum up,
- Recovery mode doesn't give me any option
- My phone reboots itself on recovery mode - checked all the buttons and I took them off even but still does.
- I can go into ODIN mode and stays there all day!
On ODIN mode it says:
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER RP SWREV: 2
ODIN fails to flash any WHOLE ROM file and just can "flash" the PIT and two different recovery.img (the latest from the stock.vzw_roo66.tar file.
Hope this doesn't give anyone a headache after reading it!
Click to expand...
Click to collapse
Hi,
Kindly register yourself at XDA post which you can query in http://forum.xda-developers.com/galaxy-s3-verizon/help
Experts there may be able to help you
I inherited a Galaxy S7 from my brother after he recently passed away. He was with T-Mobile, so it's a G930T (I have the original box, too, which has come in handy). I brought it back home with me... to France. I figured I'd have it unlocked and replace my old smartphone with this newer one.
Since I didn't know what his pin was, I did a factory reset... and found myself stuck in FRP!
At that point I called T-Mobile and was able to have myself added as an authorized user on my brother's account. They gave me the pin (too late! gah!) and unlocked the phone on their end, as it had been fully paid for. But as far as the FRP thing they were unable to help.
After a lot of googling, I found a bunch of how-to videos explaining how to bypass FRP, I thought I was in luck... except none of them worked for me. Then I came across a comment stating that flashing the device might do the trick. So I decided to try that... but now I'm locked in a boot loop (on the Samsung Galaxy S7 screen that keeps flashing on and off).
Here's what I did, step by step:
1) I installed Odin 3.13.1 from samsungodin.com
2) I downloaded & unpacked a stock ROM from sammobile.com, more specifically this one:
G930TUVS8CRJ1 - GALAXY S7 SM-G930T TMB USA (T-MOBILE)
3) I connected the phone to the laptop
4) I ran Odin and selected (with the AP button) the AP_GS30T* file & hit "start"
Odin said PASS! and I thought all was good... except it wasn't.
So I went googling some more and found a great page... which I am not allowed to link to yet, apparently, but it's on thedroidguy's website.
Only problem is that I can NOT get into the Recovery Menu. When I try the procedure (Home+Volume Up+Power) all I get is "recovery booting" in a bright blue font and THAT starts flashing on and off instead of the Galaxy S7 screen. If I redo the same button sequence, it just switches back to the other screen.
The ONLY other screen I can get to (unless there's another trick I haven't heard of yet) is the blue 'Warning' screen from which you can install ROM's (Home+Volume Down+Power).
So I tried to reinstall that same ROM two other times. First because I wasn't sure if I'd ran Odin as an administrator the first time around, figured that might be the issue, but that didn't change anything. Then I gave it another shot, this time using the phone's original USB cable (I had initially used mine), hoping that would make a difference... but of course, it did not.
So... is there anything I can do at this stage? Did I maybe go for the wrong ROM? Is there another one I can try?
I just hope it's not permanently bricked :-o
So I managed to unbrick my device, yay me! It took me some time to figure it out, but the solution was quite simple. Up until that point I had only been flashing the AP file alone. What fixed my problem was to also flash the bootloader (BL) file. This got me out of that boot loop.
I still haven't managed to bypass that annoying FRP lock, though. Every technique I've tried has failed.
On the plus side, I'm becoming an expert at flashing :-o
I just came across a method that, I think, could work: flash the factory combination file, enable usb debugging, then flash the regular firmware (with all files except CP).
My problem is that I can only find ONE combination file for the G930T but it doesn't match ANY of the firmwares available on sammobile... is this a problem?
The filename is similar to the v6 firmwares, only the last 4 characters don't match.
The other issue is that none of the v6 firmwares will flash on my device (they all fail pretty quickly while going through the AP file)... will using the combination file fix this?
Any thoughts or suggestions would be greatly appreciated.
Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288
cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.
Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm
Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.
Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.
Same situation right now with my S7. Damn.
Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa
Anyone?
I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...
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!
After the most recent update my phone got put into a bootloop that wouldnt stop for some reason, it would boot and then after I wanna say less than 20 seconds it would reboot itself, and just kept going on in this cycle unless I powered it off when it was booted. Anyway I've been trying everything I can to get the damn thing working again so I can at the very least get my pictures off of it without factory resetting it and nothing is working, and I sorta feel like I've made things worse. I tried flashing with Odin but after that the thing just stopped booting alltogether so that kinda limited my options a lot. Now I'm trying to sideload an update from an sd card which might work if i can find the right thing to sideload onto it but before it gets anywhere it tells me error in /sideload/package.zip (status 7) so either I just need a different thing to sideload or something's broken. Either way I don't know how to get it working cause I have no idea what I'm doing here so now I need help.
My phone is SM-G970U SPR
Sounds like you are in a bad spot. If your pictures are on internal storage then flashing anything in Odin will wipe that.
I think you need to accept that they may be lost.
not so fast, i've used home_csc in all my flashes and when I finally got one working all my stuff was still intact. Now i just need to figure out how to get it to stop bootlooping.
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
AlphaFeedback said:
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
Click to expand...
Click to collapse
Download the latest official firmware with Frija tool (no download caps unlike websites like Sammobile etc). Just be aware that if you download and use Android 11 you wont be able to downgrade to Android 10.
After you have downloaded it unpack the zip and run Odin. In order to preserve your data flash the HOME_CSC file not the regular CSC... file. Once you unpack the files you will see.
The phone needs to be in download mode for flashing and battery is suggested to be at 40% or more.
Btw a good way to get out of bootloop and get the phone to shut down is to connect the USB cable (could be from charger or PC) and then press Volume Down+Power buttons to force a restart. It may be nessesary to do this a few times.
At one point you will not see the boot screen but instead it will show the lightning bolt charging logo and the percentage. After that you can simply unplug the cable and the phone will turn off.
In order to enter Download mode the best way is to start with phone turned off. Hold Bixby+Volume Down buttons and connect the USB cable from PC. Once you see the confirmation screen you can release the buttons and press Volume Up to continue.
AlphaFeedback said:
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
Click to expand...
Click to collapse
So incredibly glad to hear I'm not a lone soul dealing with this issue. I've tried a whole bunch of things to fix this issue but nothing is getting me anywhere. I tried flashing android 10 but as that other lad said you can't flash older versions of android.
At this point I think my only chance of saving the phone is to wait for a new system update to release and flash that in case it somehow magically fixes the phone for some reason. I wouldn't recommend trying to flash atm because it doesn't seem to help currently and if you donk it up you'll lose your data which is not something either of us want to do.
I'll let you know what happens if I try flashing a future update.
Well i had an even bigger problem initially. Not only was my S10e bootlooping. My EFS partition was missing files (dont know how that happened). That meant that IMEI was blank and there was not network connectivity aside from Wi-Fi.
Unfortunately even the stock firmware flash does not fix EFS. Thankfully i had a backup (multiple actually) stored away including EFS. So with some fiddiling around in custom recovery file manager (TWRP) i manged to get that restored. I did lose bunch of pictures in intrernal storage tho. Thankfully it was nothing important. Now i keep everything on SD card and SD Cards backup in PC.
Now im trying to get the phone rooted with Magisk but the damn thing is not working.
This underscores the importance of regular (i had weekly TWRP) backups. I had backups of all partitions except internal data like pictures etc. Lesson learned i guess.
Hey RaXelliX thanks for lending a hand! Unfortunately I'm using a Mac Pro and Frija is a Windows exclusive *tears*
it seems that my next best alternative is to use Samloader instead of Frija, and JOdin3 instead of Odin. After some research ive realized that I am way out of my depth , but shall continue nonetheless. I'm gonna try your method with these alternatives and hope for the best, that sounds good in theory I was just curious to the thoughts of others more experienced.
And Oske829 your definitely not alone, stay strong and best of luck
Thanks!
There was a new firmware on Sammobile that I just tried flashing, didn't fix the problem, still bootlooping. I am officially out of ideas on how to fix this. I think there's something funky at the hardware/software level that's throwing a fit about having to run android 11 that's causing this, but I have no clue what it could be or how to resolve it. Not sure if there's anything i can do at this point to save my data.
Oske829 said:
There was a new firmware on Sammobile that I just tried flashing, didn't fix the problem, still bootlooping. I am officially out of ideas on how to fix this. I think there's something funky at the hardware/software level that's throwing a fit about having to run android 11 that's causing this, but I have no clue what it could be or how to resolve it. Not sure if there's anything i can do at this point to save my data.
Click to expand...
Click to collapse
You could try flashing a custom recovery (i suggest TWRP: https://eu.dl.twrp.me/beyond0lte/ S10e Exynos version) and the once in recovery connect USB cable to move the data off. If you succeed then you could wipe the phone and get out of bootloop.
When flashing recovery via Odin use the AP field and select the twrp-3.5.0_9-4-beyond0lte.img.tar file and make sure NAND Erase and Re-Partition are OFF. Auto-Reboot could be on or off.
This would touch only the recovery partition and will not wipe data unless you do it yourself inside TWRP.
There are a few caveats with this. The phone may complain about missing VBMETA header. If that's the case i will share a modified TAR file that includes that and TWRP itself. Or the phone could fail flashing custom recovery due to Vaultkeeper that prevents flashing unofficial binaries. This usually happens a day or two after flashing firmware. After that Vaultkeeper disengages.
Obviously your bootloader should be unlocked. You can do that by pressing Bixby+Vol Down before connecting the cable (with phone off) and then long press Vol Up to enter bootloader unlock mode. Bootloader can later be relocked again.
RaXelliX said:
You could try flashing a custom recovery (i suggest TWRP: https://eu.dl.twrp.me/beyond0lte/ S10e Exynos version) and the once in recovery connect USB cable to move the data off. If you succeed then you could wipe the phone and get out of bootloop.
When flashing recovery via Odin use the AP field and select the twrp-3.5.0_9-4-beyond0lte.img.tar file and make sure NAND Erase and Re-Partition are OFF. Auto-Reboot could be on or off.
This would touch only the recovery partition and will not wipe data unless you do it yourself inside TWRP.
There are a few caveats with this. The phone may complain about missing VBMETA header. If that's the case i will share a modified TAR file that includes that and TWRP itself. Or the phone could fail flashing custom recovery due to Vaultkeeper that prevents flashing unofficial binaries. This usually happens a day or two after flashing firmware. After that Vaultkeeper disengages.
Obviously your bootloader should be unlocked. You can do that by pressing Bixby+Vol Down before connecting the cable (with phone off) and then long press Vol Up to enter bootloader unlock mode. Bootloader can later be relocked again.
Click to expand...
Click to collapse
Is this exclusively for exynos phones or can I run twrp on a qualcomm device?
nevermind i found the snapdragon version of twrp
I'm trying to unlock the bootloader the way you described but that doesn't seem to be doing anything, and any guides I'm seeing on how to unlock it all involve doing something that resets the phone which isn't what I'm going for.
Oske829 said:
I'm trying to unlock the bootloader the way you described but that doesn't seem to be doing anything, and any guides I'm seeing on how to unlock it all involve doing something that resets the phone which isn't what I'm going for.
Click to expand...
Click to collapse
You might be out of luck as Snapdragon versions do not allow bootloader unlocks. At least as far as i know. I wrongly assumed you had Exynos version. If the data is important the last resort might be to contact some data recovery company. Im sure they have tools to access the internal memory even if the phone bootloops or flat out refuses to boot.
Flash 4 file firmware
Use Home_csc
If you want keep your data
Hucin44 said:
Flash 4 file firmware
Use Home_csc
If you want keep your data
Click to expand...
Click to collapse
I believe he already tried that and the phone is still bootlooping. Im betting that whatever causes the bootloop is in the data, the data he needs to access.
A bad situation all around because if he wipes the data it will likely fix the bootloop but he will lose the data. If he keeps the data the phone will keep bootlooping and he wont be able to access it. Although i would argue that the data you cant access is effectively lost anyway and that the proper functioning of the phone is more important.
I've heard that theres tools you can use to recover deleted data after resets and stuff since data doesnt get wiped when its deleted its just marked as stuff that can be written over. So I would think there would be a way for me to reset my phone to get it working and then recover the data with one of those programs, but the problem is from what I've heard you need a rooted device to do any of that and since I can't unlock my bootloader I don't think that can happen.
The one last thing I'm going to try before I seek out help from data recovery people is to try pushing the smartswitch apk onto the phone with adb and then hoping I have enough uptime to install it before the phone reboots cause I've heard you can use smartswitch in download mode to backup data, but I haven't found any guides anywhere about how this is done so I don't know if its actually doable.
Oske829 said:
I've heard that theres tools you can use to recover deleted data after resets and stuff since data doesnt get wiped when its deleted its just marked as stuff that can be written over. So I would think there would be a way for me to reset my phone to get it working and then recover the data with one of those programs, but the problem is from what I've heard you need a rooted device to do any of that and since I can't unlock my bootloader I don't think that can happen.
The one last thing I'm going to try before I seek out help from data recovery people is to try pushing the smartswitch apk onto the phone with adb and then hoping I have enough uptime to install it before the phone reboots cause I've heard you can use smartswitch in download mode to backup data, but I haven't found any guides anywhere about how this is done so I don't know if its actually doable.
Click to expand...
Click to collapse
Well I find myself here after 48 hours of s10e hell, with an almost identical issue. After a couple attempts and a trip to our local cell phone repair place, we ended up doing a factory reset, with the same hopes -- that the files were still there but the space marked as "free" and a 3rd party data recovery program could bring them back from the dead.
But they all require your phone to be rooted first - and this being my first venture into phone rooting I'm not really sure which route to go, or if it'll even be worth the effort. Does rooting the phone mean flashing it with a new OS, or simply unlocking superuser access so the recovery software can do its bit? (bear in mind, a lot of these products try to root the phones themselves, but none of them seem to work - I've tried about 4 different products thus far).
I'm convinced that if I can root this phone, the recovery software WILL find those lost sectors and recover the lost data, even after a factory reset -- there's plenty of youtube videos out there that say you can do this, but the rooting bit is what's got me tied up in knots!
huh.. jeah, latest update bricked my s10e too.
but my case, when power on phone, nothing happens, just black.. when conect cable to pc , then i can enter recovery and download mode..
till now nothing helped..
oem locked, frp locked, cant flash custom binaries!
hope next update will fix this madnes..
or need to find same firmware as update.zip what we can flash using stock recovery option (sadly saamsung dont give any update.zip files, i gues its money thing)
so, odin dont help, chimera tools dont help, and enginering combination file give some approval error to flash factory binaries!
houdini987 said:
I'm convinced that if I can root this phone, the recovery software WILL find those lost sectors and recover the lost data, even after a factory reset -- there's plenty of youtube videos out there that say you can do this, but the rooting bit is what's got me tied up in knots!
Click to expand...
Click to collapse
well ,as far as i know, thease all recovery lost data works with HDD type disks, flash memory are out of luck..
because, i easy restored deleted data from my HDD, if it wasnt multiple times formated or writed full hdd , deleted, writed full etc.. but with SSD that software isnt working, due flash memory.. but, maybe im just to old, and there are new softs who can do that, just, i have not seen any jet!