Database Users

[Q] Major issue with Australian SM-9005, help!

Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.

zuuus said:
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
Click to expand...
Click to collapse
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.

ultramag69 said:
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
Click to expand...
Click to collapse
Hey mate, last version of firmware was the Stock Telstra SM-N9005 / TEL ROM I found on www . sammobile . com/firmwares/2/
I have tried at least 10 different ROMs with no luck, every single one does the same thing.
I did send it off to Telstra to try for a repair, they sent it back to me unrepaired due to nothing to do with the software but a 1/4mm scratch my keys made in the chrome plastic around the edge with the words "unable to be repaired due to physical damage" with a little sticker pointing to the scratch. ****ing ridiculous if you ask me.
Honestly I don't know all that much to do with the modems and csc's so it might be that causing my problems but I have tried a bunch of different ones without any change.
At my wits end here, phone is just over 30 days old and I can't use the damn thing.

try odin back to stock, then use kies to "emergency firmware restoore" Kies can be a life saver in some situation, make sure you use beta 3 version

[Q] Messed up phone

Hi guys.
So I got a problem. Actually a buch of them, but first things first. So back in March I updated my i9505 to 5.0.1 with Odin and stuff. Later on I decided to root my phone and install some nightly CM12. Everything went pretty well until some weeks ago something started to happen. I got notifications about updates for Android but I wouldn't care as my phone was well, at that time, working extremely well. But then things got really messed up. At first the camera - most of the pictures weren't saving. But that was okay I guess I heard about problems with camera. Though it wasn't the only thing that was messing up. Phone got reeaaaallly slow, lags, apps started to freeze and most important, random reboots and the sound wasn't working. No one could hear me when I was talking with them and I couldn't hear them. That was the most important issue, because everything was fine and then, using the phone casually, the sound went out. I had to restart the phone. With the random reboots 20 times a day, and my intended reboots because of the sound issue, you can tell how mad I was. So I intalled some ROM, Touchwiz 5.0.2 probably (can't remember if it was 5.0.1 or 2, sorry!) with Galaxy S6 features through TWRP (installed a zip). It was even worse. A lot more random reboots, camera not working at all, apps freezing constantly after using them for couple seconds. Can't use my phone anymore, it's unusuable.
No idea what might be the cause. Might be Kernel? You guys have anything to help? Also installed a clean ROM through odin, but it's the same. I lost my root and TWRP recovery.

Well it sounds more like a hardware problem.
You wiped everything before flashing? That is the /system partion and the /data partition.
You can try flashing a stock rom with re-partition and .pit file ( I assume you are familiair how Odin works).
or
Flash TWRP
Perform a full wipe (/data and /system).
Flash a rom you want.
If the problems are still there it's hardware related.

Lennyz1988 said:
Well it sounds more like a hardware problem.
You wiped everything before flashing? That is the /system partion and the /data partition.
You can try flashing a stock rom with re-partition and .pit file ( I assume you are familiair how Odin works).
or
Flash TWRP
Perform a full wipe (/data and /system).
Flash a rom you want.
If the problems are still there it's hardware related.
Click to expand...
Click to collapse
Yes, of course I wiped everything. Common thing to do when installing ROMs.
Weird thing now. So I installed official kernel for the device, via Odin, and then flashed the phone via Odin too with stock ROM. Still don't know much about kernels and stuff, was it necessary to flash that kernel and then flashing ROM, or was only flashing the ROM enough because the kernel comes with it?
Though I gotta say it's kinda better. Sound doesn't just turn off, but there are still a lot random reboots and sometimes the device won't boot up at all. And it's pretty much that now. Most of the apps are working ok, they freeze sometimes though. Oh and rear camera and NFC aren't working. I probably broke them because of the falls the device experienced with me these past few days.
Can you elaborate on Re-partition and *.pit file thing?

[solved] Phone is acting weird ... random reboots shortly after boot

Hi there,
I started this topic because I am out of options and I don't know what to do at this point.
My Phone is a XT1562 DualSim.
I recently flashed http://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690 and I also installed "MODEM" (MPD24.107-70) from page 1, but not right away.
First I wiped everything expect "internal storage". The phone booted but it restarted during boot (which might be okay) but then it rebooted again during boot. The boot process finally finished and I got to the screen "Android is starting - Optimising app x of y." The phone rebooted even during that process and that is definitely not normal I think. So after a couple of reboots android did finally optimise all apps but the phone did still reboot withing the first 30 seconds after it was booted.
From here I did a lot of testing and doing. These are my findings:
- When I set phone to flight mode / airplane mode it does NOT reboot... Hurray!
- When I flash another ROM (Official CM 13, http://forum.xda-developers.com/mot...m-cyanogenmod-13-preview-moto-x-play-t3252255) the phone runs like a charm, NO reboots whatsoever.
- - But as soon as I flash gapps and the phone is booted, I get the reboots again (usually within the first 30 seconds).
- - Again setting the phone to flight mode prevents itself from rebooting.
- - Apparently it doesn't matter what version of gapps I flash. I even tested the light version (ARM, 6.0, Pico, from http://opengapps.org/). It still reboots. I also tried gapps mini and stock.
Oh and I don't think its MODEM (mentioned above) related, because I faced these problems already before I installed / updated the MODEM. Well I thought its MODEM related, that's why I went back to MODEM stock version MPD24.107-52 but that did't help either. I should mention that I am not sure if I had MPD24.107-52 installed originally but spetrum (the rom developer) pointed me to that version: http://forum.xda-developers.com/showpost.php?p=69129552
I also restored my working TWRP backup from an android I used for month and guess what, yep, reboots
brrrrr this is frustrating
I never experienced that before and frankly I am out of ideas.
Anything is welcome and appreciated
Thank you

If nothing helps reflashing the whole firmware is always an option

minimale_ldz said:
If nothing helps reflashing the whole firmware is always an option
Click to expand...
Click to collapse
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?

I always go back to flashing stock rom with rsdlite whenever things went wrong and I can't solve it by flashing small fixes.

rancor187 said:
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
Click to expand...
Click to collapse
I mean full stock firmware you flash with fastboot or RSD. Roms are usually only system + kernel, so not very helpful in your case

Guys! Good news. I did go back to stock firmware and from there to official CM13. Of course I had to root and install TWRP again but it was worth it.
I lost a few days spending my time with it but I'm glad its all good now thanks to you.

S6 Edge+ G928F dead? NEED HELP!

[My phone is already repaired by Samsung under warranty, my internal storage was broken so they replaced the motherboard. There is no need to reply to this thread anymore. Thanks anyway]
Hello everyone, I need help!!!!
Today my Samsung GS6 Edge+ died. (At least, that's what I think)
I own my G928F for 1,5 years now. I rooted it two weeks after that. Several weeks ago I flashed a new ROM called N-Lite Nougat v4.1 which has worked smoothly and without any problems since I've flashed it.
However, today, the 26th of June, my phone turned off all of a sudden while scrolling through Facebook. I haven't flashed, installed nor done, anything that would affect my phone in such a way that it would crash this way. I tried force rebooting with the 3 buttons pressed (Home, Vol+, On/Off) several times. My phone just boots into the ROM and then freezes instantly. Again tried force rebooting for like 5 times, NO luck. Then I tried booting into recovery mode (TWRP 3.1.0.0), cleared Dalvik and cache, factory reset, rebooted, still no luck. Tried several other custom ROM's, still NO luck. Also tried flashing stock Samsung Firmware using ODIN, no luck whatsoever.
I couldn't find any similar problems in the ROM thread, nor anywhere else on the internet. Besides that, I'm starting to think this problem is a defect to the hardware, not the software.
Does anyone know what would be the best thing to do in my situation? Or perhaps anyone who might know what the problem might be and have a possible solution?
Thanks in Advance.

Recovery mode (TWRP 3.1.0.0) is accessible though, but that's all. While trying to install another ROM it just reboots randomly, during flashing progress.

When you say you tried flashing stock rom with ODIN, does it fail or does it succeed but freezes up when you are back in android OS?

kdogguk said:
When you say you tried flashing stock rom with ODIN, does it fail or does it succeed but freezes up when you are back in android OS?
Click to expand...
Click to collapse
It succeeds. But when it's done it just keeps going in a bootloop. It doesn't even boot into Android now. I've used the right settings in Odin. Even tried several different versions of Odin. No success

Larss97 said:
It succeeds. But when it's done it just keeps going in a bootloop. It doesn't even boot into Android now. I've used the right settings in Odin. Even tried several different versions of Odin. No success
Click to expand...
Click to collapse
Out of curiosity, when you flashed the stock Rom was it 6.0.1 or 7.0?
Does it just get stuck on the S6 EDGE + screen for a while? If so you might be to impatient as first boot on almost all roms both custom or stock take a while to boot up. If it shows the Samsung splash screen over and over then yes it's bootlooping.
I can't think of any other reason for it bootlooping, especially if you have flashed a stock Rom, unless maybe you flashed 7.0 rom and still have a 6.0.1 bootloader. But I think that just causes loss of baseband, not a bootloop.
I would suggest another kernel, but that is normally included in the stock rom.
Do you download them from sammobile or another site? If it's another site, is it a reliable site?

kdogguk said:
Out of curiosity, when you flashed the stock Rom was it 6.0.1 or 7.0?
Does it just get stuck on the S6 EDGE + screen for a while? If so you might be to impatient as first boot on almost all roms both custom or stock take a while to boot up. If it shows the Samsung splash screen over and over then yes it's bootlooping.
I can't think of any other reason for it bootlooping, especially if you have flashed a stock Rom, unless maybe you flashed 7.0 rom and still have a 6.0.1 bootloader. But I think that just causes loss of baseband, not a bootloop.
I would suggest another kernel, but that is normally included in the stock rom.
Do you download them from sammobile or another site? If it's another site, is it a reliable site?
Click to expand...
Click to collapse
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha

Larss97 said:
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Click to expand...
Click to collapse
The last thing I can think of was did you get the right rom for your phone? 928F or 928T etc.
Other than that it might be a trip to the repair centre I'm afraid.

Larss97 said:
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Click to expand...
Click to collapse
Try to do a factory reset in the stock recovery. It might help.

vishnu8058 said:
Try to do a factory reset in the stock recovery. It might help.
Click to expand...
Click to collapse
Done that, no success

kdogguk said:
The last thing I can think of was did you get the right rom for your phone? 928F or 928T etc.
Other than that it might be a trip to the repair centre I'm afraid.
Click to expand...
Click to collapse
Yeah i got the right rom for my phone. I've already sent it to a certified Samsung repair centre, it's still under warranty. Thanks for the help anyway

Samsung Note 4 N910F is not stuck in bootloop, still doesn't really boot

Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!

Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.

Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?

Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.

eMMC failure, snapdragon models are susceptible to this.

Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.

Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.

KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?