Related
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Same thing here. Flashed wrong ROM via TWRP.
As a result, immediate loop (repetitive vibration, led blinking red) when connected via USB. No recovery access. Only fastboot access (blue led).
Locked bootloader.
Flashtool:
- tried flashing kernel.sin extracted from a stock ftf - no good (locked bootloader, unlocking requires flashboot which is not accessible).
- tried flashing system.sin extracted from a stock ftf - no good, flashtool says
INFO - Flashing selected system
and immediately after that
INFO - Please check the log before rebooting into system
So it clearly doesn't do anything. Any other approaches to try?
Tech core said:
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
Click to expand...
Click to collapse
Flashmode does not work, it starts cycling immediately.
Tech core said:
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
Click to expand...
Click to collapse
Yes, certainly.
Tech core said:
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or at least take a rest for what the heck is going on with your phone
Click to expand...
Click to collapse
Can't flash anything, so can't try it.
Tech core said:
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Click to expand...
Click to collapse
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
TheControlled said:
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
Click to expand...
Click to collapse
I didnt get your comment brief it to me
Hello guys,
It is my first time yesterday to flash and root my Xperia Z5 since the camera app always says that it is currently in use.
I used this guide by sceryavuz . And it turned out great, I have used my phone for a day without any errors or problems encountered. But the thing is, I still cannot use the camera app and it has the same currently used by other application message so I decided to downgrade it to Marshmallow this morning. So I went to the same routine, downloaded an FTF file and loaded it into the flashtool.
After clicking Flash device in the flashtool and waited for the flashmode, I connected and pressed the volume down button of my phone but the flashtool is not reading and recognizing my phone. So I decided to open the TWRP and assumed that factory resetting my phone will do the work and it turns out that it just removed the /system folder and now I have a bigger problem with my phone.
When I'm connecting in flashmode the LED is turning to red, green, then will turn off, and then will do the same cycle if left unattended.
Could you guys please help me out with this. You'll be greatly appreciated guys. Thanks!
My phone is E6653 Xperia Z5
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
ofmoll said:
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
Click to expand...
Click to collapse
Hi ofmoll,
I'm sorry for the very late response, I had an internet connection issue this past week. I have tried your suggestion by using Carbon Rom, it works perfectly fine but I have one problem. It is not charging and the battery keeps saying that it is on 100% even if it is not. I'm trying to reflash other ROMs and I'll get back to you as soon as I finish flashing. Happy new year! Thanks!
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Toshiiiiiiii said:
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Click to expand...
Click to collapse
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
ofmoll said:
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
Click to expand...
Click to collapse
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Toshiiiiiiii said:
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Click to expand...
Click to collapse
As said, first of all try what I said. It nothing of that solves it, I suggest you 3 options
1. Either go stock, try using XPeria Companion, but I think since you flashed custom it doesn't work, at least for me. For Companion you'll need to relock bootloader. Or go stock by flashing a stock rom via TWRP. Note that after flashing a custom rom you'll never go back to the "real" stock if you don't have a backup, but you can always flash a stock rom.
2. You can also try to reflash the rom and see if that works.
3. Download a Custom kernel, then go to TWRP, wipe everything, then first of all flash the Kernel (remember to ensure that's a kernel for your device). Then reflash the ROM. This could look stupid because the ROM comes with a built-in kernel itself, but it solved an issue I had with random reboots. I didn't read this anywhere, I tried and for me it solved a problem I had which everybody was telling me that was caused by hardware, then it came out to be a Kernel issue. Try to if you want.
Try what I said before as well. This is all I know
Cheers
Edit: I forgot to tell you that PC Companion won't recognize your phone if it's running a customROM. Use Android File Transfer instead. You also need to check "use usb to transfer files" on the notifications pannel. Enable USB debugging as well, I guess you know how to do it, in case: you need to go to "about phone" in settings, hit 8 times Build Number, then the developer options should appear and check Android Debugging. That's it.
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!