Database Develop

*URGENT* Huge Problem with my S3 Mini

Hey XDA guys,
I've got an I8190N
I've got a pretty big problems and I need the help of your big brains.
Well a long time ago (17th September 2013) I posted a thread about a problem with my phone, when I booted up, it had this screen:
*Image should either be here or in the attached thumbnails*
So about 3 weeks ago from today I was trying to install a new CM11 ROM update from Maclaw but after I put the zip on my sd card and booted into TWRP recovery (2.6.3.0, just in case it needs mentioning), the phone shut off in the middle of the installation, I thought it was just the usual bugs I get whilst flashing ROMs so I tried to turn it on and it wouldn't turn on.
After a couple of attempts I finally realised that it's able to go into download mode only, I think that means it's soft-bricked right?
So I kept trying to re-install the stock ROM (unroot, unbrick etc) through odin but it kept failing.
I sent the phone to repairs and they wouldn't repair it (because it's rooted obviously, I thought maybe they wouldn't know but of course they did).
I obviously can't get a replacement and start over again because the warranty is void now that I've rooted it
So now they've sent it back and it's currently a paper weight that can go into download mode and refuses to install stock ROMs through Odin.
What do I do? I really need help guys (I don't need to worry about backups because I always backup)
Please answer soon, otherwise I'll be without a phone and my phone company will keep charging me for my contract eventhough I'm not using the phone.
Thanks in advance for any help given

LordwinOfficial said:
Hey XDA guys,
I've got an I8190N
I've got a pretty big problems and I need the help of your big brains.
Well a long time ago (17th September 2013) I posted a thread about a problem with my phone, when I booted up, it had this screen:
*Image should either be here or in the attached thumbnails*
So about 3 weeks ago from today I was trying to install a new CM11 ROM update from Maclaw but after I put the zip on my sd card and booted into TWRP recovery (2.6.3.0, just in case it needs mentioning), the phone shut off in the middle of the installation, I thought it was just the usual bugs I get whilst flashing ROMs so I tried to turn it on and it wouldn't turn on.
After a couple of attempts I finally realised that it's able to go into download mode only, I think that means it's soft-bricked right?
So I kept trying to re-install the stock ROM (unroot, unbrick etc) through odin but it kept failing.
I sent the phone to repairs and they wouldn't repair it (because it's rooted obviously, I thought maybe they wouldn't know but of course they did).
I obviously can't get a replacement and start over again because the warranty is void now that I've rooted it
So now they've sent it back and it's currently a paper weight that can go into download mode and refuses to install stock ROMs through Odin.
What do I do? I really need help guys (I don't need to worry about backups because I always backup)
Please answer soon, otherwise I'll be without a phone and my phone company will keep charging me for my contract eventhough I'm not using the phone.
Thanks in advance for any help given
Click to expand...
Click to collapse
I believe that kies has emergency firmware that you can use to revive your phone? Try that. What does it say when it fails in odin?

hello,
so you can still go into download modus?
try the latest recovery (2.7 if i'm correct...) and flash with odin.
then try to boot into recovery and reflash the latest mclaw (or any other) non stock firmware.
think about it that you have to unzip the odin firmware package you download from maclaws site ( i forgot it and got messing around 2hours ago.... also staring at the erro in odin and thinking W*F is happening :cyclops: but then i realized i need to unzip the package...
realy good luck.....

Hi
Odin flash pit file

It just says the big black FAIL in the red background where it's supposed to be PASS in the green background

Could you guys give me download links to the PIT files, TWRP and the firmwares so I could get the right ones please?
Thanks

LOOK HERE
(i8190_goldenxx.zip) is the pitfile for I8190 only and i8190N_goldenxx.zip for I8190N version
BUT: these are NO flashable files - extract them and choose xxx.pit in Odin.
MJ

Could you give me a link to the pit file please

Do you have a link to the firmware I should use because tys0n gave me one before which was the service firmware (like 1.29gb) but it wouldn't work for this problem

LordwinOfficial said:
Do you have a link to the firmware I should use because tys0n gave me one before which was the service firmware (like 1.29gb) but it wouldn't work for this problem
Click to expand...
Click to collapse
come on boy, it´s really easy to find it, but ok, it´s friday and weekend comes ...
Firmware
Look at the attached files in that post
to flash a pre-rooted, deodexed and zipaligned ROM try this one
MJ

LordwinOfficial said:
Hey XDA guys,
I've got an I8190N
I've got a pretty big problems and I need the help of your big brains.
Well a long time ago (17th September 2013) I posted a thread about a problem with my phone, when I booted up, it had this screen:
*Image should either be here or in the attached thumbnails*
So about 3 weeks ago from today I was trying to install a new CM11 ROM update from Maclaw but after I put the zip on my sd card and booted into TWRP recovery (2.6.3.0, just in case it needs mentioning), the phone shut off in the middle of the installation, I thought it was just the usual bugs I get whilst flashing ROMs so I tried to turn it on and it wouldn't turn on.
After a couple of attempts I finally realised that it's able to go into download mode only, I think that means it's soft-bricked right?
So I kept trying to re-install the stock ROM (unroot, unbrick etc) through odin but it kept failing.
I sent the phone to repairs and they wouldn't repair it (because it's rooted obviously, I thought maybe they wouldn't know but of course they did).
I obviously can't get a replacement and start over again because the warranty is void now that I've rooted it
So now they've sent it back and it's currently a paper weight that can go into download mode and refuses to install stock ROMs through Odin.
What do I do? I really need help guys (I don't need to worry about backups because I always backup)
Please answer soon, otherwise I'll be without a phone and my phone company will keep charging me for my contract eventhough I'm not using the phone.
Thanks in advance for any help given
Click to expand...
Click to collapse
You can go to recovery mode then by using three button combo
if its no working flash it from here using odin

Sorry, it's just not my day, phone breaks, gf breaks up with me because I didn't reply to her because my phone broke lol just ain't able to fix my phone myself like usual, I got a USB jig on the side just in case I need it if that'll be of any help? & Thanks for the links, appreciate the help

Fixed
Thanks guys, the phones fixed
Really appreciate all the help

T mobile note 4 restart, and power issues

I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.

Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?

Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk

aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.

I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858

I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!

notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.

I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....

tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me

Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.

thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.

I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button

phone crashing issue

So, question.... This might not be a Rom issue. But I figured I would ask. Has anyone been having issues of the phone crashing and completely shutting down when you open the camera app.... Or any camera app? I've found two ways to get the phone back on after this happens. You can pull the battery and restart... Or plug the phone into any charger and after a second it will show you the battery w lightning bolt.... Then show its charging normally with the phone off... Then you can reboot.
Now things to point out.... It doesn't matter if the battery is at 96%....or 46%.....this still happens. Also, I just bought a brand new battery for the phone maybe a month ago, and it's still doing the same thing....
Another also.... I kept thinking this was a hardware issue.... And had tmobile replace the phone.... This is my 4th phone... And they've all been doing the same things.
I also thought this could have been a conflicting app issue. So I uninstalled almost everything that I don't use and still have been having the same problem..... So.... Anyone? Any thoughts? Thanks
My phone is rooted , running [ROM] Maximum OvrDriVE 6.0.1 MM V3.2 (8/24/16) [910T/910W8/910T3] Running update 3.5

SamJamz said:
So, question.... This might not be a Rom issue. But I figured I would ask. Has anyone been having issues of the phone crashing and completely shutting down when you open the camera app.... Or any camera app? I've found two ways to get the phone back on after this happens. You can pull the battery and restart... Or plug the phone into any charger and after a second it will show you the battery w lightning bolt.... Then show its charging normally with the phone off... Then you can reboot.
Now things to point out.... It doesn't matter if the battery is at 96%....or 46%.....this still happens. Also, I just bought a brand new battery for the phone maybe a month ago, and it's still doing the same thing....
Another also.... I kept thinking this was a hardware issue.... And had tmobile replace the phone.... This is my 4th phone... And they've all been doing the same things.
I also thought this could have been a conflicting app issue. So I uninstalled almost everything that I don't use and still have been having the same problem..... So.... Anyone? Any thoughts? Thanks
Click to expand...
Click to collapse
For folks to assist, you will need to provide basic info like rooted or no what firmware are you on, what model of note 4 etc....

I have the exact same problem with OP and will also have chance of crashing if you open Facebook or FB Messenger or Google Chrome. Sometimes it will die instantly around 80% where once die on 90%+ when trying to take a picture using stock camera apps. When it die you see a quick less-than-second horizontal matrix line.
Some detail of my current phone is as below:
Model: SM-N910T3
Android OS: 6.0.1
Baseband: N910T3UVU3EPJ2
Kernel: 3.10.40-9385989 ; [email protected] #1 ; Wed Oct 12 15:31:09 KST 2016
Build No.: MMB29M.N910T3UVU3EPJ2
Root Status: None (Never rooted)
Firmware: Stock ROM (Never flashed Custom ROM, flashed latest Stock ROM once, success)
The problem occur when I get OTA update from LL to MM. Few months later update again through OTA to current firmware but problem still occur. Then tried factory reset but didn't solve the problem. I thought of bad update download with OTA, so I download the latest firmware on SamMobile and flash it with Odin3.11.1 hoping will fix the problem. It didn't fix the problem, but I seen some new apps shown up as below:
- Android System WebView
- Beaming Service for Samsung
- ANT Radio Service
- ANT+ Plugins Service
- Briefing for Samsung (Update) <--- Exact apps name shown in Google Play
None of these apps were what I'm aware of even after I did the latest OTA updates. I hope anyone can help troubleshooting this issue as this is really annoying and now I have to always carry a power bank with me. For now I will try to re-download the firmware again and see if that will help although I doubt it will. Many thanks in advance!
---------- Post added at 12:42 PM ---------- Previous post was at 12:36 PM ----------
Also I have the same issue as the OP in the link below with the same battery usage drop picture.
http://forums.androidcentral.com/samsung-galaxy-note-4/610523-note-4-sudden-battery-drain.html
I go through the whole thread but none of the solution work. Though it might be helpful to post it here.

http://forum.xda-developers.com/note-4-tmobile/help/note-4-issues-post-11-06-2016-t3495012

sloanster said:
http://forum.xda-developers.com/note-4-tmobile/help/note-4-issues-post-11-06-2016-t3495012
Click to expand...
Click to collapse
I see your post is for N910T. Mine is N910T3, will flashing T2 stock firmware works?

jackgan said:
I see your post is for N910T. Mine is N910T3, will flashing T2 stock firmware works?
Click to expand...
Click to collapse
You can try..
Odin will either let you or not!
I find it hard to mess up the device, I've tried lol...
But that's just me!!!
It's yours to risk...
I'm currently on the T2 firmware!

After update to EPJ2, my Note is crashing too. Seems like there is a heekup in a processing power/ram. It lags for a moment and shuts down. So far this happened with Camera app, Chrome, Facebook, and a few other apps. Sometimes I would get "emmc read fail" or something along the lines and the phone would not boot. The only thing that seems to be MORE stable is Dirty Unicorns ROM, anything based of the STOCK or any Samsung ROM crashing.

Same issue: Note 4 restarts itself, many times.
This is my first post. I have the same problem with my Note 4: Bought it new a month ago (via eBay with 30 days warranty, then cannot return or exchange). The phone restarts itself many times, especially when I use the camera. A friend suggested me to download the stock ROM (N910TUVU2EPJ2) and use ODIN. Now, as long as I slow a bit, pressing and wait then the phone is okay. If I press anything fast, many times, then it restarts itself again. Seems like the RAM is dead. I have read somewhere that we can downgrade from N910TUVU2EPJ2 (version 6.0.1) to N910TUVU2DOK2 (version 5.0.1) and it runs smoother. Anyone has any idea, please help. If downgrading to the DOK2 can solve the problem, please let me know. Thank you for this great forum.

Skinny7 said:
This is my first post. I have the same problem with my Note 4: Bought it new a month ago (via eBay with 30 days warranty, then cannot return or exchange). The phone restarts itself many times, especially when I use the camera. A friend suggested me to download the stock ROM (N910TUVU2EPJ2) and use ODIN. Now, as long as I slow a bit, pressing and wait then the phone is okay. If I press anything fast, many times, then it restarts itself again. Seems like the RAM is dead. I have read somewhere that we can downgrade from N910TUVU2EPJ2 (version 6.0.1) to N910TUVU2DOK2 (version 5.0.1) and it runs smoother. Anyone has any idea, please help. If downgrading to the DOK2 can solve the problem, please let me know. Thank you for this great forum.
Click to expand...
Click to collapse
I'm on pe3 is that a good one I'm a noob on this form

Firmware update, EQC1?

I don't see EQC1 on sammobile, anyone else see the 127 MB update?
I'm on EQB1.

Yup, I see it, 127.53mb on both of mine SM-N910T3 and
SM-N910T

I have it as well. Have you flashed yet?

I have it too. I'm not sure I want to flash, especially if it patches the ability to root my phone.
My phone also suffers from the SD card / reboot issue (the phone constantly boot loops when both an SD card and SIM card are in the phone). I wonder if this update will fix that?

I tried flashing it and it failed, I'm running a stock highly modified rom. I'll try reflashing the original stock unmodified rom when I get a chance tomorrow and apply the update. It looks like it's just security updates

Says "Various system improvements" for the QC1 update.
https://support.t-mobile.com/docs/DOC-28899

I updated to this version the other day, now I'm looking to root. Anyone know if the old root method still works? I may try myself in the next few days myself and find out.

I upgraded to it yesterday. Took about 30 minutes from start of install to finish. It updates the security to March 2017, has the new Google Play Store. Other than that I do not notice any other differences

Can i root after upgrade?

Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?

febzz88 said:
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
Click to expand...
Click to collapse
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.

d0ug said:
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
Click to expand...
Click to collapse
Hi,
That's certainly is one possible scenario (hardware failing). But based on my extensive research too, many have said that this could be faulty firmware. I went to a Samsung Experience Center and talked with a guy there and he said that it's a known issue affecting many Galaxy Note 4 Sprint users a few months ago. Samsung in the end replaced/repaired the affected units free of charge.
In the past 2 months or so, more and more Galaxy Note 4 users started experiencing this issue. And so it could be that the firmware triggered the issue, and eventually damaged the hardware.
Since we don't really have a 100% certain answer (of course, Samsung will never tell us), I'm just trying to see if anyone has updated the phone to the latest firmware and could tell us if it fixed the issue.

Soooo..... Is this rootable or not?

sino8r said:
Soooo..... Is this rootable or not?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242

I can't seem to get TWRP to work on this. I've tried several times with Odin, it appears to be successful, phone reboots, but then when I try to reboot into recovery there's no TWRP, only stock. Anyone else have this issue or any suggestions?
Edit: Tried something I remembered reading in another thread. I pulled the battery immediately after Odin successfully finished and the booted directly into recovery. It worked. I'm flashing pvsgh's rooted EQC1 and will report back if TWRP sticks
Edit 2: Success. Seems like pulling the battery after Odin/TWRP before the phone reboots did the trick

ok, thanks for the suggestion.

Anybody have a link for the firmware?

thecrunked said:
Anybody have a link for the firmware?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...firmware-galaxy-note-4-n910tuvs2eqb1-t3569911

Can I autoroot with EQC1?

I tried auto root and got
RECORVERY IS NOT SEANDROID ENFORCING,
AM I screwed? I assume there's some way to get back to EQC1 and boot the phone. There has to be. But could I do it and keep the data. I was trying to get deleted photos back.

Question SM-G998B Bricked

Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?

Seems different?
Well I would try Odin and an official ROM anyway, no pain no gain right?

What exactly were you doing before this occured?

You try the old delete usb driver, restart computer, install usb driver then restart computer and restart phone and try again.

SirDigbyCC said:
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Click to expand...
Click to collapse
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something

flairepathos.info said:
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
Click to expand...
Click to collapse
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.

To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.

SapphireEX said:
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
Click to expand...
Click to collapse
Oh I see the issue now you need to wipe all and re-flash full firmware when flashing the device using Odin
if that doesn't work flash the partitions with the kernel drivers and system partition
I had a similar issue with my current mtk phone and it was because the boot/preloader partition bilieved i had flashed the wrong firmware for my device(it was just a different firmware release for my phone
Just to be safe some ota updates break wehn the bootloader is not unlocked (when updationg from say android 8(oreo) -9(pie)...)
especially because of code errors in the update, cache/vendor partition being too full after downloading update

SirDigbyCC said:
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
Click to expand...
Click to collapse
If you're telling the truth, and it wasn't a bad module / firmware / etc, it is possible your eMMC got too hot and melted some solder. I've seen it happen before.
You'll want to diagnose everything you can. If you're on Windows, does it recognize a USB device or a COM device? If linux, does lsusb return anything useful about it?
If it's not being detected, and multiple wires doesn't change anything, are you able to access sahara mode / download / DFU? If so, go to those and try again.
If you are lying, and this is a bad firmware flash / OTA brick, you'll need to tell us otherwise we'll be going in circles.

So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?

SirDigbyCC said:
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
Click to expand...
Click to collapse
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.

SapphireEX said:
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
Click to expand...
Click to collapse
I appreciate the vote of confidence, I don't think it was an OTA update that did it this time, it usually requests to do updates which I highly doubt I would have pocket approved through a flip case only short after pressing play on Spotify.

So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!

SirDigbyCC said:
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
Click to expand...
Click to collapse
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!

shriom_manerker said:
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
Click to expand...
Click to collapse
It was free, turned out to be a hardware issue internally so I think covered by warranty as I have Care+ which has an excess of £40 which they didn't make me pay. They also replaced the screen due to some dead pixels, and the battery! Happy days!
Thanks all for your suggestions!