Related
CLICK HERE TO GO TO THE WIKI
I have decided to open a Questions and Answers thread on this section of the forum. This is a good way to keep the number of new threads with questions down to a minimum, which will make new threads essentially for people that are contributing to the Samsung Epic 4G. This includes, but is not limited to, people that are providing the following:
- Roms & Kitchens
- Programs & Apps
- Fixes & Tweaks
- Skins & Themes
- Tips & Tricks
I would like to request the help from other members to keep the thread in order and in check. This will have the added side effect of creating an ever self updating knowledge base that will far extend the content of the Wiki. This will in turn save us from having to answer the same question a billion times...
Please refer to the Wiki first before asking any questions though! It can be located here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700
CLICK HERE TO GO TO THE WIKI
Any idea when the OTA push for2.2 will start?
jg187211 said:
Any idea when the OTA push for2.2 will start?
Click to expand...
Click to collapse
Unfortunately, we don't have anyone in the community who has inside access to that information. Some of our members are affiliated with Sprint, and so have slightly more reliable rumors, but even their sources have thus far been wrong if they quoted a specific date...
So I hope you understand that I'm not being a jerk when I say, we won't know until it actually happens (and this will probably always be the case)
That being said, this most recent leak (DK28) seems stable so far IMO, so it could potentially become our official update
ok im a total noob to all this stuff. i followed the guide to update my epic to 2.2. the problem is, that the camera, gallery, and a couple other apps dont work. Can someone help me? Should i go back to 2.1, if so, how do i do that?
EDIT: Angry rant removed, thanks to the mods for a quick response (and to the member who's post was removed: no hard feelings, I hope you understand)
Just remember to read before posting, to make sure your post will be relevant and not redundant
jayzn210 said:
ok im a total noob to all this stuff. i followed the guide to update my epic to 2.2. the problem is, that the camera, gallery, and a couple other apps dont work. Can someone help me? Should i go back to 2.1, if so, how do i do that?
Click to expand...
Click to collapse
Whenever flashing a ROM using either recovery, it's always a good idea to wipe the phone (as in factory reset - I'm not referring to wiping the cache or the dalvik cache, although both steps are also usually recommended)
If you used the odin method described in this thread: http://forum.xda-developers.com/showthread.php?t=861213
then you might have flashed the wrong tar - DK05 and DK17 both had the camera problem, make sure you have the DK28 file.
If you have the right tar, then you could have an incomplete download... I doubt that though, when that happened to me, my phone wouldn't boot at all. But you might want to redownload the tar just to be sure (double check the filesize after it finishes and before you flash, if it seems too small then it messed up again)
That's the best general advice I can offer, but if you'd like to provide more details about the method you used (especially a link to the guide you used, if it isn't the one I provided), someone here might be able to identify where you're going wrong
i followed the instructions from http://forum.xda-developers.com/showthread.php?t=861213. i didnt use odin, i just used the .zip method. it took me a lot of tries cause i kept getting errors. the second mirror link worked for me, but like i said, my camera, gps, gallery and some other apps dont work.
oh and everytime i try to flash again, i get the error.
It sounds like you're either starting from the wrong rom or not wiping the phone before flashing the zip. All of the zip updates I have seen require you to start from DI18 stock (root an clockwork seem to be okay in my experience, all other mods must be removed) - if you have installed any custom roms, your best bet is to follow the odin method using the stock DI18 tar - so you may as well just skip the zip methodand odin to the stock DK28 tar
And you absolutely must wipe the phone (again, factory reset - I suspect many people are just wiping the cache and/or the dalvik cache).
Sent from my SPH-D700 using XDA App
Odin flashing
I've got a quick question. I'm looking to move to a build using the DK28 information release and it requires that I update the pit and modem files on my phone using Odin. Do I need to flash a 2.2 rom right away or am I safe to boot into my current rom first?
KaiXXV said:
I've got a quick question. I'm looking to move to a build using the DK28 information release and it requires that I update the pit and modem files on my phone using Odin. Do I need to flash a 2.2 rom right away or am I safe to boot into my current rom first?
Click to expand...
Click to collapse
Are you doing the strictly odin method (full froyo in a tar file)? Or an update.zip?
The odin method *should* include the modem and everything (and you use the updated pit in the same process) - you'll have to read the particular thread that you got the download link from, but I haven't noticed any odin tar files that required the modem separately
For the update.zip method, I don't know if it matters whether you flash the modem before or after applying the zip through recovery - I don't think either one overwrites the other, but that's a part of the process I can only guess about. But regardless of when you odin flash the modem, that's when you'll use the new pit file (the same as the odin-only method above).
As far as I know, the primary difference is that the update.zip doesn't inherently overwrite user data (but you'll probably have broken programs that FC all the time, which means a wipe is necessary, making this somewhat null). I prefer the odin method because it is a fresh flash of the entire system (I usually let it repartition as well - no one else has posted about that feature so I have no idea if it's a fluke that it hasn't given me problems)
Hope that helps
which is the best
so i have updated to dk28 froyo 2.2 i like battery life and performance can anyone offer info on which is the best rom for me or just some insight on which rom is the best overall
How do I stop running applications from starting every time I restart my phone?? I have the start up auditor but for some reason everytime I restart my phone the apps I have disabled keep restarting themselves and I have to go into the running programs and disable them manually. WTH?? Doesnt programs constantly running in the background kill the battery life?? How do I disable apps from starting?
youngpro83 said:
How do I stop running applications from starting every time I restart my phone?? I have the start up auditor but for some reason everytime I restart my phone the apps I have disabled keep restarting themselves and I have to go into the running programs and disable them manually. WTH?? Doesnt programs constantly running in the background kill the battery life?? How do I disable apps from starting?
Click to expand...
Click to collapse
How I understand it, especially with Froyo, you shouldn't have to kill programs in the background, if said 'background' process or service is working normal or efficiently. I still kill the DRM process when I reboot my phone, and not sure if it's still causing drain issues.
Also (someone else confirm this), I believe that constantly 'killing' certain background processes actually uses MORE battery, since it has to constantly restart itself. I've had a much more stable device *not* using auto killers, and just sniping one here and there that I know to cause drain.
Some reading material on GC, tho, in regards to memory management
Ignore me!
devo52 said:
so i have updated to dk28 froyo 2.2 i like battery life and performance can anyone offer info on which is the best rom for me or just some insight on which rom is the best overall
Click to expand...
Click to collapse
A lot of it is personal preference - this early in the game, the primary differences between the roms are going to be mostly cosmetic. So for now, the best advice I can offer is to try each of them and decide which theme you like. Regardless of how you upgraded, you had to use odin, so you have succeeded at the most difficult step of the process - and odin can bring your phone back to life if something goes wrong, so it's an invaluable skill to have.
In the meantime, keep watching the threads (quietly, unless you have a question that hasn't been asked already - we're working on cleaning up the forum to make it easier for everyone to find answers... but I digress...)
It's too early to be sure of any of the fixes out there - we have at least three separate fixes for the GPS issues; some people find success with one, others with another, and a lucky few don't need the fixes at all... so in summary, we can't say which is better or worse just yet, stay tuned and decide whether you want to experiment on the bleeding edge, or wait for these things to be stable and thoroughly tested.
And if you have any doubts, just stick with the stock DK28 for now
tl;dr, questions in BOLD.
Okay, after spending the entire night scouring the internet/this forum and starting from absolutely zero-knowledge about the Android OS, I managed to update my Epic to 2.2, and root the phone. Now, I'm kinda stuck as far as customization goes. I see all these cool skins and battery life mods and stuff, but they don't exactly offer any steps as to how to install them. Since I don't exactly know what file-types do what, I'm kinda shooting blindly at trying to update/install something "custom" onto the phone. So, my question(s) is/are:
What does the ROM do?
What does the ROOT do?
I know the root basically "unlocks" your phone, but that's all I know. The process of customizing the phone still remains a mystery. (that's the problem with following step-by-step instructions, rather than actually knowing what you're doing.)
I also don't understand the purpose of flashing a phone. Flashing, in my experience is to update something, like say a BIOS. But that sets the system back to square 1 as far as all settings go, in this particular example.
If I flash, with say Odin, after having updated to DK28 and "rooting," won't this make all the "customization" that I've done prior basically 'null' because I've just flashed the phone into a blank-state?
Sorry if these are questions easily answered by searching, but I just spent my entire sleep-cycle trying to find the answers to these questions, and managed to only get so far. I look forward to the answers On another note, I am now EXTREEEEMELY pleased with my phone. Before this evening, I was just the regular, old run-of-the-mill enduser. I liked the cool built-in customizations and all the apps and what not, but never dreamed of being able to customize my phone to THIS EXTENT. So, now it's something I'm very interested in doing..it makes my phone truly mine.
zdavidi said:
What does the ROM do?
What does the ROOT do?
Click to expand...
Click to collapse
Did you see the link to the Wiki in the original post of this thread? That's where I started when I first got here, it helped me understand the basics.
zdavidi said:
If I flash, with say Odin, after having updated to DK28 and "rooting," won't this make all the "customization" that I've done prior basically 'null' because I've just flashed the phone into a blank-state?.
Click to expand...
Click to collapse
It depends on what you flashed with Odin. If you only flash a modem file, then your customizations and apps are untouched. If you flash an entire ROM in "tarball" form then not only does it re-write the modem but it also overwrites all user data. Think of the latter as resetting the phone to stock and works even if you cannot boot up.
When can we expect a custom Kernel with netfilters for wifi tethering?
n00b question.
If an SDK version is released (say, like, Gingerbread today), does that mean chefs could take it and cook up a ROM for ANY phone (say, like, the Epic)? Or do they need something else to do that?
Remove Touchwiz Launcher (consequences?)
Hey-- I'm using Quantum 2.0.0 ROM, and I never use the touchwiz launcher. Does anyone know if it's safe to just remove the apk? (TouchWiz30Launcher.apk) or is there other functionality tied to it?
I use LauncherPro, fyi.
Please forgive my ignorance... I've searched the forums, looked at the wiki...
I use titanium backup and am now running the DK27 froyo build by noobnl. My question... How do I restore my e-mail accounts to the phone everytime without having to re-type them in? I've been flashing a rom every other day on average since I got the phone and it's getting REALLY old.
Morning Gentlemen,
I have had my Galaxy S3 on Rogers (Toronto) for over a month. I've been reading and downloading Roms (Kylan, Blazin, 2 others)
and am ready to flash. I actually flashed Blazin but went back to stock from my nandroid backup because the Google store
wouldn't work...then read I had to flash the GAPPS from the list - I coulnd't decern which one I needed........ANyone??????
Further, my only issue is to obtain better battery life. Are loading ROMS the best way? Ill go back to Blazin if this will yield me the
best results.....
Anyone on Rogers (or any other carrier) care to chime in???
And another thing - once a ROM is flashed and people are saying that for example, S-VOice needs to be added and a
link is presented, how is that file installed? Through CWM? Flash??
Very Much appreciated.
DSSKing
dssking said:
Morning Gentlemen,
I have had my Galaxy S3 on Rogers (Toronto) for over a month. I've been reading and downloading Roms (Kylan, Blazin, 2 others)
and am ready to flash. I actually flashed Blazin but went back to stock from my nandroid backup because the Google store
wouldn't work...then read I had to flash the GAPPS from the list - I coulnd't decern which one I needed........ANyone??????
Further, my only issue is to obtain better battery life. Are loading ROMS the best way? Ill go back to Blazin if this will yield me the
best results.....
Anyone on Rogers (or any other carrier) care to chime in???
And another thing - once a ROM is flashed and people are saying that for example, S-VOice needs to be added and a
link is presented, how is that file installed? Through CWM? Flash??
Very Much appreciated.
DSSKing
Click to expand...
Click to collapse
GAPPS are generally only flashed when using Cyanogen MOD ROMs, due to liability it had to be separated. Most, if not all ROMs outside of Cyanogen will have functioning google apps. If they do get wonky, sometime a full wipe is needed before, and after (at least for me, I wipe after as well). Or sometimes all you need to do is just wipe the cache of the particular app within settings and you're good to go.
For battery life, it is the user-based depending on the apps\widgets\refresh frequency. But generally speaking YES, some developers tweak their ROMs in a way so it has better battery life, smoother transitions, or better memory management, etc... The features of these ROMs are usually along with the OP. The best (and only) way to figure out which ROM is best for your use is to flash away and take it for a test drive.
For your last question regarding flashing items like S-Voice or what not... once the word "flash" is used, it usually refers to Clockwork, CWM, TWRP, whatever... so yes it relates to that. Flashing through this method requires .zip files so if it's a .zip, most likely its "flashed".
But my advice... read, read, and then once you're comfortable with what was said by the developer... READ IT AGAIN.
Good luck and happy flashing!
Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
happy4ya said:
Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
Click to expand...
Click to collapse
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Aerowinder said:
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Click to expand...
Click to collapse
Thanks for all the info. So I definitely have the FLO model.
I would like to use Titanium Backup for Root and a few other things that need root access so I definitely want to do this.
Also, being that this tablet has no micro SD, I definitely want to have read-write access with a USB drive. I've had this for almost a week already and I haven't loaded anything into it yet because I figured I'd be wiping it. I really don't want to mess with stock because of the lack of a few things. I really just can't stand having devices with restricted use. That's not what I paid for.
I never used Kit Kat before and not sure if I'll like it. Do you know if you can go back to 4.3? I know with some of the other devices (like my Galaxy S3 phone), once you update it OTA, they lock stuff up and you cannot roll back.
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
happy4ya said:
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
Click to expand...
Click to collapse
You can roll back to 4.3. Google hasn't gone full Apple yet. But I strongly advise against doing so, as it's a large step backwards.
Understood on stock OS, agree no options anywhere. Slimkat+franco.kernel+banks gapps. You won't look back. Also in developer options, switch to ART. Dalvik sucks. If you're using Banks' minimal gapps, the lack of some syncing libs (for the AOSP calendar nobody uses) will cause random FCs until you reboot a second time. Nothing to worry about. Just grab the Google Calendar, or whatever calendar you use, from the play store and freeze the AOSP one with TiBu. Another FC you might see is gms.location. It should only happen once. Something with play services.
Once you are rooted, you can grab BetterBatteryStats to see what's killing your battery. On stock installs, it's mostly going to be location-based stuff keeping it awake. You already turned off reporting, but you also need to switch location mode to Device only.
If i revert to kitkat, all i need is the Rom from sammobile correct? Or are there drivers or something superarte that needs flashing prior to downgrading?
In case you wonder why, my battery is draining to quick although i ensured to be at 100% and unplugged then clicked go. I also removed all files from device storage because i feel that Odin anything with a clean sdcard will giver smoother rom. Just my opinion. And also it is choppy, won't activate my common apps and i swear my data got stupid. Like slow as heck even though my 10gb plan just refreshed 5 days ago. And i hate the colors in the warning bars. Plus it doesn't show preview of name when recibing text, etc... that's what I've picked up this far. I've had it since last night 2300 est time.
Any suggestions?
I don't know if you still have the phone, if you do, I don't know whether or not you continued anyways:
for those who still need to know:
Flash the image from sammobile to the device using Odin 3.11 (or newer) on your windows pc
remember: sammobile premium access needed for archived files
So, let me begin this tale with this disclaimer: I've worked with modding communities across a whole span of genres, from gaming to building computers. I will begin with the assumption that I am at fault in this case and I'm clearly doing something wrong. I've about reached the end of possibilities that I can explore on my own, so it's not like I tried one thing and gave up.
Once upon a time, I knew more about what I was doing than I do now. I first bought the T800 model several years ago, and the first thing I did was learn how to root it and flash CWM recovery. I went on all sorts of adventures with the device but never fully explored the potential; just installed awesome stuff that I thought I would use forever and got rid of bloatware and other useless crap. Flashforward to a few months ago, when I realized I had a really nice tablet that I had spent money on but didn't use like I had wanted to. I'm working more and more on audio mixing, and I wanted to install an app for the tablet that would allow me to remotely operate a mixing board. To my dismay, the app required an updated version of Android, and I hadn't a clue as to how to do that because the tablet was rooted and such and the thing wasn't going to update (was stuck on stock 4.4.2). I don't remember what I had done with it many years ago - at least not very well - and all I had learned was nearly gone. I refreshed a little, made a backup, checked to see what I had and noticed I still had the CWM recovery up, things were still rooted fine, and I was prime for flashing a new ROM and wiping everything. Found the Lineage ROM, slapped that puppy down, aaaand... Verification wasn't happening. Huh? It didn't even try to install, it just gave up and put the stock ROM back on. Tinkered with it for a second and thought, eh, whatever, I'll just let it update itself now that it's been wiped and everything. Only the device still wouldn't let me update it to Marshmallow or whatever update limit it's got.... Awesome... Did a little more research. Oh, my recovery is probably super out of date. Grabbed ODIN, slapped a brand spankin' new TWRP recovery that was geared for my device on it, and decided that I shouldn't go with Lineage. I'll just go with a stock Nougat ROM (can't post a link, but if it's important I can PM it to you if it's relevant).
Followed instructions to the T (as far as I'm aware) and this time did everything with a fresh new outlook into what I was doing. Flashed it, flashed GAPPS, aaaaaand.... Samsung logo won't go away.... -sigh-... Wiped it again, tried to make sure everything was wiped correctly, made sure everything was up to date. Tried again, but alas... Nothing working right for me.
Perhaps during this tale you've already picked up on something I royally messed up. Perhaps you're thinking, "Wow, how did this doofus not brick his tablet?" Am I getting old and stupid? Was there still research I missed? I started with the low road of easy modding and had to force myself to a higher road of deeper learning and STILL came up empty-handed, so now I'm asking this awesome community for a hand. I know you can't do this for me, but I'd appreciate a guiding light, or at the very least a link to an article that I really should have picked up on. Let me know if there's information I've missed that I should also be putting out, and thanks for reading regardless!
If I reached a point where I don't understand what's going on and I am banging my head against the wall, I would download the latest stock firmware for my device from sammobile and flash it with odin. If I recally it correctly, that would be the November 2016 security release of Marshmallow, the last Samsung provided. This should wipe away everything you have on the tablet. Then, if you need to flash root or alternative ROM, flash TWRP and proceed from there.
Akopps said:
If I reached a point where I don't understand what's going on and I am banging my head against the wall, I would download the latest stock firmware for my device from sammobile and flash it with odin. If I recally it correctly, that would be the November 2016 security release of Marshmallow, the last Samsung provided. This should wipe away everything you have on the tablet. Then, if you need to flash root or alternative ROM, flash TWRP and proceed from there.
Click to expand...
Click to collapse
Much obliged for your response, I've been up for a bit hoping maybe the boot process would just take a while, but no luck there. In the meantime I've been trying a few different Lineage nightly builds and they all seem to result in the same problem; surely they can't all be messed up and it's obviously something I'm doing wrong. My last recourse is to do this terminal fix I found that worked for someone else, but I doubt I'd be that lucky. I will assume that the Nov 2016 Marshmallow release is a google search away (or am I just bad at finding things...), and I'll post back here either within the hour or tomorrow night when I have time to find this build. Again, thank you.
Merancapeman said:
Much obliged for your response, I've been up for a bit hoping maybe the boot process would just take a while, but no luck there. In the meantime I've been trying a few different Lineage nightly builds and they all seem to result in the same problem; surely they can't all be messed up and it's obviously something I'm doing wrong. My last recourse is to do this terminal fix I found that worked for someone else, but I doubt I'd be that lucky. I will assume that the Nov 2016 Marshmallow release is a google search away (or am I just bad at finding things...), and I'll post back here either within the hour or tomorrow night when I have time to find this build. Again, thank you.
Click to expand...
Click to collapse
Download the appropriate MM version from below. Boot to recovery, factory reset, flash with Odin.
First boot will take around 10 minutes.
http://updato.com/firmware-archive-...xact=1&r=&v=Marshmallow(Android+6.0.1)&rpp=15
Merancapeman said:
So, let me begin this tale with this disclaimer: I've worked with modding communities across a whole span of genres, from gaming to building computers. I will begin with the assumption that I am at fault in this case and I'm clearly doing something wrong. I've about reached the end of possibilities that I can explore on my own, so it's not like I tried one thing and gave up.
Once upon a time, I knew more about what I was doing than I do now. I first bought the T800 model several years ago, and the first thing I did was learn how to root it and flash CWM recovery. I went on all sorts of adventures with the device but never fully explored the potential; just installed awesome stuff that I thought I would use forever and got rid of bloatware and other useless crap. Flashforward to a few months ago, when I realized I had a really nice tablet that I had spent money on but didn't use like I had wanted to. I'm working more and more on audio mixing, and I wanted to install an app for the tablet that would allow me to remotely operate a mixing board. To my dismay, the app required an updated version of Android, and I hadn't a clue as to how to do that because the tablet was rooted and such and the thing wasn't going to update (was stuck on stock 4.4.2). I don't remember what I had done with it many years ago - at least not very well - and all I had learned was nearly gone. I refreshed a little, made a backup, checked to see what I had and noticed I still had the CWM recovery up, things were still rooted fine, and I was prime for flashing a new ROM and wiping everything. Found the Lineage ROM, slapped that puppy down, aaaand... Verification wasn't happening. Huh? It didn't even try to install, it just gave up and put the stock ROM back on. Tinkered with it for a second and thought, eh, whatever, I'll just let it update itself now that it's been wiped and everything. Only the device still wouldn't let me update it to Marshmallow or whatever update limit it's got.... Awesome... Did a little more research. Oh, my recovery is probably super out of date. Grabbed ODIN, slapped a brand spankin' new TWRP recovery that was geared for my device on it, and decided that I shouldn't go with Lineage. I'll just go with a stock Nougat ROM (can't post a link, but if it's important I can PM it to you if it's relevant).
Followed instructions to the T (as far as I'm aware) and this time did everything with a fresh new outlook into what I was doing. Flashed it, flashed GAPPS, aaaaaand.... Samsung logo won't go away.... -sigh-... Wiped it again, tried to make sure everything was wiped correctly, made sure everything was up to date. Tried again, but alas... Nothing working right for me.
Perhaps during this tale you've already picked up on something I royally messed up. Perhaps you're thinking, "Wow, how did this doofus not brick his tablet?" Am I getting old and stupid? Was there still research I missed? I started with the low road of easy modding and had to force myself to a higher road of deeper learning and STILL came up empty-handed, so now I'm asking this awesome community for a hand. I know you can't do this for me, but I'd appreciate a guiding light, or at the very least a link to an article that I really should have picked up on. Let me know if there's information I've missed that I should also be putting out, and thanks for reading regardless!
Click to expand...
Click to collapse
Hello, Lineage dev for T800 here.
Did you flash the updated bootloader I link in the OP? Gotta be on the MM one for it to boot past that samsung logo
Can be flashed via ODIN, instructions are on there!
Lemme know if you get it!
DarkExistence said:
Hello, Lineage dev for T800 here.
Did you flash the updated bootloader I link in the OP? Gotta be on the MM one for it to boot past that samsung logo
Can be flashed via ODIN, instructions are on there!
Lemme know if you get it!
Click to expand...
Click to collapse
Just got back from work, about to test it out and will update on both situations (should one not work out). Regardless of the success, I'm genuinely honored that you guys are helping me in this process and I didn't expect such a warm and welcoming bit of support. Too often I see the "well any bloomin' idiot with enough IQ in his head to tie his shoe could have done this" comment, although I'm almost positive I'm going to get this fixed with your help and realize I've done something super stupid.
Welp, I'm a right idiot. I went with the first option, which was to attempt to flash a stock MM ROM. I followed akopps and ashyx' advice and went to that website where I believed I found the appropriate file and downloaded it. For some odd reason it took about 8 hours to download almost 2gb, which is odd because my net is faster than that. Anyway, I let it sit overnight so no issues there. A while ago I attempted to copy it over to my SD card, which was met with a slew of problems thanks to the copy process being cancelled multiple times. Maybe because the size of it? I had plenty of space. At any rate, it wasn't going to be an issue because I knew it was something I was probably doing wrong and would figure out later. I skipped and went straight toward DarkExistence's fix, which was to make sure I had the MM bootloader (I saw this instruction in your thread but at the time wasn't sure what it entailed and thought I was perfectly safe, and this was sadly before I learned more about what I was doing). Went through that process just in case, wiped, flashed the Lineage ROM , flashed GAPPS, rebooted, aaaand...
Bugger me, it worked.
So now I feel like a proper idiot. I hope this ends up in a google search down the line so other doofuses can stumble upon my own mistake and see that sometimes overlooking one simple thing can make all the difference. Will update in the future should anything change and I find myself doomed once more, but so far things seem tip-top. I checked to see if I could install the mixer remote app I had initially begun this journey for, and lo and behold it is now available for me to download! Now all that's left is to figure out how to root it, and voila! Thank you all so much, I am almost as relieved as I am embarrassed.