Related
Hi Everyone,
I've come on bended knee, and I have about 30 xda windows up where Ive tried to upgrade a perfectly working LG from android 2.2. But no matter what I try I cant get beyond the LG wink icon on the screen.
I have tried fastboot omao4boot 1.22 modified etc but I cant get past MLO (x-loader) I say YES to this but NO to 'fastboot devises' as per instructions (although why I say no to this, I dont know?) anyway it just says 'waiting for device' but nothing happens even if I take the battery out and disconnect from USB and reconnect, nothing ever happens?
So having redone the fastboot procedure, I managed to into boot mode - yellow round icon on screen and then tried to flash using LG flash tool 1.2 with LGP920 30A bin & fls files which it does and completes successfully, I have also used the LG recovery tool to flash recovery and firmware but all of the above wont let me boot the devise it just sits at the LG Icon.
Tried booting into recovery with 3d + vol + key but just ignores and goes to red LG Icon with the usual boot sound, I just cant get anything else to work! Is it down to the MLO loader issue. I dont know what else to do.
Please can anyone help me recover my phone I wanted to upgrade to JellycreamR5 cause its suppose to be a good rom but nothing now works :crying:
I know its not a busy forum now days and most have moved on, but please any assistance to get this beautiful phone going again would be brilliant.
Thanks for the time to read about this dilemma!
ATB
Ok, so if it boots to the LG logo with boot sound it is probably nothing wrong with bootloaders. It is either the system or just something incompatible on the data partition. Of you can make it too recovery try factory reset
Ok I think Ive fixed it!
Did lots of things to try to get to work, but heres roughly the guide.
Used 'rebooter' for Optimus 3d which saved the phone in the 1st instance, it was the only flasher that completed the flash... but remember 1st unplug the phone but micro usb in then remove the battery, then hold the + vol key and insert into the Win XP computer usb, I had already prepared and ran the rebooter.bat file which was waiting for omao device. Once detected keep hold the + key add battery when it says wait 5 secs, dont let the key go, say NO to flash boot but yes to the rest. It will say job done or words to that effect.
Turn on phone holding just the + key to get into download mode. Change the LGE CDMA USB SERIAL PORT to com41 in control panel device manager, refresh search for new hardware to check updated port.
Then use LG Flash to flash V3.0A which worked !
Disconnect the phone remove battery and reinsert, reboot devise, it will boot in TWRP which isnt great but good enough for flash, loaded a Rom onto the sd card and installed the software, after the usual clearing everything like Delvick/Settings etc.
Job done, rebooted and worked, still got TRWP on the boot loading would prefer Clockwork but never mind, had enough of fiddling and just enjoying having my device back
Havent tried a sim in it but might have to to the IMEI fix but hoping not.
Many thanks for your input, I know tech moves on, but there is a wealth on knowledge on these devices and it just seems to be lost in the ether.
Best wishes.
My phone didn't charge during the night as it came unplugged somehow and it got thrown into a bootloop which essentially show the LG boot screen and then restarts again and again in the same fashion. 2 seconds of black screen and 9 seconds of LG screen then bam, restart over. I have booted into the factory reset screen and when I click yes twice, it just reboots right back into the loop. So what I am hoping I can do is flash the rom to an older firmware perhaps. I am not sure what is going on with it, but I can't afford to replace it and I have no warranty.
The issue I am having is I do not see an up-to-date current guide on how to go about flashing to stock rom for the LG stylo H631. The last tutorial I could find was a video from march and that was in a different language so no dice. I have found guides all over the internet from various periods of times that all point in different directions. Some say use LG flashtoolkit. Some say use LGbridge, some say LGup works. None of these are detecting my phone due to it being a bootloop and can't make it into the actual phone. I know how to get to download mode on my phone, but what to use to get the firmware and flash the phone to stock, I do not have a clue.
The last firmware I remembering it having was Lollipop. So overwhelmed with this and lost. Can someone please point me in the right direction on some kind of up-to-date guide with what current software to use and what to do. Thank you as it's much appreciated sooooo much!
UPDATE: Well I just found out that I can get into the downlod mode screen where it says press and hold volume up to continue to download screen, but it doesn't get to the download screen, instead it just goes to reboot back into the same loop from hell. Any ideas guys? From all the research I have done all night, it looks like it could possibly be a battery issue also doesn't help that I know that the battery did completely drain. It seems like buying a new battery may be an answer? Still confused and overwhelmed..
Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?
Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..
Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.
hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please
Been having problems a while now, they've been progressively getting worse. Seemed to happen after an update.
Basically the phone freezes and reboots. Can be anything, unlocking, playing games, opening internet browser, opening gmail. Just frustrating, the phone just freezes, then reboots and loads up. Progressively getting worse and just gets hotter and hotter which seems to throw it off more. With the exception of a Software problem from the update (Damaged O/S and/or Bootloader), I'm starting to think the phone may be damaged. I've dropped it a fair share of times, but it's in a case :cyclops: so shouldn't be too bad
What I've done so far
- Cleared cache via Recovery Mode, this temporarily fixes it, the phone boots up again normally, but randomly freezes and reboots again
- Booted phone in safe mode - same problems
- Factory Restore --> Phone restores, but even when installing the apps again in goes through 3/4 reboots
I've enabled Dev Options and USB Debugging (and also OEM Unlock). If I try flashing with ODIN I just get a SW Check Revision failed message.
When the phone gets stuck in it's boot, it just displays the initial "Samsung Galaxy S7 Android" screen and nothing else, the occasional Samsung loading screen, but that sometimes freezes too. The times when I can get into the recovery mode, I've looked at the last log files, and there's sometimes errors relating to /mnt and a couple of directories, but I don't know enough about the O/S to troubleshoot and sometimes it fails to get into Manual Mode, I'll see if I can get photos of the last log file. The reboot reason is UNKNOWN
I've installed ADB, when the phone is loaded up into Windows, and I use adb devices it shows up. When I go into download mode, it says "List of attached devices" and then shows nothing. So I'm assuming it's a different issue, otherwise it wouldn't work in windows either
Bit stumped now. The phone isn't rooted, I'm not bothered about losing data, since I backed it up the first time I factory restored, so there's nothing valuable on there. I'm just getting tired of factory restoring it, since I don't think that's the problem. I'm thinking either the Factory Restore image is damaged or the phone is.
Any suggestions would be appreciated.
Phone is UK Based on Giff Gaff network. These are the files I'm trying to use to flash it
The option isn't ticked in ODIN (3.14.4) to Wipe Partition either
AP_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship_meta.tar
BL_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship.tar
CP_G930FXXU4ESAE_CL987828_QB11799217_SIGNED.tar
HOME_CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
I read somewhere if I use this file it wipes the data. So haven't tried this
CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
GrabAndSmash said:
Been having problems a while now, they've been progressively getting worse. Seemed to happen after an update.
Basically the phone freezes and reboots. Can be anything, unlocking, playing games, opening internet browser, opening gmail. Just frustrating, the phone just freezes, then reboots and loads up. Progressively getting worse and just gets hotter and hotter which seems to throw it off more. With the exception of a Software problem from the update (Damaged O/S and/or Bootloader), I'm starting to think the phone may be damaged. I've dropped it a fair share of times, but it's in a case :cyclops: so shouldn't be too bad
What I've done so far
- Cleared cache via Recovery Mode, this temporarily fixes it, the phone boots up again normally, but randomly freezes and reboots again
- Booted phone in safe mode - same problems
- Factory Restore --> Phone restores, but even when installing the apps again in goes through 3/4 reboots
I've enabled Dev Options and USB Debugging (and also OEM Unlock). If I try flashing with ODIN I just get a SW Check Revision failed message.
When the phone gets stuck in it's boot, it just displays the initial "Samsung Galaxy S7 Android" screen and nothing else, the occasional Samsung loading screen, but that sometimes freezes too. The times when I can get into the recovery mode, I've looked at the last log files, and there's sometimes errors relating to /mnt and a couple of directories, but I don't know enough about the O/S to troubleshoot and sometimes it fails to get into Manual Mode, I'll see if I can get photos of the last log file. The reboot reason is UNKNOWN
I've installed ADB, when the phone is loaded up into Windows, and I use adb devices it shows up. When I go into download mode, it says "List of attached devices" and then shows nothing. So I'm assuming it's a different issue, otherwise it wouldn't work in windows either
Bit stumped now. The phone isn't rooted, I'm not bothered about losing data, since I backed it up the first time I factory restored, so there's nothing valuable on there. I'm just getting tired of factory restoring it, since I don't think that's the problem. I'm thinking either the Factory Restore image is damaged or the phone is.
Any suggestions would be appreciated.
Phone is UK Based on Giff Gaff network. These are the files I'm trying to use to flash it
The option isn't ticked in ODIN (3.14.4) to Wipe Partition either
AP_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship_meta.tar
BL_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship.tar
CP_G930FXXU4ESAE_CL987828_QB11799217_SIGNED.tar
HOME_CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
I read somewhere if I use this file it wipes the data. So haven't tried this
CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
Click to expand...
Click to collapse
Hello the SW Check error means the firmware your trying to flash is older than the firmware already on device. You can only flash the same or up, never down.
The firmware you've posted is quite old. The unbranded original for United Kingdom you need is BTU. I linked it off Sammobile but if you know how to use Sam Firm tool you can get it much faster direct from Samsung.
If problems persist after flashing this, then yes it's a hardware problem.
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXS8ETC1/327922
cooltt said:
Hello the SW Check error means the firmware your trying to flash is older than the firmware already on device. You can only flash the same or up, never down.
The firmware you've posted is quite old. The unbranded original for United Kingdom you need is BTU. I linked it off Sammobile but if you know how to use Sam Firm tool you can get it much faster direct from Samsung.
If problems persist after flashing this, then yes it's a hardware problem.
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXS8ETC1/327922
Click to expand...
Click to collapse
Thanks,
I've got the SamFirm download tool because I was irritated waiting for the download, I'll try downloading and flashing it.
Should I flash the lot, or just one specific thing?
Also, I used Sam Firm to download the firmware for the phone but using the Auto Method.
What is the "Version" I need to enter based on SamFirm, is it listed somewhere, or is it the phone itself? G930FXX8ETC1 ?
GrabAndSmash said:
Also, I used Sam Firm to download the firmware for the phone but using the Auto Method.
What is the "Version" I need to enter based on SamFirm, is it listed somewhere, or is it the phone itself? G930FXX8ETC1 ?
Click to expand...
Click to collapse
You don't need to specify a version just put in SM-G930F, then BTU in region. It will automatically find the correct firmware for download.
Download, let it do its checks. A zip file with 5 files inside, 2xCSC, only one goes in Odin. CSC_home will keep files and settings on device but can often cause problems. I alsway use just CSC for a clean install. Obviously put the other files where they need to go too.
Sorry yes, flash all files, you'll have a clean new phone.
First boot can take about 5-10 mins, and the updating, erasing screens are normal.
cooltt said:
You don't need to specify a version just put in SM-G930F, then BTU in region. It will automatically find the correct firmware for download.
Download, let it do its checks. A zip file with 5 files inside, 2xCSC, only one goes in Odin. CSC_home will keep files and settings on device but can often cause problems. I alsway use just CSC for a clean install. Obviously put the other files where they need to go too.
Click to expand...
Click to collapse
Thank you, I managed to figure it out, I'm sure it's what I did last time, not sure if it just picked up the wrong version somewhere. IT seems to match the info in your post anyway.
I don't give a toss about the data since I'm over writing it all anyway. Do I still ignore the option to wipe the partition in ODIN, or should that be included to?
GrabAndSmash said:
Thank you, I managed to figure it out, I'm sure it's what I did last time, not sure if it just picked up the wrong version somewhere. IT seems to match the info in your post anyway.
I don't give a toss about the data since I'm over writing it all anyway. Do I still ignore the option to wipe the partition in ODIN, or should that be included to?
Click to expand...
Click to collapse
Leave the default options already ticked in Odin. You don't need to change anything there.
cooltt said:
Leave the default options already ticked in Odin. You don't need to change anything there.
Click to expand...
Click to collapse
Thanks,
Just finished flashing the image now, so going about the restore process to see if it's fixed it or not.
(still think it's buggered though, my phone froze/rebooted even when doing android config)
If needed I'll just keep using it in a semi-working state until I buy a new one and put up with it
EDIT - Just froze / rebooted configuring the main O/S after connecting to google account. New phone time by looks of it
Only other possible thing I can think of is the battery. There were alarms in the log file and the phone does reboot more when it gets hot. Given the phone is 4 years old now, I wonder if the battery is damaged and the phone is having a hissy fit
GrabAndSmash said:
Thanks,
Just finished flashing the image now, so going about the restore process to see if it's fixed it or not.
(still think it's buggered though, my phone froze/rebooted even when doing android config)
If needed I'll just keep using it in a semi-working state until I buy a new one and put up with it
EDIT - Just froze / rebooted configuring the main O/S after connecting to google account. New phone time by looks of it
Click to expand...
Click to collapse
Yeah look like battery overheating making it reboot
cooltt said:
Yeah look like battery overheating making it reboot
Click to expand...
Click to collapse
I'll give it a try for now, I've got the correct files for flashing it at least this time thanks, I''ll try replacing the battery in the future, and if I find out it fixes the problems I'll update the post. Or if I figure out what's causing it
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!