Related
Morning all,
I apologise if this is in the wrong section but I am new to the forum and in a bit of pickle.
Around a week ago I rooted my lovely new note 3 to hopefully one day install some nice new ROM to get rid of the horrid touch wiz and actually see the full potential of the phones power. However, for some silly reason while I was using titanium backup on my phone I thought it would be a good idea to uninstall touch wiz thinking it would magically go back to basic android however it didn't. It is completely broken now, woops. The first issue I had was it would boot up and stick to the Samsung logo and just glow so I thought it would be an idea to install stock ROM via ODIN to try and revert it back to normal. Once I downloaded the correct stock ROM it was uploading through download mode however at the last minute it failed with a ext4 error which I think it means it's bricked? Not sure, completely new to this. I am now a bit stuck as I am not 100% sure what to do next.
The phone will only boot into either the firmware upgrade has encountered an issue, basically Odin mode or download mode. I have tried recovering it through kies however it cant connect to it. It knows it is there as it will start searching for it when it's connected however says it can't find it. It wont boot into recovery mode.
My phone is a note 3 SN SN-9005. The system status is custom, reactivation lock is off, Knox kernel lock 0x0, Knox warranty void 0x1 and write protection is enabled.
Obviously I would like to get the phone back to normal, I don't care if it has to be completely wiped and brought back to normal I would like it to just work. I've been an complete idiot and fiddled with something I'm not 100% sure on and I would like to not have a 600 quid paper weight hehe.
I have tried putting stock firmware back on but it always fails with an ext4 error.
I will greatly appreciate any help or feedback.
I have recieved some good feedback on this so far however I am unable to get it fixed properly.
apdnote said:
Morning all,
I apologise if this is in the wrong section but I am new to the forum and in a bit of pickle.
Around a week ago I rooted my lovely new note 3 to hopefully one day install some nice new ROM to get rid of the horrid touch wiz and actually see the full potential of the phones power. However, for some silly reason while I was using titanium backup on my phone I thought it would be a good idea to uninstall touch wiz thinking it would magically go back to basic android however it didn't. It is completely broken now, woops. The first issue I had was it would boot up and stick to the Samsung logo and just glow so I thought it would be an idea to install stock ROM via ODIN to try and revert it back to normal. Once I downloaded the correct stock ROM it was uploading through download mode however at the last minute it failed with a ext4 error which I think it means it's bricked? Not sure, completely new to this. I am now a bit stuck as I am not 100% sure what to do next.
The phone will only boot into either the firmware upgrade has encountered an issue, basically Odin mode or download mode. I have tried recovering it through kies however it cant connect to it. It knows it is there as it will start searching for it when it's connected however says it can't find it. It wont boot into recovery mode.
My phone is a note 3 SN SN-9005. The system status is custom, reactivation lock is off, Knox kernel lock 0x0, Knox warranty void 0x1 and write protection is enabled.
Obviously I would like to get the phone back to normal, I don't care if it has to be completely wiped and brought back to normal I would like it to just work. I've been an complete idiot and fiddled with something I'm not 100% sure on and I would like to not have a 600 quid paper weight hehe.
I have tried putting stock firmware back on but it always fails with an ext4 error.
I will greatly appreciate any help or feedback.
I have recieved some good feedback on this so far however I am unable to get it fixed properly.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=_sMnC6UkJBI
this is a vid on how to unroot i know its not what you want but dose show you how to get back to stock with odin
Hi,
I've been do many flash last 24 hours on my Galaxy S4(Model SGH-I337M, Telus). Initialy, i've the factory stock rom, rooted. So, yesterday, i've decided to install Cyanogen mods nightly on my phone. Not the first time i've been used it on my phone. No problem before. So, this night, after a friend show me the release canditate release seem to be more stable, i've been try to put it on my phone. So, accidentaly wipe all the data on my phone. When i'm back home, i've put again the samsung original rom from my operator(4.2.2), found here, on the website, whit odin. All completed succefully, but i've noticed that the wifi won't turn on after the flash, and no sound from the speaker. So, i've put Cyanogen nigthlies again to test if it rom relative, but same issues here, no sound, but the wifi was working. The phone was very instable, so. Then, finaly, put the original rom again, without any rooting. Stuck on samsung logo, that i've finaly got fixed by clear the data and cache. But, no sound, and no wifi. Instable too.
Precision about phone: Unlocked whit the service mode(work), and enabled AWS whit a software and file(tutorial found here)
My question is: Anything else i can do to make my phone work fine again, and does it's possible to make the phone totaly stock? When i boot up, i've noticed that the phone, whit all rom i've try, said on samsung logo: Kernel is not sendroid enfonced, warranty status: kernel, so i can't go to return my phone on warranty whit that. How i can erase that line, and make my phone seem to be no modified?
Just to specify, it's not the first time i flash a phone. Do many flash, whit galaxy s2, s3 and s4, and sure, mine. Got try Cyanogen, stock, know how Odin work and all, try many rom, and before today, never has any problem to do turn back, but now, it's seem to be impossible.
Thank you very much for your help, very appreciated!
I would flash the stock firmware with odin again. After flashing do a factory reset in the stock recovery.
jd1639 said:
I would flash the stock firmware with odin again. After flashing do a factory reset in the stock recovery.
Click to expand...
Click to collapse
I've just try this. Flash the stock rom whit odin, and factory reset on original recovery after. Same, no wifi, no any sound.
Just see yesterday, when i'm flashing, i'm flashing on the bootloader in odin(whit the tar for the stock rom). Today, correct this by flash on the pda section, still not work. Found here on the forum the stock bootloader, rom, csc, and modem, but when i do this whit odin, odin said fail.
Thank very much, i think my phone is dead, and nothing to do to exchange it on warranty.
I think Kies has an emergency firmware recovery mode.... maybe that'll work.
Found a nice guide here: http://forum.xda-developers.com/showthread.php?t=2261153
saj222 said:
I think Kies has an emergency firmware recovery mode.... maybe that'll work.
Found a nice guide here: http://forum.xda-developers.com/showthread.php?t=2261153
Click to expand...
Click to collapse
Just try this. Kies is the worst software i've ever see. The software completely freeze random. When i go to the emergency menu, never, kies recognize my phone here. I've tried to plug my phone, no recognized. Tried without plug it, no recognized. When i plug it, kies said connection in progress, and can stay here 30 min.
I'm a idea of what is my problem. Before do install of cyanogen, i've been applied the samsung official 4.3 update, whit knox. And, according to what i read on many forum, knox is not ereasable, So, it's completely freeze my phone, and nothing to do.
Anyone have the factory telus bootloader and other factory stock items because i want to put it stock.
Thank.
Finally get problems fixed by take the TELUS stock 4.3 ROM and flash it whit Odin. After, can flash cyanogen nightlies again and the phone work well again.
Whit the stock ROM, didn't see any line on the Samsung boot logo that i've rooted. After root this appear again. Knox regardless of ROM installed said 0x1.
If anyone have a fix to put it again 0x0 very appreciated otherwise the phone work fine and thank you very much for your help.
dardares said:
Just try this. Kies is the worst software i've ever see. The software completely freeze random. When i go to the emergency menu, never, kies recognize my phone here. I've tried to plug my phone, no recognized. Tried without plug it, no recognized. When i plug it, kies said connection in progress, and can stay here 30 min.
I'm a idea of what is my problem. Before do install of cyanogen, i've been applied the samsung official 4.3 update, whit knox. And, according to what i read on many forum, knox is not ereasable, So, it's completely freeze my phone, and nothing to do.
Anyone have the factory telus bootloader and other factory stock items because i want to put it stock.
Thank.
Click to expand...
Click to collapse
I've seen worse software, it's no better or worse than iTunes.
Sent from my SGH-I337M using Tapatalk
dardares said:
Finally get problems fixed by take the TELUS stock 4.3 ROM and flash it whit Odin. After, can flash cyanogen nightlies again and the phone work well again.
Whit the stock ROM, didn't see any line on the Samsung boot logo that i've rooted. After root this appear again. Knox regardless of ROM installed said 0x1.
If anyone have a fix to put it again 0x0 very appreciated otherwise the phone work fine and thank you very much for your help.
Click to expand...
Click to collapse
can u plz give me link for the flash file u just flash
i have same problem here after i flash with 4.2.2 no sound and phone freez all time
i like to flash 4.3 so i can fix my phone
thanks
mps5566 said:
can u plz give me link for the flash file u just flash
i have same problem here after i flash with 4.2.2 no sound and phone freez all time
i like to flash 4.3 so i can fix my phone
thanks
Click to expand...
Click to collapse
This is the link i've found whit all the factory stock operator ROM. This is what rescue me.
http://forum.xda-developers.com/showthread.php?t=2269304
@Spacemonkie4207 never my itune was freeze, and i can do basic operation like transfer music or create playlist without any problem. My kies stay on connection in progress, and turn, turn, turn, but never connect. And when it connect, only one operation, and kies completely freeze, stop responding, need to close it, and open it again. Tried many cable, usb cable, reinstalling software, two other computer, but nothing to do.
I recovered back to stock from custom to 4.3 however if you do so, depending on carrier you could lose root and the ability to install custom recovery.
I would revert back to 4.2.2 (as it's knox free) go to samsungupdates (google it) and pull the 4.2.2 for your region and carrier. flash with odin 3.9
you'll lose root, but you can always perform again as long as not on 4.3 (with 4.3 u can still root if you remove all the knox stuff, u just lose warranty).
Az
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!
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:
Hi guys
I need some quick help identifying what happened to my S4. It's not bricked by the way, it's just some weird debugging mode which became enabled.
I have just sold it on eBay, and therefore I performed a standard factory reset followed instantly by a standard ODIN flash of the official latest firmware to remove root (which is something I've done many times on this phone without an issue).
However this time, since I did it, everytime I turn the phone on, just before the standard Samsung Galaxy S4 logo appears, I get a strange flashing screen which displays some technical details on the phone (different to the one I used to have when running a custom kernel) which include: serial number, Knox status, power on reason, some CPU details and in particular, a line saying debug mode level: medium. I have never came across it so I tried removing the battery and re-flashing the software, neither of which have helped.
I would like to find out if anyone had come across this and if so, how could this be revered back as I need to ship the phone to the buyer.
Attached is the photo I managed to capture with my DSLR which shows more detail... Please help.
Thanks a lot
Regards
Please can someone take a look at this?
mateuszd said:
Please can someone take a look at this?
Click to expand...
Click to collapse
mateuszd said:
Please can someone take a look at this?
Click to expand...
Click to collapse
Go to recovery and make a factory reset, when the galaxy s4 logo shows up remove the battery immediately, wait 5 seconds then go to download mode and flash the firmware, after the device reboots make a factory reset again
Will try that, what I did so far is flashing the latest Black Edition rom which removed the issue and then flashing back the latest normal ROM and the issue came back straight away. It's like a weird bootloader it comes with.
I'm downloading an older ROM from March as this is the one I flashed a while ago and had no problems with.
Fixed it, just downloaded I9505XXUFNB8 which is from March and flashed it, then, updated over OTA. It's now on latest version without the weird bootscreen issue.
What's strange is that it was an official (latest) build downloaded from SamMobile and later downloaded again though SamFirm tool and both produced same behaviour yet upgrading to it though OTA did not cause the issue.
Thanks