Database Users

Please help me: Corrupt TMO Tab

Hello,
Please Help!! My stock (firmware but rooted) TMO Tab started locking up and then progressed into constant reboots, lockups and semi hard resets (I lose all screens and they are back to stock, email accounts are gone in stock client, but apps are still there and a lot of other information is still there like wifi, bluetooth setting/devices etc.) Also, sometimes, the device hangs on the Samsung logo on boot up and I have to power down holding the button for 10 seconds and then turn back on..
It is almost like I got a virus. I did a hard reset the other night, went to bed with about 80% battery and it was completely dead in the morning. Last night went to bed with 91% and it was dead in the AM. Something is wrong and draining my battery.
Tmo is not standing behind their product because I bought it without a contract and said Samsung would either refund me or send me a new one(which I knew it couldn't be right), and it wasn't. They said send it in for 10-14 days and they will send me a working model.
So given all the problems I am having which seem to be software related, which software should I install? Something I won't have problems with or will still allow me to accept future Tmo updates if needed or wanted.
Also I am upset over the email limit(one month unlike the VZ version etc) on the stock email client so a Euro version would be fine if it had that feature and I also am not using the Tmo network so a disabled 3G network for data is not a problem.
Thanks for your help and suggestions.
Best,
BC

Please help me...
Update: My Tab was stuck on the Samsung logo for the longest time this morning(like 3 hours). I did the volume up/power button and wiped but still was stuck. It finally booted up but I am sure it is going to lock up and I will have to go through the same thing hoping to get it to boot up.
What could've caused it? What should I do while i have it on? Should I update to the Euro software and if so, which one? There are so many choices and not sure which one to do. Also, would I be able to go back to the stock tmobile s/w if I can return it for a replacement?
One thing that i noticed in the apps is a folder called error 1.0.0 but I cannot uninstall it. Is this normal and does anyone else have it? The other thing is that I still have the same memory available as when I had all my apps, email etc in it. Like it didn't really erase everything.
Please help and point me in the right direction. I have been scouring the net for 4 hours now and I don't know which way to go.
Thank you,
BC

Perhaps you poked around in the files system and accidently removed something? I would go to the Roto Stock firmware package thread, and flash that to repair a corrupt file system. Only a guess on my part, but it won't do any harm.

Well I suppose but I don't recall messing around with anything. I was hoping that while I had to change or repair my software, I should put the best on that there is to offer.
What software do you use or recommend?
Thanks for the reply! This is driving me crazy! I have had to turn off and back on at least 15 times today trying to get it to work amd habe wiped like 5 times.
Do you think I should just try and get a replacement from tmobile?
Thanks,
Brian

Woah, slow down partner. Make a Titanium Backup to the external sd card then remove it. Flash Rotohammers stock T Mobile firmware. Reroot with SuperOneCLick. Reinsert the external SD and reinstate your apps with Titanium. If things are still wonky after that then it's probably a hardware problem.
EDIT: I'd flash using Odin 1.7. It's just easier than Heimdall to me. Personal preference I suppose.

halftonehero said:
Woah, slow down partner. Make a Titanium Backup to the external sd card then remove it. Flash Rotohammers stock T Mobile firmware. Reroot with SuperOneCLick. Reinsert the external SD and reinstate your apps with Titanium. If things are still wonky after that then it's probably a hardware problem.
EDIT: I'd flash using Odin 1.7. It's just easier than Heimdall to me. Personal preference I suppose.
Click to expand...
Click to collapse
I did the backup and reinstalled after one of the wipes but it keeps locking up and not booting up. I haven't had it on 1 time successfully yet today and it past 10PM...
The main reason I would like a different firmware is because I want the full functionality of the email client like in some of the other tabs and android devices.
Tmobile and i don't know who else (I read ATT) crippled the email and it doesn't have the option to have all email on the device which is great for short trips without the laptop.
What about some of Roto's other firmwares? Like i said previously, I am not using Tmobiles data or service so it doesn't matter. I also read that the browser and overall was really smooth.
Is it ok to root with z4root? I have the app on my sd card and that is how i've done it before.
Thanks for your suggestions and i appreciate all feedback. I have to do something because this device has become a paperweight.
Thank you,
BC

bconfer said:
I did the backup and reinstalled after one of the wipes but it keeps locking up and not booting up. I haven't had it on 1 time successfully yet today and it past 10PM...
The main reason I would like a different firmware is because I want the full functionality of the email client like in some of the other tabs and android devices.
Tmobile and i don't know who else (I read ATT) crippled the email and it doesn't have the option to have all email on the device which is great for short trips without the laptop.
What about some of Roto's other firmwares? Like i said previously, I am not using Tmobiles data or service so it doesn't matter. I also read that the browser and overall was really smooth.
Is it ok to root with z4root? I have the app on my sd card and that is how i've done it before.
Thanks for your suggestions and i appreciate all feedback. I have to do something because this device has become a paperweight.
Thank you,
BC
Click to expand...
Click to collapse
hey dude you sound nervous as hell man, relax. as long as you can get your phone in to download mode. you will be ok. flash rotos tmobile stock firmware. if it works hooray! if not flash rotos jme 4

Still out of commission
I am not nervous, just annoyed as hell.
I flashed the stock tmobile firmware, booted it up and it crashed after about 10 minutes and I am back stuck on the samsung logo. I haven't been able to get it to boot up for about 5-6 days. I have wiped many times and no dice.
Should I wipe cache partition? Try the JME software?
Thanks for your help!
BC

I goofed, and I don't know how I did it

Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...

Think I figured it out
Well after writing this, for my own personal sense of masochism and an overall morbid curiosity, I kept reading, and figured out how to get the phone to actually boot into proper recovery mode (as in NOT Odin), and was able to get a ROM back on the phone, as I didn't care for any of the nandroids I had there. As I am not sure that anyone actually viewed this before I resolved my own issue much less had a chance to respond, it's not appropriate to thank anyone for solving my own problem, except for the poster of the thing that I read which led to my resolution, but I will throw out a blanket thank you to all those that take the time to develop, write, and help others solve the stupid stuff, it is appreciated, at least by this Ohioan, who sometimes manages to get in over his head!
dsly4425 said:
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Click to expand...
Click to collapse

Huge problem S4 not working anymore..

So this is my sad story..
I bought a second hand Samsung S4 (i337M Telcel) Unlocked, the day i got it, i tested in front of the seller everything was nice and smooth.. So i payed..
I was very excited and i proceed to make the Root proccess, at beginning i was having issues with the drivers and Odin, then i was able to fix it..
Anyways long story short i ended up with the ROOT, CYANOGENMOD CM11, and PHILZ 6.. The first day was working fine my cellphone.. (I must say i rooted in my life at least 4 devices even an S4 i9500 all of then with success and not a single problem.. Using them form months and even gears.. The latest was a Moto E..)
Ok so the i337M was working good since the first morning with the root, but in the afternoon it just turned off one time.. Was weird but i didnt pay much atention..
The second day i was listening music and suddenly it turned off, and since then the cellphone is not able to keep on for more than 10min..
Some times i can load the complete OS and ofter 2 min it turn off sometimes at the Samsung S4 logo turn off something i must say is that the Device every single time i turn it on, on the Samsung S4 screen says "kernel is not seandroid enforcing" in red letters, some people say it happens when the root process is not made correctly some says it normal because its rooted..
I already installed from Odin the Stock ROM from SamMobile, and the problem is exactly the same.. A friend of mine told me it could be the Logic Card AKA Motherboard.. But i want to believe its just a software problem.. Cuz' before i rooted cellphone was working..
- Download mode: Works like a charm not a single problem and basically its the only way i keep trying different options to install on the phone..
- Discovery mode: With CWM sometimes works good, sometimes it just turn off, with Philz runs good not turning off or something and its how i was able to wipe data, cache, dalvik, factory reset to the cellphone..
Im thinking in starting over like pretending i didnt do anything to the cellphone, try again the root, the rom, the PHILZ (dont know how to call it).. and hope for the best..
Any advice or reliable links where i can download the correct files for my S4 i337M.. You are basically the last reliable source i have to fix my S4 if you give up with me, then i must admit my cellphone has passed away ..
Hope you can help me thanks in advance and have an excellent day!!:laugh::good:

The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.

creepyncrawly said:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
Click to expand...
Click to collapse
Thanks for your reply.. I still dont know how but with Philz recovery, i was able to make a full wipe, i mean it deletes everything every single folder previously made was erased, and i can tell you that because i have a folder called ROOM where i places my ROM, Kernel, etc.. So i can flash them in discovery..
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..
Just two advices.. Never ever download files from Youtube ****y links.. Always go to the source.. Youtubers are assholes.. Real help and information comes from real people that knows what they are talking about like this forum and also updated and real ROM's come from the main source not Mega o Linkbucks...
Other advice embrace your self to do it.. Study every single question you have in Android, from KERNEL to ROM and ROOT.. Isn't that difficult..
One more question, Which ROM with Lollipop would you suggest to install i have the i337M?

SUNDR1V3R said:
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..]
Click to expand...
Click to collapse
May I make a suggestion? Now that you have the phone working, can you possibly just use it for a week without doing anything to it? Don't try to root it or do anything other than text, make phone calls, and install a few programs. This will establish a baseline of behavior for your device, so you'll be able to tell when its behavior is out of the ordinary.
I understand your desire to make it your own. I got my S4 brand new from AT&T and said that I would wait at least a month before rooting it or changing roms, in case there was a problem and needed to return it. I had good intentions, but I couldn't stand it anymore and rooted it after only 3 days! It will take a lot of patience, but you really need to use it for more than a few hours to make sure that the hardware is okay.

I agree take baby steps, week stock, week root, week recovery. Figure out if its hardware or one of the steps is causing it.

[A2017G] LineageOS 14.1 - Can not access TWRP anymore, can't get through setup either

Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks

OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty

Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.

OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good

my S7 edge is hard bricked

I had BlackDiamond.N8.PIE.V2.0 over a year on my phone and it was working with no problem.
today I decided to update my phone, first updated the TWRP to the latest version "TWRP-3.4.0-0-hero2lte" updated without any problem,
then I downloaded BlackDiamond N8 Port V10.0, wiped everything (even internal storage), and installed the ROM,
it installed successfully, wiped the caches, reboot to the system, android loaded without any issue,
after loading into android, I added my google account, and I was testing the phone, after 10min of working with the phone,
while I was testing the camera app (it's was a little laggy) my phone freezes and after a couple of seconds, the screen went black! I thought it's gonna reboot, but nothing happened.
I tried to hard reset the phone by pressing "power+volume down+home key", but it didn't work, connecting to the charger is nothing happen, there is no LED light, my phone is completely dead
does anyone have any idea why this happened? installation and booting to android was completely fine, everything worked fine, and suddenly my phone freeze and hard bricked.
you know this is not the first time I'm installing custom ROM, I'm done it before and I've always been careful, never had any issue like this, but this time really I don't know what happened and to be honest, I really love my S7 Edge, I don't want to replace it.

aalireza439 said:
I had BlackDiamond.N8.PIE.V2.0 over a year on my phone and it was working with no problem.
today I decided to update my phone, first updated the TWRP to the latest version "TWRP-3.4.0-0-hero2lte" updated without any problem,
then I downloaded BlackDiamond N8 Port V10.0, wiped everything (even internal storage), and installed the ROM,
it installed successfully, wiped the caches, reboot to the system, android loaded without any issue,
after loading into android, I added my google account, and I was testing the phone, after 10min of working with the phone,
while I was testing the camera app (it's was a little laggy) my phone freezes and after a couple of seconds, the screen went black! I thought it's gonna reboot, but nothing happened.
I tried to hard reset the phone by pressing "power+volume down+home key", but it didn't work, connecting to the charger is nothing happen, there is no LED light, my phone is completely dead
does anyone have any idea why this happened? installation and booting to android was completely fine, everything worked fine, and suddenly my phone freeze and hard bricked.
you know this is not the first time I'm installing custom ROM, I'm done it before and I've always been careful, never had any issue like this, but this time really I don't know what happened and to be honest, I really love my S7 Edge, I don't want to replace it.
Click to expand...
Click to collapse
Possibly a hardware problem. You will have to take some technician for a more accurate analysis.

Dark Stranger said:
Possibly a hardware problem. You will have to take some technician for a more accurate analysis.
Click to expand...
Click to collapse
if it's hardware, why I didn't have any problem before updating the ROM? is it possible updating damaged the phone?

one more thing, I saw some people use a dongle called USB-JIG on dead Samsung phones, that enter phone to download mode and after that flashing with Odin.
do you think it's work on my phone?

aalireza439 said:
if it's hardware, why I didn't have any problem before updating the ROM? is it possible updating damaged the phone?
Click to expand...
Click to collapse
It can occur, despite being very difficult. I already corrupted the xperia bootloader I had, but it never happened on my samsung devices. I even have a s7 edege and I am changing his rom and I never had any problems. As I said, you should take the device to an assistance center to get an idea of what really happened. Perhaps it could be a hidden problem, which was only expressed by changing the rom, or it could give the same problem with the old rom. What I can say is that a simple exchange of rom, would hardly cause a hard brick in a device.
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
aalireza439 said:
one more thing, I saw some people use a dongle called USB-JIG on dead Samsung phones, that enter phone to download mode and after that flashing with Odin.
do you think it's work on my phone?
Click to expand...
Click to collapse
You can also try, because if your device is not completely dead, it can come back to life with this procedure. But I still recommend taking the device in for a technical assistance.

There are 3 cases in this:
1. If you flashed a corrupted/wrong bootloader in twrp/flashfire or anything that doesn't blocks a wrong flash like odin. Your phone is dead for good. Only a usb jig/repair box or a local mobile technician can fix that.
2. Your phone is bugged with black screen. Installing a custom rom can cause weird things. Sometimes hard stuck with screen off/black .. now you need to wait for battery draining itself completely and then plugging in charger and trying to get in download mode. If you could go in download mode then you can reflash through odin and it will be back to normal. Although sudden turn off and then complete deadness is often a hardware failure.
3. If phone after draining completely doesn't shows life when connected to charger and can't go in dl mode then its either hardware failure or bootloader problem like in no.1 point. You will need to take it to a mobile repairer or use a repair box/jig nevertheless.
Sent from my hero2lte using XDA Labs