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 can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
OK first, I will say that I have been reading for days and days and am getting nowhere at all. I am running out of time as I am leaving Monday backpacking from OKC to Portland to meet a friend, then proceeding immediately to about 35 national parks. I HAVE to get this thing functional so that I can depend on it on the road for communication. Its current state makes me nervous. I got this tablet already rooted, custom stock rom, and with an unlocked ICS boot loader version 0.3.11. The only problems with it were the common charger/screen response issue. For $100, I can deal with that.
I flashed the Lightspeed from from the main list, everything went well... Until it rebooted the first time. Since then, directly after the bootloader screen, it briefly shows what looks like semi-colorful TV static, then shows boot animation and boots into the OS. It has never frozen on either screen.
I decided Lightspeed was not at all what I wanted, so I flashed CM10. I have yet to find anywhere in the Aroma installer where I can choose the apps installed, ONLY THEME CUSTOMIZATION. After the flash, it kept the boot animation from CM, and loaded right back into what looked like Lightspeed, and shows Lightspeed in the about menu also. I reflashed it, choosing a different boot animation to test, and did the same thing again, except it loaded ZERO extra apps at all, not even the stock bloatware. Nothing from any of the 3 roms. I reflashed Lightspeed, same thing again. No extra apps and just bare basic stuff. EXCEPT SUPERUSER. THAT DID LOAD ONTO IT EACH TIME. I haven't lost root access, the recovery works fine.
I flashed the V8 bootloader, and tried the above again. Same issues still. All of them. I have read until I'm blue in the face. If there is a way to fix this without using a PC, that would be grand. I have very limited PC access.
Anyone have any ideas? I have followed every single step 100%, I'm positive. I'm not new to rooting, flashing, and jailbreaking (doesn't apply here I know),"so lay it on me.
EDIT- I downloaded the 4.0.4 FLEX-Reaper rom and going to try that now and then I give up for the night. Tomorrow is the last day I have to mess with this before I leave. I tried to upload screenshots of the problems, but it won't let me attach them. Maybe that is another problem. Ugh who knows. Help
EDIT- That rom bricked my tablet. Through that brick, I found a working solution for the SoD, found a way to recover without files on external SD, *THIS FIXES THE BRICKS CAUSED BY CM10 AND REFLEX!!!* and I didn't lose anything. This thing is back in pristine order. I can finally sleep! Will post later on how I did it. I need sleep now.
Hi,
Given that I have had the misfortune (self inflicted) of 'upgrading' to the MH8 firmware I am finding that even rooted Tasker can no longer do the things it once did, e.g. reliably turn on/off bluetooth or even kill a basic app (even using root). I am wondering therefore whether I could use something like CM10.2 instead. My Knox warranty qfuse is stuffed as it is, so no point trying to stay true to stock any more and thought I might give CM10.2 a go.
The question I have is can this be done now that I have the Knox'ed bootloader?
If so is the installation the same as for a normal 10.2 install, and will I have to do a system reset? I am assuming yes to the latter, just wanted to make sure.
If someone is able to clarify that would be great - I don't expect warranty to be intact any more, clearly the boat has sailed, so would it be possible to run CM 10.2 or similar now?
I figured in for a penny, in for a pound so I went ahead and tried it anyway.
On the first attempt I noticed I only had around 2Gb of free space so did some digging and see that this is partly because you can't change the partition table on the S4 and, using a file browser, because it looked like I had some crud left over from before (despite clearing caches etc).
Using the recovery I tried formatting everything but that just soft bricked things, so I went ahead and re-flashed MH8 to get back to stock and then followed the steps to install CWM recovery and ultimately CM10.2 nightly. I now had the majority of the 9.25Gb available to me which is enough for my needs, although a shame you cannot just use all of the space as you wish and not as Samsung wants.
So far quite impressed with CM10.2, feels nice and snappy and obviously without most of the Samsung cruft. Just missing the S-View cover functionality at the moment but other than that I'm happy an will probably stick with it.
I have been running CM (currently CM11) on my SGS4 since I bought it from Sprint in summer 2013. However, Sprint changed their international partners pretty seriously in the past 2 years, so I *really* need a PRL update for international travel. Normally the easiest way to do this is to reboot to stock or TriForce, run the "update PRL" and "update Profile" options from in TriForce, and go on with my life.
But I encrypt my phone. So I had to boot into TWRP, wipe and format *everything* and make sure the phone came up unencrypted in CM. All is OK.
So I reboot, flash TriForce 5.4 custom with stock (not KK) kernel. Flash works fine, I reboot... and am prompted to decrypt the device before I can do anything. None of the decryption passwords I've used in the past (I checked my password safe) are working. When I flash back to CM, it boots fine, and the settings says that the device is not encrypted.
I downloaded and tried TriForce 5.2 and 4.0, both are giving the same problem. I have used TriForce in the past on this phone, so it SHOULD be fine....?
Someone in #twrp said that the location of the encryption key changed from Android 4.4 to 5.0. So my only remaining thought now is that there was also a change from 4.3 to 4.4, and the encryption key for 4.3 didn't get removed in the wipe, and since the partition is NOT encrypted, the decryption, even if I have the right key, fails, so I can't get into the phone. Hope that makes sense.
Anyone have any guess better, or, if I'm right, know what I need to move/edit to fix this?
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
docsmooth said:
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
Click to expand...
Click to collapse
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
docsmooth said:
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
Click to expand...
Click to collapse
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
http://money.cnn.com/2015/05/21/technology/resell-android-phone/
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
mikeprius said:
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
Click to expand...
Click to collapse
I was never able to get the stock odin download. The whole problem came up because I was going overseas... I got around it by just buying a local SIM rather than using the Sprint roaming (again, I was doing all this just to update the PRL. new GSM SIM = no PRL update needed). On the way home less than a week later, I cracked the screen so bad the LCD and backlight wouldn't even go on.
I replaced it with a Nexus 6. A bit big, but it doesn't suffer Samsung software awfulness, so I didn't have to flash it with CM to make it usable.