Hi guys,
Sorry for the incoming wall of text but this issue im having is massive and after doing a buttload of research im still no closer to anything.
I have the international Galaxy S4 (GT-I9505). So everything started when my phone was running CM 10.2 then i did an OTA update to I believe it was 10.3. My phone would boot and the OS would start but I kept getting an error message saying some android system program wasnt working and basically made it unusable. So i decided to go back to CM10.2. After much trouble, I finally managed to get back to CM10.2 but I decided i was sick and tired with CM and wanted to go back to Samsung Stock firmware. This is where all the trouble began and its been a nightmare so far. I had TWRP 2.6.0.0 flashed too. I downloaded the TGY-I9505ZHUEMK2-20131122112513.zip file from samsung-updates and moved it onto my phone and wanted to install the .zip from TWRP. I kept getting an error message so I installed it through ODIN instead. Ok, so it worked from there and all was fine and dandy until I couldnt get the wifi to turn on, as in, it wouldnt even toggle on not that it wasnt connecting but that it physically wouldnt turn on. I figured I should do an OTA update incase it was a software problem. Alas, I got the error message saying that I cant because my phone was modified. Once again, I reinstalled the firmware through ODIN 1.85 and this time I didnt root it but i still got the same error message. I then used Triangle Away to try to reset the flash counter incase that would help. No matter how many times i did, the counter would always stay at 7. So after hours of research I stumbled upon an article about the infamous KNOX flag implemented in 4.3 and decided to see if I had triggered it. So I checked under download mode but I couldnt see anything relating to it but I did see 0x30. I forget what it was for. In the end I found this thread ( http://forum.xda-developers.com/showthread.php?t=2444671 ) and downloaded the PIT file and the pre rooted firmware linked in that thread and installed them and all went smoothly. The WiFi still wont turn on but triangle away was able to reset the flash counter to 0 this time. Now when I attempt to turn on the WiFi i get a notification saying 'The device has detected an application attempting unpermitted actions and has stopped loading. To protect your device, it is recommended you reboot'. I tried rebooting but that didnt help. I tried removing the battery and putting it back but that didnt work either. I tried holding down on the notification and clearing cache and then closing the app but that didnt help. The application in question is called : SEandroid (version 1.0). When I scroll to the bottom of the permissions list I did see something interesting that could have something to do with this. One of the permissions was labeled Qualcomm WiFi p2p.
The SSN is -I9505GSMH
Model Number: GT-I9505
Android vers: 4.2.2
Baseband Version: I9505ZHUBMF4
Kernel Version: 3.4.0-626292
[email protected]#1
Tue May 14 19:17:56 KST2013
Build no.: JDQ39.I9505ZHUAME3
SELinux Status: Permissive
Device Status shows Custom.
Please guys, any help would be appreciated. I'm about to throw this dang phone into the ninth circle of hell.
EDIT:
Wwll guys, Im feeling like a special ed guy now. I found out about the WIFI fix and after flashing that with ODIN, it worked all dandy now. My second question would be, if I were to put TWRP back on, would that screw with anyhting?
hkhouli said:
Hi guys,
Sorry for the incoming wall of text but this issue im having is massive and after doing a buttload of research im still no closer to anything.
I have the international Galaxy S4 (GT-I9505). So everything started when my phone was running CM 10.2 then i did an OTA update to I believe it was 10.3. My phone would boot and the OS would start but I kept getting an error message saying some android system program wasnt working and basically made it unusable. So i decided to go back to CM10.2. After much trouble, I finally managed to get back to CM10.2 but I decided i was sick and tired with CM and wanted to go back to Samsung Stock firmware. This is where all the trouble began and its been a nightmare so far. I had TWRP 2.6.0.0 flashed too. I downloaded the TGY-I9505ZHUEMK2-20131122112513.zip file from samsung-updates and moved it onto my phone and wanted to install the .zip from TWRP. I kept getting an error message so I installed it through ODIN instead. Ok, so it worked from there and all was fine and dandy until I couldnt get the wifi to turn on, as in, it wouldnt even toggle on not that it wasnt connecting but that it physically wouldnt turn on. I figured I should do an OTA update incase it was a software problem. Alas, I got the error message saying that I cant because my phone was modified. Once again, I reinstalled the firmware through ODIN 1.85 and this time I didnt root it but i still got the same error message. I then used Triangle Away to try to reset the flash counter incase that would help. No matter how many times i did, the counter would always stay at 7. So after hours of research I stumbled upon an article about the infamous KNOX flag implemented in 4.3 and decided to see if I had triggered it. So I checked under download mode but I couldnt see anything relating to it but I did see 0x30. I forget what it was for. In the end I found this thread ( http://forum.xda-developers.com/showthread.php?t=2444671 ) and downloaded the PIT file and the pre rooted firmware linked in that thread and installed them and all went smoothly. The WiFi still wont turn on but triangle away was able to reset the flash counter to 0 this time. Now when I attempt to turn on the WiFi i get a notification saying 'The device has detected an application attempting unpermitted actions and has stopped loading. To protect your device, it is recommended you reboot'. I tried rebooting but that didnt help. I tried removing the battery and putting it back but that didnt work either. I tried holding down on the notification and clearing cache and then closing the app but that didnt help. The application in question is called : SEandroid (version 1.0). When I scroll to the bottom of the permissions list I did see something interesting that could have something to do with this. One of the permissions was labeled Qualcomm WiFi p2p.
The SSN is -I9505GSMH
Model Number: GT-I9505
Android vers: 4.2.2
Baseband Version: I9505ZHUBMF4
Kernel Version: 3.4.0-626292
[email protected]#1
Tue May 14 19:17:56 KST2013
Build no.: JDQ39.I9505ZHUAME3
SELinux Status: Permissive
Device Status shows Custom.
Please guys, any help would be appreciated. I'm about to throw this dang phone into the ninth circle of hell.
EDIT:
Wwll guys, Im feeling like a special ed guy now. I found out about the WIFI fix and after flashing that with ODIN, it worked all dandy now. My second question would be, if I were to put TWRP back on, would that screw with anyhting?
Click to expand...
Click to collapse
Im having the same problem as you but wifi fix doesn't seem to do anything.
after i run it i get a permission error.
can you give me a bit more details on which wifi fix you used and how you ran it.
xgutterratx said:
Im having the same problem as you but wifi fix doesn't seem to do anything.
after i run it i get a permission error.
can you give me a bit more details on which wifi fix you used and how you ran it.
Click to expand...
Click to collapse
Yes please send me the wifi fix too! having same issue and I'm at a loss. Thanks!
Related
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..
KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..
KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday
And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was
My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated
Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.
Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:
hello everyone
phone: i9505
I few weeks ago i rooted my phone (no problem) made a back up using rom manager on sdcard.
I decided to restore my phone with the back up i had made. Once it had finished restoring, I rebooted phone, go to unlock the screen and i am spammed with messages like: unfortunately process com.google.process.gapps has stopped and so on. Could not use phone because there was so many messages coming up!
my friend advised me to re-root it so i did, the problem didnt go away......
searched google found no answer to my problem
I thought un-rooting will solve the problem so I downloaded latest stock uk firmware (4.4.2) from sammobile, ran odin, put MD5 file in PDA, successfully un-rooted but when i turn my phone on now there is some writing on the top left corner it says (its pretty hard to make out it goes so fast):
REBOOT MODE = 0X684E39A6
POWER ON REASON = 0X1 (key power on)
CABLE: 0X00
DEBUG LEVEL MID
BOARD REV: 11
MSM CHIP REV 2
MSM HW ID: 0X71B0E1
BOOTLOADER VERSION: I9585XXEGNG8
BOOTLOADER AP SWAEV: 4
SPEED BIN: 2
ACPU PVS:2
SERIAL NUM:0X07FF9243
when i put my phone in dowload mode it says all this^ as well
after unrooting i went to setting and did a factory reset
ive tried rooting again, then unrooting but my phone doesnt seem fully unrooted? it says im on official, i also noticed i cant place widgets on screen
i tried google search but could not find an answer, mainly because i dont know what to search for but i know somethings not right
i just want my phone back to how it was, for now
if you need anymore info please let me know!
thanks in advanced!
Have you tried this guide to installing stock? I used this and it worked fine.
http://forum.xda-developers.com/showthread.php?t=2265477
There's a bit at the bottom about bootloops, I don't remember if I had one but I know I had to flash it anyway due to a problem I had after flashing the stock rom, so to be safe you should probably flash that after stock is flashed on as well.
lichking21st said:
Have you tried this guide to installing stock? I used this and it worked fine.
http://forum.xda-developers.com/showthread.php?t=2265477
There's a bit at the bottom about bootloops, I don't remember if I had one but I know I had to flash it anyway due to a problem I had after flashing the stock rom, so to be safe you should probably flash that after stock is flashed on as well.
Click to expand...
Click to collapse
thanks for the reply
ill try this and seee how it goes! i hope it gets it sorted
Galaxy S4 - i337m - Android 4.3
Okay, so here's my problem.
Today in the morning after I woke up, I checked my phone and it said it had downloaded a software update. It was just a complimentary update for 4.3, it said bug fixing, etc. in details. I clicked accept and the installation started.
After this, all crap started to happen.
The Wi-Fi NEVER worked again, everytime I clicked the Wi-Fi widget in the notification bar, it turned green and immediately switched back to gray. It also didn't work when trying to turn Wi-FI on from the settings menu.
I tried everything, the battery pulling, the thing of disabling the Wi-Fi energy save, and nothing worked. It all pointed to a factory reset.
So I did all my backups (My S4 was rooted), and finally made the factory reset.
After this finished, I did all the starting configuration of the S4 (like when it was brand-new). Then, I tried to turn on Wi-Fi.
Surprise, surprise. DIDN'T WORK.
I'm so desperate right now, I don't know what to do.
I'm currently downloading 4.4.2 to flash it via Odin, and see if this works.
Any help, please?
Flashing the 4.4.2 ROM you're downloading now should definitely fix the problem. I know that in some instances, us I9505 owners have to flash a stock ROM twice through Odin before the modem will function. It sounds like your software update broke the modem in this fashion, which is why the ROM install you're planning should fix it. Be aware however that installing KitKat will give you Knox if you don't already have it.
Strephon Alkhalikoi said:
Flashing the 4.4.2 ROM you're downloading now should definitely fix the problem. I know that in some instances, us I9505 owners have to flash a stock ROM twice through Odin before the modem will function. It sounds like your software update broke the modem in this fashion, which is why the ROM install you're planning should fix it. Be aware however that installing KitKat will give you Knox if you don't already have it.
Click to expand...
Click to collapse
Fine. Right at this moment I'm installing 4.4.2
Hope this works.
I'll tell you what happens.
Morning Guys,
Ive had all sorts of fun and games with this damn G950F every time i root it it throws up a problem.
It had just gotten to unlock time for the third time, but started throwing up 'SystemUI has stopped working' errors when i hit the 'app list' button. Didnt think much of it, and went to root. SuperSU took and was granting root permissions but would not update the binary. I fell asleep at some stage and didnt go back to it until this morning.
Went to use the phone this morning and its reset itself and thrown up a big red message about only having stock binaries installed. Queue about 7 hours of not being able to resurrect a phone that had spat out TWRP and now appeared to have a locked down bootloader again. Finally realised i could flash the stock XSA rom without the bootloader and resurrected the phone.
Fired it up, and its no longer detecting the SIM card, and *all* of the Mobile Network settings are missing. Cant find an answer to this anywhere. Im hoping like hell its a software issue (another non answered question i have is that i get weird ass settings options with strange labels and duplicate entries and options that crash the settings app after some re-flashes.
Anyway.. wat do plez?
Have tried - Factory resets and cache wipes both in UI and recovery. Reflashing AP, CP, CSC and/or CSC_HOME. Cant flash BL as its currently 'prenormal'. Keep reading the 'download mode, start odin, quickly hit buttons' trick but have never gotten it to work, and ill try it again right now to triple check but im 99.9999% sure it wont let me re-flash Nougat on it for the same reason.
Cheers in advance.
UPDATE - So it looks like something has accidentally'd the IMEI. Now looking for non root non bootloader methods to bring it back. Looks like thats my problem.
Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha