Related
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
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:
I have tried everything I can possibly think of in a short period of time, and need an answer in a hurry. The phone (Verizon Samsung Galaxy Note 3 N-900V) was rooted back when kitkat was the main OS using geohot's towelroot (or possibly kingo root I can't remember which i used after I got the phone and upgraded from ICS). I have 2 of these exact same phones, used the exact same rooting method, and unrooted by uninstalling the superuser app, rebooted, and installed the OTA update to lolipop. My phone works fine, (the one I'm typing from) however, my other phone decided to take a dump. It's a software bug between the samsung firmware and the new lolipop OS. It was working for several months, then all the sudden it wouldn't recognize/register the APN. Now it doesn't see anything just about with the phone. Not even the IMEI from the phones serial number. The sim card has been replaced twice and has worked for a matter of a few hours, however, upon restarting the phone, it goes back to no service, and nothing is registered or recognized. I reflashed the phone with the stock 5.0 Lolipop using Odin several times to no avail. My phone (one I'm using now) once did this months ago, and I was able to access the service menu and reregister the SIM card and phone has worked fine since. With this other phone, I can't get into the service menu at all because nothing is registering. So, after reflashing 4 or 5 times, factory reseting from both the OS and from recovery booting, it still has the same issue. Here is my question. It used to be when I reflashed, the custom padlock would disappear. I'm getting a new phone tomorrow, and I need to get rid of the custom padlock before I return the old phone. I can use Odin, or whatever but it has to be something, I can do while it stays stock. The knox counter has not been tripped, and the flash counter is not tripped nor showing anything on the download mode. Everything lools, and feels stock, except that custom padlock. Is there a way to get rid of that custom padlock unrooted, by reflashing? I even used a pit file to repartition, but that didn't work either. Need help A.S.A.P.!
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Hard Brick
xxperrin said:
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Click to expand...
Click to collapse
You thinking maybe a NAND erase?
Hard Brick
I've thought about flashing the wrong rom too but dunno if that will work 100%. I either need to fix it, or make it 100% unrecoverable. Any advice?
HI
My friend need help with his NOTE 3 SM-N9005 LTE
Phone wont boot anymore. It only bootloops. I installed stock rom 2 times with ODIN and still phone stuck on recovery booting and then reboots only.
Then i flashed TWRP with ODIN and cleared everything on phone and wiped then installed MagMa_NX_UX9.7_Premium_XDA ROM
and everything sucess and seems fine, but when comes to boot it only stucks at Note 3 Splash some time and reboots.
I wonder if his partitions are ****ed up or something? ODIN dont show any errors neither.
HE said that this came after some update or something but i dont know if he tells the truth about what really happened
with the phone.
Any way to reparition whole phone and maybe update bootloader or something?
I forgot to mention that he replaced the LCD with new one but could it realy be issue? Because everything works in recovery and i can see Samsung Note splash screen.
I manage to fix it.
I flashed EUR version of STOCK ROM instead of NEE and phone finnaly booted. I dont know what the heck problem was.
Hi ladies/gents,
I've just flashed my Samsung S5 (SM-G900F) with the latest UK BTU stock firmware from sammobile.com for my unlocked device (I've used SIM cards in the device in 3 different countries fine).
I reset the device into Boot mode, cleared the cache and factory reset, then boot the phone into download mode.
Using Odin I flashed the .tar.md5 file under the "AP" section of Odin with auto-reboot & F.Reset Time checked , the process was a success (according to Odin), and then when the phone restart: nothing but being stuck on the Samsung S5 boot flashing boot screen.
I've tried clearing the cache and factory resetting again, as well as installing the AP file again, to no joy.
I'm pretty dumbfounded by this as it seems this is the most straight forward and "safe" flashing to do on the device, yet now I seem to have bricked the phone in doing so.
Most of the advice I can find on the internet to fix the boot loop issue suggests doing the exact process I have just ran through, so I'm pretty close to calling it quits and looking at another brand of smartphone.
If anyone has any advice on how I can try and recovery the use of my phone, I'd be most grateful.
Thanks.
Okay guys/gals in the time it took me to feel sorry for myself and get desperate enough to create a post here the phone seems to have just turned on and working fine
I did restart the phone a bunch of times, but it seems just leaving it 20-30+ minutes does the trick.
Patience is a virtue!
Hi
I am having exactly the same issue with a G900I - tried everything!
Any advice??